search

netbox-community / netbox

The premier source of truth powering network automation. Open source under Apache 2. Public demo: https://demo.netbox.dev
http://netboxlabs.com/oss/netbox/
Apache License 2.0
15.38k stars 2.49k forks source link

Custom fields for interfaces #1254

Closed jeanders closed 7 years ago

jeanders commented 7 years ago

Issue type: Feature request

It would be very handy to have the ability to configure custom fields on interfaces as well. I am currently looking to store information such as if it is access or trunk, workstation or printer, etc.

jeremystretch commented 7 years ago

This has come up before, and it's been decided not to extend custom fields to interfaces. #150 will address VLAN assignment, and descriptions can be used to indicate the type of connected device (in lieu of creating a discrete connection).

taktv6 commented 6 years ago

Seriously? Not supporting custom fields for interfaces unnecessarily limits the possibility to use netbox for automation purpose. Please fix.

hypokondrickard commented 6 years ago

it would be super useful here aswell. I'm building a services database where netbox is involved as a backend component. Because there is no way of "tagging" an interface with a service identifier and filter based on that via the API, I have to use a separate database to track what interfaces has been assigned the different services.

If it's been decided that custom fields on interfaces wont benefit mankind, could we still maybe make the /dcim/interfaces endpoint support filtering based on interface description?

Thanks a lot

sirtux commented 6 years ago

Hey @jeremystretch,

We have seen here 15 likes and 6 hearts for getting this feature - I understand if you don't have the ressources and time to implement this, but would you be willing to accept a patch for this?

If so, we would be willing to sponsor a patch in the near future.

Thanks, Tom

jord-bh commented 6 years ago

@sirtux @jeremystretch I would love to see this happen, it would open up a lot of automation capabilities revolving around interfaces. If I can be of any assistance be it testing or developing, I am also willing to put in some effort on this.

reening commented 5 years ago

Another +1 for this, for example I'd love to have the ability to add a custom boolean field to an interface for a DHCP client. Other use cases could be interface/encapsulation types or tunnel endpoints. I don't like filtering based on names and using the global config context, since these parameters are specific to the interface. It is currently limiting in writing full automation using Netbox.

I'd also be happy to spend some hours implementing this if it will be accepted. It seems that there is quite some demand for a feature like this.

sirtux commented 5 years ago

We are working on this right now, and probably create a pull request and see if this is accepted, since the maintainers don't comment here right now. Stay tuned.

aakso commented 5 years ago

I think custom fields are vital for the usability of any configuration database. I'm planning of generating the base configuration based on the device interfaces at the same time assigning link networks and such thru the IPAM.

hypokondrickard commented 5 years ago

Everyone, seems Mr Stretch has closed a feature request #2281 as beeing a duplicate to this one.

Fingers crossed this one is about to be re-opened.

jeremystretch commented 5 years ago

This issue has been discussed and closed. Locking this thread.