How to introduce CD and containers in a large organisation

1. Containerdays 2016
rainbows @ Libertyglobal
AnneBakker
DirectorWebDevelopment

2. Liberty global
Key Facts:
• World's largest international TV and broadband company
• Revenue: $19.3 billion
• Employees: 45,0002
• 56 million homes passed
• 29 million customers
• 59 million RGUs (video, internet, and voice subscribers)
http://www.libertyglobal.com

3. 🌈Business Value
• ↓Time to markets
• ↓Costs of software delivery ($ for 1 loc)
• ↓Operational issues related to deployments
• ↓AWS costs (higher density)
• quick response, tactical solutions, innovation
• the feeling of editing PHP live on the server

4. Challenge
Delivery pipeline
Dev Test Prod
🔥
💰Over budget
Late
😢
Clogged by lage projects
5-6 weeks?

5. Puzzle
Continuous
Delivery
Agile DevOps
Containers Micro
services

6. Journey
2013 2016
Docker (ECS)
OpsWorks
CoreOSCF
Ruby/Chef

7. Abstraction
Hardware
Virtualization
Containers
IaaS
PaaS
DiyS
ps
Dev
changes the dialog between Dev and Ops

8. Today
AWS
Internal
Web API Gateway
Internet
H H H H …
Service Gateway

9. Today
AWS ECS
Consul
Fabio
Docker
registry
Graphite
Service Gateway
AWS services
Vault
ELK
Jenkins
CaaS.rb

10. 7 learnings
introducing CD and Containers in a large company

11. Just do it1
very good for your air miles…

12. Just do it
• …and ask for forgiveness later
• Start small, start simple, start now
• starting with dev and test environments
• using one of the many ‘container as a service’
solutions out there…
• build up a team and get them familiar with the
technology and DevOps culture
1

13. Things will fail2
Perhaps not as dramatic as this…

14. Things will fail
• ask for forgiveness… an try not to get tied up in
process, longer test cycles and approval discussions
• Service monitoring! shared to everyone to know
exactly what is happening (ELK)
• Create a ‘blast zone’ (AWS account)
• Do Canary releases
• MTTR vs MTBF
2

15. Old habits3
Only Sinterklaas is happy to deploy at night…

16. Old habits
• Lengthy change approval processes and ticket
systems that make you don’t want to make any
changes…
• Releasing software at night
• Decouple deployment from releasing
• Create a fast track for small changes…
• then make all your changes small
3

17. Security4
and we will make them pay for it as well…

18. Security
• Most security measures are implemented by
network segmentation and firewalls
• Try to involve security early on; work from
document reviewing to active participation
• A service gateway (fixed IPs) can help you
connect to legacy systems and deal with firewalls.
• Containers and immutable infrastructure should be
a blessing for security (audit trail in github)
4

19. Legacy5
Can I deploy this in containers?

20. Legacy
• You cannot just put ‘the big stateful monolith’ into a
docker container and expect rainbows to appear
• You can however augment and slowly migrate
legacy systems into microservices and containers.
• Hardest part is to split it into decoupled subsystems
and carving out the state (apply the DDD book)
• Containers allow you to run microservices cost
effective
5

21. Evergreen6
Don’t let your software get stale

22. Evergreen
• “Legacy software” arises when you do BIG software
projects and deploy and forget
• Usually large (vendor) monoliths interwoven to a point
where no-one dares to make changes
• Not easy to update dependencies, or do partial upgrades
• Start thinking services with dedicated long term teams
supporting its lifecycle
• Microservices and containers can help you fight the curve
6

23. Ownership7
“You build it, you run it”, you own it

24. Ownership
• End to end ownership is perhaps the most valuable
and most difficult virtue to achieve in large
companies.
• Create a DevOps Culture breaking down the Silos
• ChatOps vs ticket tools (take the emotion out)
• Team size vs ownership (Pizza size)
• Only 🌈rainbows from there on…
7

25. Your puzzle
Smaller
Think
Try to avoid heavy lifting