Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

DevOps 101 - an Introduction to DevOps

1.342 visualizaciones

Publicado el

DevOps is an increasingly useful tool for achieving business objectives, enabling your teams to work together to improve the efficiency and quality of software delivery. However, despite its growing popularity, there is still a lack of clarity over what DevOps actually means, how organizations should do it and what's the best way to get started.

DevOps 101 takes a brief look at the history of DevOps, why it started, what problems it is intended to solve and how you can start implementing it.

The slides were delivered by James Betteley, Head of Education at the DevOpsGuys in a one-hour webinar. The full recording is available here - https://youtu.be/4gC3WpbetKs?t=2s

James has spent the last few years neck-deep in the world of DevOps transformation, helping a wide range of organizations optimize the way they collaborate to deliver better software, faster. James was joined by Elizabeth Ayer, Portfolio Manager, from Redgate Software. Elizabeth looks after a range of Redgate products that help teams extend their DevOps practices to SQL Server databases.

For more information visit www.devopsguys.com and www.red-gate.com

Publicado en: Software
  • Sé el primero en comentar

DevOps 101 - an Introduction to DevOps

  1. 1. www.devopsguys.com | Phone: 0800 368 7378 | e-mail: team@devopsguys.com | 2016
  2. 2. 3 Introductions James Betteley DevOps Evangelist & Coach. DevOps Transformation
  3. 3. 4 Agenda Introductions (done!) DevOps History DevOps Defined Why DevOps Happened DevOps Principles DevOps Practices How do we do DevOps? DevOps KPIs
  4. 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. 5. 6 DevOps Defined Sysadmins who code Recruiters Optimised value delivery DevOpsGuys Automation DevOps Engineers
  6. 6. 7 The DevOps “calms” model • Culture • Automation • Lean • Measurement • Sharing
  7. 7. Continuous Delivery + Operability = DevOps
  8. 8. OPERABILITYScalability Deployability Resilience Monitoring Alerting Disaster Recovery Supportability Maintainability
  9. 9. 10 why did DevOps happen?
  10. 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. 11. 12 Why did DevOps happen? “How do we deliver maximum value to our customers and shareholders?” It was the wrong question 
  12. 12. The first ingredient of DevOps: Shared Goals
  13. 13. DevOps Principles
  14. 14. 15 The DevOps “calms” model • Culture • Automation • Lean • Measurement • Sharing
  15. 15. 16 The DevOps “calms” model • Create a culture of collaboration and ownership. • Start small and scale out, not up.
  16. 16. 17 The DevOps “calms” model • Fast feedback through automation. • We need information to guide our decisions
  17. 17. 18 The DevOps “calms” model • Lean approach to system’s thinking • Localised optimisations are a mirage • Being busy != being valuable
  18. 18. 19 The DevOps “calms” model • Measure the right things • Be empirical, let the stats guide you. • Beware of the cultural impact
  19. 19. 20 The DevOps “calms” model • Share goals to create a common purpose • Share experiences to encourage learning
  20. 20. 21 Gene Kim’s “3 Ways” of DevOps
  21. 21. 22 Gene Kim’s “3 Ways” of DevOps
  22. 22. 23 Gene Kim’s “3 Ways” of DevOps
  23. 23. DevOps Practices
  24. 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. 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
  26. 26. 27 Cloud “The Cloud” Innovative Accessible Cheap Scalable Configurable Fast Visible Automated!
  27. 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. 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. 29. 30 Continuous Delivery • “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software”
  30. 30. 31 Microservices
  31. 31. 32 Continuous Delivery
  32. 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. 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. 34. 35 Tooling
  35. 35. DevOps Applied How Do Organisations do DevOps?
  36. 36. 37 What do these organisations have in common?
  37. 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. 38. 39 How to change an organisation’s culture
  39. 39. DevOps Topologies How Organisations organise their organisations
  40. 40. DevOps Solutions DevOps Coaching Workshops & Training DevOps Engineering Application Lifecyle Automation DevOps Consultancy DevOps, Agile & Cloud Strategy ccelerateducate ransform
  41. 41. Measuring Success
  42. 42. 47 Key Performance Indicators
  43. 43. 48 Further reading
  44. 44. Questions?
  45. 45. 50 50 www.devopsguys.com Phone: 0800 368 7378 | e-mail: team@devopsguys.com CONTACTS Redgate Database DevOps Team databasedevops@red-gate.com DevOpsGuys team@devopsguys.com

×