Practical DevOps

Adopting DevOps with
Seven domain Workshops
Kelvin Yeung
Lead Architect
Greater China
CA technologies

2 © 2014 CA. ALL RIGHTS RESERVED.
Agenda
1. Introduction to DevOps. What and Why DevOps
2. Seven Domain Workshops. Your own Prioritization
3. Open Discussion

Dev Meet Ops, Ops Meet Dev
Dev Meets Ops
• See infrastructure as code
treat it the same way.
• Don’t lean on Ops just act,
scaling is also your
responsibility.
• Dev handles incidents and
problems.
Ops Meets Dev
• Ops picks up task to meet the
sprint commitment. Create
downstream env.
• Ops in the project team in day
1.
• Give a part of your control
plane away: API
N.Y. : Metropolitan Litho. Studio, c1879.
Why such a fail relationship
• Conflicting interest and KPI
• Ops comes in the last minutes.
• Working from different locations
• Outsourcing.

What is DevOps
“DevOps is a culture, movement or
practice that emphasizes the
collaboration and communication of
both software developers and
other IT professionals while
automating the process of
software delivery and
infrastructure changes.
It aims at establishing a culture and
environment where
building, testing, and releasing
software.”
Source: https://en.wikipedia.org/wiki/DevOps

Grass-root Movement was born of
the need to improve IT service
delivery agility.
Better utilize technology—especially
automation tools that can leverage
an increasingly programmable and
dynamic infrastructure from a life
cycle perspective.
What is DevOps
Source: http://www.gartner.com/it-glossary/devops/

“method of developing software
which enables developers and
other IT operations
professionals to communicate
and collaborate on projects,
with the goal of accelerating
the delivery of new business
services.”
 CA Technologies commissioned Vanson
Bourne to survey 1,300 IT executives
from large organizations in 21 countries
across the globe.
 The research explored key topics in
DevOps awareness, adoption,
implementation and benefits.
What is DevOps

Misconceptions about DevOps
Source: https://www.sdxcentral.com/articles/contributed/michael-huttermann-what-is-devops-common-misunderstandings/2014/04
http://www.evolven.com/blog/devops-misunderstandings-and-how-devops-really-drives-business-needs.html#sthash.mfZQglRy.dpuf
• DevOps strives for new organizational units or teams.
• DevOps holds all parties collectively responsible for the outcome.
• DevOps and continuous delivery (CD) are very tightly coupled.
• DevOps is using cutting edge tools.
• DevOps is agile.

Q9: What benefits have you seen or do you anticipate seeing from implementing DevOps in
your organization? Total: 859 who have or plan to have DevOps
Benefits of DevOps
DevOps Benefits Seen or Anticipated
28%
45%
38%
35%
35%
42%
46%
35%
48%
53%
39%
36%
51%
54%
55%
49%
45%
56%
46%
41%
0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
Increase in revenue
Our software/services available across more…
Fewer employees working on developing &…
Reduced time-to-market
Increased numbers of customers
Improved quality of deployed applications
Reduction in spend on development and…
New software/services that would otherwise not…
Increased collaboration between departments
Increased frequency of deployments of our…
Alread seen Anticipate seeing
94%
94%
91%
91%
91%
90%
89%
81%
67%
89%
Source: https://www.ca.com/us/register/forms/collateral/techinsights-report-what-smart-businesses-know-about-devops.aspx

Top Obstacles to Implementing DevOps
21%
21%
23%
24%
24%
25%
28%
35%
0% 5% 10% 15% 20% 25% 30% 35% 40%
Lack of the rights skills within…
The difficulty of merging the working…
Lack of understanding of the business…
No budget/no clarity over whose…
Lack of understanding of phases of…
Security or compliance concerns
Roles and responsibilities across dev…
Organizational complexity – people,…
Q6: What are the major obstacles to implementing a DevOps strategy in your organization
(select a maximum of three)? Total: 1,300
Common Barriers to DevOps Success

Is Your IT Organization Prepared to Implement DevOps?
1. Do you have well-defined roles and responsibilities for your development and operations
staffs?
2. Are your critical processes documented?
3. Have you built a business case and educated your top management on the benefits?
4. Have you assessed the current skills of your staff and identified what additional training
may be required?
5. Have you identified critical trouble-making applications that might be a great place to
start with your DevOps initiatives?

