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

Have circuits capable of hosting services #1995

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

Originally created by @oskaregils on GitHub (Sep 9, 2018).

We are interested in having a list of "services" assigned to a circuit.
This would be a new container in the GUI similar to what exists on devices.

We could use the current services configuration fields even though it is not directly applicable to my use-case.
I have another concept I´m trying to put together that relates to idea of Netbox managing a new object called services ...but that is perhaps too extensive.

It would be useful to be able to assign/refrence a backup/secondary circuit to the service.
Assume same could apply to services hosted on devices?

The usecase relates to our setup.
We could have circuits either failing or being reported to go to scheduled down time (maintenance).
For this I want to see a list of services transported across that circuit and would be affected.
Also useful to see what services are being routed over secondary circuit as backup so they will be protected.

Assume this is a minor add-on as this feature already exists for devices and is to be applied to circuits the same way. At least for the simple version, without reference to secondary/backup device/circuit

Originally created by @oskaregils on GitHub (Sep 9, 2018). We are interested in having a list of "services" assigned to a circuit. This would be a new container in the GUI similar to what exists on devices. We could use the current services configuration fields even though it is not directly applicable to my use-case. I have another concept I´m trying to put together that relates to idea of Netbox managing a new object called services ...but that is perhaps too extensive. It would be useful to be able to assign/refrence a backup/secondary circuit to the service. Assume same could apply to services hosted on devices? The usecase relates to our setup. We could have circuits either failing or being reported to go to scheduled down time (maintenance). For this I want to see a list of services transported across that circuit and would be affected. Also useful to see what services are being routed over secondary circuit as backup so they will be protected. Assume this is a minor add-on as this feature already exists for devices and is to be applied to circuits the same way. At least for the simple version, without reference to secondary/backup device/circuit
adam closed this issue 2025-12-29 17:21:17 +01:00
adam commented 2025-12-29 17:21:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 10, 2018):

NetBox models TCP/UDP services only as they relate to specific devices. Tracking higher-level modeling of dependencies is out of scope for the project.

@jeremystretch commented on GitHub (Sep 10, 2018): NetBox models TCP/UDP services only as they relate to specific devices. Tracking higher-level modeling of dependencies is out of scope for the project.
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#1995
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?