Ad
More Related Content
What's hot (20)
Similar to DevOps Torino Meetup Group Kickoff Meeting - Why a meetup group on DevOps, what does it mean DevOps (20)
Ad
More from Rauno De Pasquale (12)
Ad
Recently uploaded (20)
DevOps Torino Meetup Group Kickoff Meeting - Why a meetup group on DevOps, what does it mean DevOps
- 1. GROUP KICKOFF Torino DevOps Meetup
- 2. ABOUT US ➤ Rauno De Pasquale, Co-Founder and CTO at Newesis Srl, constantly trying to reconcile his degree in Philosophy with a passion for computer science. After almost 18 year at Deltatre, at the beginning of 2019 he creates Newesis, with the aim of simplifying the use of the most advanced services of Cloud platforms even in fields other than sports. ➤ Samuele Camatari, Founder and CEO of Jusan Network Srl, Co-Founder and CEO at Newesis Srl, an eclectic manager with more than 25 years experience in the Information Technology industry. Between the most influential voice in the Italian e-commerce ecosystem, he has made technology and networking his reason for living. ➤ Newesis is a pure technology based, Cloud Native company, having as a target to support and evolve adoption of DevOps culture and practices, with particular focus on Kubernetes as technological platform. ➤ Twitter: @RaunoDepa ➤ Twitter: @CamatariSamuele ➤ Twitter: @newesissrl
- 3. WHY A NEW MEETUP GROUP➤ Turin has multiple Meetup Groups related to technologies in many of these groups DevOps practices are mentioned in some form ➤ CNCF Turin ➤ Agile Community Torino ➤ Google Cloud Developer Community Torino ➤ AWS User Group ➤ Meetup Microsoft Azure Torino ➤ Turin Web Performance Group ➤ DevOps is a hot topic but there is not a commonly agreed definition about the term ➤ We have not found any existing group having a specific focus on DevOps and on how to define it as a cultural approach
- 4. GROUP PURPOSE ➤ Create and evolve a common definition of what does DevOps mean ➤ Demystify common misconceptions about DevOps ➤ Identify patterns and anti-pattern on DevOps adoption ➤ Share lessons learnt about DevOps adoption processes ➤ Identify best practices for DevOps adoption ➤ Share real life experience on DevOps processes in different working environments ➤ Learn about DevOps tools and practices from practical example ➤ Define a common set of tools and practices to select from in our daily work ➤ Share information about training and events related to the world of DevOps
- 6. DEVOPS – A DEFINITION DevOps is a set of practices that automates the processes between software development and IT teams, in order that they can build, test, and release software faster and more reliably. The concept of DevOps is founded on building a culture of collaboration between teams that historically functioned in relative siloes. The promised benefits include increased trust, faster software releases, ability to solve critical issues quickly, and better manage unplanned work. Atlassian
- 7. DEVOPS – A DEFINITION The combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. This speed enables organizations to better serve their customers and compete more effectively in the market.Amazon
- 8. DEVOPS – A DEFINITION DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. DevOps is not just automating a pipeline so we can quickly deliver software. Our goal is to deliver value. It is very important to realize that DevOps is not a product. You cannot buy DevOps and install it. DevOps is not just automation or infrastructure as code. DevOps is people following a process enabled by products to deliver value to our end users. Donovan Brown – Principal DevOps Manager at Microsoft
- 9. THE RAISE OF DEVOPS ➤ At the 2008 Agile Toronto conference, Patrick Dubois and Andrew Schafer held a session on applying Agile principles to infrastructure as opposed to application code. ➤ Velocity 2009 conference, John Allspaw and Paul Hammond gave the seminal “10 Deploys per Day: Dev and Ops Cooperation at Flickr.” ➤ Patrick Dubois created the first DevOpsDays in Ghent, Belgium, in 2009, coining the word “DevOps.” ➤ in 2009 at another O’Reilly conference, Velocity, Andrew Clay Shafer gave a presentation on Agile Infrastructure, showing the iconic picture of a wall between developers and operations with a metaphorical depiction of work being thrown over the wall. ➤ In March of 2011, Cameron Haight of Gartner presented his predictions for the trajectory of DevOps over the next few years, creating interest in DevOps movement by enterprises. ➤ In 2012, the State of DevOps report was conceived and launched by Alanna Brown at Puppet.
- 10. 1. DevOps is Only for Startups 2. DevOps Replaces Agile 3. DevOps is Incompatible with ITIL 4. DevOps is Incompatible with Information Security and Compliance 5. DevOps Means Eliminating IT Operations, or “NoOps” 6. DevOps is Just “Infrastructure as Code” or Automation 7. DevOps is Only for Open Source Software 8. DevOps cross functional teams mean to increase costs because you need more people FALSE MYTHS
- 11. • Culture • “When asked what the most difficult thing about adopting DevOps is, I reply — without hesitation — the people” (Donovan Brown). People and process first. If you don’t have culture, all automation attempts will be fruitless. • Automation • The full independency and responsibility of the team for the delivery of value to the end user is a fundamental principle of DevOps. Automation is key not only to allow faster iterations but specifically to make the process repeatable independently from the presence of a certain person or group of people. • Measurement • The continuous improvement process (Kaizen) is at the heart of DevOps. If you can’t measure, you can’t improve. A successful Devops implementation will measure everything it can as often as it can. • Sharing • The transfer of knowledge aims to avoid constraints in the organization, and to promote the collective intelligence. Visibility makes it possible to know if the work of a team can introduce a problem to another team and it also allows for early feedback. Transparency is what allows everyone to work towards a common goal. DEVOPS PRINCIPLES - CAMS
- 12. THE THREE WAYS System Thinking: the principles of Flow, which accelerate the delivery of work from Development to Operations to our customers, emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department. Feedback Loops: the principles of Feedback, which enable us to create ever safer systems of work, creating the right to left feedback loops. Culture of Experimentation: the principles of Continual Learning and Experimentation, which foster a high-trust culture and a scientific approach to organizational improvement risk- taking as part of our daily work
- 13. Agile Software Development – faster iteration Microservices Architecture – increasing complexity Cloud Platforms – increasing scale Containers, Serverless – increasing abstraction WHY DEVOPS – THE CONTEXT
- 14. “I need a server… now” “I want access to the production systems” “The application won’t run on our infrastructure because we don’t support that version” “The architecture of the application doesn’t match our security model” “We can not work on that task because we need xyz who is currently busy working late at night” (the “hero” syndrome) “We weren’t consulted about the backup requirement so it can not be move to production” “It’s not our fault, our code is perfect, it works on my machine” “Why can’t they implement that technology? Why are they so backward?” WHY DEVOPS - DEV VS OPS
- 15. Common mistake is to think DevOps as “Dev does Ops” or as “Ops does Dev”. Dev and Ops have different skillsets and knowledge that must be combined to get values for the end users. Sysadmins have the ability to transition to a DevOps team, as long as they are willing to learn current and emerging technologies, and are open to innovative ideas and solutions. Developers have the ability to transition to a DevOps team, as long as they are willing to consider reliability and operability as part of their duties, and are open to innovative ideas and solutions. DEV DOES OPS - OPS DOES DEV
- 16. “DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support.” (Jez Humble) “DevOps is about Ops who think like devs. Devs who think like ops.” (John Allspaw) Development teams need to embed operations people into their project and development life cycles. Operations people need to bring development people into the problem and change management space. “DevOps is also characterized by operations staff making use many of the same techniques as developers for their systems work.” (Jez Humble) DEVOPS IS DEV + OPS
- 17. Is SRE an alternative to DevOps? Google creates and evolved the concept independently from DevOps movement. «If you think of DevOps like an interface in a programming language, class SRE implements DevOps. SRE includes additional practices and recommendations that are not necessarily part of the DevOps interface. DevOps and SRE are not two competing methods for software development and operations, but rather close friends designed to break down organizational barriers to deliver better software faster. DevOps emerged as a culture and a set of practices that aims to reduce the gaps between software development and software operation. The DevOps movement does not explicitly define how to succeed. SRE prescribes how to succeed in the various DevOps areas.” (Liz Fong-Jones, Seth Vargo) DEVOPS VS SRE (SITE RELIABILITY ENGINEERING)
- 18. DEVOPS MANIFESTO – SRE MANIFESTO
- 19. WHAT IS YOUR DEFINITION OF DEVOPS?
- 20. REFERENCES - BOOKS ➤ The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win (Gene Kim , Kevin Behr, George Spafford) ➤ The Devops Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations (Gene Kim, Jez Humble, Patrick Debois, John Willis, John Allspaw) ➤ Site Reliability Engineering: How Google Runs Production Systems (Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Richard Murphy) ➤ The Site Reliability: Practical Ways to Implement SRE (Betsy Beyer, Niall Richard Murphy, David K. Rensin, Kent Kawahara, Stephen Thorne) ➤ The Practice of Cloud System Administration: Designing and Operating Large Distributed Systems, Volume 2 (Thomas A. Limoncelli, Strata R. Chalup, Christina J. Hogan) ➤ Release It! Design and Deploy Production-Ready Software (Michael T. Nygard) ➤ Accelerate: The Science Behind Devops: Building and Scaling High Performing Technology Organizations (Nicole Forsgren, Jez Humble, Gene Kim) ➤ What is DevOps? (Mike Loukides) ➤ The DevOps Adoption Playbook: A Guide to Adopting DevOps in a Multi-Speed IT Enterprise (Sanjeev Sharma)
- 21. REFERENCES - WEB ➤ State of DevOps Puppet - https://puppet.com/resources/report/state-of- devops-report/ ➤ DevOps Team Topologies - https://web.devopstopologies.com/ ➤ Microsoft DevOps Resource Center - https://docs.microsoft.com/en- us/azure/devops/learn/ ➤ DevOps Fundamentals - https://medium.com/faun/all-about-devops- fundamentalsyou-ever-wanted-to-know-2333328a2b40 ➤ Donovan Brown Definition of DevOps - https://medium.com/@DonovanBrown_41367/dissecting-the-definition- 69151da0435f ➤ Agile and DevOps - https://www.atlassian.com/agile/devops ➤ Agile and DevOps – https://theagileadmin.com/what-is-devops/ ➤ CAMS - https://blog.chef.io/what-devops-means-to-me/ ➤ What is DevOps - https://www.kartar.net/2010/02/what-devops-means-to- me/ ➤ AWS definition of DevOps - https://aws.amazon.com/devops/what-is- devops/ ➤ Four Principles of DevOps - http://radify.io/blog/four-principles-of-devops/ ➤ DevOps vs SysAdmin - https://opensource.com/article/19/7/devops-vs- sysadmin ➤ What DevOps is not - https://agileweboperations.com/2010/12/02/what- devops-is-not/
- 22. REFERENCES – VIDEO ➤ How Netflix Thinks of DevOps - https://www.youtube.com/watch?v=UTKIT6STSVM ➤ What's the Difference Between DevOps and SRE? (class SRE implements DevOps) - https://www.youtube.com/watch?v=uTEL8Ff1Zvk ➤ What is DevOps? In Simple English - https://www.youtube.com/watch?v=_I94-tJlovg ➤ DevOps Culture at Amazon - https://www.youtube.com/watch?v=mBU3AJ3j1rg ➤ What is DevOps (DevOps 101 from IBM)- https://www.youtube.com/watch?v=UbtB4sMaaNM&list=PLOsp HqNVtKAAm1dmyiR9WMmw1UBoOwZVj ➤ #ChefConf 2014: Jez Humble, "DevOps Culture and Practices To Create Flow” - https://www.youtube.com/watch?v=oX8af9kLhlk ➤ Spotify Engineering Culture (by Henrik Kniberg) - https://www.youtube.com/watch?v=4GK1NDTWbkY ➤ DevOps Vs. SRE: Competing Standards or Friends? (Cloud Next ‘19) - https://www.youtube.com/watch?v=0UyrVqBoCAU&t=1s