Yes, I suggest to add it in an annex, so the new readers understand our next step. I can double check with the wording if we could use other word
instead of “shall”.
发件人: Nguyenphu, Thinh (Nokia - US/Irving) [mailto:thinh.nguyenphu@nokia.com]
发送时间: 2017年6月27日
22:26
收件人: Lishitao
抄送: tosca@lists.oasis-open.org
主题: Re: 答复: [tosca] Groups - Adding annex for CSAR package considieration for DF-r1 .doc uploaded
Meeting note conclusion does not mean that we agreed to have an annex, and specific requirements to csar or VNF package.
I am ok with the highlighted bullet points as we are working on the df concept in a service template.
The annex has "shall" statement, which we could not agreed.
Hi
As we discussed during the NFV&SDN adhoc on May 24, the purpose of this annex is just used to record what we conclude for the packaging issue for
deployment flavor. I think we agreed during the adhoc that there should not be only one pattern for VNFD venders to design their VNF. If there are other possible pattern can be used, we can also add it into this annex.
https://www.oasis-open.org/committees/document.php?document_id=60825&wg_abbrev=tosca
2
|
|
Deployment flavour
Discussion from last meeting:
Way forward:
1, to clarify how to implement IFA without change IFA API based on multiple VNFDs in the CSAR package method (Michael, Thinh)
2, what TOSCA mechanism has to be changed to support multiple DFs into a CSAR (Bruce)
Conclusion:
- Supporting the single one DF per service template. Support one or more service templates in the CSAR package.
- Current working assumption, 1 TOSCA Service Template = a VNFD with a single DF.
- CSAR package contains one or more service templates.
|
Issue1: whether main service template is needed
Alex: how to define new capabilities aligning with tosca-simple-profile-yaml
Thinh: need to discuss together with simple yaml WG
An example for substitution mapping based method is needed. (Thinh)
Alex: enterprise example
Alex: align with IFA changes
Shitao: considering put the conclusion parts in the left table into tosca-nfv-profile (annex: )
|
It is premature to agreed on CSAR package with deployment flavor. There must not be requirement to CSAR package or VNF Package specification.
It is best first to agreed to how DF solution. Also, there multiple instance of "shall" statement in section x.2 that are not applicable.
Also the figure is not truly represent VNFD. It missing CP, VL, interfaces, etc.
What is the purpose of put these text in NFV profile?
|