The study we have conducted of existing cloud platforms shows that their operating requires the use of specific and proprietary APIs. This PaaS providers’ policy is hampering the interactions between different clouds. If appropriate solutions are not considered, this issue would for instance slow down the democratization of clouds federation and cooperation. As a part of our work, we developed a generic PaaS application provisioning and management API (called COAPS API). Our proposed solution applies the separation of concerns principle by separating the provisioning and the management API from the defined description model.

1. Multi-PaaS Provisioning
Sami Yangui & Mohamed Mohamed
Institut Mines-Telecom, Telecom SudParis.
Summary: The study we have conducted of existing cloud platforms shows that their
operating requires the use of specific and proprietary APIs. This PaaS providers’ policy is
hampering the interactions between different clouds. If appropriate solutions are not
considered, this issue would for instance slow down the democratization of clouds
federation and cooperation. As a part of our work, we developed a generic PaaS
application provisioning and management API named CompatibleOne Application and
Platform Service - COAPS. Our solution applies the separation of concerns principle by
separating the provisioning and the management API from the defined description model.
www.ow2.org
Twitter #ow2con

2. Application provisioning on PaaS
●
PaaS operating requires the use of specific and proprietary APIs
–
●
Issue: Cooperation and interactions between different clouds
Motivating example
–
Provisioning of a Web application (WAR archive)
–
Requirements to be provisioned by the hosting PaaS
●
–
–
2
Apache tomcat as service container
MySQL as database service
www.ow2.org
Twitter #ow2con

3. Application provisioning Issues
●
Provisioning steps are specific per PaaS provider
–
Not the same commands
–
Not the same inputs
–
Not the same order of creation
However,
●
They have all the same semantics
OCCI-compliant API to manage and provision
PaaS resources
3
www.ow2.org
Twitter #ow2con

4. COAPS API
●
PaaS-independent approach for the provisioning and
management of applications in the Cloud
Resource description manifest to express user requirement
●
Unified description model for cloud application description
●
Generic RESTful API to interact with heterogeneous PaaS
C
O
A
P
S
P aaS 2
P aaS 2
Application
P aaS 1
P aaS 1
Cloud consumer
●
Manifest
(Application
description)
4
www.ow2.org
Twitter #ow2con

5. Video Demo
5
www.ow2.org
Twitter #ow2con

6. COAPS on
6
www.ow2.org
Twitter #ow2con

7. COAPS useful links
●
●
COAPS sources
●
http://gitorious.ow2.org/ow2-compatibleone/coaps
●
●
COAPS Web client for Cloud Foundry PaaS
●
http://star-paas-client.cloudfoundry.com/
●
●
COAPS implementation for Cloud Foundry PaaS
●
7
http://cf-paas-api.cloudfoundry.com/
www.ow2.org
Twitter #ow2con