PaaS Orchestration and Adaptation https://site.cloudsocket.eu/web/guest/common-understanding-wiki/-/wiki/330801 2026-04-13T00:14:53Z 2026-04-13T00:14:53Z Wilfrid Utz https://site.cloudsocket.eu/web/guest/common-understanding-wiki/-/wiki/330801/PaaS Orchestration and Adaptation?_36_version=1.1 2017-02-07T08:31:19Z 2017-02-07T08:31:19Z

<table id="toc"><tbody><tr><td><ul><li><a href="#Problem_Description"><span class="tocnumber">1</span> <span class="toctext">Problem Description</span></a></li><li><a href="#Solution_Approach"><span class="tocnumber">2</span> <span class="toctext">Solution Approach</span></a></li><li><a href="#Architecture"><span class="tocnumber">3</span> <span class="toctext">Architecture</span></a></li><li><a href="#Usage"><span class="tocnumber">4</span> <span class="toctext">Usage</span></a></li><li><a href="#References"><span class="tocnumber">5</span> <span class="toctext">References</span></a></li></ul></td></tr></tbody></table> <a name="Problem_Description"><!----></a><h2><span>Problem Description</span></h2><p><span class="diff-html-removed" id="removed-diff-0" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">The problem we target.</span></p><h2><span><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">Solution Approach</span></span><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0"><!----></span></h2><p><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">The approach we took to develop a solution.</span></p><h2><span><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">Architecture</span></span><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0"><!----></span></h2><p><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">Here is a diagram with the architecture and the reference / interplay to other components.</span></p><h2><span><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">Usage</span></span><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0"><!----></span></h2><p><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">Here are links to external git repos with READMEs or links to the internal wiki with API descriptions.</span></p><h2><span><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">References</span></span><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0"><!----></span></h2><p><span class="diff-html-removed" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">Here are links to publications and deliverables.</span></p><p><span class="diff-html-added" id="added-diff-0" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">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.</span></p><p><br><!----></br></p> <a name="Solution_Approach"><!----></a><h2><span><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">Solution Approach</span></span><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff"><!----></span></h2><p><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">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.</span></p><p><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">[Life-cycle figure]</span></p> <a name="Architecture"><!----></a><h2><span><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">Architecture</span></span><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff"><!----></span></h2><p><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">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.</span></p> <a name="Usage"><!----></a><h2><span><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">Usage</span></span><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff"><!----></span></h2><p><a class="externallink" rel="nofollow" href="http://134.60.64.166/cloud-provider-engine-ui/#/login"><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">http://134.60.64.166/cloud-provider-engine-ui/#/login</span></a><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff"><!----></span></p> <a name="References"><!----></a><h2><span><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">References</span></span><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff"><!----></span></h2><p><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">For more details on this, please check the respective repositories: Research branch of Cloudiator/Colosseum </span><a class="externallink" rel="nofollow" href="https://github.com/cloudiator/colosseum/tree/cs-paas-prototype"><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">https://github.com/cloudiator/colosseum/tree/cs-paas-prototype</span></a><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff"><!----></span></p><p><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">Unified PaaS component </span><a class="externallink" rel="nofollow" href="https://www.cloudsocket.eu/common-understanding-wiki/-/wiki/Main/Unified+PaaS+component"><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff">https://www.cloudsocket.eu/common-understanding-wiki/-/wiki/Main/Unified+PaaS+component</span></a><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="last-diff"><!----></span></p>

Wilfrid Utz 2017-02-07T08:31:19Z Wilfrid Utz https://site.cloudsocket.eu/web/guest/common-understanding-wiki/-/wiki/330801/PaaS Orchestration and Adaptation?_36_version=1.2 2017-02-07T08:32:45Z 2017-02-07T08:32:45Z

