DevOps practices
2 likes5,490 views
DevOps represents a change in IT culture that focuses on rapid delivery of services through practices like agile development and continuous integration. It emphasizes collaboration between development and operations teams and utilizes automation tools. Adopting DevOps practices can impact an organization, and teams need expertise in the tools used. Continuous improvement is important, as is eliminating bottlenecks and reducing wait times during the development process. Version controlling all components and automating environment creation can help enable continuous deployment.
DevOps practices
- 1. F R O M I C T E X P E R T P E R S P E C T I V E SERHIY PEREVOZNYK DEVOPS PRACTICES
- 2. G A R T N E R I T G L O S S A R Y WHAT IS DEVOPS? DevOps represents a change in IT culture, focusing on rapid IT service delivery through the adoption of agile, lean practices in the context of a system-oriented approach. DevOps emphasizes people (and culture), and seeks to improve collaboration between operations and development teams. DevOps implementations utilize technology — especially automation tools that can leverage an increasingly programmable and dynamic infrastructure from a life cycle perspective.
- 3. LEN, BASS. “DEVOPS: A SOFTWARE ARCHITECT’S PERSPECTIVE.” DEVOPS PRACTICES DevOps is a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality
- 4. KIM, GENE. “THE PHOENIX PROJECT” DEVOPS CULTURE We need to create a culture that reinforces the value of taking risks and learning from failure and the need for repetition and practice to create mastery.
- 5. MIKE ROTHER CONTINUOUS IMPROVEMENT It almost doesn’t matter what you improve, as long as you’re improving something
- 6. KIM, GENE. “THE PHOENIX PROJECT” DEVOPS TRANSFORMATION By modifying our development and deployment processes, we’re hardening and securing both the applications and production infrastructure in a meaningful and systematic way
- 7. LEN, BASS. “DEVOPS: A SOFTWARE ARCHITECT’S PERSPECTIVE.” ADOPTING DEVOPS The difficulty of adopting a practice is related to its impact on other portions of the organization
- 8. LEN, BASS. “DEVOPS: A SOFTWARE ARCHITECT’S PERSPECTIVE.” DEVOPS IMPACT The difficulty of adopting a practice is related to its impact on other portions of the organization
- 9. LEN, BASS. “DEVOPS: A SOFTWARE ARCHITECT’S PERSPECTIVE.” DEVOPS TOOLS There must be expertise in the installation, configuration, and use of each tool. Tools have new releases, inputs, and idiosyncrasies. Tool expertise has to be integrated into the organization
- 10. E. M. GOLDRATT. “THE GOAL.” PRODUCTIVITY Productivity is the act of bringing a company closer to its goal. Every action that brings a company closer to its goal is productive. Every action that does not bring a company closer to its goal is not productive.
- 11. DAVID P. JOYCE DELIVER MORE It’s not “the more you start, the more you finish,” it’s “the more you finish, the more you finish.”
- 12. KIM, GENE. “THE PHOENIX PROJECT” UNPLANNED WORK Unlike the other categories of work, unplanned work is recovery work, which almost always takes you away from your goals. That’s why it’s so important to know where your unplanned work is coming from.
- 13. E. M. GOLDRATT. “THE GOAL.” BOTTLENECK A bottleneck is any resource whose capacity is equal to or less than the demand placed upon it. And a non- bottleneck is any resource whose capacity is greater than the demand placed on it
- 14. E. M. GOLDRATT. “THE GOAL.” ELIMINATE BOTTLENECKS STEP 1. Identify the system's bottlenecks. STEP 2. Decide how to exploit the bottlenecks. STEP 3. Subordinate everything else to the above decision. STEP 4. Elevate the system's bottlenecks. STEP 5. If, in a previous step, a bottleneck has been broken go back to step 1
- 15. KIM, GENE. “THE PHOENIX PROJECT” WAIT TIME The wait time is the ‘percentage of time busy’ divided by the ‘percentage of time idle.’ In other words, if a resource is fifty percent busy, then it’s fifty percent idle. The wait time is fifty percent divided by fifty percent, so one unit of time. Let’s call it one hour. So, on average, our task would wait in the queue for one hour before it gets worked. On the other hand, if a resource is ninety percent busy, the wait time is ‘ninety percent divided by ten percent’, or nine hours. In other words, our task would wait in queue nine times longer than if the resource were fifty percent idle
- 16. KIM, GENE. “THE PHOENIX PROJECT” DEPLOYMENT Find out how production vulnerabilities got there in the first place and that we ensure that they don’t happen again by modifying our deployment processes
- 17. LEN, BASS. “DEVOPS: A SOFTWARE ARCHITECT’S PERSPECTIVE.” CONTINUOUS INTEGRATION You cannot do continuous deployment without first doing continuous integration.
- 18. KIM, GENE. “THE PHOENIX PROJECT” DEVOPS ENVIRONMENT There should be absolutely no way that the Dev and QA environments don’t match the production environment
- 19. H E A D L I N E G O E S H E R E VERSION CONTROL You need to get everything in version control. Everything. Not just the code, but everything required to build the environment. Then you need to automate the entire environment creation process. You need a deployment pipeline where you can create test and production environments, and then deploy code into them, entirely on-demand. That’s how you reduce your setup times and eliminate errors, so you can finally match whatever rate of change Development sets the tempo at.
- 20. KIM, GENE. “THE PHOENIX PROJECT SECURITY Integrating security into all of our daily work, no longer securing things after they’re deployed.
- 21. KIM, GENE. “THE PHOENIX PROJECT POWER OF DEVOPS Dev and Ops working together, along with QA and the business, are a super-tribe that can achieve amazing things
- 22. SERHIY PEREVOZNYK https://perevoznyk.wordpress.com https://www.linkedin.com/in/perevoznyk Images from https://unsplash.com