Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Netbox integration to request VLAN-ID's and IP space for new transit sessions with customers (tenants) #263

Open
ebais opened this issue Jun 25, 2020 · 2 comments
Assignees
Labels
status: accepted type: feature request Issue is an accepted feature request
Milestone

Comments

@ebais
Copy link

ebais commented Jun 25, 2020

As you are working on Netbox integration anyway, please provide the feature to request a vlan ID (pool) and IPv4 and IPv6 range (from a pool) and assign them to a tenants (perhaps even to a specific port on a device ... )

It will allow the peering-manager to assist in setting up BGP transit sessions towards customers and make it easier and faster to deploy them. ( especially across various devices with multiple sessions. )

@gmazoyer gmazoyer self-assigned this Jun 25, 2020
@gmazoyer gmazoyer added the type: feature request Issue is an accepted feature request label Jun 25, 2020
@gmazoyer
Copy link
Member

This is definitively some kind of NetBox interaction that we could have for better automation. We do need to track the interconnections, VLANs and device ports. It would probably be smart to think about this while dealing with #246.

@gmazoyer gmazoyer added this to the v2.0 milestone Oct 11, 2020
@mngan
Copy link
Contributor

mngan commented Oct 12, 2020

For our use case, we mainly want to allocate the link nets for the connection from a specific pool associated the device/site, and have that pushed back into Netbox as well. I was planning on doing this as a plugin for Netbox that pushed the BGP creation request to Peering-Manager, which what my current standalone provisioning tool does. But we don't use VLAN's for most of our connections, so it would be good to have that be optional.

@jamesditrapani jamesditrapani added this to To do in NetBox via automation Apr 30, 2021
@stale stale bot added the status: wontfix Not an issue, no fix to be done, no code to be changed label Jul 12, 2021
@peering-manager peering-manager deleted a comment from stale bot Jul 12, 2021
@stale stale bot removed the status: wontfix Not an issue, no fix to be done, no code to be changed label Jul 12, 2021
@gmazoyer gmazoyer removed this from To do in NetBox Dec 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: accepted type: feature request Issue is an accepted feature request
Projects
None yet
Development

No branches or pull requests

3 participants