A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2019; you can also visit <a rel="external noopener" href="https://biblio.ugent.be/publication/8590095/file/8590115.pdf">the original URL</a>. The file type is <code>application/pdf</code>.
Service Specific Management and Orchestration for a Content Delivery Network
<span title="">2018</span>
<i title="IEEE">
<a target="_blank" rel="noopener" href="https://fatcat.wiki/container/wem7gsbe7rh5hdvk376bnrenl4" style="color: black;">2018 4th IEEE Conference on Network Softwarization and Workshops (NetSoft)</a>
</i>
Preserved Fulltext
Any non-trivial network service requires service specific orchestration to meet its carrier-grade requirements regarding resiliency, availability, etc. How the network service components are mapped on the substrate, how VNFs get reconfigured after a monitored event or how they scale, only network service/function developers know how to execute such workflows to guarantee an optimal QoS. It is therefore of paramount importance that NFV Service Platforms allow developer specified input when
<span class="external-identifiers">
<a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1109/netsoft.2018.8459994">doi:10.1109/netsoft.2018.8459994</a>
<a target="_blank" rel="external noopener" href="https://dblp.org/rec/conf/netsoft/SoenenTXKVUS18.html">dblp:conf/netsoft/SoenenTXKVUS18</a>
<a target="_blank" rel="external noopener" href="https://fatcat.wiki/release/aibpknkhdjgchfnymssd3fm4bi">fatcat:aibpknkhdjgchfnymssd3fm4bi</a>
</span>
more »
... ming such life cycle events, instead of defining generic workflows. Within the scope of the SONATA and 5GTANGO projects, a mechanism was designed that allows developers to create and execute Service and Function Specific Managers. These managers are processes, created by the developer, that define service or function specific orchestration behaviour. The SONATA Service Platform executes these managers to overwrite generic Service Platform behaviour, creating developer customised life cycle workflows. We will demonstrate the development, testing and operational execution of these managers by using a Content Delivery Network which requires specific placement and scaling behaviour.
<a target="_blank" rel="noopener" href="https://web.archive.org/web/20190429101706/https://biblio.ugent.be/publication/8590095/file/8590115.pdf" title="fulltext PDF download" data-goatcounter-click="serp-fulltext" data-goatcounter-title="serp-fulltext">
<button class="ui simple right pointing dropdown compact black labeled icon button serp-button">
<i class="icon ia-icon"></i>
Web Archive
[PDF]
<div class="menu fulltext-thumbnail">
<img src="https://blobs.fatcat.wiki/thumbnail/pdf/53/ea/53ea1e4292a248c576384d5fb58a9b372c4c9319.180px.jpg" alt="fulltext thumbnail" loading="lazy">
</div>
</button>
</a>
<a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1109/netsoft.2018.8459994">
<button class="ui left aligned compact blue labeled icon button serp-button">
<i class="external alternate icon"></i>
ieee.com
</button>
</a>