-
Notifications
You must be signed in to change notification settings - Fork 13
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
Controlled rollout of ZOS on mainnet #2413
Comments
Doesn't mean to be picky on the wording part.
But i think what you really mean is
Other than staging, we can also employ feature flag/toggle technique:
|
We have already qanet, testnet as staging environments for the release in pipeline, what is needed is controlled rollout on a small, defined, subset of nodes on mainnet. |
Oh okay, feature flag/toggle then |
Flag is already toggled/set as part of zos upgrade. When we want to upgrade nodes on mainnet network, we create a proposal - on tfchain - that has a zos version to upgrade the whole network to, and as soon as the node picks up that proposal approval it starts its upgrade. What is needed is breaking that into two steps:
|
OK, so it is clear that we want is controlled rollout. |
Farm IDs can be included in the A/B testing but we can't include node IDs. |
If the node isn't registered, it's not part of the allowed nodes list by design, no? |
I mean the registration/noded module in general even the node is registered. This step is known after the identityd module (which is the one responsible for the upgrade) |
Alright, let's remove the nodes list and stick to farm ids only |
Do you want to use the node address instead? or just farm IDs will be enough? |
I think farm IDs are enough, addresses are too cumbersome IMO |
WIP:
|
Testing in progress
|
The current situation is we have a config file which specify if the version is safe to upgrade or not https://github.com/threefoldtech/zos-config/blob/main/development-v4.json#L68 |
We need to implement a Controlled rollout for ZOS upgrades, specially on mainnet to facilitate controlled experiments on different nodes or farms. The primary goal is to allow for testing the next version of ZOS on selected nodes or farms without impacting the entire network. This will be crucial for evaluating new features or optimizations before rolling them out to the broader network.
safe_to_upgrade_network
defaulted tofalse
: This flag will be used to indicate whether it is safe to proceed with network-wide upgrades with the latest zos version specified on chain or notTODO...
The text was updated successfully, but these errors were encountered: