Devops culture in customer systemsPresentation Transcript
Devops Culture inCustomer Systems
All right stop. Collaborate and listen.Teams.
Teams - Previously"Devops" rotationsOps asDeployment dictatorsProduction paladinsMonitoring monarchsIncrease visibilityReduce time to productionSchedule changes
Teams - CurrentlyOps as expertsAutonomyEmpower teamFull application ownership*Remove blockersReduce feedback loopGSD methodologyOpen discussions* from Platform up.
Monitoring - PreviouslyOpsCreate checksReceive alertsRespond to issuesEscalate to Teams
Monitoring - CurrentlyTeamsCreate checksReceive alerts*Respond to issuesEscalate to Ops* for the application, during business hours
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
Deployments - AutobotsV1Get build artifactEdit puppet with versionLogin to deploy boxRun Deploybot
Deployments - AutobotsV2Get build artifactEdit puppet with versionGo to webpage, click.From: Tan Le <firstname.lastname@example.org>To: Diamond Team <email@example.com>Cc: autobots <firstname.lastname@example.org>Subject: FW: Studio deployed to ProductionThis time we use the Push button deploy via Jenkins
* fist bump *
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
Schema Changes - SchemabotV1Grab the SQL from the repositoryModify for productionRun Schemabot