Enable linking circuits based on a common circuit service group #94

Closed
opened 2025-12-29 15:32:40 +01:00 by adam · 7 comments
Owner

Originally created by @ryanmerolle on GitHub (Jun 30, 2016).

Circuits seems to be specifically focused on a single end, but there is no way to link circuits tied to a single "service group." A service group would be 1 or many circuits.

Originally created by @ryanmerolle on GitHub (Jun 30, 2016). Circuits seems to be specifically focused on a single end, but there is no way to link circuits tied to a single "service group." A service group would be 1 or many circuits.
adam closed this issue 2025-12-29 15:32:40 +01:00
Author
Owner

@rkwl1 commented on GitHub (Jul 12, 2016):

Circuits should be able to link the A and Z location. Also a field for cross connect provider, as those can change from datacenter to datacenter.

@rkwl1 commented on GitHub (Jul 12, 2016): Circuits should be able to link the A and Z location. Also a field for cross connect provider, as those can change from datacenter to datacenter.
Author
Owner

@ryanmerolle commented on GitHub (Jul 13, 2016):

Yep as the feature states this would be achieved given some sort of service group. Service groups allow for not just A to Z, but A through Z and some.

@ryanmerolle commented on GitHub (Jul 13, 2016): Yep as the feature states this would be achieved given some sort of service group. Service groups allow for not just A to Z, but A through Z and some.
Author
Owner

@bsakdol commented on GitHub (Nov 30, 2016):

Just my two cents, since I was looking for this exact feature... The A to Z link of a circuit is what I was originally looking for, but I could certainly see how a service group would be more generally beneficial, since multi-point connections could be grouped together in this way. Either way, it would be great to see this feature added.

@bsakdol commented on GitHub (Nov 30, 2016): Just my two cents, since I was looking for this exact feature... The A to Z link of a circuit is what I was originally looking for, but I could certainly see how a service group would be more generally beneficial, since multi-point connections could be grouped together in this way. Either way, it would be great to see this feature added.
Author
Owner

@alexjhart commented on GitHub (Dec 20, 2016):

I was looking to solve connecting two ends of a circuit today and found this service group issue would likely solve that. I wonder if this is more of a short term feature request or more of a long term roadmap type item? I see it has been open for several months, yet has the minor feature tag.

@alexjhart commented on GitHub (Dec 20, 2016): I was looking to solve connecting two ends of a circuit today and found this service group issue would likely solve that. I wonder if this is more of a short term feature request or more of a long term roadmap type item? I see it has been open for several months, yet has the minor feature tag.
Author
Owner

@jeremystretch commented on GitHub (Dec 21, 2016):

#49 has been completed to allow for both the A and Z sides of a circuit to be defined (this will be available in v1.8.0). I'm going to close this issue out as it seems to overlap heavily with this feature. Adding a mechanism for grouping circuits seems like it would be redundant to the existing combination of provider and type.

@jeremystretch commented on GitHub (Dec 21, 2016): #49 has been completed to allow for both the A and Z sides of a circuit to be defined (this will be available in v1.8.0). I'm going to close this issue out as it seems to overlap heavily with this feature. Adding a mechanism for grouping circuits seems like it would be redundant to the existing combination of provider and type.
Author
Owner

@ryanmerolle commented on GitHub (Dec 21, 2016):

So how does this take care of carrier provided MPLS and VPLS circuits where there are multiple sides to a service?

@ryanmerolle commented on GitHub (Dec 21, 2016): So how does this take care of carrier provided MPLS and VPLS circuits where there are multiple sides to a service?
Author
Owner

@jeremystretch commented on GitHub (Dec 21, 2016):

Each circuit has only two endpoints, regardless of the type of service it carries.

@jeremystretch commented on GitHub (Dec 21, 2016): Each circuit has only two endpoints, regardless of the type of service it carries.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#94