Enable the import of device types from JSON-formatted definitions

[jeremystretch]

Currently, each NetBox user must create their own device types. This results in wasted effort because users inevitably end up duplicating work. For instance, ten users who each use Juniper EX4300-48T switches will end up creating identical (or at least exceeding similar) device types.

We don't want to pre-populate device types in NetBox on initial installation, because it's impossible to predict which device types a user will want. Extraneous device types would result in clutter that needs to be deleted.

Ideally, we could begin compiling a library of device type definitions formatted as JSON. A user could select the desired device types from the library and import them into NetBox to create device types.

[fltchr]

Is this users per instance (i.e. if I create a device for a Cisco 3560, my boss won't be able to select it), or NetBox users in general (i.e. if I create a device, there is no "device community" to share it with other companies?

If the first point, I haven't noticed yet (haven't tested on more than one user account as of yet), but we'll definitely need that before moving forward., if the second, a user submitted gallery or library would be an awesome resource.

[rgstori]

+1 for the user submitted gallery, I think it would be very popular;
even with anybody's particular setting, little tweaks to each device type can
always be done after the import

[jeremystretch]

@fltchr "User" in this context just means an organization using NetBox. Sorry for the confusion.

Here's a scenario. You just got in a shipment of Juniper QFX5100-48S switches that need to be racked up. You've never used these before, so first you need to create a new device type in NetBox. But rather than creating one manually, you can instruct NetBox to import a definition from a GitHub repo, e.g. netbox-devicetypes/juniper/qfx5100-48s.json. NetBox downloads the file and automatically creates a new DeviceType along with its console, power, and interface templates as defined.

I just need to come up with the logic to process JSON and start a library.

[stianvi]

@jeremystretch There are also modules for devices that need to be taken into consideration.

example:
QFX5100-24Q: 32 ports (with hot-swappable expansion modules)
QFX5100-24Q-AA: 32 ports (with hot-swappable expansion modules)

And then there is the cabling too:
QFX5100-48S: 72 ports (48 10GbE SFP/SFP+ ports + 24 10GbE ports using QSFP+ to SFP+ DAC or QSFP+ to SFP+ fiber splitter cables and optics)

[jeremystretch]

@stianvi Expansion modules aren't part of the device, so they aren't attached to a device type. They may or may not be installed; that's up to the user to define. And cabling isn't modelled at all.

[leandroteleco]

I'm very interested on this feature.
I'm working at important Service Provider and we are testing Netbox at our Demolab,

Thanks you for to do and to improve NetBox, I think could countribute with the device types submitted gallery. :)

[askbow]

An export feature for device types might be a good idea too: some of us have already created libraries of devices, sharing them might be useful, given import is implemented.

[tobymccann]

This would be extremely useful, including some of the ideas already mentioned such as export. I imagine some type of verification mechanism to verify the accuracy of each device type, but that could probably be controlled via Github workflow.

[prolix21]

This would save so much work. We just setup Netbox and the thought of having to create all these device types gives me a headache.