Implementing dev ops to face a two speed it architecture

Implementing DevOps to face a two speed IT architecture
March 2018
Davide Veronese
davide.veronese@it.ibm.com
https://davideveronese.wordpress.com/
https://www.linkedin.com/in/davide-veronese-b8b08b28/

Agenda
2
Ø DevOps proposition
Ø DevOps strategy
Ø Best practices adopted by other customers
Ø Case Study
Ø solutions
Ø Q&A – Next steps

3
Scaling innovation in the enterprise can be
challenging
IBM 3
• Existing culture, process and organizational structure
inhibit innovation, speed and continuous experimentation
• Industry compliance, managed risk and governance requirements make it
difficult to scale successful pilots
• Operations, complexity and back-end systems bog down efforts

4
The solution: Implement a DevOps methodology that:
• breaks down silos within development
& operations
• addresses the practices & challenges
that disrupt execution
• brings the flexibility & speed of a
startup to the enterprise
Disrupt, or be disrupted
IBM 4

Enabling DevOps Transformation
Cloud adoption trends
Organizational
& cultural
transformation
Architecture
transformation
Monolithic
Distributed
Components
Stateful
Services
Stateless
Services
Siloed Business
Aligned
Cloud Native
Cloud Enabled
DevOps
transformations
Existing IT
Technically
Aligned
Customer
Aligned
5

DevOps in a multi-speed IT world to enable digital business
Accelerate Innovation
Think Code Deliver Run
API
Catalog
Think Code Deliver Run
Operational Excellence
Edge Applications
Core
Applications
Production
Production
Shared
Services
Innovation Edge
Rapid Delivery for Innovation • Agile • Experimentation • Hybrid Cloud • PaaS • APIs • Containers
Industralized Core
Deliver at regular cadence • WaterfallèAgile • Stability • Predictability • Core and Legacy • Hybrid Infrastr.
Partner Ecosystem
API Economy • Monetization • Service
providers and consumers
6
Finding the balance
between agility and
stability

Enabling DevOps Transformation
Cloud adoption trends
Cultural transformation
Architecture
transformation
Monolithic
Distributed
Components
Stateful
Services
Stateless
Services
Siloed Business
Aligned
Cloud Native
Cloud Enabled
DevOps
transformations
Existing IT
Technically
Aligned
Customer
Aligned
Innovative
DevOps
NextGen DevOps
• Bank on-premises + Cloud
• Start from current SW cycle
• Re-use (part of) current automation
• Maintain current target envs
• Cloud enabled
• 100% Cloud (also Hybrid)
• Integration with Bank
premises
• Open (e.g. Git, CloudFoundry,
Jenkins)
• Costs accountable on Cloud
7

The Hybrid IT Reference Architecture
Hybrid IT as a Platform-as-a-Service with DevOps
Services
&
Infrastructure
Application
marketplace
Rapid development
DevOps
Automation
&
Orchestration
h
• Service catalogue
enables business,
app developer,
and IT users to
consume services
from a storefront
• Pattern library
provides
standardized app,
middleware, DB
environments
• Orchestrator
enables pattern
based
deployment on
hybrid
infrastructure
across multiple
providers
• Enables
consumption
based cost model
PaaS Marketplace
(Cloud native apps)
Traditional development
(enabled cloud apps)
IaaS / PaaS / SaaS
service catalogue
Rapid innovation
(API ecosystem)
Continuous
innovation
Collaborative
development
Continuous
testing
Continuous
integration
Collaborative
lifecycle mgnt
User feedback &
optimization
Continuousrelease&
deployment
Cloud Broker and
Orchestrator
Pattern
composition
BPM
Auto scaling Cost aggregation
Specialized compute services
Mainframe Exadata Power
system
Teradata
x86 env
Networking
Application
performance mgnt
Analysis and
reporting
Operation&service
management,
VisibilityandControl
Public cloud GW
Pattern engine
Private cloud
connector
Public cloud
connector
Developer Business
users
IT user /
Ops
On premise
Containers
Private/Dedicated Public/Shared
Off-premise
8

