Presentation on the technical and cultural challenges when adopting Puppet in a brownfield UK government account. Talk will cover how we were able to get key stakeholder backing and confidence, and how we were able to rapidly skill up multiple teams to use Puppet. We'll discuss some key technical challenges, and how we overcame these. I'll describe the benefits that were reaped from utilizing Puppet, and how that has enabled the implementation of a large fully distributed service. Also, how we migrated from Puppet 3 to Puppet 4; what's next; and how we envisage continuing to use Puppet to exploit its capabilities.

1. INDY BAINS
INTERCEPTING PUPPET IN A LARGE GOVERNMENT
ESTATE

2. ABOUT ME
INDY BAINS
▸ @ibains007
▸ www.linkedin.com/in/indybains

3. AGENDA
▸ The client
▸ Existing processes
▸ Challenges
▸ Actions
▸ Implementation
▸ Benefits
▸ Future

4. THE CLIENT

5. THE CLIENT

6. THE CLIENT
PAIN POINTS

7. THE CLIENT
AMBITIONS

8. CHALLENGES
▸ Changes to the platform needed to be:-
▸ Quicker
▸ More reliable
▸ Consistent
▸ Made by a single team

9. CHALLENGES
▸ Organisation
▸ Commercial
▸ Cultural
▸ People / Capability
▸ Technical
▸ Security

10. ACTIONS
MAKE IT REAL

11. ACTIONS
STAKEHOLDER INVOLVEMENT
▸ Senior Management
▸ Security
▸ Configuration management
▸ Service management
▸ Development teams

12. IMPLEMENTATION

13. IMPLEMENTATION

14. IMPLEMENTATION
HIERA
Role

15. IMPLEMENTATION
HIERA
WWW
R10K R10K R10K R10K
EYAML

16. App
Server A
App
Server B
App
Server C
Physical Load BalancerPhysical Load Balancer
Data IP (floating)
Management IP
App
Server D
App
Server D
NETWORKING

17. App
Server D
Physical Load Balancer
App
Server A
App
Server B
App
Server C
Software Load Balancer
Service
Discovery
Management /
Data IPSoftware Load BalancerSoftware Load Balancer
App
Server D
App
Server D
Healthcheck
NETWORKING

18. BENEFITS
▸ Infrastructure - as - code
▸ Documentation is accurate
▸ Consistency
▸ Secrets management
▸ Reduced reliance on other teams
▸ Eliminated configuration drift
SUMMARY

19. CAPABILITY
TRAINING

20. FUTURE
▸ Puppet 3 -> 4 (2017)
▸ Immutable infrastructure
▸ Orchestration

21. QUESTIONS