Devops culture in customer systems
Upcoming SlideShare
Loading in...5
×
 

Devops culture in customer systems

on

  • 626 views

 

Statistics

Views

Total Views
626
Views on SlideShare
600
Embed Views
26

Actions

Likes
1
Downloads
1
Comments
0

1 Embed 26

http://www.geekle.id.au 26

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Devops culture in customer systems Devops culture in customer systems Presentation 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
  • EMPOWOARRR!!!!
  • Monitoring.Deployments.
  • 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 <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
  • * 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
  • * fist bump *
  • Whats next?
  • Ask yourselfIs my work adding value?