...
"vf-module-id":"<vf-module-id>",
"vf-module-model-invariant-id":"<uuid>"
"vf-module-model-version-id":"<uuid>",
"vf-module-model-customization-id":"<uuid>",
"oof_directives":{},
"sdnc_directives":{},
...
"template_data":{ … }
}
The ‘model-customization-id’ will need to ‘vf-module-model-*-id’s will be used by the Multicloud plugin to retrieve the associated cloud artifacts. It will be the job of the SDC client in Multicloud to download the artifacts and make an association between the model -customization-id IDs and the artifacts during SDC distribution.
...
QUESTION: What is the purpose of the ‘generic-vnf-id’ and ‘vf-module-id’ paramtersparameters? I initially was thinking multicloud could use these to query AAI for the model-customization-id, but since SO has it already, it can send and avoid the extra AAI lookup. So, is there another use of ‘generic-vnf-id’ and ‘vf-module-id’ ?
ANSWER: they were put there for heatbridge and metadata purposes (not for model information lookup).
‘user_directives’ is new and ‘sdnc_directives’ was in the API before but not used. Both will have a format similar to the following:
...
Take a look at this page: https://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=5822888116350907 for thoughts on this topic.
...