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

InfiniBand support for virtual interface. #4149

New Issue
Closed
opened 2025-12-29 18:33:27 +01:00 by adam · 5 comments
adam commented 2025-12-29 18:33:27 +01:00
Owner
Copy Link

Originally created by @blackgold on GitHub (Sep 28, 2020).

Environment

  • Python version: 3.7.0
  • NetBox version: v2.8.9

Proposed Functionality

Infiniband devices support SRIOV feature. When creating virtual functions, node and port GUID are empty. Operator sets node and port guid. It will be helpful to keep track of these virtual interfaces and their corresponding node and port GUIDs.

In the current net box, when an interface of Type "virtual" is created, there is no option to specify

  1. that the interface is InfiniBand vf
  2. no option to specify node and port guid.

I will be nice to have the ability to specify that the virtual interface is of type InfiniBand, and it has so and so node guid and port guid. This can be interface property or we can have something like GUID-AM (guid address management) and attach GUID object to the interface, just like IP address can be attached to virtual interface.

Use Case

When creating InfiniBand virtual functions, node and port GUID are empty. Operator sets node and port guid. It will be helpful to keep track of these virtual interfaces and their corresponding node and port GUIDs. For example when a node reboots, a startup script can read interface information from netbox and set the node and port guids.

Database Changes

I am a netbox noob. I suppose it would require to extend interface of type virtual.

External Dependencies

I don't think there is need for any external dependencies.

Originally created by @blackgold on GitHub (Sep 28, 2020). ### Environment * Python version: 3.7.0 * NetBox version: v2.8.9 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Infiniband devices support SRIOV feature. When creating virtual functions, node and port GUID are empty. Operator sets node and port guid. It will be helpful to keep track of these virtual interfaces and their corresponding node and port GUIDs. In the current net box, when an interface of Type "virtual" is created, there is no option to specify 1. that the interface is InfiniBand vf 2. no option to specify node and port guid. I will be nice to have the ability to specify that the virtual interface is of type InfiniBand, and it has so and so node guid and port guid. This can be interface property or we can have something like GUID-AM (guid address management) and attach GUID object to the interface, just like IP address can be attached to virtual interface. <!-- 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 When creating InfiniBand virtual functions, node and port GUID are empty. Operator sets node and port guid. It will be helpful to keep track of these virtual interfaces and their corresponding node and port GUIDs. For example when a node reboots, a startup script can read interface information from netbox and set the node and port guids. <!-- 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 I am a netbox noob. I suppose it would require to extend interface of type virtual. <!-- 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 I don't think there is need for any external dependencies.
adam added the pending closurestatus: under review labels 2025-12-29 18:33:27 +01:00
adam closed this issue 2025-12-29 18:33:27 +01:00
adam commented 2025-12-29 18:33:27 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Sep 28, 2020):

Potentially linked to https://github.com/netbox-community/netbox/issues/5102

@jsenecal commented on GitHub (Sep 28, 2020): Potentially linked to https://github.com/netbox-community/netbox/issues/5102
adam commented 2025-12-29 18:33:27 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Oct 6, 2020):

Possibly also relates to #1254

@candlerb commented on GitHub (Oct 6, 2020): Possibly also relates to #1254
adam commented 2025-12-29 18:33:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 16, 2020):

Need someone familiar with InfiniBand to chime in here. #1519 proposes the ability to associate a virtual interface with a parent physical interface. Would that satisfy this FR? And if not, what would remain to be added assuming #1519 is implemented?

@jeremystretch commented on GitHub (Nov 16, 2020): Need someone familiar with InfiniBand to chime in here. #1519 proposes the ability to associate a virtual interface with a parent physical interface. Would that satisfy this FR? And if not, what would remain to be added assuming #1519 is implemented?
adam commented 2025-12-29 18:33:27 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Dec 31, 2020):

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.

@stale[bot] commented on GitHub (Dec 31, 2020): 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 18:33:27 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 16, 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.

@stale[bot] commented on GitHub (Jan 16, 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 status: under review
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#4149
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?