-
Notifications
You must be signed in to change notification settings - Fork 27
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
Create Framework Step that executes Snapshot/Restore upgrade #7
Labels
Comments
14 tasks
Goal is to have a PR for this out by 2022-12-16. Think it's doable as long as the PR from the previous step (#40) isn't too contentions. |
4 tasks
Slightly ahead of schedule; got it working and ready for PR today.
|
4 tasks
PR posted: #47 |
Demo'd the UTF to @sumobrian @kartg @okhasawn @lewijacn. Overall, folks thought it looked good with a few comments:
|
PR merged; task complete. Resolving. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Blocked By
Task
Create a validation framework step that executes a snapshot/restore upgrade [1] on the cluster created in a preceding step. You may assume the starting and ending nodes have the same number of nodes. The ending cluster version must be user-configurable via a supplied Dockerfile.
Why snapshot restore? It's widely used, it enables us to have both the starting and ending clusters spun up in parallel at the end for testing, and enable us to develop our final validation testing script such that it can be pointed at any two starting/ending clusters (including "real" customer clusters).
[1] Snapshot/Restore steps - https://github.com/sumobrian/migration-tools/pull/4
Acceptance Criteria
The text was updated successfully, but these errors were encountered: