Cloud Computing - Making IT Simple

<Insert Picture Here>

OTN Architect Day
Cloud Computing - Making IT Simple
Dr. James Baty
VP, Oracle Global Enterprise Arch. Pgm.

The following is intended to outline our general
product direction. It is intended for information
purposes only, and may not be incorporated into any
contract. It is not a commitment to deliver any
material, code, or functionality, and should not be
relied upon in making purchasing decisions.
The development, release, and timing of any
features or functionality described for Oracle‟s
products remain at the sole discretion of Oracle.

© 2011 Oracle Cloud Computing – Making IT Simple 2

Oracle Cloud Strategy

• Deliver systems and software to build public and private clouds
- Oracle ExaLogic and Oracle Exadata for IaaS
- Oracle Fusion Middleware and Oracle Database for PaaS
- Oracle Fusion Applications for SaaS

• Ensure that cloud computing is fully enterprise grade
- Highly efficient, performant, available, scalable and secure infrastructure
- Complete, integrated, and standards-based development platform
- Modern set of enterprise applications, including social and mobile

• Provide flexible consumption choices
- Private cloud, “as-a-Service” from Oracle Partners or Oracle directly
- Flexibility to move applications between these choices


How key is standardization?
What are Deployable Entities?
„Refactoring‟ Dev / Ops Roles
Building a Roadmap to Cloud


Roadmap to Cloud
Multi-Dimensional Journey

Optimize

Automate

Consolidate
Achieve new
Standardize Reduce the operational
manual tasks models &
Reduce the for managing greatest
Define a footprint of IT efficiency
single solution deployed
for a given applications
problem

Individual enterprises or applications may join the roadmap at different points


Moving to Cloud
First Inventory Applications & Workloads
Suitable for cloud now Not as suitable for cloud
Time based Vertically scaled applications
Very parallel (i.e. batch) Consistent load levels
Spiky traffic Latency sensitive applications
Capital intensive (especially Insecure applications
startup)
Hardware device dependent (e.g.
Proof of Concept fax server, SNA gateway)
Low utilization ISV unsupported
Less deployment costs Per CPU licensed applications
High bandwidth costs / high real
estate


What Do You Want the Cloud to Do?
Start with Common Use Cases
Augmentation
(Elastic scaling)

Shared Services

Development
and Test
Resource sharing
(consolidation)

Most enterprises are trying
• Shared development and test environments
• Hardware & Services consolidation


Shared Services – Many Possibilities

Shared •Sharing Applications across org
Functions •Enabled by SOA, BPM

Java PaaS •Build & deploy to common platform
•Enterprise Private Cloud

Shared SOA •Application services integration

X X •Centralized authorization for
Shared Security X all apps
X X XX

DBaaS •Rapid access to all enterprise data
•Parallel Processing of Transactions


Private Database Cloud Architectures
Common Building Blocks - Shared Server & Storage Pools

DW CRM ERP DW ERP CRM DW ERP CRM
DB

DB

DB

DB
DB

DB

DB
OS OS OS

Hypervisor Hypervisor OS OS OS OS

Server Operating System Database
Deploy in dedicated VMs Share server pool Share database instance
Server virtualization Real Application Clusters Real Application Clusters


Which Apps for Which DB Cloud?
Each Architecture Serves Different Workloads

Workload Type Optimal Cloud
Architecture
Mission or Business Critical Deployment Operating System
Packaged Applications Operating System
Data Warehouse Applications Operating System
Operating System
Standardized environment
or Database
Internal Applications Database
Rapid provisioning (i.e. Test and Dev) Database or Server
Mixed workload consolidation Server
As-Is consolidation Server


Database Cloud Planning
Identification of Applications to Migrate
- New applications are deployed to the Cloud
- Existing applications are migrated based on:
• Difficulty
• ROI
• Suitability
- The benefits and difficulties of consolidating existing
applications in the Cloud will vary
• Applications with highly varying peaks will show
greatest benefit
- The “lowest hanging fruit” should be migrated to the
Cloud first


Engineered Systems in the Cloud
Extreme performance PaaS services

• Reference configuration
• Known sizing
• Order as ‘part number’
• Unified support
• Simplified deployment
• Run existing apps
• Enterprise scale
• High performance


Build from Scratch vs. Exadata
Commonwealth Bank of Australia
Build From Scratch Reference Oracle Exadata
with Components Configurations Database Machine

