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

Enable assignment of VLAN during Prefix import #42

Closed
Gelob opened this issue Jun 27, 2016 · 2 comments
Closed

Enable assignment of VLAN during Prefix import #42

Gelob opened this issue Jun 27, 2016 · 2 comments
Milestone

Comments

@Gelob
Copy link
Contributor

Gelob commented Jun 27, 2016

The Prefix Import functionality does not currently accept the VLAN field

@jeremystretch
Copy link
Member

This was intentional. Since a site can have multiple VLANs with the same VID and name, there's no way to specify a unique VLAN in CSV. I suppose we could implement it anyway, and simply return an error if duplicate VLANs are found.

@topside844
Copy link

topside844 commented Jun 28, 2016

IMHO, you should not be allowing multiple VLANs that have the exact same identifying information (VLAN name, VLAN ID, site) without adding some other piece of identifying information to the table.

Maybe we utilize a 'Default' VLAN database that's used automatically within each site, with the ability to instantiate additional VLAN (or VXLAN) domains in a location if necessary? This would allow network admins to create "PODs" within each site that each contain their own unique set of L2 networks.

@jeremystretch jeremystretch changed the title Add VLAN Field to Prefix Import Enable assignment of VLAN during Prefix import Jul 7, 2016
@jeremystretch jeremystretch added this to the v1.3 milestone Jul 12, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants