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

Remove specific data rates from InfiniBand interface choices #4843

New Issue
Closed
opened 2025-12-29 19:21:11 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:21:11 +01:00
Owner
Copy Link

Originally created by @krono on GitHub (Apr 28, 2021).

NetBox version

426e64ae8dd3 (v2.10.4)

Feature type

Change to existing functionality

Proposed functionality

The numeric data rates currently displayed for the different InfiniBand "speed generations" should be removed from the user interface.

Use case

Currently, the interface descriptions for InfiniBand EDR, HDR etc. include a numeric data rate:
Bildschirmfoto 2021-04-28 um 15 44 09

However, these can be potentially misleading.
The numeric data rates are correct for one lane of the data rate generation.
That is, one lane HDR has a data rate of 50 Gbps. However, next to no InfiniBand-Interface is one-lane;
most currently sold hardware is four-lane (or "has a port width of four" in InfiniBand TA parlance ).

This fact is often not even mentioned.
For example this HCA is a "HDR adapter" and supports a 200Gbps data rate; it is a four-lane HDR adapter, but that fact is nowhere mentioned. Simliarly, this switch supports HDR at 200Gbps (which is four-lane) or 100 Gbps "via splitter", which means, 2 times 2-lane HDR.

On the other hand, users might be temped to select from the interface list by number.
For example, say they have a switch that says "100Gbps" on the tin (and is in fact an EDR swich), so they select "NDR", which does not reflect reality.

Therefore dropping the numeric data rates will reduce the likelyhood of confusion about numeric data rates and InifniBand names.

Database changes

none

External dependencies

none

Originally created by @krono on GitHub (Apr 28, 2021). ### NetBox version 426e64ae8dd3 (v2.10.4) ### Feature type Change to existing functionality ### Proposed functionality The numeric data rates currently displayed for the different InfiniBand "speed generations" should be removed from the user interface. ### Use case Currently, the interface descriptions for InfiniBand EDR, HDR etc. include a numeric data rate: ![Bildschirmfoto 2021-04-28 um 15 44 09](https://user-images.githubusercontent.com/119279/116414369-b304c000-a838-11eb-88d4-84881c449dcd.PNG) However, these can be potentially misleading. The numeric data rates are correct for _one lane_ of the data rate generation. That is, _one lane HDR_ has a data rate of 50 Gbps. However, next to no InfiniBand-Interface is one-lane; most currently sold hardware is four-lane (or "has a port width of four" in [InfiniBand TA parlance](https://www.infinibandta.org/infiniband-roadmap/) ). This fact is often not even mentioned. For example [this HCA](https://store.mellanox.com/products/nvidia-mcx653105a-hdat-sp-connectx-6-vpi-adapter-card-hdr-infiniband-and-200gbe-single-port-qsfp56-pcie-4-0-x16-tall-bracket-sp-indicates-single-pack.html) is a "HDR adapter" and supports a 200Gbps data rate; it is a four-lane HDR adapter, but that fact is nowhere mentioned. Simliarly, [this switch](https://store.mellanox.com/products/nvidia-mqm8700-hs2f-quantum-hdr-infiniband-switch-40-qsfp56-ports-2-power-supplies-ac-x86-dual-core-standard-depth-p2c-airflow-rail-kit.html) supports HDR at 200Gbps (which is four-lane) or 100 Gbps "via splitter", which means, 2 times 2-lane HDR. On the other hand, users might be temped to select from the interface list by number. For example, say they have a switch that says "100Gbps" on the tin (and is in fact an EDR swich), so they select "NDR", which does not reflect reality. Therefore dropping the numeric data rates will reduce the likelyhood of confusion about numeric data rates and InifniBand names. ### Database changes none ### External dependencies none
adam added the type: featurepending closure labels 2025-12-29 19:21:11 +01:00
adam closed this issue 2025-12-29 19:21:11 +01:00
adam commented 2025-12-29 19:21:12 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 28, 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 28, 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:21:12 +01:00
Author
Owner
Copy Link

@krono commented on GitHub (Jun 28, 2021):

@callumstrubi, you provided the initial Infiniband code, would you agree with my reasoning?

@krono commented on GitHub (Jun 28, 2021): @callumstrubi, you provided the initial Infiniband code, would you agree with my reasoning?
adam commented 2025-12-29 19:21:12 +01:00
Author
Owner
Copy Link

@krono commented on GitHub (Sep 1, 2021):

:(

@krono commented on GitHub (Sep 1, 2021): :(
adam commented 2025-12-29 19:21:12 +01:00
Author
Owner
Copy Link

@krono commented on GitHub (Sep 1, 2021):

This is a simple documentation change wich just 3 days ago bit my colleague.

@krono commented on GitHub (Sep 1, 2021): This is a simple documentation change wich just 3 days ago bit my colleague.
adam commented 2025-12-29 19:21:13 +01:00
Author
Owner
Copy Link

@plaurin84 commented on GitHub (Sep 8, 2021):

I agree with @krono regarding the misleading values of Infiniband.
This issue is relevant to me as well.

@jeremystretch how can we help make this happen?

@plaurin84 commented on GitHub (Sep 8, 2021): I agree with @krono regarding the misleading values of Infiniband. This issue is relevant to me as well. @jeremystretch how can we help make this happen?
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#4843
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?