OMG Cloud Interoperability Workshop:
Defining an End-to-End Cloud
with Web Architecture
Stuart Charlton
Chief Software Architect & VP Products, Elastra
The Enterprise Cloud Company www.elastra.com

Agenda
• Enterprise Cloud Computing
• Why End-to-End?
» The Cloud as a System-of-Systems Architecture
» Global, Interoperable Cloud Deployments
• The Interoperability Challenge
» Possible Areas of Consensus & Risks
• Case Study: Resource Reservation & Provisioning
» Elastic Deployment Markup Language (EDML)
» Elastic Platform Provider Interface (PPI)
» A Platform Architecture for Interoperable Hybrid Clouds
2 OMG Cloud Interoperability Workshop www.elastra.com

About Elastra
• San Francisco-based startup, founded 2007
• $15 million in combined Series A & B Funding
• Broad Industry Expertise in Management Team
» Ex. BEA, Oracle, Sun Microsystems, EMC, Plumtree
• Software Products for Enterprise Cloud Computing
3 OMG Cloud Interoperability Workshop www.elastra.com

Enterprise Cloud Computing
Consumption, Plan & DCA
EA Portfolio of
ning, Improvement Standards &
s Policies Virtualized
System Lifecycles APPLICATION Private Clouds
Hyperlinked Models RESOURCES
IT OPS MGT APP ARCH
& Metadata
Improved End-to-End Policies
Service Policy-Based
IT OPS Design with
Delivery with
Flexibility Dynamic Availability Public Clouds
Control Efficient Consumption
Metering Servers Application
& Billing Storage VMs
ENABLING BUSINESS TRANSFORMATION
• Resetting the Cost Structure: Decoupling Fixed Costs from Variable Consumption
• Driving Down Lead Times & Acquisition Times
• Increasing Visibility in IT & Business Service Management
4 www.elastra.com

Helping Drive a Collaborative Process
ENTERPRISE IT OPERATIONS
ARCHITECTS
Change &
Standard
Configuration
APPLICATION Designs
Management
ARCHITECTS IT MANAGEMENT
Policy-Based End-to-End Auditing, Me
Architectural Collaborative tering, and
Designs IT Service Planning
Model
DEV/QA TEAMS Automated Planning, SYSTEM ADMINS
Provision & Configuration
Code, Resou Deploy &
rces, Configure
& Builds Systems
ENTERPRISE CLOUD
Test System Staging System Production System
Private & Public Cloud Resources
5 www.elastra.com

Why End-to-End?
Tackling a System-of-Systems Architecture
• System-of-System Characteristics (Mark Meier)
» Operational Independence of Elements
» Managerial Independence of Elements
» Evolutionary Development
» Emergent Behavior
» Geographic Distribution
• Some Heuristics for Architecture of SoS:
» Stable Intermediate Forms & Policy Triage
» Our Leverage is at the Interfaces
 “The greatest leverage in system architecting is at the
interfaces. The greatest dangers are also at the
interfaces.” (Rechtin)
6 OMG Cloud Interoperability Workshop www.elastra.com

Why End-to-End?
The Multi-Organizational Cloud Deployment
• Composite Applications span IT services & clouds
• Clouds are different shapes and sizes
» SaaS, PaaS, IaaS
• Interoperability Private cloud resources are essential
• What are the common patterns?
» Configuration Management
» Resource Management
» Data Integration
» Identity Federation & Trust
7 OMG Cloud Interoperability Workshop www.elastra.com

Why End-to-End?
Basis for Evolution of the Exposed Elements
• Lifecycle (e.g. ITIL, OSLC, etc.)
• Policy
» Reactive Constraints
» Proactive Plans
• Architecture
» Many Viewpoints!
• Packages & Images & Dependencies
» E.g. OVF
• Configurations (many shapes & sizes)
• Data Centre Resources (e.g. CIM)
8 OMG Cloud Interoperability Workshop www.elastra.com

The Interoperability Challenge:
Finding Areas of Consensus
• Areas of possible agreement
» Reservation & provision of resources
 Especially virtualized data centre infrastructure
 Question assumptions of existing standards
» Identity & Trust (Beware: bottomless pit)
» Licenses, Access Rights, and Payment
• Areas of active research & development
» IT & Business Service Lifecycle Management
 To what degree is ITIL v3 the last word?
» Configuration Management (Many Shapes & Sizes)
» Data & Application Integration
9 OMG Cloud Interoperability Workshop www.elastra.com

