--number-of-bakers

[nicolasochem]

This is an incremental feature on top of what we already have and is worth doing now.

Currently bootstrap-nodes is a k8s deployment while nodes are a k8s statefulset.

• turn bootstrap-nodes into a statefulset
• make the number of bakers configurable on mkchain i.e. --number-of-bakers just like --number-of-nodes
• --generate-constants should generate the appropriate number of baking accounts
• ensure every baking process in the pods are configured to bake for the account according to the statefulset pod number
• every block should be baked at priority 0. scale down is supported, in which case some blocks will be baked at priority 1 or more.
• scale up is not supported - you must decide at chain creation how many baking accounts you want, after that, changing the baker cycles require on-chain operations and waiting several cycles

[harryttd]

Related to #17

[nicolasochem]

running mkchain --number-of-nodes 3 --number-of-bakers 2 should generate the following accounts and nodes in the values yaml file:

accounts:
- baker: true
  bootstrap: true
  key: !!binary |
    snip
  name: baker_2
  private: true
- baker: true
  bootstrap: true
  key: !!binary |
    snip
  name: baker_2
  private: true
nodes:
- bake_for: baker_1
- bake_for: baker_2
- {}

And passing the yaml above to helm should spin up 2 bakers and one regular node.

[brandisimus]

@nicolasochem has this been done already? can we close it? thanks!

[nicolasochem]

yes

…

On Tue, Jan 26, 2021 at 8:38 AM brandisimus ***@***.***> wrote: @nicolasochem <https://github.com/nicolasochem> has this been done already? can we close it? thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAWXCY7VUSRW22SO4566KTS33VYDANCNFSM4TC4DELA> .

[brandisimus]

as per above - closing.