• No results found

Storage CloudSim: A Simulation Environment for Cloud Object Storage Infrastructures

N/A
N/A
Protected

Academic year: 2021

Share "Storage CloudSim: A Simulation Environment for Cloud Object Storage Infrastructures"

Copied!
25
0
0

Loading.... (view fulltext now)

Full text

(1)

STEINBUCH CENTRE FOR COMPUTING - SCC

Storage CloudSim: A Simulation Environment for

Cloud Object Storage Infrastructures

http://github.com/toebbel/StorageCloudSim

(2)

Agenda

Introduction & Use Cases Motivation

STaaS Simulation Concept Implementation

Evaluation

(3)

Cloud Computing and STaaS

Cloud computing: scalable hardware and service provisioning [5]

Deployment Models

Service Models

Storage as a Service (STaaS)

Online / near-line, non-volantine storage at low costs [6] Object or block storage

Private Community Public Hybrid

X+Y

Infrastructure Platform Software Iaa S Pa aS Sa aS VMs / STaaS

(4)

CDMI (Cloud Data Management Interface)

Standard API to access object STaaS, released by SNIA, 2012 [3] RESTful, HTTP based

Organizes objects in containers, user separation, access via IDs or names

(5)

CloudSim

Popular Java event-based simulation

environment for IaaS, developed by CLOUDS Lab at University of

Melbourne [1] [2] Lacks for STaaS modeling:

No standard Cloud user interface

Not realistic disk model No simulation of

concurrent use of bandwidths

(6)

Motivation

Simulations required to

Estimate costs for users in multi cloud scenarios

Compare different constellations of hardware components & policies

No known STaaS simulation environment

StorageCloudSim

Develop extension for CloudSim to simulate STaaS

Accurate models for servers & disks Realistic simulation of IO limitations Use of STaaS standards like CDMI Model multi-Cloud STaaS usage

(7)

Implementation - Class Diagram

StorageCloud CdmiRootContainer CdmiObjectContainer CdmiObject

CdmiMetadata CdmiEntity CdmiCloud-Characteristics StorageBlob StorageBlobLocation IObjectStorageDevice ObjectStorageServer CdmiRequest CdmiResponse ScheduleEntry <<create>> <<creates>> StorageBroker <<create>> <<receives>> StorageMetaBroker UserRequest <<processes>> <<creates>> / <<destroys>> UsageSequence SLARequirement <<processes>> <<forwards>> SLARequest * GETContainerRequest GETObjectRequest PUTObjectRequest DELETEObjectRequest ... TimeawareResource EventTracker TrackableResource UsageHistory TrackableResource ReportGenerator <<reads>> UsageSequenceFile-Generator <<creates XML for>>

(8)

Implementation - Components

StorageCloud CdmiRootContainer CdmiObjectContainer CdmiObject

CdmiMetadata CdmiEntity CdmiCloud-Characteristics StorageBlob StorageBlobLocation IObjectStorageDevice ObjectStorageServer CdmiRequest CdmiResponse ScheduleEntry <<create>> <<creates>> StorageBroker <<create>> <<receives>> StorageMetaBroker UserRequest <<processes>> <<creates>> / <<destroys>> UsageSequence SLARequirement <<processes>> <<forwards>> SLARequest * GETContainerRequest GETObjectRequest PUTObjectRequest DELETEObjectRequest ... TimeawareResource EventTracker TrackableResource UsageHistory TrackableResource ReportGenerator <<reads>> UsageSequenceFile-Generator <<creates XML for>>

Monitoring

CDMI

CDMI

Storage Models

Usage Models

(9)
(10)

Implementation - SLA based StaaS Brokering

SLA requirements are defined in UsageSquence

UsageSquence independent from each other

MetaBroker chooses best provider for each UsageSquence using SLA matching policies and SLA rankings

Example SLA matching policies:

Supports Capability (WebDav export, metadata modification, …)

Does not have Restriction (max. container/object size)

Max./min. allowed feature metric (max. latency, min bandwidth, max storage cots per GB,…)

Example SLA Ranking: Assign Score to each Cloud:

𝑠𝑐𝑜𝑟𝑒 = 𝑐𝑜𝑛𝑠𝑡

𝑝𝑟𝑖𝑐𝑒 𝑝𝑒𝑟 𝑠𝑡𝑜𝑟𝑒𝑑 𝐺𝐵

(11)

Evaluation – STaaS Clouds Setup

Modelling of a single- (Amazon S3) and multi-Cloud (all three) scenario Linear pricing model

Amazon S3 SCC intra Swift Cloud

#servers / #disks per server

6/6 1/3 4/4

write/read rate, write/read latency capacity per disk

156 MB/s 9.5 ms / 8.5 ms 2 TB 64 MB/s / 156 MB/s 11 ms / 9 ms 1 TB 156 MB/s 9.5 ms / 8.5 ms 2 TB # allowed replica 3 3 1

Max. obj. size Unlimited 16 GB unlimited

total capacity 72 TB 3 TB 32 TB $ per uploaded GB 0.0002 $ $ per stored GB $ per down. GB 0.05 $ 0.01 $ 0.04 $ 0.0002 $ 0.01 $ 0.1 $

(12)

Evaluation

– Modeled STaaS UsageSquences

Simulations with two types of UsageSquences

Three experiments: mixed (50, 500, 5000 input sequences), normal only and scientific only (250 input sequences)

Sequence A Sequence B

total traffic per sequence

Gamma distr. 𝛼 = 2, 𝛽 = 3,

max 15 GB

1..100 GB (uniform distr.)

