cloud interoperability demo at ogf29

OGF29 – Cloud Standards Interoperability Demo

OCCI, CDMI & OpenNebula

Chicago, June 20-22, 2010

Agenda

1. Intro – Krishna Sankar

2. CDMI – Mark Carlson

3. CDMI iPad Client Demo – Rich Ramos

4. OCCI – Thijs Metch

5. JavaFX Client Demo – David Moolenaar

Cloud Interoperability

• Always on the top on everybody’s mind

– Just after security, compliance & control

• This demo is a first step

• Not how well the bears dance, but the fact that they could dance !

• CDMI/OCCI working across the storage and compute clouds

– CDMI Storage primitives (incl allocation, access, rules, policies, constraints …)

– OCCI – CSP interface

Demo Architecture

FileBasedProvider

FS

CDMI LibraryOCCILayer

SPI Layer

Glue Code

Server Framework

Client S/W

200

400

420

410

430

510500

300

100

OCCI 310

JClouds

460

470

CDMI320

Future !

JavaFXGUI

OCCI

Open Nebula

CDMI

SNIARI

Storage

2 or 3 client machines

Cloud Layer Software Compute & Hosting Infrastructure

Storage

Client Software •OCCI – Open Nebula•CDMI RI •Glue code between

•Raw Intel based machines (Sun Solaris)•Virtual Machine instances

Glue Code

•Public Internet•Private Network

VMVM

VMVM

•Storage Array or NAS•Public Clouds (being proxied)

Demo Topology

Server Server JClouds

Future !

The Complete CDMI Picture

Model for the CDMI InterfaceThe resources which are accessed through the RESTful interface

CDMI Specification

• SNIA Architecture (industry standard):

– http://snia.org/cloud

– Implementations are under way

8

CDMI iPad Demo

Rich Ramos

Individual

ogf29@RichRamos.com

CDMI iPad Client: Goals

1. Primarily Instructional on CDMI

2. Not General Purpose “Cloud Storage” Client

3. Show Network Interactions

4. Show Object Information

5. Provide CDMI Object Library (future)

What is OCCI?

• Open Cloud Computing Interface

– Becoming OGF proposed standard

• OCCI provides features to identify, link and categorize “dumb RESTful resources”

• OCCI-infrastructure defines kinds, actions, & attributes to work with virtual machines

CDMI in Cloud Computing

12

A single cloud computing

infrastructure can implement

both the OCCI and CDMI

interfaces

The infrastructure abstracts

the configuration of the

networking and virtual

machine details and uses the

standard interface merely to

define connectivity

A cloud computing client can

then utilize the interfaces to

both specify the data

requirements and then use

that data for guests

OpenNebulaOpen-Source Toolkit for Building Cloud Infrastructures

• Open Source Created and Supported at the University of Madrid under Dr. Rubén S. Montero & Dr.Ignacio M. Llorente. CDMI Integration Provided by Gary.Mazzaferro @AlloyCloud .com

• Orchestrates storage, network and virtualization technologies to enable the dynamic placement ofmulti-tier services on distributed infrastructures, combining both data center resources and remotecloud resources, according to allocation policies

• Provides internal and Cloud administration and user interfaces for the full management of the IaaSCloud platform

• Private Cloud: Management of

virtual infrastructure in the data-

center or cluster

• Hybrid Cloud : Combination of

private with Cloud resources

• Public Cloud: Cloud interfaces for

the full management of services

CDMI OCCI/OpenNebula Integration

Virtual Infrastructure Manager

OCCICloud

InterfaceScheduler

Virtualization

Local User and

Administrator Interface

Storage Networking

Virtualization Servers

SPI Layer

NFSProviders

NFS

Protocol

Provider Exports

Glue

• Custom Glue Interface

• NFS Provider

• Guest Integration

•“Create” Function Supported

CDMI OCCI/OpenNebula Integration Future Version

Virtual Infrastructure Manager

OCCICloud

InterfaceScheduler

Virtualization

Local User and

Administrator Interface

Storage Networking

Virtualization Servers(XEN, Amazon, Vmware, VirtualBox)

SPI Layer

FileBasedProviders

Provider API

File Protocols

BlockBasedProviders

DataBasedProviders

Block Protocols

Data Protocols

The Client

A Standards Based Cloud Client

Used JavaFX

Developed by R2AD, LLC

Sponsored by DISA CTO

cloud.r2ad.net

Client Requirements• Simple/Small

– Implement use-case (first with simple get/put)

– Keep UI footprint small – potential phone app

– UI became more sophisticated with experience

April 2010 May 2010

Flat list to Tree

Added Tabs

Icons

Edit Resource Location

Learning JavaFX

Authentication Models

Added Log

June 2010

Client Interactions• Required to communicate with OCCI + CDMI

– Clear specifications and examples very helpful

– Used local test server to code up initial GET/PUT

– Use case driven (keeping goals on target)

Login

Create Storage Use case

Get Compute

Get Storage

Create Virtual

Machine Use caseManage

Cloud

OCCI server

CDMI server

http http

http http

XML

JSON

JavaFX Client Demo

Client Lesson Learned• Code for network not being reliable

– Let user cancel requests. Timeouts.

– Use local cache or persistence?

• Use of remote admin tools helpful

– ssh terminal, vSphere admin console

– Virtual Desktop Interface (VDI)

• Teleclient Solution w/Sun Secure Global Desktop or VNC

• Virtual Machines for servers helpful

– Snapshots, transportability, etc.

• Way Ahead:

– Make code more efficient (reduce server calls, parsing)

– More integration with OCCI/CDMI – more features. security

– Looking for feedback and chance to develop more