This document discusses using Rundeck to drive Docker containers for testing environments. It notes that using Docker allows for easily running multiple instances and versions of applications without needing dedicated hardware. Rundeck provides a graphical interface to send commands to Docker, capture output, and manage Docker images in a web-based and intuitive way. The document demonstrates creating separate Docker images - one for environment dependencies and configuration, and another for the application itself - and using Rundeck to deploy them, in order to rapidly deploy test environments with minimal overhead.

1. Driving Docker with
Rundeck
Ian Richardson

2. Why Docker?
The demand for test environments within our organization is
increasing
Running multiple instances or versions of an application
is not easily feasible in a shared environment
Rapid deployment of test environments minimizes IT
overhead
Scalability provides opportunity for team members to
leverage personal environments, improves QA process

3. Why Rundeck?
Needed a quick and easy way to drive Docker from a
graphical interface
Send commands to Docker
Capture output
Web-based, intuitive

4. Docker Images
Images are built from Dockerfiles, native configuration
management
For complex configurations bootstrap Chef, Puppet, etc.
via the Dockerfile
To keep deployment rapid, create an environment image
that is referenced in the application Dockerfile

5. Environment image
Operating system
Application dependencies
Environment configuration
Application image
Application installation & configuration

6. Demo

7. Wrapping Up
Vagrant Box: https://github.com/ianrichardson/
cloudaustin-rundeck-docker.git
Contact:
@Iano #austindevops freenode
@ianrichardson twitter
Questions?