This example is an extension of the simple LAMP deployment. Here we'll deploy a web server with an HAProxy load balancer in front. This set of playbooks also have the capability to dynamically add and remove web server nodes from the deployment. It also includes examples to do a rolling update of a stack without affecting the service.
(This example requires Ansible 1.2)
###Setup Entire Site.
This example is an extension of the simple LAMP deployment. Here we'll install
First we configure the entire stack by listing our hosts in the 'hosts' inventory file, grouped by their purpose:
and configure a web server with an HAProxy load balancer in front, and deploy
an application to the web servers. This set of playbooks also have the
capability to dynamically add and remove web server nodes from the deployment.
It also includes examples to do a rolling update of a stack without affecting
the service.
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:
[webservers]
[webservers]
web3
web3
@ -22,23 +33,34 @@ After which we execute the following command to deploy the site:
ansible-playbook -i hosts site.yml
ansible-playbook -i hosts site.yml
The deployment can be verified by accessing the IP address of your load balnacer host in a web browser: http://<ip-of-lb>:8888. Reloading the page should have you hit different webservers.
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
should have you hit different webservers.
###Removing and Adding a Node
###Removing and Adding a Node
Removal and addition of nodes to the cluster is as simple as editing the hosts inventory
Removal and addition of nodes to the cluster is as simple as editing the
and re-running:
hosts inventory and re-running:
ansible-playbook -i hosts site.yml
ansible-playbook -i hosts site.yml
###Rolling Update
###Rolling Update
Rolling updates are the preferred way to update the web server software or deployed application, since the load balancer can be dynamically configured to take the hosts to be updated out of the pool. This will keep the service running on other servers so that the users are not interrupted.
Rolling updates are the preferred way to update the web server software or
deployed application, since the load balancer can be dynamically configured
to take the hosts to be updated out of the pool. This will keep the service
running on other servers so that the users are not interrupted.
In this example the hosts are updated in serial fashion, which means
In this example the hosts are updated in serial fashion, which means that
that only one server will be updated at one time. If you have a lot of web server hosts, this behaviour can be changed by setting the 'serial' keyword in webservers.yml file.
only one server will be updated at one time. If you have a lot of web server
hosts, this behaviour can be changed by setting the 'serial' keyword in
webservers.yml file.
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:
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 hosts 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.
# This Playbook implements a rolling update on the infrastructure, change the value of the serial keyword to specify the number of servers the update should happen.
- name:Remove the code from server
command:rm -rf /var/www/html/*
- name:disable nagios alerts for this host's webserver service