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

Add Power Panel or Power Feed Chaining or a Description Field to Power Panel #3051

New Issue
Closed
opened 2025-12-29 18:25:09 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:25:09 +01:00
Owner
Copy Link

Originally created by @jlhuston on GitHub (Dec 8, 2019).

Environment

  • Python version:
  • NetBox version:

Proposed Functionality

It would be useful to show chaining of electrical power as it flows from panel to subpanel (to distribution panel, etc.) before heading to individual feeds that are then connected to equipment.

An alternative solution would be to allow for a Markup description field on the Power Panel where I can add comments that describe the feed and then be able to search on it.

An alternate alternative would be to use a made up device to model circuit panels and daisychain feeds (similar to a PDU device), in which case, this is moot?

Use Case

This will allow for answering questions about what is impacted if a major power line outage is expected (as in, "we're disconnecting the high-voltage feed to panel H1D3 on Friday; will that impact the data center?" We could then use this chain of connections to trace the output of H1D3 to one or more panels and one or more feeds to equipment in order to assess impacts).

It would also be useful to summarize power utilization (I saw another feature request in place for showing power utilization up and down the chain of power usage).

Database Changes

For the relationship-based solution, allowing Power Panels to have a Power Port of their own that can connect to another Power Panel or Power Feed or device output (as in, a hardwired UPS or Transformer output).

For the description solution, the addition of a text field.

External Dependencies

None

Originally created by @jlhuston on GitHub (Dec 8, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: <!-- Example: 3.5.4 --> * NetBox version: <!-- Example: 2.3.6 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality It would be useful to show chaining of electrical power as it flows from panel to subpanel (to distribution panel, etc.) before heading to individual feeds that are then connected to equipment. An alternative solution would be to allow for a Markup description field on the Power Panel where I can add comments that describe the feed and then be able to search on it. An alternate alternative would be to use a made up device to model circuit panels and daisychain feeds (similar to a PDU device), in which case, this is moot? <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case This will allow for answering questions about what is impacted if a major power line outage is expected (as in, "we're disconnecting the high-voltage feed to panel H1D3 on Friday; will that impact the data center?" We could then use this chain of connections to trace the output of H1D3 to one or more panels and one or more feeds to equipment in order to assess impacts). It would also be useful to summarize power utilization (I saw another feature request in place for showing power utilization up and down the chain of power usage). <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes For the relationship-based solution, allowing Power Panels to have a Power Port of their own that can connect to another Power Panel or Power Feed or device output (as in, a hardwired UPS or Transformer output). For the description solution, the addition of a text field. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam closed this issue 2025-12-29 18:25:09 +01:00
adam commented 2025-12-29 18:25:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 9, 2019):

The model is limited to Power Panel -> Power Feed -> PDU -> Device because representing facility power infrastructure is out of scope for NetBox, which is primarily a network management tool.

An alternative solution would be to allow for a Markup description field on the Power Panel where I can add comments that describe the feed and then be able to search on it.

Please open a separate FR with a specific use case if you'd like to propose this.

@jeremystretch commented on GitHub (Dec 9, 2019): The model is limited to Power Panel -> Power Feed -> PDU -> Device because representing facility power infrastructure is out of scope for NetBox, which is primarily a network management tool. > An alternative solution would be to allow for a Markup description field on the Power Panel where I can add comments that describe the feed and then be able to search on it. Please open a separate FR with a specific use case if you'd like to propose this.
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
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#3051
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?