DevOps requires agility. The document discusses how DevOps involves operations and development engineers working together throughout the entire service lifecycle. It provides the example of Etsy, which deployed code to production an average of 32-50 times per day. Continuous integration is presented as a way to integrate changes frequently in order to detect issues early. The key aspects of continuous integration discussed are having a CI server that rebuilds and runs tests on every commit, as well as activities like unit testing, code analysis, reporting and visualization.
The Journey of devops and continuous delivery in a Large Financial InstitutionKris Buytaert
The Journey of devops and continuous deliverey in a Large Financial Institution,
as presented by @markheistek and myselve at Velocity Conf 2013, Longon
Devops Management is a topic discussed in the halls of conferences and few managers. This talk will focus on the topic of management in a highly collaborative and cooperative environment, specifically one that is rapidly growing with a focus on continuous development/deployment
Walk This Way - An Introduction to DevOpsNathen Harvey
"DevOps" is a term that has become mainstream enough to be hated, misunderstood, misused, and abused. But what is "DevOps"? And, more importantly, why should I care?
Continuously Deploying Culture: Scaling Culture at Etsy - Velocity Europe 2012Patrick McDonnell
There was a time not long ago when Etsy was laden with barriers, silos, broken communication, and noncooperation. This talk will focus on the various stages of Etsy's cultural development from the early days to present. We will tell of how Etsy overcame numerous challenges and built a strong company culture while continuing to scale.
DevOps & Security from an Enterprise Toolsmith's Perspectivedev2ops
Slides from presentation by Alex Honor and Damon Edwards at DevOps Connect at RSA 2015 in San Francisco on April 20, 2015.
Abstract:
IT organizations are feeling the squeeze from seemingly conflicting business mandates. At one moment the message is “Go Go Go. DevOps, Lean Startup, Continuous Delivery… move faster and give more people access”. The next moment the message is “Be more secure. Compliance above all. Keep us out of the press!”. Damon Edwards and Alex Honor work with many enterprises who are facing these challenges. This talk is an in the trenches view of how these companies are responding and learning to go faster and be more secure.
The Journey of devops and continuous delivery in a Large Financial InstitutionKris Buytaert
The Journey of devops and continuous deliverey in a Large Financial Institution,
as presented by @markheistek and myselve at Velocity Conf 2013, Longon
Devops Management is a topic discussed in the halls of conferences and few managers. This talk will focus on the topic of management in a highly collaborative and cooperative environment, specifically one that is rapidly growing with a focus on continuous development/deployment
Walk This Way - An Introduction to DevOpsNathen Harvey
"DevOps" is a term that has become mainstream enough to be hated, misunderstood, misused, and abused. But what is "DevOps"? And, more importantly, why should I care?
Continuously Deploying Culture: Scaling Culture at Etsy - Velocity Europe 2012Patrick McDonnell
There was a time not long ago when Etsy was laden with barriers, silos, broken communication, and noncooperation. This talk will focus on the various stages of Etsy's cultural development from the early days to present. We will tell of how Etsy overcame numerous challenges and built a strong company culture while continuing to scale.
DevOps & Security from an Enterprise Toolsmith's Perspectivedev2ops
Slides from presentation by Alex Honor and Damon Edwards at DevOps Connect at RSA 2015 in San Francisco on April 20, 2015.
Abstract:
IT organizations are feeling the squeeze from seemingly conflicting business mandates. At one moment the message is “Go Go Go. DevOps, Lean Startup, Continuous Delivery… move faster and give more people access”. The next moment the message is “Be more secure. Compliance above all. Keep us out of the press!”. Damon Edwards and Alex Honor work with many enterprises who are facing these challenges. This talk is an in the trenches view of how these companies are responding and learning to go faster and be more secure.
(Talk given at Continuous Lifecycle London 2016)
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not funding the build/test/deployment capability properly
- No effective logging or application metrics
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing. Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.
Continuous Testing: Preparing for DevOpsSTePINForum
by Ingo Philipp, Distinguished Evangelist, Tricentis at STeP-IN SUMMIT 2018 - 15th International Conference on Software Testing on August 30, 2018 at Taj, MG Road, Bengaluru
1 year has passed since my Devops laboratory talk in Devopsdays Melbourne and we haven't stopped experimenting. After all the buzz and great conversations at Devops days I decided to extend the talk with a few more experiments on top of the previous presentation. This talk was first presented in Last.conf Melbourne on June 2016. The objective is no matter were your company is in terms of adopting a Devops culture/mindset there is always opportunities to try something new.
The experiments covered include:
E0. At the beginning, there was devs and ops
E1. Placements
E2. The tooling team (code name Gandalf)
E3. Secondments
E4. Ops as an attribute of Business areas
E5. The era of Guilds
E6. The raise of the Delivery Engineering teams
E7. Sec + DevOps
E8. Leverage vs Autonomy
E9. Finance + DevOps
E10. ????
Achieving continuous testing is a daunting task for many test teams still struggling with combining agile, test automation, and increased speed. We know that change is rarely easy. Fixing or getting rid of some practices is tough. However, one-step-at-a-time change can take you far and fast. To jumpstart your team, Michael Hackett shares learnings from four LogiGear clients in various stages of continuous integration, continuous testing, and continuous delivery. Failures in one organization ranged from naively thinking that automating every manual script was a good thing to misusing agile principles; this team needed an overhaul. Michael began with better test design, got rid of old style automation, and defined four sets of automated suites for different purposes, environments, and execution times. Very quickly the test team was contributing faster and providing more useful feedback to the whole development team. Join Michael and get moving to higher levels of continuous testing.
The Web moves fast, really fast. No one talks about what version of a web site you are using. Maybe you are using the beta version. Even then, it is always new. The Web is obsessed with new. It thrives on new. To meet this demand, in the early years of the web, teams learned a new way to deploy their software. Rather than the traditional models used by compiled, installed software, these pioneers on the Internet deployed software when it was ready. That meant Web sites could be responsive to changes, fix bugs quickly, and add new features to compete with the market. This method is still alive today. Successful web companies still do this to keep their advantage. While there are no set rules, there are good examples of what others do and how it helps them be successful.
Test Driven Development: Blueprint, Toolbox, and Master CraftStephen Ritchie
Many say that the practice of test driven development (TDD) has the ability to transform software engineering. Let’s break it down from a skeptical pragmatist’s viewpoint. This presentation focuses on three key ideas; the blueprint, the toolbox, and the master craft. Let’s look at TDD as a blueprint for writing code and discuss the implications and benefit. Let’s go beyond the theoretical application of TDD and focus on the toolbox, with examples of what developers need to know to get going. Finally, TDD is a master craft of Agile engineering. To be effective with TDD, let’s look at the progression of skills needed to achieve the promised results of TDD and to maximize its value.
Stephen is the organizer of DC Alt.Net (http://bit.ly/ZRDxUj). He frequent speaker and trainer on many .NET topics, including automated testing, continuous integration, code analysis, and .NET best practices.Stephen is the author of the book "Pro .NET Best Practices" (http://amzn.to/v8TD8E).
(Talk given at Continuous Lifecycle London 2016)
Continuous Delivery techniques and practices are often misunderstood. This session will explore some Continuous Delivery anti-patterns based on work 'in the wild' with a wide range of organisations across different industry sectors:
- Believing that "Continuous Delivery is not for us"
- Ignoring the database
- Thinking that a deployment pipeline is just a series of chained jobs in Jenkins
- Not funding the build/test/deployment capability properly
- No effective logging or application metrics
By avoiding these pitfalls, we can increase the effectiveness of our software delivery efforts.
DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing. Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.
Continuous Testing: Preparing for DevOpsSTePINForum
by Ingo Philipp, Distinguished Evangelist, Tricentis at STeP-IN SUMMIT 2018 - 15th International Conference on Software Testing on August 30, 2018 at Taj, MG Road, Bengaluru
1 year has passed since my Devops laboratory talk in Devopsdays Melbourne and we haven't stopped experimenting. After all the buzz and great conversations at Devops days I decided to extend the talk with a few more experiments on top of the previous presentation. This talk was first presented in Last.conf Melbourne on June 2016. The objective is no matter were your company is in terms of adopting a Devops culture/mindset there is always opportunities to try something new.
The experiments covered include:
E0. At the beginning, there was devs and ops
E1. Placements
E2. The tooling team (code name Gandalf)
E3. Secondments
E4. Ops as an attribute of Business areas
E5. The era of Guilds
E6. The raise of the Delivery Engineering teams
E7. Sec + DevOps
E8. Leverage vs Autonomy
E9. Finance + DevOps
E10. ????
Achieving continuous testing is a daunting task for many test teams still struggling with combining agile, test automation, and increased speed. We know that change is rarely easy. Fixing or getting rid of some practices is tough. However, one-step-at-a-time change can take you far and fast. To jumpstart your team, Michael Hackett shares learnings from four LogiGear clients in various stages of continuous integration, continuous testing, and continuous delivery. Failures in one organization ranged from naively thinking that automating every manual script was a good thing to misusing agile principles; this team needed an overhaul. Michael began with better test design, got rid of old style automation, and defined four sets of automated suites for different purposes, environments, and execution times. Very quickly the test team was contributing faster and providing more useful feedback to the whole development team. Join Michael and get moving to higher levels of continuous testing.
The Web moves fast, really fast. No one talks about what version of a web site you are using. Maybe you are using the beta version. Even then, it is always new. The Web is obsessed with new. It thrives on new. To meet this demand, in the early years of the web, teams learned a new way to deploy their software. Rather than the traditional models used by compiled, installed software, these pioneers on the Internet deployed software when it was ready. That meant Web sites could be responsive to changes, fix bugs quickly, and add new features to compete with the market. This method is still alive today. Successful web companies still do this to keep their advantage. While there are no set rules, there are good examples of what others do and how it helps them be successful.
Test Driven Development: Blueprint, Toolbox, and Master CraftStephen Ritchie
Many say that the practice of test driven development (TDD) has the ability to transform software engineering. Let’s break it down from a skeptical pragmatist’s viewpoint. This presentation focuses on three key ideas; the blueprint, the toolbox, and the master craft. Let’s look at TDD as a blueprint for writing code and discuss the implications and benefit. Let’s go beyond the theoretical application of TDD and focus on the toolbox, with examples of what developers need to know to get going. Finally, TDD is a master craft of Agile engineering. To be effective with TDD, let’s look at the progression of skills needed to achieve the promised results of TDD and to maximize its value.
Stephen is the organizer of DC Alt.Net (http://bit.ly/ZRDxUj). He frequent speaker and trainer on many .NET topics, including automated testing, continuous integration, code analysis, and .NET best practices.Stephen is the author of the book "Pro .NET Best Practices" (http://amzn.to/v8TD8E).
The practice of continuous integration (CI) has the ability to transform software development from a set of manual processes to a logical series of reproducible, automated processes. There are three concepts that are key to continuous integration; the blueprint, the toolbox, and the master craft. This session presents the CI lifecycle as a blueprint. You will see and understand the series of development processes that establish an effective, automated progression from source code to a packaged deliverable. You will learn about the CI server, which is the fundamental tool that initiates, performs, coordinates, and reports throughout the CI phases. The toolbox includes both the CI server and the combination of technologies that support CI. Continuous integration is a master craft of Agile engineering. To help you be effective with continuous integration, this talk demonstrates both the knowledge and skills needed to achieve the desired results of CI and to maximize its value.
Jan de Vries - How to convince your boss that it is DevOps that he wantsAgile Lietuva
- We all know that we could implement DevOps a lot faster if we only would have commitment from our boss. We all know that there is a shiny business case for almost every DevOps implementation
- And we all know that the whole company will reap the benefits regarding speed, agility and stability once we implemented DevOps. Actually, it provides good, fast and cheap at the same time. So, what are we waiting for? What is your boss waiting for? What is C-level waiting for?
- That’s something we will do research on in this workshop. We will also share our research on this from the recent past.
- The workshop starts with a presentation about 7 practices that a company should adopt to be able to apply DevOps.
- The technique that we use is called Appreciative Inquiry. To tackle a problem, it discovers the best practices that work, the reason they work and how these combined practices can be used to avoid the problem ahead and create a strategic change. The aim is to build – or even rebuild – organizations around what works, rather than trying to fix what doesn’t.
- So we want to know what your boss is afraid of and what you have already tried to convince him that he is better off with DevOps. You will leave the workshop with the combined Appreciative Inquiry insights of all the attendees
SPRINT 13 Workshop 1 What is, and how do you do AGILE? Roo Reynolds - GDS, Andrew Austin-Hancock - Maritime and Coastguard Agency, Keith Oliver - HM Coastguard, James Findlay - DfT
My talk about DevOps in Knowit Developer Summit 2018 in Oslo. This talk is a condensed version of the DevOps workshop I run for management teams and technical teams to start their journey as an organization towards DevOps. We refer to DASA DevOps Agile Skills Association's definitions of DevOps. The talk includes also Knowit DevOps Maturity Model high level description.
AgileLIVE Webinar: Build a DevOps Culture & Infrastructure for Success Part 1VersionOne
Lessons Learned from Target’s DevOps Journey
Heather Mickman, Director, Enterprise Services & Integration, and Ross Clanton, Sr. Group Manager - Engineering Practices, at retail giant Target, will share the key challenges and lessons learned.
DevOps - an Agile Perspective (at Scale)Brad Appleton
by Brad Appleton, Agile Day Chicago 2018, October 26 2018;
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
AgileDC15 I'm Using Chef So I'm DevOps Right?Rob Brown
Introduce DevOps to the uninitiated
Demystify the terminology and techno-centric jargon
Provide an assessment model that you can take back to your organization to help establish a baseline of behaviors and practices, and guidance on moving towards more of a DevOps culture
One of the values of the Agile manifesto is working software over comprehensive documentation. However many agile teams think that now we are Agile we don’t need to document. Come to this session to learn about lightweight documentation and how to strike a sensible balance between working software and documentation. Learn which documents are necessary and which documents you can do without as well. Learn about JIT lightweight alternatives to our tradition documentation set. Leave with specific techniques to evaluate the value of each document along with recommended alternatives.
Scrum and Agile Engineering Practices - What every ScrumMaster needs to know
Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We'll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We'll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team's software development process.
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices.
This presentation covers three basic ideas: static code analysis, dynamic code analysis, and the analyze-improve-monitor cycle. This session demonstrates many pragmatic tools and technologies that you can apply today within your .NET projects in order to perform effective code analysis.
Overcoming the Obstacles, Pitfalls, and Dangers of Unit TestingStephen Ritchie
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses DateTime.Now? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests?
This presentation is about clearing away automated testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Securing your Kubernetes cluster_ a step-by-step guide to success !
DevOps Requires Agility
1. DevOps Requires Agility
Stephen D. Ritchie – Managing Consultant – Excella Consulting, Inc., 2300 Wilson Blvd, Suite 630, Arlington, VA 22201 – 703.840.8600 – http://excella.com
Stephen D. Ritchie
@RuthlessHelp
Oct 21, 2014
Agile Professionals Meetup
October 2014
2. Live Tweet, Slides and Examples
• Twitter: @RuthlessHelp
• Slides:
http://www.slideshare.net/ruthlesshelp
• Code Samples:
http://github.com/ruthlesshelp
Stephen D. Ritchie
2
3. 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.
http://theagileadmin.com/what-is-devops/
Stephen D. Ritchie 3
4. DevOps Defined
• Operations and Development Folks
– Working together
– Entire lifecycle
• Change in Mindset
– Values
– Principles
– Methods
– Practices
– Tools
Stephen D. Ritchie
4
5. Example: Etsy
• Overview, June 2012
– Launched June 18, 2005
– 875,000 active sellers
– 33.5 million items for sale
– $65.9 million in sales, May 2012
– 1.4 billion page views, May 2012
– 102 engineers
• How often do they release to Production?
Stephen D. Ritchie
5
6. Etsy Deployments
• Reported February 2011
“In January (a month in which we did over a billion
page views), code committed by 76 unique
individuals was deployed to production by 63
different folks a total of 517 times.”
• Reported June 2012
– 32 times per day
• Reported March 2014
– 50 times per day
– http://www.infoq.com/news/2014/03/etsy-deploy-
50-times-a-day
Stephen D. Ritchie
6
7. Let’s Step Back
• Dan Pink
– Drive: The surprising truth about what
motivates us
• RSA Animate video
– https://www.youtube.com/watch?v=u6XAPnuF
jJc
Stephen D. Ritchie
7
9. The Problem
Stephen D. Ritchie
Source
Code
1 3 2
9
Scott’s
Computer
Susan’s
Computer
You
1
2
3
Scott makes changes
Susan makes changes
You can’t build
10. What Went Wrong?
Stephen D. Ritchie
10
Conflicts
Missing Files
Breaking Changes
11. How do you
find
integration
issues?
Stephen D. Ritchie 11
12. Manual Integration
Build
Run Some Unit Tests
Perform Static Analysis
Clean + Rebuild All
Stephen D. Ritchie
12
28. Closing Thought: CAMS
• Culture
– People and process first
– Virtuous discipline
• Automation
– Dev: building, testing, analyzing, packaging, deploying
– Ops: release management, provisioning, configuration management,
systems integration, monitoring and control, and orchestration
• Measurement
– Measure everything you can as often as you can
– Visibility and transparency
• Sharing
– Openness, share ideas and problems
– Confront problems, not each other
– Fail your way to success
Stephen D. Ritchie
28
29. Stephen’s Contact Info
• Email:
stephen.ritchie@excella.com
• LinkedIn:
http://www.linkedin.com/in/sritchie
Stephen D. Ritchie
29