2. Mr. White has ďŹfteen years of experience designing and managing the
deployment of Systems Monitoring and Event Management software. Prior
to joining IBM, Mr. White held various positions including the leader of the
Monitoring and Event Management organization of a Fortune 100 company
and developing solutions as a consultant for a wide variety of organizations,
including the Mexican SecretarĂa de Hacienda y CrĂŠdito PĂşblico, Telmex,
Wal-Mart of Mexico, JP Morgan Chase, Nationwide Insurance and the US
Navy Facilities and Engineering Command.
Andrew White
Cloud and Smarter Infrastructure Solution Specialist
IBM Corporation
4. Ground rules for this
sessionâŚ
â˘âŻ If you canât tell if I am trying to be funnyâŚ
ââŻ
GO AHEAD AND LAUGH!
â˘âŻ Feel free to text, tweet, yammer, or whatever.
Use
â˘âŻ If you have a question, no need to wait until
the end. Just interrupt me. Seriously⌠I
donât mind.
5. Why are we here?
I am going to share some of what I have learned about
Software Defined,
Continuous Integration,
& Process Management
7. According to Enterprise
Management AssociatesâŚ
âSoftware-DeďŹnedâ serves to âabstract app/service design and
delivery away from the details of the hosting/delivery technologies.
This is delivered by making use of technical enablers
including virtualization and programmability (APIâs)
This approach drives Service-Aligned IT and
allows for more ďŹexible applications
Preference is given to open solutions that shift control from
hardware to software and leave single purpose appliances for
ďŹexible capabilities managed from a central location
8. The 4 key principles for
AT&T:
Domain
Â
2.0
Â
Open
 â
 APIs
Â
are
 the
Â
perfect
 tool
Â
Simple
 â
Â
More
Â
common
Â
infrastructure
Â
Scalable
 â
Â
Supports
Â
growth
Â
Secure
 â
Â
Protect
 the
Â
Control
 Plane
Â
Source: John Donovan, Senior Executive VP AT&T, Keynote Presenter at Open Networking Summit 2014, 4 MAR 2014
9. What is driving this move?
Three Trends
Vitrualization
Utilization and operation
Cloud Computing
Building blocks (compute, network, and
storage) with economies of scale
Internet of Things
Home Cinema, Connected Car
Two Industry Initiatives
Software DeďŹned Environments
New architectural approach, Open Network
Foundation - OpenFlow/OpenDaylight, Open
Data Center Alliance
Network Function Virtualization
New architectural approach, leaving dedicated
hardware for VMs, ETSI
Three Implications
Network Cloud
Lower cost, simpliďŹed operations, ďŹexibility
Use Cases
CDN, video on demand, home automation
Industry Status
Wide support for ONF and NVF
10. Increasing
Complexity
§ď§âŻHeterogeneous environments
§ď§âŻOrganizational silos
§ď§âŻSkill gaps
Massive
Scale
§ď§âŻUsers, transactions, data
§ď§âŻRapid demand cycles
§ď§âŻUnpredictable
Rapid
Pace
§ď§âŻEvolving ecosystem
§ď§âŻMinimize time to value
§ď§âŻAccelerating business needs
Todayâs IT infrastructures are too complex, provide poor scalability, and are
slow to keep up with todayâs rapid rate of change
A new set of challenges
V1 V2 V3 V4 V5 V5 ... âŚ. Vn
C
C
W1 W2 W3 W4
R1 R2 R3
Traditional
(Systems of Record)
Emerging
(Systems of Interaction)
Workload View
11. Future
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
§ď§âŻ Rapidly changing workloads,
dynamic patterns
§ď§âŻ Dynamic automatic composition
of heterogeneous system
§ď§âŻ Autonomic and proactive
management
Current
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
§ď§âŻ Diverse workload, limited
patterns
§ď§âŻ Homogeneous resource
pooling
§ď§âŻ Expert conďŹguration and
mapping of workload
Traditional
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
§ď§âŻ Few, stable, and well known
workloads
§ď§âŻ Fixed System hardware,
manual scaling
§ď§âŻ Hardwired workload, minimal
conďŹguration
W1 W2 W3 W4
R1 R2 R3
Volatile workload characteristics result from changing business requirements
V1 V2 V3 V4 V5 ⌠Vn
V1 V2 V3 V4 V5 V5 ... âŚ. Vn
C
C
Workloads are volatile
12. SDE is an Enabler
Software Defined Environment
Cloud Environment
Traditional
Environment
Social and
Mobile
Big Data and
Analytics
Other
Business
Applications
Workload
Service
Delivery
IT Infrastructure
Programmable, open standards-based infrastructure foundation
to enable cloud, mobile and other dynamic enterprise solutions
SDE is the infrastructure
approach to provide the
most efďŹcient and scalable
cloud solutions
SDE improves agility of business applications and
accelerates the application lifecycle through rapid change
13. So@ware
 DeďŹned
 Environments
 provides
 abstracEons
 of
 workloads,
Â
services
 and
 infrastructure
 and
 an
 end-Ââto-Ââend
 mappings
Â
.
Workload Abstraction
Based on pattern and
functional and non-functional requirements
Resource Abstraction
Semantically rich abstractions of heterogeneous
resource capabilities and system components
Mapping to resource
Map requirements to potential system
architectures. Proactively orchestrate
infrastructure and workload
Continuous Optimization
Autonomously construct available system
architecture to optimize workload outcome
Agility
EfficiencyConsumability
IMG
IMG
IMG
Agile Workload
Development Services
Workload Abstraction
SSD HDD
Tape
PowerVM
x86 KVM
PowerVM
x86 KVM
RDMA
Ethernet
Software Defined Compute, Network and Storage
Agility, Consumability, Efficiency (ACE)
Resource Abstraction
Software Defined Environments
Continuous, Autonomous Mapping
J2EE/OLTP
Transactional
Map/Reduce
Analytics
Web 2.0 Pattern
Web
14. Increasing Automation
SDE fully integrates IT infrastructure across resource domains to maximize
utilization, ensure compliance and decrease administration costs
BEFORE AFTER
StorageNetwork
Compute Continuous Optimization
+
+
+
+
+
+
+
+
+
+
+
+
Compute
§ď§âŻIT silos and costly specialization
§ď§âŻSlow and manual
§ď§âŻReactive administration
§ď§âŻFully integrated management
§ď§âŻRapid, repeatable and automated
§ď§âŻProactive administration
Policy
Policy
Policy
Policy
Software Defined Environment
Application
Aware
Policy
SDE in Action
15. Software Defined Networking (SDN) moves the network control
plane away from the switch to the software â for improved
programmability, efficiency and extensibility
Virtualized Network
OS
OS
OS
OS
SDN API
Open Flow
Open Flow
Open Flow
Software Defined Control Plane
SDN Controller
& Analytics
Routing API Traffic Engineering API Flow Insertion API Firewall API
routing
VPN
âŚ
monitoring
Direct Access to Physical Network
Traditional Switches
Console Based HW Configuration
routing
VPN
IPS
monitoring
OS
routing
VPN
IPS
monitoring
OS
routing
VPN
IPS
monitoring
OS
routing
VPN
IPS
monitoring
OS
Network Services
Traditional switch and router vendors being disrupted by the emerging SDN
16. What is the promise
of Software-DeďŹned
Everything?
18. What the CIO is hoping
â˘âŻ Economies of Scale from End-to-End Virtualization
â⯠Develop a truly shared infrastructure
â⯠Eliminate âvendor lock-inâ
â⯠Compete on cost with 3rd party IT providers
â˘âŻ Break Down the Silos
â⯠Align with services and not technologies (silos of virtualization
are still silos)
â⯠Improve time to value
â⯠Reduce the number of IT specialties in the workforce
â˘âŻ Empower the business
â⯠Enable the self service consumption of IT services
â⯠Simplify the services being offered
â⯠Enable continuous improvement
19. What the architects are hoping
â˘âŻ Cleanly separate the environment into four layers (planes):
Management, Services, Control, and Forwarding - providing
the architectural underpinning to optimize each plane within
the network.
â˘âŻ Centralize the appropriate aspects of the Management,
Services and Control planes to simplify the design and lower
operating costs.
â˘âŻ Use the Cloud for elastic scale and ďŹexible deployment,
enabling usage-based pricing to reduce time to service and
correlate cost based on value.
â˘âŻ Create a platform for network applications, services, and
integration into management systems, enabling new
business solutions.
â˘âŻ Standardize protocols for interoperable, heterogeneous
support across vendors, providing choice and lowering cost.
20. Reality Sets in
The current environment is not ready for change
The staff is overworked, stafďŹng levels are dropping, open
reqâs go unďŹlled to an inability to ďŹnd adequate talent.
The business wonât abandon âlegacy toolsâ
Increasing amounts of governance are established to manage the chaos
Technical debt and security risks cause
incidents that distract from deployments
21. Architecture by Accident
The Humble StartâŚ
Meeting DemandâŚ
The First BottleneckâŚ
The Second BottleneckâŚ
Becoming Mission
CriticalâŚ
Enabling SOAâŚ
The Fun BeginsâŚ
How Did We Get Here?
22. Game changers
1.⯠Increased demands for high availability and
low latency
2.⯠The visibility gap grows
3.⯠Market forces drive increased velocity and
volume of changes
4.⯠Productivity losses and customer satisfaction
decreases impact the business
23. Broken Promises
The ultimate result in the exact opposite of what
the CIO initially hoped for:
â˘âŻ Communication failures
â˘âŻ Security incidents
â˘âŻ Poor performance
â˘âŻ Compliance failure
â˘âŻ Higher costs
25. Software delivery is
critical to success
86%
of
 companies
 believe
 so/ware
 delivery
