Draft
Conversation
Adds an end-to-end test that validates VM migration between CRNs: create an instance, verify SSH on the initial CRN, unlink that CRN, wait for the scheduler to reallocate to a different CRN, and verify SSH on the new node. The test is written ahead of the scheduler-rs migration implementation to define the expected contract. Changes: - tests/test_migration.py: new migration test with helpers - tests/conftest.py: add crn_nodes fixture for multi-CRN tests - docs/superpowers/specs/: design spec - docs/superpowers/plans/: implementation plan
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
1 participant
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.
Summary
test_instance_migration— an end-to-end test that creates a VM, verifies SSH on the initial CRN, unlinks that CRN, and asserts the scheduler migrates the instance to a different CRN with SSH restoredcrn_nodessession fixture toconftest.pyfor multi-CRN test support (gracefully skips when < 2 CRNs)CRN_COUNT=2during CRN provisioningThe test defines the contract for scheduler-rs migration support, which is being developed in parallel.
Test plan
CRN_COUNT=2and scheduler-rs migration support enabledCRN_COUNT=1pytest --collect-only)