The DevOps Way of Delivering Results in the Enterprise

  • 15,146 views
Uploaded on

Delivering Software as a Service in the cloud requires agility and speed. Sadly, those are two attributes that big companies aren’t usually good at doing. Instead of organizing to deliver results, …

Delivering Software as a Service in the cloud requires agility and speed. Sadly, those are two attributes that big companies aren’t usually good at doing. Instead of organizing to deliver results, companies tend to build silos where development, operations, QA and security operate as separate entities. DevOps unites these groups to deliver services faster and provide results that matter.

This talk will arm you with the DevOps patterns to follow as well as point out specific anti-patterns to avoid. To show you how to implement DevOps in your org, this talk will cover sample architectures and Open Source tooling. Come hear how to start delivering results with increased agility and speed.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
15,146
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
719
Comments
0
Likes
12

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. The DevOps Way of Delivering Results in the Enterprise James Wickett james_wickett@mentor.com twitter: @wickett mentor.com/embeddedAndroid  is  a  trademark  of  Google  Inc.  Use  of  this  trademark  is  subject  to  Google  Permissions.Linux  is  the  registered  trademark  of  Linus  Torvalds  in  the  U.S.  and  other  countries.
  • 2. I want you to besuccessful andmake a difference
  • 3. James WickettSr. DevOps EngineerMentor GraphicsEmbedded Software Divisionregular blogger at:theagileadmin.comruggeddevops.org CISSP, GWAPT CCSK, GSEC, GCFW @wickett james_wickett@mentor.com
  • 4. Experience• Started using AWS cloud in early 2008• 2.5 years working on a DevOps team• History of working in the enterprise and in startups and in startups inside the enterprise• DevOps Days Austin Organizer
  • 5. ConclusionsThe cloud necessitates a new approachto our operations (business and tech)DevOps has worked for startups and canwork for the enterpriseRugged DevOps fills some of the needsof the enterpriseUse a Behavior Driven Infrastructureapproach
  • 6. DevOps Antipatterns• Rebrand your Ops team as the DevOps team• Use a machines to people hiring ratio to determine headcount• Deploy software manually• Believe chef/puppet/cfengine will solve all your problems• Test only the application code• Deploy to a production-like environment only after development is complete• Rely on the standard logs for metrics• Hide stuff from your team
  • 7. before devops and enterprise,lets start with cloud
  • 8. courtesy of akakumo http://www.flickr.com/photos/kky/704056791/sizes/o/
  • 9. “Cloud? I’ve been doing that since 1988. It’s just the same old thing with a new name." - Technohipster “Rugged DevOps will help you build your cloud” - http://bit.ly/rugged-devops
  • 10. OSSM On-Demand Scalable Self-service MeasuredDave Nielsen > http://www.rackspace.com/blog/on-definitions-keeping-it-simple-with-ossm/
  • 11. we sell time now
  • 12. “I don’t want you to send me aninstallation disc” - your customer
  • 13. we sell social and friendships
  • 14. New landscapeAre New Skills Required for Cloud Computing?Cloud computing requires new skills - 74%Cloud computing does not require new skills - 26% source: The 2011 (ISC)2 Global Information Security Workforce Study
  • 15. Specific New Skills Required for Cloud ComputingA detailed understanding of cloudcomputing - 92% agreeEnhanced technical knowledge - 82% agreeContract negotiation skills - 49% agree source: The 2011 (ISC)2 Global Information Security Workforce Study
  • 16. Code is social
  • 17. Delivery is Kingcourtesy of dbaron: http://www.flickr.com/photos/dbaron/2437975928/
  • 18. Time To Market is Crucial
  • 19. SaaS and PaaS
  • 20. New World of Services
  • 21. Give me API orGive me Death -@littleidea
  • 22. the old way is broken
  • 23. DevOps is the newhotness for startups
  • 24. DevOps is a movement predicated by:cloud, startups, SaaS, consumerization of IT
  • 25. “there is nothing to suggest thatdevops can’t work in the enterprise” -Patrick Debois Cutter IT Journal,Vol. 24, No. 12, pg 3
  • 26. DevOps?
  • 27. Dev http://www.flickr.com/photos/johnemofunk/551939308
  • 28. Ops http://www.flickr.com/photos/kristykay/125709246
  • 29. source: Gene Kim, “When IT says No” @SXSW 2012
  • 30. DevOps
  • 31. http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr
  • 32. http://upload.wikimedia.org/wikipedia/commons/b/b5/Devops.svg
  • 33. http://dev2ops.org/blog/2010/2/22/what-is-devops.html
  • 34. http://dev2ops.org/blog/2010/2/22/what-is-devops.html
  • 35. http://dev2ops.org/blog/2010/2/22/what-is-devops.html
  • 36. CultureAutomationMeasurementSharingsource: John Willis (@botchagalupe) and Damon Edwards (@damonedwards)
  • 37. DevOps is Culture
  • 38. Culture is the mostimportant aspect to DevOpssucceeding in the enterprise
  • 39. CultureEliminate the blame gameOpen post-mortemsRewarding failure (and emphasis ontesting)Release often
  • 40. DevOps Antipattern:Rebrand your Ops team as the DevOps team
  • 41. DevOps Antipattern:Use a machines to people hiring ratio to determine headcount
  • 42. DevOps is Automation
  • 43. AutomationDeployControlMonitoringConfig ManagementOrchestration
  • 44. Unique bitsSoftware (RPM)OS Image (AMI)
  • 45. DevOpsAntipattern: Deploy software manually
  • 46. DevOps Antipattern: Test only the application code
  • 47. DevOps Antipattern:Manual configuration ofproduction environments
  • 48. DevOps Antipattern:Believe chef/puppet/cfengine will solve all your problems
  • 49. DevOps Antipattern:Deploy to a production-like environment only after development is complete
  • 50. DevOps isMeasurement
  • 51. MeasurementPerformance metricsLogsMetrics mapped to business goalsIntegration with people
  • 52. DevOps Antipattern:Rely on the standard logs for metrics
  • 53. DevOps is Sharing
  • 54. SharingFeedback loopsEnables the Automation andMeasurementSignificantly impacts Culture
  • 55. http://www.flickr.com/photos/mrphotographyfan/6108192865
  • 56. DevOps Antipattern: Hide stuff from your team
  • 57. Don’t forget Lean
  • 58. and Kanban courtesy of fright42: http://www.flickr.com/photos/fright42/5329361800/sizes/l/in/photostream/
  • 59. The DevOps Library
  • 60. Enterprise?
  • 61. the perception ofThe Enterprise
  • 62. slow
  • 63. innovation starved
  • 64. process obsessed
  • 65. compliance and conformity as first order goals
  • 66. control
  • 67. DevOps and Enterprise are unlikelytraveling companions
  • 68. “there is nothing to suggest thatdevops can’t work in the enterprise” -Patrick Debois Cutter IT Journal,Vol. 24, No. 12, pg 3
  • 69. “The main challenge will be reevaluating theexisting people and processes froma constant collaboration viewpoint,keeping the business goals in mind.” -Patrick Debois Cutter IT Journal,Vol. 24, No. 12, pg 3
  • 70. Startups needCashCustomers (stakeholders)ExperimentationRisk
  • 71. The Enterprise has different needs
  • 72. The Enterprise needsLongevityStakeholdersRevenueComplianceSafeguards (data, legal, ...)
  • 73. HTTP://BIT.LY/RUGGED-DEVOPS
  • 74. THE INEQUITABLEDISTRIBUTION OFLABOR IN SECURITYMIMICS THAT IN DEV/OPS
  • 75. 2% of an engineeringdev team areworking on security - BSIMM 2012 data, http://bsimm.com/
  • 76. I recognize that my code will be attacked by talentedand persistent adversaries who threaten our physical, economic, and national security.I recognize that my code will be used in ways Icannot anticipate, in ways it was not designed, and for longer than it was ever intended.I am rugged, not because it is easy, but because it is necessary... and I am up for the challenge.
  • 77. Current Softwareslide from http://bit.ly/rugged-devops
  • 78. Rugged Softwareslide from http://bit.ly/rugged-devops
  • 79. Current Software slide from http://bit.ly/rugged-devops
  • 80. Rugged Software slide from http://bit.ly/rugged-devops
  • 81. Current Software slide from http://bit.ly/rugged-devops
  • 82. Rugged Software slide from http://bit.ly/rugged-devops
  • 83. ADVERSITY REQUIRESRUGGED SOLUTIONS slide from http://bit.ly/rugged-devops
  • 84. Building solutions to handle adversity will cause unintended, positive benefits that will provide value that would have been unrealized otherwise. RUGGEDIZATION THEORY slide from http://bit.ly/rugged-devops
  • 85. NO PAIN, NO GAIN slide from http://bit.ly/rugged-devops
  • 86. slide from http://bit.ly/rugged-devops
  • 87. Rugged DevOpsrepeatable – no manual stepsreliable - no DoS herereviewable – aka auditrapid – fast to build, deploy, restoreresilient – automated reconfigurationreduced - limited attack surface slide from http://bit.ly/rugged-devops
  • 88. Rugged DevOps Testingunit testssmoke testssecurity tests (gauntlt)outside-in tests (cucumber, aruba)monitoring (created from your tests)
  • 89. What about the toolchain?
  • 90. Paul Hammond, Scaling Typekit Infrastructure for Startups,Velocity 2012
  • 91. Paul Hammond, Scaling Typekit Infrastructure for Startups,Velocity 2012
  • 92. Our Toolchain and Software Stackubuntu chef AWS (ec2, s3)mongodb Datadog cucumbernginx pingdom arubatornado loggly gauntlthaproxy PagerDuty CloudWatchIRC JIRA github
  • 93. Behavior Driven InfrastructureWrite failing tests describing theinfrastructure you wish you hadMake them pass by writing infrastructureautomation code (chef/puppet)Repeat
  • 94. In summary
  • 95. Culture is the mostimportant aspect to DevOpssucceeding in the enterprise -me, 30 minutes ago
  • 96. ConclusionsThe cloud necessitates a new approachto our operations (business and tech)DevOps has worked for startups and canwork for the enterpriseRugged DevOps fills some of the needsof the enterpriseUse a Behavior Driven Infrastructureapproach
  • 97. DevOps Antipatterns• Rebrand your Ops team as the DevOps team• Use a machines to people hiring ratio to determine headcount• Deploy software manually• Believe chef/puppet/cfengine will solve all your problems• Test only the application code• Deploy to a production-like environment only after development is complete• Rely on the standard logs for metrics• Hide stuff from your team
  • 98. The DevOps Way of Delivering Results in the Enterprise James Wickett james_wickett@mentor.com twitter: @wickett mentor.com/embeddedAndroid  is  a  trademark  of  Google  Inc.  Use  of  this  trademark  is  subject  to  Google  Permissions.Linux  is  the  registered  trademark  of  Linus  Torvalds  in  the  U.S.  and  other  countries.