Â
Â
is
 important
 or
 cri5cal
Â
25%
leverage software delivery effectively today
But onlyâŚ
Source: âThe Software Edge: How effective software development drives competitive advantage,â IBM Institute of Business Value, March 2013
69%
outperform
those who donât
of those who
leverage software
delivery today
28. Feedback Loops
Unfortunately feedback has taken on both positive and negative
indications. In reality, positive feedback is not âpraiseâ and
negative feedback is not âcriticism.â Positive feedback
reinforces while negative feedback balances.
Profits
Productivity
Cost Cutting
Reinforcing
Balancing
31. Be Careful of Good
Intentions
Availability
Change
Frequency
Change
Size
Change
Capability Change
Risk
(-)
(+)
(+)
(-) (-)
Business
Value
Business
Demand
Change
Backlog (+)
(+)
(+)
(+)
(-)
(+)
Change
Process
Release
Process
(+)
(+)
(-)
(+)
(+)
Adapted From: http://www.lean4it.com/2013/05/devops-cld-part-2.html
32. Be Careful of Good
Intentions
Availability
Change
Frequency
Change
Size
Change
Capability Change
Risk
(-)
(+)
(+)
(-) (-)
Business
Value
Business
Demand
Change
Backlog (+)
(+)
(+)
(+)
(-)
(+)
Change
Process
Release
Process
(+)
(+)
(-)
(+)
(+)
Change
Automation
Adapted From: http://www.lean4it.com/2013/05/devops-cld-part-2.html
(+) (-)(-)
33.
34. Organizations donât fail
because they take the
wrong path, they fail
because they canât
imagine a better path
than the one they are on.
-- Marty Neumeier
39. Turning Services Into Solutions
Service
 Interface
Â
Automa5on
Â
Orchestra5on
Â
Choreography
Â
Business
 Service
Â
OďŹering
Â
Billing
Â
Customer
Â
Management
Â
Add
 Customer
Â
Order
Â
Management
Â
Assign
 Service
 to
Â
Customer
Â
Order
 FulďŹllment
