[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 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> 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:
Changes in SOL 001:
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. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]