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

Optionally Assigning a Site to a VM Cluster #1509

Closed
cimnine opened this issue Sep 19, 2017 · 4 comments
Closed

Optionally Assigning a Site to a VM Cluster #1509

cimnine opened this issue Sep 19, 2017 · 4 comments
Labels
type: feature Introduction of new functionality to the application

Comments

@cimnine
Copy link
Contributor

cimnine commented Sep 19, 2017

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 2.7
  • NetBox version: 2.2-beta1

Description

Each of our clusters is restricted to a certain site. Therefore I would like to optionally assign a site to a cluster.

@cimnine
Copy link
Contributor Author

cimnine commented Sep 19, 2017

If set, this could also be used to restrict which host devices can be selected for the cluster.

@cimnine cimnine changed the title VM Cluster optionally to Region Optionally Assigning a Site to a VM Cluster Sep 19, 2017
@darkstar
Copy link

Just to clarify: This is for clusters that don't consist of physical devices, right? Like AWS or Azure clusters?

Because if you assign a device to a cluster, that device has a physical location in a certain rack, and that rack is located in a site.

@cimnine
Copy link
Contributor Author

cimnine commented Sep 19, 2017

I had physical devices in mind. You could also build a cluster across sites. Ultimately I want to be able to filter the clusters by site and ideally also to restrict it to devices of that site.

@jeremystretch jeremystretch added beta type: feature Introduction of new functionality to the application labels Sep 20, 2017
@jeremystretch
Copy link
Member

Implemented in 2ca161f

lampwins pushed a commit to lampwins/netbox that referenced this issue Oct 13, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

3 participants