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

Allow duplicate cluster names within a site #1943

Closed
mabazyar opened this issue Mar 2, 2018 · 6 comments
Closed

Allow duplicate cluster names within a site #1943

mabazyar opened this issue Mar 2, 2018 · 6 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
Milestone

Comments

@mabazyar
Copy link

mabazyar commented Mar 2, 2018

Issue type

[] Feature request
[X] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: v2.3.0

Description

There is no possibility to represent an infrastructure having two different virtual clusters with the same name in two different virtual cluster groups located in different Sites. Whereas, this possibility is in place in racks.

The following shows how to reproduce the issue:

  1. Hit "Cluster-Groups" under virtualization menu
  2. Add two different cluster groups like cg1 and cg2
  3. Hit "Clusters" under virtualization menu
  4. add a cluster and name it like "staging" and put it under cg1
  5. add one more cluster with the same name and put it under cg2

At step 5, you will encounter error "Cluster with this Name already exists".

@mabazyar
Copy link
Author

mabazyar commented Mar 7, 2018

Just wanted to follow up to make sure if it is doable.
Cheers,

@mabazyar
Copy link
Author

mabazyar commented Mar 9, 2018

@jeremystretch

I think it may have to do with
#238
and
#1963

@jeremystretch
Copy link
Member

This pretty much parallels #238, which would allow duplicate rack names within a site.

@jeremystretch jeremystretch changed the title Possibility to have Identical virtual cluster name in different virtual cluster groups. Allow duplicate cluster names within a site Mar 14, 2018
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Mar 14, 2018
@jeremystretch jeremystretch added status: needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: accepted This issue has been accepted for implementation labels Jul 24, 2020
@Simperdy
Copy link

Simperdy commented Feb 5, 2021

I have the same problem. This would be very useful for me.

@SquirrelSloth
Copy link

Same as Simperdy and bb-Ricardo, we have 9 vCenter instances running in 3 environments and several of them have the same cluster names, but even though they are from different cluster groups we cannot create the duplicate clusters, leaving us to either group them all together or append the environment to the cluster name (which is not optimal because it doesn't reflect the actual cluster name in vCenter).
Being able to keep the naming constraint just within a cluster group is fine (like how setting IP address unique enforcement within a specific VRF is done right now).

@WilliamDEdwards
Copy link

+1. This would allow for administering multisite virtualisation clusters.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs milestone Awaiting prioritization for inclusion with a future NetBox release labels Oct 19, 2021
@jeremystretch jeremystretch added this to the v3.1 milestone Oct 19, 2021
@jeremystretch jeremystretch added this to Data Model in Roadmap Oct 19, 2021
@jeremystretch jeremystretch self-assigned this Oct 19, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
No open projects
Roadmap
Data Model
Development

No branches or pull requests

5 participants