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
