Cloud initiatives are beginning to dominate enterprise IT roadmaps. Successful adoption of Cloud and the subsequent governance challenges warrant a Cloud reference architecture that is applied consistently across the enterprise. This presentation will answer questions such as what exactly a Cloud is, why you need it, what changes it will bring to the enterprise, and what the key capabilities of a Cloud infrastructure are - using Oracle's Cloud Reference Architecture, which is part of the IT Strategies from Oracle (ITSO) Cloud Enterprise Technology Strategy (ETS).
Raspberry Pi 5: Challenges and Solutions in Bringing up an OpenGL/Vulkan Driv...
Oracle Cloud Reference Architecture
1.
2. <Insert Picture Here>
Oracle Cloud Reference Architecture
Build your Cloud – the right way!
Anbu Krishnaswamy Anbarasu
Enterprise Architect
Global Enterprise Architecture Program, Oracle Corporation
Architect Day – Reston – May 2012
3. Agenda
1. Introduction
2. Evolution to Cloud-based IT
3. IT Strategies from Oracle (ITSO) and Oracle
Reference Architecture (ORA)
4. Oracle Cloud Reference Architecture
5. Case Study – Oracle Public Cloud
6. Summary
5. NIST Definition of Cloud Computing
Cloud computing is a model for enabling convenient, on-
demand network access to a shared pool of configurable
computing resources (e.g., networks, servers, storage,
applications, and services) that can be rapidly provisioned
and released with minimal management effort or service
provider interaction.
5 Essential Characteristics 3 Service Models 4 Deployment Models
• On-demand self-service • SaaS • Public Cloud
• Resource pooling • PaaS • Private Cloud
• Rapid elasticity • IaaS • Community Cloud
• Measured service • Hybrid Cloud
• Broad network access
Source: NIST Definition of Cloud Computing v15
6. Definition of “Cloud Service”
Cloud services are self-contained units of functionality or IT
capability offered through cloud computing to its consumers.
Cloud service offerings range from managed units of
computing infrastructure (such as storage) through
platforms (database, web containers, etc.) all the way to
complete software solutions (e.g. finance, HR, etc)
• Cloud Services don’t necessarily refer to
• SOA Services
• Web Services
• Helpdesk Services
• …
8. Cloud Evolution
Dimension Cloud Difference
Business Model
CAPEX Vs OPEX, Metering,
Chargeback, and Billing
Level of Automation High Degree
Style of IT Service Management Self Service, Consumer centric
Scale and Velocity Massive and Fast – Policy Driven
Organizational Roles Dev-Ops Shift
Multiple levels, Heavy Resource
Multi-tenancy
Sharing
9. Cloud Difference
Shared IT Private Public Hybrid
Location On Premise On Premise External Both
Cost Allocation Centralized Budget Chargeback Billing Both
Initial Outlay High High Low Medium
Cost Model CAPEX CAPEX OPEX CAPEX/OPEX
Automation Low/Med High High High
Service Manual/Slow Self-service Self-service Self-service
Management
Scale Low Medium High High
Velocity Slow Fast Fast Fast
IT Roles Dev–Ops divide Dev-Ops shift Dev-Ops shift Dev-Ops shift
Efficiency Medium High High High
Operations Self Self Provider Both
Security Risk Low Low Med/High Med/High
Multi-tenancy Across LOB Across LOB With other With Other
customers customers
10. Deploying Applications in Traditional
Environments
1 to 2 Months
1-5 Weeks 1-2 days 1-5 days 1-5 days 1-2 days Start
• Manual, Error Prone, Non-repeatable
11. Deploying Applications in Virtual
Environments
1 to 2 weeks
1-5 days 1-2 days 1-5 days 1 day 1-2 days Start
• Faster but still - Manual, Error Prone, Non-repeatable
12. Traditional Vs Cloud Deployment
Specify and procure Platform-as-a-Service
hardware Deployment
Traditional App Deployment (User driven)
(Admin driven)
DEPLOYMENT
PORTAL
Configure hardware
Request App
Deployment via Cloud
Deploy hardware
Middleware JEE
Adjust capacity as
Deploy middleware and demand changes App
Database database
OS/Machines
Retire app when
Deploy app and configure not needed
settings
User unaware of
Add hardware and reconfigure underlying
stack as demand grows infrastructure Self-Service Provisioning
16. Enterprise Technology Strategy (ETS)
Interaction
A
E B
Enterprise Management
Enterprise Development
Business Processes
Enterprise Security
D C
Business Services
Practitioner Maturity Method
Guides Model Development Application Infrastructure
Information Assets
ORA
Information Management
Perspective
Shared Infrastructure
Customer Field Tools
Enablement Enablement
Oracle Reference Architecture
35. Enterprise Manager Cloud Control
Cloud Management
Cloud Management
3rd
Oracle ISV Enterprise Manager
Party
Applications Apps
Apps
Application
Performance Self-Service
Management
Platform as a Service
Lifecycle
Chargeback
Management
Oracle Fusion Middleware
Configuration Resource
Management Scheduling
Oracle Database
Application Quality
Capacity Planning
Management
Infrastructure as a Service
Ops Center
Physical & Virtual
Systems
Management
36. Engineered Systems in the Cloud
Extreme performance for Cloud Services
• Reference configuration
• Known sizing
• Order as ‘part number’
• Unified support
• Simplified deployment
• Run existing apps
• Enterprise scale
• High performance
37. Oracle Virtual Assembly Builder
Automating Deployment of Deployment Models
config1
config2
Assembly =
Appliances
(VM Templates +
Dev/Test configuration
Environment Metadata) +
relationships & Production
start order Environments
Metadata
• 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 instance has well-contained configuration parameters for flexibility
40. Summary
ITSO – Unified Reference
Evolution – Understand
Architecture to build
the evolution of IT to
solutions to support your
Cloud and what it
business
means to you
Oracle Cloud Reference Oracle Products –
Architecture – helps you enable you to build
manage, govern, and enterprise-grade private
accelerate Cloud and public Clouds
Adoption
For more information on Oracle Reference Architecture (ORA), please
visit http://www.oracle.com/goto/itstrategies
41. The preceding 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 remains at the sole discretion of Oracle.