Managing WordPress with Ansible

Managing WordPress
with Ansible
David Murphy, October 2015

View Slide

@schwuk
http://schwuk.com

View Slide


View Slide

opinionated

View Slide

more than
one way
to do it

View Slide

why bother
with any of this?

View Slide

doing it
yourself

View Slide

knowing how to
do it yourself

View Slide

automation

View Slide

if you are going to do
something more than
once, automate it

View Slide

Choices

View Slide

Choice #1:
Software

View Slide


View Slide

Choice #2:
Platform

View Slide


View Slide

they are
all good

View Slide

Choice #3:
Hosting

View Slide


View Slide

they are not
all good

View Slide

Choice #4:
Tool

View Slide


View Slide

again,
they are
all good

View Slide


View Slide

Ansible is a powerful
automation tool that you
can learn quickly.

View Slide

how does it work?

View Slide

inventory
playbooks
roles

View Slide

Inventory

View Slide

Sample inventory
[webservers]
www1.example.com
www2.example.com
[dbservers]
db0.example.com
db1.example.com

View Slide

Naming patterns
[webservers]
www[01:50].example.com
[databases]
db-[a:f].example.com

View Slide

Groups-of-groups
[web]
host1
host2
[database]
host2
host3
[site:children]
web
database

View Slide

Out-of-scope
Dynamic inventory
(e.g., Amazon EC2)

View Slide

Our inventory
[development]
my_vagrant_host ansible_sudo=yes
[production]
wcmcr.schwuk.com

View Slide

demo

View Slide


View Slide

Playbooks

View Slide

Sample playbook
---
- hosts: webservers
remote_user: root
tasks:
- name: ensure apache is at the latest version
yum: pkg=httpd state=latest
- name: write the apache config file
template: src=/srv/httpd.j2 dest=/etc/httpd.conf
- hosts: databases
remote_user: root
tasks:
- name: ensure postgresql is at the latest version
yum: name=postgresql state=latest
- name: ensure that postgresql is started
service: name=postgresql state=running

View Slide

Modules

View Slide

yum
Manages packages with the yum package manager1
- yum: pkg=httpd state=latest
1 http://docs.ansible.com/ansible/yum_module.html

View Slide

template
Create/modify ﬁles using variables2
- template: src=/srv/httpd.j2 dest=/etc/httpd.conf
2 http://docs.ansible.com/ansible/template_module.html

View Slide

service
Controls services on the remote host(s)3
- service: name=postgresql state=running
3 http://docs.ansible.com/ansible/service_module.html

View Slide

Modules, modules, modules
→ command, get_url
→ apt, apt_key, apt_repository
→ digital_ocean, linode, ec2, gce, docker
→ irc, slack, hipchat, mail
→ mysql_db, mysql_user
→ git, subversion

View Slide

But where are...
→ Apache/NGINX?
→ PHP?

View Slide

install → conﬁgure → control

View Slide

apt → template → service

View Slide

Deploying
WordPress

View Slide

Famous 5-Minute Install4
→ download/unzip
→ create database
→ edit conﬁg
→ upload
4 http://codex.wordpress.org/InstallingWordPress#Famous5-Minute_Install

View Slide

A better example
→ install packages
→ create database, then database user
→ download/unzip
→ edit conﬁg
→ conﬁgure webserver
→ ensure webserver is running

View Slide

First, some variables
vars:
db_name: wcmcr
db_user: wcmcr
db_password: correcthorsebatterystaple
site_name: wcmcr.schwuk.com
site_alias: wcmcr

View Slide

Install packages
- name: Install mysql-server
apt: name=mysql-server state=present↩
update_cache=yes cache_valid_time=3600
- name: Install apache2
apt: name=apache2 state=present
- name: Install libapache2-mod-php5
apt: name=libapache2-mod-php5 state=present
- name: Install php5-mysql
apt: name=php5-mysql state=present
- name: Install python-mysqldb
apt: name=python-mysqldb state=present
- name: Install python-httplib2
apt: name=python-httplib2 state=present

View Slide

Install packages take two
- name: Install required packages
apt:
name: "{{ item }}"
state: present
update_cache: yes
cache_valid_time: 3600
with_items:
- mysql-server
- apache2
- libapache2-mod-php5
- php5-mysql
- python-mysqldb
- python-httplib2

View Slide

Database setup
- name: Create WordPress database
mysql_db:
name: "{{ db_name }}"
state: present
- name: Create WordPress user
mysql_user:
name: "{{ db_user }}"
password: "{{ db_password }}"
priv: "{{ db_name }}.*:ALL"
state: present

View Slide

Install WordPress
- name: Create directory for WordPress
file:
path: /srv/{{ site_alias }}
state: directory
mode: 0755
- name: Get WordPress
get_url:
url: http://wordpress.org/latest.tar.gz
dest: /tmp/wordpress.tar.gz
- name: Extract WordPress
unarchive:
src: /tmp/wordpress.tar.gz
dest: /srv/{{ site_alias }}
copy: no

View Slide

Edit conﬁg
- name: Generate Keys and Salts
uri:
url: https://api.wordpress.org/secret-key/1.1/salt/
dest: /srv/{{ site_alias }}/keys.php
creates: /srv/{{ site_alias }}/keys.php
- name: Configure WordPress
template:
src: wp-config.php
dest: /srv/{{ site_alias }}/wordpress/wp-config.php
owner: root
group: root
mode: 0644

View Slide

wp-config.php template
define('DB_NAME', '{{ db_name }}');
define('DB_USER', '{{ db_user }}');
define('DB_PASSWORD', '{{ db_password }}');
define('DB_HOST', 'localhost');
define('DB_CHARSET', 'utf8');
define('DB_COLLATE', '');
include dirname( __FILE__ ) . '../keys.php';
$table_prefix = 'wp_';
define('WP_DEBUG', false);
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');
require_once(ABSPATH . 'wp-settings.php');

View Slide

Conﬁgure webserver
- name: Configure webserver
template:
src: apache-site.conf
dest: /etc/apache2/sites-available/{{ site_alias }}.conf
owner: root
group: root
mode: 0644
notify:
- restart apache
- name: Disable default site_alias
command: a2dissite 000-default
- name: Enable WordPress site
command: a2ensite {{ site_alias }}

View Slide

Handlers
handlers:
- name: restart apache
service: name=apache2 state=restarted

View Slide

demo

View Slide


View Slide

Next
steps

View Slide

Questions?

View Slide

Managing WordPress with Ansible

Managing WordPress with Ansible

David Murphy

More Decks by David Murphy

Other Decks in Technology

Featured

Transcript