Successfully reported this slideshow.
Your SlideShare is downloading. ×

The DevOps Way of Delivering Results in the Enterprise

Ad

The DevOps Way
                       of Delivering Results
                      in the Enterprise

                     ...

Ad

I want you to be
successful and
make a difference

Ad

James Wickett
Sr. DevOps Engineer

Mentor Graphics
Embedded Software Division



regular blogger at:
theagileadmin.com
rug...

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Upcoming SlideShare
Devops the Microsoft Way
Devops the Microsoft Way
Loading in …3
×

Check these out next

1 of 102 Ad
1 of 102 Ad

The DevOps Way of Delivering Results in the Enterprise

Download to read offline

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.

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.

Advertisement
Advertisement

More Related Content

Advertisement
Advertisement

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
  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. Culture Automation Measurement Sharing source: John Willis (@botchagalupe) and Damon Edwards (@damonedwards)
  37. DevOps is Culture
  38. Culture is the most important aspect to DevOps succeeding in the enterprise
  39. Culture Eliminate the blame game Open post-mortems Rewarding failure (and emphasis on testing) 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. Automation Deploy Control Monitoring Config Management Orchestration
  44. Unique bits Software (RPM) OS Image (AMI)
  45. DevOps Antipattern: Deploy software manually
  46. DevOps Antipattern: Test only the application code
  47. DevOps Antipattern: Manual configuration of production 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 is Measurement
  51. Measurement Performance metrics Logs Metrics mapped to business goals Integration with people
  52. DevOps Antipattern: Rely on the standard logs for metrics
  53. DevOps is Sharing
  54. Sharing Feedback loops Enables the Automation and Measurement Significantly 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 of The Enterprise
  62. slow
  63. innovation starved
  64. process obsessed
  65. compliance and conformity as first order goals
  66. control
  67. DevOps and Enterprise are unlikely traveling companions
  68. “there is nothing to suggest that devops can’t work in the enterprise” -Patrick Debois Cutter IT Journal,Vol. 24, No. 12, pg 3
  69. “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
  70. Startups need Cash Customers (stakeholders) Experimentation Risk
  71. The Enterprise has different needs
  72. The Enterprise needs Longevity Stakeholders Revenue Compliance Safeguards (data, legal, ...)
  73. HTTP://BIT.LY/RUGGED-DEVOPS
  74. THE INEQUITABLE DISTRIBUTION OF LABOR IN SECURITY MIMICS THAT IN DEV/OPS
  75. 2% of an engineering dev team are working on security - BSIMM 2012 data, http://bsimm.com/
  76. 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.
  77. Current Software slide from http://bit.ly/rugged-devops
  78. Rugged Software slide 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 REQUIRES RUGGED 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 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
  88. Rugged DevOps Testing unit tests smoke tests security 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 Stack ubuntu chef AWS (ec2, s3) mongodb Datadog cucumber nginx pingdom aruba tornado loggly gauntlt haproxy PagerDuty CloudWatch IRC JIRA github
  93. Behavior Driven Infrastructure Write failing tests describing the infrastructure you wish you had Make them pass by writing infrastructure automation code (chef/puppet) Repeat
  94. In summary
  95. Culture is the most important aspect to DevOps succeeding in the enterprise -me, 30 minutes ago
  96. 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
  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/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.

×