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

Port types for AV equipment #2473

New Issue
Closed
opened 2025-12-29 18:19:10 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:19:10 +01:00
Owner
Copy Link

Originally created by @kdadev on GitHub (Mar 20, 2019).

We have used NetBox on TV infrastructure management. To describe links between audio and video devices we have to add few port types.
Video: BNC-SDI, HD-BNC, BNC-CVBS, S-VIDEO and some vendor-specific
Audio: TRS, XLR, mini-TRS and some vendor specific.

I'm not sure that these additions should be pushed into main code, but for feature releases of NetBox it could be good for us to know, which constant values in dcim/constants.py should be best to use to escape possible incompatibility in the future.

Say, we get to use new constant PORT_TYPE_VIDEO_HDBNC. Which value is best to use for this constant to avoid intersection with new port types added in future releases? Is there any range of values for custom usage only?

Originally created by @kdadev on GitHub (Mar 20, 2019). We have used NetBox on TV infrastructure management. To describe links between audio and video devices we have to add few port types. **Video:** BNC-SDI, HD-BNC, BNC-CVBS, S-VIDEO and some vendor-specific **Audio:** TRS, XLR, mini-TRS and some vendor specific. I'm not sure that these additions should be pushed into main code, but for feature releases of NetBox it could be good for us to know, which constant values in **dcim/constants.py** should be best to use to escape possible incompatibility in the future. Say, we get to use new constant `PORT_TYPE_VIDEO_HDBNC`. Which value is best to use for this constant to avoid intersection with new port types added in future releases? Is there any range of values for custom usage only?
adam added the status: duplicate label 2025-12-29 18:19:10 +01:00
adam closed this issue 2025-12-29 18:19:10 +01:00
adam commented 2025-12-29 18:19:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 20, 2019):

This issue has been closed as it does not conform to one of the provided templates as required by the contributing guide. If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).

@jeremystretch commented on GitHub (Mar 20, 2019): This issue has been closed as it does not conform to one of the [provided templates](https://github.com/digitalocean/netbox/issues/new/choose) as required by the [contributing guide](https://github.com/digitalocean/netbox/blob/master/CONTRIBUTING.md). If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).
adam commented 2025-12-29 18:19:11 +01:00
Author
Owner
Copy Link

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

In addition to what Jeremy mentioned, this has been proposed in:

#2865
#1272

The ultimate decision is TV infrastructure is outside of the scope of Netbox.

@DanSheps commented on GitHub (Mar 20, 2019): In addition to what Jeremy mentioned, this has been proposed in: #2865 #1272 The ultimate decision is TV infrastructure is outside of the scope of Netbox.
adam commented 2025-12-29 18:19:11 +01:00
Author
Owner
Copy Link

@kdadev commented on GitHub (Mar 20, 2019):

You're right. Thanks.

@kdadev commented on GitHub (Mar 20, 2019): You're right. Thanks.
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: duplicate
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#2473
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?