Â
Provisioning
Â
Â
Deploy
 Device
 ConďŹgure
 Device
Â
40. Palette of library
assets enable easy
workflow composition
through drag and drop
Access to rich libraries
(toolkits) of reusable
automation assets that
enable to speed
automation creation
Rich set of actions types,
flow control, data handling
primitives that simplify
creation of complex
automations
Easy workflow action editing
for managing: data mapping,
error recovery options,
implementation details , etc.
Graphical editor for
composing and
connecting
workflows
Rich tooling
functions to edit,
version, debug,
optimize workflows
Automating Processes
42. OrŸďchesŸďtraŸďtion [AWR-kuh-strey-shun]
â˘âŻ A central process controls everything and coordinates the
execution of different operations involved in the operation
â˘âŻ The services do not "knowâ that they are involved in a
composite process
â˘âŻ Only the central coordinator of the orchestration is aware of
the desired outcome,
â˘âŻ The orchestration leverages explicit process deďŹnitions to
operate the services in the correct order of invocation
Â
1.⯠the act of arranging a piece of music
2.⯠the planning or execution of events in order to achieve a desired effect
3.⯠The technique of arranging or manipulating, especially by means of
clever or thorough planning or maneuvering
44. ChoŸďreŸďogŸďraŸďphy [kawr-ee-OG-ruh-fee]
Â
1.⯠the art of composing ballets and other dances
2.⯠the method of representing the various movements in dancing by a
system of notation
3.⯠The arrangement or manipulation of actions leading up to an event
â˘âŻ Choreography does not rely on a central coordinator.
â˘âŻ Each service knows exactly who and when to execute
â˘âŻ Focuses on the exchange of messages and information
â˘âŻ All services need to be aware of the business process,
operations to execute, messages to exchange, timing, etc.
46. Choreography vs. Orchestration
â˘âŻ From the perspective of composing services to
execute business processes, orchestration is a more
ďŹexible paradigm and has the following advantages
over choreography:
â⯠The coordination of component processes is centrally
managed by a known coordinator.
â⯠Web services can be incorporated without their being
aware that they are taking part in a larger business
process.
â⯠Alternative scenarios can be put in place in case faults
occur.
Page
 46
Â
47. Orchestration Requirements
â˘âŻ Event-based processing
â˘âŻ Coordinate asynchronously between services
â˘âŻ Correlate messages being exchanged
â˘âŻ Provide for parallel processing
â˘âŻ Allow for transaction roll-back
â˘âŻ Manipulate and transform data between messaging
partners
â˘âŻ Be able to manage long running business
transactions and activities
â˘âŻ Have a robust mechanism for fault and error
handling
48. Why use an event-based
orchestration engine?
to have the ability to receive
real-time feedback to assist its
decision making processes
49. When decisions are not made based
on information, itâs called gambling.
50. Environments
QA
PROD
Banking Application
Banking Application
Banking Application
DEV
IBM UrbanCode Deploy
OpenStack Heat
IBM Platform Resource Scheduler
Server
Storage
Network
Application "
Lifecycle
Applications
Heat Orchestration Template (HOT)
Heat Orchestration Template (HOT)
OpenStack Heat
IBM Platform Resource Scheduler
Server
Storage
Network
TEST
IBM Cloud Orchestrator
Architecture on Purpose
Public
Dedicated
Private
Traditional
IT
Application
template
Infrastructure
template
Hardware
51.
52. Completing the journey
Define
â˘âŻ Review the existing architecture
â˘âŻ Review the business outcomes
â˘âŻ DeďŹne the end state
Prioritize
â˘âŻ Consolidations
â˘âŻ Technologies to virtualize
â˘âŻ Business processes to model and workďŹows to automate
Execute
â˘âŻ Look for early wins
â˘âŻ Evolve incrementally
â˘âŻ Organize the teams effectively
53. You have to be realistic about how fast
you can mature. Iterating helps form a
cultural of continuous improvements
Iterative development