starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Software and Hardware lifecycle management #8383

New Issue
Closed
opened 2025-12-29 20:36:04 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:36:04 +01:00
Owner
Copy Link

Originally created by @ognjen011 on GitHub (Jul 29, 2023).

NetBox version

v3.5.6

Feature type

Data model extension

Proposed functionality

We have a bunch of different types of routers/servers with different OS versions. Under Devices a new option for Software and Hardware lifecycle or somewhere there with sub menu to divide software from the hardware. It would be really nice to be able to have as part of Netbox different images versions so that we can track the following options about these images, recommended version, current version installed, end of life for software ,LTS versions releases for the images. Same thing for the hardware to be able to see end of support for hardware, end of support contract with a vendor. End of software support end of security patches for the given hardware.

Use case

We have a bunch of different types of routers/servers with different OS versions. This would help with automating and planning upgrades. This allows better planing of the current inventory. It will prevent for the most part running versions of images that might already be end of life and unsupported by the vendor. I guess it will help to make sure that a specific reales that are running in the network do not have any serious vulnerability attached to that version of software release.

Database changes

Not sure what needs to change in the DB

External dependencies

None

Originally created by @ognjen011 on GitHub (Jul 29, 2023). ### NetBox version v3.5.6 ### Feature type Data model extension ### Proposed functionality We have a bunch of different types of routers/servers with different OS versions. Under Devices a new option for Software and Hardware lifecycle or somewhere there with sub menu to divide software from the hardware. It would be really nice to be able to have as part of Netbox different images versions so that we can track the following options about these images, recommended version, current version installed, end of life for software ,LTS versions releases for the images. Same thing for the hardware to be able to see end of support for hardware, end of support contract with a vendor. End of software support end of security patches for the given hardware. ### Use case We have a bunch of different types of routers/servers with different OS versions. This would help with automating and planning upgrades. This allows better planing of the current inventory. It will prevent for the most part running versions of images that might already be end of life and unsupported by the vendor. I guess it will help to make sure that a specific reales that are running in the network do not have any serious vulnerability attached to that version of software release. ### Database changes Not sure what needs to change in the DB ### External dependencies None
adam closed this issue 2025-12-29 20:36:04 +01:00
adam commented 2025-12-29 20:36:04 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jul 29, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@abhi1693 commented on GitHub (Jul 29, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:36:05 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jul 30, 2023):

@ognjen011, I would recommend looking for similar conversations in discussions (or start one) but otherwise this seems more like a feature that would be implemented in a plugin.

@jsenecal commented on GitHub (Jul 30, 2023): @ognjen011, I would recommend looking for similar conversations in discussions (or start one) but otherwise this seems more like a feature that would be implemented in a plugin.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure plugin candidate status: revisions needed type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8383
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?