bigchaindb/bigchaindb
1
0
Fork 0
mirror of https://github.com/bigchaindb/bigchaindb.git synced 2024-06-30 13:42:00 +02:00
Code Releases Activity
a0bb61d1c7
bigchaindb/deploy-cluster-aws
History
troymc a0bb61d1c7 Rename bigchain-deployment dir to deploy-cluster-aws
2016-03-23 14:27:31 +01:00
..
bigchain Rename bigchain-deployment dir to deploy-cluster-aws 2016-03-23 14:27:31 +01:00
create_hostlist.py Rename bigchain-deployment dir to deploy-cluster-aws 2016-03-23 14:27:31 +01:00
fab_prepare_chain.py Rename bigchain-deployment dir to deploy-cluster-aws 2016-03-23 14:27:31 +01:00
fabfile.py Rename bigchain-deployment dir to deploy-cluster-aws 2016-03-23 14:27:31 +01:00
get_elastic_ips.py Rename bigchain-deployment dir to deploy-cluster-aws 2016-03-23 14:27:31 +01:00
get_instance_status.py Rename bigchain-deployment dir to deploy-cluster-aws 2016-03-23 14:27:31 +01:00
hostlist.py Rename bigchain-deployment dir to deploy-cluster-aws 2016-03-23 14:27:31 +01:00
Readme.md Rename bigchain-deployment dir to deploy-cluster-aws 2016-03-23 14:27:31 +01:00
run_and_tag.py Rename bigchain-deployment dir to deploy-cluster-aws 2016-03-23 14:27:31 +01:00
startup.sh Rename bigchain-deployment dir to deploy-cluster-aws 2016-03-23 14:27:31 +01:00

Readme.md

Create and configure the storage backend in Amazon's Cloud

Getting started

  • Checkout bigchaindb and copy bigchain-deployment to bigchaindb repository

Prerequesites

  • Valid AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY is needed, both are exported as variables to the shell
  • awscli,
  • boto
  • fabric w/ fabtools

Cluster Installation

  • Got to the DEPLOY-directory and run './startup.sh' with two parameters (tag and number of nodes)...that's it! e.g.: ./startup.sh bro 7 to install a cluster tagged as bro with seven nodes.

If an error occurs...

There are some issues during the rollout on Amazon (presumably also in other cloud/virtual environments): if you tested with a high sequence it might be possible, that you run into:

  • NetworkError: Host key for ec2-xx-xx-xx-xx.eu-central-1.compute.amazonaws.com did not match pre-existing key! Server's key was changed recently, or possible man-in-the-middle attack. If so, just clean up your known_hosts file and start again.