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.