...
Today, Policy hardcodes the entire body of the operation that APPC has to execute against the VNF during closed loop. 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 API interface if possible.
For example, if DD will be available, a user can define ModifyConfig parameters in CDS (extension of current CDT) and specify the parameter resolution in DD. During closed loop, Policy will just tell APPC to execute ModifyConfig against a specific VNF. APPC will then look at the VNF template (built with CDS) to retrieve the ModifyConfig parameters and use DD for their resolution. If DD will not be available, then ModifyConfig parameters could be defined in CLAMP and pushed to Policy during closed loop creation. Policy will then pass these parameters to APPC during closed loop execution. This is how the automated scale out use case is designed for Casablanca.
...