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

Using single service for multiple virtual machines/devices #10129

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

Originally created by @betadrome on GitHub (Aug 22, 2024).

NetBox version

v4.0.9

Feature type

Data model extension

Proposed functionality

I am proposing a new feature in NetBox that would allow a single service to be associated with multiple virtual machines or devices.
It would therefore be good if you could either specify no virtual machine/device at all or as many as possible. In other cases, it can also be useful if you can specify devices and virtual machines at the same time, although I can't think of a direct example at the moment.

Use case

For example, in the context of a high-availability cluster, it is usually not defined on which virtual machine or on which devices exactly the service is currently running.
Classic examples here would be:

  • Nginx
  • HAProxy
  • Amazon Elastic Load Balancing (ELB)
  • Kubernetes Ingress Controller
    … in conjunction with the underlying services, for example monitoring.

Database changes

Probably

External dependencies

Since the feature already exists in this form, I don't think so

Originally created by @betadrome on GitHub (Aug 22, 2024). ### NetBox version v4.0.9 ### Feature type Data model extension ### Proposed functionality I am proposing a new feature in NetBox that would allow a single service to be associated with multiple virtual machines or devices. It would therefore be good if you could either specify no virtual machine/device at all or as many as possible. In other cases, it can also be useful if you can specify devices and virtual machines at the same time, although I can't think of a direct example at the moment. ### Use case For example, in the context of a high-availability cluster, it is usually not defined on which virtual machine or on which devices exactly the service is currently running. Classic examples here would be: * Nginx * HAProxy * Amazon Elastic Load Balancing (ELB) * Kubernetes Ingress Controller … in conjunction with the underlying services, for example monitoring. ### Database changes Probably ### External dependencies Since the feature already exists in this form, I don't think so
adam added the type: featurecomplexity: mediumnetboxstatus: backlog labels 2025-12-29 21:27:14 +01:00
adam commented 2025-12-29 21:27:15 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 22, 2024):

I think my FR (if implemented) would also accomplish what you're asking for: https://github.com/netbox-community/netbox/issues/17196

@ghost commented on GitHub (Aug 22, 2024): I think my FR (if implemented) would also accomplish what you're asking for: https://github.com/netbox-community/netbox/issues/17196
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 complexity: medium netbox status: backlog 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#10129
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?