[SON ETH] Bring up the entire Ethereum qa test network environment #351

New issue

Closed

opened 2022-04-22 11:50:20 +00:00 by hirunda · 4 comments

hirunda commented

2022-04-22 11:50:20 +00:00

(Migrated from gitlab.com)

Test network node should:

mine new blocks
run HTTP server for handling RPC calls
be configurable trough JS console

This ticket should be used as well for posting and sharing all details which are found during bring up.

Test network node should: - mine new blocks - run HTTP server for handling RPC calls - be configurable trough JS console This ticket should be used as well for posting and sharing all details which are found during bring up.

hirunda commented

2022-04-22 11:50:20 +00:00

(Migrated from gitlab.com)

assigned to @hirunda

hirunda commented

2022-04-22 12:03:28 +00:00

(Migrated from gitlab.com)

mentioned in issue #342

hirunda commented

2022-04-25 19:30:30 +00:00

(Migrated from gitlab.com)

Build the image with:

docker-compose build ethereum-for-peerplays

Run with the:

docker-compose up ethereum-for-peerplays-miner

Note that with last command we are running miner service which depends on the boot node [ethereum-for-peerplays].
Depending will run first the boot node then miner node. In order to mine, miner should have at least one peer. Since we are working in test network the boot node peer will be automatically added to miner , so miner could start with producing blocks. The miner node and boot node are connected with the commands

--nodekeyhex="b0ac22adcad37213c7c565810a50f1772291e7b0ce53fb73e7ec2a3c75bc13b5"

We explicitly define here the key for the boot node in hex format.

--bootnodes="enode://af22c29c316ad069cf48a09a4ad5cf04a251b411e45098888d114c6dd7f489a13786620d5953738762afa13711d4ffb3b19aa5de772d8af72f851f7e9c5b164a@ethereum-for-peerplays:30303"

On the miner node we assign explicitly boot node as a peer, previously defined with nodekeyhex.

There are also other commands which introduce restriction in discovering and CDR, which is the purpose of test network.

Build the image with: `docker-compose build ethereum-for-peerplays` Run with the: `docker-compose up ethereum-for-peerplays-miner` Note that with last command we are running miner service which depends on the boot node [ethereum-for-peerplays]. Depending will run first the boot node then miner node. In order to mine, miner should have at least one peer. Since we are working in test network the boot node peer will be automatically added to miner , so miner could start with producing blocks. The miner node and boot node are connected with the commands `--nodekeyhex="b0ac22adcad37213c7c565810a50f1772291e7b0ce53fb73e7ec2a3c75bc13b5"` We explicitly define here the key for the boot node in hex format. ` --bootnodes="enode://af22c29c316ad069cf48a09a4ad5cf04a251b411e45098888d114c6dd7f489a13786620d5953738762afa13711d4ffb3b19aa5de772d8af72f851f7e9c5b164a@ethereum-for-peerplays:30303"` On the miner node we assign explicitly boot node as a peer, previously defined with nodekeyhex. There are also other commands which introduce restriction in discovering and CDR, which is the purpose of test network.

serkixenos commented

2022-04-27 13:04:49 +00:00

(Migrated from gitlab.com)

changed title from Bring up the entire Ethereum qa test network environment to {+[SON ETH] +}Bring up the entire Ethereum qa test network environment

changed title from **Bring up the entire Ethereum qa test network environment** to **{+[SON ETH] +}Bring up the entire Ethereum qa test network environment**

serkixenos (Migrated from gitlab.com) closed this issue

2022-04-28 12:31:12 +00:00