Mirroristas/bigchaindb
2
0
Fork 0
mirror of https://github.com/bigchaindb/bigchaindb.git synced 2024-10-13 13:34:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Changed example AWS deployment config file to use an Ubuntu 16.04 AMI & updated docs

Browse Source
This commit is contained in:
troymc 2016-11-13 14:59:40 +01:00
parent 32a247552c
commit 38e28d80e5
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
deploy-cluster-aws/example_deploy_conf.py
View File

@ -43,9 +43,9 @@ USE_KEYPAIRS_FILE=False
# Canonical (the company behind Ubuntu) generates many AMIs # Canonical (the company behind Ubuntu) generates many AMIs
# and you can search for one that meets your needs at: # and you can search for one that meets your needs at:
# https://cloud-images.ubuntu.com/locator/ec2/ # https://cloud-images.ubuntu.com/locator/ec2/
# Example: # Example: ami-8504fdea is what you get if you search for:
# (eu-central-1 Ubuntu 14.04 LTS amd64 hvm:ebs-ssd 20161020) # eu-central-1 16.04 LTS amd64 hvm:ebs-ssd
IMAGE_ID="ami-9c09f0f3" IMAGE_ID="ami-8504fdea"
# INSTANCE_TYPE is the type of AWS instance to launch # INSTANCE_TYPE is the type of AWS instance to launch
# i.e. How many CPUs do you want? How much storage? etc. # i.e. How many CPUs do you want? How much storage? etc.

4
docs/server/source/clusters-feds/aws-testing-cluster.md
View File

@ -126,7 +126,7 @@ BRANCH="master"
WHAT_TO_DEPLOY="servers" WHAT_TO_DEPLOY="servers"
SSH_KEY_NAME="not-set-yet" SSH_KEY_NAME="not-set-yet"
USE_KEYPAIRS_FILE=False USE_KEYPAIRS_FILE=False
IMAGE_ID="ami-9c09f0f3" IMAGE_ID="ami-8504fdea"
INSTANCE_TYPE="t2.medium" INSTANCE_TYPE="t2.medium"
SECURITY_GROUP="bigchaindb" SECURITY_GROUP="bigchaindb"
USING_EBS=True USING_EBS=True
@ -137,6 +137,8 @@ BIND_HTTP_TO_LOCALHOST=True
Make a copy of that file and call it whatever you like (e.g. `cp example_deploy_conf.py my_deploy_conf.py`). You can leave most of the settings at their default values, but you must change the value of `SSH_KEY_NAME` to the name of your private SSH key. You can do that with a text editor. Set `SSH_KEY_NAME` to the name you used for `<key-name>` when you generated an RSA key pair for SSH (in basic AWS setup). Make a copy of that file and call it whatever you like (e.g. `cp example_deploy_conf.py my_deploy_conf.py`). You can leave most of the settings at their default values, but you must change the value of `SSH_KEY_NAME` to the name of your private SSH key. You can do that with a text editor. Set `SSH_KEY_NAME` to the name you used for `<key-name>` when you generated an RSA key pair for SSH (in basic AWS setup).
You'll also want to change the `IMAGE_ID` to one that's up-to-date and available in your AWS region. If you don't remember your AWS region, then look in your `$HOME/.aws/config` file. You can find an up-to-date Ubuntu image ID for your region at [https://cloud-images.ubuntu.com/locator/ec2/](https://cloud-images.ubuntu.com/locator/ec2/). An example search string is "eu-central-1 16.04 LTS amd64 hvm:ebs-ssd". You should replace "eu-central-1" with your region name.
If you want your nodes to have a predictable set of pre-generated keypairs, then you should 1) set `USE_KEYPAIRS_FILE=True` in the AWS deployment configuration file, and 2) provide a `keypairs.py` file containing enough keypairs for all of your nodes. You can generate a `keypairs.py` file using the `write_keypairs_file.py` script. For example: If you want your nodes to have a predictable set of pre-generated keypairs, then you should 1) set `USE_KEYPAIRS_FILE=True` in the AWS deployment configuration file, and 2) provide a `keypairs.py` file containing enough keypairs for all of your nodes. You can generate a `keypairs.py` file using the `write_keypairs_file.py` script. For example:
```text ```text
# in a Python 3 virtual environment where bigchaindb is installed # in a Python 3 virtual environment where bigchaindb is installed