Stories from the trenches of improving Continuos Integration using Docker

1. Docker at ANZ
DevOps Lead ANZ (Odecee)
@gedesuparsa
https://au.linkedin.com/in/gedes

2. Before & After
• Build queues often blow out
to hours
• Feedback is not continuous
leading to a spike to work in
progress
• Devops needs to babysit
each build (not
autonomous) due to
underspec & over
subscribed.
BB
x5
BB
x5
BB
x5
git
Developer
Build
Queue
•
•
•
1-3hrs
Mac
Minis
VM
Bamboo Build
Agent
Checkin
Feedback
for green
build
>24hrs
Before
(slow feedback – aka waterfall)
Today
(fast feedback)
Build
Queue
1-2min
git
Developer
Checkin
Feedback
for green
build
<30min
Docker
images
Redhat7 VM (4)
Firewall
Firewall
Firewall
Firewall
Web
App App
DB
MQ
Simul
ator
Redis
BB
Work In Progress
t
Work In Progress
1
• Docker images created &
destroyed on demand
• Work in progress drops (less
context switching)
• Moving Redhat7 to SOE will
remove firewalls & ability to
extend to other envs,
currently only for CI.
• VM size is elastic, but relies
on robust hardware
management. Strategic intent
to move to AWS for long term
scalable solution.
2
1
2
3
3
1
2
3
1
2
3
4
Docker
containers
Splunk
t
4
Log
data
*
LISA

3. Output & Next Step
• Over 200 builds a day
• Over 270 GB Docker Images
– WebSphere App Server & Liberty, MQ, LISA (tests),
Redis, nginx, Oracle DB,
– Developer images
• Increase Linux farm capacity
• Scale the image repository

4. What’s made it happen
• Management support
• Spike & show value through demonstration
• Picked greenfields – careful choice of
retrofitting
• Aligning benefits with support teams
• Measurements & solving problems