Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Transforming to OpenStack: a sample roadmap to DevOps

4,669 views

Published on

Presentation given at the OpenStack summit in Paris (Kilo) on Tue Nov 4th.

Last summit I had the pleasure to present a talk which encountered some success "Are enterprise ready for the OpenStack transformation?" (also published on SlideShare) . This talk is a follow up on what are the best practices that are successful in operating the transformation. We will first focus on identifying the right use cases for a generic enterprise, then define a roadmap with an organisational and a technical track, to finish with the definition what would be our success criterias for our group. This will happen as a workshop summary based on the multiple engagements eNovance has been delivering over the past 2 years.

Published in: Technology

Transforming to OpenStack: a sample roadmap to DevOps

  1. 1. TRANSFORMING TO OPENSTACK A SAMPLE ROADMAP Nick Barcet @nijaba <nijaba@redhat.com> VP Products & Pre-sales → eNovance Director Product Management - OpenStack → Red Hat OpenStack Summit Kilo - November 2014
  2. 2. ABOUT ME ● VP Products & Pre-Sales @ eNovance ● Director Prod. Mgmt. – OpenStack @ Red Hat ● Been working on OpenStack since Austn ● Founded OpenStack Telemetry (aka Ceilometer) ● Traveling the world doing OpenStack ● @nijaba on irc & twiter
  3. 3. PREVIOUSLY IN ATLANTA
  4. 4. ARE ENTERPRISES READY FOR THE OPENSTACK TRANSFORMATION ● Openstack is not a product ● It will never be “enterprise ready” by itself ● License costs are marginal ● Concentrate on enabling beter processes ● And beter tools ● Transforming your enterprise to produce more value http://www.slideshare.net/NicolasBarcet/are-enterprises-ready-for-the-openstack-transformation
  5. 5. DEVOPS TRANSFORMATION?
  6. 6. TWO DIMENSIONS OF DEVOPS STANDARDIZATION AUTOMATION PEOPLE PROCESS TECHNOLOGY CONTINUOUS IMPROVEMENT
  7. 7. STANDARDIZATION STANDARDIZE TECHNOLOGY • Operating systems (with patch levels) • Application servers • Libraries, Languages, Tooling • Build and packaging technologies • Commercial Off The Shelf STANDARDIZE PROCESSES • Systems Development Life Cycle • Release management • Monitoring • Escalation management
  8. 8. THREE LEVELS OF AUTOMATION APPLICATION LIFE CYCLE AUTOMATION Application MIDDLEWARE PLATFORM AUTOMATION Web/app servers | Libraries INFRASTRUCTURE AUTOMATION Virtualization | OS | Bare metal ACCELERATE DEVOPS USING REDHAT OPEN HYBRID CLOUD 8
  9. 9. C O N T IN U O U S IM P R O V E M E N T MEASURE ROI— METRICS IMPROVE MONITOR DEPLOY TEST CODE BUILD PLAN AGILE
  10. 10. PEOPLE DEVOPS PROCESS TECHNOLOGY PEOPLE • Cultural paradigm shift • Cross-training of skills • Collaboration and involvement of teams across all aspects from designing through monitoring of application • The question everyone should ask is “Is my application driving business value based on the state it is in now?” • Short-lived and interim DevOps Enablement Team can be created in organizations
  11. 11. PROCESS • Agile methodologies • Governance and continuous feedback loops to reduce and eliminate technical debt • Defne metrics for measure • Project is not done until the application is driving value for the customers and business • Automate everything • If something breaks, don’t hack. Fix the automation script and start over. • Common frames of reference (for dev, qa and ops) for application monitoring in production • Developers on call PEOPLE DEVOPS PROCESS TECHNOLOGY
  12. 12. TECHNOLOGY • Automation is key. OpenStack and OpenShift provide lots of required automation capabilities out-of-the-box. • Standardize software versions, patch levels, and provisioning mechanisms • Faster application environment provisioning, root cause analysis • Notifcations and pro-active monitoring PEOPLE DEVOPS PROCESS TECHNOLOGY
  13. 13. A SAMPLE ROADMAP
  14. 14. BACKGROUND • IT has been externalized in a separate entty serving the group • Shadow IT is creeping up (AWS) • External compettors to IT • Fear about loss of data control Must ofer a cloud internally, but how? Existence of IT at risk Compliance risk
  15. 15. ASSESSMENT WORKSHOP • 2 day workshop • All stakeholders in the same room • List of 40 use cases prepared in advance
  16. 16. MATURITY ASSESSMENT • Advanced automaton capabilites • Multple deployments a day • Capabilites as a Service • Templatze individual infrastructure ters; Containers • Auto-Scaling, Pro-actve monitoring and automatc management Self-provisioning of • Virtual Machines • Platorms • Applicaton Environments • Templatze n-ter architecture ters and complex environments • Contnuous Deployment and push-buton applicaton deployments • One deployment a day • Contnuous Integraton • Infrastructure as code • Basic automaton & auto-scaling • Migraton of VMs to OpenStack (IaaS) • Development of greenfeld applicatons in OpenShif (PaaS) • Basic systems provisioning through standardizaton Or ga niz at on al Ma tur ity
  17. 17. FROM USE CASES TO POPULATIONS From the use cases, 3 discrete populaton groups emerged:
  18. 18. HIGH LEVEL ROADMAP
  19. 19. 3 MILESTONES (1/3) Milestone 1 Standardizaton Commoditzaton ● Build a frst environment ○ Used by CI for testng ○ Contnuously Deployed ● Play ground for admins ○ No producton impact, all tech features available Goals: ➔ Defne the frst version of the portal ➔ Propose an SLA for Devs
  20. 20. 3 MILESTONES (2/3) Milestone 2 Ops and Devs join theirs eforts ● Build a development environment ○ First producton app (low hanging fruit) ○ First reportng billing ○ Deployed automatcally when test are ok in frst env Goals: ➔ Defne frst stacks template ➔ Defne UI for applicaton provisioning ➔ Propose the SLA for frst users
  21. 21. 3 MILESTONES (3/3) Milestone 3 End users results delivered ● Build a producton environment ○ mult data center ○ smart placement interface ○ complete billing / reportng ○ Deployed automatcally when validated by Dev Goals: ➔ Validate SLA + Functons ➔ Defne next applicatons priorites
  22. 22. 3 ENVIRONMENTS FROM ONE SOURCE
  23. 23. C O N T IN U O U S D E L IV E R Y REDHAT OPEN HYBRID CLOUD IDEA PRODUCT FEATURE SELF PROVISIONING ENVIRONMENT STANDARDIZATION AUTO SCALING CENTERALIZED OPS MANAGEMENT DEV QA UAT PROD IDE CONFIGURATION MANAGEMENT CONTINUOUS INTEGRATION MONITORING CYCLE TIME PRODUCT MANAGER DEVELOPERS TEST ENGINEERS OPERATIONS PERSONNEL CONTINUOUS DELIVERY
  24. 24. METHOD
  25. 25. R O L E S , S P R IN T S A N D M IL E S T O N E S
  26. 26. P O P U L A T IO N T R E N D S PO PO 26
  27. 27. SUMMARY
  28. 28. PROBLEMS ● IT has been externalised in a separate entity serving the group ● Shadow IT is creeping up (AWS) ● IT also has external competitors ● Group is fearing loss of data control SOLUTIONS BENEFITS ● Offer an internal IaaS and PaaS Cloud ● Build a self service portals for Admins, Devs and Ops ● Organize small teams with cross roles members ● Use SCRUM to enable rapid feedback based adaptability ● Grow agile/devops awareness through contamination, not top down decision ● Use cloud as the opportunity to go devops ● Reduce time to market not only for IT assets but throughout the organisation ● Retain sensitive information internally ● Obtain clear reports on costs and purpose ● Grow self responsibility in all teams ● IT returns as a solution providers instead of a road block ● Refocused teams on solving business problems SUMMARY
  29. 29. LIMITED TIME OFFER BUY OUR OPENSTACK CERTIFICATION EXAM, GET THE ONLINE LEARNING COURSE FREE! First 500 to buy the exam get the related course free for 90 days. redhat.com/training/paths/openstack
  30. 30. GUARANTEE YOUR SEAT VISIT THE RED HAT BOOTH FOR DETAILS For today only, the first 10 to register on the EX210 with promo code Prep4Stack will be guaranteed a spot (otherwise subject to availability).

×