...
There are two methods to support HPA in SO:. In the Frankfurt release, only the Method 1 will be supported.
- Method 1: Use of Homing information that is made during the SO decompose processing.
- During SO decompose processing, SO calls OOF for collecting homing information for the service (which includes the VNFs).
- Call the OOF APIs to perform the optimize service/VNF homing and placement
- Use the existing homing workflows to pass hardware platform capability requirements to OOF
- See the following diagram for the component interaction.
...
- Method 2: If the above processing does not work for the vendor VNF HPA, OOF will be called from the SOL003 Adapter per VNF. The following describes the interactions between SOL003 Adapter and OOF.
- Note: current, OOF does NOT support the VNF Level Homing request. OOF API enhancement is under discussion. Otherwise, the method 1 (Service Level Homing) is used for Frankfurt. TBD.Frankfurt - Out of Frankfurt Release scope
- VNFM Adapter sends out homing requests to OOF (OSDF) containing resource info
- OOF (OSDF) pulls all the related homing constraints from Policy
- OOF (HAS) checks AAI database to pull region (flavor) information
- OOF (HAS) communicates with Multi-Cloud to check cloud capacity (vims which fulfill the requirements)
- OOF (OSDF) returns homing allocation solution to VNFM Adapter
- OOF collects information as following:
- Service and Resource Info, from: AAI
- HPA Flavors/Capabilities/Capacity Info, from: AAI
- Policy Models (Homing, PCI) from: Policy
- Infrastructure Metrics Info (capacity), from: MultiCloud
- Cloud Agnostic Intent Info, from: MultiCloud
- PCI configuration data (not yet a part of SDC model)
- SOL003 Adapter Homing Request to OOF
- <describe the homing request API and contract here>
...