https://github.com/tableflip/makelunch-infrastructure
:hocho: :floppy_disk: Ansible scripts for deploying makelunch
https://github.com/tableflip/makelunch-infrastructure
Last synced: 5 months ago
JSON representation
:hocho: :floppy_disk: Ansible scripts for deploying makelunch
- Host: GitHub
- URL: https://github.com/tableflip/makelunch-infrastructure
- Owner: tableflip
- Created: 2015-08-25T07:09:50.000Z (almost 11 years ago)
- Default Branch: master
- Last Pushed: 2016-11-22T15:10:08.000Z (over 9 years ago)
- Last Synced: 2025-06-01T12:53:48.620Z (about 1 year ago)
- Language: Nginx
- Homepage:
- Size: 36.1 KB
- Stars: 2
- Watchers: 3
- Forks: 1
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Makelunch Infrastructure
**Ansible scripts for deploying and maintaining the servers**
```sh
├── Vagrantfile # Test the scripts locally with `vagrant up`
├── bootstrap.yml # Get a new vm ready for ansible
├── dev # Inventory for local dev
├── playbook.yml # The roles assigned to various hosts
├── production # Inventory for LIVE
└── roles # Define the tasks that set up a given role.
```
[Ansible](http://docs.ansible.com/ansible/index.html) works by assigning roles to hosts.
- A **host** is any server in our infrastructure.
- A **role** can be things like `frontend`, `db`, etc.
Roles contain the tasks and and files to install and configure the services needed.
**e.g**: `frontend` _clones our app code, installs npm deps, and configures nginx as a proxy._
Key to making it work is ensuring tasks are idempotent. We can run all the tasks at any time. Either the task changes the system as required, or has no effect if that change is already in place.
An **inventory** defines named groups of servers. We use **playbooks** to assign roles those groups. We have a playbook that bootstraps a brand new vm to be used by ansible, which we assume will be run once on against each machine.
```sh
ansible-playbook -i production bootstrap.yml --extra-vars "ansible_ssh_user=root"
```
where
- `-i production` limits the hosts affected to just those listed in `production/inventory`
- `bootstrap.yml` is the playbook to run.
- `--extra-vars "ansible_ssh_user=root"` tells ansible to connect as `root` for this run. It's only needed while we don't have an ansible user.
`bootstrap.yml` sets up the `ansible` user that'll be used for all subsequent management and not much else.
```yaml
- hosts: all
roles:
- bootstrap
```
By assigning `all` hosts the role `bootstrap`, it's telling ansible to run the tasks defined in `roles/boostrap/tasks/main.yml`
```yaml
- name: Ensure base OS is up-to-date
become: yes
apt: upgrade=dist update_cache=yes
- name: Ensure ansible user exists
become: yes
user: name=ansible comment="Ansible" groups="ansible,sudo"
...
```
Once we have an `ansible` user, we can forget about `bootstrap.yml`, and get on with setting up our roles, as defined in `playbook.yml`
At the start of a project, it's normal to have all the roles on the same host; a single vm dealing with the frontend, api and db, as it's then much easier to roll out additional VMs for staging and test.
When we need to scale the infrastructure we can add additional hosts to an inventory, to scale a roll horizontally across many identically configured servers, and we can split roles our to separate hosts, to create optimised VMs with a single purpose; e.g. a separate `db` server.
## Prerequisites
**You need to add a `secrets.yml` file into `group_vars/all`**
This file extracts out all of the secrets for the deployments that we'd prefer not to keep in the repo. Ask a tableflipper for a copy.
## Usage
**To bootstrap a local test server with vagrant**
- Install Ansible
- Install Vagrant (`brew install vagrant`)
- Add `10.100.108.100 dev.lunch.tableflip.io` to your local `/etc/hosts`
```sh
# Download and provision a vm
vagrant up
# bootstrap.yml is run automagically by vagrant.
# Install and configure all the things!
ansible-playbook -i dev playbook.yml
```
You now have a test vm, running locally
---
**To bootstrap a new production vm**
- Add the new remote to the relevant inventory
- Add your public ssh key in `/root/.ssh/authorized_keys` on the remote
```sh
# bootstrap ansible user
ansible-playbook -i production bootstrap.yml --extra-vars "ansible_ssh_user=root"
# Intall app and dependencies
ansible-playbook -i production playbook.yml
```
---
A (╯°□°）╯︵[TABLEFLIP](https://tableflip.io/) project.