Cloud 122 building the perfect cloud

© IBM Corporation 1
IBM Software University 2015
WebSphere Technical University PLUS
Mobile, BPM, Cloud, Integration, Application
Platform, IBM z Systems and Digital Experience
13 – 16 October 2015|Dublin, Ireland
Cloud 122
Building the Perfect Cloud
Scott Simmons
Master Cloud Advisor
IBM Cloud

The Problem with MANY Current “Cloud” Solutions
“Google – tecture”

© IBM Corporation 3© IBM Corporation 3
Cloud – The Current Architectural Realities
•  Current IT – Virtualization “run amok”
•  The Promise of Cloud … huge!
•  The Challenges of Cloud … not huge!
•  So … Is There a Perfect Cloud?

•  Cloud Architectures – Evaluating Options
•  Architecture Principles in “Cloud Building”
•  Practices for Success in the Cloud

–  Assessing Cloud Delivery and Deployment
–  Hybrid Cloud IS Cloud Computing
–  The Promise of Cloud Standards

Networking Networking Networking Networking
Storage Storage Storage Storage
Servers Servers Servers Servers
Virtualization Virtualization Virtualization Virtualization
O/S O/S O/S O/S
Middleware Middleware Middleware Middleware
Runtime Runtime Runtime Runtime
Data Data Data Data
Applications Applications Applications Applications
Tradi&onal
IT
Infrastructure
as a Service
Pla5orm
as a Service
So7ware
as a Service
Client Manages
Vendor Manages in Cloud
Client Manages
Client Manages
Customiza&on; higher costs; slower &me to value
Standardiza&on; lower costs; faster &me to value
Assessing Cloud Delivery Options
1-3

Assessing Cloud Deployment Options
•  On Premise Cloud
•  Off Premise Cloud
•  Hybrid Clouds
Systems of Record
Systems of Engagement
Private Public
On Premise
Off Premise

Cost /
investment
Features
(initial & future)
Elasticity
Security
Service
Integration / SLA
Provider
switching effort
Client
Architecture
Control
1
Provider designed
and operated
Provider designed
and operated
User A User B
User C
User D User E
5
Enterprise C
Enterprise B
Enterprise A
4
Deployment
models
2 3
Client designed
and owned
Client
data center
Client
data center
Provider
data center
Private
cloud
Managed
private cloud
Hosted
private cloud
Shared
cloud
Public
cloud
High-Level Cloud Deployment Tradeoffs

Shared
off-premises
cloud
Dedicated
on-premises
cloud
Traditional IT Dedicated
off-premises
cloud
Key considerations: •  Data
•  Integration
•  Control / Governance
Enterprise
applications
Cloud enabled
Cloud native apps / services
Hybrid cloud
The Reality – Hybrid Cloud IS Cloud Computing

Hybrid Cloud Enables “N-Speed”/Bi-Modal IT
Rapid iterations
Cloud Native
Slower iterations
Cloud Ready
Alignment
Continuous synchronization
and planning
Continuous testing
Continuous deployment
and monitoring
Plan Develop Build Test Deploy Production
Plan Develop Build Test Deploy Production
http://www.redbooks.ibm.com/abstracts/redp5191.html?Open

Hybrid Cloud Patterns
Notice: Objects in mirror are closer than they appear
(e.g. it would be nice if this were really this simple …)

Cloud Standards Enable Architectural Flexibility
Hybrid CloudPrivate Cloud Off-premise cloud
IaaS
PaaS
SaaS
OAuth
OSLC
http://www.ibm.com/developerworks/cloud/library/cl-open-architecture/

OpenStack Provides IaaS Foundation
Network Dashboard
Compute Image Object
Storage
IdentityBlock Storage
Compute (Nova)
Dashboard (Horizon)
Image (Glance)
Identity (Keystone)
Object Storage (Swift)
Network (Neutron)
Block Storage (Cinder)
Metering (Celiometer)
Orchestration (Heat)
Containers (Magnum)
And more to come

Cloud Foundry is the industry’s Open PaaS and
provides a choice of clouds, frameworks, and application services.

(PaaS also needs to support OpenStack and native containers as well)
Cloud Foundry Provides PaaS Foundation

Static website Web frontendUser DB Queue Analytics DB
Development
VM
QA server Public Cloud Contributor’s
laptop
Containers Provides Delivery/Runtime Foundation
Mul1plicity of Stacks Mul1plicity of hardware
environments
Production Cluster
Customer Data
Center
…that can be manipulated using
standard operations and run
consistently on virtually any
hardware platform sharing OS
and bins/libraries as needed
An engine that enables any
payload to be
encapsulated as a
lightweight, portable, self-
sufficient container…
https://www.opencontainers.org/

Building the Perfect Cloud Agenda
–  “Cloud Ready IT”
–  Common Cloud Anti-patterns
–  Architectural Aspects for the Perfect Cloud

