DevOps Architecture Design presentation was given by Ojasvi Jagtap as a part of DevOps++ Alliance Global Summit #doppa17.

1. #DOPPA17
Devops Architecture
Design
Ojasvi Jagtap
9th September 2017

2. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Devops Introduction
Devops Infrastructure
Automation
Devops Workflow with CI-CD-CD
Devops Architecture
Cost based analysis
Agenda

3. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Devops Introduction

4. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
What is DevOps?
Devops = Automation + Continuous Improvement + Co-ordination
Devops key work areas are,
-Infrastructure creation and management.
-Automation
-Workflow creation and maintenance
- Co-ordination between teams.
Devops

5. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Continuous Improvement with Devops
Communicate/Co-
ordinate with
teams
Discover
bottlenecks/
improvement
areas /
Optimization
areas /
refinement scope
Fix and automate
discovered areas
Test automation
Integrate with
Devops workflow

6. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Infrastructure

7. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Devops Infrastructure
Organizations Infrastructure can be categorize into below three high level categories.
IT Infrastructure
• VCS (Git/Stash)
• JIRA
• Code review Tool (Gerrit)
• Repository
Manager(Artifactory)
• Authentication
Management
server(LDAP)
• Database
• ……..
Build Infrastructure
• Platform build servers
• Servers to run code
coverage/ test
frameworks which needs
access to source code.
• ……
Test Infrastructure
• Deployment test
• Acceptance test
• Sanity test
• Functional test
• …..

8. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)

9. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)

10. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)

11. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Infrastructure Hosting

12. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)

13. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Cloud Services (IaaS)
Cloud Providers like Amazon Web Services (AWS), Windows
Azure, Google Compute Engine, Rackspace Open Cloud, and IBM
SmartCloud Enterprise etc

14. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Automation

15. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Success rate of Devops is highly depend on the automation
percentage.
More you automate, more you go close to Devops….
1) Automated Infrastructure management.
2) Automated Builds.
3) Automated Tests.
(Unit test, Coverage test, Functional test, Sanity tests etc)
4) Automated Deployment.

16. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Workflow

17. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Continuous Integration
Continuous Delivery
Continuous Deployment
Devops Workflows

18. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Continuous Integration (CI)

19. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)

20. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
• Make the whole process from check-in to release more efficient
• Automate more, shorten development cycle, release faster!
• Quickly identify check-ins that break builds or cause unit test failures
• Find more defects early in the software cycle
• Finding and fixing defects early and quickly is inexpensive in the long run
• Debugging and investigating defects later on takes time and resources that could
otherwise be used on new development
Why Continuous Integration?

21. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)

22. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Continuous Delivery (CD)

23. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
What is Continuous Delivery
• Continuous Delivery (CD) is the natural extension of Continuous Integration:
an approach in which teams ensure that every change to the system is
releasable. In CD teams keep producing valuable software in short cycles and
ensure that the software can be reliably released at any time. It is used in
software development to automate and improve the process of software
delivery.
• Continuous Delivery doesn't mean every change is deployed to production all
the time, It means that every change is proven to be deployable and of
releasable quality at any time.

24. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Core Tools of CI/CD
• Use of Source / Version Control
• CI Tool like Jenkins
• Configuration management tools like Ansible, Vagrant etc
• Build and Test Infrastructure
• Automated Build
• Automated Tests
• Automated Deployment

25. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Common CI/CD Workflow

26. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Continuous Deployment (CD)

27. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
What is Continuous Deployment
• Continuous deployment is the next extension of continuous delivery, every
change that passes the automated tests is deployed to production
automatically. Continuous deployment should be the goal of most companies
that are not constrained by regulatory or other requirements.
• Continuous Deployment is a software development practice in which every
code change goes through the entire pipeline and is put into production,
automatically, resulting in many production deployments every day.
• With Continuous Delivery your software is always release-ready, yet the timing
of when to push it into production is a business decision, and so the final
deployment is a manual step. With Continuous Deployment, any updated
working version of the application is automatically pushed to production.
Continuous Deployment mandates Continuous Delivery, but the opposite is
not required.

28. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Continuous Delivery Vs Deployment
 You need to decide scope of your Devops workflow automation.
 Continuous deployment is more suitable for the web based application release cycles
where it requires to deploy new version as soon as it is available.
 For products which does not require frequent deployment, and release time is more than
a month, in that case you can automate deploy but can trigger deployment manually.

29. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Architecture Design

30. Continuous Delivery Pipeline
Architecture

31. Continuous Deployment Pipeline
Architecture

32. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Cost Based Tool Analysis

33. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Sample 1
Low Cost Setup using Open source / free Tools

34. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Sample 2
Medium cost setup combining Open source / free Tools +
Proprietary Tools

35. #DOPPA17
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Thank you