The DevOps Way of Delivering Results in the Enterprise
•
25 likes•14,815 views
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.
Recommended
More Related Content
Viewers also liked
Viewers also liked (14)
More from James Wickett
More from James Wickett (20)
Recently uploaded
Recently uploaded (20)
The DevOps Way of Delivering Results in the Enterprise
- 1. The DevOps Way of Delivering Results in the Enterprise James Wickett james_wickett@mentor.com twitter: @wickett mentor.com/embedded Android 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 be successful and make a difference
- 3. James Wickett Sr. DevOps Engineer Mentor Graphics Embedded Software Division regular blogger at: theagileadmin.com ruggeddevops.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. Conclusions The cloud necessitates a new approach to our operations (business and tech) DevOps has worked for startups and can work for the enterprise Rugged DevOps fills some of the needs of the enterprise Use a Behavior Driven Infrastructure approach
- 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 Measured Dave 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 an installation disc” - your customer
- 13. we sell social and friendships
- 14. New landscape Are 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 Computing A detailed understanding of cloud computing - 92% agree Enhanced technical knowledge - 82% agree Contract negotiation skills - 49% agree source: The 2011 (ISC)2 Global Information Security Workforce Study
- 16. Code is social
- 17. Delivery is King courtesy 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 or Give me Death -@littleidea
- 22. the old way is broken
- 23. DevOps is the new hotness for startups
- 24. DevOps is a movement predicated by: cloud, startups, SaaS, consumerization of IT
- 25. “there is nothing to suggest that devops can’t work in the enterprise” -Patrick Debois Cutter IT Journal,Vol. 24, No. 12, pg 3
- 27. DevOps?
- 28. Dev http://www.flickr.com/photos/johnemofunk/551939308
- 29. Ops http://www.flickr.com/photos/kristykay/125709246
- 30. source: Gene Kim, “When IT says No” @SXSW 2012
- 31. DevOps
- 38. Culture Automation Measurement Sharing source: John Willis (@botchagalupe) and Damon Edwards (@damonedwards)
- 40. Culture is the most important aspect to DevOps succeeding in the enterprise
- 41. Culture Eliminate the blame game Open post-mortems Rewarding failure (and emphasis on testing) Release often
- 42. DevOps Antipattern: Rebrand your Ops team as the DevOps team
- 43. DevOps Antipattern: Use a machines to people hiring ratio to determine headcount
- 46. Unique bits Software (RPM) OS Image (AMI)
- 47. DevOps Antipattern: Deploy software manually
- 48. DevOps Antipattern: Test only the application code
- 49. DevOps Antipattern: Manual configuration of production environments
- 50. DevOps Antipattern: Believe chef/puppet/cfengine will solve all your problems
- 51. DevOps Antipattern: Deploy to a production-like environment only after development is complete
- 53. Measurement Performance metrics Logs Metrics mapped to business goals Integration with people
- 54. DevOps Antipattern: Rely on the standard logs for metrics
- 56. Sharing Feedback loops Enables the Automation and Measurement Significantly impacts Culture
- 58. DevOps Antipattern: Hide stuff from your team
- 60. and Kanban courtesy of fright42: http://www.flickr.com/photos/fright42/5329361800/sizes/l/in/photostream/
- 62. Enterprise?
- 63. the perception of The Enterprise
- 64. slow
- 66. process obsessed
- 67. compliance and conformity as first order goals
- 68. control
- 69. DevOps and Enterprise are unlikely traveling companions
- 70. “there is nothing to suggest that devops can’t work in the enterprise” -Patrick Debois Cutter IT Journal,Vol. 24, No. 12, pg 3
- 71. “The main challenge will be reevaluating the existing people and processes from a constant collaboration viewpoint, keeping the business goals in mind.” -Patrick Debois Cutter IT Journal,Vol. 24, No. 12, pg 3
- 73. The Enterprise has different needs
- 74. The Enterprise needs Longevity Stakeholders Revenue Compliance Safeguards (data, legal, ...)
- 76. THE INEQUITABLE DISTRIBUTION OF LABOR IN SECURITY MIMICS THAT IN DEV/OPS
- 77. 2% of an engineering dev team are working on security - BSIMM 2012 data, http://bsimm.com/
- 79. I recognize that my code will be attacked by talented and persistent adversaries who threaten our physical, economic, and national security. I recognize that my code will be used in ways I cannot 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.
- 81. Current Software slide from http://bit.ly/rugged-devops
- 82. Rugged Software slide from http://bit.ly/rugged-devops
- 83. Current Software slide from http://bit.ly/rugged-devops
- 84. Rugged Software slide from http://bit.ly/rugged-devops
- 85. Current Software slide from http://bit.ly/rugged-devops
- 86. Rugged Software slide from http://bit.ly/rugged-devops
- 87. ADVERSITY REQUIRES RUGGED SOLUTIONS slide from http://bit.ly/rugged-devops
- 88. 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
- 89. NO PAIN, NO GAIN slide from http://bit.ly/rugged-devops
- 91. Rugged DevOps repeatable – no manual steps reliable - no DoS here reviewable – aka audit rapid – fast to build, deploy, restore resilient – automated reconfiguration reduced - limited attack surface slide from http://bit.ly/rugged-devops
- 92. Rugged DevOps Testing unit tests smoke tests security tests (gauntlt) outside-in tests (cucumber, aruba) monitoring (created from your tests)
- 93. What about the toolchain?
- 94. Paul Hammond, Scaling Typekit Infrastructure for Startups,Velocity 2012
- 95. Paul Hammond, Scaling Typekit Infrastructure for Startups,Velocity 2012
- 96. Our Toolchain and Software Stack ubuntu chef AWS (ec2, s3) mongodb Datadog cucumber nginx pingdom aruba tornado loggly gauntlt haproxy PagerDuty CloudWatch IRC JIRA github
- 97. Behavior Driven Infrastructure Write failing tests describing the infrastructure you wish you had Make them pass by writing infrastructure automation code (chef/puppet) Repeat
- 98. In summary
- 99. Culture is the most important aspect to DevOps succeeding in the enterprise -me, 30 minutes ago
- 100. Conclusions The cloud necessitates a new approach to our operations (business and tech) DevOps has worked for startups and can work for the enterprise Rugged DevOps fills some of the needs of the enterprise Use a Behavior Driven Infrastructure approach
- 101. 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
- 102. The DevOps Way of Delivering Results in the Enterprise James Wickett james_wickett@mentor.com twitter: @wickett mentor.com/embedded Android 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.