CMLDEV-1127: Introduce STARTING node state for nodes pending full activation#226
Merged
tmikuska merged 1 commit intoMay 12, 2026
Conversation
tmikuska
deleted the
CMLDEV-1127-introduce-starting-node-state-for-nodes-pending-full-activation
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CMLDEV-1127: Introduce STARTING node state for nodes pending full activation
Summary
• Adds
STARTINGto the set of states considered “active” inNode.is_active(), so nodes waiting for full activation match server semantics and callers that filter on is_active().• Single-commit change on top of the shared ancestor with
dev; no API or dependency churn.Changes
• Models:
virl2_client/models/node.py(virl2_client/models/node.py) —active_statesnow{"STARTING", "STARTED", "QUEUED", "BOOTED"}foris_active().