<table id="toc"><tbody><tr><td><ul><li><a href="#Problem_Description"><span class="tocnumber">1</span> <span class="toctext">Problem Description</span></a></li><li><a href="#Solution_Approach"><span class="tocnumber">2</span> <span class="toctext">Solution Approach</span></a></li><li><a href="#Architecture"><span class="tocnumber">3</span> <span class="toctext">Architecture</span></a></li><li><a href="#Usage"><span class="tocnumber">4</span> <span class="toctext">Usage</span></a></li><li><a href="#References"><span class="tocnumber">5</span> <span class="toctext">References</span></a></li></ul></td></tr></tbody></table> <a name="Problem_Description"><!----></a><h2><span>Problem Description</span></h2><p>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.</p><p><br><!----></br></p> <a name="Solution_Approach"><!----></a><h2><span>Solution Approach</span></h2><p>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.</p><p>[Life-cycle figure]</p> <a name="Architecture"><!----></a><h2><span>Architecture</span></h2><p>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.</p> <a name="Usage"><!----></a><h2><span>Usage</span></h2><p><a class="externallink" rel="nofollow" href="http://134.60.64.166/cloud-provider-engine-ui/#/login">http://134.60.64.166/cloud-provider-engine-ui/#/login</a></p> <a name="References"><!----></a><h2><span>References</span></h2><p>For more details on this, please check the respective repositories: Research branch of Cloudiator/Colosseum <a class="externallink" rel="nofollow" href="https://github.com/cloudiator/colosseum/tree/cs-paas-prototype">https://github.com/cloudiator/colosseum/tree/cs-paas-prototype</a></p><p>Unified PaaS component <a class="externallink" rel="nofollow" href="https://www.cloudsocket.eu/common-understanding-wiki/-/wiki/Main/Unified+PaaS+component">https://www.cloudsocket.eu/common-understanding-wiki/-/wiki/Main/Unified+PaaS+component</a></p>

Wilfrid Utz 2017-02-07T08:32:45Z Wilfrid Utz https://site.cloudsocket.eu/web/guest/common-understanding-wiki/-/wiki/330801/PaaS Orchestration and Adaptation?_36_version=1.3 2017-02-07T08:47:25Z 2017-02-07T08:47:25Z

<table id="toc"><tbody><tr><td><ul><li><a href="#Problem_Description"><span class="tocnumber">1</span> <span class="toctext">Problem Description</span></a></li><li><a href="#Solution_Approach"><span class="tocnumber">2</span> <span class="toctext">Solution Approach</span></a></li><li><a href="#Architecture"><span class="tocnumber">3</span> <span class="toctext">Architecture</span></a></li><li><a href="#Usage"><span class="tocnumber">4</span> <span class="toctext">Usage</span></a></li><li><a href="#References"><span class="tocnumber">5</span> <span class="toctext">References</span></a></li></ul></td></tr></tbody></table> <a name="Problem_Description"><!----></a><h2><span>Problem Description</span></h2><p>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.</p><p><br><!----></br></p> <a name="Solution_Approach"><!----></a><h2><span>Solution Approach</span></h2><p>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.</p><p><span class="diff-html-removed" id="removed-diff-0" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">[Life-cycle figure]</span><span class="diff-html-added" id="added-diff-0" previous="removed-diff-0" changeId="added-diff-0" next="added-diff-1"><img alt="paas%255F0.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas%25255F0.png" changeType="diff-added-image" onLoad="updateOverlays()" onError="updateOverlays()" onAbort="updateOverlays()"/></span></p> <a name="Architecture"><!----></a><h2><span>Architecture</span></h2><p>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.</p><p><span class="diff-html-added" id="added-diff-1" previous="added-diff-0" changeId="added-diff-1" next="last-diff"><img alt="paas%255F1.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas%25255F1.png" changeType="diff-added-image" onLoad="updateOverlays()" onError="updateOverlays()" onAbort="updateOverlays()"/></span><span class="diff-html-added" previous="added-diff-0" changeId="added-diff-1" next="last-diff"><!----></span></p> <a name="Usage"><!----></a><h2><span>Usage</span></h2><p><a class="externallink" rel="nofollow" href="http://134.60.64.166/cloud-provider-engine-ui/#/login">http://134.60.64.166/cloud-provider-engine-ui/#/login</a></p> <a name="References"><!----></a><h2><span>References</span></h2><p>For more details on this, please check the respective repositories: Research branch of Cloudiator/Colosseum <a class="externallink" rel="nofollow" href="https://github.com/cloudiator/colosseum/tree/cs-paas-prototype">https://github.com/cloudiator/colosseum/tree/cs-paas-prototype</a></p><p>Unified PaaS component <a class="externallink" rel="nofollow" href="https://www.cloudsocket.eu/common-understanding-wiki/-/wiki/Main/Unified+PaaS+component">https://www.cloudsocket.eu/common-understanding-wiki/-/wiki/Main/Unified+PaaS+component</a></p>