Cloud native success
Single Function…. Stateless... Disposable.... Explicit....
Microservices
Cloud native
application
APIs
9
Cloud Native Computing Foundation (https://cncf.io/): a Linux Foundation Collaborative Project and
organization dedicated to advancing the development of cloud native applications and services, IBM has backed the CNCF’s
commitment to developing next generation cloud native applications based in open source and open standards

Creating a stable, operable and well integrated group of projects for
“born in the cloud” applications
• Container Packaged
• Dynamically Managed
• Micro-services Oriented
Seeded with Kubernetes from Google

• An open governance structure for creating open industry standards
around container formats and runtime
• Free from any particular company, OS, stack or client
• Spec, Reference Runtime and Image Format
§ Seeded with runC from Docker
OPEN CONTAINER INITIATIVE

• Fully managed hosted runtime
• Integrated logging, monitoring, load
balancing, registry and auto-scaling
• Advanced security features
• Orchestration with auto-recovery groups
• Built using Docker technology
IBM containers (1/2)

Docker Value IBM Value-add Customer Value
Docker Hub Registry holds a repository of 75000+ Docker
images
• IBM hosted private registry containing IBM images - linked to Docker
Hub
• Client unique registry available on and off premises
• Enterprise-ready images
• Security readiness guidance via the Vulnerability Advisor
Access to the images you require to deploy
containers that meet your business needs and
strategy
Open-source, standardized, lightweight, self sufficient LXC
container technology
• Enhanced performance with bare metal deployment
• Run images to local datacenter or cloud
• Deployment choice with pSeries & zSeries
Flexibility to choose the right hybrid cloud mix
for your business
Build, ship, and run standardized containers
• Integrated monitoring & logging
• Elasticity to grow storage & container needs
• Life-cycle management of containers and data volumes
• No VMs to manage
• Scalable, auto-recovery container groups
Docker ease of use combined with enterprise-
level integrity and confidence
Container connections using links and service discovery
• Private network communication
• External IP address
• Subnet Range
Extends and connects Docker containers to
production-ready enterprise environments
IBM Containers
Bluemix now comes with a fully integrated, high performance Docker experience, meaning monitoring, logging, elasticity,
enterprise images, and VM abstraction are all standard.

IBM proposition – DevOps adoption
3 – Optionally adopt containers
technology to optimize flexible
deployment
Image
registry
Bluemix
Delivery Pipeline
NextGen DevOps
(Cloud based)
API Management
2- PaaS DevOps solution based on
Bluemix for cloud native
applications (http://12factor.net)
Rational
Doors+RSA
Rational Team Concert IBM UrbanCode IBM Cloud Orchestrator
Innovative DevOps
(On-premise + Cloud)
1- Innovative DevOps for
not cloud native
applications
14

15
ROI: The Value of Deployment Automation
and DevOps

16
Example of Customer Metrics – Vanson Bourne research
The ROI of Enterprise DevOps http://devops.com/2015/03/09/the-roi-of-enterprise-devops/

DevOps process simplification savings can
be significant

Plan / Measure Development / Test Release / Deploy Monitor / Optimize
ScaledReliableRepeatablePracticed
Define release with
business objectives
Measure to customer value
Optimize applications
Use enterprise issue
resolution procedures
Standardize and automate
cross-enterprise
Automate patterns-based
provision and deploy
Manage data and virtualize
services for test
Deliver and integrate
continuously
Plan and source
strategically
Dashboard portfolio
measures
Automate problem isolation
and issue resolution
Optimize to customer KPIs
continuously
Improve continuously with
development intelligence
Test Continuously
Manage environments
through automation
Provide self-service build,
provision and deploy
Link objectives to releases
Centralize Requirements
Management
Measure to project metrics
Link lifecycle information
Deliver and build with test
Centralize and automate
test management
Plan departmental releases
and automate status
Automate deployment with
standard topologies
Monitor using business and
end user context
Centralize event notification
and incident resolution
Document objectives locally
Manage department
resources
Manage Lifecycle artifacts
Schedule SCM integrations
and automated builds
Test following construction
Plan and manage releases
Standardize deployments
Monitor resources
consistently
Collaborate Dev/Ops
informally
The Adoption Model is a tool to help an organization to understand where they are with DevOps practices,
and where to improve, with an incremental adoption vs. a big bang approach
Complete the DevOps Maturity Self Assessment
DevOps Managed
Services
DevOps Maturity model

IBM Cloud Orchestration - BPM
?
European bank example
SIAM
Service
Portal
Private
Cloud
(on premise)
CCAZ/CCAN
Systems & Service Man
SIAM (ITIL)
(Tactical Processes)
P4
CMS
IaaS
Portal
Service Now (ITIL)
Integrated
Service
Portal
P2
P1
P3
ITSO
Portal
SIAMAPIICOAPICMSAPI
HEAT Pattern Engine
CHEF
CMDB
VM
RHEL
WIN
SSCE
P4.1
P4.2
SSH
CHEF
agent
P3.2
P2.1
P2.2
P1.1
P1.2
ISPAPI
P3.1
uDeploy
I 4-3
I 3-2
I 2-1a
I 2-1bI 2-6a
I 1-2
HEATdb
I 2-3b
uDeploy
Portal
UCDAPI
P5.1
E4
E3
E2
E5
E1
I 1-6
I 5-3
P5
Business Service
IT Service
IT Service Topology
IT Platform Technology
IT Infra Technology
Appl. Deploy & Config. Service
RES
agent
UCD
agent
I 2-3a
Pre
HOT
RESAM
E6
I 6-1
I 6-2a
I 2-6b
Post - I & P
I 2-5
Recipe
Management
agents
Plug-in
Middleware
I 6-2b
P5.2
Deploy / Config. Appl.
Operate
?
I 3-5

ü Appl X (35%)
ü Appl Y (35%)
April Release
15th May
Initial Proof of Concept in Production for “validation”
Incremental implementation approach
§ Fixed team capacityà focus on step-by-step targets
§ Selected mix of competencies (customer + IBM ADM/SWG)
§ Move fast & safe to mitigate risk and deliver value at every
Release in Plan (accelerate ROI)
ü First
Bug Fix
ü Appl X, Y (100%)
ü Appl Z (40%)
June Release
July Release
Under
Evaluation
Nov Release
Under
Evaluation
Feb Release
ü Siebel
Sept Release
Apr
15
May
15
June
15
July
15
Nov
15
Feb
16
Sept
15
Under Investigation*
UrbanCode Deploy Adoption Approach
ü Appl Z (100%)
ü App YY
ü Appl X (POC)
Dec Release
Dec1
5

Human errors appreciably reduced (25 % estimated)
1st / 2nd level effectively applying error preventive approach during the deploy
phase avoiding “post opening” errors.
Error’s logs immediately available and Service Operation’s time saving in detecting and
solving business flow(s) issues (average detection dropped to real time from 1-1,5
hours x single flow)
SW Package download from/to different envs (IAT to PROD)
automatically executed (average dropped to 0,5 from 3 hours)
Centralized console to govern and monitor the deployment flows and errors in
real time
Improve Quality
Decrease Risk
Operational
Standardization
Reduce
Unproductive
Work
Operational
Standardization
Reduce
Unproductive
Work
Raise
Visibility / Audit
Raise
Visibility / Audit
Metrics – Production Environment Deploy vs
Semi Automated Approach

Error Reduction
and Prevention
Faster Time to
Market
Enhanced Cust.
Experience
FOC reduction
on CC
+ 20% Environments availability at 8:00 AM
+ 1000 Customers Care agents potentially available
Makes logs immediately available and allows support to be ready to
solve problems faster thanks to a simple interface
Allows preventive approach in errors detection during deploy before
systems’ opening and avoid errors post opening
Human error is appreciably reduced, thanks to automation in some
steps
No wasted time in downloading packages
Simplify deployment steps and improve productivity thanks to
deployment of BugFix directly from IAT environment
Potentially increasing of deployments frequency
Error Reduction
and Prevention
+ 20% Efficiency in reduction of pending customer
transactions on the Back-End systems …..
Error Reduction
and Prevention
IBM and Client’s joint Assessment after Sprint 1

IBM Rome Software Lab
- 23 -
Waterfall
Agile DevOps
Agile
Agile / DevOps
IBM Design Thinking
Evolution Path
2010
2014
2006

- 24 -
How to start: right roles & skills
The success of the
project depends on
our ability to build a
team and how the
members interacts
each other

DevOps
Agile
Design
Thinking
Project Start Analysis &
Planning
Define
Requirements
Design Development - Build - Testing Iteration
End
Delivery
Define Project Scope Define Features Build Application Delivery Application
Continuous Monitoring
Continuous Customer
Feedback and Optimization
- 25 -
Continuous Release & Deployment/
Automated Deployments
Product Backlog
Release Backlog Prioritization Backlog
Hills
Playbacks0
Retrospectives
Team Co-located - Team Self-managing - Team empowered
Feature Presentation
Continuous Business Planning
Collaboration / Shift-left Testing
Collaborative & Collaborative
Development
Continuous Testing/Automated
testing
Playbacks1
Users Story
Pair Programming
Daily Scrum
MVP
Sponsor Users

- 26 -
Continuous & Collaborative Development
consists of the following practices:
? Why
These practices help to better organize the
tasks and share the knowledge
How
Using automated deployment processes
that are transparent and repeatable.
§ Automated monitoring & reporting of
automated test execution is in place
§ Actually: Limited action to proactively
reduce technical debts
§ Whole team supports production
§ Automatically provision some
environments
Frequency
Daily
Duration
For all the duration of the project
- 26 -
Best Practices
Automated builds & Continuous integration:
Team integrate changes continuously into the continuous
builds process. Automatic BVT runs daily
Managing Technical debts:
Full team understand the need to manage and reduce
technical debts sprint after sprint
Dev & Ops Collaboration:
Close collaboration/interlock exists across the whole
team. Everyone understands the current feature and how
it is expected to behave in production. Whole team
completes all necessary work to deliver the feature
Infrastructure Automation/ Provisioning:
We provide the capability to replicate environments using
our own orchestrator solution in Cloud

- 27 -
Develop artifacts (dev,
test, doc)
Build Application
Support Continuous
Integration
Store “release” artifacts
Make them versionable
Support Continuous
Integration
Run automated Quality
Assurance tests
Promote to Staging
Provisioning new Staging
env on Cloud
Run real customer tests
cases
Generate tickets to promote
into Production
Provisioning new
build in Production
IBM UrbanCode Deploy
Rational Performance Tester JUnit
Rational Team Concert Selenium FrameworkRational Quality Manager
Rational Security AppScan Robot Framework
IBM Control Desk
IBM Security QRadar
IBM Endpoint Manager
IBM Application Performance
Management
IBM Workload Automation
Continuous Monitoring and OptimizationCollaborative Develop and Continuous Testing
Development
Build
Package
Repo
QA
Environment
Staging
Environment
Production
Environment
Application Deployment Automation
Cloud Provisioning

How does Bluemix work?
Bluemix is underlined by three key open compute technologies: Cloud Foundry, Docker, and OpenStack. It extends each of
these with a growing number of services, robust DevOps tooling, integration capabilities, and a seamless developer experience.
28

IBM proposition – NextGen DevOps
3 – Optionally adopt containers
technology to optimize flexible
microservices deployment
Image
registry
Bluemix
Delivery Pipeline
Next Gen DevOps
(Cloud based)
API Management
2- PaaS DevOps solution based on
Bluemix for cloud native
applications (http://12factor.net)
Rational
Doors+RSA
Rational Team Concert IBM UrbanCode IBM Cloud Orchestrator
Innovative DevOps
(On-premise + Cloud)
1- Innovative DevOps for
not cloud ready
applications
Bank - IBM Confidential 29

UI Microservice
Order Microservice
Catalog Microservice
SQL-DB
Cloudant
Microservices based application with SQL and no-SQL

«Catalog»
dev team
«Order» dev
team
«UI» dev team
ON-Prem system test env production env
Continuous Integration & Continuous Deployment pipeline architecture
Build
Unit
test
Functional
test
Automated DevOps
pipeline starts on new
application release
1
If no errors the system
automatically push the validated
build to the next phase
2
UCD automatically import the
changes from the correct SW
branches
3
If no errors the system
automatically takes a snapshot
and move it forward
4
Build
Unit
test
Functional
test
Build
Unit
test
Functional
test

Deployment model in production
IBM-SQLCloudant
UI Microservice
Catalog
Micorservice
Order
Microservice

PoC on going
Application Release Management
Cloud ProvisioningApplication Deployment Automation
DevOps: a possible provisioning and deploy on
cloud Tool Chain for Bank
Line of
Business
Jenkins
IBM UrbanCode
IBM Cloud Orchestrator
Bluemix
Serena Dimension HP Quality Center
CA Virtualization
Rational
Automation
Framework
Cloud environment
Possible extension with RTC (and Git)
IBM Test
Virtualization
Server

35
IBM UrbanCode Deploy – Plug-ins
35

Continuous testing from build to production
Orchestrate and automate the deployment and testing of applications, middleware configuration, and database
changes into development, test and production environments
Databases Internal
Messages
Third-party
Services
virtual components
Simultaneously
test across
multiple test
stages
Dev QA
IBM Rational Test
Virtualization Server
IBM UrbanCode
Deploy
IBM Rational
Test Workbench
integrated with
Test Environments
Dynamic Infrastructure
Deploy what is ready,
virtualize the rest
Continuously test in
production-like env.
Deploy private, secure
right sized test data
IBM InfoSphere
Optim Test Data Mgmt
UC Deploy Plugins
IBM Rational
Quality Manager
Manage quality across
the delivery lifecycle
36

APPL1
SYSTEM UNDER
DEVELOPMENT
New system development scenario
APPL2MQ
JDBC
APPL3
XML/HTTP
Ø Test virtualization is an enabler for
continuous integration testing
Ø Services, applications, systems are
introduced into the continuous integration
cycle in a prioritized, controlled fashion
APPL4
REST
APPLA
JMS
APPLB REST
CICS TG
37

Outsourcing development scenario
Physical
Test Environment
DB1
DEVICE1
APPL2
APPL1
Virtual
Test Environment
DB1
DEVICE1
APPL2
APPL1
Switch Capture
& Model
38
Ø Capture and model the outsourced environment
Ø Test against the on premise virtualized
environment without any limitation imposed by
the outsourcer or by the contract (volume
constraints, access window, planned
maintenance, etc.)

Docker Value IBM Value-add Customer Value
• Automate Docker builds
• Manage and distribute Docker
images in private image registries
• Easily host containers in the cloud
• Scale and auto-recovery
• Logging and monitoring
DedicatedLocal Shared
Docker
IBM Containers based on Docker
39

IBM’s Commitment to Open Technology
e-Business
Service Oriented
Architecture
Social
Business
Mobile
Computing
Hybrid
Cloud
Big Data &
Analytics
NO
SQL
Open Cloud
Architecture

Implementing dev ops to face a two speed it architecture

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a Implementing dev ops to face a two speed it architecture

Similar a Implementing dev ops to face a two speed it architecture (20)

Último

Último (20)

Implementing dev ops to face a two speed it architecture