Support for offline storage of modules

[jeremystretch]

NetBox version

v4.2.6

Feature type

Data model extension

Proposed functionality

Add ForeignKeys to Site and Location on the Module model, replicating what exists today on the Device model. If the module is installed within a device, these values will be inherited from the parent device. If not installed within a device, the module can be assigned to a site and (optionally) a location designated for storage.

We should also add an explicit "storage" choice for the status fields on both Device and Module.

Use case

Introducing a relationship between a module and a site/location enables a module to exist outside the context of a parent device. Although modules generally are not considered operational on their own, this is useful for tracking modules for inventory purposes.

Database changes

• Add site and location ForeignKeys on Module

External dependencies

N/A

[jeremystretch]

Unfortunately this is going to be more complicated than originally assumed. One of the reasons NetBox currently prohibits moving modules among devices is that the individual components belonging to a module may introduce blocking relationships. For example, interfaces belonging to a module are also assigned to a device; deinstalling the module requires severing that relationship. This is especially involved where those interfaces (or similar components) serve as cable termination points.

Another complicating factor is token-based component names. When a component template is added to a module type, its name can be tokenized to effect automatic naming according to the module bay in which it is installed. "Removing" a module requires reversing that renaming function, however no canonical backward path currently exists.

This is going to require substantially more planning and implementation work than I had hoped. Given that we're due to release the v4.3 beta in just two weeks, I'm going to bump it from that milestone.