The document discusses the Sirocco multi-cloud management framework. It provides a unified API based on the DMTF CIMI standard to manage multiple cloud providers. It describes Sirocco's architecture including modules for provisioning, placement management, and monitoring. Placement management aims to select the best cloud provider and data center based on requirements and optimization rules. The document outlines current status and next steps to further integrate providers and enhance placement rules.

1. The Sirocco multi-cloud management
framework
Frédéric Dang Tran
Paweł Rubach
Orange Labs
{frederic.dangtran,pawel.rubach}@orange.com

2. Outline
§ Context and objectives
§ Sirocco architecture overview
§ Focus on the DMTF CIMI standard
§ Placement management
§ Conclusion
OW2Con 2011, November 23-24, Orange Labs, Paris. 2
www.ow2.org

3. Context and Objectives (1/2)
§ Accessing a single Cloud provider is not enough
> Cloud bursting from a private to a public cloud during load peeks
> Satisfy application specific constraints such as location, performance,
costs, ...
> Means to implement disaster recovery and HA configurations by replication
over multiple clouds
§ Hiding IaaS provider heterogeneity
> Different APIs
> Different infrastructure models : compute, storage, network
> Different format of VM images
OW2Con 2012, November 27-29, Orange Labs, Paris. 3
www.ow2.org

4. Context and Objectives (2/2)
§ What is Sirocco ?
> Multi-cloud management platform
> Single point of entry to access multiple cloud providers
> Unified IaaS API based on the DMTF CIMI API standard
> Extensible and open middleware framework
OW2Con 2012, November 27-29, Orange Labs, Paris. 4
www.ow2.org

5. Sirocco Architecture
Sirocco multi-cloud
management framework
CIMI API Server
Request orchestration
Resource Provider
User &Tenant Image Monitoring &
Provisioning & Placement
management
& Lifecyle mgmt Management
Management Metering
Cloud Provider
API gateway and connection
management
5

6. DMTF CIMI API (1/3)
§ DMTF Cloud Management Working Group (CMWG)
> Focus on Cloud IaaS API
> Cloud Infrastructure Management Interface (CIMI) 1.0 API specification
released 29 August 2012
§ 34 involved companies and 10+ academic or alliance partners:
> IBM, VMware, CA, Cisco, Citrix, Fujitsu, HP, Huawei, ZTE, Microsoft,
Oracle, Red Hat, Telecom Italia, Telefonica, France Telecom…
OW2Con 2012, November 27-29, Orange Labs, Paris. 6
www.ow2.org

7. DMTF CIMI API (2/3)
CIMI Provider
OVF
import/export
Machine Volume Network System
Compute resource Persistent storage Level 2 network Appliance
with CPU, memory that can be Broadcast domain grouping
and local disks attached/detached machines,
to/from a Machine volumes and
Block or file- networks
system level Managed as
Sirocco multi-cloud manager single unit 7

8. Mapping CIMI API à IaaS API
vCloud Director
CIMI model
System
Network
Amazon VPC
OpenStack Quantum
8

9. Placement Management – Motivation
How to choose the cloud provider or data center where an app is deployed
For a single cloud operator:
> Operating geographically distributed data centers with potentially
differentiated service offers
> Different policies: load balancing, energy management, disaster
recovery (deploy on two clouds separated by a distance), deploy close
to active users, deploy within a network distance (latency, bandwidth)
For a cloud broker
> Mediate in face of cloud providers with different service offers, prices,
> Maximize revenue
9

10. Placement Management - matching provider “iaas” offers based on
virtual machine configuration
Cloud Provider ”A”
BUNDLE CPU MEM (GB) DISK (GB)
NAME
Request
? SMALL
MEDIUM
{1, 2}
{2, 4, 8}
(0.5 – 2.0)
(1.0 – 8.0)
(2 – 40)
(4 – 200)
WhichMEM
CPU offer toDISK
choose? LARGE {4, 8, 16} (2.0 – 16.0) (16 – 800)
(GB) (GB)
{4} (6 - 8) (40 – 100) Cloud Provider ”B”
CPU MEM (GB) DISK (GB)
{1,2,4,8,16} (0.25-32.0) (1-1000)
10

11. Placement Management – Requirements for Architecture
§ Flexible and extensible : facilitate administration of placement
policies
§ Adapt to evolving operator goals and policies
§ Evolving constraints
§ Allow adaptation to changes in demand, changes in cloud provider
offers, prices, policies
11

12. Placement Management – Architecture
OW2Con 2012, November 27-29, Orange Labs, Paris. 12
www.ow2.org

13. Placement Management – Current Status
§ Developed extensions to the CIMI model to allow for:
> matching by capabilities (including bundles)
> matching by locations (including network distance etc.)
> passing placement requests and decisions
§ Developed PoC according to the presented architecture with
simplified matching and optimization rules
13

14. Conclusion: next steps
§ Complete DMTF CIMI 1.0 API implementation
§ Integrate third-party VM Image Factories (e.g. UShareSoft)
§ Integrate Application Lifecycle Management service based on OVF
§ IaaS provider support: complete mapping of CIMI network model to
– VMware vCloud Director
– OpenStack Quantum
§ Placement management:
> Enhance matching rules
> Provide a mechanism to change rules dynamically
> Implement feedback mechanisms
OW2Con 2012, November 27-29, Orange Labs, Paris. 14
www.ow2.org

15. Pointers
§ OW2 Sirocco project home page
> http://sirocco.ow2.org
§ SCM repositories
> svn://svn.forge.objectweb.org/svnroot/sirocco/cloudmanager/trunk
> git://gitorious.ow2.org/ow2-sirocco
§ OpenCloudware collaborative project (FSN)
> http://www.opencloudware.org
§ LGPL open-souce license
OW2Con 2012, November 27-29, Orange Labs, Paris. 15
www.ow2.org