-
Notifications
You must be signed in to change notification settings - Fork 44
SOT NOP upgrade sequence, allow explicit upgrade sequence with tags #2431
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,17 +1,58 @@ | ||
| # Compatibility Testing | ||
|
|
||
| We have a simple tool to check compatibility for CL nodes. The example command will filter and sort the available tags, rollback and install the oldest version, and then begin performing automatic upgrades to verify that each subsequent version remains compatible with the previous one. | ||
| ## Prerequisites | ||
|
|
||
| Authorize in our SDLC ECR registry first. Get the creds and run | ||
| ```bash | ||
| aws ecr get-login-password --region us-west-2 | docker login --username AWS --password-stdin <sdlc_ecr_registry> | ||
| ``` | ||
|
|
||
| ## Testing Upgrade Sequence | ||
|
|
||
| We have a simple tool to check compatibility for CL node clusters. The example command will filter and sort the available tags, rollback and install the oldest version, and then begin performing automatic upgrades to verify that each subsequent version remains compatible with the previous one. | ||
|
|
||
| `buildcmd`, `envcmd`, `testcmd` can be arbitrary bash commands. | ||
|
|
||
| ```bash | ||
| ctf compat backward \ | ||
| --registry <sdlc_ecr_registry> \ | ||
| --buildcmd "just cli" \ | ||
| --envcmd "cl r" \ | ||
| --testcmd "cl test ocr2 TestSmoke/rounds" \ | ||
| --refs 2.32.0 \ | ||
| --refs 2.33.0 \ | ||
| --refs 2.34.0 \ | ||
| --refs 2.35.0 \ | ||
| --nodes 3 | ||
| ``` | ||
|
|
||
| Keep in mind that `refs` should be present in regsitry you are testing against, the first (oldest) `ref` should also have a valid end-to-end test that works. | ||
|
|
||
| In CI we detect SemVer tags automatically, whenever a new tag appears we select last 3, rollback to the oldest and perform upgrade process. | ||
|
|
||
| ```bash | ||
| ctf compat backward \ | ||
| --registry <sdlc_ecr_registry> \ | ||
| --buildcmd "just cli" \ | ||
| --envcmd "cl r" \ | ||
| --testcmd "cl test ocr2 TestSmoke/rounds" \ | ||
| --include_tags +compat \ | ||
| --nodes 3 \ | ||
| --versions_back 3 | ||
| --versions-back 3 | ||
| ``` | ||
|
|
||
| Since some of our products have a different release and tagging strategies you should add `+compat` tags to all released versions and use this tool in CI to check compatibility on `+compat` tag. | ||
| In case you have multiple DONs in your product and names of nodes are different please use `--node-name-template custom-cl-node-%d` option | ||
|
|
||
| Use `ctf compat restore` to rollback to current branch (default is `develop`) | ||
| ## Modelling Node Operators Cluster | ||
|
|
||
| It is possible to fetch versions node operators are currently running and model DON upgrade sequence locally. Logic is the same, get all the versions, rollback to the oldest one, setup product, verify, try to upgrade all the versions running the oldest test for each upgrade. | ||
|
|
||
| ```bash | ||
| ctf compat backward \ | ||
| --registry <sdlc_ecr_registry>\ | ||
| --buildcmd "just cli" \ | ||
| --envcmd "cl r" \ | ||
| --testcmd "cl test ocr2 TestSmoke/rounds" \ | ||
| --nop northwestnodes \ | ||
| --versions-back 3 \ | ||
| --nodes 3 | ||
| ``` |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| - NOPs from SOT upgrade sequence | ||
| - Allow specify upgrade sequence explicitly |
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, FYI for CRE we'd use
workflow-node%d