haochenpan / benchmarking_hyperledger Goto Github PK

run chmod 400 id to secure the SSH private key if you are using the code for the first time

if nodes' public ips have changed (after server restart), modify servers.sh

if nodes' private ips have changed (add/remove node in GCP), check files in client and server folders (clinet/hosts: all hl servers, each appear twice)

if hl root server private ip have changed, go to functions.sh and modify hl_root_private_ip

in test.sh (run == make function all == uncomment the command):

run copy_configs, and for sanity check, run remove_logs

adjust artificial latency

run start_servers, and start_clients followed by two parameters: # of threads per client driver, and # of Tx send per thread

after a while (1-5 minutes), SSH to the hl root instance, go to folder ~/blockbench/benchmark/hyperledger, run . stop-peers.sh (this step cannot be automated due to some strange SSH issue)

repeat the previous two steps if you want to test on different start_clients parameters

run download_logs and finally remove_logs so that logs are this folder

now say I want to SSH from 15 to 14:

at 15, generate pk, sk:

ssh-keygen -t rsa -f ./id -C systopicsgroup3

upload the pk (test.pub in this case) to 14, and do:

``

mkdir -p ~/.ssh && cat id.pub >> ~/.ssh/authorized_keys

finally, at 15:

ssh -i test [email protected]

or even better

ssh 10.150.0.29 ssh -i ~/mgmt/id -o StrictHostKeyChecking=no [email protected] ssh -i id -o StrictHostKeyChecking=no [email protected]