HPA Implementation - Changes to ONAP Modules
- Policy Framework - creates homing/placement constraint policies based on input from sysadmin or VNFD
- OOF - makes homing/placement decisions based on constraint policies
- SO/VFC - call OOF to decide where VNF components will be deployed
- AAI - contains inventory information, inclusive of HW platform capabilities
- Multi-Cloud - discovers inventory information, inclusive of HW platform capabilities
Concerns
- On distribution of Network Service - want to preserve existing functionality of OOF to create HPA constraint policy from the HPA present in the Tosca VNFD
- Currently SO and VFC make similar calls to OOF - if SOL003 makes a similar call - in support of Grant request - keep API to OOF the same.
- ls the HPA information able to be represented in the current Grant Request/Response API?
- OOF provides a homing solution based on HPA and other constraints for the Service - how will this work in the ETSI case? Is there VNF level homing?
- For an ETSI NS/VNF/PNF - what info, if any, distributed to SO vs what gets stored in ETSI Catalog microservices?
{"serverDuration": 217, "requestCorrelationId": "5687cb38075e48378976d592ac816d21"}