Agenda
2. Seven Domain Workshops. Your own Prioritization
3. Open Discussion

Seven Domain Workshop
Business
Strategy
Process
Architect
Projects
and
Applications
Costs &
Benefits
Building
Blocks
Organization
&
Governance
• DevOps enabled Business Strategies
• Visibility of hybrid waterfall & agile PPM
Meeting ever changing business initiative
• Reference Architectures
• Manageability/Availability
• Scalability
• Security
• Release Automation
• Test Automation
• Fast Feedback
• Organization Design
• Funding
• Skill-sets
• Roles & Responsibilities
• Picking right pilot and seek for the
fast pass.
• Funding the sharing capability with
multiple projects.
• Construction costs
• Business & IT Benefits
• Key Measures
• Max of existing manual and new
automated process
• Application centric change
management

Seven Domain Workshops – Prioritization Worksheet
Prioritization Worksheet
The Prioritization Worksheet consist of checklists and
questionnaires for organization who intended to know more about
DevOps adoption.
The purpose of the Prioritization Worksheet is to allow an
organization to better understand their priority of go deeper on
some/all of these areas.
CA is pleasure to plan and offer the 1-7 workshop(s) with the
sequence which fit to the organization the most.

Seven Domain Workshop –
1. Business Strategy Business Strategy
 A successful Journey needs a destination
• Faster Time to Market
• Competitive Differentiation
• Operational efficiency
• Quality
• Consistency & Compliance
• Agility

The appetites vary
Our need to compete & evolve is the same – but starting points/appetites vary
Waiting to
long for
Testing
Taking
too long
to
Develop
Too many
projects for
Environments
to handle Cost of
correcting
Defects too High
Too Many Errors
per Release
How
Long to
release
one line
of
Code?
Cost of
Environments
Spiralling
Business
moving faster
than IT
Time to
provision
environments

Q2: Which of the following do you think of as the most important components of any DevOps
strategy (select a maximum of three)? Total: 859 who have or plan to have DevOps
4%
25%
32%
32%
42%
45%
47%
52%
0% 10% 20% 30% 40% 50% 60%
Pre-production performance…
Aligned processes across dev &…
Continuous release cycles
Accelerated applications testing
Service virtualization
Collaborative teaming between…
Agile development
IT automation
The Most Important Components of DevOps

2. Process Process
Manual release and roll back Continuous Delivery
Existing Process To- Be Process
Delayed manual testing Continuous Validation
Scheduled code integration Continuous Integration
Ad hoc env provision
Scheduled automated env
provision
At random feedback from
production to development
Fast & standardized feedback
Too many teams
involved
Outsourced app
dev / operation
Non stand way of doing
thing
Legacy burden
Difficult to
merge/centralize task
Resistant

2. Process Process
 Work in parallel to speed time-to-market
 Create higher quality, more resilient apps that
are easier to deploy and manage
 Find defects early; fix quickly and reliably
 Accelerate release deployment
 Reduce manual effort, cost and errors
 Protect investment in existing tools
 Streamline complex, multi-tiered deployments
 Gain and share insight into mobile, enterprise and
mainframe apps and underlying infrastructure
 Identify and resolve issues quickly to assure
optimal customer experience
Agile Parallel
Development
Continuous
Delivery
Agile
Operations
Focusedonprocessestoenable:

2. Process Process
Current
State
Future
Vision &
Gap
Develop
Roadmap
Opportunity Tactical Actions
 The strategy and planning phase and implementation roadmap is
not a one-off exercise but should be seen as an on-going
process.
 Make sure that enterprises still deliver value while developing
their SOA capability.
 Acting tactically allows a pragmatic approach to delivering value
from the DevOps roadmap while at the same time addressing the
immediate concerns within each iteration.

2. Process Process

2. Process Process
Test
Automation
SCM
1
Artifact
repository
Dev SIT UAT STG
Release
Automation
(RA)
Continuous
Integration / Build
Automation
2
3
4
5
6 8
7 9
1. Release items tagged in SCM
2. Continuous Integration / Binary build
3. Built artifacts published to Repository (tagged to source)
4. RA deploys from Repository to Dev
5. RA kicks off automated tests on Dev
6. RA deploys from Repository to SIT
7. RA kicks off automated tests on SIT
8. RA deploys from Repository to UAT
9. RA kicks off automated tests on UAT
10. RA initiates / validates Change Request
11. On CR approval, RA deploys to STG and PRD
PRD /
DR
CR
10
11
Vision: Teams
reduce release
process from days to
hours, with
monitoring initiated
to detect problems
before production

