DevOps 101 - an Introduction to DevOps
Download as PPTX, PDF6 likes6,500 views
The document outlines the principles and practices of DevOps, including its history, definitions, and the 'CALMS' model (Culture, Automation, Lean, Measurement, Sharing). It emphasizes the importance of collaboration between development and operations teams, continuous delivery, and various automation techniques. Additionally, it highlights key practices and steps for implementing DevOps, as well as performance indicators for measuring success.
![26
Configuration as Code
package "apache2" do
case node[:platform]
when "centos","redhat","fedora","suse"
package_name "httpd"
when "debian","ubuntu"
package_name "apache2"
when "arch"
package_name "apache"
end
action :install
end](https://image.slidesharecdn.com/devops101-anintroductiontodevops-170127122138/85/DevOps-101-an-Introduction-to-DevOps-25-320.jpg)
DevOps 101 - an Introduction to DevOps
- 1. www.devopsguys.com | Phone: 0800 368 7378 | e-mail: [email protected] | 2016
- 2. 3 Introductions James Betteley DevOps Evangelist & Coach. DevOps Transformation
- 3. 4 Agenda Introductions (done!) DevOps History DevOps Defined Why DevOps Happened DevOps Principles DevOps Practices How do we do DevOps? DevOps KPIs
- 4. 5 DevOps History Lesson • 2008 Patrick Dubois is a consultant working on a DC migration project for the Belgian government • 2008 Agile Systems Administration group formed by Dubois and Andrew Shafer • 2009 Velocity ‘09 – John Allspaw & Paul Hammond give talk on 10+ Deploys a day at Flickr • 2009 First DevOpsDays conference • 2010 First DevOpsDays US • 2013 DevOps defined (sort of) as “an intimate understanding between the development and operations teams”
- 5. 6 DevOps Defined Sysadmins who code Recruiters Optimised value delivery DevOpsGuys Automation DevOps Engineers
- 6. 7 The DevOps “calms” model • Culture • Automation • Lean • Measurement • Sharing
- 7. Continuous Delivery + Operability = DevOps
- 9. 10 why did DevOps happen?
- 10. 11 why did DevOps happen? “How do we keep up with the demand for new features and new technologies while maintaining stability and high performance?” We tried to answer this question:
- 11. 12 Why did DevOps happen? “How do we deliver maximum value to our customers and shareholders?” It was the wrong question
- 12. The first ingredient of DevOps: Shared Goals
- 14. 15 The DevOps “calms” model • Culture • Automation • Lean • Measurement • Sharing
- 15. 16 The DevOps “calms” model • Create a culture of collaboration and ownership. • Start small and scale out, not up.
- 16. 17 The DevOps “calms” model • Fast feedback through automation. • We need information to guide our decisions
- 17. 18 The DevOps “calms” model • Lean approach to system’s thinking • Localised optimisations are a mirage • Being busy != being valuable
- 18. 19 The DevOps “calms” model • Measure the right things • Be empirical, let the stats guide you. • Beware of the cultural impact
- 19. 20 The DevOps “calms” model • Share goals to create a common purpose • Share experiences to encourage learning
- 20. 21 Gene Kim’s “3 Ways” of DevOps
- 21. 22 Gene Kim’s “3 Ways” of DevOps
- 22. 23 Gene Kim’s “3 Ways” of DevOps
- 23. DevOps Practices
- 24. 25 Infrastructure as Code workflow CreateWebVM { InlineScript { "Creating VM $($Using:VMName)" Select-AzureSubscription $Using:SubscriptionName $VM = New-AzureVMConfig -Name $Using:VMName ` -InstanceSize "ExtraSmall" ` -ImageName $Using:imageName ` -AvailabilitySetName $Using:availgroup $VMConfig = Add-AzureProvisioningConfig -Linux ` -VM $VM ` -LinuxUser $Using:username ` -SSHKeyPairs $Using:sshkey ` -password $Using:password New-AzureVM -ServiceName $Using:CloudService.ServiceName -VM $VMConfig } } Declarative Reusable Automated Testable
- 25. 26 Configuration as Code package "apache2" do case node[:platform] when "centos","redhat","fedora","suse" package_name "httpd" when "debian","ubuntu" package_name "apache2" when "arch" package_name "apache" end action :install end
- 27. 28 Test-driven • As a lazy ops guy I want an Ansible role that will install Apache on an Ubuntu Server So that I can host the best website ever • Additional notes: • Install whatever the latest version of Apache is, we're a bleeding edge company • Must work on Ubuntu 14.04 (current) and 15.04 (future rollout) • The external load balancer will route incoming http requests to port 55555 on all machines • The NSA wants their own root account on all our environments • Please remove telnet for maximum security
- 28. 29 Test-driven require 'spec_helper' describe package('apache2') do it { should be_installed } end describe service('apache2') do it { should be_running } end describe port(55555) do it { should be_listening } end describe user('NSA') do it { should exist } it { should belong_to_group('root') } end
- 29. 30 Continuous Delivery • “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software”
- 30. 31 Microservices
- 32. 33 Continuous Delivery – 8 principles 1. The process for releasing/deploying software MUST be repeatable and reliable 2. Automate everything! 3. If somethings difficult or painful, do it more often 4. Keep everything in source control 5. Done means “released” 6. Build quality in! 7. Everybody has responsibility for the release process 8. Improve continuously
- 33. 34 Continuous Delivery – 4 practices 1. Build binaries only once 2. Use precisely the same mechanism to deploy to every environment 3. Smoke test your deployment 4. If anything fails, stop the line!
- 34. 35 Tooling
- 35. DevOps Applied How Do Organisations do DevOps?
- 36. 37 What do these organisations have in common?
- 37. 38 5 Steps to Doing DevOps 1. Establish your goals 1. What does DevOps mean to the team? 2. Build the platform 1. Environments 2. Continuous Delivery 3. Test Automation 3. Assemble the team 4. Be agile, not waterfall 5. Work together to achieve great things 1. Autonomy, mastery & purpose
- 38. 39 How to change an organisation’s culture
- 39. DevOps Topologies How Organisations organise their organisations
- 44. DevOps Solutions DevOps Coaching Workshops & Training DevOps Engineering Application Lifecyle Automation DevOps Consultancy DevOps, Agile & Cloud Strategy ccelerateducate ransform
- 48. Questions?
- 49. 50 50 www.devopsguys.com Phone: 0800 368 7378 | e-mail: [email protected] CONTACTS Redgate Database DevOps Team [email protected] DevOpsGuys [email protected]
Editor's Notes
- #4: Why do I do what I do? Learning objectives: What are you hoping to learn from this session?
- #7: On the Dev side of the business: Development, Sales, Marketing, Business Analysis, Product Management On the Ops side we have: DBAs, Inf, Networks, support. Amazon: DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity:
- #8: Just use this slide to underline the fact that Automation is only 1 component part of DevOps
- #9: In terms of practical application…
- #12: We wanted a high rate of change, and high stability. We probably didn’t explicitly give these objectives to different departments, but we didn’t do enough from stopping those silo’s being built. We ended up with Dev = change and Ops = stability We had 2 competing goals
- #14: Gene Kim calls this “system’s thinking” in his “3 ways of devops” but we’ve been using shared goals for ages.
- #19: Flow game!!!! Paper planes.
- #23: Feedback loops game
- #28: Piss easy to provision, configure and scale
- #30: Here’s a little serverspec script to test our configuration!
- #32: Separate your services Decoupled components
- #38: They all do DevOps differently
- #39: Agree what your goals are, what problems you’re trying to solve, and what DevOps means to you (is it just automation or is it a mindset?). You all need to be on the same page before you start, otherwise you’ll misunderstand each other, and without knowing your goals, you won’t know why you’re doing what you’re doing. Build the platform. DevOps relies heavily on fast feedback loops, so you need to enable them before you go any further. This means putting in place the foundations of a highly automated Continuous Delivery platform – from requirements management though to branching strategy, CI, test automation and environment automation. Don’t try to create an enterprise-scale solution, just start small and do what you need to do to support 1 team, or this thing will never get off the ground. You’ll probably need to pull together a bunch of DevOps engineers to set this platform up – this is often how “DevOps teams” come about, but try to remember that this team should be a transitional phase, or at least vastly scaled down later on. Assemble the team. We’re talking about a cross-functional delivery team here. This team will include all the skills to design, build, test, deliver and support the product, so we’re looking at a Product Owner, Business Analyst, Developers, Testers, and Infrastructure Engineers among others (it largely depends on your product – it may need to be extended to include UX designers, Security and so on). Be agile, not waterfall. Waterfall’s just not going to work here I’m afraid. We’re going to need a framework that supports much faster feedback and encourages far greater collaboration at all times. So with that in mind, adopt a suitable agile framework like scrum or Kanban, but tailor it appropriately so that the “Ops” perspective isn’t left out. For example – your “definition of done” should stretch to include operability features. “Done” can no longer simply mean “passed UAT”, it now needs to mean “Deployable, monitorable and working in Pre-Live” at the very minimum. Another example: Your product backlog doesn’t just contain product functionality, it needs to include operability features too, such as scalability, maintainability, monitoring and alerting. Work together to achieve great things. Let the delivery team form a strong identity, and empower them to take full ownership of the product. The team needs autonomy, mastery and purpose to fully unlock its potential.
- #40: No such thing as a single organisational culture An organisation’s culture is a blend of several subcultures
- #42: See Netflix and Facebook as examples of cross functional product delivery teams Amazon are like this too – you build it, you run it.
- #43: Spotify – Squads are cross-functional delivery teams, basically
- #44: Google Asos
- #47: What are some good DevOps KPIs?