PaaS Orchestration and Adaptation
Problem Description
PaaS abstraction is still an open and on-going topic in current research. It can drastically decrease costs, by e.g. sharing infrastructure of public PaaS providers to host an application. Therefore, the integration of a PaaS abstraction into the Cloud Provider Engine is of major interest for CloudSocket. See Deliverable D3.3 for a research on current Cloud Orchestration Tools and their state towards PaaS services and provider integration.
Solution Approach
Our solution for this is two-fold: (i) enhancing the application and component instance life-cycle by PaaS-specific activities, and (ii) integrating and developing the PaaS Unified Library (PUL) into the Cloud Provider Engine, which is powered by Colosseum.
[Life-cycle figure]
Architecture
The communication to the cloud provider is ensured by the PaaS abstraction layer “Dagger”, which is the higher-level pendant to Sword, the IaaS abstraction layer. This layer unifies the API calls to different Cloud providers.
Usage
http://134.60.64.166/cloud-provider-engine-ui/#/login
References
For more details on this, please check the respective repositories: Research branch of Cloudiator/Colosseum https://github.com/cloudiator/colosseum/tree/cs-paas-prototype
Unified PaaS component https://www.cloudsocket.eu/common-understanding-wiki/-/wiki/Main/Unified+PaaS+component