firecares-ansible

The Devops Repo for FireCARES

Ansible Playbook that installs and configures these applications that are commonly used in production Django deployments:

Nginx
Gunicorn
PostgreSQL
Supervisor
Virtualenv
Memcached
Celery
RabbitMQ

Default settings are stored in roles/role_name/vars/main.yml. Environment-specific settings are in the env_vars directory.

Tested with OS: Ubuntu 14.04 LTS x64

Getting Started

A quick way to get started is with Vagrant and VirtualBox.

Requirements

Ansible (Tested using Ansible 2.8.6)
Vagrant (Tested using Vagrant 2.1.2)
VirtualBox *(Tested using VirtualBox 5.2.20 on MacOS Mojave)

NOTE: in order to retrieve the latest set of FireCARES database fixtures, be sure to add AWS information into the aws_access_key_id and aws_secret_access_key settings within env_vars/base.yml before provisioning your VM. The secret_vault.yml contains the key/secret to use to pull down fixtures.

git clone https://github.com/FireCARES/firecares-ansible.git
git clone https://github.com/FireCARES/firecares.git
cd firecares-ansible
vagrant up

Wait a few minutes for the magic to happen. Access the app by going to this URL: http://192.168.33.15

Additional vagrant commands

SSH to the box

vagrant ssh

Re-provision the box to apply the changes you made to the Ansible configuration

vagrant provision

Reboot the box

vagrant reload

Shutdown the box

vagrant halt

Running the Ansible Playbook to provision servers

First, create an inventory file for the environment, for example:

# development

[all:vars]
env=dev

[webservers]
webserver1.example.com
webserver2.example.com

[dbservers]
dbserver1.example.com

Next, create a playbook for the server type. See webservers.yml for an example.

Run the playbook:

ansible-playbook -i development webservers.yml

You can also provision an entire site by combining multiple playbooks. For example, I created a playbook called site.yml that includes both the webservers.yml and dbservers.yml playbook.

A few notes here:

The dbservers.yml playbook will only provision servers in the [dbservers] section of the inventory file.
The webservers.yml playbook will only provision servers in the [webservers] section of the inventory file.
An inventory var called env is also set which applies to all hosts in the inventory. This is used in the playbook to determine which env_var file to use.

You can then provision the entire site with this command:

ansible-playbook -i development site.yml

If you're testing with vagrant, you can use this command:

ansible-playbook -i vagrant_server vagrant.yml

Activating the virtual environment from vagrant

vagrant ssh
sudo su firecares
workon firecares

Deployment

There are quite a few steps necessary to setup a new full FireCARES environment in AWS; however, in order to display to production (https://firecares.org) or test (https://test.firecares.org), all that is needed to be done is execute one of the following scripts:

./deploy-test.sh
./deploy-prod.sh

Additionally, there are some helper scripts to make common operations a little simpler:

./cur_prod.sh -- dumps the IP address of the current production machines (active and previous deployment/rollback)
./maint_mode.sh -- apply/unapply maintenance mode to production (eg. MODE=on ./main_mode.sh turns on maintenance mode and MODE=off ./main_mode.sh)

Debugging in Pycharm

You can use Pycharm to put breakpoints and perform typical IDE debugging tasks. See this documentation for instructions

Infrastructure Tests

To run infrastructure sanity checks, ensure that StrictHostKeyChecking is off for AWS in your ~/.ssh/config:

Host *.compute.amazonaws.com
    StrictHostKeyChecking no

Then, run: ./test.sh to perform sanity checks on the currently deployed development environment; likewise, run: ENV=prod ./test.sh to test the active production environment.

FireCARES/firecares-ansible