Adding media ports #4235

Closed
opened 2025-12-29 18:34:10 +01:00 by adam · 6 comments
Owner

Originally created by @pozar on GitHub (Nov 1, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.9.8

Proposed Functionality

Netbox would be perfect for recording and broadcast studios but there needs to be a couple of different categories of media interfaces added such as video and audio. Of course, there are analog and digital components to each such as:

Audio
Analog
RCA Pin Plug - Male
RCA Pin Plug - Female
XLR - Male
XLR - Female
1/4" TRS - Male
1/4" TRS - Female
1/4" TS - Male
1/4" TS - Female
3.5mm TRS - Male
3.5mm TRS - Female
3.5mm TRRS - Male
3.5mm TRRS - Female
...
Digital
SPIDF - Optical
SPIDF - Coax
AES3 - Male
AES3 - Female
HDMI Type A
HDMI Type B
HDMI Type C
HDMI Type D
HDMI Type E
...
Video
Analog
Composite BNC - Male
Composite RCA - Male
S-Video - Male
VGA - Male
...
Digital
HDMI Type A
DVI-D Dual-Link
DVI-D Single-Link
DVI-I Dual-Link
DVI-I Single-Link
Mini DisplayPort
...

Use Case

Recording and Broadcast Studios

Database Changes

Possibly new tables such as dcim_media*

External Dependencies

No external libraries or services should be needed.

Originally created by @pozar on GitHub (Nov 1, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/g/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.9 * NetBox version: 2.9.8 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Netbox would be perfect for recording and broadcast studios but there needs to be a couple of different categories of media interfaces added such as video and audio. Of course, there are analog and digital components to each such as: Audio Analog RCA Pin Plug - Male RCA Pin Plug - Female XLR - Male XLR - Female 1/4" TRS - Male 1/4" TRS - Female 1/4" TS - Male 1/4" TS - Female 3.5mm TRS - Male 3.5mm TRS - Female 3.5mm TRRS - Male 3.5mm TRRS - Female ... Digital SPIDF - Optical SPIDF - Coax AES3 - Male AES3 - Female HDMI Type A HDMI Type B HDMI Type C HDMI Type D HDMI Type E ... Video Analog Composite BNC - Male Composite RCA - Male S-Video - Male VGA - Male ... Digital HDMI Type A DVI-D Dual-Link DVI-D Single-Link DVI-I Dual-Link DVI-I Single-Link Mini DisplayPort ... <!-- 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 Recording and Broadcast Studios <!-- 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 Possibly new tables such as dcim_media* <!-- 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 No external libraries or services should be needed.
adam closed this issue 2025-12-29 18:34:10 +01:00
Author
Owner

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

The interface model is intended to model only network interfaces, so it would not make sense to add non-network types. This has been proposed and rejected in prior feature requests.

@jeremystretch commented on GitHub (Nov 2, 2020): The interface model is intended to model only network interfaces, so it would not make sense to add non-network types. This has been proposed and rejected in prior feature requests.
Author
Owner

@pozar commented on GitHub (Nov 3, 2020):

@jeremystretch Netbox supports power and console interfaces/ports that are not network. Could you suggest another model here for media ports in netbox?

@pozar commented on GitHub (Nov 3, 2020): @jeremystretch Netbox supports power and console interfaces/ports that are not network. Could you suggest another model here for media ports in netbox?
Author
Owner

@pozar commented on GitHub (Nov 3, 2020):

@jeremystretch Just to follow up, if I did the work, would it be accepted in the main branch?

@pozar commented on GitHub (Nov 3, 2020): @jeremystretch Just to follow up, if I did the work, would it be accepted in the main branch?
Author
Owner

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

Netbox supports power and console interfaces/ports that are not network

Yes, and it has specific models to support those. It does not use the Interface model for that purpose.

if I did the work, would it be accepted in the main branch?

No, because this functionality is outside NetBox's scope. Again, this has already been discussed in previous issues.

@jeremystretch commented on GitHub (Nov 3, 2020): > Netbox supports power and console interfaces/ports that are not network Yes, and it has specific models to support those. It does not use the Interface model for that purpose. > if I did the work, would it be accepted in the main branch? No, because this functionality is outside NetBox's scope. Again, this has already been discussed in previous issues.
Author
Owner

@ypid commented on GitHub (Nov 4, 2020):

Sounds like a nice scope for a plugin. Go wild @pozar :). From what I see, the docs for plugin development are extensive: https://netbox.readthedocs.io/en/stable/plugins/development/

Ref: #3020, #2865
Cc: @kdadev, @candlerb

@ypid commented on GitHub (Nov 4, 2020): Sounds like a nice scope for a plugin. Go wild @pozar :). From what I see, the docs for plugin development are extensive: https://netbox.readthedocs.io/en/stable/plugins/development/ Ref: #3020, #2865 Cc: @kdadev, @candlerb
Author
Owner

@pozar commented on GitHub (Nov 5, 2020):

@ypid Thanks for the pointer. I'll review this.

@pozar commented on GitHub (Nov 5, 2020): @ypid Thanks for the pointer. I'll review this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4235