Eos: Please advise how can I create Multi-Host Private Blockchain Network.
Because I would like to deploy Private Blockchain like Diagram below. But Document have only method for setup Multi-Node on Single Host
https://developers.eos.io/eosio-nodeos/docs/local-multi-node-testnet
Moreover I tried to understand this Document but I'm not sure that's the right solution for build node on multiple servers or not. When I look at method for create genesis.json files. It seem not clear about EOS_PUB_DEV_KEY that Should I use Public Key from another server or not? (Example : use Public Key of Server 2 in genesis.json file on Server 1).
https://developers.eos.io/eosio-nodeos/docs/bios-boot-sequence
Please advise solution or guideline for me, Thank you very much.
chanwitkepha
All 3 comments
This is not an issue related to code you should have to ask this type of questions over聽https://eosio.stackexchange.com聽 and close this issue.
yashbhavsar007
on 26 Dec 2018
The documentation at https://developers.eos.io/eosio-nodeos/docs/bios-boot-sequence is more explicit about how to construct a network of multiple producer nodes. To generalize the instructions to multiple VMs, simply substitute appropriate IPs and ports for the p2p-peer-address parameters of each remote node as required for your network. The genesis.json file must be identical on all nodes that will be synchronized.
For an automated deployment tool, use eosio-launcher. From your build directory, run programs/eosio-launcher/eosio-launcher --help for documentation. Use --launch none to generate config files without starting a network. Experiment with various values of --nodes and --pnodes and --shape to see how config files change depending on the numbers of producing and non-producing nodes and the generated topology.
If you still have questions and wish to discuss further, please post in https://eosio.stackexchange.com. To keep things organized, Github issues are intended for bug reporting and feature tracking, and Stack Exchange is the right place for any technical support discussions. Thanks!
jgiszczak
on 26 Dec 2018
Dear jgiszczak. Thank you very much for your advise about eosio-launcher and community in stackexchange.
chanwitkepha
on 26 Dec 2018
Related issues
jiazechen
路
3Comments
Dexaran
路
3Comments
xiaomaogy
路
3Comments
hoopslb
路
3Comments
Npizza
路
3Comments
Most helpful comment
The documentation at https://developers.eos.io/eosio-nodeos/docs/bios-boot-sequence is more explicit about how to construct a network of multiple producer nodes. To generalize the instructions to multiple VMs, simply substitute appropriate IPs and ports for the
p2p-peer-addressparameters of each remote node as required for your network. The genesis.json file must be identical on all nodes that will be synchronized.For an automated deployment tool, use
eosio-launcher. From yourbuilddirectory, runprograms/eosio-launcher/eosio-launcher --helpfor documentation. Use--launch noneto generate config files without starting a network. Experiment with various values of--nodesand--pnodesand--shapeto see how config files change depending on the numbers of producing and non-producing nodes and the generated topology.If you still have questions and wish to discuss further, please post in https://eosio.stackexchange.com. To keep things organized, Github issues are intended for bug reporting and feature tracking, and Stack Exchange is the right place for any technical support discussions. Thanks!