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

Fibre Optic Cable with Tube modelling #10485

New Issue
Closed
opened 2025-12-29 21:32:07 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:32:07 +01:00
Owner
Copy Link

Originally created by @Etibru on GitHub (Nov 16, 2024).

NetBox version

v4.1.6

Feature type

Data model extension

Triage priority

N/A

Proposed functionality

In many cases, the modeling of fiber cables in Netbox is not precise enough. It would be very interesting to model a fiber cable that contains tubes, which themselves contain fibers.
For example, in the vast majority of cases, a 48-fiber cable is made up of several different-colored tubes, each containing different-colored fibers.
image

image

Use case

In a datacenter, fiber rocades are positioned between the MMR (meet me room) and the IT rooms. Very often these are several cables with different optical fiber capacities (24, 48, 72, 128, ...) and at each end we have patch panels.
To be able to identify a particular fiber in a cable, you'd need to know that its position on a patch panel refers to the purple fiber in the blue tube of cable XXX.

Database changes

No response

External dependencies

No response

Originally created by @Etibru on GitHub (Nov 16, 2024). ### NetBox version v4.1.6 ### Feature type Data model extension ### Triage priority N/A ### Proposed functionality In many cases, the modeling of fiber cables in Netbox is not precise enough. It would be very interesting to model a fiber cable that contains tubes, which themselves contain fibers. For example, in the vast majority of cases, a 48-fiber cable is made up of several different-colored tubes, each containing different-colored fibers. ![image](https://github.com/user-attachments/assets/0776e81a-7bb2-4dad-9ea5-d46bd942fd35) ![image](https://github.com/user-attachments/assets/4304a956-f1bf-4bda-befa-e4dc17b29e36) ### Use case In a datacenter, fiber rocades are positioned between the MMR (meet me room) and the IT rooms. Very often these are several cables with different optical fiber capacities (24, 48, 72, 128, ...) and at each end we have patch panels. To be able to identify a particular fiber in a cable, you'd need to know that its position on a patch panel refers to the purple fiber in the blue tube of cable XXX. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 21:32:07 +01:00
adam closed this issue 2025-12-29 21:32:07 +01:00
adam commented 2025-12-29 21:32:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 18, 2024):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Nov 18, 2024): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 21:32:08 +01:00
Author
Owner
Copy Link

@Etibru commented on GitHub (Nov 18, 2024):

Thank you. The subject is perhaps too complicated to be treated as an issue, I have taken the content and created a discussion to find the best modeling solution. :)
Fibre Optic Cable with Tube modelling · netbox-community/netbox · Discussion #18036

@Etibru commented on GitHub (Nov 18, 2024): Thank you. The subject is perhaps too complicated to be treated as an issue, I have taken the content and created a discussion to find the best modeling solution. :) [Fibre Optic Cable with Tube modelling · netbox-community/netbox · Discussion #18036](https://github.com/netbox-community/netbox/discussions/18036)
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 status: revisions needed 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#10485
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?