2. Process Process
Application Release Operations
Release artifact
composition
(manifest)
Artifact life
cycle mgmt
(repository)
Integration
(CM / Repo /
Test / CMDB)
Environments
&
Infra-structure
Organization
(roles &
responsibilties)
Promotion
path
Process
reusability
Release
delivery
Proven repeatable implementation methodology

3. Projects and Applications Projects & Applications
Heat Map: Pick a pilot for Quick Win

3. Projects and Applications Projects & Applications
Existing waterfall
project
timeline
Dev1
Dev2
Dev3
System Test
Integration
UAT
System Integration
Dev
1
Dev
2
Dev
1
Dev
3
Dev
2
Dev
3
Uncertain delivery schedule – defects persist until UAT
Typical composite app today waits
for whole assembly to begin
With service virtualization quality effort
moved earlier in the lifecycle
Performance Test
Reduction in SDLC
Faster Delivery
Performance
UAT
…
New parallel
project
timeline with
service
virtualization

4. Building Blocks Building Blocks
PLAN OPERATE
CA Application Test CA SV & Cloud Test
API Management
CA Security
CA Service Virtualization
API Management
CA Release Automation
CA PPM CA Ops and APM
Continuous Integration Continuous Delivery
Continuous Validation
Operational Feedback

5. Cost and Benefits Cost & Benefits
How Will You Primarily Measure Success of DevOps?
Q8. Which of the following statements best describes how you will measure the success of your
DevOps initiatives? Total: 859 who have or plan to have DevOps
49%
38%
13% External factors:
increased revenue,
faster time-to-
market, improved
competitive
positioning,
enhanced customer
experience
Internal factors:
lower costs, fewer
bugs, improved
efficiencies, better
ROI, improved
collaboration
Haven’t
decided
yet

Efficiency
Measure how RA makes the
existing processes more
productive and reduce costs.
Manual Process
Manual process eliminated by
automation
Custom frameworks
The average reduction in headcount for
maintaining custom deployment tools
Audit checks
Reduction is time to generate audit
report for compliance and verification
Automation Value Acceleration
Reduction in time for validating
build integrity
INDIRECT BENEFITS
- Deployment bodies
Quality
Measure the value of quality
improvements achieved by
using RA
Overall Deployment Quality
The total number of code defects
crept during the deployment
Overall System Quality
The amount of production downtime
Defect Escape Ratio
The number of code defects found
during each phase of the SDLC with
CV
INDIRECT BENEFITS
-Service Level Maintenance
-Ability to offer guarantees
-Ensuring Compliance
Business Agility
Measure time to market new
features using RA
Competitive Edge
Respond to market needs with
accelerated deployments
MTTM
Deliver new features driven by
business needs
INDIRECT BENEFITS
-Customer Satisfaction
Ratings

6. Organization and Governance Organization &
Governance
Continuous
Improvement
Continuous
Improvement
Schedule
Based
Waterfall
Enterprise
DevOps
Reactionary
SPEED
QUALITY Enterprise DevOps Maturity Model

6. Organization and Governance
Create a working
group for each
DevOps discipline
and run is as a
development effort
PI #2
Automated
testing
team
Team:
(example)
Program Increment #1 (~10-11 weeks)
Build teams and establish cadence
Release
Planning
(1-2 weeks)
Sprints (~2 weeks each)
1. Create
backlog
2. Define
metrics
Sprint#1
Sprint#2
Sprint#3
Sprint#4
Sprint#5
Teams are a
mix of DevOps
engineers and
developers
from the
teams
The team meets in-person to build the backlog and define the desired
outcomes. At the end of each sprint, the team will deliver a demo of
working software, a retrospective, and planning for the next sprint.
The team
refines the
backlog at
the
beginning
of each PI.
Organization &
Governance

Governance
Developers must be able to on-board themselves quickly with minimal coaching
Welcome to the
DevOps hub
technologies
education
documentation
working groups
https:devopshub.yourcompany.com
The place for engineers
to go for information on
DevOps technologies
“Technology is
always the
easiest part of
the problem.”
- Mike Bland, 18F
Build a self-service hub1
* Conceptual wireframe

