1. www.unicomlearning.com
India Agile Week-2013
Oct. 25th 2013 Bangalore
Journey to the center of the DevOps
Case study of DevOps practices
Janardhanam Venkat
Director of Engineering
www.agileinbusiness.com
2. www.unicomlearning.com
Overview
UNICOM Presents
India Agile Week-2013
• Why you need DevOps?
• Industry statistics
• Orchestrate Devops
– How ops are involved in Agile process at CollabNet?
• Tools & Workflow
• DevOps Environment
• Customer Case Study
3. • Delays in new releases after QA qualified
• Failures in deployments
• Non compliance risk concerns
• No standardized / manual release process
• Dev and Ops finger pointing
Ops involved at the end of the release
When you need DevOps?
4. Challenges across the industry
Source: IT OPS & DEVOPS PRODUCTIVITY REPORT 2013
“The primary causes of downtime are:
human configuration error (40%),
software quality (30%) and missing
patches (20%).
5. Ops another Stakeholder ?
• Agile Manifest
– Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
– Deliver working software frequently, from a couple of weeks to a couple
of months, with a preference to the shorter timescale.
• Ops to be included in agile process from the beginning of the
release
• Eliminate manual hand off and reduce errors
• Enable faster release of changes
6. 1. DevOps culture
2. Streamline SDLC from planning to deployment
3. Visibility throughout the release & deploy pipeline
4. Implementation and automation of tools & workflows
Process
Tools
People
Orchestrate DevOps
8. • Growing multi-platform
requirements
• Increasing code complexity
without operational
consideration
• Enterprise-wide frequency of
iterations and releases
• Increasing compliance and
control such as security,
availability, performance
• Lack of knowledge on application
internals
• Trying to reduce changes to
avoid potential problems
Control
operations
Agility
development
1. Culture
9. • Establish & advocate collaborative, DevOps culture
• Adopt discipline and initiative to get stakeholders together –
Collective ownership
• Focus on mutual benefits and work on common goals
• Break silos between teams
• Implement process that emphasize business value
1. Culture
11. • Ops stories in release backlog
• Security Vulnerability
• Performance
• Product Installer usability
• PO collaborates with ops in writing stories
Source: Jason Sanders Teched North America
2. Streamline SDLC
12. • Ops in Sprint Review
• Application Installer
• Product Migration qualification
• Configuring application stacks
• Test new and modified feature flags
• Admin doc qualification
• Snapshot & Recovery process testing
• Security / Audit history
• Smoke Test - Installation and configuration – Exit Criteria
2. Streamline SDLC
14. • Traceability of application lifecycle via a centralized platform
• Alignment of release metrics between dev, ops & business
• Establish modes of communication
• Reporting and Devop dashboard
3. Visibility through the release & deploy pipeline
15. 8
Automate DeploymentCommence Coding
Product Owner Submits
- New Requirements
- or New Defects
Team Collaborates
(code – test – fix code – test…)
Continuous Integration
(Automate flow/track processes; App-Build, Test/QA, Release…)
Controlled Release
Project FRSApp
Monitoring &
Feedback loops
1
2
3
4
5
6 7
Engage Dev Team
3. Visibility through the release & deploy pipeline
17. 4. Automation of Tools & Workflow
• Shorter development sprint
• Bottle neck at the QA gates
• Different dir. structure, OS configurations and user permissions
• Version all the configuration, script and infrastructure
18. 8
Automate DeploymentCommence Coding
Product Owner Submits
- New Requirements
- or New Defects
Team Collaborates
(code – test – fix code – test…)
Continuous Integration
(Automate flow/track processes; App-Build, Test/QA, Release…)
Controlled Release
Monitoring &
Feedback loops
1
2
3
4
5
6 7
Engage Dev Team
ALM ARAProvision
4. Automation of Tools & Workflow
19. Packaging
Final Deliverables
Multiple OS
Distributed Environment
Deployment Steps
Role Based Access
Security
Target Environment
Configuration
Environment Specific
Approval Process
4. Automation of Tools & Workflow - ARA
Workflows Model
20. DevOps Environment
Profile
Dev Test Production
CI
CentOS
CentOS CentOS Redhat Redhat RedhatSuse
Packaging
CentOSWin
Workflows
Model
Redhat
Early Release
21. A large bank in Hong KongCompany
• Long application provisioning cycles
• High costs due to inefficient process
• High error rates due to manual changes
Challenge
• Fully Automated Deployment
• Focused on Internet Banking, Teller Application and other internal
applications
Solution
• 10x reduction in deployment timeResults
Customer Case Study
22. • Manual deployments, complex dependencies
• Many touch-points (SIT, UAT and Production) with pre & post activities
• Time Consuming, Wait Time, Inconsistency, No traceability, Audit Issues
• 70 applications, 2-3 people and 45 min on average per deployment per app.
• Higher Risk due to manual efforts & longer downtime
80 Hours Per Week
Before CollabNet Deploy
23. • Unattended deployment no duplication of effort, zero latency
• Meet compliance & security requirements
• Traceability with audit trail and visibility of build/deployment process
• Integrity maintained by retrieving source files from Source Control
• Automated notification of deployment progress
• Standard across all applications e.g. Teller, Internet Banking, etc.
8 Hours Per Week
After CollabNet Deploy
24. Deploy Workflow
• One click to commence deployment
• Centralized process
• Repeatable
• Scalable
• Centralized logging
25. • Productivity & Agility:
– Transform cumbersome, manual application deployments into fully
governed, lean and efficient automated processes that take minutes
instead of hours or days.
• Compliance and Governance:
– Automatic end-to-end tracking and reporting on all deployment
related changes and change activity and a built in segregation of
duties mechanism for planning and execution.
• Efficiency & Cost Savings:
– Reduce risk of millions and more by eliminating deployment related
outages as well as thousands of dollars save per deployment in terms
of time saved to configure, deploy and fix defects.
• Right technology is imperative:
– A single integrated platform creates multiple efficiencies increasing
transparency, reuse and trust within agile teams
• Best Engineering practices
Summary
