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

Assignment of power feeds to location #4794

New Issue
Closed
opened 2025-12-29 19:20:33 +01:00 by adam · 6 comments
adam commented 2025-12-29 19:20:33 +01:00
Owner
Copy Link

Originally created by @martinum4 on GitHub (Apr 19, 2021).

NetBox version

v2.11-beta1

Feature type

Change to existing functionality

Proposed functionality

  • Allow Power feeds to be assigned to a Location and define default values for Voltage and Amperage.

Examples:

  • We define a Location (Room) in Berlin for Telco-Equipment where the defaults are 48VDC.
  • We connect a rackmounted PDU to an outlet that is mounted overhead on a ceiling cable tray.

Use case

By being able to assign Feeds to a location it is easier to map out responsibilities inside a campus-like setting, especially when you see a power feed as an instance of a circuit-breaker, Admin responsibilities usually ends at the circuit breaker and everything beyond that is handled by facility professionals and should be out of scope for Netbox.

Database changes

No response

External dependencies

No response

Originally created by @martinum4 on GitHub (Apr 19, 2021). ### NetBox version v2.11-beta1 ### Feature type Change to existing functionality ### Proposed functionality - Allow Power feeds to be assigned to a Location and define default values for Voltage and Amperage. Examples: - We define a Location (Room) in Berlin for Telco-Equipment where the defaults are 48VDC. - We connect a rackmounted PDU to an outlet that is mounted overhead on a ceiling cable tray. ### Use case By being able to assign Feeds to a location it is easier to map out responsibilities inside a campus-like setting, especially when you see a power feed as an instance of a circuit-breaker, Admin responsibilities usually ends at the circuit breaker and everything beyond that is handled by facility professionals and should be out of scope for Netbox. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:20:33 +01:00
adam closed this issue 2025-12-29 19:20:33 +01:00
adam commented 2025-12-29 19:20:34 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Apr 22, 2021):

Power feeds belong to a power panel, and a power panel can be assigned to a location (formerly rackgroup) - see sketch at #5534. In essence, a power panel is a grouping of (one or more) power feeds at a physical location.

Could you therefore model it by creating a power panel in each of the different locations where there is a power feed / circuit breaker?

@candlerb commented on GitHub (Apr 22, 2021): Power feeds belong to a power panel, and a power panel can be assigned to a location (formerly rackgroup) - see sketch at #5534. In essence, a power panel is a grouping of (one or more) power feeds at a physical location. Could you therefore model it by creating a power panel in each of the different locations where there is a power feed / circuit breaker?
adam commented 2025-12-29 19:20:34 +01:00
Author
Owner
Copy Link

@tchmnkyz commented on GitHub (Apr 29, 2021):

See Personally I would like to see it where i can have a power panel and that has its sources (feeds) and then you can break the panel down and have breaker 01 and 03 goes to rack 001, breaker 02 and 04 goes to rack 002. And then it would be really nice if we could get a visualization of the power panel similar to a rack elevation.

@tchmnkyz commented on GitHub (Apr 29, 2021): See Personally I would like to see it where i can have a power panel and that has its sources (feeds) and then you can break the panel down and have breaker 01 and 03 goes to rack 001, breaker 02 and 04 goes to rack 002. And then it would be really nice if we could get a visualization of the power panel similar to a rack elevation.
adam commented 2025-12-29 19:20:34 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Apr 29, 2021):

I don't actually use the power features of Netbox, but I thought the model was the other way round: a power feed is not the input to a power panel, a power feed is the output from a power panel (i.e. a "breaker" in your terminology).

@candlerb commented on GitHub (Apr 29, 2021): I don't actually use the power features of Netbox, but I thought the model was the other way round: a power feed is not the *input* to a power panel, a power feed is the *output* from a power panel (i.e. a "breaker" in your terminology).
adam commented 2025-12-29 19:20:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 29, 2021):

I thought the model was the other way round: a power feed is not the input to a power panel, a power feed is the output from a power panel

This is correct. The flow is power panel -> power feed -> power port.

@jeremystretch commented on GitHub (Apr 29, 2021): > I thought the model was the other way round: a power feed is not the input to a power panel, a power feed is the output from a power panel This is correct. The flow is power panel -> power feed -> power port.
adam commented 2025-12-29 19:20:35 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 29, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 29, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:20:35 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 29, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jul 29, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 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#4794
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?