1. Devops Culture in
Customer Systems

2. All right stop. Collaborate and listen.
Teams.

3. Teams - Previously
"Devops" rotations
Ops as
Deployment dictators
Production paladins
Monitoring monarchs
Increase visibility
Reduce time to production
Schedule changes

5. EMPOWOARRR!!!!

6. Monitoring.
Deployments.

7. Teams - Currently
Ops as experts
Autonomy
Empower team
Full application ownership*
Remove blockers
Reduce feedback loop
GSD methodology
Open discussions
* from Platform up.

8. Monitoring - Previously
Ops
Create checks
Receive alerts
Respond to issues
Escalate to Teams

9. Monitoring - Currently
Teams
Create checks
Receive alerts*
Respond to issues
Escalate to Ops
* for the application, during business hours

10. Deployments - Previously
Grab the correct build artifact
Edit puppet with artifact version
Add scheduled downtime for the server
Remove server from the load balancer
Run puppet on server
Add server into the load balancer
Remove the scheduled downtime

14. Deployments - AutobotsV1
Get build artifact
Edit puppet with version
Login to deploy box
Run Deploybot

15. Deployments - AutobotsV2
Get build artifact
Edit puppet with version
Go to webpage, click.
From: Tan Le <tan.le@rea-group.com>
To: Diamond Team <diamond@rea-group.com>
Cc: autobots <cstechteam@rea-group.com>
Subject: FW: Studio deployed to Production
This time we use the Push button deploy via Jenkins

16. * fist bump *

17. Schema Changes - Previously
Grab the SQL from the repository
Modify for production
Add scheduled downtime for the server
Remove server from the load balancer
Run the migration*
Add server into the load balancer
Remove the scheduled downtime
* inverse replication order - knowledge of the database topology required

18. Schema Changes - SchemabotV1
Grab the SQL from the repository
Modify for production
Run Schemabot

19. * fist bump *

20. What's next?

21. Ask yourself
Is my work adding value?