...
This change to the Heat template structure has an impact on the way the Policy Engine will execute closed loop. Today, when a policy violation in the vFirewall use case is detected, the Policy Engine tells APPC to execute a corrective action against the vPacketGen VNF by providing the VNF UUID of the vPacketGen itself. (Pamela Dragosh Plz confirm) Policy Engine will have need to use the VF module UUID of the vPacketGen instead of the VNF UUID. Policy doesn't have this capability right now.
Leveraging CDS and Data Dictionary for Instantiation
...
Removing ModifyConfig Parameters from the Policy Template
Today, Policy hardcodes the entire body Policy now allows the Control Loop Designer to specify the payload for APPC API calls through CLAMP. Policy will copy the entire payload of the operation that APPC has to execute against the VNF during closed loop into the APPC LCM request.
ModifyConfig action including the parameters and their resolution will be defined in CDS as described above. We will implement CDS API model implementation and actor implementation in policy so that we can either directly invoke CDS to push the NETCONF payload to the vPacketGen VNF or invoke APPC to execute ModifyConfig against the traffic generator VNF.(Pamela Dragosh Plz confirm the below items.) For Dublin, we plan to remove this limitation. Further details about Policy/APPC interaction will be defined later, depending on which technologies we can leverage for Dublin release.
Pamela Dragosh - we want to also deprecate the old API for ModifyConfig and use APPC's latest LCM API interface if possible.
...