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

Ability to link services on devices #2436

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

Originally created by @trunet on GitHub (Mar 5, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.5.7

Proposed Functionality

Netbox should have a way to link services on devices. If one device provides a service, it should be able to link (connect) it on another device.

Use Case

I have a storage cluster with multiple 4U nodes, each with its own IP address, network interfaces, memory, CPUs, .... On netbox, I created an NFS service on each storage node (device).

Than, I have my servers that access this devices, they can mount the NFS of one specific storage node.

I would like to link multiple servers connecting to each storage device so we can track what is connected where.

Originally created by @trunet on GitHub (Mar 5, 2019). ### Environment * Python version: 3.6 * NetBox version: 2.5.7 ### Proposed Functionality Netbox should have a way to link services on devices. If one device provides a service, it should be able to link (connect) it on another device. ### Use Case I have a storage cluster with multiple 4U nodes, each with its own IP address, network interfaces, memory, CPUs, .... On netbox, I created an NFS service on each storage node (device). Than, I have my servers that access this devices, they can mount the NFS of one specific storage node. I would like to link multiple servers connecting to each storage device so we can track what is connected where.
adam closed this issue 2025-12-29 17:26:04 +01:00
adam commented 2025-12-29 17:26:05 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Mar 5, 2019):

This would amount to a major new feature, and unfortunately we're not currently accepting requests which would extend NetBox's scope (see the contributing guide). It's a topic we'll almost certainly revisit at some point in the future once the current backlog of feature requests has been addressed.

@DanSheps commented on GitHub (Mar 5, 2019): This would amount to a major new feature, and unfortunately we're not currently accepting requests which would extend NetBox's scope (see the contributing guide). It's a topic we'll almost certainly revisit at some point in the future once the current backlog of feature requests has been addressed.
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#2436
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?