Tal,

A few points…

1.      We have four parsers and one orchestrator already in use within ONAP. 
These are well established parsers supported by different companies that 
participate in ONAP. IMHO, we are ought to be looking to reduce this set to one 
parser/orchestrator combination that we can use going forward, across all ONAP 
projects that need them.

2.      Given our S3P ambitions, we need to ensure that the parser/orchestrator 
that we choose is seasoned and established enough to support the function of 
ONAP components.

3.      We, the ETSI NFV SOL001 team, have made a conscious decision to make 
use of the TOSCA Simple YAML profile 1.2 grammar elements. We also made a 
conscious choice to mitigate lack of commercial and open source support of 1.2 
grammar by enabling alternative way of encoding VNFDs in TOSCA, using 1.1 
grammar, albeit with some limitation.

4.      AFAIK, TOSCA Simple YAML Profile WG has finished the 1.2 grammar 
definition and is working on v1.3 of the grammar.

My two cents…

Alex Vul
Intel Corporation


From: [email protected] [mailto:[email protected]] On 
Behalf Of Tal Liron
Sent: Monday, June 25, 2018 20:03


https://github.com/tliron/puccini

I will reiterate the two points I made and add another:

  *   TOSCA 1.2 has not been released yet. It is currently in draft 2 version. 
It might be a good idea to wait for it to be finalized before rushing to 
implement it.
  *   Puccini does not support TOSCA 1.2 right now, but it will in the future 
(when TOSCA 1.2 is officially released).
  *   Puccini is not currently part of ONAP. If it works well for SO, we can 
then talk about implications for supporting TOSCA 1.2 in SDC and other ONAP 
components.
Once again I will ask -- what TOSCA 1.2 features are important to you?

On Mon, Jun 25, 2018 at 9:45 PM, gaoweitao 
<[email protected]<mailto:[email protected]>> wrote:
Hi, Tal, Alex, Michela, all,

      Can you give me some detail information about TOSCA parser that already 
support TOSCA 1.2 ?

     From TOSCA template consumer perspective, not only SDC/SO should support 
that, but also all the consumer of TOSCA template, such as VFC, etc. we really 
need to figure out the affected projects.

BR
Victor

发件人: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] 代表 Tal 
Liron
发送时间: 2018年6月26日 10:25
收件人: [email protected]<mailto:[email protected]>
抄送: Michela 
<[email protected]<mailto:[email protected]>>; 
Lando,Michael <[email protected]<mailto:[email protected]>>
主题: Re: [onap-discuss] [SO] is YAML v1.2 supported ?

I think you mean TOSCA 1.2. (YAML 1.2 is supported by most TOSCA parsers.)

If you do mean TOSCA 1.2, then it is on the roadmap for Puccini which will soon 
be tested as a candidate for parsing TOSCA in SO. (It currently supports TOSCA 
1.1.)

What are the particular TOSCA 1.2 features that you need?


On Mon, Jun 25, 2018 at 11:27 AM, Alex Vul 
<[email protected]<mailto:[email protected]>> wrote:
Michael, Michela, et al,

To my knowledge there are no commercial or open source TOSCA 
orchestrators/interpreters that support YAML 1.2 grammar. Even if SDC can 
recognize the node/capability/data/etc types, our TOSCA tools are not going to 
parse the templates correctly. To me this is a bigger problem that ONAP needs 
to address…

Best regards,

Alex Vul
Intel Corporation


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] On 
Behalf Of Michela
Sent: Monday, June 25, 2018 08:58
To: [email protected]<mailto:[email protected]>; 
Lando,Michael <[email protected]<mailto:[email protected]>>
Subject: [onap-discuss] [SO] is YAML v1.2 supported ?

HI Michael ,
Is YAML 1.2 supported in SDC for VNF onboarding ?
If not, is there any plan to add it in R3 ?
BR
Michela






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10571): https://lists.onap.org/g/onap-discuss/message/10571
Mute This Topic: https://lists.onap.org/mt/22681690/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to