“Cloud Ready IT”
How do I leverage exis1ng on-
premises assets (data and services)
for cloud and also free up resources
for innova1on?
How do I leverage exis1ng on-
premises system of record assets
(data and services) for cloud?
How do I elas1cally scale my back-end
systems to handle new traﬃc from
engaging applica1ons in the cloud?
Systems of
Engagement
Systems of
Record
Secure Manage Deploy Connect Scale
Enable Hybrid Cloud Prepare for Hyper Scale Op&mize IT
Applica&on Integra&on Middleware
Share
In all of these areas – you need to consider organizational (people/process) implications

Cloud Architecture Is More Than Technology
The transformation to a composable business is more than
technology, it’s about people, process, and culture
People
•  Empowerment
•  Faster Decision Making
•  Roles/Responsibilities
Process & Delivery
•  Continuous Delivery
•  Canary Testing
•  “Chaos Monkey”
Organization & Culture
•  DevOps
•  Agile
And this is where we find most of the problems with cloud adoption

Common Cloud Anti-Patterns
•  No definition of strategic and tactical goals
•  Business/LOB not part of planning/design
•  Not evaluating all potential options
•  Lack of complete requirements (esp NFRs)
•  Fragmented architecture approach
•  Focusing solely on tools/technology
•  Not following a Fit-For-Purpose approach

Architectural Aspects for the Perfect Cloud
•  Applying Architectural Thinking
•  Requirements and Architectural Decisions
•  Considering Topology Options
•  Defining the “Cloud Technology Stack”
•  Cloud Workload Assessment
•  Adopting Cloud Application Architecture
•  Organizational Alignment

Applying Architectural Thinking
Inputs Thinking Process Outputs
Requirements
What is to be solved?
Qualities
How “good” is it?
Constraints
What freedom do we have?
Architecture
(Functional
Nonfunctional
Operational)
Architecture Viability
& Representation
Assets & Technology
What is available?

Requirements and Architectural Decisions
Performance Compute, Network, Storage
Availability Scalability, Failover
Disaster Recovery Redundancy, RTO/RPO Considerations
Management/Orchestration Patterns, Templates, Automation
Monitoring Proactive, Autoscaling Policies
Audit/Control Regulatory Requirements
Backup SLA aspects, Scheduling, Data Loss Issues
Compliance Regulatory Requirements e.g. Geo Placement
Configuration Management Processes, Regulatory Aspects, Governance
Security Policies, IAM, Encryption, Privacy, Isolation
Price/Cost Migration Cost, Off Premise Cost, Resources
Interoperability/Integration Data Security, Availability Considerations
Viability Flexibility, Technology Evolution, Organization

Cloud Delivery Considerations
I
a
a
S
Existing code/middleware
Networking/Security functions
Complex deployment
No capability to easily move to
bare metal/virtualized
Large number of interfaces
P
a
a
S
“Cloud native”
Polygot requirements
Integration to on prem data
Innovative/agile organization
Existing application/middleware
Security/Process Constraints
Traditional Tools/Methods
S
a
a
S
Requirements met by package
Middleware As A Service
XaaS
Customization Needed
External Integration
Security Concerns (Data)
Focus is primarily on
Functional Requirements

Cloud Deployment Considerations (Off Premise)
Focus is primarily on
Nonfunctional Requirements
(e.g. security, availability,
performance)

Orchestration Services
(and Patterns/Templates)
Development Tools
On Premises Infrastructure
Middleware Platform Svcs
DevOps and Testing SolutionsDevelopmentOperations
OpenStack
Hybrid Oﬀ Premises On Premises Tradi7onal IT
Defining the “Cloud Technology Stack”
Virtualization and Containers
PaaS

Sensitive data
Complex processes and
transactions
Regulation-sensitive
Not yet virtualized
third-party software
Highly customized
Analytics
Collaboration
Development and test
Workplace, desktop, and
devices
Infrastructure
storage
Infrastructure
compute
Business processes
Industry applications
Preproduction
systems
Information-
intensive
Isolated
workloads
Mature
workloads
Batch
processing
New workloads
made possible by
clouds…Medical imaging
Financial risk
Collaborative care
Energy management
Disaster recovery
Ready
for cloud…
May not yet
be ready
for migration…
Cloud Workload Assessment

Twelve Key Questions to Assess Overall Cloud
Affinity of a Workload
1.  How self-contained is the workload?
2.  What are the scalability requirements for this workload?
3.  How standardized can the underlying IT infrastructure be?
4.  How standardized is the workload itself?
5.  How differentiated is the workload [is it a source of competitive advantage]?
6.  Is the workload available as an application or business process on the cloud?
7.  Does the organization have strong motivation to move the workload to run in multi-tenant
environment to improve operational efficiency and for long-term cost reduction or any other
positive reasons?
8.  What is the size of the migration/transformation effort?
9.  What are the data transfer requirements for the workload?
10. To what degree does the workload require adherence to performance and support non-
functional requirements (NFRs)?
11. How large is the benefit of rapid application deployment for this workload?
12. Does the workload require strong control to meet compliance or regulatory requirements?

