...
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. If we decide to reshape the Heat templates as described above, Policy Engine will have to use the VF module UUID of the vPacketGen instead of the VNF UUID. Policy doesn't have this capability right now, so reshaping the Heat templates is currently under investigation. A possible approach could be to reshape only the vFirewall/vSink Heat template and leave the vPacketGen Heat template as is. This, however, may complicate the adoption of CDS technologies (see below), which would have to deal with cross references in Heat templates of elements at different levels (i.e. VF module vs. VNF).
Finally, Heat templates should be follow the ONAP VNF Guidelines and pass VNF Validation.
Leveraging CDS and Data Dictionary
...