diff options
| author | Dave Johnson <dave@ansibleworks.com> | 2016-07-29 01:14:55 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-07-29 01:14:55 +0300 |
| commit | 664057b35a2d57e8e482b453fb7b72dccbbf36c4 (patch) | |
| tree | 6e0ea24913ccf43b0e9b8f7edc6d3daf67370d6e | |
| parent | f73de6091104cd331d5d325769bf2e1ca9663720 (diff) | |
Updated specifically for AWS
| -rw-r--r-- | lamp_haproxy/aws/README.md | 21 |
1 files changed, 10 insertions, 11 deletions
diff --git a/lamp_haproxy/aws/README.md b/lamp_haproxy/aws/README.md index e1258e0..68eb588 100644 --- a/lamp_haproxy/aws/README.md +++ b/lamp_haproxy/aws/README.md @@ -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. - [webservers] + [tag_ansible_group_webservers] webserver1 webserver2 - [dbservers] + [tag_ansible_group_dbservers] dbserver - [lbservers] + [tag_ansible_group_lbservers] lbserver - [monitoring] + [tag_ansible_group_monitoring] nagios After which we execute the following command to deploy the site: - ansible-playbook -i hosts site.yml + ansible-playbook -i ec2.py 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 ec2.py 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 command: - ansible-playbook -i hosts rolling_update.yml + ansible-playbook -i ec2.py 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. |