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

Add Status to Cluster #8471

Closed
hagbarddenstore opened this issue Jan 27, 2022 · 1 comment
Closed

Add Status to Cluster #8471

hagbarddenstore opened this issue Jan 27, 2022 · 1 comment
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@hagbarddenstore
Copy link
Contributor

NetBox version

v3.1.6

Feature type

New functionality

Proposed functionality

Just like VirtualMachine, Device and others have a Status field, it would be nice to also add this to Clusters.

I'm proposing the following values:

  • Active
  • Offline
  • Planned
  • Staged
  • Decommissioning

Use case

Right now there's no nice way to letting a user know which stage in the lifecycle a Cluster is in.

So, it needs to be manually communicated that a Cluster is not ready for production yet or to be taken out of production, thus making it unsuitable for adding new VirtualMachines to.

Database changes

Add field status to the virtualization.cluster model.

External dependencies

None

@hagbarddenstore hagbarddenstore added the type: feature Introduction of new functionality to the application label Jan 27, 2022
@jeremystretch
Copy link
Member

I was going to ask if this could potentially conflict with the statuses of assigned VMs (where an "active" VM could be assigned to an "offline" cluster), but of course the same scenario exists for devices and sites, and it hasn't been an issue AFAICT.

@jeremystretch jeremystretch added the needs milestone Awaiting prioritization for inclusion with a future NetBox release label Jan 28, 2022
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed needs milestone Awaiting prioritization for inclusion with a future NetBox release labels Apr 7, 2022
@jeremystretch jeremystretch added this to the v3.3 milestone Apr 7, 2022
@jeremystretch jeremystretch self-assigned this May 19, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 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
None yet
Development

No branches or pull requests

2 participants