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

Provider Network Service ID #5581

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

Originally created by @ryanmerolle on GitHub (Oct 29, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.0.8

Feature type

Data model extension

Proposed functionality

Most Service Providers assign a Service ID to the provider networks. It would be ideal if that were extended in the model.

The alternative is to just set a custom field for this, but I figure it is a common enough use case that the data model extension could be seen as reasonable.

Use case

For those who setup multiple mesh / provider networks, or need to call out a provider network issue, it is ideal to be able to track the service id of such a network.

Database changes

No response

External dependencies

No response

Originally created by @ryanmerolle on GitHub (Oct 29, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.0.8 ### Feature type Data model extension ### Proposed functionality Most Service Providers assign a Service ID to the provider networks. It would be ideal if that were extended in the model. The alternative is to just set a custom field for this, but I figure it is a common enough use case that the data model extension could be seen as reasonable. ### Use case For those who setup multiple mesh / provider networks, or need to call out a provider network issue, it is ideal to be able to track the service id of such a network. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:29:44 +01:00
adam closed this issue 2025-12-29 19:29:44 +01:00
adam commented 2025-12-29 19:29:45 +01:00
Author
Owner
Copy Link

@YWatchman commented on GitHub (Oct 29, 2021):

I created a customfield 'line_tag' which can optionally do regex validation, I think this is better to create as a customfield. Circuit IDs and cables should be documented under the section which is made for it.

@YWatchman commented on GitHub (Oct 29, 2021): I created a customfield 'line_tag' which can optionally do regex validation, I think this is better to create as a customfield. Circuit IDs and cables should be documented under the section which is made for it.
adam commented 2025-12-29 19:29:45 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Nov 12, 2021):

I created a customfield 'line_tag' which can optionally do regex validation, I think this is better to create as a customfield. Circuit IDs and cables should be documented under the section which is made for it.

I'm not sure I understand why it's better as a customfield. That is a good option, I just propose updating the model since many VPLS providers allow you to provision multiple provider networks if you so choose. They identify said networks with service ids in addition to the normal handoff circuit ids.

@ryanmerolle commented on GitHub (Nov 12, 2021): > I created a customfield 'line_tag' which can optionally do regex validation, I think this is better to create as a customfield. Circuit IDs and cables should be documented under the section which is made for it. I'm not sure I understand why it's better as a customfield. That is a good option, I just propose updating the model since many VPLS providers allow you to provision multiple provider networks if you so choose. They identify said networks with service ids in addition to the normal handoff circuit ids.
adam commented 2025-12-29 19:29:45 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 15, 2021):

I agree with Ryan, in a round about way.

Our provider has a circuit id and a "BPSO" (Big pipe service order) and I am sure many other providers are similar, so I think having an additional field is good approach.

@DanSheps commented on GitHub (Nov 15, 2021): I agree with Ryan, in a round about way. Our provider has a circuit id and a "BPSO" (Big pipe service order) and I am sure many other providers are similar, so I think having an additional field is good approach.
adam commented 2025-12-29 19:29:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 23, 2021):

I created a customfield 'line_tag' which can optionally do regex validation, I think this is better to create as a customfield

FYI custom validation was added for all fields in NetBox v3.0.

@jeremystretch commented on GitHub (Dec 23, 2021): > I created a customfield 'line_tag' which can optionally do regex validation, I think this is better to create as a customfield FYI [custom validation](https://netbox.readthedocs.io/en/stable/customization/custom-validation/) was added for all fields in NetBox v3.0.
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: accepted 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#5581
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?