Hi,
The document is mainly about the VNF package issue, but it also include
the network service(P3, some ns node) as well.
If it is only for the VNF, please correct me. thanks.
P3, The VNF node is lost. I have uploaded the network service
definition for R1 on the wiki, please review it.
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599839/NSD%20Specification.pdf
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599838/NS%20Package%20Specification.pdf
P4 , For VFC side, agree to move the type definitions into one yaml file.
P6, The VoLTE csar’s does not contain mainServiceTemplate.yaml
There is only one service template which its name is
openovnf_csarName.yaml
Vendor need to change openovnf_csarName.yaml to
mainServiceTemplate.yaml
[Maopeng] the service template can be configured, not an fixed file
name, according to the tosca standard.
It is configured in the
VoLTE.csar\TOSCA-Metadata\TOSCA.meta
Entry-Definitions: Definitions/ns2__VoLTE.yaml
This way I think it is also supported by the vvg csar
that the David provided.
There is no support with nested service templates
No nested support
[Maopeng] R1, no nested service templetes in the NS.
P7 Is the issue same with P4? but the type definition file name is not
same.
P8 I think we need some inputs in the VoLTE case. I think now the SDC
supports the function.
P9 About the import, is it possible tha both list and Map<String, List>
could be supported in VNF packages?
P10 About the Substitution, is it possible that the OASIS standerd
substitution suppported as well?
Best Regards
Maopeng_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
