Hi Haibin, With regarding to HPA capability of "ovsDpdk" , it is the HPA capability to apply to the whole cloud region, and there is no way to choose consuming it or not. So It makes less sense to specify 'host aggregate' and associate it with certain flavor. In this case, the HPA capability of "ovsDpdk" can neither discovered via flavor nor represented as a child node under flavor in AAI. So the proposed solution is : Discover the HPA capability of "ovsDpdk" via VIM onboarding process (By specifying the ovsDpdk capability in ESR VIM registration GUI portal), and represent this HPA capability of "ovsDpdk" as a child node of "cloud region" in AAI.
The impact of this solution is: * Multi-cloud need implement the discovery and registration process (doable and verified in Amsterdam release) * OOF need consume this HPA capability of "ovsDpdk" by looking up it under cloud-region in AAI, instead of looking up it under flavor. * Policy need consume this HPA capability of "ovsDpdk" by looking up it under cloud-region in AAI, instead of looking up it under flavor. And any suggestion or concern? Thank you very much! ------------------------------------------------------------------------------------------------------------------------------- Huang.haibin 11628530 86+18106533356
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
