Hi Rittwik and DENG,
Is modeling discussion covering network service and VNF descriptors? Or it is
broader to cover all of the ONAP functions?
Yes, I am planning to attend.
Thinh
From: onap-discuss-bounces at lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of denghui
Hi Tai,
We need the substitution_mapping grammar feature from TOSCA YAML v1.2.
Thinh
From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On
Behalf Of Tal Liron
Sent: Monday, June 25, 2018 9:25 PM
To: onap-discuss@lists.onap.org
Cc: Michela ; Lando,Michael
Subject: Re:
Hi Deng Hui,
Thank you for preparing Liaison document. My comments are the following:
1. What is the date for milestone 4?
2. The first link requires ONAP login. Thus, ETSI NFV members may not have
the login. LS should provide public links or avoid providing one.
Hi Xu,
Thanks for the summary. With respect to naming convention poll, I would like
to share of what I just posted on the wiki page.
I would like to share with the team on the result from ETSI NFV IFA WG
discussion on the IE and attributes renaming. At the time the development of
IFA011 and
Hi Deng Hui,
This statement in meeting note is not correct either.
“2) will update onap type with TOSCA NFV profile, and”
We did not agreed to update onap types with TOSCA NFV profile
(tosca-nfv-profile-wd05-rev03). The tosca-nfv-profile-wd05-rev03 is out of date
and no long align with ONAP
Hello,
After reviewing https://wiki.onap.org/display/DW/NetworkService, I still have
many issues with network service IM model. The following are my comments:
Figure ONAP R2 (Simplification for implication)
[image2018-3-13_20-44-5.png]
[Thinh] Some of key network service class such as
Hi Lingli,
Would you please add these two wiki pages as part of DM service discussion on
the agenda item 2.1 or service DM.
https://wiki.onap.org/display/DW/Network+Service+Model+and+TOSCA+Types
https://wiki.onap.org/display/DW/Network+Service+Virtual+Link
Thinh
From:
Hi Jessie,
Your summary below shows there are a lot of inconsistency of TOSCA types naming
convention with IFA011. I fully acknowledge it. SOL WG is in the process of
cleaning it up with these guidelines:
* SOL001 Type naming convention is UpperCamelCase.
* SOL001 properties naming