upload-download ratio 3:1 uploads only

size of biggest object 1 KB .. 1 GB 1..100 GB (uniform distr.)

Idle time between two requests

10 ms – 30 s Bursts of 5 operations,

5-10 min idle between bursts

SLAs cdmi_create_container

cdmi_delete_container

SLA available capacity > Y

cdmi_create_container cdmi_delete_container No max_container_size max_object_size > X

SLA available capacity > Y

Rating 1 𝑠𝑡𝑜𝑟𝑒 + 1 𝑢𝑝𝑙𝑜𝑎𝑑 + 1 𝑑𝑜𝑤𝑛𝑙𝑜𝑎𝑑 1 𝑠𝑡𝑜𝑟𝑒 + 1 𝑢𝑝𝑙𝑜𝑎𝑑

(13)

Evaluation – Effect of Object Size

MetaBroker selects Clouds with lowest Costs with respect of SLA SCC Cloud selected for small objects as it is the cheapest Cloud For big objects, Swift is preferred to Amazon as it is cheaper

(14)

Evaluation – STaaS requests SLA Violations

Due to over capacity, all sequences after minute 28000 are declined. Only 15 requests failed due to SLA violation (object size can not be satisfied)

(15)

Evaluation – Total Usage Costs

Multi-Cloud is more cost-saving compared to single Cloud (in terms of costs per succeeded requests)

(16)

Evaluation

– Effect of UsageSquence Type

Restrictive SLA (as in Scientific sequences) leads not to cost-savings for the multi-Cloud usage

(17)

Conclusion

Development of STaaS extension for CloudSim simulation environment Modelling of different SLA requirements and SLA matching policies for STaaS Clouds

Evaluation of used Storage and costs for single and multi-Cloud

scenario with different UsageSquence types

Usage of multiple Clouds lead to cost-savings if SLA is not too restrictive

More complex SLA matching policies (location, throughput) More complex price models for STaaS

Dynamic Broker Decisions

Modeling of different storage controller policies (example: OpenStack

Swift Ring)

(18)

References

[1] Rodrigo N Calheiros, Rajiv Ranjan, Anton Beloglazov, C´esar AF De Rose, and Rajkumar Buyya. Cloudsim: a toolkit for modeling and

simulation of cloud computing environments and evaluation of resource provisioning algorithms. Software: Practice and Experience, 41(1):23–50, 2011.

[2] Rodrigo N Calheiros, Rajiv Ranjan, C´esar AF De Rose, and Rajkumar Buyya. Cloudsim: A novel framework for modeling and simulation of cloud computing infrastructures and services. arXiv preprint arXiv:0903.2525, 2009.

[3] Cloud Data Management Interface (CDMI) Version 1.0.2.

[4] Amazon Inc. Amazon s3, cloud computing storage for files, images, videos, 2013. [Online; accessed 17-July-2013].

[5] Peter Mell and Timothy Grance. The nist definition of cloud computing (draft). NIST special publication, 800(145):7, 2011.

[6] A. Schill and T. Springer. Verteilte Systeme: Grundlagen und Basistechnologien. Springer London, Limited, 2007.

(19)
(20)
(21)

Implementation – Storage Models

CdmiObject StorageBlob StorageBlobLocation IObjectStorageDevice ObjectStorageServer TimeawareResource

(22)

Implementation – Storage Models

StorageCloud CdmiRootContainer CdmiObjectContainer CdmiObject

CdmiMetadata CdmiEntity CdmiCloud-Characteristics CdmiRequest CdmiResponse ScheduleEntry <<create>> <<creates>> <<processes>>

(23)

Implementation – Usage Models

CdmiRequest CdmiResponse StorageBroker <<create>> <<receives>> StorageMetaBroker UserRequest <<processes>> <<creates>> / <<destroys>> UsageSequence SLARequirement <<forwards>> SLARequest * UsageSequenceFile-Generator <<creates XML for>> 1

(24)

Simulation Workflow

Usage-Sequences in XML Sequence-Generator Simulation Stat. Generator Sample Streams, Traces, Logs Plots, Logs, CSV ScenarioCloud

(25)

Implementation – Provider Side Hardware Modeling

Operation 2 Operation 3 Operation 1 t1 t2 t3 t4 t5 t7 100% 60% Used Capacity Time Operation 4 Operation 2 Operation 3 Operation 1 t1 t2 t3 t4 t5 t6 t7 t8 100% 60% Used Capacity Time Operation 5 Operation 4 Operation 2 Operation 3 Operation 1 t1 t2 t3 t4 t5 t6 t7 t8 100% 60% Used Capacity Time

References

Related documents

Strong evidence indicates that, as well as changes in global average conditions such as temperature and precipitation, projected climate change is likely to be accompanied by

In memory of Harold Taub, beloved husband of Paula Taub by: Karen &amp; Charles Rosen.. Honouring Maria Belenkova-Buford on her marriage by: Karen &amp;

Volume (2018), Issue 1 Spring 2018 Wildlife Sightings Newsletter of the Iowa Chapter of The Wildlife Society. Make TWS Journals Your Publishing Choice

Advantage: Tungsten carbide, TSP, and diamond enhanced inserts provide extra protection to the gauge. Benefit: In-gauge hole and longer bit life;

To address these questions, the following goals were set: (a) to reproduce field explosions pertaining to primary blast injury as accurate as possible in a controlled

Presence of such trends in field of international students mobility within Ukrainian universities indicates at two major problems: (1) existence of information gap among

“ the seven words of our LORD on

s-process p-process Mass known Half-life known