High-level:
The Definition of high-level TOSCA DM about HPA could refer to Supported HPA Capability Requirements(DRAFT). The example, which acts as a resource of SDC, could refer to [demo.git] / tosca / vCPE /
SDC leverages the resource to set up a service, an example output of the service is attached: service-VcpeWithAll-csar.csar
Low-level:
There are several components, which acts of SDC client, to parse the output CSAR to do interactive:
- SO: sends out homing requests to OOF by parsing the CSAR, which includes OOF will respond with the most appropriate flavors accordingly
- Policy: after user distributes the service, it will download the related CSAR and dynamically generate the policies based on specified rules.
- VFC: sends out homing requests to OOF by parsing the CSAR, which includes OOF will respond with the most appropriate flavors accordingly
The flow of HPA like below:
- Policy generates policies after user distributes SDC service by parsing CSAR
- TOSCA: VFC sends homing requests to OOF by parsing the SDC CSAR
- HEAT: SO sending homing requests to OOF by parsing the SDC CSAR
- OOF fetch policies from Policy based on the input from VFC or SO
- OOF fetch flavor from AAI based on the received policies
- OOF composite the output to VFC or SO
SO we need to keep alignment about the how to parse the SDC CSAR, the mapping from CSAR to low-level fields. below is the logic of Policy side used: