We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
FIWARE.Epic.Cloud.CloudEdgePaaS.ServiceProvisioning - FIWARE Forge Wiki

FIWARE.Epic.Cloud.CloudEdgePaaS.ServiceProvisioning

From FIWARE Forge Wiki

Jump to: navigation, search
Name Service Provisioning Chapter Cloud Hosting
Goal As an edgelet developer, I want to be able to use a provisioning API in order to deploy and update my edgelet (and required resources) to the Cloud Edge platform and have it updated in all relevant distributed nodes.
Description Platform provisioning ensures that:
  • a newly provisioned edgelet is stored in the master node's catalogue and available for end user installation
  • new versions of edgelets are automatically updated to all nodes
  • other resources and services (e.g. databases) required by edgelet are deployed to the set of nodes, placement being defined by metadata: localization, required quality of service (latency, bandwidth, ...), hardware capabilities...
Rationale The platform provisioning is necessary before deploying edgelets on the different nodes of the infrastructure. Taking into account the different placement policies is useful for deploying edgelets efficiently, as well as following SLAs
Personal tools
Create a book