DevOps
Geoff Bowers
Daemon Internet Consultants
December 2014
version control
Easy Branching
- Distributed Version Control System
- GIT or Mercurial
- Devs comfortable with branching
- Repo visible to infrastructure
developer environments
vagrantup.com
Not Quite Ops
- Model solutions locally
- Windows, OSX, Linux
- Learn how servers are put together
Provisioning Services
- Chef Recipies (Ruby)
- Shell scripts
- Ansible Playbooks (Python)
Not to forget... Puppet, Salt, etc
PaaS
Platform as a Service
- Java WAR files; Cloudbees
- Focus on isolating services
- brilliant for simple apps
Ultimately, ourrequirements were too complex.
scriptable servers
Moving Into Ops
- running scripts to build servers
- linux based
- monolithic installs; but still great
- leap to make more complex set ups
Convergence of several strategies to make the next step...
separate
app & infrastructure
12factor.net
Adam Wiggins, Heroku Co-Founder
Isolating Apps
disposable servers
config via environment
microservices route
Treat commodity SaaS solutions as 1st class citizens
AWS OpsWorks
OpsWorks
- Framework for complex solutions
- Chef as a Service
- Plenty of work to do...
Collossus - the app we built to orchestrate the app.
containers
containerisation
Docker, Docker, Docker!
https://www.docker.com/
with Rocket as a 50:1 long shot
https://coreos.com/blog/rocket/
Why containers?
- takes 20-30 mins to bring up an EC2 instance
- containers can be "versioned"
- testing & code progression options
Why not containers?
- Mesos; Marathon, Zookeeper
- 10 servers for a production environment
- 20 servers for multi AZ
- Landscape changes daily
Waiting for Amazon ECS...
tl;dr
Short Version
- version control
- development/test environments with vagrant
- choose a provisioner (eg. Ansible)
- isolate app from infrastructure
- AWS OpsWorks
- containers (everywhere.. soon)