Authority node #70
Merged
Authority node #70
Conversation
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
DeepCode Report (#612be4)DeepCode analyzed this pull request. |
nikzaugg
force-pushed
the
authority-node
branch
2 times, most recently
from
124922c to
94779d6
Compare
- frontend-container cann call backend container an trigger it to run a shell script
… container, all running on separate ports
- cannot find other nodes
…e everything else works
…me network - makes them discoverable
- also cleanup
- don't commit /wallet/sealer*
- should be fetched from the auth backend
- dete dockrrode stuff - remove dummy script
- /chainspec will fetch the chainspec and write it to a file - /peer will trigger an RPC call to the running chain to register node - updated /register, will read wallet address from keyStore file and send it to auth backend
…nnot access other services (auth backend)
- also subscribe to nr of sealers - allow step change when enough sealers
…l sealers (incl. parity-node)
- backend also needs .env file
nikzaugg
force-pushed
the
authority-node
branch
from
6a804ff to
612be42
Compare
|
The following steps will be developed in a separate branch:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Okay boys, my little Docker experiment has arrived:
What's new:
projectspoa-blockchain: has all pre-created keyStore files for the parity blockchain and scripts to start multiple nodessealer: represent the actual sealer node with afrontend,backendandparity-nodeDockerfileas you can onlydocker run parity/parityas normal user, and I had to copy over key files... Docker: run parity as normal user openethereum/parity-ethereum#9689sealer/parity-node/docker-compose.ymlfile. A single node is started withrun.sh <sealerNr:int>. This script will copy thechainspec.jsonand the needed keys inside the local folders. Then it will generate a temporary.envfile with variables for thedocker-compose.yml.poa-blockchain/scripts/dev-chain.shsealer/parity-node/docker-compose.ymlare put on the same network (that took forever for me to realize xD i previously had all nodes running but apparently on different networks, such that they could never peer, even tough the RPC call was successful each time)poa-blockchain/scripts/start-sealer.sh $1runs thedocker-compose.ymlinsidesealer. This spins up a frontend and backend. It's configured such that all requests from the frontend go to the correct backend. This can be done multiple times for different sealers.TODO: