[onap-discuss] 答复: Re: ONAP issues

[zhang.maopeng1]

Hi







Mainly wiki of ONAP is a good place:  https://wiki.onap.org/


Hope this can help you.






BR


Maopeng



原始邮件



发件人：AshaRawat 
收件人：onap-discuss@lists.onap.org 
日 期 ：2018年03月30日 15:22
主 题 ：Re: [onap-discuss] ONAP issues


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


could you please respond!



On Mon, Mar 19, 2018 at 4:47 PM, Asha Rawat  wrote:

Hi Team,
I am trying to get some information regarding ONAP which i am unable to find in 
google .

could anyone please help on this?

Regards,
Asha Rawat
8588896641___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling] about the NSD in SDC

[zhang.maopeng1]

add the mail title. 








原始邮件



发件人：张茂鹏10030173
收件人：ml6...@intl.att.com tg8...@intl.att.com 

抄送人：onap-discuss@lists.onap.org 
日 期 ：2018年03月29日 13:15
主 题 ：[onap-discuss] [modeling]


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss



Hi Michael, Tal






   NSD definition has been already in the SDC code. Here is the link:


   
https://gerrit.onap.org/r/gitweb?p=sdc.git;a=tree;f=catalog-be/src/main/resources/import/tosca/nfv-types/NSD;h=bf5cabb52dc41025f4708c7c095e304196e7e6a6;hb=HEAD.
  


   How to design the NSD as resources in the SDC via the NSD node?   Thanks






BR


Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling]

[zhang.maopeng1]

Hi Michael, Tal






   NSD definition has been already in the SDC code. Here is the link:


   
https://gerrit.onap.org/r/gitweb?p=sdc.git;a=tree;f=catalog-be/src/main/resources/import/tosca/nfv-types/NSD;h=bf5cabb52dc41025f4708c7c095e304196e7e6a6;hb=HEAD.
  


   How to design the NSD as resources in the SDC via the NSD node?   Thanks






BR


Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: 答复: RE: [model][vCPE] Things missing in Onap Tosca DM?

[zhang.maopeng1]

Hi Steve






As  I know the vCPE case requirement of cloudinit user scripts is implimented 
via openstack api(vm create()).


In the Tosca configure standard process, the configure() will be after the 
create().  I think as  properties of Vdu.compute maybe is a good selection.





BR


Maopeng



原始邮件



发件人：SteveBaillargeon 
收件人：张茂鹏10030173;lianhao...@intel.com 
抄送人：onap-discuss@lists.onap.org 
日 期 ：2018年03月20日 22:56
主 题 ：RE: [onap-discuss] 答复: RE: [model][vCPE] Things missing in Onap Tosca DM?




Hi


All node types derived from TOSCA Root supports the standard 
tosca.interfaces.node.lifecycle.Standard interface.


 


I am assuming R2 ONAP will use such standard interface in conjunction with the 
TOSCA normative install workflow supported by all TOSCA orchestrators including 
ARIA.


Is this correct?


 


With such standard interface and workflow, it is possible to use cloud init and 
inject data using the TOSCA configure operation that is part of the 
tosca.interfaces.node.lifecycle.Standard interface.


 


Regards


Steve


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhang.maope...@zte.com.cn
 Sent: Tuesday, March 20, 2018 12:47 AM
 To: lianhao...@intel.com
 Cc: onap-discuss@lists.onap.org
 Subject: [onap-discuss] 答复: RE: [model][vCPE] Things missing in Onap Tosca DM?


 

Hi all

 

1. As I understand,  the heat template features vCPE used includes 
metadata,usedata,,, which are not included in the IM and DM now. 

2. pre-created network issue can be gotten as a input from TOSCA, but needs a 
properties of VL to represent it, such as description or a new properties.

 

BR

Maopeng


原始邮件



发件人：Lu,Lianhao 



收件人：Gaoweitao (Victor, MANO) onap-discuss@lists.onap.org 
 



抄送人：张茂鹏10030173;Vul, Alex Huang,  Haibin 




日 期 ：2018年03月20日 11:45



主 题 ：RE: [model][vCPE] Things missing in Onap Tosca DM?




Hi Victor,


 


I’ve got some following-up  questions


 


1. SSH key pairs for VM


When  saying to use inject file to handle this, do you mean to inject ssh 
public key to ~/.ssh/authorized_keys file within in the VM?


 


2. cloudinit user scripts


I’ve looked at the inject file definition in IM. Here I’ve several questions 
about inject file:

According to IM, the inject file property “Describes the information (e.g. URL) 
about the scripts, config drive metadata, etc. which can be used during Vdu 
booting process.” Do we need to specify  the destination pathname within the VM 
 image for the injected scripts? Openstack needs this kind of information.

vCPE usecase’s cloudinit scripts needs  to get some run-time dynamic properties 
& attributes of other VDUs, do we have a mechanism to pass those 
property/attribute values to the inject files?

Why can’t we leverage the existing tosca.interfaces.node.lifecycle.Standard 
interface, just like  
https://github.com/openstack/tosca-parser/blob/master/toscaparser/tests/data/CSAR/tosca_elk/Definitions/tosca_elk.yaml#L79
   . This could solve the above run-time properties issue.


 


BR


-Lianhao


 



From: Gaoweitao (Victor, MANO) [mailto:victor@huawei.com] 
 Sent: Tuesday, March 20, 2018 9:48 AM
 To: Lu, Lianhao ; onap-discuss@lists.onap.org
 Cc: zhang.maope...@zte.com.cn; Vul, Alex ; Huang, Haibin 

 Subject: 答复: [model][vCPE] Things missing in Onap Tosca DM?




 


Hi  Lianhao,


   


Please see my comments inline.


 


BR


Victor


 



发件人:  Lu, Lianhao [mailto:lianhao...@intel.com] 
 发送时间:  2018年3月19日  19:25
 收件人: onap-discuss@lists.onap.org
 抄送: zhang.maope...@zte.com.cn; Vul, Alex ;   Gaoweitao 
(Victor, MANO) ; Huang, Haibin 
 主题:  [model][vCPE] Things missing in Onap Tosca DM?




 


Hi Guys,


 


I’m now looking at the vCPE usecase 
(https://wiki.onap.org/pages/viewpage.action?pageId=3246168#UseCase:ResidentialBroadbandvCPE(Approved)-Description),
   and try to convert its heat 
template(https://git.onap.org/demo/tree/heat/vCPE) into latest onap Tosca  DM 
(https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile   ). 
I found the following things in heat and can NOT find the corresponding mapping 
in the Tosca DM.


 


1. SSH key pairs for VM


Heat supports creating ssh keypair for VM to enable login with ssh 
public/private keys. However I could not find corresponding in latest onap 
tosca DM. Should we support this in  tosca DM?


 


Victor: I think inject file could handle this.


 


2. cloudinit user scripts


In heat, vCPE uses cloudinit user script to executed within the VM after VM has 
been launched to configure the VNF softwares within the VM. However, in tosca 
DM, there is 

[onap-discuss] 答复: RE: [model][vCPE] Things missing in Onap Tosca DM?

[zhang.maopeng1]

Hi all






1. As I understand,  the heat template features vCPE used includes 
metadata,usedata,,, which are not included in the IM and DM now. 


2. pre-created network issue can be gotten as a input from TOSCA, but needs a 
properties of VL to represent it, such as description or a new properties.






BR


Maopeng



原始邮件



发件人：Lu,Lianhao 
收件人：Gaoweitao (Victor, MANO) onap-discuss@lists.onap.org 

抄送人：张茂鹏10030173;Vul, Alex Huang, Haibin 

日 期 ：2018年03月20日 11:45
主 题 ：RE: [model][vCPE] Things missing in Onap Tosca DM?




Hi Victor,


 


I’ve got some following-up  questions


 


1. SSH key pairs for VM


When  saying to use inject file to handle this, do you mean to inject ssh 
public key to ~/.ssh/authorized_keys file within in the VM?


 


2. cloudinit user scripts


I’ve looked at the inject file definition in IM. Here I’ve several questions 
about inject file:


-According to IM, the inject file property “Describes the information 
(e.g. URL) about the scripts, config drive metadata, etc. which can be used 
during Vdu booting process.” Do we need to specify the destination pathname 
within the VM  image for the injected scripts? Openstack needs this kind of 
information.


-vCPE usecase’s cloudinit scripts needs  to get some run-time dynamic 
properties & attributes of other VDUs, do we have a mechanism to pass those 
property/attribute values to the inject files?


-Why can’t we leverage the existing 
tosca.interfaces.node.lifecycle.Standard interface, just like  
https://github.com/openstack/tosca-parser/blob/master/toscaparser/tests/data/CSAR/tosca_elk/Definitions/tosca_elk.yaml#L79
  . This could solve the above run-time properties issue.


 


BR


-Lianhao


 



From: Gaoweitao (Victor, MANO) [mailto:victor@huawei.com] 
 Sent: Tuesday, March 20, 2018 9:48 AM
 To: Lu, Lianhao ; onap-discuss@lists.onap.org
 Cc: zhang.maope...@zte.com.cn; Vul, Alex ; Huang, Haibin 

 Subject: 答复: [model][vCPE] Things missing in Onap Tosca DM?




 


Hi  Lianhao,


   


Please see my comments inline.


 


BR


Victor


 



发件人: Lu, Lianhao [mailto:lianhao...@intel.com] 
 发送时间: 2018年3月19日 19:25
 收件人: onap-discuss@lists.onap.org
 抄送: zhang.maope...@zte.com.cn; Vul, Alex ;  Gaoweitao 
(Victor, MANO) ; Huang, Haibin 
 主题: [model][vCPE] Things missing in Onap Tosca DM?




 


Hi Guys,


 


I’m now looking at the vCPE usecase 
(https://wiki.onap.org/pages/viewpage.action?pageId=3246168#UseCase:ResidentialBroadbandvCPE(Approved)-Description),
  and try to convert its heat 
template(https://git.onap.org/demo/tree/heat/vCPE) into latest onap Tosca  DM 
(https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile  ). I 
found the following things in heat and can NOT find the corresponding mapping 
in the Tosca DM.


 


1. SSH key pairs for VM


Heat supports creating ssh keypair for VM to enable login with ssh 
public/private keys. However I could not find corresponding in latest onap 
tosca DM. Should we support this in tosca DM?


 


Victor: I think inject file could handle this.


 


2. cloudinit user scripts


In heat, vCPE uses cloudinit user script to executed within the VM after VM has 
been launched to configure the VNF softwares within the VM. However, in tosca 
DM, there is no direct mapping to such things in VDU. Should I use 
tosca.interfaces.node.lifecycle.Standard  interface instead or should we add 
new properties in VDU (see openstack tacker’s VDU as an example 
https://github.com/openstack/tacker/blob/master/tacker/tosca/lib/tacker_nfv_defs.yaml#L239
 )? The new userdata should also support inputs like 
tosca.interfaces.node.lifecycle.Standard interface.


 


Victor: In general, we will use inject file handle this. You can refer here: 
https://wiki.onap.org/display/DW/Node+Type tosca.nodes.nfv.Vdu.Compute and IM 
inject file definition for more info : 
https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version#DesignTimeModelCleanVersion-Class:VDU/VDUDesc.


 


3. pre-created networks:


vCPE will use 2 pre-created networks which are created when ONAP itself is 
being deployed: onap_public_net is used to make VM be able to connect to 
internet, onap_private_net is the oam network which is used to make some of the 
vCPE vnf  talk to some onap component(e.g. dcae_collector). So this requires 
the VNF VM to be connected to a pre-created network. However in tosca DM, it 
seems that there is no way to specify a VDU created by tosca DM connecting to a 
pre-created network which is already  created during ONAP deployment using 
heat.  Should we add an property in tosca.nodes.nfv.VnfVirtualLink to indicate 
whether the network is pre-created or not?


Victor：Pre-created 

[onap-discuss] 答复: Re: [onap-tsc] [modeling] ONAP R2 IM to DM design

[zhang.maopeng1]

Hello


   


   6. VNFD: https://jira.onap.org/browse/MODELING-72


According to the time limited, CMCC and ZTE as volunteers will corperate to 
take the classes for R2 needed.






BR


Maopeng



原始邮件



发件人：denghui(L) 
收件人：onap-discuss@lists.onap.org onap-tsc 

抄送人：Rittwik Jana 
日 期 ：2018年03月10日 09:51
主 题 ：Re: [onap-tsc] [modeling] ONAP R2 IM to DM design


___
ONAP-TSC mailing list
onap-...@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

  

Hello all


 


Currently, only 1,2,3,5 have been take, many thanks to Ericsson/Intel/Huawei


we still missing contributor for 4,6,7, R2 DM spec aligned with IM need to be 
finalized before next Tuesday modeling call.


 


Please help to volunteer


 


Thanks a lot


 


DENG Hui


 



From: denghui (L) 
 Sent: Thursday, March 8, 2018 8:46 PM
 To: onap-discuss@lists.onap.org; 'onap-tsc' 
 Cc: Rittwik Jana ; 'Lingli Deng' 

 Subject: [modeling] ONAP R2 IM to DM design




 


Hello all


 


As agreed in modeling subcommittee meeting, we need to update the onap types of 
the data model to reflect the agreements reached in information model.


 


It’s huge work to achieve the goal, in order to accelerate, 7 separate tasks 
have been created based on the current IM. We encourage interested people to 
volunteer to take the lead  for particular task.


 


The tasks including:


1. VDU: https://jira.onap.org/browse/MODELING-67


2. HPA: https://jira.onap.org/browse/MODELING-68


3. CP: https://jira.onap.org/browse/MODELING-69


4. DeploymentFlavor: https://jira.onap.org/browse/MODELING-70


5. VL: https://jira.onap.org/browse/MODELING-71


6. VNFD: https://jira.onap.org/browse/MODELING-72


7. monitor: https://jira.onap.org/browse/MODELING-73


 


It’s expected that the lead would help provide tosca definitions on the 
contribution page 
(https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile) and


help implement related logic in SDC, APPC/VFC projects.


 


Thanks a lot


 


DENG Hui___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: RE: RE: Re: 答复: [modeling] Comparison of R2 proposed IM classes and IFA011

[zhang.maopeng1]

I think it is the first time in the ONAP to go through it. right?






More infomation about the HPA data model in the ONAP model discussion, which is 
provided by Anatoly(ATT)。



https://wiki.onap.org/display/DW/Hardware+Platform+Requirements






is it same?






BR


Maopeng



原始邮件



发件人：Vul,Alex 
收件人：张茂鹏10030173;
抄送人：yang...@huawei.com jessie.jew...@oamtechnologies.com 
onap-discuss@lists.onap.org 

日 期 ：2018年03月01日 19:59
主 题 ：RE: RE: RE: Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM 
classes and IFA011




Sure, we can go through it one more time…


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, March 1, 2018 12:54 PM
 To: Vul, Alex 
 Cc: yang...@huawei.com; jessie.jew...@oamtechnologies.com; 
onap-discuss@lists.onap.org
 Subject: 答复: RE: RE: Re: [onap-discuss]答复:  [modeling] Comparison of R2 
proposed IM classes and IFA011


 

You can provide the discussion as input to the ONAP model. 

Let's discuss how to model it in the ONAP. 

 

Again we need the real input of HPA parameters definition, not only the 
keyvalue pairs.

 

BR

Maopeng


原始邮件



发件人：Vul,Alex 



收件人：张茂鹏10030173;



抄送人：yang...@huawei.com jessie.jew...@oamtechnologies.com  
onap-discuss@lists.onap.org 




日 期 ：2018年03月01日 19:42



主 题 ：RE: RE: Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM 
classes and IFA011




They have been discussed… They have not been all added to the final draft…


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, March 1, 2018 12:37 PM
 To: Vul, Alex 
 Cc: yang...@huawei.com; jessie.jew...@oamtechnologies.com; 
onap-discuss@lists.onap.org
 Subject: 答复: RE: Re: [onap-discuss]答复:   [modeling] Comparison of R2 proposed 
IM classes and IFA011


 

Alex

 

The "requestAdditionalCapabilities" are mainly keyvalue pairs in the IFA011.

 In R2,  the HPA related KEYs should be as inputs and the key name or value 
structure should be discussed in the model.

 

BR

Maopeng


原始邮件



发件人：Vul,Alex 



收件人：张茂鹏10030173;



抄送人：yang...@huawei.com jessie.jew...@oamtechnologies.com   
onap-discuss@lists.onap.org  




日 期 ：2018年03月01日 19:23



主 题 ：RE: Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM classes 
and IFA011




Maopeng,


 


Forgot to mention one more thing…


 


Already existing VNFs, with already existing VNFDs that use alternative IFA011 
HPA specification format,   based on “requestAdditionalCapabilities” attribute, 
are  not going to be impacted by this change… VNFs that are used as part of the 
VoLTE use cases don’t need to be converted to the new format, unless there a 
desire to do so…


 


Same goes for already existing HEAT based VNFs…


 


Kind regards,


 


Alex Vul


Intel Corporation


 


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, March 1, 2018 10:25 AM
 To: Vul, Alex 
 Cc: yang...@huawei.com; jessie.jew...@oamtechnologies.com; 
onap-discuss@lists.onap.org
 Subject: 答复: Re: [onap-discuss]答复:[modeling] Comparison of R2 proposed IM 
classes and IFA011


 

Hi Alex

 

 As a model contributor, join the discussion.

 Could you give the specific HPA parameters and completed usecases in R2? 

 Does the LAB need to provide some specific hardwares to test these 
features? 

 If we model the HPA parameters and implemented in R2, I think some real 
implemented inputs are needed.

 

Thanks

Maopeng


原始邮件



发件人：Vul,Alex 



收件人：yangxu (H) jessie jewitt 
onap-discuss@lists.onap.org




日 期 ：2018年03月01日 16:48



主 题 ：Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM classes and 
IFA011




___
 onap-discuss mailing list
 onap-discuss@lists.onap.org
 https://lists.onap.org/mailman/listinfo/onap-discuss
 
  


Jessie, Xu


 


There are a few things still missing from the agreed upon model. We need to add 
in items related tothe HPA support. HPA is a functional requirement being 
implemented  in R2. We need to ensure that the agreed upon model does not 
preclude the implementation of HPA.


 


Thank you,


 


Alex Vul


Intel Corporation


 


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of yangxu (H)
 Sent: Thursday, March 1, 2018 9:29 AM
 To: jessie jewitt ; 
onap-discuss@lists.onap.org
 Subject: [onap-discuss] 答复: [modeling] Comparison of R2 proposed IM 

[onap-discuss] 答复: RE: RE: Re: 答复: [modeling] Comparison of R2 proposed IM classes and IFA011

[zhang.maopeng1]

You can provide the discussion as input to the ONAP model. 


Let's discuss how to model it in the ONAP. 






Again we need the real input of HPA parameters definition, not only the 
keyvalue pairs.






BR


Maopeng







原始邮件



发件人：Vul,Alex 
收件人：张茂鹏10030173;
抄送人：yang...@huawei.com jessie.jew...@oamtechnologies.com 
onap-discuss@lists.onap.org 

日 期 ：2018年03月01日 19:42
主 题 ：RE: RE: Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM 
classes and IFA011




They have been discussed… They have not been all added to the final draft…


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, March 1, 2018 12:37 PM
 To: Vul, Alex 
 Cc: yang...@huawei.com; jessie.jew...@oamtechnologies.com; 
onap-discuss@lists.onap.org
 Subject: 答复: RE: Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed 
IM classes and IFA011


 

Alex

 

The "requestAdditionalCapabilities" are mainly keyvalue pairs in the IFA011.

 In R2,  the HPA related KEYs should be as inputs and the key name or value 
structure should be discussed in the model.

 

BR

Maopeng


原始邮件



发件人：Vul,Alex 



收件人：张茂鹏10030173;



抄送人：yang...@huawei.com jessie.jew...@oamtechnologies.com  
onap-discuss@lists.onap.org 




日 期 ：2018年03月01日 19:23



主 题 ：RE: Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM classes 
and IFA011




Maopeng,


 


Forgot to mention one more thing…


 


Already existing VNFs, with already existing VNFDs that use alternative IFA011 
HPA specification format,  based on “requestAdditionalCapabilities” attribute, 
are  not going to be impacted by this change… VNFs that are used as part of the 
VoLTE use cases don’t need to be converted to the new format, unless there a 
desire to do so…


 


Same goes for already existing HEAT based VNFs…


 


Kind regards,


 


Alex Vul


Intel Corporation


 


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, March 1, 2018 10:25 AM
 To: Vul, Alex 
 Cc: yang...@huawei.com; jessie.jew...@oamtechnologies.com; 
onap-discuss@lists.onap.org
 Subject: 答复: Re: [onap-discuss]答复:   [modeling] Comparison of R2 proposed IM 
classes and IFA011


 

Hi Alex

 

 As a model contributor, join the discussion.

 Could you give the specific HPA parameters and completed usecases in R2? 

 Does the LAB need to provide some specific hardwares to test these 
features? 

 If we model the HPA parameters and implemented in R2, I think some real 
implemented inputs are needed.

 

Thanks

Maopeng


原始邮件



发件人：Vul,Alex 



收件人：yangxu (H) jessie jewitt 
onap-discuss@lists.onap.org   




日 期 ：2018年03月01日 16:48



主 题 ：Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM classes and 
IFA011




___
 onap-discuss mailing list
 onap-discuss@lists.onap.org
 https://lists.onap.org/mailman/listinfo/onap-discuss
 
  


Jessie, Xu


 


There are a few things still missing from the agreed upon model. We need to add 
in items related to   the HPA support. HPA is a functional requirement being 
implemented  in R2. We need to ensure that the agreed upon model does not 
preclude the implementation of HPA.


 


Thank you,


 


Alex Vul


Intel Corporation


 


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of yangxu (H)
 Sent: Thursday, March 1, 2018 9:29 AM
 To: jessie jewitt ; 
onap-discuss@lists.onap.org
 Subject: [onap-discuss] 答复: [modeling] Comparison of R2 proposed IM classes 
and IFA011




 


Hi Jessie,


 


For the agreement, please look at 
https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version.


The differences with IFA011 are shown in orange.


As for “vnfProductName”, the agreement is to have the same name as IFA011   for 
the time being.


 


Best regards,


Xu


 


发件人: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] 代表 jessie jewitt
 发送时间: 2018年2月28日   23:45
 收件人: onap-discuss@lists.onap.org
 主题: [onap-discuss] [modeling] Comparison of R2 proposed IM classes and IFA011


 


Hi-


I'm trying to understand how the IM model proposed for R2 compares to 
IFA011.



 


When I look on this wiki:



https://wiki.onap.org/display/DW/Resource+IM+Discussion+Based+on+IFA011



 


it looks like the IFA011 model was reviewed and decisions were made. For 
example, in the VNFD, one decision was to rename vnfProductName   to Name. It 
is marked as "AGREED".



 


However, when I look at the R2 class VNFD, the attribute is still called 

[onap-discuss] 答复: RE: Re: 答复: [modeling] Comparison of R2 proposed IM classes and IFA011

[zhang.maopeng1]

Alex






The "requestAdditionalCapabilities" are mainly keyvalue pairs in the IFA011.


 In R2,  the HPA related KEYs should be as inputs and the key name or value 
structure should be discussed in the model.






BR


Maopeng



原始邮件



发件人：Vul,Alex 
收件人：张茂鹏10030173;
抄送人：yang...@huawei.com jessie.jew...@oamtechnologies.com 
onap-discuss@lists.onap.org 

日 期 ：2018年03月01日 19:23
主 题 ：RE: Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM classes 
and IFA011




Maopeng,


 


Forgot to mention one more thing…


 


Already existing VNFs, with already existing VNFDs that use alternative IFA011 
HPA specification format, based on “requestAdditionalCapabilities” attribute, 
are  not going to be impacted by this change… VNFs that are used as part of the 
VoLTE use cases don’t need to be converted to the new format, unless there a 
desire to do so…


 


Same goes for already existing HEAT based VNFs…


 


Kind regards,


 


Alex Vul


Intel Corporation


 


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, March 1, 2018 10:25 AM
 To: Vul, Alex 
 Cc: yang...@huawei.com; jessie.jew...@oamtechnologies.com; 
onap-discuss@lists.onap.org
 Subject: 答复: Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM 
classes and IFA011


 

Hi Alex

 

 As a model contributor, join the discussion.

 Could you give the specific HPA parameters and completed usecases in R2? 

 Does the LAB need to provide some specific hardwares to test these 
features? 

 If we model the HPA parameters and implemented in R2, I think some real 
implemented inputs are needed.

 

Thanks

Maopeng


原始邮件



发件人：Vul,Alex 



收件人：yangxu (H) jessie jewitt 
onap-discuss@lists.onap.org  




日 期 ：2018年03月01日 16:48



主 题 ：Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM classes and 
IFA011




___
 onap-discuss mailing list
 onap-discuss@lists.onap.org
 https://lists.onap.org/mailman/listinfo/onap-discuss
 
  


Jessie, Xu


 


There are a few things still missing from the agreed upon model. We need to add 
in items related to  the HPA support. HPA is a functional requirement being 
implemented  in R2. We need to ensure that the agreed upon model does not 
preclude the implementation of HPA.


 


Thank you,


 


Alex Vul


Intel Corporation


 


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of yangxu (H)
 Sent: Thursday, March 1, 2018 9:29 AM
 To: jessie jewitt ; 
onap-discuss@lists.onap.org
 Subject: [onap-discuss] 答复: [modeling] Comparison of R2 proposed IM classes 
and IFA011




 


Hi Jessie,


 


For the agreement, please look at 
https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version.


The differences with IFA011 are shown in orange.


As for “vnfProductName”, the agreement is to have the same name as IFA011  for 
the time being.


 


Best regards,


Xu


 


发件人: onap-discuss-boun...@lists.onap.org   
[mailto:onap-discuss-boun...@lists.onap.org] 代表 jessie jewitt
 发送时间: 2018年2月28日  23:45
 收件人: onap-discuss@lists.onap.org
 主题: [onap-discuss] [modeling] Comparison of R2 proposed IM classes and IFA011


 


Hi-


I'm trying to understand how the IM model proposed for R2 compares to 
IFA011.



 


When I look on this wiki:



https://wiki.onap.org/display/DW/Resource+IM+Discussion+Based+on+IFA011



 


it looks like the IFA011 model was reviewed and decisions were made. For 
example, in the VNFD, one decision was to rename vnfProductName  to Name. It is 
marked as "AGREED".



 


However, when I look at the R2 class VNFD, the attribute is still called 
"vnfProductName".



 


Should I be ignoring the decisions made on the wiki above?



Is there another place that shows the differences between the R2 classes and 
IFA011.



 


Thanks for your help,



Jessie___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: Re: 答复: [modeling] Comparison of R2 proposed IM classes and IFA011

[zhang.maopeng1]

Hi Alex







 As a model contributor, join the discussion.


 Could you give the specific HPA parameters and completed usecases in R2? 


 Does the LAB need to provide some specific hardwares to test these 
features? 


 If we model the HPA parameters and implemented in R2, I think some real 
implemented inputs are needed.






Thanks


Maopeng







原始邮件



发件人：Vul,Alex 
收件人：yangxu (H) jessie jewitt 
onap-discuss@lists.onap.org 

日 期 ：2018年03月01日 16:48
主 题 ：Re: [onap-discuss]答复:  [modeling] Comparison of R2 proposed IM classes and 
IFA011


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

  

Jessie, Xu


 


There are a few things still missing from the agreed upon model. We need to add 
in items related to the HPA support. HPA is a functional requirement being 
implemented  in R2. We need to ensure that the agreed upon model does not 
preclude the implementation of HPA.


 


Thank you,


 


Alex Vul


Intel Corporation


 


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of yangxu (H)
 Sent: Thursday, March 1, 2018 9:29 AM
 To: jessie jewitt ; 
onap-discuss@lists.onap.org
 Subject: [onap-discuss] 答复: [modeling] Comparison of R2 proposed IM classes 
and IFA011




 


Hi Jessie,


 


For the agreement, please look at 
https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version.


The differences with IFA011 are shown in orange.


As for “vnfProductName”, the agreement is to have the same name as IFA011 for 
the time being.


 


Best regards,


Xu


 


发件人: onap-discuss-boun...@lists.onap.org  
[mailto:onap-discuss-boun...@lists.onap.org] 代表 jessie jewitt
 发送时间: 2018年2月28日 23:45
 收件人: onap-discuss@lists.onap.org
 主题: [onap-discuss] [modeling] Comparison of R2 proposed IM classes and IFA011


 


Hi-


I'm trying to understand how the IM model proposed for R2 compares to 
IFA011.



 



When I look on this wiki:



https://wiki.onap.org/display/DW/Resource+IM+Discussion+Based+on+IFA011



 



it looks like the IFA011 model was reviewed and decisions were made. For 
example, in the VNFD, one decision was to rename vnfProductName to Name. It is 
marked as "AGREED".



 



However, when I look at the R2 class VNFD, the attribute is still called 
"vnfProductName".



 



Should I be ignoring the decisions made on the wiki above?



Is there another place that shows the differences between the R2 classes and 
IFA011.



 



Thanks for your help,



Jessie___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] About Runtime Catalog

[zhang.maopeng1]

Hi Michael






As you said in the ARC and TSC meeting there are some SDC codes, which have 
the willing to be reused in the RTC, could you give the specifical sdc 
component or codes gerrit links that you mentioned?


If provided, it will help the RTC team to evaluate the code value and 
whether it can satisfy the RTC requirements.


Thanks






BR


Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: RE: Re: [onap-tsc] Official ONAP ArchitectureSlide

[zhang.maopeng1]

Hi Jamil


   


From the VFC project coming into ONAP, VFC focus on ETSI NFV implimention, 
which is well-known in the community.


In R1 arch, VFC marked with ETSI NFV is no problem, which can make the 
reader more clear about the main-contribution project.


Because VFC as one project in ONAP, so say ONAP implement ETSI NFV, it is 
OK as well.  But the mapping pre-shared really confuses the reader.


As I know ONAP scope is more the ETSI NFV, also SDN domain and service 
domain.





BR


Maopeng



原始邮件




发件人： ;
收件人：张茂鹏10030173; ;
抄送人： ; ; 
; ; 
;
日 期 ：2017年11月15日 23:47
主 题 ：RE: RE: Re: [onap-discuss] [onap-tsc] Official ONAP ArchitectureSlide







Hi Maopeng


I understand that it is not easy to map ETSI to ONAP architecture. But I don’t 
think by putting VFC aligned with ETSI NFV make any sense.


As we are in one project my preference is to mention that ONAP is a way to 
implement ETSI NFV functionalities.


Regards


jamil


 


 


De : zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Envoyé : mercredi 15 novembre 2017 08:54
 À : CHAWKI Jamil IMT/OLN; christopher.don...@huawei.com
 Cc : kp...@linuxfoundation.org; onap-discuss@lists.onap.org
 Objet : 答复: RE: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


 

Hi Jamil

 

As the reader, It will confus me about the mapping method.  It does not 
make sense.

About the interfaces, I have explained in the another email. 

VFC mainly focus on the NSLCM and VNFLCM, which mainly is align to the ETSI 
NFV LCM related interfaces. 

VFC also provides the driver to adaptor more vendor VNFM to do the 
integration. 

 

BR

Maopeng


原始邮件



发件人： ;



收件人：张茂鹏10030173;



抄送人： ; ;



日 期 ：2017年11月14日  19:54



主 题 ：RE: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide




 


Hi Maopeng

In slide 9 you have a  first mapping of ONAP architecture to ETSI NFV one.  

For APPC stream NFVO is distributed between SO and DCAE. The VNFM is also 
distributed in SO, APPC and DCAE.

Regards

Jamil


 


De : zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Envoyé : mardi 14 novembre 2017 11:44
 À : CHAWKI Jamil IMT/OLN
 Cc : kp...@linuxfoundation.org; onap-discuss@lists.onap.org
 Objet : 答复: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


 

Hi jamil

  

   One quick question:

   How is the ONAP architecture Functionally aligned with ETSI NFV?  Which 
components are NFVO and VNFM in the ONAP aligned   with ETSI NFV?

   Thanks

 

BR

Maopeng


原始邮件



发件人： ;



收件人： ; ;   
; ;  
;



日 期 ：2017年11月14日  17:43



主 题 ：Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide




 



Hello Kenny


I have a question on the ETSI aligned of VFC module, to my knowledge the VFC 
interfaces   are not aligned with ETSI NFV.


I think we need to remove this term from VFC and to add that ONAP architecture 
is Functionally   aligned with ETSI NFV.


Regards


Jamil


 



De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
De la part de Kenny Paul
 Envoyé : mardi 14 novembre 2017 01:04
 À : onap-discuss; onap-tsc
 Cc : Lisa Caywood
 Objet : [onap-tsc] Official ONAP Architecture Slide




 


As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least. 


The officially approved image for the Amsterdam Architecture and be found here:



https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2



 


 


 


In preparation for the release announcement here is what we are asking in order 
of priority:



 



-If an archecture image is referecned in your official readthedocs 
documentation, please use this image 




 


-If an archecture image is referenced in your wiki pages,  please add the URL 
above to reference the the image.




 


-If an archecture image is referecned in a presentation slide deck, please 
ensure you use this image.




 


I am intentionally NOT distributing it because that is how we ended up with so 
many versions in the first place. :-)


 


Thanks!



 


 


 


Best Regards, 
 -kenny
 
 Kenny Paul,  Technical Program Manager
 kp...@linuxfoundation.org
 510.766.5945






 




_
  Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous 

[onap-discuss] 答复: Re: [onap-tsc] Official ONAP Architecture Slide

[zhang.maopeng1]

Hi  Susana,






  VFC project in R1 includes NFVO and VNFM components, mainly 
focused on the NS LCM and VNFLCM.


 NSLCM  NBI and GVNFM NBI  please refer to 
https://wiki.onap.org/display/DW/VF-C+R1+Deliverables  NSLCM API Specification 
v0.1.  and GVNFM API Specification v0.1.


 As the project started, NSLCM and GVNFM mainly refer to IFA 
document and refer to the SOL Draft, because the SOL does not provide engough 
APIs and is not published at that time.


 Now SOL003 is published and SOL005 is still in the draft(almost 
stable), I compare the API of the SOL, the main flow is same and most of LCM 
interfaces be aligned.


 In the following release, VFC team will plan to align the SOL as 
needed and also consider the usecase requirements.



 In the R1, VFC has more work on the integration with other ONAP 
componenst. The document is not well formatted, we will try to do it in the 
next release.


 If interested about VFC projects, welcome to join, thanks.





BR


Maopeng



原始邮件




发件人： ;
收件人： ; ; 
; ; 
; ;
日 期 ：2017年11月14日 22:25
主 题 ：Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide








Hi,


 


Is it so that VF-C interfaces are not aligned with ETSI NFV ones? In the 
documentation of VF-C it appeared like aligned, but I observed  the reference 
is made to IFA007 and IFA008 and not to the published APIs, as opposed to 
referencing SOL005 for NS LCM.


In any case, it is difficult to find now the documentation of the VF-C; 
wouldn’t it be good to add relevant links to the modules, their  documentation, 
user guides, etc in the Amsterdam arch page?


 


Regards


/Susana


 

 

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of jamil.cha...@orange.com
 Sent: Tuesday, November 14, 2017 10:41 AM
 To: Kenny Paul ; onap-discuss 
; onap-tsc ; Arpit 
Joshipura (ajoship...@linuxfoundation.org) ; 
Lisa Caywood 
 Subject: Re: [onap-tsc] Official ONAP Architecture Slide




 


Hello Kenny


I have a question on the ETSI aligned of VFC module, to my knowledge the VFC 
interfaces are not aligned with ETSI NFV. 


I think we need to remove this term from VFC and to add that ONAP architecture 
is Functionally aligned with ETSI NFV..


Regards


Jamil


 



De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
De la part de Kenny Paul
 Envoyé : mardi 14 novembre 2017 01:04
 À : onap-discuss; onap-tsc
 Cc : Lisa Caywood
 Objet : [onap-tsc] Official ONAP Architecture Slide




 


As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least. 


The officially approved image for the Amsterdam Architecture and be found here:



https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2



 


 


 


In preparation for the release announcement here is what we are asking in order 
of priority:



 



-If an archecture image is referecned in your official readthedocs 
documentation, please use this image 




 


-If an archecture image is referenced in your wiki pages,  please add the URL 
above to reference the the image.




 


-If an archecture image is referecned in a presentation slide deck, please 
ensure you use this image.




 


I am intentionally NOT distributing it because that is how we ended up with so 
many versions in the first place. :-)


 


Thanks!



 


 


 


Best Regards, 
 -kenny
 
 Kenny Paul,  Technical Program Manager
 kp...@linuxfoundation.org
 510.766.5945






 



_
   Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez 
le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les 
messages electroniques etant susceptibles d'alteration, Orange decline toute 
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.   This 
message and its attachments may contain confidential or privileged information 
that may be protected by law; they should not be distributed, used or copied 
without authorisation. If you have received this email in error, please notify 
the sender and delete this message and its attachments. As emails may be 
altered, Orange is not liable for messages that have been modified, changed or 
falsified. Thank 

[onap-discuss] Update the ONAP R2+ Service IM Discussion Page, please concern the issues, thanks

[zhang.maopeng1]

Hi David, Jimmy, and Andy, Kevin


   


please confirm some questions below about the ECOMP Model document.






   1. about the class Figure 2 ONAP Service Components


@ Andy Mayer   @ Kevin Scaggs


   1.1.  why does serviceComponentInstance and ResourceInstances use 
reference, but the ServiceInstance uses ComposedOf?


   1.2. Could we unify term among the catalogItem, specification and 
description in the left blocks of the diagram?


   Suggest: In the design time, use package represents all files of 
service;  use Description represent the service templete or specification.


 


   2. about the clase figure 3 ONAP  Service Characteristics


   2.1. @ Jimmy Forsyth  David Shadmi @ Andy Mayer   @ Kevin Scaggs  
is the AAI and SDC align to the diagram above?  If not, does the model need to 
be changed?


   2.2. @Andy Mayer @ Kevin ScaggsServiceDesc's attributes are directly 
definited, not using the method above. Please confirm it.


   2.3. @ Andy Mayer  @ Kevin Scaggs in the diagram above, there is no 
ServiceCatalogItemType, but in the document it exits.


 
ServiceNetworkAssociation and serviceRecipe are the same question.


  Please 
confirm them and update the diagram if needed.


 



BR


Maopeng



原始邮件




发件人：张茂鹏10030173
收件人： ; ; ;
抄送人： ; ; 
;
日 期 ：2017年11月14日 19:39
主 题 ：Update the ONAP R2+ Service IM Discussion Page,  please concern the 
issues, thanks








Hi David, Jimmy, and Andy






   I update the wiki page: 
https://wiki.onap.org/pages/viewpage.action?pageId=16004631.


   The issues with the name of yours is updated. Please help me to confirm with 
them. If the your name related the issue are wrong, please correct them.


   Hope we can make the service model agreement as much as we can.


   Thanks.






BR


Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: Re: [onap-tsc] Official ONAP Architecture Slide

[zhang.maopeng1]

Hi jamil


  


   One quick question:


   How is the ONAP architecture Functionally aligned with ETSI NFV?  Which 
components are NFVO and VNFM in the ONAP aligned with ETSI NFV?


   Thanks






BR


Maopeng



原始邮件




发件人： ;
收件人： ; ; 
; ; 
;
日 期 ：2017年11月14日 17:43
主 题 ：Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide








Hello Kenny


I have a question on the ETSI aligned of VFC module, to my knowledge the VFC 
interfaces are not aligned with ETSI NFV.


I think we need to remove this term from VFC and to add that ONAP architecture 
is Functionally aligned with ETSI NFV.


Regards


Jamil


 



De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
De la part de Kenny Paul
 Envoyé : mardi 14 novembre 2017 01:04
 À : onap-discuss; onap-tsc
 Cc : Lisa Caywood
 Objet : [onap-tsc] Official ONAP Architecture Slide




 


As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least. 


The officially approved image for the Amsterdam Architecture and be found here:



https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2



 


 


 


In preparation for the release announcement here is what we are asking in order 
of priority:



 



-If an archecture image is referecned in your official readthedocs 
documentation, please use this image 




 


-If an archecture image is referenced in your wiki pages,  please add the URL 
above to reference the the image.




 


-If an archecture image is referecned in a presentation slide deck, please 
ensure you use this image.




 


I am intentionally NOT distributing it because that is how we ended up with so 
many versions in the first place. :-)


 


Thanks!



 


 


 


Best Regards, 
 -kenny
 
 Kenny Paul,  Technical Program Manager
 kp...@linuxfoundation.org
 510.766.5945






 




_
 Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez 
le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les 
messages electroniques etant susceptibles d'alteration, Orange decline toute 
responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This 
message and its attachments may contain confidential or privileged information 
that may be protected by law; they should not be distributed, used or copied 
without authorisation. If you have received this email in error, please notify 
the sender and delete this message and its attachments. As emails may be 
altered, Orange is not liable for messages that have been modified, changed or 
falsified. Thank you.___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: Official ONAP Architecture Slide

[zhang.maopeng1]

Hi






  There maybe is lack of Usecase UI project in picture.  It is important in the 
VoLTE usecase R1.  could anyone confirm with it?  Thanks.





BR


Maopeng



原始邮件




发件人： ;
收件人： ; ;
日 期 ：2017年11月14日 08:04
主 题 ：[onap-discuss] Official ONAP Architecture Slide






As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least. 
The officially approved image for the Amsterdam Architecture and be found here:

https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2


In preparation for the release announcement here is what we are asking in order 
of priority:



-If an archecture image is referecned in your official readthedocs 
documentation, please use this image 



-If an archecture image is referenced in your wiki pages,  please add the URL 
above to reference the the image.



-If an archecture image is referecned in a presentation slide deck, please 
ensure you use this image.

I am intentionally NOT distributing it because that is how we ended up with so 
many versions in the first place. :-)

Thanks!





Best Regards, -kennyKenny Paul,  Technical Program 
Managerkpaul@linuxfoundation.org510.766.5945___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: Re: [SDC] About vnf package imported and onboard.

[zhang.maopeng1]

hi all






   I add yuanxing in the loop. Yuanxing will be in charge of the ZTE VNF 
package.  If set up a call, please info yuanxing.






Best Regards


Maopeng







原始邮件



发件人：袁虎10090474
收件人： ; ;
抄送人： ; ; 
;张茂鹏10030173;赵化冰10201488;李滋00164331;
日 期 ：2017年10月10日 10:05
主 题 ：答复: RE: Re: [SDC] About vnf package imported and onboard.







Hi Tal,




Can you show me recently?


And Can send the  example of vCSCF vnf package to me first?






Thanks,


Yuan Hu

















发件人： ;
收件人：袁虎10090474; ;
抄送人： ; ;张茂鹏10030173;
日 期 ：2017年10月10日 01:15
主 题 ：RE: Re: [SDC] About vnf package imported and onboard.








Tal:


Please set up call with them to show the flow from onboarding to import on the 
vCSCF.


 


 


 


 


 


 


BR,


 


Michael Lando


Opensource TL , SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


From: yuan@zte.com.cn [mailto:yuan@zte.com.cn] 
 Sent: Monday, October 09, 2017 7:42 AM
 To: Lando,Michael ; SHADMI, DAVID 
 Cc: Lando,Michael ; SHADMI, DAVID ; 
onap-discuss@lists.onap.org; zhang.maope...@zte.com.cn
 Subject: 答复: Re: [SDC] About vnf package imported and onboard.


 

Hi Michael,

 

This is the home page of the latest version of SDC.

But, I did not see the menu for importing and onboard a VNF package.

How to import and onboard a vnf package designed with a third-party platform?

At the same time, can you give me an example of vnf package?



 


Thanks,


Yuan Hu

 


原始邮件



发件人：袁虎10090474



收件人： ;



抄送人： ; ;张茂鹏10030173;



日 期 ：2017年09月30日 09:14



主 题 ：答复: Re: [SDC] About vnf package imported and onboard.




 


Hi Michael,

 

I have already installed this version of SDC.

And how to import and onboard a vnf package designed with a third-party 
platform.

Is there a manual?

 

Thanks,

Yuan Hu

 

 




发件人： ;



收件人：袁虎10090474; ;



抄送人： ;张茂鹏10030173;



日 期 ：2017年09月29日 15:18



主 题 ：Re: [SDC] About vnf package imported and onboard.




 



The code is in.
 The tag you describe will provide you with the correct docker.
 
  Original Message 
 From: yuan@zte.com.cn
 Date: Fri, Sep 29, 2017, 08:44
 To: "Lando,Michael" , "SHADMI, DAVID" 
 CC: onap-discuss@lists.onap.org, zhang.maope...@zte.com.cn
 Subject: [SDC] About vnf package imported and onboard.
 
 
 Hi Michael and David,
 
 
 I saw you submit the code for importing and onboard of vnf package.
 
 Did you already support this function?
 
 And which version of docker images supports this function? 1.1-STAGING-latest?
 
 I want to test it.
 
 
 Thanks,
 
 Yuan Hu___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: 答复：[vfc][sdnc] How VFC will store network info in A

[zhang.maopeng1]

hi gaurav.agrawal






   In my mind, based on the AAI current schema, the network and subnetwork 
should be stored in the AAI in the following schema:


 /network/l3-networks/l3-network/{network-id}



 /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}


 


BR


Maopeng



原始邮件



发件人： ;
收件人： ;张茂鹏10030173;
抄送人： ;
日 期 ：2017年10月09日 14:00
主 题 ：RE: [onap-discuss] 答复：[vfc][sdnc] How VFC will store network info in A








Hi Maopeng/Yang Xu,


 


Do we have any update on this? This integration piece is pending kindly support.


 


Thanks and Regards,


Gaurav


 



From: Yang Xu (Yang, Fixed Network) 
 Sent: 2017年9月28日  12:43
 To: Gaurav agrawal; zhang.maope...@zte.com.cn
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] 答复：[vfc][sdnc] How VFC will store network info in 
A




 


Hi Maopeng,
 
 We discussed this topic in F2F meeting yesterday. Would you please provide us 
the name of the developer who can help on VFC side so we can follow up 
directly? time is running out, please help.
 
 Thanks,
 -Yang
 
 Sent from HUAWEI AnyOffice




From:Gaurav agrawal



To:zhang.maope...@zte.com.cn,Yang Xu (Yang, Fixed Network)



Cc:onap-discuss@lists.onap.org



Date:2017-09-27 09:32:53



Subject:RE: [onap-discuss] 答复：[vfc][sdnc] How VFC will store network info in 
A



 



Hi Maopeng,


 


Let me provide my understanding on this topic, @Yang Xu please add to it.


 


This is required in case of VoLTE use case wherein SDNC needs to associate 
local network within datacenter to a VXLAN tunnel available between datacenters 
(edge and core). In this regard we expect user to input the network name and 
find the associated networkId in SDNC by referring to  the local network 
information added by VFC in A


 


Input from UUI 
(https://gerrit.onap.org/r/#/c/12933/2/catalog-be/src/main/resources/import/tosca/normative-types/overlayTunnel/overlayTunnel.yml)





 


Request to 3rd party controller from SDNC:


{


"l3-dci-connect": {


"id": "CDD702C3-7719-4FE6-A5AD-3A9C9E265309", 


 "name": "PODX-routerY", 


 "description": "VPC A connect VPC B", 


 "router_id": "CBB702C3-6789-1234-A5AD-3A9C9E265309", 


 "firewall_enable":  "false“ //false


"local_networks": 
["8a41319d-87cf-4cd6-8957-f4a1066c63a8","c1134ed3-dce8-41c4-af81-2b15834f0c7a"],
 


 "local_network_all":false, 


 "evpn_irts":  ["1:5000"],  


 "evpn_erts":  ["1:5000" ], 


 "l3_vni": "5001", 


 }


}


 


Thanks and Regards,


Gaurav


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhang.maope...@zte.com.cn
 Sent: 2017年9月26日  13:11
 To: Yang Xu (Yang, Fixed Network)
 Cc: onap-discuss@lists.onap.org
 Subject: [onap-discuss] 答复：[vfc][sdnc] How VFC will store network info in A



 


hi yang 
 
 could you clearfy the network and subnetwork info from sdnc in the whole case, 
and how does the sdnc use it? 
 
 
 BR 
 maopeng


原始邮件 



发件人： YangXu(Yang,FixedNetwork); 



收件人： 张茂鹏10030173; onap-discuss@lists.onap.org; 



抄送人： chinamobile; 



日期：2017-09-21 14:35:16



主题：[vfc][sdnc] How VFC will store network info in A 




Hi Maopeng and VFC team,


 


SDNC team needs to know some information about the networks created by VFC, 
e.g. network id and subnet. Where does VFC store the network information in 
A? Can you point to us A node and attributes used for such information? 
An A  query example would be greatly appreciated.


 


Regards,


-Yang___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复：[vfc][sdnc] How VFC will store network info in A

[zhang.maopeng1]

hi yang



could you clearfy the network and subnetwork info from sdnc in the whole case, 
and how does the sdnc use it?





BR

maopeng








 

 原始邮件
 
 

 

 

 

 
 发件人：
 YangXu(Yang,FixedNetwork)
 

 
 收件人：
 张茂鹏10030173
 onap-discuss@lists.onap.org
 

 
 抄送人：
 chinamobile
 

 
 日期：2017-09-21 14:35:16
 

 
 主题：[vfc][sdnc] How VFC will store network info in A
 

 

 
 
 
 
 
 


 
 
 
Hi Maopeng and VFC team,
 

 
 

 
  
 

 
 
SDNC team needs to know some information about the networks created by VFC, 
e.g. network id and subnet. Where does VFC store the network information in 
A? Can you point to us A node and attributes used for such information? 
An A query example would be greatly appreciated. 
 

 
 

 
  
 

 
 
Regards,
 

 
 
-Yang___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: VNF instantiation sequence

[zhang.maopeng1]

hello yangxu

   

 In the VoLTE case, I don't receive the requirements from the VNF vendor 
that one vnf depends on the others.

 So in the R1, VoLTE case do not need todefine the VNF sequence.  In the 
futrue, we can cooperate with SDC team to do it if needed.




We have tried to support the VNF instantiation parallel in R1. Because the 
time is limited, we put it as an strecth goal.







BR

Maopeng








原始邮件



发件人： 
收件人：  
日 期 ：2017年09月08日 01:35
主 题 ：[onap-discuss] VNF instantiation sequence







Hi Yang Yan,


 


We are working on vEPC and vIMS network service design. Two questions came up:


 


a.   Do we need to define VNF instantiation sequence in SDC?


b.  If no VNF sequence is defined, does/can VFC instantiate VNFs in 
parallel?


 


Regards,


-Yang___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: Re: Invitation: SDC & VFC integration meeting @Fri2017-09-01 9pm - Sat 2017-09-02 12am (CST) (onap-discuss@lists.onap.org)

[zhang.maopeng1]

Hi david

  

I think “Network Service” and “E2E Service”  categories as predefined in R1 
are OK for VFC.   For SO, please seshu and chuanyu confirm with it.

   Thanks




BR

Maopeng




原始邮件



发件人： 
收件人：冯远兴10034308
抄送人：    
张茂鹏10030173  
 
日 期 ：2017年09月06日 02:52
主 题 ：RE: Re: [onap-discuss] Invitation: SDC & VFC integration meeting 
@Fri2017-09-01 9pm - Sat 2017-09-02 12am (CST) (onap-discuss@lists.onap.org)







Hi,


 


I manually added the two categories using SDC Admin role.



 My suggestion is to use “Network Service” and “E2E Service”, as it generic and 
would allow SO to implement a generic support for these two type of services.


If there is an agreement on these two categories, we would include them in the 
predefined list of service categories.


 


Thanks,


David


 


 


From: feng.yuanx...@zte.com.cn [mailto:feng.yuanx...@zte.com.cn] 
 Sent: Monday, September 04, 2017 9:32 PM
 To: SHADMI, DAVID 
 Cc: zhaohuab...@gmail.com LEVY, DONALD E  LANDO, MICHAEL 
 yangya...@chinamobile.com zhang.maope...@zte.com.cn 
denglin...@chinamobile.com denghu...@huawei.com onap-discuss@lists.onap.org
 Subject: 答复: Re: [onap-discuss] Invitation: SDC & VFC integration meeting @ 
Fri2017-09-01 9pm - Sat 2017-09-02 12am (CST) (onap-discuss@lists.onap.org)


 

Hi David,

 

Thanks for your presentation which was really helpful.

I imported your nsd.yml and underlayvpn.yml in my sdc portal and it works. 
After that I succeed to create two VFs(vIMS and vEPC).  

Unfortunately, I can't find two category types(Network Service and E2E 
Service). I use VolteNS instead. Does it make difference? BTW, my sdc 
version is:1.1-STAGING-latest．

 

 

 

BR

Feng yuanxing

 

 

 

 


原始邮件



发件人： 



收件人：     
张茂鹏10030173   
 



日 期 ：2017年09月02日 07:31



主 题 ：Re: [onap-discuss] Invitation: SDC & VFC integration meeting @ 
Fri2017-09-01 9pm - Sat 2017-09-02 12am (CST) (onap-discuss@lists.onap.org)




 


Hello All,



 


Here is the summary of the call we had today:



 


1.   CSAR format – I update the slide we discussed on Monday based on 
today’s call






  


2.   VoLTE E2E service


a.   Enclosed please find the NSD and underlayvpn node type definition I 
used in the call.


b.   Use the following steps to create the VoLTE E2E service:


i.Import and certify the NSD.yml as VFC


ii.Import and certify the underlayvpn.yml as VL


iii.Create vIMS and vEPC services to get the uuid and invariantUUID 
information needed for the vIMS and vEPC NSs


iv.Create vIMS_NS VF as new AllottedResources (Network Service 
subcategory)


1.   Add the NSD VFC and populate the properties


2.   Define all properties as inputs (had to do that for the properties to 
be visible when generating the VoLTE service TOSCA)


v.Create vEPC_NS VF – same steps as in #4


vi.Create the VoLTE E2E service with vIMS, vEPC, and underlayvpn


  


Thanks,



David



 


-Original Appointment-
  From: ONAP [mailto:f26tu6tqeqou1li98n7uvq6...@group.calendar.google.com] 
  Sent: Monday, August 28, 2017 9:25 PM
  To: ONAP LEVY, DONALD E LANDO, MICHAEL yangya...@chinamobile.com 
zhang.maope...@zte.com.cn denglin...@chinamobile.com denghu...@huawei.com 
onap-discuss@lists.onap.org
  Subject: [onap-discuss] Invitation: SDC & VFC integration meeting @ Fri 
2017-09-01 9pm - Sat 2017-09-02 12am (CST) (onap-discuss@lists.onap.org)
  When: Friday, September 01, 2017 8:00 AM-11:00 AM (UTC-06:00) Central Time 
(US & Canada).
  Where: https://zoom.us/j/648493837



   


more  details »
  


SDC & VFC integration meeting



When


Fri 2017-09-01 9pm – Sat 2017-09-02 12am China Time - Beijing


   


Where


https://zoom.us/j/648493837 (map)


   


Calendar


onap-discuss@lists.onap.org


   


Who


•


Huabing Zhao - creator


   


•


dl2...@att.com


   


•


ml6...@att.com


   


•


yangya...@chinamobile.com


   


•


zhang.maope...@zte.com.cn


   


•


denglin...@chinamobile.com


   


•


denghu...@huawei.com


   


•


onap-discuss@lists.onap.org


   


 


   


Hi there, 




ZTE Open Source is inviting you to a scheduled Zoom meeting. 




Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/648493837




Or iPhone one-tap :
  US: +14086380968,,648493837# or +16468769923,,648493837# 
  Or Telephone：
  Dial(for higher quality, dial a number based on your current 

[onap-discuss] 答复: RE: Invitation: SDC & VFC integration meeting @ Fri2017-09-01 9pm - Sat 2017-09-02 12am (CST) (onap-discuss@lists.onap.org)

[zhang.maopeng1]

Hi David




Thanks for your greatful work.

This is the record URL: 
https://zoom.us/recording/play/KIwLvr5cJb2Q_vx1BdHBTF0-f-pFpTkD_gpO3iBSeq5VDapCSe-FjbbhS2LkTygO
 




BR

Maopeng



原始邮件



发件人： 
收件人：    
张茂鹏10030173  
 
日 期 ：2017年09月02日 07:30
主 题 ：RE: [onap-discuss] Invitation: SDC & VFC integration meeting @ 
Fri2017-09-01 9pm - Sat 2017-09-02 12am (CST) (onap-discuss@lists.onap.org)





 Hello All,
 Here is the summary of the call we had today:
 CSAR format – I update the slide we discussed on Monday based on today’s call


 
  VoLTE E2E service

Enclosed please find the NSD and underlayvpn node type definition I used in the 
call.

Use the following steps to create the VoLTE E2E service:

Import and certify the NSD.yml as VFC

Import and certify the underlayvpn.yml as VL

Create vIMS and vEPC services to get the uuid and invariantUUID information 
needed for the vIMS and vEPC NSs

Create vIMS_NS VF as new AllottedResources (Network Service subcategory)

Add the NSD VFC and populate the properties

Define all properties as inputs (had to do that for the properties to be 
visible when generating the VoLTE service TOSCA)

Create vEPC_NS VF – same steps as in #4

Create the VoLTE E2E service with vIMS, vEPC, and underlayvpn

  Thanks,
David
  -Original Appointment-
  From: ONAP [mailto:f26tu6tqeqou1li98n7uvq6...@group.calendar.google.com] 
  Sent: Monday, August 28, 2017 9:25 PM
  To: ONAP LEVY, DONALD E LANDO, MICHAEL yangya...@chinamobile.com 
zhang.maope...@zte.com.cn denglin...@chinamobile.com denghu...@huawei.com 
onap-discuss@lists.onap.org
  Subject: [onap-discuss] Invitation: SDC & VFC integration meeting @ Fri 
2017-09-01 9pm - Sat 2017-09-02 12am (CST) (onap-discuss@lists.onap.org)
  When: Friday, September 01, 2017 8:00 AM-11:00 AM (UTC-06:00) Central Time 
(US & Canada).
  Where: https://zoom.us/j/648493837
   more details »
  SDC & VFC integration meeting
WhenFri 2017-09-01 9pm – Sat 2017-09-02 12am China Time - Beijing   
Wherehttps://zoom.us/j/648493837 (map)   Calendar
onap-discuss@lists.onap.org   Who•Huabing Zhao - creator
   •dl2...@att.com   •ml6...@att.com   •
yangya...@chinamobile.com   •zhang.maope...@zte.com.cn   •  
  denglin...@chinamobile.com   •denghu...@huawei.com   •
onap-discuss@lists.onap.org   Hi there, 

ZTE Open Source is inviting you to a scheduled Zoom meeting. 

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/648493837

Or iPhone one-tap :
  US: +14086380968,,648493837# or +16468769923,,648493837# 
  Or Telephone：
  Dial(for higher quality, dial a number based on your current location)：
  US: +1 408 638 0968 or +1 646 876 9923 
  Meeting ID: 648 493 837
  International numbers available: 
https://zoom.us/zoomconference?m=1O70GAs-yNBBPJICgPTuoy42OL0_AxkM

Going?   Yes - Maybe - Nomore options »
Invitation from Google Calendar 
You are receiving this courtesy email at the account 
onap-discuss@lists.onap.org because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. 
Alternatively you can sign up for a Google account at 
https://www.google.com/calendar/ and control your notification settings for 
your entire calendar.

Forwarding this invitation could allow any recipient to modify your RSVP 
response. Learn More.
<< File: invite.ics >>  << File: ATT1.txt >>___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] About deploy the DMaaP

[zhang.maopeng1]

Hi Varun



  I want to install the dmaap as an develop environment, and run it alone.

  Could you give me some introduction?




Thank you

Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: Re: Re: [SDC] Access sdc api failed.

[zhang.maopeng1]

hi micheal




Thanks for your sharing. 

   

   In the wiki:https://wiki.onap.org/display/DW/Consumer+creation 

The following users are predefined:

appc

vid

dcae

aai

sdnc

mso




   could you add the vfc as the predefined in R1?

   Thanks




BR

Maopeng




原始邮件



发件人： 
收件人：傅锦华10108953 
抄送人： 
日 期 ：2017年08月31日 03:34
主 题 ：Re: [onap-discuss] Re:  [SDC] Access sdc api failed.







Hi,


 


As described before SDC has two sets of API’s:


Internal:


 


Internal API’s use a header called user_id to check if the user is provisioned 
in the system and if his role allows him to execute this  API.


The internal API’s are provided to the SDC UI and should not be used by 
external components.


 


External:


 


This is a set of API’s provide to external component access to the SDC catalog 
this API’s are protected by basic authentication.


In order to use them you will first need to create a consumer in the system.


After one is created you will add the user and password to the request as a 
basic authentication header.


Please take a look here on how to generate the consumer and input him into the 
system: https://wiki.onap.org/display/DW/Consumer+creation


LINK to sdc external API’s:


https://wiki.onap.org/display/DW/SDC+API


 


Now in your case option 1 is missing the USER_ID header


And option two you did not create a consumer in the system.


 


Hope this helps


 


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of fu.jin...@zte.com.cn
 Sent: Wednesday, August 30, 2017 6:17 AM
 To: rene.rob...@orange.com
 Cc: onap-discuss@lists.onap.org
 Subject: [onap-discuss]  Re: [SDC] Access sdc api failed.


 

Hi Rene,

Can you give me more details about the rest call for sdc catalog, such as 
Header info, Auth info(user), 

I just use GET 
http://10.74.148.219:8080/sdc2/rest/v1/catalog/resources/fc006225-1364-43f2-a905-3ef08f211ea0,
 but  got the following msg:

status=403,resp_body={

  "requestError": {

"serviceException": {

  "messageId": "SVC4002",

  "text": "Error: Missing information.",

  "variables": []

}

  }

}

Is there something need to be added to the request header?

And I have another question, I have downloaded the 
SDC_Catalog_External_API_AID_v1.1.0.docx from wikipage of sdc, In the document,

I see the rest api for get list of resoures or services which is different from 
your sample, should I use your sample or ref the api document?

6.1.2 Request (GET)

https://{serverRoot}/sdc/v1/catalog/{assetType}

 

Thanks,

Jinhua

 



 


 


发件人： 



收件人：袁虎10090474 



抄送人： 



日 期 ：2017年08月29日 20:26



主 题 ：Re: [onap-discuss] [SDC] Access sdc api failed.




 


Hi,


 


Try that kind of uri to get a resource by its name :


 


GET {{your SDC server 
IP}}/8080/sdc2/rest/v1/catalog/resources/resourceName/vEPC/resourceVersion/1.1


 


Or this uri to get a resource by its unique id :


 


GET {{your SDC server 
IP}}/8080/sdc2/rest/v1/catalog/resources/b5c6cc2c-30c8-4212-8b42-75d2875e8f9f


 


I do not think that exist an uri to get all resources. Trying your uri, I have 
the same response than you.


 


Best regards.


 


 





 


René Robert 
 rene.rob...@orange.com


 


 


 


De : onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] De la part de yuan@zte.com.cn
 Envoyé : mardi 29 août 2017 10:32
 À : ml6...@intl.att.com
 Cc : onap-discuss@lists.onap.org
 Objet : [onap-discuss] [SDC] Access sdc api failed.


 

Hi Michael,

 

I'm trying to get the existing resources of sdc used the SDC Catalog External 
API.

But its returns some error message.

Do you know the reason for the failure? And how to resolve this problem?

 

Request Url (GET):

http://{sdc_ip}:8080/sdc/v1/catalog/resources 

 

Login User Id:

cs0008 or gv0001

 

Request Body:

N/A

 

Response:

{

"requestError": {

"policyException": {

"messageId": "POL5003",

"text": "Error: Not authorized to use the API.",

"variables": []

}

}

}

 


Thanks,


Yuan Hu




_
  Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez 
le signaler a l'expediteur et 

[onap-discuss] 答复: RE: 答复: RE: [SDC] Failes to parse ZTE csar

[zhang.maopeng1]

Hi tal




  It is an nullpoint error.  

  two ways:




  First,  change the file in the csar with attachment




  Second, I contribute  codes  to the JTOSCA to make the program stronger 
to avoid the null point error. 

   JIRA: https://jira.onap.org/browse/SDC-261

   gerrit: https://gerrit.onap.org/r/#/c/9375   please 
review it.






BR


Maopeng




原始邮件



发件人： 
收件人：张茂鹏10030173 
抄送人：    

日 期 ：2017年08月30日 14:51
主 题 ：RE: [onap-discuss] 答复: RE: [SDC] Failes to parse ZTE csar







Thank you very much


 


We try some of the CSAR and its work. Thank you for the quick response


 


We have problem currently only with one CSAR: vMME.csar


I am attaching the CSAR to the mail


 


We are checking if it’s a parser issue or CSAR/Tosca problem. I will like to 
get your inputs


 


The exception that we get is


 


java.lang.NullPointerException


at 
org.openecomp.sdc.toscaparser.api.utils.ValidateUtils.validateString(ValidateUtils.java:66)


at 
org.openecomp.sdc.toscaparser.api.DataEntity.validateDatatype(DataEntity.java:178)


at 
org.openecomp.sdc.toscaparser.api.DataEntity.validate(DataEntity.java:126)


at 
org.openecomp.sdc.toscaparser.api.DataEntity.validateDatatype(DataEntity.java:232)


at 
org.openecomp.sdc.toscaparser.api.Property.validate(Property.java:88)


at 
org.openecomp.sdc.toscaparser.api.NodeTemplate.validate(NodeTemplate.java:242)


at 
org.openecomp.sdc.toscaparser.api.TopologyTemplate._nodeTemplates(TopologyTemplate.java:130)


at 
org.openecomp.sdc.toscaparser.api.TopologyTemplate.(TopologyTemplate.java:69)


at 
org.openecomp.sdc.toscaparser.api.ToscaTemplate._topologyTemplate(ToscaTemplate.java:222)


at 
org.openecomp.sdc.toscaparser.api.ToscaTemplate.init(ToscaTemplate.java:191)


at 
org.openecomp.sdc.toscaparser.api.ToscaTemplate.(ToscaTemplate.java:97)


at 
org.openecomp.sdc.toscaparser.JToscaMetadataParse.testSPGWcsar(JToscaMetadataParse.java:32)


at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)


at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)


at java.lang.reflect.Method.invoke(Method.java:498)


at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)


at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)


at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)


at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)


at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)


at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)


at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)


at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)


at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)


at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)


at 
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)


at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)


at org.junit.runners.ParentRunner.run(ParentRunner.java:363)


at org.junit.runner.JUnitCore.run(JUnitCore.java:137)


at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)


at 
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)


at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)


at 
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)


 


 


 


 


 


 


Best regards


Tal Halfon


 


Development Manager @ Amdocs 


 


P. +972 54 2213763


 





 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhang.maope...@zte.com.cn
 Sent: Wednesday, August 30, 2017 5:38 AM
 To: Halfon Tal 
 Cc: Marina Vinokurov  Oren Kleks  
Tali Orenbach  onap-discuss@lists.onap.org
 Subject: [onap-discuss] 答复: RE: Failes to parse ZTE csar


 

hi tal

 

  

[onap-discuss] 答复: Re: [SDC] Access sdc api failed.

[zhang.maopeng1]

hi michael



   thank you.   

  

  In the wiki, 
https://wiki.onap.org/display/DW/SDC+API?preview=/10781738/10781741/SDC_Catalog_External_API_AID_v1.1.0.docx
 

  I think the apis in this docx are for the external, right?

 

 we also meet the problem, could you give us some example? I think 
maybe the auth meets something problem.


Response:{"requestError": {"policyException": { 
   "messageId": "POL5003","text": "Error: Not authorized to 
use the API.","variables": []}}}







BR

Maopeng




原始邮件



发件人： 
收件人： 袁虎10090474
抄送人： 
日 期 ：2017年08月29日 20:37
主 题 ：Re: [onap-discuss] [SDC] Access sdc api failed.





Sdc has two sets of apis one internal and one used by external components. In 
order to accses our internal api you will need to creat a consumer. I will 
creat an entry in the wiki describing it.

 Original Message 
From: rene.rob...@orange.com
Date: Tue, Aug 29, 2017, 15:26
To: yuan@zte.com.cn, "Lando,Michael" 
CC: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [SDC] Access sdc api failed.

Hi,

Try that kind of uri to get a resource by its name :

GET {{your SDC server 
IP}}/8080/sdc2/rest/v1/catalog/resources/resourceName/vEPC/resourceVersion/1.1

Or this uri to get a resource by its unique id :

GET {{your SDC server 
IP}}/8080/sdc2/rest/v1/catalog/resources/b5c6cc2c-30c8-4212-8b42-75d2875e8f9f

I do not think that exist an uri to get all resources. Trying your uri, I have 
the same response than you.

Best regards.


[Logo 
Orange]

René Robert
rene.rob...@orange.com



De : onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists..onap.org] De la part de yuan@zte.com.cn
Envoyé : mardi 29 août 2017 10:32
À : ml6...@intl.att.com
Cc : onap-discuss@lists.onap.org
Objet : [onap-discuss] [SDC] Access sdc api failed.


Hi Michael,



I'm trying to get the existing resources of sdc used the SDC Catalog External 
API.

But its returns some error message.

Do you know the reason for the failure? And how to resolve this problem?



Request Url (GET):

http://{sdc_ip}:8080/sdc/v1/catalog/resources



Login User Id:

cs0008 or gv0001



Request Body:

N/A



Response:

{

"requestError": {

"policyException": {

"messageId": "POL5003",

"text": "Error: Not authorized to use the API.",

"variables": []

}

}

}



Thanks,

Yuan Hu

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: Failes to parse ZTE csar

[zhang.maopeng1]

hi tal




  csar.meta  is used to identify the package type, etc.   The file can 
be ignored for  the SDC parser.

  

Thanks

Maopeng




原始邮件



发件人： 
收件人：  张茂鹏10030173赵化冰10201488
抄送人：   
日 期 ：2017年08月29日 15:48
主 题 ：RE: Failes to parse ZTE csar







Hi


 


We are trying to parse the CSAR supply by ZTE for the VoLTE usecase


The CSAR are located @ 
https://wiki.onap.org/display/DW/SDC+2017-07-31+Meeting+notes


 


We are using a valid tosca parser


 


We are getting this exception for all the CSAR there, All the CSAR have a file 
call csar.meta and the parses can parse it because it does not contain valid 
YAML content.


I need help to understand what is this file and why do I need it on the root. 
If needed I need this file to be fixed


For exmple SPGW.csar


 


org.openecomp.sdc.toscaparser.api.common.JToscaException: The file "csar.meta" 
in the CSAR 
"C:\onap\workspace\tosca\jtosca\target\test-classes\csars\SPGW.csar" does not 
contain valid YAML content


 


at 
org.openecomp.sdc.toscaparser.api..prereq.CSAR._parseAndValidateMetaProperties(CSAR.java:167)


at 
org.openecomp.sdc.toscaparser.api..prereq.CSAR.validate(CSAR.java:93)


at 
org.openecomp.sdc.toscaparser.api..ToscaTemplate._getPath(ToscaTemplate.java:508)


at 
org.openecomp.sdc.toscaparser.api..ToscaTemplate.init(ToscaTemplate.java:140)


at 
org.openecomp.sdc.toscaparser.api..ToscaTemplate.(ToscaTemplate.java:97)


at 
org.openecomp.sdc.toscaparser.JToscaMetadataParse.testSPGWcsar(JToscaMetadataParse.java:32)


at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)


at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)


at java.lang.reflect.Method.invoke(Method.java:498)


at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)


at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)


at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)


at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)


at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)


at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)


at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)


at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)


at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)


at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)


at 
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)


at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)


at org.junit.runners.ParentRunner.run(ParentRunner.java:363)


at org.junit.runner.JUnitCore.run(JUnitCore.java:137)


at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)


at 
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)


at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)


at 
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)


 


Disconnected from the target VM, address: '127.0.0.1:57744', transport: 'socket'


 


 


 


Best regards


Tal Halfon


 


Development Manager @ Amdocs 


 


P. +972 54 2213763


 






This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,you may review at 
https://www.amdocs.com/about/email-disclaimer___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: SDC weekly meeting notes 28/8

[zhang.maopeng1]

Hi







   Two issuses feedback:


   1.can the CSAR structure be aligned according to the request to have the 
service template yaml and mf in the root level (owner Meopeng)


   [Maopeng]


  This issue is more related to the VNF vendors. The 
below is the infomation I get.


   In the wiki page CSAR structure, it combines the 
ETSI or OASIS option1 and option2.  it is almost a new one and has more 
duplicated contents.


Our aim is to support both option1 and option2 in 
SDC,  and then it is an temporary solution because of the develop time just for 
R1.


ZTE will support to add the files in the root level 
for the VoLTE case in R1 as an temporary solution






I get the infomation from Victor.gao thatHuawei 
will also  support to add the files in the root level for the VoLTE case in R1.






   2.VF-C team to provide the list of artifacts that would be included in 
the onboarded VNF and used by VF-C (owner Meoperg)


  [Maopeng]  


  1.  In R1, because SDC does not support the image 
storage,   VF-C(NFVO) has no artifacts to deal in  the VNF package. In the R2, 
VFC will cooperate with SDC to implicate the VNF image upload function.


  2.   In R1, VF-C(NFVO) will use plan folfder in 
artifacts  to store the workflow files for the NS packages


  3.  In R1, the VNF vendoer has requirements to  add 
somefolders in artifacts, which is related to the VNF vendors. 


  4.  In R2+, VF-C(GVNFM) will have the requirement for 
the artifacts in VNF packages






BR


Maopeng



原始邮件



发件人： 
收件人： 
抄送人： 
日 期 ：2017年08月29日 05:46
主 题 ：[onap-discuss] SDC weekly meeting notes 28/8





Hi,
Attached is a link to our meeting notes:
https://wiki.onap.org/plugins/servlet/mobile?contentId=1015829#content/view/15990847
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: [modeling][sdc][so][vfc][vnfsdk]ONAP namingconvention options

[zhang.maopeng1]

Hi




 For NFV domain, agree with option 2.


 For the whole onap namespace, agree with option3




Thanks

Maopeng








原始邮件



发件人： 
收件人： 
抄送人： 
日 期 ：2017年08月28日 09:38
主 题 ：[onap-discuss] [modeling][sdc][so][vfc][vnfsdk]ONAP namingconvention 
options







I suggest we consider either option 2 or option 3.


 


Thanks,


Lingli





Hello all We hadn’t have the time to discuss this yesterday teleconf based on 
the request from SDC,so I posted here to get more comments in the list 
regarding to ONAP Naming convention.OPENECOMP historically follow 1st option, 
and OPENO follow 2nd option.●   1st: Openecomp: org.openecomp.*●   2nd: 
OPEN-O: tosca.nodes.nfv.*●   3rd :  tosca.nodes.onap.●   4th:●   
standard part is based on TOSCA simple/TOSCA NFV●   Extension could be onap 
Thank you all for your comments. Best regards, DENG Hui___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: SDC weekly meeting notes 28/8

[zhang.maopeng1]

hi

 Thanks for your clarification.  A few comments below.




Thanks

Maopeng

原始邮件






发件人： 
收件人：  张茂鹏10030173赵化冰10201488
抄送人：    

日 期 ：2017年08月29日 15:48
主 题 ：RE: SDC weekly meeting notes 28/8






Hi SDC community

Action items from the meeting 

1) Can the SDC support nested artifacts in imported CSAR?
Yes, We are supporting folders in the /Artifacts

 [Maopeng]  Have the folders in the artifacts  some limits?  Can the VNF 
vendor add some folders that they wants?


2) provide VNFSDK team with information and code location about the current SDC 
CSAR validations (owner Tal H.)
We need two things if we want to meet the R1 timeline
1) Copy the MainServiceTemplate.yaml from the / Definitions to the ROOT 
CSAR and change is name to  MainServiceTemplate.yaml
2) Copy the data from the Tosca.meta into the MainServiceTemplate.mf
MainServiceTemplate.mf sample:

metadata:
vnf_product_name: VNF_Name
vnf_provider_id: ZTE
vnf_package_version: 1.0
vnf_release_data_time: 2017.01.01T10:00+03:00

source: MainServiceTemplate.yaml
source: Definitions/GlobalSubstitutionTypesServiceTemplate.yaml
source: Artifacts/install.sh
source: Artifacts/create_stack.sh

I have attach a sample of the MainServiceTemplate.mf to the mail


  [Maopeng] Tosca.meta content is different from the  
MainServiceTemplate.mf. For VNF vendors, it is not a copy from Tosca.meta.




In the wiki page CSAR structure, it combines the 
ETSI or OASIS option1 and option2.  it is almost a new one and has more 
duplicated contents.

If the aim is to support both option1 and option2 
in SDC, we should consider the issue and avoid to make it confused to the VNF 
vendor.

If it is an temporary solution because of the 
develop time just for R1, we should note it.



   
Best regards
Tal Halfon

Development Manager @ Amdocs  

P. +972 54 2213763

 

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lando,Michael
Sent: Tuesday, August 29, 2017 12:46 AM
To: onap-discuss@lists.onap.org
Cc: Franko, Dudi 
Subject: [onap-discuss] SDC weekly meeting notes 28/8

Hi,
Attached is a link to our meeting notes:
https://wiki.onap.org/plugins/servlet/mobile?contentId=1015829#content/view/15990847
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [SDC][VFC] VNFD and NSD Discussion Meeting Invitation

[zhang.maopeng1]

Hi, 


   

   This the meeting link as we plan to arrange.




Topic:   VNFD and NSD Discussion Meeting

Time: Sep 1, 2017 9:00 PM Beijing, Shanghai



Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/648493837




Or iPhone one-tap :

US: +14086380968,,648493837#  or +16468769923,,648493837# 

Or Telephone：

Dial(for higher quality, dial a number based on your current location)：

US: +1 408 638 0968  or +1 646 876 9923 

Meeting ID: 648 493 837

International numbers available: 
https://zoom.us/zoomconference?m=1O70GAs-yNBBPJICgPTuoy42OL0_AxkM







BR


maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: [SDC][VFC]about the VoLTE VNF Descriptor gaps slide

[zhang.maopeng1]

could Michael add a slot for these issues in the sdc meeting?



thanks








 

 原始邮件 
 
 
 
 
 
 
 
 
 
 发件人：张茂鹏10030173 
 
 
 
 收件人：ml636r@att.comds2...@att.com 
 
 
 
 抄送：ml636rds200phalfont@amdocs.comonap-disc...@lists.onap.org 
 
 
 
 日期：2017-08-28 09:43:35 
 
 
 
 主题：答复: [onap-discuss][SDC][VFC]about the VoLTE VNF Descriptor gaps slide 
 
 
 
 
 
 

 
 
 
 hi


 
 


 
What's the issues going-on?   Could Michael or David give some feed back?

 
There are not more than three weeks for us.

 
Those issues really effect the code develop for VFC integration with SDC. 

 
Hope we can make it clear ASAP.

 
Thanks.

 
 


 
 Best Regards

 
 Maopeng

 
 
 
 


 
 
 
 

 
 
 
 
 
 
 
 
 发件人： 
 张茂鹏10030173 
 
 
 
 收件人： 
  
  
 
 
 
 抄送人： 
  
  
 
 
 
 日 期 ： 
 2017年08月24日 00:03 
 
 
 
 主 题 ： 
 答复: [onap-discuss][SDC][VFC]about the VoLTE VNF Descriptor gaps slide 
 
 
 
 
 



 
 
 
 
 
 
 
 
 hi David and Michael,


 
 


 
 The attachment is the vvg and vfw package.The URL is the slide, please 
pay attion to the P7-P9

 
  
https://wiki.onap.org/download/attachments/11930732/ONAP_SDC%26VFC_Integration_V0.2.pptx?version=1=1502820052000=v2
 

 
 

 
 The NSD and package document:   

 
 
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599839/NSD%20Specification.pdf
 

 
 
   
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599838/NS%20Package%20Specification.pdf

 
 
 
 
 
VoLTE VNF Descriptor gaps that the tal provided is in the attachement as 
well.


 
Please review the NSD and package documents, and give the reply about the 
TOSCA issues.

 
 


 
 Best Regards

 
 Maopeng

 
 


 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 发件人： 
 张茂鹏10030173 
 
 
 
 收件人： 
  
  
  
 
 
 
 抄送人： 
  
 
 
 
 日 期 ： 
 2017年08月23日 10:28 
 
 
 
 主 题 ： 
 [onap-discuss][SDC][VFC]about the VoLTE VNF Descriptor gaps slide 
 
 
 
 
 



 
 
 
 
 
 
 Hi,

 
  The document is mainly about the VNF package issue, but it also include 
the network service(P3, some ns node) as well.

 
  If it is only for the VNF, please correct me. thanks.

 
 


 
   P3,  The VNF node is lost.   I have uploaded the network service 
definition for R1 on the wiki, please review it.

 
 
   
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599839/NSD%20Specification.pdf
 

 
 
   
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599838/NS%20Package%20Specification.pdf

 
  


 
  P4 , For VFC side, agree to move the type definitions into one yaml file. 
 

 
  P6,   The VoLTE csar’s does not contain mainServiceTemplate.yaml

 
  There is only one service template which its name is 
openovnf_csarName.yaml

 
  Vendor need to change openovnf_csarName.yaml to 
mainServiceTemplate.yaml

 
 [Maopeng] the service template can be configured, not an fixed 
file name, according to the tosca standard.

 
   It is configured in the 
VoLTE.csar\TOSCA-Metadata\TOSCA.meta

 
   Entry-Definitions: Definitions/ns2__VoLTE.yaml

 
   This way I think it is also supported by the vvg 
csar that the David  provided. 

 
 


 
   There is no support with nested service templates 

 
No nested support

 
   [Maopeng] R1, no nested service templetes in the NS.

 
 


 
 P7 Is the issue same with P4? but the type definition file name is not 
same. 

 
 P8  I think we need some inputs in the VoLTE case. I think now the SDC 
supports the function.

 
 P9  About  the import,  is it possible tha both list  and Map could be supported in VNF packages?

 
 P10 About the Substitution, is it possible that the OASIS standerd 
substitution suppported as well?

 
 


 
 Best Regards

 
 Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: [SDC][VFC]about the VoLTE VNF Descriptor gaps slide

[zhang.maopeng1]

hi





   What's the issues going-on?   Could Michael or David give some feed back?

   There are not more than three weeks for us.

   Those issues really effect the code develop for VFC integration with SDC. 

   Hope we can make it clear ASAP.

   Thanks.




Best Regards

Maopeng



原始邮件



发件人：张茂鹏10030173
收件人：  
抄送人：  
日 期 ：2017年08月24日 00:03
主 题 ：答复: [onap-discuss][SDC][VFC]about the VoLTE VNF Descriptor gaps slide








hi David and Michael,





The attachment is the vvg and vfw package.The URL is the slide, please 
pay attion to the P7-P9

 
https://wiki.onap.org/download/attachments/11930732/ONAP_SDC%26VFC_Integration_V0.2.pptx?version=1=1502820052000=v2
 



The NSD and package document:   


https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599839/NSD%20Specification.pdf
 


   
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599838/NS%20Package%20Specification.pdf



VoLTE VNF Descriptor gaps that the tal provided is in the attachement as 
well.


   Please review the NSD and package documents, and give the reply about the 
TOSCA issues.




Best Regards

Maopeng













发件人：张茂鹏10030173
收件人：   
抄送人： 
日 期 ：2017年08月23日 10:28
主 题 ：[onap-discuss][SDC][VFC]about the VoLTE VNF Descriptor gaps slide







Hi,

 The document is mainly about the VNF package issue, but it also include 
the network service(P3, some ns node) as well.

 If it is only for the VNF, please correct me. thanks.




  P3,  The VNF node is lost.   I have uploaded the network service 
definition for R1 on the wiki, please review it.


   
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599839/NSD%20Specification.pdf
 


   
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599838/NS%20Package%20Specification.pdf

 


 P4 , For VFC side, agree to move the type definitions into one yaml file.  

 P6,   The VoLTE csar’s does not contain mainServiceTemplate.yaml

 There is only one service template which its name is 
openovnf_csarName.yaml

 Vendor need to change openovnf_csarName.yaml to 
mainServiceTemplate.yaml

[Maopeng] the service template can be configured, not an fixed file 
name, according to the tosca standard.

  It is configured in the 
VoLTE.csar\TOSCA-Metadata\TOSCA.meta

  Entry-Definitions: Definitions/ns2__VoLTE.yaml

  This way I think it is also supported by the vvg csar 
that the David  provided. 




  There is no support with nested service templates 

   No nested support

  [Maopeng] R1, no nested service templetes in the NS.




P7 Is the issue same with P4? but the type definition file name is not 
same. 

P8  I think we need some inputs in the VoLTE case. I think now the SDC 
supports the function.

P9  About  the import,  is it possible tha both list  and Map 
could be supported in VNF packages?

P10 About the Substitution, is it possible that the OASIS standerd 
substitution suppported as well?




Best Regards

Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: Please review A schema changes for VFC

[zhang.maopeng1]

hi victor





 attachment is not in the mail. please sent it again.




Thanks

Maopeng








原始邮件



发件人： 
收件人：  
抄送人： 
日 期 ：2017年08月23日 17:56
主 题 ：[onap-discuss] Please review A schema changes for VFC







Hi Jimmy, Yangyan,


 


I’d like ask a timeslot in A weekly meeting to review the 
schema changes for VFC.


 


Attachment is the draft schema for VFC.


 


Please let me know your suggestion.


 


Thanks in advance.


 


BR


Victor


 


*
 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使


用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通


知发件人并删除本邮件！


*
 
 
*


This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person 


or entity whose address is listed above. Any use of the information contained 
herein in any way (including, but not


limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) 


is prohibited. If you receive this e-mail in error, please notify the sender by 
phone or email immediately and delete it!
 
*___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [SDC][VFC]about the VoLTE VNF Descriptor gaps slide

[zhang.maopeng1]

Hi,

 The document is mainly about the VNF package issue, but it also include 
the network service(P3, some ns node) as well.

 If it is only for the VNF, please correct me. thanks.




  P3,  The VNF node is lost.   I have uploaded the network service 
definition for R1 on the wiki, please review it.


   
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599839/NSD%20Specification.pdf
 


   
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599838/NS%20Package%20Specification.pdf

 


 P4 , For VFC side, agree to move the type definitions into one yaml file.  

 P6,   The VoLTE csar’s does not contain mainServiceTemplate.yaml

 There is only one service template which its name is 
openovnf_csarName.yaml

 Vendor need to change openovnf_csarName.yaml to 
mainServiceTemplate.yaml

[Maopeng] the service template can be configured, not an fixed file 
name, according to the tosca standard.

  It is configured in the 
VoLTE.csar\TOSCA-Metadata\TOSCA.meta

  Entry-Definitions: Definitions/ns2__VoLTE.yaml

  This way I think it is also supported by the vvg csar 
that the David  provided. 




  There is no support with nested service templates 

   No nested support

  [Maopeng] R1, no nested service templetes in the NS.




P7 Is the issue same with P4? but the type definition file name is not 
same. 

P8  I think we need some inputs in the VoLTE case. I think now the SDC 
supports the function.

P9  About  the import,  is it possible tha both list  and Map 
could be supported in VNF packages?

P10 About the Substitution, is it possible that the OASIS standerd 
substitution suppported as well?




Best Regards

Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: [SDC][VFC]SDC meeting notes

[zhang.maopeng1]

Hi Michael and David,

 

  About thequestion2,, I have uploaded the definition for 
R1 on the wiki, please review it.


   
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599839/NSD%20Specification.pdf
 

   
https://wiki.onap.org/display/DW/Modeling+specification+for+ONAP+Release+1?preview=/13599755/13599838/NS%20Package%20Specification.pdf

   

  Could you feed back the TOSCA specific issues(P7-P9) and 
the NSD/ NSpackage issues? Becase the M3 deadline is coming, please confirm 
these issues. 

   Thanks.




Best Regards

Maopeng




原始邮件



发件人：张茂鹏10030173
收件人：  
抄送人： 
日 期 ：2017年08月22日 00:57
主 题 ：答复: RE: [onap-discuss] [SDC][VFC]SDC meeting notes







Hi,




 Thanks michael and david for the VL demonstration in the meeting. 




  Because the time limit, TOSCA specific issues(P7-P9) are not discussed.

 If possible, please give the comments back in mail or arrange another 
meeting.

 

There are the two issues remained. If I am wrong, please correct me.

1. VNF Package & VNFD , which I have sent a solution for VoLTE case in R1 
in the discuss list.  Please confirm it. 

2. We have discussed the NSD( using TOSCA NFV profile and import openo 
node), but we needs a document to define the NSD as interface for R1.

 I do the help to write the document.   
Affact project:  [SDC,VFC] 




Best Regards

Maopeng













发件人： 
收件人：张茂鹏10030173
抄送人： 
日 期 ：2017年08月17日 20:59
主 题 ：RE: [onap-discuss] [SDC][VFC]SDC meeting notes







We will do it as part of our weekly meeting.


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, August 17, 2017 2:57 PM
 To: Lando,Michael 
 Cc: onap-discuss@lists.onap.org
 Subject: 答复: [onap-discuss] [SDC][VFC]SDC meeting notes


 

hi 

 

   thanks Michael.

   For the VL in the VFC slide P4 issuse, the SDC team will arrange a meeting 
to do a demonstration about the SDC design and discuss the TOSCA specific 
issues(P7-P9) next week.

   Is it arranged in the SDC week meeting or a new meeting?

 

Best Regards

Maopeng



原始邮件



发件人： 



收件人： 



日 期 ：2017年08月16日 02:20



主 题 ：[onap-discuss] SDC meeting notes




 


Hi,


Attached below Is the link to today’s meeting notes:


https://wiki.onap.org/display/DW/SDC+2017-08-15+Meeting+notes


 


Highlights:


· VFC and SDC integration discussion


·  presentation from VNF-SDK regarding their suggestion for providing 
meta data to the SO and VNC


· presentation by Amdocs regarding gaps identified as part of the work 
to support the importing of Tosca into SDC


To progress the open issues we will be holding another meeting on 16/8 9 -11 EST


 


 


 


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: [SDC][VFC]SDC meeting notes

[zhang.maopeng1]

Hi,




 Thanks michael and david for the VL demonstration in the meeting. 




  Because the time limit, TOSCA specific issues(P7-P9) are not discussed.

 If possible, please give the comments back in mail or arrange another 
meeting.

 

There are the two issues remained. If I am wrong, please correct me.

1. VNF Package & VNFD , which I have sent a solution for VoLTE case in R1 
in the discuss list.  Please confirm it. 

2. We have discussed the NSD( using TOSCA NFV profile and import openo 
node), but we needs a document to define the NSD as interface for R1.

 I do the help to write the document.   
Affact project:  [SDC,VFC] 



Best Regards

Maopeng




原始邮件



发件人： 
收件人：张茂鹏10030173
抄送人： 
日 期 ：2017年08月17日 20:59
主 题 ：RE: [onap-discuss] [SDC][VFC]SDC meeting notes







We will do it as part of our weekly meeting.


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, August 17, 2017 2:57 PM
 To: Lando,Michael 
 Cc: onap-discuss@lists.onap.org
 Subject: 答复: [onap-discuss] [SDC][VFC]SDC meeting notes


 

hi 

 

   thanks Michael.

   For the VL in the VFC slide P4 issuse, the SDC team will arrange a meeting 
to do a demonstration about the SDC design and discuss the TOSCA specific 
issues(P7-P9) next week.

   Is it arranged in the SDC week meeting or a new meeting?

 

Best Regards

Maopeng



原始邮件



发件人： 



收件人： 



日 期 ：2017年08月16日 02:20



主 题 ：[onap-discuss] SDC meeting notes




 


Hi,


Attached below Is the link to today’s meeting notes:


https://wiki.onap.org/display/DW/SDC+2017-08-15+Meeting+notes


 


Highlights:


· VFC and SDC integration discussion


·  presentation from VNF-SDK regarding their suggestion for providing 
meta data to the SO and VNC


· presentation by Amdocs regarding gaps identified as part of the work 
to support the importing of Tosca into SDC


To progress the open issues we will be holding another meeting on 16/8 9 -11 EST


 


 


 


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [sdc][vfc] SDC questions from VF-C

[zhang.maopeng1]

Hi michael




Thanks for sharing the packages.  

Now in the packages you shared, the VF and service are both in the one 
package.  

In R1, for the VoLTE case, the VF and service are indepandent packages.  
could you provide the VF and service packages seperated?

 If the service package can include VNFs and extVL, it can make greate help 
to VFC team.

  

Thanks

Maopeng








原始邮件



发件人： 
收件人：  张茂鹏10030173 
 
抄送人： 
日 期 ：2017年08月14日 14:02
主 题 ：RE: 答复: 答复: Re: 答复: [onap-discuss] 答复： 答复：RE: RE: RE: RE: [sdc][vfc] SDC 
questions from VF-C







Hi,


This is an example of the csar currently created as part of the use case 
vlw/vdns.


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office:  +972 (3) 5451487


Mobile:  +972 (54) 7833603


e-mail: ml6...@intl.att.com


 



 



From: SHADMI, DAVID 
 Sent: Monday, August 14, 2017 7:46 AM
 To: 杨艳  zhang.maope...@zte.com.cn Rozin, Eden 
 Lando,Michael   'Lingli Deng' 

 Cc: onap-discuss@lists.onap.org
 Subject: Re: 答复: 答复: Re: 答复: [onap-discuss] 答复： 答复：RE: RE: RE: RE: [sdc][vfc] 
SDC questions from VF-C




 


Hi Michael,



 



Can you please share the latest samples we have with the VF-C team?



 



Yan - the samples Michael can share are not final, and some you should expect 
some changes.



 



Thanks,



David  



 




Sent via the Samsung Galaxy S7 edge, an AT 4G LTE smartphone




 



 



 Original message 



From: 杨艳 



Date: 8/13/17 11:19 PM (GMT-06:00)



To: "SHADMI, DAVID" , zhang.maope...@zte.com.cn, "ROZIN, EDEN" 
, "LANDO, MICHAEL" , 'Lingli Deng' 




Cc: onap-discuss@lists.onap.org 



Subject: 答复: 答复: Re: 答复: [onap-discuss] 答复： 答复：RE: RE: RE: RE: [sdc][vfc] SDC 
questions from VF-C



 



Hi David,


 


Thanks for your  arrangement. We want to know more details about  the service 
and VNF package  format exported from SDC, can you share an example of service 
and  VNF CSAR Package that SDC created before this meeting?


 


Best Regards,


Yan


 



发件人: SHADMI, DAVID [mailto:ds2...@att.com] 
 发送时间: 2017年8月14日 9:59
 收件人: 杨艳 zhang.maope...@zte.com.cn ROZIN, EDEN LANDO, MICHAEL 'Lingli Deng'
 抄送: onap-discuss@lists.onap.org
 主题: Re: 答复: Re: 答复: [onap-discuss] 答复： 答复：RE: RE: RE: RE: [sdc][vfc] SDC 
questions from VF-C




 


Hi Yan,



 



Sorry for missing your meeting. I was out on Friday and Micahel who is located 
in Israel is working Sun-Thu.



 



The first 30 min are reserved for R1 outstanding items.



@Michael, please add the VF-C to the agenda (after the workflow designer item). 



 



Thanks,



David



 




Sent via the Samsung Galaxy S7 edge, an AT 4G LTE smartphone




 



 



 Original message 



From: 杨艳 



Date: 8/13/17 8:40 PM (GMT-06:00)



To: 'yangyanyj' , zhang.maope...@zte.com.cn, 
"SHADMI, DAVID" , "ROZIN, EDEN" , "LANDO, 
MICHAEL" ,  'Lingli Deng' 



Cc: onap-discuss@lists.onap.org 



Subject: 答复: Re: 答复: [onap-discuss] 答复： 答复：RE: RE: RE: RE: [sdc][vfc] SDC 
questions from VF-C



 


Hi David, Micheal and Maopeng,

Nobody from SDC team attended the discussion on last Friday, Maybe I sent the 
invitation too late so that you missed the invitation.

We want to utilize the SDC weekly meeting to accomplish this discussion. It 
would be good, if you can reserve a slot for this discussion in addition to 
other topics you have already arranged.


 

Best Regards,

Yan

-约会原件-
 发件人: yangyanyj [mailto:yangya...@chinamobile.com] 代表 yangyanyj
 发送时间: 2017年8月11日 13:43
 收件人: zhang.maope...@zte.com.cn ds2...@att..com er4...@intl.att.com 
ml6...@att.com
 抄送: onap-discuss@lists.onap.org
 主题: 已更新:Re: 答复: [onap-discuss] 答复： 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions 
from VF-C
 时间: 2017年8月11日星期五 21:00-22:00(UTC+08:00) 北京，重庆，香港特别行政区，乌鲁木齐。
 地点: 

Hi david, micheal and maopeng,

Thanks Mao Peng summarize the above issues. I think a tel conf will be more 
efficient, so VF-C  team invites SDC team  to participate in tonight's 
discussion, we hope the SDC team  can help us to clarify the remaining issues.


Topic: VF-C and SDC Discussion
 Time: Aug 11, 2017 9:00 PM Beijing, Shanghai
 
 Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/9117271979
 
 Or iPhone one-tap (US Toll):  +16465588656,,9117271979# or 
+14086380968,,9117271979#
 
 Or Telephone:
 Dial: 

[onap-discuss] 答复: Re: 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C

[zhang.maopeng1]

Hi Micheal 




 Thanks， find them definition in the 
service-vfw.csar\Definitions\nodes.yml. This issue can be closed.

 We can upload it to the WIKI.  Those dedfinition is important to VFC, if 
it is changed in R1, please info VFC team.  

  

Thanks

 Maopeng




原始邮件



发件人： 
收件人：张茂鹏10030173
抄送人：   
孟照星10024238  

日 期 ：2017年08月14日 14:31
主 题 ：Re: 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C





All the info is located as normativea and heats. Open the zip and the info you 
request is there.

If you dont find it ping me and i will send it to you i simply dont have accses 
right now to send you the info directly

 Original Message 
From: zhang.maope...@zte.com.cn
Date: Mon, Aug 14, 2017, 09:25
To: "Lando,Michael" 
CC: "SHADMI, DAVID" , yangya...@chinamobile.com, 
denglin...@chinamobile.com, meng.zhaoxi...@zte.com.cn, 
onap-discuss@lists.onap.org, "Rozin, Eden" 
Subject: 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C


hi michael



Yes,  normative node type is provided base on the TOSCA simple 
profile:tosca_simple_yaml_1_0_0.

   But node type include not only normative, but also SDC ECOMP node types,  
such as Service,VNF, extVL,extCP, etc , which is listed  in the document 
"SDC_TOSCA_AID_1710 v16.docx" chapter 4.6. but no definition.

   Those node type definitions are important to VFC.   Could you provide those 
node definitions for R1?


Thanks

Maopeng

原始邮件
发件人： 
收件人： 张茂鹏10030173
抄送人：  孟照星10024238 
 
日 期 ：2017年08月14日 14:08
主 题 ：RE: RE: RE: [sdc][vfc] SDC questions from VF-C

David:
Our normative can be found here:
https://wiki.onap.org/pages/viewpage.action?pageId=10784241



BR,

Michael Lando
Opensource & Frontend Team Lead, SDC
AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com


From: SHADMI, DAVID
Sent: Thursday, August 10, 2017 7:04 AM
To: zhang.maope...@zte.com.cn Lando,Michael 
Cc: yangya...@chinamobile.com denglin...@chinamobile.com 
meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org Rozin, Eden 

Subject: RE: RE: RE: [sdc][vfc] SDC questions from VF-C

Hello,

#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF packages 
in R1. Also, SDC is planning to add Open-O TOSCA types.
#3 – @Michael – Could you please make sure we the node type definition file(s) 
for VF and Service exist in the wiki. @Maopeng  - could you please elaborate 
more on the node type you would like to add.
#5 – Please see enclosed email.


Thanks,
David


From: zhang.maope...@zte.com.cn 
[mailto:zhang.maope...@zte.com.cn]
Sent: Wednesday, August 09, 2017 9:15 PM
To: LANDO, MICHAEL > SHADMI, 
DAVID >
Cc: yangya...@chinamobile.com 
denglin...@chinamobile.com 
meng.zhaoxi...@zte.com.cn 
onap-discuss@lists.onap.org ROZIN, EDEN 
>
Subject: 答复: RE: RE: [sdc][vfc] SDC questions from VF-C


hi micheal & david



 Thanks micheal

  Now many advices need David to answer. If the email can reply, it 
will be OK.  Possible, meeting & email may be more effective way.

 The service package and vnf package CSAR in the SDC catalog, please 
share them. Thanks

  About the parser, VFC written in python can not use the java lib  
directly.

  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1

  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
 If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?



Best Regards

Maopeng
原始邮件
发件人： >
收件人：张茂鹏10030173
抄送人： > 
>  

[onap-discuss] 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C

[zhang.maopeng1]

hi michael

   

Yes,  normative node type is provided base on the TOSCA simple 
profile:tosca_simple_yaml_1_0_0.

   But node type include not only normative, but also SDC ECOMP node types,  
such as Service,VNF, extVL,extCP, etc , which is listed  in the document 
"SDC_TOSCA_AID_1710 v16.docx" chapter 4.6. but no definition.

   Those node type definitions are important to VFC.   Could you provide those 
node definitions for R1?




Thanks

Maopeng




原始邮件



发件人： 
收件人： 张茂鹏10030173
抄送人：  孟照星10024238 
 
日 期 ：2017年08月14日 14:08
主 题 ：RE: RE: RE: [sdc][vfc] SDC questions from VF-C







David:


Our normative can be found here:


https://wiki.onap.org/pages/viewpage.action?pageId=10784241


 


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 



 



From: SHADMI, DAVID 
 Sent: Thursday, August 10, 2017 7:04 AM
 To: zhang.maope...@zte.com.cn Lando,Michael 
 Cc: yangya...@chinamobile.com denglin...@chinamobile.com 
meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org Rozin, Eden 

 Subject: RE: RE: RE: [sdc][vfc] SDC questions from VF-C




 


Hello,


 


#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF packages 
in R1. Also, SDC is planning to add Open-O TOSCA types.


#3 – @Michael – Could you please make sure we the node type definition file(s) 
for VF and Service exist in the wiki. @Maopeng  - could you please elaborate 
more on the node type you would like to add.


#5 – Please see enclosed email.


 


 


Thanks,


David


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Wednesday, August 09, 2017 9:15 PM
 To: LANDO, MICHAEL  SHADMI, DAVID 
 Cc: yangya...@chinamobile.com denglin...@chinamobile.com 
meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org ROZIN, EDEN 

 Subject: 答复: RE: RE: [sdc][vfc] SDC questions from VF-C


 

hi micheal & david

 

 Thanks micheal

  Now many advices need David to answer. If the email can reply, it 
will be OK.  Possible, meeting & email may be more effective way.

 The service package and vnf package CSAR in the SDC catalog, please 
share them. Thanks

  About the parser, VFC written in python can not use the java lib  
directly.

  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1

  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
  If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?



Best Regards

Maopeng


原始邮件



发件人： 



收件人：张茂鹏10030173



抄送人：    
孟照星10024238  




日 期 ：2017年08月10日 03:27



主 题 ：RE: RE: [sdc][vfc] SDC questions from VF-C




 


 


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Wednesday, August 09, 2017 7:09 PM
 To: Lando,Michael 
 Cc: yangya...@chinamobile.com SHADMI, DAVID  
denglin...@chinamobile.com meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org
 Subject: 答复: RE: [sdc][vfc] SDC questions from VF-C


 

Hi Michael

 

thanks for your reply. 

 

1. For the api document,  I really need more time to read it. For R1, the 
VFC team main funciton is to get the distributed Service CSAR and VF CSAR from 
SDC catalog. thanks.

2. About the VNF package, thanks for sharing the vFW/vDNS CSAR. Is the 
Tosca onboarding function release on R1?  which tosca profile does the SDC 
follows in R1? does the VNF vendor need to follow it? thanks.  [Michael: David  
 please advise]

3. About the service package, please provide the CSAR example for R1. In 
the wiki page, SDC_TOSCA_AID_1710 document has no nodes definitions, such as 
service, VF, VL,etc. could you provide the nodes definition for R1 in the wiki? 
 could SDC support adding   new node type? such as VF, could we add a new VFXX 
extending from VF via SDC GUI, and 

[onap-discuss] 答复: 答复： 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C

[zhang.maopeng1]

Hi david, micheal




   Email Summary is as following, please check it.   If I am wrong, please 
correct me. Please PTL(yangyan,micheal) arrange a virtual meeting to discuss 
these issues,  thanks.




   1.  Now the things confirmed:

   1.1. In ONAP R1, the SDC will add the openo tosca type. The types’ 
namespace would follow OpenECOMP convention

   Note: the final node type definition still need to be cleared.

   1.2. controllerinfo in the service level will be supported via new 
parameter servicetype and serviceRole.




2.  There are still following questoins needed to be clear from SDC side.

 2.1.  VF level need the vnfminfo, for VFC suggests add a new parameter 
for VF.  what's the advices from SDC team?

  vnfminfo is used by vf-c to identify which vendor vnfm driver 
to choose. The vnfminfo is a string, such as gvnfm,juju,zte,HUAWEI,etc. hope 
the description can clear the vnfminfo parameter. 

 2.2. Whether to support ELAN VL, which can be shared among VNFs.


  [Maopeng ] now the SDC supports VL, but it is automatically 
produced.  Now I can design the Eline type VL, but for the VoLTE case , we need 
   multiple VNFs share one VL.


  what's the automatic rule of VL creating? How to 
design it? could you show with us. thanks.   


  [Michael: David can you respond?]


 2.3. About Service /VNF package


 2.3.1  In the wiki page, SDC_TOSCA_AID_1710 document has no 
nodes definitions, please provide it in the wiki.


   [David] @Michael – Could you please make sure we the 
node type definition file(s) for VF and Service exist in the wiki?


 2.3.2  We want to know the VNF CSAR package format exported 
from SDC, can you give us an example, we want to confirm whether the package 
has some format restrictions.


   [Maopeng ] In the R1,  VNFSDK bundles a VNF package, and 
import to the SDC. VFC get the VNF package from theSDC catalog. 
   


   Is theVNF package defined in the VNFSDK or SDC for R1? 
What's the VNF package format for VFC in R1?
 


[Michael] since we are now still developing the 
Tosca onboarding I cannot provide you the exact output. I can   share an 
example of the CSAR we currently create  for the vFW/vDNS use case.   


[Maopeng] The service package and vnf package 
CSAR in the SDC catalog, please share them. Thanks


This is really a block issuse for VFC if the 
service and VF package format can not be provided specifically in time.






2.4. About the parser, VFC written in python can not use the java lib  
directly.


  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1


  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
 If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?


  


Best Regards

Maopeng



原始邮件



发件人：张茂鹏10030173
收件人： 
抄送人：  
日 期 ：2017年08月10日 21:43
主 题 ：[onap-discuss] 答复： 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C





hi, 
 
The vnfminfo is a string, such as gvnfm,juju,zte,HUAWEI,etc. 
hope the description can clear the vnfminfo parameter. 
 
thanks. 
 
 






发件人:   张茂鹏10030173  
收件人:ds2...@att.com
抄送:er4...@intl.att.com onap-discuss@lists.onap.org
日期:   2017-08-10 21:29:59  
主题:[onap-discuss] 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C  


hi, 
 
vnfminfo is used by vf-c to identify which vendor vnfm driver to choose. 
 
thanks 
maopeng 
 
 




发件人:   SHADMI,DAVID  
收件人:张茂鹏10030173 LANDO, MICHAEL ROZIN, EDEN
抄送:yangya...@chinamobile.com denglin...@chinamobile.com 孟照星10024238 
onap-discuss@lists.onap.org
日期:   2017-08-10 20:57:55  
主题:RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C  




  




Hi,


 


My comments are embedded.


 


@Michal, @Eden – could you please help with the three questions about ELAN VL, 
service and VNF package, and the Parser?


 


Thanks,


David


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, August 10, 2017 2:57 AM
 To: SHADMI, DAVID 
 Cc: LANDO, MICHAEL  yangya...@chinamobile.com 
denglin...@chinamobile.com meng.zhaoxi...@zte.com.cn 
onap-discuss@lists.onap.org ROZIN, EDEN 
 Subject: 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C


 

hi david

 

thanks, david. a few 

[onap-discuss] 答复： 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C

[zhang.maopeng1]

hi,



The vnfminfo is a string, such as gvnfm,juju,zte,HUAWEI,etc.

hope the description can clear the vnfminfo parameter.



thanks.






 

 原始邮件 
 
 
 
 
 
 
 
 
 
 发件人: 
 张茂鹏10030173 
 
 
 
 收件人:ds2...@att.com 
 
 
 
 抄送:er4...@intl.att.com onap-discuss@lists.onap.org 
 
 
 
 日期: 
 2017-08-10 21:29:59 
 
 
 
 主题:[onap-discuss] 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C 
 
 
 
 
 
 hi, 
 
