You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, just a single client combination is provided for obol DVT configuration.
e.g., nethermind-lighthouse-charon-lodestar-...
It does not make any problem itself. However, if all cluster members use the same configuration, which makes single point of failure against the same client.
In this approach(like MA to MSA), we need to divide a single docker-compose file to several docker-compose files.
🎯 Problem to be solved
background
At the moment, just a single client combination is provided for obol DVT configuration.
e.g., nethermind-lighthouse-charon-lodestar-...
It does not make any problem itself. However, if all cluster members use the same configuration, which makes single point of failure against the same client.
In this approach(like MA to MSA), we need to divide a single docker-compose file to several docker-compose files.
It makes easy management, easy to use. These changes can be deployed for https://github.com/ObolNetwork/lido-charon-distributed-validator-node/
Obol can provides predefined multiple client configurations easily.
It allows operators
example
current :
single docker-compose.yml including nethermind-lighthouse-lodestar-charon-...
want:
docker-compose.yml
docker-compose-el-nethermind.yml, docker-compose-el-....yml
docker-compose-cl-lighthouse.yml, docker-compose-cl-....yml
docker-compose-vc-xxx.yml, docker-compose-vc-....yml
docker-compose-charon.yml
...
...
full example of concept : cosmostation@0f64add
expected work if these changes are acceptable
🧪 Tests
👐 Additional acceptance criteria
❌ Out of Scope
The text was updated successfully, but these errors were encountered: