bigchaindb/bigchaindb
1
0
Fork 0
mirror of https://github.com/bigchaindb/bigchaindb.git synced 2024-06-15 17:13:20 +02:00
Code Releases Activity
0a890801c5
bigchaindb/deploy-cluster-aws
History
troymc 0a890801c5 Rename bigchaindb.conf to rethinkdb.conf (@ AWS deployment)
2016-03-31 15:13:42 +02:00
..
conf Rename bigchaindb.conf to rethinkdb.conf (@ AWS deployment) 2016-03-31 15:13:42 +02:00
awscommon.py Moved shared AWS constants & functions to awscommon 2016-03-31 10:57:05 +02:00
create_rethinkdb_conf.py Rename bigchaindb.conf to rethinkdb.conf (@ AWS deployment) 2016-03-31 15:13:42 +02:00
fab_prepare_chain.py Put import unicode_literals back in Fabric pyfiles 2016-03-30 17:36:09 +02:00
fabfile.py Rename bigchaindb.conf to rethinkdb.conf (@ AWS deployment) 2016-03-31 15:13:42 +02:00
launch_ec2_nodes.py Refactor how bigchaindb.conf gets written 2016-03-31 14:38:11 +02:00
Readme.md Notes in Readme.md in prep for migration to boto3 2016-03-24 10:04:15 +01:00
startup.sh Rename bigchaindb.conf to rethinkdb.conf (@ AWS deployment) 2016-03-31 15:13:42 +02: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 - DO WE EVEN USE THIS?
  • boto - DEPENDENCY BEING REMOVED
  • boto3 (Python 2 or 3)
  • fabric w/ fabtools (Python 2 only)

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.