Devops Culture inCustomer Systems
All right stop. Collaborate and listen.Teams.
Teams - Previously"Devops" rotationsOps asDeployment dictatorsProduction paladinsMonitoring monarchsIncrease visibilityRed...
EMPOWOARRR!!!!
Monitoring.Deployments.
Teams - CurrentlyOps as expertsAutonomyEmpower teamFull application ownership*Remove blockersReduce feedback loopGSD metho...
Monitoring - PreviouslyOpsCreate checksReceive alertsRespond to issuesEscalate to Teams
Monitoring - CurrentlyTeamsCreate checksReceive alerts*Respond to issuesEscalate to Ops* for the application, during busin...
Deployments - PreviouslyGrab the correct build artifactEdit puppet with artifact versionAdd scheduled downtime for the ser...
Deployments - AutobotsV1Get build artifactEdit puppet with versionLogin to deploy boxRun Deploybot
Deployments - AutobotsV2Get build artifactEdit puppet with versionGo to webpage, click.From: Tan Le <tan.le@rea-group.com>...
* fist bump *
Schema Changes - PreviouslyGrab the SQL from the repositoryModify for productionAdd scheduled downtime for the serverRemov...
Schema Changes - SchemabotV1Grab the SQL from the repositoryModify for productionRun Schemabot
* fist bump *
Whats next?
Ask yourselfIs my work adding value?
Devops culture in customer systems
Devops culture in customer systems
Devops culture in customer systems
Devops culture in customer systems
Upcoming SlideShare
Loading in …5
×

Devops culture in customer systems

822 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
822
On SlideShare
0
From Embeds
0
Number of Embeds
48
Actions
Shares
0
Downloads
3
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Devops culture in customer systems

  1. 1. Devops Culture inCustomer Systems
  2. 2. All right stop. Collaborate and listen.Teams.
  3. 3. Teams - Previously"Devops" rotationsOps asDeployment dictatorsProduction paladinsMonitoring monarchsIncrease visibilityReduce time to productionSchedule changes
  4. 4. EMPOWOARRR!!!!
  5. 5. Monitoring.Deployments.
  6. 6. Teams - CurrentlyOps as expertsAutonomyEmpower teamFull application ownership*Remove blockersReduce feedback loopGSD methodologyOpen discussions* from Platform up.
  7. 7. Monitoring - PreviouslyOpsCreate checksReceive alertsRespond to issuesEscalate to Teams
  8. 8. Monitoring - CurrentlyTeamsCreate checksReceive alerts*Respond to issuesEscalate to Ops* for the application, during business hours
  9. 9. Deployments - PreviouslyGrab the correct build artifactEdit puppet with artifact versionAdd scheduled downtime for the serverRemove server from the load balancerRun puppet on serverAdd server into the load balancerRemove the scheduled downtime
  10. 10. Deployments - AutobotsV1Get build artifactEdit puppet with versionLogin to deploy boxRun Deploybot
  11. 11. Deployments - AutobotsV2Get build artifactEdit puppet with versionGo 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 ProductionThis time we use the Push button deploy via Jenkins
  12. 12. * fist bump *
  13. 13. Schema Changes - PreviouslyGrab the SQL from the repositoryModify for productionAdd scheduled downtime for the serverRemove server from the load balancerRun the migration*Add server into the load balancerRemove the scheduled downtime* inverse replication order - knowledge of the database topology required
  14. 14. Schema Changes - SchemabotV1Grab the SQL from the repositoryModify for productionRun Schemabot
  15. 15. * fist bump *
  16. 16. Whats next?
  17. 17. Ask yourselfIs my work adding value?

×