I think weâre in agreement on the âother-definitionsâ proposal. Weâll make sure to update the spec accordingly.
Calin, youâre correct that v1.2 substitution mapping is ill-defined. We could adopt the âconventionâ youâre suggesting to make things work, but that was never really documented in the spec. Letâs discuss further during the Jan. 15 YAML
meeting.
Thanks,
Chris
From: Calin Curescu <calin.curescu@ericsson.com>
Sent: Friday, January 11, 2019 6:15 AM
To: Priya T G <priya.g@netcracker.com>; Lishitao <lishitao@huawei.com>; Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>; Chris Lauwers <lauwers@ubicity.com>; Matt Rutkowski <mrutkows@us.ibm.com>
Cc: Nguyenphu, Thinh (Nokia - US/Irving <thinh.nguyenphu@nokia.com>; KATZMAN, ANATOLY <ak435s@intl.att.com>; claude.noshpitz@att.com; tosca@lists.oasis-open.org
Subject: Re: Multiple entry definitions - TOSCA Simple Profile v1.3
Hi,
Afaik, before the holidays we agreed to follow Mattâs proposal that he uploaded in the documents section:
There, we have the âentry-definitionsâ with cardinality [0,1] which is the entry template. In addition there is âother-definitionsâ with cardinality [0,N] which may can contain other useful definitions, like types, substitution templates,
etc.
Semantically, the other-definitions are the same as the imports, with the difference that they do not need to be known when creating the main service template. They are put together when creating the CSAR file, so one decides then which
say specify type definition to include.
This solution is the better than a list of entry definitions, since it does not create confusions of which is the service template (i.e. which is the yaml file that provides the service template). For example, a substitution template can
be used also as a standalone main template. With the above definition, if its yaml file is put among the âother-definitionsâ it is clear that it should be used as a substitution template. If you would put it in a list of multiple entry-definitions it would
not be clear for the orchestrator which is the âmainâ service template.
This will come in v 1.3. and will elegantly solve the problem that Priya presented below as the definition of the two substitution templates are put in the âother-definitionsâ.
Chris: maybe this was not well defined from the beginning, but if Priyaâs example is not correct, how could we ever use substitution templates in v. 1.2? Can we not assume for the âimportâ definitions,
that all the imported yaml files are additional definitions (where non-substitution templates are discarded and substitution templates will be used only as substitution templates), i.e. exactly the same behavior that we want for âother-definitionsâ.
BR,
/Calin
From:
Priya T G <priya.g@netcracker.com>
Date: Friday, 11 January 2019 at 13:52
To: Lishitao <lishitao@huawei.com>, Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>, Chris Lauwers <lauwers@ubicity.com>,
Matt Rutkowski <mrutkows@us.ibm.com>
Cc: Calin Curescu <calin.curescu@ericsson.com>, "Nguyenphu, Thinh (Nokia - US/Irving" <thinh.nguyenphu@nokia.com>, "KATZMAN, ANATOLY" <ak435s@intl.att.com>,
"claude.noshpitz@att.com" <claude.noshpitz@att.com>, "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
Subject: RE: Multiple entry definitions - TOSCA Simple Profile v1.3
Hi Shitao,
After discussion with Chris in Simple Profile WG , we concluded that SOL 001 needs changes based on multiple entry definitions. So the below statement you quoted no longer holds good
J
Regards,
Priya
From: Lishitao [mailto:lishitao@huawei.com]
Sent: Friday, January 11, 2019 6:18 PM
To: Priya T G <priya.g@netcracker.com>; Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>; Chris Lauwers <lauwers@ubicity.com>;
Matt Rutkowski <mrutkows@us.ibm.com>
Cc: Calin Curescu <calin.curescu@ericsson.com>; Nguyenphu, Thinh (Nokia - US/Irving <thinh.nguyenphu@nokia.com>; KATZMAN, ANATOLY <ak435s@intl.att.com>;
claude.noshpitz@att.com;
tosca@lists.oasis-open.org
Subject: çå: Multiple entry definitions - TOSCA Simple Profile v1.3
Hi Priya
The SOL001 example you referred to is correct. And I also agree with what Arturo explained.
what do you mean by âETSI NFV does not currently have a use case for multiple entry definitions as proposed in Simple profile v1.3â, my understanding
is that the next version of SOL001 will introduce the multiple entry definition feature, right?
Regards
shitao
åää:
Priya T G [mailto:priya.g@netcracker.com]
åéæé:
2019å1æ11æ
20:35
æää: Arturo Martin
De Nicolas <arturo.martin-de-nicolas@ericsson.com>; Chris Lauwers <lauwers@ubicity.com>; Matt Rutkowski <mrutkows@us.ibm.com>
æé: Lishitao <lishitao@huawei.com>;
Calin Curescu <calin.curescu@ericsson.com>; Nguyenphu, Thinh (Nokia - US/Irving <thinh.nguyenphu@nokia.com>; KATZMAN, ANATOLY <ak435s@intl.att.com>;
claude.noshpitz@att.com;
tosca@lists.oasis-open.org
äé:
RE: Multiple entry definitions - TOSCA Simple Profile v1.3
Chris,
Agree with Arturo, we had consensus on multiple entry definitions before the holidays.
Regards,
Priya
From: Arturo Martin De Nicolas [mailto:arturo.martin-de-nicolas@ericsson.com]
Sent: Friday, January 11, 2019 2:53 PM
To: Chris Lauwers <lauwers@ubicity.com>; Priya T G <priya.g@netcracker.com>; Matt Rutkowski <mrutkows@us.ibm.com>
Cc: Lishitao <lishitao@huawei.com>; Calin Curescu <calin.curescu@ericsson.com>; Nguyenphu, Thinh (Nokia - US/Irving <thinh.nguyenphu@nokia.com>;
KATZMAN, ANATOLY <ak435s@intl.att.com>;
claude.noshpitz@att.com;
tosca@lists.oasis-open.org
Subject: RE: Multiple entry definitions - TOSCA Simple Profile v1.3
Hi Chris,
Yes, you made a similar statement in one of the last calls we had in 2018. However, I remember we also concluded that with v.1.2 there was no means to include in the same CSAR the top level service template and multiple
service template used for substitution of node templates in the top level. Therefore, for SOL001 I think we have to do it like that. But it is important to get the change on the multiple entry definitions in v.1.3 (see separate mail I sent two days ago) in
order to adopt it in SOL001 in the future.
BR,
Arturo
From:
tosca@lists.oasis-open.org <tosca@lists.oasis-open.org>
On Behalf Of Chris Lauwers
Sent: Thursday, 10 January 2019 19:41
To: Priya T G <priya.g@netcracker.com>; Matt Rutkowski <mrutkows@us.ibm.com>
Cc: Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>; Lishitao <lishitao@huawei.com>; Calin Curescu <calin.curescu@ericsson.com>;
Nguyenphu, Thinh (Nokia - US/Irving <thinh.nguyenphu@nokia.com>; KATZMAN, ANATOLY <ak435s@intl.att.com>;
claude.noshpitz@att.com;
tosca@lists.oasis-open.org
Subject: [tosca] RE: Multiple entry definitions - TOSCA Simple Profile v1.3
Hi Priya,
Apologies for the delayed reply. After looking at this more, I believe the approach youâre describing wonât work: the top-level VNF service template (which defines a topology template) includes the two service templates
for the different deployment flavors. Each of these service templates also define their own topology template. This results in an overall service that defines three topology templates, which wonât work (this would be like a C file with a main() program including
another C file that also has a main()).
Thanks,
Chris
From: Priya T G <priya.g@netcracker.com>
Sent: Monday, December 10, 2018 8:37 AM
To: Chris Lauwers <lauwers@ubicity.com>; Matt Rutkowski <mrutkows@us.ibm.com>
Cc: Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>; Lishitao <lishitao@huawei.com>; Calin Curescu <calin.curescu@ericsson.com>;
Nguyenphu, Thinh (Nokia - US/Irving <thinh.nguyenphu@nokia.com>; KATZMAN, ANATOLY <ak435s@intl.att.com>;
claude.noshpitz@att.com
Subject: Multiple entry definitions - TOSCA Simple Profile v1.3
Chris and Matt,
As a follow up of our discussion on multiple entry definitions last week, I would like to summarize that a few changes were made in SOL 001 based on the original DF proposal from Chris and Shitao in SOL 001 (i.e. after updates
to v1.3 specification):
Original proposal:
- Top level service template has only node type
- Lower level service templates imported top level service template
Changes in SOL 001:
- Top level service template having a node template for VNF , instead of node type (snippet below). The VNF node type definition is present in the another template (in the snippet below, sunshineVNF.yaml
)and is imported in the top level service template.
- The other imports in the snippet below are for the DF service templates - sunshinedbsimple.vnfd.tosca.yaml and sunshinedbcomplex.vnfd.tosca.yaml.
- Multiple lower level service templates, each representing a deployment flavor.
Due to these changes in SOL 001, in my view, ETSI NFV does not currently have a use case for multiple entry definitions as proposed in Simple profile v1.3
Arturo, Shitao, All,
Please feel free to share your views on this topic.
Regards,
Priya
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or
privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact
the sender and delete the material from any computer.
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or
privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact
the sender and delete the material from any computer.
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged
material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender
and delete the material from any computer.