Wilfrid Utz 2017-02-07T08:47:25Z Wilfrid Utz https://site.cloudsocket.eu/web/guest/common-understanding-wiki/-/wiki/330801/PaaS Orchestration and Adaptation?_36_version=1.4 2017-02-07T11:30:28Z 2017-02-07T11:30:28Z

<table id="toc"><tbody><tr><td><ul><li><a href="#Problem_Description"><span class="tocnumber">1</span> <span class="toctext">Problem Description</span></a></li><li><a href="#Solution_Approach"><span class="tocnumber">2</span> <span class="toctext">Solution Approach</span></a></li><li><a href="#Architecture"><span class="tocnumber">3</span> <span class="toctext">Architecture</span></a></li><li><a href="#Usage"><span class="tocnumber">4</span> <span class="toctext">Usage</span></a></li><li><a href="#References"><span class="tocnumber">5</span> <span class="toctext">References</span></a></li></ul></td></tr></tbody></table> <a name="Problem_Description"><!----></a><h2><span>Problem Description</span></h2><p>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.</p><p><br><!----></br></p> <a name="Solution_Approach"><!----></a><h2><span>Solution Approach</span></h2><p>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.</p><p><span class="diff-html-removed" id="removed-diff-0" previous="first-diff" changeId="removed-diff-0" next="added-diff-0"><img alt="paas%255F0.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas%25255F0.png" changeType="diff-removed-image" onLoad="updateOverlays()" onError="updateOverlays()" onAbort="updateOverlays()"/></span><span class="diff-html-added" id="added-diff-0" previous="removed-diff-0" changeId="added-diff-0" next="removed-diff-1"><img alt="paas0.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas0.png" changeType="diff-added-image" onLoad="updateOverlays()" onError="updateOverlays()" onAbort="updateOverlays()"/></span></p> <a name="Architecture"><!----></a><h2><span>Architecture</span></h2><p>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.</p><p><span class="diff-html-removed" id="removed-diff-1" previous="added-diff-0" changeId="removed-diff-1" next="added-diff-1"><img alt="paas%255F1.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas%25255F1.png" changeType="diff-removed-image" onLoad="updateOverlays()" onError="updateOverlays()" onAbort="updateOverlays()"/></span><span class="diff-html-added" id="added-diff-1" previous="removed-diff-1" changeId="added-diff-1" next="last-diff"><img alt="paas1.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas1.png" changeType="diff-added-image" onLoad="updateOverlays()" onError="updateOverlays()" onAbort="updateOverlays()"/></span></p> <a name="Usage"><!----></a><h2><span>Usage</span></h2><p><a class="externallink" rel="nofollow" href="http://134.60.64.166/cloud-provider-engine-ui/#/login">http://134.60.64.166/cloud-provider-engine-ui/#/login</a></p> <a name="References"><!----></a><h2><span>References</span></h2><p>For more details on this, please check the respective repositories: Research branch of Cloudiator/Colosseum <a class="externallink" rel="nofollow" href="https://github.com/cloudiator/colosseum/tree/cs-paas-prototype">https://github.com/cloudiator/colosseum/tree/cs-paas-prototype</a></p><p>Unified PaaS component <a class="externallink" rel="nofollow" href="https://www.cloudsocket.eu/common-understanding-wiki/-/wiki/Main/Unified+PaaS+component">https://www.cloudsocket.eu/common-understanding-wiki/-/wiki/Main/Unified+PaaS+component</a></p>

Wilfrid Utz 2017-02-07T11:30:28Z Wilfrid Utz https://site.cloudsocket.eu/web/guest/common-understanding-wiki/-/wiki/330801/PaaS Orchestration and Adaptation?_36_version=1.5 2017-02-07T11:31:57Z 2017-02-07T11:31:57Z

