https://confluence.simplprogramme.eu/display/SIMPL/Annex+6+-+Architecture+building+blocks Simpl provides an abstraction layer to provision Virtual Machines on the underlying infrastructure. The end users may select the virtual machine(s) which are the most tailored for their needs regarding a set of parameters (e.g. operation system, memory size, network bandwidth, etc.) https://confluence.simplprogramme.eu/display/SIMPL/Container+Provisioning Provisioning of an infrastructure resource is identical for containers, storage and VMs. Details are provided under Containers Provisioning and are also applicable to Storage and VMs. In the first step, the Infrastructure Provider (or APP/Data Providers, upon their need) can use the Deployment Script Management to add their deployment scripts. These scripts are Crossplane configuration files, that at the time of execution, will: A) Provision the infrastructure resources (VM, Container or Storage); B) Deploy Applications over the infrastructure resources (if needed); C) Load data sets or images on the infrastructure resource (if needed). After adding the deployment script (via the available UI or the API), the DeploymentScriptID, which is a unique ID for that deployment script will be returned. In the second step, at the time of creating infrastructure offerings (or bundles of app/data + infrastructure, as it would be required for use cases explained in BP 09A and BP 09B), the DeploymentScriptID is being added to the Self-Description. In the third step, when the offer has been selected and successfully contracted, the Infrastructure Provisioner API (the same API that handles the addition/removal and modifications of the Deployment Scripts in step 1) is being called, and the DeploymentScriptID will be passed to that API for execution. Therefore, that DeploymentScriptID is being validated, and if the validation is successful, will be executed. The infrastructure Provisioner Module will (as explained above): A) Provision the infrastructure resources (VM, Container or Storage).; B) Deploy Applications over the infrastructure resources (if needed); C) Load data sets or images on the infrastructure resource (if needed). And will share back the access data with the consumer. The communication between the triggering module and the infrastructure provisioner is done via a message broker, to keep the process asynchronous. https://confluence.simplprogramme.eu/display/SIMPL/ACV+08+-+Infrastructure+Resource+Consumption