Organization &
Governance
Previous Team Structure
Development Team Operation Team
Infra Team
30 coordinators 60 coordinators
Maintains a large
number of
coordinator (non
technical
personnel )for the
purpose of
coordinating
activities between
Dev and Ops
6. Organization and Governance

Governance
Restructured DevOps team to promote collaboration
6 Dev engineers
3 Operation engineer
1 Product Owner
Structure in to DevOps team of 8-10 person.
• Currently there are 150 DevOps teams in X
• Manages between 1-5 applications
• Work as a cell unit, responsible as a team to
develop and deploy the application
• Outsource partners (from India) are assigned
to DevOps team too
• No need for coordinators role

Governance
On-boarding of new DevOps team
• Shipped with a single server containing all the necessary components for quick
start on Continuous Integration . Server contains:
• Jenkins
• Maven
• Sonar
• Hands-on experienced consultant join the newly formed DevOp team for 2-3
sprints to train to be self-sufficient.
• All DevOps team owns their own CI server, but every team connect to the same
RA server.

7. Architect Architect
High performing
teams build DevOps
capabilities in
parallel across
domains
PI #2
Service
Virtualization
Objective:
Test Case
Automation
Objective:
Provisioning
test data
Objective:
Dev / Test on
public clouds
Objective:
Self-service
environment
s
Objective:
Continuous
integration
Objective:
Environment
s team
Testing
team
Deployment
team
PI #3
Teams:
(examples)
Program
Increment #1
DevOps Release Train – an example

WAN/
WWW
Web
Server
Portal
SAP
Oracle
Mainframe
Web
Services
Mainframe
3rd Party
Applications
Database
Devices
Apps
Cloud
Apps
Systems of
Engagement
Systems of
Record
Mobile
performance,
behavior, crashes
End-to-end performance – Mobile to Mainframe
Deep transaction trace / visibility
Router
Firewall
Switch
Load
Balancer
CLOUD NETWORK FRONT END BACK ENDCUSTOMER
End-to-end monitoring to detect and remediate problems

Mobile App Analytics & APM deliver deep insight into
mobile, enterprise and mainframe applications.
Connect with Unified Infrastructure Management to
provide a complete view of services.
Improve Development by sharing:
• End user experience
• Crash reports
• App Analytics

Reference for
capturing user
behavior into
automated
testing
Use mobile analysis to capture user click stream1
Create test script with product like virtual service.2

Production data
mining for
test creation
Application Performance Mgmt












Reference
architect for fast
feedback
Production Environment
Web Tier
…
App Tier
…
Back-end system
CUPAC/DCS CLS …
Behavior
Collector
Behavior
Collector
MOM
Dev/Testing Environment
CA APM Agent
to collect production
behavior
Behavior
Collector
Stress Test Load GeneratorVirtual
Service
Category
Automated Regression Test
Web Tier
…
WS App Tier
… … …
Back-end system
… … …
CA Virtual Service
Runtime in Dev/Test
env
Harvest production data
 Production data
 Production use counts
 Production response times
 Paths from real users
Instant virtual service creation
Transaction Tracing
1. Use plugin to
rapidly create virtual
service.
2. Use APM agent to
collect production data,
response time and paths
from production.
3. Virtual service
with more relevant
data and production
like behavior.
CA Application
Insight

Testing
Test Data Management
Service Virtualization to virtualize dependent systems
Web & Mobile
Functional & Regression Test
Load generator for stress test
generator
generator
generator
generator
Coordinator
FastFeedback
……
Platform
Release Automation
Reference
architect for
testing platform

Reference
architect for
continuous
delivery
DEV TEST UAT PROD
Artifact
Repository
Test
Automation
Change Mgmt.
Config Mgmt.
Infra Prov
CA LISA®
Release Automation
Continuous
Application Delivery
Build Automation
Continuous
Integration Build “Ops-ready” release

Agenda
2. The practical approach to DevOps – Tangram Domain
3. Open Discussion

Summary
• There is no one size fit all.
• Begin with the end in mind.
• Pick the right pilot application with the right
project to drive a quick win.

Email: yeungwanki@gmail.com
Linkedin: https://hk.linkedin.com/in/kelvin-yeung-73856848
Kelvin Yeung
Lead Architect
Greater China
CA technologies

Practical DevOps

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to Practical DevOps

Similar to Practical DevOps (20)

Recently uploaded

Recently uploaded (20)

Practical DevOps