<table id="toc"><tbody><tr><td><ul><li><a href="#Problem_Description"><span class="tocnumber">1</span> <span class="toctext">Problem Description</span></a></li><li><a href="#Solution_Approach"><span class="tocnumber">2</span> <span class="toctext">Solution Approach</span></a></li><li><a href="#Architecture"><span class="tocnumber">3</span> <span class="toctext">Architecture</span></a></li><li><a href="#Usage"><span class="tocnumber">4</span> <span class="toctext">Usage</span></a></li><li><a href="#References"><span class="tocnumber">5</span> <span class="toctext">References</span></a></li></ul></td></tr></tbody></table> <a name="Problem_Description"><!----></a><h2><span>Problem Description</span></h2><p>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.</p><p><br><!----></br></p> <a name="Solution_Approach"><!----></a><h2><span>Solution Approach</span></h2><p>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.</p><p><img alt="paas0.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas0.png"/></p> <a name="Architecture"><!----></a><h2><span>Architecture</span></h2><p>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.</p><p><img alt="paas1.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas1.png"/></p> <a name="Usage"><!----></a><h2><span>Usage</span></h2><p><a class="externallink" rel="nofollow" href="http://134.60.64.166/cloud-provider-engine-ui/#/login">http://134.60.64.166/cloud-provider-engine-ui/#/login</a></p> <a name="References"><!----></a><h2><span>References</span></h2><p>For more details on this, please check the respective repositories:<span class="diff-html-added" id="added-diff-0" previous="first-diff" changeId="added-diff-0" next="changed-diff-0"><!----></span></p><p><a class="externallink" rel="nofollow" href="https://github.com/cloudiator/colosseum/tree/cs-paas-prototype"><span class="diff-html-changed" id="changed-diff-0" changes="Moved to a &lt;b&gt;link&lt;/b&gt; with destination &lt;br/&gt;https://github.com/cloudiator/colosseum/tree/cs-paas-pr&lt;br/&gt;ototype with class externallink and rel nofollow." previous="added-diff-0" changeId="changed-diff-0" next="removed-diff-0">Research branch of Cloudiator/Colosseum</span></a><span class="diff-html-removed" previous="changed-diff-0" changeId="removed-diff-0" next="changed-diff-1"> </span><a class="externallink" rel="nofollow" href="https://github.com/cloudiator/colosseum/tree/cs-paas-prototype"><span class="diff-html-removed" id="removed-diff-0" previous="changed-diff-0" changeId="removed-diff-0" next="changed-diff-1">https://github.com/cloudiator/colosseum/tree/cs-paas-prototype</span></a></p><p><a href="/wiki/Special:Node:330801/Special:Edit?topic=Unified%2BPaaS%2Bcomponent" class="edit" title="Unified+PaaS+component"><span class="diff-html-changed" id="changed-diff-1" changes="Moved to a &lt;b&gt;link&lt;/b&gt; with destination &lt;br/&gt;/wiki/Special:Node:330801/Special:Edit?topic=Unified%2B&lt;br/&gt;PaaS%2Bcomponent with class edit and title &lt;br/&gt;Unified+PaaS+component." previous="removed-diff-0" changeId="changed-diff-1" next="removed-diff-1">Unified</span></a><span class="diff-html-removed" previous="changed-diff-1" changeId="removed-diff-1" next="changed-diff-2"> </span><span class="diff-html-removed" id="removed-diff-1" previous="changed-diff-1" changeId="removed-diff-1" next="changed-diff-2">PaaS component https://www.cloudsocket.eu/common-understanding-wiki/-/wiki/Main/Unified</span><a href="/wiki/Special:Node:330801/Special:Edit?topic=Unified%2BPaaS%2Bcomponent" class="edit" title="Unified+PaaS+component"><span class="diff-html-changed" id="changed-diff-2" changes="&lt;ul class='changelist'&gt;&lt;li&gt;Moved out of a &lt;b&gt;link&lt;/b&gt; with destination &lt;br/&gt;https://www.cloudsocket.eu/common-understanding-wiki/-/&lt;br/&gt;wiki/Main/Unified+PaaS+component with class &lt;br/&gt;externallink and rel nofollow.&lt;/li&gt;&lt;li&gt;Moved to a &lt;b&gt;link&lt;/b&gt; with destination &lt;br/&gt;/wiki/Special:Node:330801/Special:Edit?topic=Unified%2B&lt;br/&gt;PaaS%2Bcomponent with class edit and title &lt;br/&gt;Unified+PaaS+component.&lt;/li&gt;&lt;/ul&gt;" previous="removed-diff-1" changeId="changed-diff-2" next="last-diff">+PaaS+component</span></a></p>

Wilfrid Utz 2017-02-07T11:31:57Z Wilfrid Utz https://site.cloudsocket.eu/web/guest/common-understanding-wiki/-/wiki/330801/PaaS Orchestration and Adaptation?_36_version=1.6 2017-02-07T11:33:17Z 2017-02-07T11:33:17Z

<table id="toc"><tbody><tr><td><ul><li><a href="#Problem_Description"><span class="tocnumber">1</span> <span class="toctext">Problem Description</span></a></li><li><a href="#Solution_Approach"><span class="tocnumber">2</span> <span class="toctext">Solution Approach</span></a></li><li><a href="#Architecture"><span class="tocnumber">3</span> <span class="toctext">Architecture</span></a></li><li><a href="#Usage"><span class="tocnumber">4</span> <span class="toctext">Usage</span></a></li><li><a href="#References"><span class="tocnumber">5</span> <span class="toctext">References</span></a></li></ul></td></tr></tbody></table> <a name="Problem_Description"><!----></a><h2><span>Problem Description</span></h2><p>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.</p><p><br><!----></br></p> <a name="Solution_Approach"><!----></a><h2><span>Solution Approach</span></h2><p>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.</p><p><img alt="paas0.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas0.png"/></p> <a name="Architecture"><!----></a><h2><span>Architecture</span></h2><p>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.</p><p><img alt="paas1.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas1.png"/></p> <a name="Usage"><!----></a><h2><span>Usage</span></h2><p><a class="externallink" rel="nofollow" href="http://134.60.64.166/cloud-provider-engine-ui/#/login">http://134.60.64.166/cloud-provider-engine-ui/#/login</a></p> <a name="References"><!----></a><h2><span>References</span></h2><p>For more details on this, please check the respective repositories:</p><p><a class="externallink" rel="nofollow" href="https://github.com/cloudiator/colosseum/tree/cs-paas-prototype">Research branch of Cloudiator/Colosseum</a></p><p><span class="diff-html-removed" id="removed-diff-0" previous="first-diff" changeId="removed-diff-0" next="added-diff-0">Unified+PaaS+</span><a class="externallink" rel="nofollow" href="https://omi-gitlab.e-technik.uni-ulm.de/cloudsocket/adaptation-management"><span class="diff-html-added" id="added-diff-0" previous="removed-diff-0" changeId="added-diff-0" next="changed-diff-0">Adaptation Management component repository</span></a><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="changed-diff-0"><!----></span></p><p><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="changed-diff-0">Also please refer to the wiki pages:</span></p><p><a href="/wiki/Special:Node:330801/Adaptation_Management" title="Adaptation Management"><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="changed-diff-0">Adaptation Management</span></a><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="changed-diff-0"><!----></span></p><p><a href="/wiki/Special:Node:330801/Unified_PaaS_component" title="Unified PaaS component"><span class="diff-html-added" previous="removed-diff-0" changeId="added-diff-0" next="changed-diff-0">Unified PaaS </span><span class="diff-html-changed" id="changed-diff-0" changes="&lt;ul class='changelist'&gt;&lt;li&gt;Moved out of a &lt;b&gt;link&lt;/b&gt; with destination &lt;br/&gt;/wiki/Special:Node:330801/Special:Edit?topic=Unified%2B&lt;br/&gt;PaaS%2Bcomponent with class edit and title &lt;br/&gt;Unified+PaaS+component.&lt;/li&gt;&lt;li&gt;Moved to a &lt;b&gt;link&lt;/b&gt; with destination &lt;br/&gt;/wiki/Special:Node:330801/Unified_PaaS_component with &lt;br/&gt;title Unified PaaS component.&lt;/li&gt;&lt;/ul&gt;" previous="added-diff-0" changeId="changed-diff-0" next="last-diff">component</span></a></p>

Wilfrid Utz 2017-02-07T11:33:17Z Wilfrid Utz https://site.cloudsocket.eu/web/guest/common-understanding-wiki/-/wiki/330801/PaaS Orchestration and Adaptation?_36_version=1.7 2017-02-07T12:22:03Z 2017-02-07T12:22:03Z

