RSpecs for Storage Resources

GEC 11RSpec

July 27th, 2011

Michael Zinkzink@ecs.umass.edu

2

Motivation DiCloud offers AWS S3 and EBS storage for GENI

experimenters

ViSE Sensor NetworkS3 (storage)

EC2 servers

Researcher creates a slice with:• weather radar • storage space on S3• compute servers on EC2

OrcaDiCloud

3

Getting started

What kind of storage will be offered in GENI? One option: AWS S3 and EBS through DiCloud

Extend Orca with

• Data-centric Slices: storage as a first-class resource

with Amazon Simple Storage Service (S3) and Elastic

Block Storage (EBS)

• Cloud Computing: connect Amazon Elastic Compute

Cloud (EC2) resources to GENI

4

DiCloud Example

Obviously AWS S3 and EBS do not offer RSpecs DiCloud can serve as an RSpec translator

• Goal: Create RSpec V2 conformant resource description of available S3 and EBS storage resources.

Should also work for Eucalyptus clusters:• Eucalyptus’ Block Storage Service interface is

compatible with EBS.• Walrus is interface compatible with S3.

5

Proposal

Create RSpecs for S3 and EBS which are accessible via DiCloud as a starting point

Goal:• Keep it as general and extensible as possible• Provide working implementation in short-term future

Potential:• Storage RSpec could be adopted by other GENI cloud

services• Could be prototype for storage in GENI racks• Available in Orca CF

6

Example

7

Example for Sensor Nodes

8

Challenges

What security model for storage in the cloud?

• How to share data with others?

• Storage leases can last years

What if hard guarantees are required?

• E.g., user wants minimum I/O bandwidth for slice

9

Future Plans

Discuss storage RSpecs for ProtoGENI Discuss storage RSpecs for sensor networks Coordinate with measurement RSpec activities Start integration into RSpec V2 Provide update at GEC12