Testing and
Validation  Server Pool pre-configured
 Faster deployment
Installation and Testing and  Lower Risk
configuration Validation
Acquisition of
components Installation and
configuration
Testing and Validation
Pre-implementation
Acquisition of Configuration
System sizing
components Take delivery of Oracle
Database Machine
Weeks to Months Weeks to Months < 1 Week after Delivery

•DB deployment time reduced from 3 months to < 1 week


How key is standardization?


Cloud Architecture - Logical View
Interfaces Portals Custom UIs Self-Service APIs
Access

Native Protocols

Facilities Proxy Perimeter Security Naming Balancing

User Interaction / self service

Security and
Business
SaaS Business Process Business Service Application Policy Mgmt
Mgmt

Cloud Management
Security, Policy
Customer, Contracts, Mgmt, Security
Services

Revenue Mgmt Services
PaaS Container Queue Data
Orchestration
Operations Orchestration,
IaaS
Mediation
Server Network Storage Service Mgmt,
Capacity Mgmt, Design-time
Service Support
Deployable Entities Model Mgmt, Tools
Resources

Logical Pools Compute Networks Storage Other Clouds External
Pool
Managers Legacy

Physical Pools Compute Networks Storage Other Partners


Cloud Architecture - Logical View
Interfaces Portals Custom UIs Self-Service APIs
Access

Native Protocols

Facilities Proxy Perimeter Security Naming Balancing

User Interaction / self service

SaaS Business Process Business Service Application
Business Security and

Cloud Management
Mgmt Policy Mgmt
Services

PaaS Container Queue Data

Orchestration
IaaS Server Network Storage Operations
Design-time
Deployable Entities
Resources

Logical Pools Compute Networks Storage Other Clouds External
Pool
Managers Legacy

Physical Pools Compute Networks Storage Other Partners


Key abstractions – Making IT Simple
– Architecture concepts and portability issues
APIs
Separation of roles Code deployment,
(e.g., Cloud Provider developer discovery and
vs Service application control
Developer)

Deployable Entities Images
(aka VDCs) include Application and data
Service Templates deployment
and Context (e.g.
„Assemblies‟)

Separation of Model
control plane Architectural models
„cloud‟ vs „pool‟ may be external,
mgmt embedded, or internal

Logical ‘pools’
abstraction of
physical resources
Services
Data
Run time services
Access and formatting of may be absent or
data may differ significantly different


Service Catalogue
More than just images

• Repository of models
• Models contain
templates and
service contracts
- Payloads like virtual
server images
- Application metadata
such as configurations
and policies


Model / Service Management
Similar but separate
• Model management supports • Service management controls
design-time functions in cloud the run-time aspects of the cloud
- Exposes resources to developers - Capacity management
- Stores developer’s models for - Service management
deployment
• Operator’s main point of contact
- Validates cloud models
for the cloud
• Developer’s main point of
• Provisions / monitors resource tier
interaction with the cloud
• Contains configuration
• Model management also
management repository which is
contains the solution catalogue,
the current state of all cloud vDCs
facilitating discovery, storage,
use and re-use of cloud
services


Oracle Virtual Assembly Builder
Automating deployment of ‘assemblies’
config1

config2

Assembly =
Appliances
(VM Templates +
Dev/Test configuration
Environment Metadata) +
relationships & start
order Metadata Production
Environments
• Package up complex structure from dev/test and reconstitute in production
• Minimize setup time and risk of hard-to-debug configuration errors
• Easily replicate in production with minor variations
• Each production instance has well-contained configuration parameters for
flexibility


How Key is Standardization?
‘Refactoring’ Dev / Ops Roles


Identify Roles and Interactions
– Cloud implies changes in IT roles
Models Service

DevOps
App Owner Developer
Monitors & Creates Services Packages &
User Approves Services Deploys Services

uses
service
Monitor/manages cloud

Cloud Operator

creates resources

Cloud Builder


Design time vs run time perspectives
– need to separate development / operations horizons
BUILD
Process Modeling, Simulation
TIME
and Documentation Service
Developer

Application
Owner

Service Identification &
Discovery
End
Users
Service
Deployer

RUN
TIME Cloud Monitoring and
Metrics
Cloud Deployment Engineering
Cloud Builder
Operator