vnfminfo is used by vf-c to identify which vendor vnfm driver to choose. 
 
thanks 
maopeng 
 
 

 
 
 
 
 
 
 
 
 发件人: 
 SHADMI,DAVID 
 
 
 
 收件人:张茂鹏10030173 LANDO, MICHAEL ROZIN, EDEN 
 
 
 
 抄送:yangya...@chinamobile.com denglin...@chinamobile.com 孟照星10024238 
onap-discuss@lists.onap.org 
 
 
 
 日期: 
 2017-08-10 20:57:55 
 
 
 
 主题:RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
Hi, 
 

 
 
 
 
   
 

 
 
My comments are embedded. 
 

 
 
 
 
   
 

 
 
@Michal, @Eden – could you please help with the three questions about ELAN VL, 
service and VNF package, and the Parser? 
 

 
 
 
 
   
 

 
 
Thanks, 
 

 
 
David 
 

 
 
 
 
   
 

 
 
 
 
   
 

 
 
From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, August 10, 2017 2:57 AM
 To: SHADMI, DAVID 
 Cc: LANDO, MICHAEL  yangya...@chinamobile.com 
denglin...@chinamobile.com meng.zhaoxi...@zte.com.cn 
onap-discuss@lists.onap.org ROZIN, EDEN 
 Subject: 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C 
 

 
 
 
 
   
 

 
 
 hi david 
 

 
 
 
   
 

 
 thanks, david. a few questions below. 
 

 
 
 
   
 

 
 
#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF 
packages in R1. Also, SDC is planning to add Open-O TOSCA types. 
 

 
 
[Maopeng]does the SDC plan to add open-o TOSCA Type in R1? [David] Yes. 
That is the plan. The types’ namespace would follow OpenECOMP convention. 
 

 
 
#3 – @Michael – Could you please make sure we the node type definition 
file(s) for VF and Service exist in the wiki. @Maopeng  - could you please 
elaborate more on the node type you would like to add. 
 

 
 
 [Maopeng] If SDC can import openo tosca type in R1, I have no more node 
type to add.  But in the design time, we can desgin different VNF base on the 
VF node type and VNF package.   
 

 
 
#5 – Please see enclosed email. 
 

 
 
 [Maopeng]  Thanks. For the NS , the new parameter serviceType and 
serviceRole I think is ok.  For the VF, we need the vnfminfo. what's about your 
advice? Thanks. [David] What information the vnfminfo has? 
 

 
 
 
   
 

 
 
 
   
 

 
These questions still need your advices. 
 

 
 
   1\ Whether to support ELAN VL, which can be shared among VNFs. 
 

 
 
  [Maopeng ] now the SDC supports VL, but it is automatically produced. 
 Now I can design the Eline type VL, but for the VoLTE case , we need
multiple VNFs share one VL. 
 

 
 
  what's the automatic rule of VL creating? How to 
design it? could you show with us. thanks. 
 

 
 
[Michael: David can you respond?] 
 

 
2\The service package and vnf package CSAR in the SDC catalog, please share 
them. Thanks 
 

 
 
   3\ About the parser, VFC written in python can not use the java lib  
directly. 
 

 
 
  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1 
 

 
 
  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
  If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1? 
 

 
 
 
 
   
 

 
 Best Regards 
 

 
 Maopeng 
 

 
 
 
 
 原始邮件 
 

 
 
 
 
 
 
 
发件人：  
 

 
 
 
 
 
收件人：张茂鹏10030173  
 

 
 
 
 
 
抄送人：  孟照星10024238 
  
 

 
 
 
 
 
日 期 ：2017年08月10日 12:07 
 

 
 
 
 
 
主 题 ：RE: RE: RE: [sdc][vfc] SDC questions from VF-C 
 

 
 
 
 
 
 
 
 
   
 

 
 
 
 
Hello, 
 

 
 
  
 

 
 
#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF packages 
in R1. Also, SDC is planning to add Open-O TOSCA types. 
 

 
 
#3 – @Michael – Could you please make sure we the node type definition file(s) 
for VF and Service exist in the wiki. @Maopeng  - could you please elaborate 
more on the node type you would like to add. 
 

 
 
#5 – Please see enclosed email. 
 

 
 
  
 

 
 
  
 

 
 
Thanks, 
 

 
 
David 
 

 
 
  
 

 
 
  
 

 
 
From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Wednesday, August 09, 2017 9:15 PM
 To: LANDO, MICHAEL  SHADMI, DAVID 
 Cc: yangya...@chinamobile.com denglin...@chinamobile.com 
meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org ROZIN, EDEN 

[onap-discuss] 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C

[zhang.maopeng1]

hi,



vnfminfo is used by vf-c to identify which vendor vnfm driver to choose.



thanks

maopeng






 

 原始邮件
 
 

 

 

 

 
 发件人:
 SHADMI,DAVID 
 

 
 收件人:张茂鹏10030173 LANDO, MICHAEL ROZIN, EDEN 
 

 
 抄送:yangya...@chinamobile.com denglin...@chinamobile.com 孟照星10024238 
onap-discuss@lists.onap.org 
 

 
 日期:
 2017-08-10 20:57:55
 

 
 主题:RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C
 

 

 
 
 
 
 
 


 
 
 
Hi,
 

 
 

 
  
 

 
 
My comments are embedded.
 

 
 

 
  
 

 
 
@Michal, @Eden – could you please help with the three questions about ELAN VL, 
service and VNF package, and the Parser?
 

 
 

 
  
 

 
 
Thanks,
 

 
 
David
 

 
 

 
  
 

 
 

 
  
 

 
 
From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, August 10, 2017 2:57 AM
 To: SHADMI, DAVID 
 Cc: LANDO, MICHAEL  yangya...@chinamobile.com 
denglin...@chinamobile.com meng.zhaoxi...@zte.com.cn 
onap-discuss@lists.onap.org ROZIN, EDEN 
 Subject: 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C
 

 
 

 
  
 

 
 
 hi david
 

 
 
 
  
 

 
 thanks, david. a few questions below.
 

 
 
 
  
 

 
 
#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF 
packages in R1. Also, SDC is planning to add Open-O TOSCA types.
 

 
 
[Maopeng]does the SDC plan to add open-o TOSCA Type in R1? [David] Yes. 
That is the plan. The types’ namespace would follow OpenECOMP convention.
 

 
 
#3 – @Michael – Could you please make sure we the node type definition 
file(s) for VF and Service exist in the wiki. @Maopeng  - could you please 
elaborate more on the node type you would like to add.
 

 
 
 [Maopeng] If SDC can import openo tosca type in R1, I have no more node 
type to add.  But in the design time, we can desgin different VNF base on the 
VF node type and VNF package.  
 

 
 
#5 – Please see enclosed email.
 

 
 
 [Maopeng]  Thanks. For the NS , the new parameter serviceType and 
serviceRole I think is ok.  For the VF, we need the vnfminfo. what's about your 
advice? Thanks. [David] What information the vnfminfo has?
 

 
 
 
  
 

 
 
 
  
 

 
These questions still need your advices.
 

 
 
   1\ Whether to support ELAN VL, which can be shared among VNFs.
 

 
 
  [Maopeng ] now the SDC supports VL, but it is automatically produced. 
 Now I can design the Eline type VL, but for the VoLTE case , we need
multiple VNFs share one VL.
 

 
 
  what's the automatic rule of VL creating? How to 
design it? could you show with us. thanks.
 

 
 
[Michael: David can you respond?]
 

 
2\The service package and vnf package CSAR in the SDC catalog, please share 
them. Thanks
 

 
 
   3\ About the parser, VFC written in python can not use the java lib  
directly.
 

 
 
  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1
 

 
 
  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
  If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?
 

 
 

 
  
 

 
 Best Regards
 

 
 Maopeng
 

 
 
 
 
 原始邮件
 

 
 
 
 
 
 
 
发件人： 
 

 
 
 
 
 
收件人：张茂鹏10030173 
 

 
 
 
 
 
抄送人：  孟照星10024238 
 
 

 
 
 
 
 
日 期 ：2017年08月10日 12:07
 

 
 
 
 
 
主 题 ：RE: RE: RE: [sdc][vfc] SDC questions from VF-C
 

 
 
 
 
 
 

 
  
 

 
 
 
 
Hello,
 

 
 
 
 

 
 
#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF packages 
in R1. Also, SDC is planning to add Open-O TOSCA types.
 

 
 
#3 – @Michael – Could you please make sure we the node type definition file(s) 
for VF and Service exist in the wiki. @Maopeng  - could you please elaborate 
more on the node type you would like to add.
 

 
 
#5 – Please see enclosed email.
 

 
 
 
 

 
 
 
 

 
 
Thanks,
 

 
 
David
 

 
 
 
 

 
 
 
 

 
 
From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Wednesday, August 09, 2017 9:15 PM
 To: LANDO, MICHAEL  SHADMI, DAVID 
 Cc: yangya...@chinamobile.com denglin...@chinamobile.com 
meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org ROZIN, EDEN 

 Subject: 答复: RE: RE: [sdc][vfc] SDC questions from VF-C
 

 
 
 
 

 
 
 hi micheal & david
 

 
  
 

 
  Thanks micheal
 

 
   Now many advices need David to answer. If the email can reply, it 
will be OK.  Possible, meeting & email may be more effective way.
 

 
  The service package and vnf package CSAR in the SDC catalog, please 
share them. Thanks
 

 
   About the parser, VFC written in python can not use the java 

[onap-discuss] 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C

[zhang.maopeng1]

hi david




thanks, david. a few questions below.





#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF 
packages in R1. Also, SDC is planning to add Open-O TOSCA types.


[Maopeng]does the SDC plan to add open-o TOSCA Type in R1?


#3 – @Michael – Could you please make sure we the node type definition 
file(s) for VF and Service exist in the wiki. @Maopeng  - could you please 
elaborate more on the node type you would like to add.


 [Maopeng] If SDC can import openo tosca type in R1, I have no more node 
type to add.  But in the design time, we can desgin different VNF base on the 
VF node type and VNF package.  


#5 – Please see enclosed email.


 [Maopeng]  Thanks. For the NS , the new parameter serviceType and 
serviceRole I think is ok.  For the VF, we need the vnfminfo. what's about your 
advice? Thanks.







   These questions still need your advices.



   1\ Whether to support ELAN VL, which can be shared among VNFs.


  [Maopeng ] now the SDC supports VL, but it is automatically produced. 
 Now I can design the Eline type VL, but for the VoLTE case , we need
multiple VNFs share one VL.


  what's the automatic rule of VL creating? How to 
design it? could you show with us. thanks.


[Michael: David can you respond?]

   2\The service package and vnf package CSAR in the SDC catalog, please share 
them. Thanks




   3\ About the parser, VFC written in python can not use the java lib  
directly.


  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1


  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
 If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?





Best Regards

Maopeng



原始邮件



发件人： 
收件人：张茂鹏10030173 
抄送人：  孟照星10024238 
 
日 期 ：2017年08月10日 12:07
主 题 ：RE: RE: RE: [sdc][vfc] SDC questions from VF-C







Hello,


 


#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF packages 
in R1. Also, SDC is planning to add Open-O TOSCA types.


#3 – @Michael – Could you please make sure we the node type definition file(s) 
for VF and Service exist in the wiki. @Maopeng  - could you please elaborate 
more on the node type you would like to add.


#5 – Please see enclosed email.


 


 


Thanks,


David


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Wednesday, August 09, 2017 9:15 PM
 To: LANDO, MICHAEL  SHADMI, DAVID 
 Cc: yangya...@chinamobile.com denglin...@chinamobile.com 
meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org ROZIN, EDEN 

 Subject: 答复: RE: RE: [sdc][vfc] SDC questions from VF-C


 

hi micheal & david

 

 Thanks micheal

  Now many advices need David to answer. If the email can reply, it 
will be OK.  Possible, meeting & email may be more effective way.

 The service package and vnf package CSAR in the SDC catalog, please 
share them. Thanks

  About the parser, VFC written in python can not use the java lib  
directly.

  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1

  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
  If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?



Best Regards

Maopeng


原始邮件



发件人： 



收件人：张茂鹏10030173



抄送人：    
孟照星10024238  




日 期 ：2017年08月10日 03:27



主 题 ：RE: RE: [sdc][vfc] SDC questions from VF-C




 


 


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Wednesday, August 09, 2017 7:09 PM
 To: Lando,Michael 
 Cc: yangya...@chinamobile.com SHADMI, DAVID  
denglin...@chinamobile.com meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org
 Subject: 答复: RE: [sdc][vfc] SDC questions from VF-C


 

Hi Michael

 

thanks for your reply. 

 

1. For the api document,  I really need more time to 

[onap-discuss] 答复: RE: RE: [sdc][vfc] SDC questions from VF-C

[zhang.maopeng1]

hi micheal & david




 Thanks micheal

  Now many advices need David to answer. If the email can reply, it 
will be OK.  Possible, meeting & email may be more effective way.

 The service package and vnf package CSAR in the SDC catalog, please 
share them. Thanks

  About the parser, VFC written in python can not use the java lib  
directly.

  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1

  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
 If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?



Best Regards

Maopeng



原始邮件



发件人： 
收件人：张茂鹏10030173
抄送人：   
孟照星10024238  

日 期 ：2017年08月10日 03:27
主 题 ：RE: RE: [sdc][vfc] SDC questions from VF-C







 


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Wednesday, August 09, 2017 7:09 PM
 To: Lando,Michael 
 Cc: yangya...@chinamobile.com SHADMI, DAVID  
denglin...@chinamobile.com meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org
 Subject: 答复: RE: [sdc][vfc] SDC questions from VF-C


 

Hi Michael

 

thanks for your reply. 

 

1. For the api document,  I really need more time to read it. For R1, the 
VFC team main funciton is to get the distributed Service CSAR and VF CSAR from 
SDC catalog. thanks.

2. About the VNF package, thanks for sharing the vFW/vDNS CSAR. Is the 
Tosca onboarding function release on R1?  which tosca profile does the SDC 
follows in R1? does the VNF vendor need to follow it? thanks.  [Michael: David  
please advise]

3. About the service package, please provide the CSAR example for R1. In 
the wiki page, SDC_TOSCA_AID_1710 document has no nodes definitions, such as 
service, VF, VL,etc. could you provide the nodes definition for R1 in the wiki? 
 could SDC support adding  new node type? such as VF, could we add a new VFXX 
extending from VF via SDC GUI, and not changing the SDC code? [Michael: David 
please advise]

   4. Parser is also an issue.  Now there are many parsers. but which one can 
match the SDC output?  is the SDC output CSAR align with OASIS tosca simple 
profile 1.0?

  Could the SDC parser provide the REST API?

[Michael: the SDC parser can match our output I cannot speak 
for the other parsers. The SDC parser comes in the form of a jar that you will 
need to integrate as  a library into your code so no rest api is needed here]


5. The NS package questions about VL and parameter controlinfo and 
vnfminfo, please DAVID help me.


[Michael: David please advise]


 


   If possible, I will reserve a  zoom meeting in 21:00 2017/810 (UTC+8).  I 
can prepare an slide from VFC side and needs the SDC team help us.


[MIcheal: what would you need from us for this call?]


 


Thanks


Maopeng



发件人： 



收件人：张茂鹏10030173   



抄送人： 孟照星10024238  



日 期 ：2017年08月09日 20:00



主 题 ：RE: [sdc][vfc] SDC questions from VF-C




BR,


 


Michael Lando 


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office:  +972 (3) 5451487


Mobile:  +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Wednesday, August 09, 2017 2:05 PM
 To: yangya...@chinamobile.com Lando,Michael  SHADMI, 
DAVID 
 Cc: denglin...@chinamobile.com meng.zhaoxi...@zte.com.cn 
onap-discuss@lists.onap.org
 Subject: 答复: [sdc][vfc] SDC questions from VF-C


 


Hi Michael & David & Yan,


 


I refesh the questions, and hope the SDC team can give some answers. I also 
think we need an meeting to discuss these issues. Thanks.


 


In SDC API document, we didn’t see the registration and notification API ,can 
you provide this API for us.


[Maopeng ]   thanks for micheal share the document, 
https://wiki.onap.org/pages/viewpage.action?pageId=11929307 


 we will review it and It is very complicated api document.


 If Micheal can give an example to the VFC team, 

[onap-discuss] 答复: [sdc][vfc] SDC questions from VF-C

[zhang.maopeng1]

Hi Michael & David & Yan,






I refesh the questions, and hope the SDC team can give some answers. I also 
think we need an meeting to discuss these issues. Thanks.







In SDC API document, we didn’t see the registration and notification API ,can 
you provide this API for us.


[Maopeng ]   thanks for micheal share the document, 
https://wiki.onap.org/pages/viewpage.action?pageId=11929307 


 we will review it and It is very complicated api document.


 If Micheal can give an example to the VFC team,  it will 
be great for the whole team.






How does the SDC Resource / Service Categories fits to the VoLTE case? for 
exmaple spgw/ims etc in which Categories/subCategory?


[Maopeng ]  Service categories can be defined by the administrator via the GUI. 
 I think if we need new categories or subcategories, we can add it via the GUI. 
Right? 






2.   VNF package


We want to know the VNF CSAR package format exported from SDC, can you give us 
an example, we want to confirm whether the package has some format restrictions.


[Maopeng ] In the R1,  VNFSDK bundles a VNF package, and import to the SDC. VFC 
get the VNF package from the SDC catalog.


   Is the VNF package defined in the VNFSDK or SDC for R1? 
What's the VNF package format for VFC in R1?  






 2.  NS package


   Whether to support ELAN VL, which can be shared among VNFs.


  [Maopeng ] now the SDC supports VL, but it is automatically produced. 
 Now I can design the Eline type VL, but for the VoLTE case , we need multiple 
VNFs share one VL.


  what's the automatic rule of VL creating? How to 
design it? could you show with us. thanks.






   Whether the metadata can be extended, from VF-C side we need some fields 
,such as controlinfo, vnfminfo,..etc, so we want to know Whether SDC support 
metadata extension   


  [Maopeng ] In VoLTE case we need the conrollerinfo in service to 
identify the NS and need the VNFM info in VF to identify the SVNFM.


 If the SDC team can add the parameter in the 
