-
Notifications
You must be signed in to change notification settings - Fork 26
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
User activated upgrade support (#191)
* User activated upgrade support It is possible to force the tezos node to switch protocol at a given level. This is part of the network config section. Example: ``` "network": { "chain_name": "nico", "genesis": { "block": "BMFonSBNMfDf6MFRAw25xsCKhxx6f1gUsPr6KWnNZaviKu6Ak5D", "protocol": "PtYuensgYBb3G3x1hLLbCmcav8ue8Kyd2khADcL5LsT5R1hcXex", "timestamp": "2021-05-02T01:25:17.944261+00:00" }, "user_activated_upgrades": [ { "level": 5, "replacement_protocol": "ProtoALphaALphaALphaALphaALphaALphaALphaALphaDdp3zK" } ], "sandboxed_chain_name": "SANDBOXED_TEZOS", "default_bootstrap_peers": [], "genesis_parameters": { "values": { "genesis_pubkey": "edpkvFcxq7NYu2PCYD9pjABSZMK3ypVPnYwCPpRZCpwpsRuYvHA8ZU" } } } } ``` To make it work in tezos-k8s, the following was done: 1. support for running baker and endorser binaries for several protocols at once. This is done by converting the `protocol` value into `protocols`. This is great, since it also enables support of seamless transition between protocol during real mainnet upgrades. 2. replace the ad-hoc build of the network config with a pass-through of every key/value pair passed in values.yaml `node_config_network` value into the node's network config. This enables support of any network feature that we don't know of yet, in addition to the user-activated upgrade which is of interest here. Maybe also `sandboxed_chain_name` should be brought into this passthrough instead of being hardcoded? * add a note about memory usage when using several protocols * pluralize when appropriate
- Loading branch information
1 parent
1f8c498
commit 3da7722
Showing
6 changed files
with
45 additions
and
29 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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