Is Orchestration the Next Big Thing in DevOps


Published on

DevOps processes (such as continuous deployment and delivery) often involve writing many custom scripts that are triggered by the build system. With that approach, it is relatively hard to trace the deployment process and troubleshoot when something goes wrong. Additionally, custom scripts are often not written in an easily understood manner. In this session we will walk through specific DevOps workflows (such as install, update, etc) using Riemann as the framework in subject and see the steps required to automate those processes. We will also discuss how Cloudify uses Riemann to provide simple execution and monitoring of those workflow processes. We will share how one customer, PaddyPower, was able to leverage Cloudify to transition their traditional IT into a DevOps environment, bridging the gap betwe

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • A recent Gartner study projected that through 2015, “80 percent of outages impacting mission-critical services will be caused by people and process issues, and more than 50 percent of those outages will be caused by change, configuration, release integration, and handoff issues.[2].”
    (Ronni J. Colville and George Spafford, “Configuration Management for Virtual and Cloud Infrastructures”)


    83% of enterprises face significant roadblocks that hold them back from moving beyond cost reduction to faster time-to-market and better orchestration of their businesses. Respondents mentioned that politics, budget, time and staff are the main sources of roadblocks to getting more value out of their cloud computing investments. The majority of these roadblocks are not related to IT.  They include lack of clarity regarding organization and budget (37%), resistance to change (16%) and lack of trust (visibility and reliability) (15%).  The following graphic illustrates the enterprise cloud journey as defined in TheInfoPro Wave 5 Cloud Computing Study.
  • Is Orchestration the Next Big Thing in DevOps

    1. 1. Is Orchestration the Next Big Thing in DevOps? Nati Shalom CTO & Founder GigaSpaces @natishalom
    2. 2. DevOps Through the Car Industry Analogy
    3. 3. The Biggest Revolution? Gasoline Engine Sports Car Model T Assembly Line
    4. 4. “You can choose any color you want as long as its black...” - Henry Ford
    5. 5. Transformed the Entire Industry • Automobile enters the mass market • 10x more cars a day • 4 months pay to buy a car
    6. 6. How is this Relevant to DevOps?
    7. 7. DevOps is the Industrialization of IT IT Pre DevOps IT Post DevOps
    8. 8. DevOps is all about... • Releasing new features and products faster and at scale • 1000s of updates per day is typical
    9. 9. What’s Changed? It seems like everything BUT the kitchen sink is software defined these days. You were saying? Everything is Software Defined
    10. 10. We Can Automate Everything Configuration Networking Compute
    11. 11. The Missing Piece in the Puzzle The Missing Piece In the Puzzle?The Missing Piece in the Puzzle…
    12. 12. Software Defined Operator
    13. 13. Human vs Software Operator • Human Operator • Software Operator Input: DSL Execute: API Input: Email, Docs Execute: GUI, CLI Control: Policy Engine Control: Monitoring, SMS
    14. 14. The Impact of Human Error 14 80% of outages impacting mission-critical services will be caused by people and process issues 50% of those outages will be caused by change/configuration/release integration and hand-off issues
    15. 15. Orchestration = Software Operation
    16. 16. Typical Orchestration Model
    17. 17. TOSCA: A Standard Blueprint
    18. 18. Apache Server DB Server NodeJS NodeCeller MongoDB TOSCA-like Example • App Network • App Subnet • App Port • Security Group • Apache Floating IP • Router Gateway • Data Network • Data Subnet • Data Port • Security Group Router Monitoring, Logging CI
    19. 19. Network View
    20. 20. Topology View
    21. 21. TOSCA-like Blueprint
    22. 22. Real Life Example (HP Print) • 30 HP Helion Public Cloud accounts • 500+compute instances • 1400 Peak deployments per day • 100+compute instances per management cluster • 100xdevelopers doing deployments in a consistent fashion • <2HMove from HP Helion Public Cloud tenant to a fully provisioned and deployed service
    23. 23. Orchestrating Networks and Apps
    24. 24. Send Metrics Execute Policy Feedback Correlate with Historical Events Real Time Analytics Deploy Fail- over Scale Real Time Analytics Cloud Infrastructure Intelligent Orchestration Next: Intelligent Orchestration 11111111111 Historical Data 000000000 11111111111 000000000 11111111111 000000000
    25. 25. Does this Mark the End of IT Operations?
    26. 26. Ops in a DevOps World Apps & Ops speaks the same language Ops can deliver real value – ensuring that SLAs are met More control Over the Environment
    27. 27. The Demand For DevOps..
    28. 28. Orchestration Is the Next Big Thing
    29. 29. • Code Example • TOSCA-like Example
    30. 30. Thank You Nati Shalom @natishalom