metadata, it will be useful for the VFC  team. 


 In the meeting of SO and SDC, DAVID suggests use 
the category parameter of metadata.  It can work, but not clear for user.






Best Regards


Maopeng



原始邮件



发件人： 
收件人： 张茂鹏10030173 孟照星10024238 

日 期 ：2017年08月08日 18:13
主 题 ：[sdc][vfc] SDC questions from VF-C







Hi Michael,


VF-C team has some issues that need to be confirmed by SDC team.


1.   About SDC API(This has been listed in the blokers wiki page)


In SDC API document, we didn’t see the registration and notification API ,can 
you provide this API for us.


How does the SDC Resource / Service Categories fits to the VoLTE case? for 
exmaple spgw/ims etc in which Categories/subCategory?


2.   VNF package


We want to know the VNF CSAR package format exported from SDC, can you give us 
an example, we want to confirm whether the package has some format restrictions.


 2.  NS package


   Whether to support ELAN VL, which can be shared among VNFs.


   Whether the metadata can be extended, from VF-C side we need some fields 
,such as controlinfo, vnfminfo,..etc, so we want to know Whether SDC support 
metadata extension   


  Whether the NS package exported from SDC support TOSCA simple profile 
and standard, we want to confirm that these packages can be handled by parsers.


   


Hopefully we can get feedback from SDC team asap. If you want to know more 
details about these questions, we can also set a conf call. I suggest one time 
on Wednesday UTC 12:00/China 20:00. If you think it’s ok, I will send an 
invitation to you.


 


 


Best Regards,


Yan___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: Re: 答复: [integration] RE: About CI job Script for python project in ONAP

[zhang.maopeng1]

hi helpdesk & Gary

   

Thanks Gary for your help.  

Now the issue is still blocked and codes of VF-C can not be submitted.

Please helpdesk help them and fix it ASAP.

thanks.




Best Regards

Maopeng







原始邮件



发件人： 
收件人： 
抄送人： 傅锦华10108953
日 期 ：2017年08月08日 22:17
主 题 ：Re: [onap-discuss]答复: [integration] RE: About CI job Script for python 
project in ONAP







Hi helpdesk,


 


Can you help?  It seems that the redis minion is unavailable in Jenkins.


 


Thanks,


Gary


 


From: fu.jin...@zte.com.cn [mailto:fu.jin...@zte.com.cn] 
 Sent: Monday, August 07, 2017 8:01 PM
 To: Gary Wu 
 Cc: onap-discuss@lists.onap.org
 Subject: 答复: RE: RE: Re:[onap-discuss] 答复: [integration] RE: About CI job 
Script for python project in ONAP


 

Hi Gary,

I found that your commit for redis install in jenkins env has merged, and I 
modify the job node to ‘ubuntu1604-redis-4c-4g’,

but jenkins shows that node  ‘ubuntu1604-redis-4c-4g’ can not be found, can you 
check it again?

Thanks,

Jinhua

 


原始邮件



发件人： 



收件人：傅锦华10108953



抄送人： 



日 期 ：2017年08月04日 22:35



主 题 ：RE: RE: Re:[onap-discuss] 答复: [integration] RE: About CI job Script for 
python project in ONAP




 


Jinhua,


 


FYI I’ve submitted https://gerrit.onap.org/r/#/c/6727/ for the redis install, 
but only LF staff can merge changes in ci-management so hopefully they will get 
to it soon.


 


Once the above is in place, you’ll need to modify your build job to use the 
‘ubuntu1604-redis-4c-4g’  build-node.


 


By the way, it wasn’t clear whether you needed Activiti in this environment as 
well.  However, the  command that was provided:


 


wget https://www.activiti.org/download-bpm/releases/activiti-5.21.0.tar.gz


 


returns 404 not found (looks like it needs registration).  If you do need 
Activiti installed in the  build environment, please provide commands or links 
that can  work from the command line, and also an init.d/systemd script for 
tomcat so that we can configure the system to start tomcat on startup.


 


Thanks,


Gary


 



From: Gary Wu 
 Sent: Friday, August 04, 2017 6:27 AM
 To: 'fu.jin...@zte.com.cn' 
 Cc: onap-discuss@lists.onap.org
 Subject: RE: RE: Re:[onap-discuss] 答复: [integration] RE: About CI job Script 
for python project in ONAP




 


Hi Jinhua,


 


Ok, I’ll submit these changes to ci-management and let you know when they’re 
done. 


 


Thanks,


Gary


 


From: fu.jin...@zte.com.cn [mailto:fu.jin...@zte.com.cn] 
 Sent: Friday, August 04, 2017 1:52 AM
 To: Gary Wu 
 Cc: meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org 
zhang.maope...@zte.com.cn
 Subject: 答复: RE: Re:[onap-discuss] 答复: [integration] RE: About CI job Script 
for python project in ONAP


 

Hi Gary,

How about the redis install in jenkins env? We cannot submit the codes now, can 
you help to fix it as soon as possible?

And another problem is that ci job scripts for python project only support 
subproject pattern(like  '{project-name}-{stream}-{subproject}-verify-python'),

can you extend the template which can support non-subproject pattern(like  
'{project-name}-{stream}-verify-python'), because in onap vfc-nfvo-lcm is an 
independent project.

Thanks,

Jinhua

 


原始邮件



发件人： 



收件人：孟照星10024238傅锦华10108953



抄送人： 



日 期 ：2017年08月04日 01:26



主 题 ：RE: Re:[onap-discuss] 答复: [integration] RE: About CI job Script for python 
project in ONAP




 


Hi Zhaoxing,


 


Is the Tomcat/Activiti setup also required for your unit tests?


 


The tests that require live API calls to other running services (redis, tomcat, 
etc.) are really meant   to be implemented as CSIT test cases instead of UT 
this  way you have full control over the setup and configuration of the 
supporting services (via docker containers) as you see fit, instead of having 
to configure a special Jenkins slave VM image just to   handle your specific UT 
requirements. 


 


Would that work for you?  i.e. move the UT test cases involving live API calls 
into CSIT instead.If this can be done relatively easily then that would be 
the  ideal approach.  Otherwise, I can start the process to configure a special 
Jenkins slave VM image for you, but just be aware that the turnaround is slow 
on any needed changes/fixes on these VM  images  if your requirements change.


 


Thanks,


Gary


 


From: meng.zhaoxi...@zte.com.cn [mailto:meng.zhaoxi...@zte.com.cn] 
 Sent: Thursday, August 03, 2017 12:49 AM
 To: fu.jin...@zte.com.cn
 Cc: Gary Wu  onap-discuss@lists.onap.org
 Subject: Re:[onap-discuss] 答复: [integration] RE: About CI job Script for 
python project in ONAP


 


workflow engine


 


1. download Tomcat


cd /


sudo mkdir temp


cd /temp


wget 

[onap-discuss] 答复: SDC Questions( SDC Integration slides)

[zhang.maopeng1]

hi SDC team, VFC team,




Here is the analysis results from VFC team and please the SDC team 
confirms with it. 


No


Gaps


Action Owner


 When/Dead Line


1


Import VNF TOSCA Package into SDC Catalog, which supports TOSCA NFV Profile


SDC/Catalog


VoLTE Case profiles has been provided,   Profile need to be confirmed by SDC 
Team this week



2


NS package design supports CSAR and TOSCA NFV template


SDC/Catalog


VoLTE Case profiles has been provided,   Profile need to be confirmed by SDC 
Team this week


3


VNF Distribution


Usecase UI


Usecase UI will be in charge of this function


4


NS/VNF package info query with CSARID


SDC/Catalog


Provided in the API DOC


5


NS/VNF package info query with filter conditions


SDC/Catalog


Provided in the API DOC






Note:


How does the SDC Resource / Service Categories fits to the  the VoLTE case? for 
exmaple spgw/ims etc in which Categories/subCategory? this week


6


Http server to download NS/VNF CSAR packages or templates


SDC/Catalog


Provided in the API DOC


7


SDC Reg/Notify supports TOSCA CSAR packages and interfaces


SDC/Catalog


Not Provided in the API   DOC, need  to be added in the document or provided 
elsewhere by SDC team this week.  


8


VNF distribution function and interfaces


VFC


VNF Distribution has been showed in   the P4


the interfaces referenece:


https://wiki.open-o.org/display/NFVO/NFVO%3ANSLCM+API+Definition 5.1  


9


Provide NS/VNF TOSCA NFV Profile


Model/VFC/SDC


https://gerrit.open-o.org/r/#/admin/projects/modelling-csar


https://gerrit.open-o.org/r/#/admin/projects/modelling-specs


10


Model Parsers integrates with the SDC package output


Model/SDC


Need the SDC team output the TOSCA  Package this week.





I also add the key issues in the wiki:


https://wiki.onap.org/display/DW/July+Virtual+Developers+Event+Blockers 
SDC/VFC integration topic




 Identify the gaps before the functional freeze milestone, here are the 
action items and date.

Need to confirm whether supports importing VNF TOSCA packages into SDC  
 - by 07/28

VoLTE Case TOSCA NFV profiles has been provided, needs the SDC team output the 
TOSCA Packages according to the VoLTE Case -by 07/28

 Need  to provide  reg/notify interfaces in the API document.  -by 07/28

How does the SDC Resource / Service Categories fits to the  the VoLTE case? for 
exmaple spgw/ims etc in which Categories/subCategory?-by 07/28





  We hope the teams from each side can together resolve those issues ASAP, 
thank you.




Best Regards

Maopeng



原始邮件



发件人：张茂鹏10030173
收件人： 
抄送人：  
日 期 ：2017年07月27日 09:32
主 题 ：SDC Questions( SDC Integration slides)






hi kenny, SDC team, VFC team,




The attachment is  SDC Integration slides in the SDC Question topic.




 The CSAR model can be got from the OpenO model as reference. URL is the 
below:

   https://gerrit.open-o.org/r/#/admin/projects/modelling-csar 

   https://gerrit.open-o.org/r/#/admin/projects/modelling-specs 




 Today I will analyze the interfaces provided by SDC team, hope we can 
together make the usecase successful.

 Thanks




Best Regards

Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: Re: 答复: Re: About workflow engine

[zhang.maopeng1]

Hi Zahi




   The meeting time may conflict with the virtual development meeting. 

   IMHO, I think both the design-time and runtime are important.

   We can talk the requirement from the design-time, and also want to discuss 
the possiblity that make the workflow engine  as mirco service and make the 
designer more easy。




Best Regards

Maopeng







原始邮件



发件人： 
收件人：张茂鹏10030173
抄送人：   

日 期 ：2017年07月20日 20:59
主 题 ：Re: 答复: Re: [onap-discuss] About workflow engine 





I would like to focus our discussion on design-time change management workflows 
(e.g., pause, upgrade etc.) and how current tooling fits into the overall SDC 
architecture and UX.

Can I set a meeting for next Tuesday, 17:00 UTC+3?

Zahi Kapeluto
Lead Architect, Network Communications LOB
AT Network Applications Development · SD
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064

From: "zhang.maope...@zte.com.cn" 
Date: Thursday, 20 July 2017 at 4:54
To: ZAHI KAPELUTO 
Cc: "seshu.kuma...@huawei.com" , 
"onap-discuss@lists.onap.org" , "SACKS, ZOHAR" 

Subject: 答复: Re: [onap-discuss] About workflow engine


Hi Zahi



Yes, definite.  Workflow engines have different workflow templates. If 
the workflow is designed by user via SDC,  it will effect SDC.

In my mind, some workflow is used by user, maybe some workflow is used 
only by the code developer as well, such as Camunda offline tools, DG offline 
tools,

However  if the workflow design for user can be integrated with SDC via 
portal SDK, It will be greater.



Best Regards

Maopeng
原始邮件
发件人： 
收件人：张茂鹏10030173  
抄送人： 
日 期 ：2017年07月20日 02:27
主 题 ：Re: [onap-discuss] About workflow engine


Can we also have a discussion about the workflow designer (which should be part 
of SDC), its capabilities, proposed architecture etc.?

Zahi Kapeluto
Lead Architect, Network Communications LOB
AT Network Applications Development · SD
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064

From:  on behalf of 
"zhang.maope...@zte.com.cn" 
Date: Wednesday, 19 July 2017 at 12:46
To: "seshu.kuma...@huawei.com" , 
"onap-discuss@lists.onap.org" 
Subject: [onap-discuss] About workflow engine


Hi seshu and guys



   About the workflow engine(WFE) usage, I have an idea and want to share in 
the community, If I am wrong, please correct me.

   In the SO or controllers projects of ONAP,  there are many opensource party 
workflow engines, such as Camunda, MSO, DG, aria tosca workflow engine, ...etc.

   Most of those workflow engines now bind to the project.

   Workflow engines self are independant fucntion and can be decoupled with the 
specific project logic functions.

   Could the projects make them as micro service? If some projects use the 
same one,  the WFE instance could be shared among them.

   If possible, we can create an group or wiki page to discuss the issue.

   Thanks all.



Best Regards

Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: Re: About workflow engine

[zhang.maopeng1]

Hi Zahi




Yes, definite.  Workflow engines have different workflow templates. If 
the workflow is designed by user via SDC,  it will effect SDC.

In my mind, some workflow is used by user, maybe some workflow is used 
only by the code developer as well, such as Camunda offline tools, DG offline 
tools,

However  if the workflow design for user can be integrated with SDC via 
portal SDK, It will be greater.




Best Regards

Maopeng



原始邮件



发件人： 
收件人：张茂鹏10030173  
抄送人： 
日 期 ：2017年07月20日 02:27
主 题 ：Re: [onap-discuss] About workflow engine 





Can we also have a discussion about the workflow designer (which should be part 
of SDC), its capabilities, proposed architecture etc.?

Zahi Kapeluto
Lead Architect, Network Communications LOB
AT Network Applications Development · SD
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064

From:  on behalf of 
"zhang.maope...@zte.com.cn" 
Date: Wednesday, 19 July 2017 at 12:46
To: "seshu.kuma...@huawei.com" , 
"onap-discuss@lists.onap.org" 
Subject: [onap-discuss] About workflow engine


Hi seshu and guys



   About the workflow engine(WFE) usage, I have an idea and want to share in 
the community, If I am wrong, please correct me.

   In the SO or controllers projects of ONAP,  there are many opensource party 
workflow engines, such as Camunda, MSO, DG, aria tosca workflow engine, ...etc.

   Most of those workflow engines now bind to the project.

   Workflow engines self are independant fucntion and can be decoupled with the 
specific project logic functions.

   Could the projects make them as micro service? If some projects use the 
same one,  the WFE instance could be shared among them.

   If possible, we can create an group or wiki page to discuss the issue.

   Thanks all.



Best Regards

Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] About workflow engine

[zhang.maopeng1]

Hi seshu and guys




   About the workflow engine(WFE) usage, I have an idea and want to share in 
the community, If I am wrong, please correct me.

   In the SO or controllers projects of ONAP,  there are many opensource party 
workflow engines, such as Camunda, MSO, DG, aria tosca workflow engine, ...etc. 
 

   Most of those workflow engines now bind to the project. 

   Workflow engines self are independant fucntion and can be decoupled with the 
specific project logic functions. 

   Could the projects make them as micro service? If some projects use the 
same one,  the WFE instance could be shared among them.

   If possible, we can create an group or wiki page to discuss the issue.

   Thanks all.




Best Regards

Maopeng___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [openlab] OpenLab Kickoff Meeting Schedule

[zhang.maopeng1]

Hi chengli

 

 The time is ok for me.

 If possible, I let yunlong in the loop, who will join the integration and 
lab.




Best Regards

Maopeng







Original Mail



Sender:  
To:    
   
 ZhangMaoPeng10030173 
   
  
CC:  
Date: 2017/07/07 16:04
Subject: Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule






Hi,



If the time slot works for majority folks, I will send invite and logistic next 
Monday.



Thanks,

Chengli

在 2017年7月7日，下午4:00，Chengli Wang  写道：


Hi Subcommittees,


I would like to invite you to attend open lab subcommittee  kickoff meeting. As 
so many meetings scheduled in each week it hard to find more suitable time slot 
for everyone located in different time zone.

I propose our first meeting time is 8:30 am July 12,2017 Beijing time, 8:30 pm 
July 11, 2017, EDT, Is it work for you?



On the Kickoff meeting, I proposed agenda below, 




1. Proposed lab specification and guidelines (refer to OPNFV Pharos), linked 
here(Specification, https://wiki.onap.org/display/DW/ONAP+Lab+Specification 
Guide https://wiki.onap.org/display/DW/ONAP+Lab+Guide), Welcome review and 
comments in advance.

2. Discussion on collaboration with Integration team on CI/CD and E2E 
integration test.

3. Solicit Interest of Usecases Integration Testing from Lab Donators




Hope you can join us and feedback.



Thanks and Regards,

Chengli___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] VF-C project PTL Election

[zhang.maopeng1]

+1










Original Mail



Sender:  
To:    
 fujinhua10108953 
  
zhangmaopeng10030173  
  
  
CC:  
Date: 2017/06/24 17:30
Subject: VF-C project PTL Election







Dear VF-C committers,


 


Upon close our self-nomination period, we only have one candidate: Yan Yang. 
According to LF rules, we still need to run the election. I’d like to start the 
vote through email, and close the vote at Wednesday, June 28rd, 11:59 PM, PDT.


 


Committers, if you support Yan Yang for PTL, would you please respond to this 
message with “+1”.If you don’t, please respond with “-1”, and if you are 
neutral, please respond with “0”.


 


Regards,


Yan Yang


 


 


Committers list upon VF-C project approval date 06/08/2017 for your reference:


Lingli Deng  denglin...@chinamobile.com


Maopeng Zhang  zhang.maope...@zte.com.cn


Kanagaraj Manickam  kanagaraj.manic...@huawei.com


Jinhua Fufu.jin...@zte.com.cn


Yan Yangyangya...@chinamobile.com


Victor Gao   victor@huawei.com


Anatoly Andrianov anatoly.andria...@nokia.com


Nagesha Subramanya  nagesha.subrama...@nokia.com


Xinhui Li   lxin...@vmware.com 


Guirong Wangwangguir...@boco.com.cn


Xiaodong Ningningxiaodong2...@boco.com.cn


Yog Vashishth yog.vashis...@ril.com 


Adityakar Jhaadityakar@ril.com


Hu Dongdon...@raisecom.com   


Yannan Han hanya...@raisecom.com___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss