Devops Culture in Customer Systems

All right stop. Collaborate and listen.

Teams.

Teams - Previously

"Devops" rotationsOps as

Deployment dictatorsProduction paladinsMonitoring monarchs

Increase visibilityReduce time to productionSchedule changes

EMPOWOARRR!!!!

Monitoring.Deployments.

Teams - Currently

Ops as expertsAutonomyEmpower teamFull application ownership*Remove blockersReduce feedback loopGSD methodologyOpen discussions

* from Platform up.

Monitoring - Previously

OpsCreate checksReceive alertsRespond to issuesEscalate to Teams

Monitoring - Currently

TeamsCreate checksReceive alerts*Respond to issuesEscalate to Ops

* for the application, during business hours

Deployments - Previously

Grab 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 - AutobotsV1

Get build artifactEdit puppet with versionLogin to deploy boxRun Deploybot

Deployments - AutobotsV2

Get 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 Production

This time we use the Push button deploy via Jenkins

* fist bump *

Schema Changes - Previously

Grab 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 - SchemabotV1

Grab the SQL from the repositoryModify for productionRun Schemabot

* fist bump *

What's next?

Ask yourself

Is my work adding value?