Kyle Brown’s 9 Criteria for Cloud-ready Applications
1.  Application’s design is topology-agnostic
–  Ex: Clustering is supported, no specific cluster size needed
2.  Application’s management is infrastructure-agnostic
–  Ex: Doesn’t depend on IP addresses, hostnames, or VLANs
3.  Application doesn't use infrastructure-specific APIs
4.  Application doesn't use OS-specific features
5.  Application doesn't use the local file system
6.  Application logs to persistent storage, not the file system
7.  Application keeps session state only in the interaction layer
8.  Application components connect via standard protocols
9.  Application’s installation and configuration is scripted
–  Ex: Deployment is easily repeatable
http://www.ibm.com/developerworks/websphere/techjournal/1404_brown/1404_brown.html

Microservices and Cloud Native Applications
UI Team
Middleware
DBAs
•  Aligns to 12 Factor App – http://12factor.net
•  Monolithic application challenges
•  Design/Deployment Challenges (limits flexibility)
•  Scaling challenges due to coarse granularity
•  Microservices enable decoupled services
•  Running in isolated VM or lightweight container
•  Communicating via REST APIs
•  Can be deployed independently
•  Independently replaceable and upgradeable
•  Dependencies can be easily tracked
•  Team “owns” for lifetime (DevOps model)
http://martinfowler.com/articles/microservices.html

Organizational Alignment
•  Cloud drives organization transformation
–  Requires people & process changes
–  Probably the BIGGEST obstacle for clients
•  Transformation of people and processes
–  Often domain/workload/application specific
–  Transforms current roles/responsibilities
•  Moving to cloud successfully requires
–  Transforming Roles and Responsibilities
–  Creating a “Culture” to Drive Action
–  New/Enhanced Governance for Cloud

Building the Perfect Cloud Agenda
–  Defining The Cloud Journey
–  Lessons Learned
–  Where to now ….

Defining the Cloud Journey
Use Cases KPIs Experience
ValidationReasons to Act
Strategy/Capabilities
Strategize how to
target and integrate
cloud.
Architectural
decisions
Governance and
organizational impact
Cloud design
Management
framework
(Validated) Cloud
direction and scope
Identified cloud
opportunities
Cloud service
delivery strategy
Prioritized
workloads
Gap analysis Business case
Envision Evaluate DesignOutline
TacticalAdoption/Pilot
ExpansionImplementationSolutioningFacilitated Trial / PoC
Solution
Discussion
Architectural
decisions Business caseCloud design
Management
framework
Tactical Adoption / Pilot projects will commence at various points in the Strategy discussions/activities of the client
Start adopting low
hanging fruits to get
early benefits,
validate maturity and
fuel upper stream.

Lessons Learned On Cloud Planning and Design
•  Planning: Cloud Adoption is Strategic and Tactical
–  Build a solid business case and cost justification
–  Define organizational aspects and governance
–  Define the cloud management approach
•  Design: Define a Solid Architectural Approach
–  Define architectural requirements and decisions
–  Execute a service portfolio/workload assessment
–  Design conceptual and operational architecture
–  Determine migration approach and pilot
–  Define approach to Cloud Native applications
•  Execute: Enable the Organization
–  Establish training/skills to support target
–  Implement governance and organizational aspects

“Don’t Be The Slowest Zebra”
•  Closing thoughts ….
–  Cloud is not “magic”
–  Architecture is critical for success
–  Cloud is more than just technology
–  Standards enables future flexibility
–  Organizational transformation is key
•  Building the Perfect Cloud …
–  Not sure if a “Perfect Cloud” exists
–  But there are some good implmentations
–  Proceed with haste … and proceed with care

Assorted
Resources
And
References
Thoughts on Cloud
http://www.thoughtsoncloud.com/
K Brown – Top 9 Rules for Cloud Applications
http://www.ibm.com/developerworks/websphere/techjournal/
1404_brown/1404_brown.html
Microservices Forum
http://microservices.io/index.html
Cloud Standards Customer Council
http://www.cloud-council.org/
Open Container Initiative
https://www.opencontainers.org/
Open Stack
https://www.openstack.org/
http://www.networkworld.com/article/2983880/cloud-computing/the-
openstack-trade-off.html
Microservices
http://ibmsystemsmag.com/Blogs/IT-Trendz/September-2015/
Microservices-and-the-Development-Lifecycle/
Dzone – A Great Site for Architects and Cloud SMEs …
https://dzone.com/?oid=top_logo

© 2015 IBM Corporation
Your feedback is valuable
Please complete your session or lab evaluation!
CLOUD 122 Building the Perfect Cloud
Provide your evaluations by:
Evaluation forms:
Fill out a form at the end of each
session
Paper forms are located in each of the
session or lab rooms
Complete the session survey on
Event Connect Portal:
https://ibmeventconnect.com/
dublinevent2015
Select Sessions, then Session Finder,
and complete the survey
- Or
-

Cloud 122 building the perfect cloud

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (9)

Similaire à Cloud 122 building the perfect cloud

Similaire à Cloud 122 building the perfect cloud (20)

Plus de Scott Simmons

Plus de Scott Simmons (8)

Dernier

Dernier (20)

Cloud 122 building the perfect cloud