...
- SO: sends out homing requests to OOF by parsing the CSAR, which includes with HEAT template, 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 , with TOSCA template, OOF will respond with the most appropriate flavors accordingly
...
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, the format example refer to OOF R3 HPA & Cloud Agnostic policies
| Policy | Const value or from TOSCA CSAR | Value | Comment |
|---|---|---|---|
| service | Const | "hpaPolicy" | |
| policyName | TOSCA CSAR | "OSDF_CASABLANCA."+ content.getIdentity() | |
| description | Const | "OOF Policy" | |
| templateVersion | "OpenSource.version.1" | ||
| version | "1.0" | ||
| priority | "5" | ||
| riskType | "Test" | ||
| riskLevel | "2" | ||
| guard | "False" | ||
| content.resources | TOSCA CSAR | content.getResources().add(metaData.getValue("name")); | the resource name defined in SDC |
| content.identity | TOSCA CSAR | content.getPolicyType() + "_" + metaData.getValue("name") | |
| content.policyScope | Const TOSCA CSAR | “HPA” sdcCsarHelper.getServiceMetadata().getValue("name"); | List |
| content.policyType | Const | "hpa" | |
| content.flavorFeatures.id | TOSCA CSAR | node.toString | the name of the VDU node |
| content.flavorFeatures.type | Const | "tosca.nodes.nfv.Vdu.Compute" | placeholder |
| content.flavorFeatures.directives.type | "flavor_directives" | ||
| content.flavorFeatures.directives.attributes.attribute_name | "flavor_name" | ||
| content.flavorFeatures.directives.attribute_value | "" | ||
| content.flavorFeatures.flavorProperties.hpaFeature | TOSCA CSAR | one of available or meaningful values: cpuTopology, basicCapabilities, ovsDpdk, cpuPinning, numa, sriovNicNetwork, pciePassthrough, localStorage, instructionSetExtensions, hugePages based on below Feature judgement flow | based on HPA Policies and Mappings |
| content.flavorFeatures.flavorProperties.mandatory | from mandatory field | ||
| content.flavorFeatures.flavorProperties.architecture | from hardwarePlatform field | ||
| content.flavorFeatures.flavorProperties.hpaVersion | "v1" | ||
| content.flavorFeatures.flavorProperties.hpaFeatureAttributes | parse and tiny change from configurationValue | ||
| content.flavorFeatures.flavorProperties.directives | [ ] | OOF fill them in |
...