Cloud Roles / Actors
– each role category has possible sub-roles

Category Actor DMTF Roles
Cloud Service Operator Service Operations Mgr
Provider
Builder Service Business Mgr

Service Transition Mgr
Cloud Service Service Developer
Developer Service Developer
Deployer / DevOps
Cloud Service Consumer Business Mgr
Consumer Application Owner
Consumer Service Admin
User Service User


Example of Design vs Run Time
– Oracle Virtual Assembly Builder roles
1. Set Up Cloud 2. Build App RUN TIME
Build app using App 3. Use App
shared Developer
components
IT
Set up Cloud Set up self-
Platform service portal Dept Use app App Users
Set up
shared
App
components Deploy using
self service
4. Manage App
DESIGN Shared Components Self-Service Interface
TIME Integration / Security &
BPM Portal App Owner
SOA Identity
Manage
Application Server System
Oracle Cloud Platform Manager
Adjust
Capacity
Database Review
Charge-back
Operating System,Virtualization,Server,Storage


How Key is Standardization?


Cloud Computing Readiness
May Require Diverse Business Changes
 Consider, for example, IT governance & risk management,
information modeling & ownership, operations & service
management.
 How are these areas managed today?
• identified responsibilities, documented processes, etc.
 Do you have a mechanism for assessing capabilities in
each area?
 How will you identify needs for changes or improvements
to support cloud computing?


Example Cloud Capabilities by Domain
Areas Important to Cloud Readiness
Reference architecture Business & IT drives
Standards Costs & Benefits
Business
Architecture &
Strategy
Model templates Executive sponsorship
Data ownership Roles & responsibilities
Information Organization

Infrastructure Governance
Model packaging
Risk management
Service monitoring
Cloud change management
Operations Services

Capacity management Services portfolio management
Operational tools & processes Services engineering approach

• To succeed at Cloud services adoption, an organization must
adequately progress in all the appropriate domains.


Cloud Computing Roadmap
How Will Your Cloud Be Introduced?
Cloud computing efforts range from small ‘experiment’
projects to major strategic initiatives.
Most companies have multiple projects underway or
anticipated.
• Separate from the new architecture, is there a plan for
how the new model will be rolled out?
• E.g., by application, by business unit, by geography…
• Is cloud viewed as a limited tactical deployment, major
strategic initiative, or both?


Focused Implementation Vs. Wide Diffusion
Optimized
Cloud

Managed Strategic
Maturity

Cloud Exploiting
Cloud

Systematic
Cloud
Expanding
Opportunistic
Cloud

Ad Hoc Exploring Tactical
Cloud

Application Suite Data Center Region Enterprise
Level Level Level Level Level
Cloud Adoption
• Strategic – Complete migration for a given architecture/application,
often focusing on revenue enhancement
• Tactical – Wide deployment of a limited technology (e.g. virtualization),
often focusing on cost reduction


Key Business/IT Transformations
Current Approach Cloud Approach
IT Architecture designed Build infrastructure up-front,
up front (early binding) deploy later (late binding)

IT operations developed IT will move to building up-
and performed by the IT front operational functions for
department a self-service model.

Systems and application The cloud „control plane‟ has
management was specific to be architected as a general
to select systems and service
applications


‘Enterprise’ Clouds are Different
– a final thought SaaS
Saa
I

• NIST identifies 5 essential cloud characteristics N
T
R PaaS
Paa
- On-demand self-service, Resource pooling, Rapid elasticity,
A
N
E
Measured service, Broad network access T IaaS
Iaa

• But enterprise clouds are different from general public clouds…
- E.g., On-demand self service
• Public developer cloud – unrestricted resources provisioned in minutes, but
with no controls or corporate governance
• Enterprise private cloud – need provisioning controls, standards
enforcement, prioritization, approvals, etc.
- I.e., Enterprise cloud faster to deploy than traditional IT, but more structured than
public developer clouds

• There are other criteria with similar differences
- Security, governance, high availability, global access ….


For More Information….

oracle.com/cloud


Cloud Computing - Making IT Simple

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Cloud Computing - Making IT Simple

Similar to Cloud Computing - Making IT Simple (20)

More from Bob Rhubart

More from Bob Rhubart (20)

Recently uploaded

Recently uploaded (20)

Cloud Computing - Making IT Simple