Commit 664057b3 authored by Dave Johnson's avatar Dave Johnson Committed by GitHub
Browse files

Updated specifically for AWS

parent f73de609
......@@ -15,25 +15,24 @@ You can also optionally configure a Nagios monitoring node.
### Initial Site Setup
First we configure the entire stack by listing our hosts in the 'hosts'
inventory file, grouped by their purpose:
First, we provision the hosts neccessary for this demonstration using the included playbook, "demo-aws-launch.yml". This will provision the following instances, with the group structure specified below. The hosts are tagged via AWS EC2 tagging and the Ansible inventory sync script (or Tower) will create the appropriate groups from these tags.
After which we execute the following command to deploy the site:
ansible-playbook -i hosts site.yml
ansible-playbook -i site.yml
The deployment can be verified by accessing the IP address of your load
balancer host in a web browser: http://<ip-of-lb>:8888. Reloading the page
......@@ -45,10 +44,10 @@ The default username and password are "nagiosadmin" / "nagiosadmin".
### Removing and Adding a Node
Removal and addition of nodes to the cluster is as simple as editing the
hosts inventory and re-running:
Removal and addition of nodes to the cluster is as simple as creating new instances, syncing the
Ansible inventory and re-running:
ansible-playbook -i hosts site.yml
ansible-playbook -i site.yml
### Rolling Update
......@@ -66,7 +65,7 @@ Once the code has been updated in the source repository for your application
which can be defined in the group_vars/all file, execute the following
ansible-playbook -i hosts rolling_update.yml
ansible-playbook -i rolling_update.yml
You can optionally pass: -e webapp_version=xxx to the rolling_update
playbook to specify a specific version of the example webapp to deploy.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment