Ignites of Day 1 @ DevOpsDays Singapore 2015

- Sustainable Innovation - the Business Mantra for DevOps in Enterprise (Anoop Kumar Bhat)
- The Power of Personal Influence (Kimble Ngo)
- Agile: Break it down (Yue Lin Choong)
- #noprojects (Evan Leybourn)
- Crawl before you Run, Implementing DevOps (Jason Man)
- Automated Docker Image Builds with Jenkins, Packer, and Kubernetes (Oyvind Roti)

Transcript

3. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 1 Sustainable Innovation - the Business Mantra for DevOps in Enterprise Anoop Kumar Bhat Portfolio and Strategy Sales Director, Hewlett Packard, Asia Pacific & Japan anoop.bhat@hp.com https://sg.linkedin.com/in/anoop4bhat @AnoopKumarBhat
4. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 2 What do these applications have in common? Open Contextual Secure Fresh Low cost Reliable Sexy Social Fun Omnichannel *simple bank
5. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 3 How can we get the same level of agility & speed inside a company ?
6. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 4 What’s up on the cloud front ? Speed up provisioning Speed up release management Scale-Out Elastic Cluster Virtualized Silo Physical For the past 5 years automation approach has been cloud alpha & omega ( automate known operations, provisioning & processes, to increase speed & agility and lower the TCO) Application rules the game. It’s all about rethinking application architecture to build Cloud aware stuff. That implies a new Yalta between Ops & Apps and shake even more the 3 P’s Speed up provisioning Speed up release management Bridge the two worlds together
7. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 5 Build application in the cloud era My customers are networked. They are governed by their left brain and their watches My applications are a library of aggregated micro-services that transforms data into informations in a context They must be motivational Be ready to support any charge Be updated very frequently or die Permanently seeking for applications that makes their life easier They connect (de 1 à 10n) anytime They expect a continuous flow of new features
8. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 6 Application architecture patterns Compose services to build application Data management is ditributed as much as the services Synchronous replication is limited Fronts & App servers molecules are built from atomic components. Database is centralized and secured using clustering mechanisms. Data access and scalability could be challenging Release management can and should be automated in a traditional multi tiered application Everything is instrumented Auto-scaling elastic pool of resources Data fabric Cloud based object storage Cloud based file storage Services Services Services Elastic load balancer Zero affinity of workload to server Cloud native app Fixed storage Presentation tier Load balancer App tier Fixed data Fixed affinity of workload to server Traditional multi-tiered application Hybrid application
9. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 7 Applications are complex … Increasingly complex...
10. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Shift in priorities is demanding DevOps 8 Shift from Silos to collaboration to accelerate release velocity Integrated Team ! - Shared Customer-oriented Goals - Shared Objectives - Shared Responsibility Test Dev QA Staging & Production Dev Ops Development Quality Assurance Agile Iterations 0 1 2 3 4 Dev +Test Staging & Production Ops Before DevOps After DevOps Dev Ops Test
11. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 9 Building the Talent Equity is Key Talent Equity: is the wealth of knowledge within the Cloud100 team and Cloud BU given the diverse range of talents from different background, skillset and diversity. Why is it important? Cloud100 Talent Pool Be able to address both Traditional and Cloud Native 1 Diversity in viewpoint leads to better innovation 2 Instant access to Competitive attack knowledge 3 Mixed skillet leads to learning from each other 4 Leads to better Pan-HP and Pan-Industry Collaboration 5
12. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 10 Driving a Common Culture within teams Excellence in Strategy and Execution Passion
13. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 11 Offer an opportunity to achieve innovation- oriented goals with limited resources More encouraging of creativity and challenge orientated Develop apps that benefit the society and community A fun and effective way of getting the talent together and solving issues Examples C3: Platform of Hackathon GIDS CodeWar CodeWars Create Talent Pipelining Strategies Contribute Society Crack Business Problem Promote Innovation Driving Innovation with Hackathons for Customers United Nations Women Hackathon
14. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 12 What is Dev Ops to HP IT? DevOps … is a movement, a philosophy, a way of thinking. DevOps … is a person who can perform both Dev and Ops roles. DevOps … means cross skilling people. DevOps … is continuous delivery. DevOps … is a virtual “team” of developers and operation staff. DevOps … is a culture movement. DevOps … is monitoring DevOps is a verb. It’s not something you build it’s something you do
15. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Pain Chain – DevOps VP of Apps QA VP of Ops The Business We need to innovate Need to deliver faster/on-time Our customers are unhappy We are struggling to increase pace of delivery (50% projects late) We are releasing too many defects (20% defects leaked) We cannot risk frequent changes to production (50% releases rollbacked) The Customer
16. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 14 There is more than just application source code DevOps: a system wide approach • We consider the entire system, not just the application source code • System must also include business requirements, security • The entire system goes under development, functional testing, performance testing, staging, UAT and production • Everything in the system is “code” Application Code Network Middleware & storage Data
17. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 15 Some DevOps-y concepts for HP IT A VP can fix a typo in production A simple and riskless change should be easy to move to production. This is a test that is often used to prove that a proper continuous delivery system is in place: identify a problem, update the code, save it, run tests automatically, deploy if approved and tests succeeded. #1
18. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 16 Machines are "short-running" Machines do not need to be maintained over time (patched, upgraded, …). Instead, they are built on demand and join the application farm automatically #2 Some DevOps-y concepts for HP IT
19. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 17 Monitor business impact of the changes The "feedback loop" (monitoring) must monitor the actual impact of the changes for the customers – not only basic vitals (CPU, MEM, IO) and send back this information to developers. Such as: - Conversion rate (from basket to payment) - Number of test execution per hour - … #3 Some DevOps-y concepts for HP IT
20. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 18 Netflix's "Chaos Monkey" A program that randomly kills instances and services throughout the Netflix production architecture #4 Some DevOps-y concepts for HP IT
21. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 19 Select a few HP IT applications to transform HP IT “Unicorns" Instead of trying to fix all of HP IT, let's find the applications where DevOps matters most ("Unicorn project") • Criteria • Willing to change and collaborate between development and operations • Agile project management preferred • Needs to get better at deploying changes, need to push smaller and more frequent changes, decrease change rollout time, increase change reliability • Preferably using HP IT SDLC standards to start from a known landscape and be used as showcase within HP IT • Executive sponsorship
22. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 20 Change our Thinking….Build a better World…. anoop.bhat@hp.com https://sg.linkedin.com/in/anoop4bhat @AnoopKumarBhat Thank You!!!
29. ONLINE ME
33. I’ll be there in 5 min. If not, check this message again Hey… we said 5pm…where are you?
43. Kimble@Amplify-Influence.com www.KimbleNgo.com
45. Break it down
51. Myth?
52. Fact
66. © 2015 IBM Corporation IBM Global Business Services © 2015 IBM Corporation If you need to run a project – you’ve already failed #noprojects delivery Evan Leybourn – Agile Consultant October, 2015
67. © 2015 IBM Corporation IBM Global Business Services What is a project - a common definition? A temporary structure to govern and deliver a complex change (such as a new product or platform) 2
68. © 2015 IBM Corporation IBM Global Business Services The alternative – continuous change? #noprojects is the approach, structure, and techniques to successfully deliver continuous change without a project 3
69. © 2015 IBM Corporation IBM Global Business Services What is #noprojects? 1. The alignment of activities to outcomes 2. measured by value, 3. constrained by guiding principles and 4. supported by continuous delivery technologies 4
70. © 2015 IBM Corporation IBM Global Business Services Why #noprojects  Products don’t end when the project does  Projects fail with alarming regularity  Projects lose subject matter expertise 5
71. © 2015 IBM Corporation IBM Global Business Services Projects are expensive The three O’s of project cost; 1. Overheads, 2. Overruns and 3. Opportunity costs 6
72. © 2015 IBM Corporation IBM Global Business Services Outcomes not outputs Outcomes are valuable (direct or indirect), planned, slowly changing and define the common direction for the organisation 7
73. © 2015 IBM Corporation IBM Global Business Services Outcome profile 8
74. © 2015 IBM Corporation IBM Global Business Services Value delivery teams Dedicated cross-functional teams that are structured to contain the necessary skills required to deliver an outcome (e.g. developers, testers, HR, accountants, sales/marketing) 9
75. © 2015 IBM Corporation IBM Global Business Services Value delivery teams Do not mistake this for a project team formed in a matrix organisation 10
76. © 2015 IBM Corporation IBM Global Business Services The activity canvas An activity is any discrete work that is undertaken as part of a change 11
77. © 2015 IBM Corporation IBM Global Business Services Activity canvas 12
78. © 2015 IBM Corporation IBM Global Business Services Activity canvas 13
79. © 2015 IBM Corporation IBM Global Business Services Activity canvas 14
80. © 2015 IBM Corporation IBM Global Business Services Measuring value 1. Value degrades 2. You don’t always work on the highest value activities first 3. Local Maxima 4. Activities fail 5. The “So What” Factor 15
81. © 2015 IBM Corporation IBM Global Business Services Measuring value 1. Value degrades 2. You don’t always work on the highest value activities first 3. Local Maxima 4. Activities fail 5. The “So What” Factor 16
82. © 2015 IBM Corporation IBM Global Business Services Measuring value 1. Value degrades 2. You don’t always work on the highest value activities first 3. Local Maxima 4. Activities fail 5. The “So What” Factor 17
83. © 2015 IBM Corporation IBM Global Business Services The technology of #noprojects 1. Automated testing 2. Continuous integration 3. Continuous delivery and automated rollback 4. DevOps 18
84. © 2015 IBM Corporation IBM Global Business Services There are always exceptions A project structure can provide a "clean break" for new ideas to flourish, but should be the exception – not the default 19
85. © 2015 IBM Corporation IBM Global Business Services Final Thoughts Everything is a change, treat it accordingly. Evan Leybourn @eleybourn leybourn@sg.ibm.com Or connect with me on LinkedIn 20
87. Crawl before you Run, Implementing DevOps Jason Man
88. “As a result, Gartner, Inc. expects strong growth opportunities for DevOps toolsets, with the total for DevOps tools reaching $2.3 billion in 2015, up 21.1 percent from $1.9 billion in 2014. By 2016, DevOps will evolve from a niche strategy employed by large cloud providers to a mainstream strategy employed by 25 percent of Global 2000 organizations.”
90. DevOps =
91. People
92. Process
93. Tools
94. Start Small, think BIG
95. Mode 1 – Backporting DevOps
96. • Break down applications • Containerisation • Application Rewrite Mode 2 – Brave New World
97. Metrics
98. • Deployment (or Change) Frequency • Change Lead Time • Change Failure Rate • Mean Time To Recover (MTTR) DevOps Metrics
99. Continuous Integration • Hooks into SCM • Automated Build • Automated Tests • Nightly Builds
100. Continuous Delivery
101. Infrastructure Automation
102. Culture
103. Continuous Improvement
104. • People • Process • Tools • Identify Objectives. Start Small, think Big! • Mode 1 or Mode 2 or Both? • Identify Key Metrics • Benchmark Current State Recap
105. • Build from bottom up, “Join the Islands of Automation”. • Continuous Integration • Continuous Delivery • Infrastructure Automation • Cultural Transformation • Continuous Improvement Recap
106. Thank You Jason Man – jason@forest-technologies.co.uk @mrjasonman/ @foresttechltd
108. Automated Docker Image Builds with Jenkins, Packer, and Kubernetes
109. TL;DR - Why should you care? Reduce Boot Time Increase Reliability Reduce Dependency on 3rd Parties
110. TL;DR - Why should you care? Reduce Boot Time Increase Reliability Reduce Dependency on 3rd Parties … it's pretty cool and you get to play with awesome tech!
111. To mutate or not to mutate … that is the question Base OS Immutable Image Image
112. To mutate or not to mutate … that is the question Base OS Immutable Image Foundation Image? Image
113. Foundation Image Considerations • Installation Speed • Reliability of Remote Repository
114. Foundation Image Considerations • Installation Speed • Reliability of Remote Repository • Rate of Change • Required or Security Mandated
115. Immutable Image • Secrets? • Eliminates Config Drift
116. Immutable Image • Secrets? • Eliminates Config Drift • Even small changes require new image
117. Automated Image Builder Pipeline • Define job on Jenkins Leader • Job polls source repo for config scripts and Packer template
118. Automated Image Builder Pipeline • Define job on Jenkins Leader • Job polls source repo for config scripts and Packer template • Leader Assigns job to Build Agents running Packer
119. Some more details... • Swarm client registers build agent with Jenkins leader • Agent executes Packer build running provisioners (e.g. Docker and Google Compute)
120. Some more details... • Swarm client registers build agent with Jenkins leader • Agent executes Packer build running provisioners (e.g. Docker and Google Compute) • Docker post-processor tags creates Docker image • gcloud pushes image to Container Registry
121. Automated Image Builder Pipeline • Build Agents output Docker images to Container Registry and VM images to Compute Engine • Return Build Results to Jenkins Leader
122. The Jenkins view...
123. Containerized • Run the build system itself on Docker containers(!) • Use Kubernetes for OSS cluster scheduling and management
124. Containerized • Run the build system itself on Docker containers(!) • Use Kubernetes for OSS cluster scheduling and management • Replication Controller for HA
125. Automated Image Builder Pipeline • Jenkins • Packer • Docker • Kubernetes • Container Registry • Cloud Compute • Cloud Storage • Nginx
126. TL;DR - Why should you care? Reduce Boot Time Increase Reliability Reduce Dependency on 3rd Parties
127. Thanks! QR Link to the solution and GitHub repo Questions? roti [at] google [dot] com Credit to Evan Brown for putting together this solution!