3 Pillars of DevOps - Continuous Integration, Continuous Delivery, and Continuous Testing. Get details on What is DevOps? Basic Principles of DevOps, DevOps – The Solution Proposed, The philosophy of continuity – 7C’s of DevOps, Test Automation & Continuous Testing, Challenges in Standardizing DevOps, Role of Integration In DevOps, ESB Based Integration - Architecture, ESB Based Integration - Advantages, One Click DevOps, DevOps : Tool Integrations Across All Phases, Metrics/ Analytics in DevOps and CI, CD, CT Using Your Own Tools. For more details please visit - https://www.kovair.com/intelligent-devops/

1. Amit Dasgupta, PMP, CSM
Director – Major Accounts & Partnership
amitd@kovair.com

2. 2
What is DevOps?
• Technology to Process mapping in order to
• Improve the efficiency of your delivery process
• Reduce time to the market
• Bring people, process and tools together
• Enable continuity in the entire delivery lifecycle
DevOps

3. Basic Principles of DevOps
3
Iterative &
Incremental
Continuous
Automated &
Self-Serviced
Collaborative
HolisticThinking

4. 4
Wallofconfusion
DEV
Development
I want
Change
OPS
Operations
I want
stability
DevOps –TheSolution Proposed

5. 5
The philosophy of continuity – 7C’s of DevOps
OperationsALM
Continuous Planning
Continuous Integration
Continuous Testing
Continuous Monitoring
Continuous Delivery
Continuous Operations
Customer
Continuous Status
Update on fixes
and CRs
Coding and Check-in
for Automated Build
Functional Testing,
UAT and Test
Automation
Memory, Application
Performance, DB
Usage Monitoring
Bi-directional
IntegrationsRequirements/
CRs/Defects
Release Pipeline
Tracking
Reports, Dashboard
and Traceability
Analyst
Support
Tickets
Continuous Feedback

6. 6
• Development practice that requires developers to integrate code into a shared repository several times a day
• Each check-in is verified by an automated build, allowing teams to detect problems early
• Benefits
• Say goodbye to long and tense code merge
• Increase visibility enabling greater communication
• Catch issues early and nip them in the bud
• Spend less time debugging and more time adding features
• Build a solid foundation
• Stop waiting to find out if your code’s going to work
Continuous Integration -CI

7. 7
Developer 1 Developer 2Manager
1 Check in
changes
2
Fetch changes
3
Build
Notify Success
Or Failure 6
4 Test
5Success / Fail
Continuous
Integration
Server
Source
Control
Server
Continuous Integration -CI

8. 8
• Assesses business risk coverage
• Provides instant insight on release candidate quality
• Embeds testing within the development process, not tacked on at the end
• Avoids bottleneck, executes the right set of tests at the right stage of the delivery pipeline
• Delivers actionable & right feedback for each stage of the delivery pipeline
• Evaluates each layer of a modern architecture at the appropriate stage of the delivery pipeline
• Reduces false positives by prioritizing robust, flexible modern test frameworks over brittle scripts
• Eliminates redundancy by continuous review and optimal test suite
ContinuousTesting –CT

9. 9
ContinuousTesting
Write All
Test Scripts
CodeScript
Integrated
Code
Auto Build Auto
Automated
Integration
Testing
Auto
Automated
Acceptance
Testing
Auto
Automated
Performance
Testing
No human intervention
Write
Integration
Test Scripts
RunCode
Automated
Integration
Testing
Wait
Write
Acceptance
Test Scripts
Run
Automated
Acceptance
Testing
Wait
Write
Performance
Test Scripts
Run
Automated
Performance
Testing
Wait time impacts efficiency
Test Automation
TestAutomation &ContinuousTesting

10. 10
• Principles
• Build quality in
• Work in small batches
• Computers perform repetitive tasks, people solve problems
• Relentlessly pursue continuous improvement
• Everyone is responsible
• Benefits
• Low risk releases
• Faster time to market
• Higher quality
• Lower costs
• Better products
• Happier teams
Continuous Delivery –CD

11. ContinuousTestingContinuous Integration
Continuous Delivery
11
Version ControlDevelopment
Build & Unit
Tests
Automated
acceptance tests
User acceptance
tests
Release
Check in
Trigger
Check in
Trigger
Check in
Trigger
Feedback
Feedback
Feedback
Feedback Approval
Approval
Trigger
Feedback
Trigger
Feedback
Continuous Delivery
Scenario 1
Scenario 2

12. Challenges in Standardizing DevOps
12

13. Challenges in Standardizing DevOps
13

14. 14
• Establishes real-time alliance between delivery, development, and operations
• Achieves cross-tool traceability among data across different tools
• Embeds test strategy execution for continuous testing
• Enables continuous integration on successful accomplishment of code check-in
• Achieves continuous testing via workflow based test automation
• Enables an uninterrupted delivery
• Provides real-time visibility to release quality through reports and dashboards
• Provides meaningful metrics, reports and KPIs for speedy decision-making
• Enables continuous delivery via tracking release pipeline
Role of Integration In DevOps

15. 15
Operations Planning Development QABuild & Deploy Release
ESB Based Integration -Architecture
CrossToolTraceability CrossToolWorkflow CrossTool Reports & Dashboards
ESB Enterprise Service Bus ESB
Service Model Security Transports Service Locator
Data Transformation Interceptors Protocol Bindings

16. 16
• Faster and cheaper accommodation of existing systems.
• Increased flexibility; easier to change as requirements change.
• Protect your investment by integrating any tool of your existing tools ecosystem
• Scales from point-solutions to enterprise-wide deployment (distributed bus).
• More configuration rather than integration coding.
• Standards-based
• Less maintenance overhead compared to point to point integration
ESB Based Integration -Advantages

17. 17
ESB

18. 18
Initiation Application Development Test & Acceptance Production
Plan Code Build
Customer
Inputs
Test/QA Stage Release Deploy Provision Config Monitor

19. 19
MonitorConifgProvisionDeployReleaseStageTest/QABuildCodePlan
Custome
r Inputs
 Lead time
 Business need analysis
 Quick req. capturing
 Real-time reports
 CustomerTicket volume
• Code volume
• Commit volume
• Release speed
• Code quality
• Defect fixing speed
 Test volume
 Code coverage
 Exception counts
 Test automation
 Open rates/ close rates
 Requirements coverage
 Change request
 Release quality
 Pre-prod stability
 Release downtime
 Network bandwidth
usage
 CPU utilization
 Memory usage
 Operations/ second
 Application performance
 Issues feedback
 Mean time between
failures (MTBF)
 MeanTime to Repair/
Recover (MTTR)
 Security
 Process time
 Team efficiency
 Unplanned work
 Proper resourcing
 Time and cost allocation
 Build speed
 Failure rates
 Manual exceptions
 Performance
 Latency
 Scalability
 Deployment frequency
 Change volume
 Cycle time
 % of failed deployments
 Response time
 Uptime/Availability
 Infrastructure usage

20. 20
Operations
Release
DevPlanning
Delivery
Pipeline
Test
Automation
Build
Provisioning
& Deploy
CI,CD,CTUsingYourOwnTools
Enterprise Service Bus - ESB

21. 21
Thank You
Silicon Valley based
Software Product Company
Kovair Software Inc.
www.kovair.com
Contact: sales@kovair.com