Example:
Licenses, Access Rights, & Payment
• Uniform Rights & Duties
foundation is possible
» E.g. Open Digital Rights
Language
• Beware Patents
» i.e. ContentGuard claims
patent on any access rights
language implementation
• Cloud could use targeted,
minimal, extensions for
payment & accounting ODRL v2 Core Model
10 OMG Cloud Interoperability Workshop www.elastra.com

The Risks of Standardized Boundaries
• Insert your favorite systems design aphorism:
» Inertia to create something new vs. reuse something existing
» Local optima don’t often lead to global optima
 E.g. The End-to-End Argument in Systems Design
» Tragic increase of artificial complexity
by neglecting increased natural complexity
 E.g. The Growth of VM Image Sprawl
» Waste elimination only occurs in the Gemba
(in the actual place where value is created)
 E.g. Lean manufacturing optimization
• These risks are occurring today (e.g. OVF Extensions)
11 OMG Cloud Interoperability Workshop www.elastra.com

The Web as a System-of-Systems Architecture
State/Representation
(at a point in time)
Information Space Uniformly Identifiable
Object (Resource)
12 OMG Cloud Interoperability Workshop www.elastra.com

Hyperlinked Cloud Markup Languages
Modular, layered, open-world, “connective tissue”
CONCEPT
IMPLEMENTATION
ECML
MARKUP Elastic Computing Markup Language
• Architecture description & configuration
ECML
DEFINE
EDML
Elastic Deployment Markup Language
EDML
• Element, Settings & Capability descriptions
EMML ELML
Elastic Licensing Markup Language
• Specify Rights & Duties of Consumers
ELML
EXTEND
EMML
Elastic Management Markup Language
• Configuration items & management processes
Interoperable via XML Markup / Grounded in OWL DL Ontology
Syndicated via Atom Feeds, Published via Atompub
13 OMG Cloud Interoperability Workshop www.elastra.com

Case Study:
Interoperable Cloud Reservation & Provisioning
• How do you balance differentiation with interop?
• Capability-Driven Matchmaking
» Resource Co-Allocation & Requirement Match
Cloud Consumer Required Capabilities
{64-bit, 8 GB RAM, 500 GB NAS, VLAN,
HIPAA Compliant}
Match
Published Capabilities
Data Center Resources {32 or 64-bit, 2 to 16 GB RAM, 18 TB NAS}
14 OMG Cloud Interoperability Workshop www.elastra.com

Elastra Cloud Server v2.x Conceptual Architecture
Application Architect Data Center Architect IT Manager Systems Administrator
USER INTERFACE
MARKUP COMPONENTS DATA
CORE
DESIGN
ECML DATABASE INFORMATION
DEPLOYMENT
EDML APP. TIER INFORMATION
SYSTEM
ELML USER TIER MANAGEMENT
INFORMATION
EMML SUPPORTING CAPABILITIES &
SERVICES CATEGORIES
COMPOSER DEPLOYER PUBLISHER
PLATFORM
PLATFORM PROVIDER INTERFACE
15 www.elastra.com

EDML
(Elastic Deployment Markup Language)
Settings Instance
Resource Container
Settings Template Resource Resource
Settings Provided
Requirement Capability
Required
Handler Capability
Reference
Data Center Resource Definitions
Package
Dependencies
16 OMG Cloud Interoperability Workshop www.elastra.com

Elastic Platform Provider Interface (PPI)
Entry Points
Object Manager
Tasks Registry
Provider Objects
Hypervisor Disk VM Operating System
VLAN Chip/Core
Data Center Resources
17 OMG Cloud Interoperability Workshop www.elastra.com

An Architecture for Interoperable Hybrid Clouds
RESTful Request for Atom Feed of
Consumer Provision or Change Available Bundles
EDML
Deployer Bundler
Elastra
(Matchmaking & (Structures Resources
Platform
Parallel Task Execution) for Co-Allocation)
Service
PPI
Amazon Storage&
Providers VMWare
EC2 Network ….
18 OMG Cloud Interoperability Workshop www.elastra.com

Licensing & Availability
• Elastic Markup Languages are in beta, available
under a Creative Commons Attribution License
to customers
• Elements of the Platform will be Released as
Open Source during Spring 2009
19 OMG Cloud Interoperability Workshop www.elastra.com

Thank You
stuartc@elastra.com
The Enterprise Cloud Company www.elastra.com