starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add Status to Cluster #6011

New Issue
Closed
opened 2025-12-29 19:35:41 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:35:41 +01:00
Owner
Copy Link

Originally created by @hagbarddenstore on GitHub (Jan 27, 2022).

Originally assigned to: @jeremystretch on GitHub.

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

Originally created by @hagbarddenstore on GitHub (Jan 27, 2022). Originally assigned to: @jeremystretch on GitHub. ### 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
adam added the status: acceptedtype: feature labels 2025-12-29 19:35:41 +01:00
adam closed this issue 2025-12-29 19:35:41 +01:00
adam commented 2025-12-29 19:35:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 28, 2022):

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 commented on GitHub (Jan 28, 2022): 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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6011
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?