Plugin version
v1.1.18
NetBox version
v4.5.8
Feature type
New functionality
Proposed functionality
Hello Daniel,
I've read and understood you want to keep the scope of this plugin narrow, thus this FR before going into a PR.
Would you be open to include Software lifecycle ?
Data model can be quite simple : Manufacturers, Device Type, Version, EoM, EoSecurity, EoSupport (+ the usual Notice, Documentation, Description, Tags, Comments)
Software versions could then be assigned to devices (through the device page, or through the software page).
Similar to the Netbox device-type repo, the list of software and their characteristics could be maintained by the OpenSource community.
Would you be open to include an EoL date in the Licenses ?
Adding one date field in the Licence data model to include the EoL of the license. This would be different from the End Date of the contract assignement you can assign to a license. For example you can have a support contract end date different from the license end date.
Use case
Software lifecycle
This would allow network and security team to keep track of outdated software version deployed, prevent security breach, and help in the overall lifecycle management of the infrastructure.
EoL date for licenses
Part of our job (not the best one) is to review the licenses to renew for our network switches.
We could use a tool that keeps track of the EoL of the installed licenses to ease our renewal process or even automate it.
Database changes
All explained above.
External dependencies
None.
Plugin version
v1.1.18
NetBox version
v4.5.8
Feature type
New functionality
Proposed functionality
Hello Daniel,
I've read and understood you want to keep the scope of this plugin narrow, thus this FR before going into a PR.
Would you be open to include Software lifecycle ?
Data model can be quite simple : Manufacturers, Device Type, Version, EoM, EoSecurity, EoSupport (+ the usual Notice, Documentation, Description, Tags, Comments)
Software versions could then be assigned to devices (through the device page, or through the software page).
Similar to the Netbox device-type repo, the list of software and their characteristics could be maintained by the OpenSource community.
Would you be open to include an EoL date in the Licenses ?
Adding one date field in the Licence data model to include the EoL of the license. This would be different from the End Date of the contract assignement you can assign to a license. For example you can have a support contract end date different from the license end date.
Use case
Software lifecycle
This would allow network and security team to keep track of outdated software version deployed, prevent security breach, and help in the overall lifecycle management of the infrastructure.
EoL date for licenses
Part of our job (not the best one) is to review the licenses to renew for our network switches.
We could use a tool that keeps track of the EoL of the installed licenses to ease our renewal process or even automate it.
Database changes
All explained above.
External dependencies
None.