<table id="toc"><tbody><tr><td><ul><li><a href="#Problem_Description"><span class="tocnumber">1</span> <span class="toctext">Problem Description</span></a></li><li><a href="#Solution_Approach"><span class="tocnumber">2</span> <span class="toctext">Solution Approach</span></a></li><li><a href="#Architecture"><span class="tocnumber">3</span> <span class="toctext">Architecture</span></a></li><li><a href="#Usage"><span class="tocnumber">4</span> <span class="toctext">Usage</span></a></li><li><a href="#Video_Presentation"><span class="tocnumber"><span class="diff-html-changed" id="changed-diff-0" changes="&lt;ul class='changelist'&gt;&lt;li&gt;Moved out of a &lt;b&gt;link&lt;/b&gt; with destination #References.&lt;/li&gt;&lt;li&gt;Moved to a &lt;b&gt;link&lt;/b&gt; with destination #Video_Presentation.&lt;/li&gt;&lt;/ul&gt;" previous="first-diff" changeId="changed-diff-0" next="added-diff-0">5</span></span><span class="diff-html-changed" changes="&lt;ul class='changelist'&gt;&lt;li&gt;Moved out of a &lt;b&gt;link&lt;/b&gt; with destination #References.&lt;/li&gt;&lt;li&gt;Moved to a &lt;b&gt;link&lt;/b&gt; with destination #Video_Presentation.&lt;/li&gt;&lt;/ul&gt;" previous="first-diff" changeId="changed-diff-0" next="added-diff-0"> </span><span class="toctext"><span class="diff-html-added" id="added-diff-0" previous="changed-diff-0" changeId="added-diff-0" next="added-diff-1">Video Presentation</span></span></a><span class="diff-html-added" previous="changed-diff-0" changeId="added-diff-0" next="added-diff-1"><!----></span></li><li><a href="#References"><span class="tocnumber"><span class="diff-html-added" previous="changed-diff-0" changeId="added-diff-0" next="added-diff-1">6</span></span><span class="diff-html-added" previous="changed-diff-0" changeId="added-diff-0" next="added-diff-1"> </span><span class="toctext">References</span></a></li></ul></td></tr></tbody></table> <a name="Problem_Description"><!----></a><h2><span>Problem Description</span></h2><p>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.</p><p><br><!----></br></p> <a name="Solution_Approach"><!----></a><h2><span>Solution Approach</span></h2><p>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.</p><p><img alt="paas0.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas0.png"/></p> <a name="Architecture"><!----></a><h2><span>Architecture</span></h2><p>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.</p><p><img alt="paas1.png" class="wikiimg" src="/c/wiki/get_page_attachment?p_l_id=335868&amp;nodeId=330801&amp;title=PaaS+Orchestration+and+Adaptation&amp;fileName=paas1.png"/></p> <a name="Usage"><!----></a><h2><span>Usage</span></h2><p><a class="externallink" rel="nofollow" href="http://134.60.64.166/cloud-provider-engine-ui/#/login">http://134.60.64.166/cloud-provider-engine-ui/#/login</a></p> <a name="Video_Presentation"><!----></a><h2><span><span class="diff-html-added" id="added-diff-1" previous="added-diff-0" changeId="added-diff-1" next="last-diff">Video Presentation</span></span><span class="diff-html-added" previous="added-diff-0" changeId="added-diff-1" next="last-diff"><!----></span></h2><p><span class="diff-html-added" previous="added-diff-0" changeId="added-diff-1" next="last-diff">A video is available on </span><a class="externallink" rel="nofollow" href="https://www.youtube.com/watch?v=aGtQ210wih8"><span class="diff-html-added" previous="added-diff-0" changeId="added-diff-1" next="last-diff">YouTube</span></a><span class="diff-html-added" previous="added-diff-0" changeId="added-diff-1" next="last-diff">.</span></p> <a name="References"><!----></a><h2><span>References</span></h2><p>For more details on this, please check the respective repositories:</p><p><a class="externallink" rel="nofollow" href="https://github.com/cloudiator/colosseum/tree/cs-paas-prototype">Research branch of Cloudiator/Colosseum</a></p><p><a class="externallink" rel="nofollow" href="https://omi-gitlab.e-technik.uni-ulm.de/cloudsocket/adaptation-management">Adaptation Management component repository</a></p><p>Also please refer to the wiki pages:</p><p><a href="/wiki/Special:Node:330801/Adaptation_Management" title="Adaptation Management">Adaptation Management</a></p><p><a href="/wiki/Special:Node:330801/Unified_PaaS_component" title="Unified PaaS component">Unified PaaS component</a></p>

Wilfrid Utz 2017-02-07T12:22:03Z