Re: [onap-tsc] Modeling/etsicatalog withdraw form Kohn release

[denghui (L) via lists.onap.org]

Thank you, Amy

DENG Hui

From: ZWARICO, AMY [mailto:az9...@att.com]
Sent: Thursday, July 21, 2022 8:48 PM
To: onap-tsc@lists.onap.org; dengyuanh...@chinamobile.com; dmcbride 
; denghui (L) 
Cc: 'onap-release' ; Lefevre, Catherine 
; kp...@linuxfoundation.org; 'denglingli' 
; yangxu (H) 
Subject: RE: [onap-tsc] Modeling/etsicatalog withdraw form Kohn release

SECCOM has confirmed that modeling-etsicatalog does not contain any vulnerable 
3rd party direct dependencies.
Best regards,
Amy

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of 
Byung-Woo Jun via lists.onap.org
Sent: Thursday, July 21, 2022 6:28 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
dengyuanh...@chinamobile.com<mailto:dengyuanh...@chinamobile.com>; dmcbride 
mailto:dmcbr...@linuxfoundation.org>>; 'denghui 
(L)' mailto:denghu...@huawei.com>>
Cc: onap-...@lists.onap<mailto:onap-...@lists.onap>. 
mailto:onap-tsc@lists.onap.org>>; 'onap-release' 
mailto:onap-rele...@lists.onap.org>>; Lefevre, 
Catherine 
mailto:catherine.lefe...@intl.att.com>>; 
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; 'denglingli' 
mailto:denglin...@chinamobile.com>>; yangxu5 
mailto:yang...@huawei.com>>
Subject: Re: [onap-tsc] Modeling/etsicatalog withdraw form Kohn release

Hi David,

I’d like to clarify the following:

The modeling/etsicatalog component will not be enhanced/maintained in Kohn for 
no new feature, but the component is still deployed in ONAP, as is. The 
ONAP-ETSI alignment needs the component function.

Could you please confirm?

BR,
Byung

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> on behalf of 
hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com> via lists.onap.org 
mailto:hekeguang=chinamobile@lists.onap.org>>
Date: Thursday, July 21, 2022 at 3:06 AM
To: dengyuanh...@chinamobile.com<mailto:dengyuanh...@chinamobile.com> 
mailto:dengyuanh...@chinamobile.com>>, dmcbride 
mailto:dmcbr...@linuxfoundation.org>>, 'denghui 
(L)' mailto:denghu...@huawei.com>>
Cc: onap-...@lists.onap<mailto:onap-...@lists.onap>. 
mailto:onap-tsc@lists.onap.org>>, 'onap-release' 
mailto:onap-rele...@lists.onap.org>>, Lefevre, 
Catherine 
mailto:catherine.lefe...@intl.att.com>>, 
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org> 
mailto:kp...@linuxfoundation.org>>, 'denglingli' 
mailto:denglin...@chinamobile.com>>, yangxu5 
mailto:yang...@huawei.com>>
Subject: Re: [onap-tsc] Modeling/etsicatalog withdraw form Kohn release
Hi David,

As Yuanhong said, our models only need to be archived in modeling, and do not 
rely on the modeling/etsicatalog project.

Best regards,
Keguang


hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com>

From: dengyuanhong<mailto:dengyuanh...@chinamobile.com>
Date: 2022-07-21 15:02
To: 'David McBride'<mailto:dmcbr...@linuxfoundation.org>; 'denghui 
\(L\)'<mailto:denghu...@huawei.com>; 
hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com>
CC: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
'onap-release'<mailto:onap-rele...@lists.onap.org>; 'Catherine 
LEFEVRE'<mailto:catherine.lefe...@intl.att.com>; 'Kenny 
Paul'<mailto:kp...@linuxfoundation.org>; 
'邓灵莉'<mailto:denglin...@chinamobile.com>; 'yangxu 
\(H\)'<mailto:yang...@huawei.com>
Subject: RE: Modeling/etsicatalog withdraw form Kohn release
Hi David,

I have already contacted with Keguang, REQ-1267 does not depend on the 
modeling/etsicatalog project, it only has a relationship with the Modeling 
Committee.

Best regards,
Yuanhong

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Thursday, July 21, 2022 4:49 AM
To: denghui (L); hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com>
Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-release; 
dengyuanh...@chinamobile.com<mailto:dengyuanh...@chinamobile.com>; Catherine 
LEFEVRE; Kenny Paul; 邓灵莉; yangxu (H)
Subject: Re: Modeling/etsicatalog withdraw form Kohn release

+hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com>

Deng,

Have you and Yuanhong communicated your status to Keguang?  REQ-1267 is 
dependent on changes to the Modeling 
project<https://urldefense.com/v3/__https:/wiki.onap.org/x/8QWsBw__;!!BhdT!ju7giHiiIReslqBDvsbaDO05BUkfGD1SaI8MkYKiaYQ62u_ixcvOlDKS9dZAOkRhDr1bkZbGOPukhI5Ok21LLXyExZD8ZBc$>.
  Please advise.

Keguang - will you need to adjust the scope of REQ-1267?

David

On Wed, Jul 20, 2022 at 9:32 AM David McBride 
mailto:dmcbr...@linuxfoundation.org>> wro

Re: [onap-tsc] [Onap-release] Modeling/etsicatalog withdraw form Kohn release

[denghui (L) via lists.onap.org]

Hi Thomas

as previously mentioned, modeling/etsicatalog plans not to join K release, and 
we think it’s not necessary to include it in the documentation as well. For 
modeling/modelspec, Xu will handle it for the K release.

Thanks for your checking

DENG Hui

From: thomas.ku...@telekom.de [mailto:thomas.ku...@telekom.de]
Sent: Thursday, July 21, 2022 4:35 PM
To: dmcbr...@linuxfoundation.org; denghui (L) ; 
hekegu...@chinamobile.com
Cc: onap-tsc@lists.onap.org; onap-rele...@lists.onap.org; 
dengyuanh...@chinamobile.com; catherine.lefe...@intl.att.com; 
kp...@linuxfoundation.org; denglin...@chinamobile.com; yangxu (H) 

Subject: AW: [Onap-release] Modeling/etsicatalog withdraw form Kohn release

Hi all.
But please create a ‚Kohn’ branch if you like to see your documentation in the 
Kohn release. It is ok that your release note then shows “nothing new in this 
release” in this case.
We (doc) will create ‘Kohn’ documentation only from ‘Kohn’ branches!

Thomas
Von: onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org> 
mailto:onap-rele...@lists.onap.org>> Im Auftrag 
von David McBride
Gesendet: Mittwoch, 20. Juli 2022 22:49
An: denghui (L) mailto:denghu...@huawei.com>>; 
hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com>
Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-release 
mailto:onap-rele...@lists.onap.org>>; 
dengyuanh...@chinamobile.com<mailto:dengyuanh...@chinamobile.com>; Catherine 
LEFEVRE 
mailto:catherine.lefe...@intl.att.com>>; Kenny 
Paul mailto:kp...@linuxfoundation.org>>; 邓灵莉 
mailto:denglin...@chinamobile.com>>; yangxu (H) 
mailto:yang...@huawei.com>>
Betreff: Re: [Onap-release] Modeling/etsicatalog withdraw form Kohn release

+hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com>

Deng,

Have you and Yuanhong communicated your status to Keguang?  REQ-1267 is 
dependent on changes to the Modeling project<https://wiki.onap.org/x/8QWsBw>.  
Please advise.

Keguang - will you need to adjust the scope of REQ-1267?

David

On Wed, Jul 20, 2022 at 9:32 AM David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:
Ok - understood.  Thanks for the update. - D

On Tue, Jul 19, 2022 at 6:48 PM denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hi David

We (Yuanhong Deng together) want to inform you that Modeling/etsicatalog plan 
not join Kohn release, since there is no new feature update needed.
So there is only modeling/modelspec documentation left for K release.

Thanks a lot for your checking
Best regards,

DENG Hui

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>] On Behalf Of 
David McBride
Sent: Wednesday, July 20, 2022 3:59 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>; 
onap-release mailto:onap-rele...@lists.onap.org>>
Cc: Catherine LEFEVRE 
mailto:catherine.lefe...@intl.att.com>>; Kenny 
Paul mailto:kp...@linuxfoundation.org>>
Subject: [onap-tsc] Multicloud project withdrawing from the Kohn release #kohn 
#multicloud

Team,

I was informed, yesterday, that the Multicloud project is withdrawing from the 
Kohn release.

David

--
David McBride (pronounce<https://nmdrp.me/davidmcbride>)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>


--
David McBride (pronounce<https://nmdrp.me/davidmcbride>)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>


--
David McBride (pronounce<https://nmdrp.me/davidmcbride>)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8785): https://lists.onap.org/g/onap-tsc/message/8785
Mute This Topic: https://lists.onap.org/mt/92522747/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: 
https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Modeling/etsicatalog withdraw form Kohn release

[denghui (L) via lists.onap.org]

Thanks Keguang and yuanhong for quick response, in this case, shall we remove 
modeling dependency in REQ 1267?

Best regards,
DEGN Hui

From: hekegu...@chinamobile.com [mailto:hekegu...@chinamobile.com]
Sent: Thursday, July 21, 2022 3:07 PM
To: dengyuanh...@chinamobile.com; dmcbride ; 
denghui (L) 
Cc: onap-...@lists.onap. ; 'onap-release' 
; Lefevre, Catherine 
; kp...@linuxfoundation.org; 'denglingli' 
; yangxu (H) 
Subject: Re: RE: Modeling/etsicatalog withdraw form Kohn release

Hi David,

As Yuanhong said, our models only need to be archived in modeling, and do not 
rely on the modeling/etsicatalog project.

Best regards,
Keguang


hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com>

From: dengyuanhong<mailto:dengyuanh...@chinamobile.com>
Date: 2022-07-21 15:02
To: 'David McBride'<mailto:dmcbr...@linuxfoundation.org>; 'denghui 
\(L\)'<mailto:denghu...@huawei.com>; 
hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com>
CC: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
'onap-release'<mailto:onap-rele...@lists.onap.org>; 'Catherine 
LEFEVRE'<mailto:catherine.lefe...@intl.att.com>; 'Kenny 
Paul'<mailto:kp...@linuxfoundation.org>; 
'邓灵莉'<mailto:denglin...@chinamobile.com>; 'yangxu 
\(H\)'<mailto:yang...@huawei.com>
Subject: RE: Modeling/etsicatalog withdraw form Kohn release
Hi David,

I have already contacted with Keguang, REQ-1267 does not depend on the 
modeling/etsicatalog project, it only has a relationship with the Modeling 
Committee.

Best regards,
Yuanhong

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Thursday, July 21, 2022 4:49 AM
To: denghui (L); hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com>
Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-release; 
dengyuanh...@chinamobile.com<mailto:dengyuanh...@chinamobile.com>; Catherine 
LEFEVRE; Kenny Paul; 邓灵莉; yangxu (H)
Subject: Re: Modeling/etsicatalog withdraw form Kohn release

+hekegu...@chinamobile.com<mailto:hekegu...@chinamobile.com>

Deng,

Have you and Yuanhong communicated your status to Keguang?  REQ-1267 is 
dependent on changes to the Modeling project<https://wiki.onap.org/x/8QWsBw>.  
Please advise.

Keguang - will you need to adjust the scope of REQ-1267?

David

On Wed, Jul 20, 2022 at 9:32 AM David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:
Ok - understood.  Thanks for the update. - D

On Tue, Jul 19, 2022 at 6:48 PM denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hi David

We (Yuanhong Deng together) want to inform you that Modeling/etsicatalog plan 
not join Kohn release, since there is no new feature update needed.
So there is only modeling/modelspec documentation left for K release.

Thanks a lot for your checking
Best regards,

DENG Hui

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>] On Behalf Of 
David McBride
Sent: Wednesday, July 20, 2022 3:59 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>; 
onap-release mailto:onap-rele...@lists.onap.org>>
Cc: Catherine LEFEVRE 
mailto:catherine.lefe...@intl.att.com>>; Kenny 
Paul mailto:kp...@linuxfoundation.org>>
Subject: [onap-tsc] Multicloud project withdrawing from the Kohn release #kohn 
#multicloud

Team,

I was informed, yesterday, that the Multicloud project is withdrawing from the 
Kohn release.

David

--
David McBride (pronounce<https://nmdrp.me/davidmcbride>)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>



--
David McBride (pronounce<https://nmdrp.me/davidmcbride>)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>


--
David McBride (pronounce<https://nmdrp.me/davidmcbride>)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8784): https://lists.onap.org/g/onap-tsc/message/8784
Mute This Topic: https://lists.onap.org/mt/92496832/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: 
https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Modeling/etsicatalog withdraw form Kohn release

[denghui (L) via lists.onap.org]

Hi David

We (Yuanhong Deng together) want to inform you that Modeling/etsicatalog plan 
not join Kohn release, since there is no new feature update needed.
So there is only modeling/modelspec documentation left for K release.

Thanks a lot for your checking
Best regards,

DENG Hui

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
David McBride
Sent: Wednesday, July 20, 2022 3:59 AM
To: onap-tsc ; onap-release 

Cc: Catherine LEFEVRE ; Kenny Paul 

Subject: [onap-tsc] Multicloud project withdrawing from the Kohn release #kohn 
#multicloud

Team,

I was informed, yesterday, that the Multicloud project is withdrawing from the 
Kohn release.

David

--
David McBride (pronounce)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: dmcbr...@linuxfoundation.org



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8776): https://lists.onap.org/g/onap-tsc/message/8776
Mute This Topic: https://lists.onap.org/mt/92496832/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: 
https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Stepping down as ONAP MSB PTL

[denghui (L) via lists.onap.org]

Hi Huabing,

Good luck to your new career path and will come across with you in the future
Best regards,

DENG Hui

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Huabing Zhao
Sent: Wednesday, December 23, 2020 11:57 AM
To: onap-tsc 
Cc: ni.jinq...@zte.com.cn; meng.zhaoxing1 ; 
Wangchengli ; Kanagaraj Manickam 
; imacm...@gmail.com
Subject: [onap-tsc] Stepping down as ONAP MSB PTL

Dear TSC and all,

I want to let you know that I'm stepping down from the role of ONAP MSB PTL, as 
I'm pursuing a new career interest. I will continue helping in the community as 
needed to make the shift as smooth as possible until the new PTL is elected.

I recommend Nijinquan to serve as the next MSB PTL. He has been working on MSB 
for a long time, both on opensource and production. He has the most knowledge 
of this project among all the candidates.

Special thanks to Zhaoxing, Lingli, Hui, Xinhui, Chengli, and all my team for 
your tremendous help in the last 7 releases!

It's such an honor for me to work with you all. I'll never forget this 
wonderful journey in my life. Thank you with all my heart!

Regards,
Huabing Zhao



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7379): https://lists.onap.org/g/onap-tsc/message/7379
Mute This Topic: https://lists.onap.org/mt/79174310/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] SDC PTL election results

[denghui (L) via lists.onap.org]

Congratulations to Christophe for new leadership
Thanks Ofir for your work.

DENG Hui

From: onap-disc...@lists.onap.org [mailto:onap-disc...@lists.onap.org] On 
Behalf Of Ofir Sonsino
Sent: Tuesday, July 28, 2020 5:07 PM
To: onap-...@lists.onap.org; onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org; Closset, Christophe 

Subject: [onap-discuss] SDC PTL election results

All SDC committers have voted: 
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_fd54171122362463

Congratulations to Christophe Closset !

Result is now reflected at 
https://wiki.onap.org/display/DW/Voting+Results+History


Br,
Ofir

From: onap-...@lists.onap.org 
mailto:onap-...@lists.onap.org>> On Behalf Of Closset, 
Christophe
Sent: Wednesday, July 22, 2020 10:23 AM
To: onap-...@lists.onap.org; 
onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: Re: [onap-sdc] Nominations for SDC PTL are open

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Dear all,

I'd like to nominate myself for the PTL role of SDC.



Short Summary
I've been part of the ONAP community since its inception in 2017 and I've been 
involved in many aspects of it :
I'm a committer on CLAMP, integration and have been contributing changes to 
CLAMP, SO, SDC, portal, AAF, Doc, integration and a few on OOM.
I've been working in SDN for a long time (at least for the last 5years+), 
supporting AT&T teams in the open sourcing of ECOMP and I've been recently 
engaged in SDC and would be honored to push the work further.



Objective

As PTL, I want to work with the SDC team and make SDC a success for the whole 
ONAP community.


Regards
Christophe

From: onap-...@lists.onap.org 
mailto:onap-...@lists.onap.org>> On Behalf Of Sonsino, 
Ofir
Sent: Tuesday, July 21, 2020 10:23 AM
To: onap-tsc@lists.onap.org; 
onap-...@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: [onap-sdc] Nominations for SDC PTL are open

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Dear SDC committers,

Nominations for the PTL position for SDC project are open, according to the 
process described at:
https://wiki.onap.org/display/DW/Annual+Community+Elections+-+Process#AnnualCommunityElectionsProcess-PTLElections

Individuals interested in running for the PTL position should reply-all 
indicating their intention to run.
Nominations are due by 12PM UTC, July 23th.

Br,

Ofir Sonsino
Project Technical Lead, SDC
AT&T Network Application Development * NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
***
Office: +972 (3) 5451417
Mobile: +972 (52) 4377782
E-mail: ofir.sons...@intl.att.com



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

View/Reply Online (#6899): https://lists.onap.org/g/onap-tsc/message/6899
Mute This Topic: https://lists.onap.org/mt/75840434/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] FW: Result of MultiCloud PTL election in 2020

[denghui (L) via lists.onap.org]

Cong!

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Deng Yuanhong
Sent: Wednesday, July 22, 2020 10:05 AM
To: onap-tsc@lists.onap.org; bin.y...@windriver.com
Subject: Re: [onap-tsc] FW: Result of MultiCloud PTL election in 2020

Congratulations!!!

BR,
Yuanhong

From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Yang Bin
Sent: Tuesday, July 21, 2020 10:35 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] FW: Result of MultiCloud PTL election in 2020

Dear TSC,

The annual MultiCloud PTL election result is revealed 
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_dfb31346a2c03bc5, I am 
elected as PTL in 2020.

I also update the voting results history: 
https://wiki.onap.org/display/DW/Voting+Results+History

Thanks,

B.R.
Bin

From: Yang, Bin
Sent: Tuesday, July 21, 2020 10:26 AM
To: 'Sood, Ritu' mailto:ritu.s...@intel.com>>; Zhang, 
Xiaohua mailto:xiaohua.zh...@windriver.com>>; 
'Huang, Haibin' mailto:haibin.hu...@intel.com>>; 
'Xinhui Li' mailto:lxin...@vmware.com>>; '岳烈骧 
(yueliexi...@chinamobile.com)' 
mailto:yueliexi...@chinamobile.com>>; 'Multanen, 
Eric W' mailto:eric.w.multa...@intel.com>>
Subject: Result of MultiCloud PTL election in 2020

Dear committers,

The PTL election result is published at 
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_dfb31346a2c03bc5, I am 
honored to be elected as PTL in 2020.

Thank all of you for the trust and support, I will continue to do my best to 
contribute the success of  MultiCloud project.

B.R.
Bin

From: Yang, Bin
Sent: Thursday, July 16, 2020 8:50 AM
To: 'Sood, Ritu' mailto:ritu.s...@intel.com>>; Zhang, 
Xiaohua mailto:xiaohua.zh...@windriver.com>>; 
'Huang, Haibin' mailto:haibin.hu...@intel.com>>; 
'Xinhui Li' mailto:lxin...@vmware.com>>; '岳烈骧 
(yueliexi...@chinamobile.com)' 
mailto:yueliexi...@chinamobile.com>>; 'Multanen, 
Eric W' mailto:eric.w.multa...@intel.com>>
Subject: RE: civs poll for PTL vote, RE: self-nomination for MultiCloud PTL, 
RE: MultiCloud PTL election in 2020

Dear guys,

There is something wrong with civs that Xiaohua and me didn’t receive the vote 
link supposed to be sent by civs while I add voter’s emails. I just re-add the 
voter’s emails for us, and I got the link immediately.

Please let me know if you encounter the same issue so that I can try to add 
your email to civs voters again to workaround the issue.

B.R.
Bin

From: Yang, Bin
Sent: Tuesday, July 14, 2020 12:14 PM
To: Sood, Ritu mailto:ritu.s...@intel.com>>; Zhang, 
Xiaohua mailto:xiaohua.zh...@windriver.com>>; 
Huang, Haibin mailto:haibin.hu...@intel.com>>; Xinhui 
Li mailto:lxin...@vmware.com>>; 岳烈骧 
(yueliexi...@chinamobile.com) 
mailto:yueliexi...@chinamobile.com>>; Multanen, 
Eric W mailto:eric.w.multa...@intel.com>>
Subject: civs poll for PTL vote, RE: self-nomination for MultiCloud PTL, RE: 
MultiCloud PTL election in 2020

Dear committers,

By end of day July 13th 2020, I am the only one self-nominating as PTL of 
MultiVIM/Cloud project, I create civs poll and you are expected to receive a 
private civs poll link.  Please kindly cast your vote by end of July 20th 2020.

Thanks,
B.R.
Bin


From: onap-disc...@lists.onap.org 
mailto:onap-disc...@lists.onap.org>> On Behalf Of 
Yang Bin
Sent: Friday, July 10, 2020 7:58 PM
To: onap-disc...@lists.onap.org; Yang, Bin 
mailto:bin.y...@windriver.com>>; 
onap-tsc@lists.onap.org
Cc: Sood, Ritu mailto:ritu.s...@intel.com>>; Zhang, 
Xiaohua mailto:xiaohua.zh...@windriver.com>>; 
Huang, Haibin mailto:haibin.hu...@intel.com>>; Xinhui 
Li mailto:lxin...@vmware.com>>; 岳烈骧 
(yueliexi...@chinamobile.com) 
mailto:yueliexi...@chinamobile.com>>; Multanen, 
Eric W mailto:eric.w.multa...@intel.com>>
Subject: [onap-discuss] self-nomination for MultiCloud PTL, RE: MultiCloud PTL 
election in 2020

Dear Multi-VIM/Cloud committers,

I would like to nominate myself for the role of Project Technical Lead (PTL) of 
Multi-VIM/Cloud project.

I have been contributing to MultiVIM/Cloud project since its inception, I am 
very proud of being part of this team for six successful releases, I would like 
to have your continuous support to make this project a great and successful 
one. Thanks,

B.R.
Bin Yang



From: onap-disc...@lists.onap.org 
mailto:onap-disc...@lists.onap.org>> On Behalf Of 
Yang Bin
Sent: Monday, July 6, 2020 6:36 PM
To: onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Cc: Sood, Ritu mailto:ritu.s...@intel.com>>; Zhang, 
Xiaohua mailto:xiaohua.zh...@windriver.com>>; 
Huang, Haibin mailto:haibin.hu...@intel.com>>; Xinhui 
Li mailto:lxin...@vmware.com>>;

[onap-tsc] Project maturity review request for modeling project

[denghui (L) via lists.onap.org]

Dear TSC,



I'm requesting project maturity review for modeling,

the completed template can be found here 
-https://wiki.onap.org/display/DW/Project+Maturity+Review+for+Modeling



Thank you for your consideration.

DENG Hui

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

View/Reply Online (#6740): https://lists.onap.org/g/onap-tsc/message/6740
Mute This Topic: https://lists.onap.org/mt/75414513/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!!

[denghui (L)]

Hi Lingli and Eric,

For modeling part,

1)  Slicing modeling, it is more specific topic with the committed 
implementation.

2)  5G/ORAN & 3GPP standards harmonization, 
https://jira.onap.org/browse/REQ-38, It is more ORAN related ORAN RIC, 
SDN-R/CDS,

3)  For 5G / 5G Service Modeling: Modeling (exploratory) work for creating 
a 5G Service, it has been moved to lower priority according to 
https://wiki.onap.org/display/DW/ONAP+R6+Modeling+High+Level+Requirements

So I don’t see any confliction here.

Thanks a lot for your checking again
Best regards,

DENG Hui



From: Lingli Deng [mailto:denglin...@chinamobile.com]
Sent: Tuesday, October 15, 2019 6:37 AM
To: onap-tsc@lists.onap.org
Cc: 'MAYER, ANDREW J' ; denghui (L) 
Subject: 答复: [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD 
!!!

Hi Eric,

Thanks for pointing out the issues. I also believe we need to consolidate and 
differentiate usecase and modeling/functional requirements. And I have some 
good progress to report.

From the usecase perspective, according to the discussion we had in Anterwep 
hosted by Alla, we are merging the following two into a single one E2E network 
slicing usecase, and getting prepared for an architectural review next week

4)  Vertical Industry Oriented On-demand 5G Slice Service

5)  Network Slicing

From the modeling requirement perspective, I am afraid that it seems to me that 
there are internal dependencies between some of them, so high recommend to sort 
out the relation, do some consolidation and properly prioritize related 
modeling threads.

6)  Modeling: Enhanced Nested and Shared Service Information Model - 5G / 
E2E Network Slicing modeling

7)  Modeling: 5G / ORAN & 3GPP Standards Harmonization

8)  5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G 
Service

But I am not a modeling expert, so perhaps we need to do something similar as 
we did with usecase and asking the SubC co-chairs to help us out.

Lingli

发件人: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] 代表 Eric Debeau via Lists.Onap.Org
发送时间: 2019年10月14日 20:30
收件人: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
主题: Re: [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!!

Hello

There is still a lot of requirements. How do we intend to prioritize all the 
requirements ?

In addition, I believe that some requirements are overlapping:

Eg for network slicing, I can find the following requirements and it is 
difficult to commit for such requirements

9)  Modeling: Enhanced Nested and Shared Service Information Model - 5G / 
E2E Network Slicing modeling

10)   Modeling: 5G / ORAN & 3GPP Standards Harmonization

11)   5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G 
Service

12)   Vertical Industry Oriented On-demand 5G Slice Service

13)   Network Slicing

We also have various levels of description:

-Some requirements are very atomic

-Some requirements are more global (eg Network Slicing)

I also noticed that some requirements and use-cases are not listed in the right 
table

·End to End Layer 1 Service Management. Modeling the Optical Service 
should be a use –case

·Service Resolver should be a feature and not a use-case

If the requirements only impact one project (and Integration), it should be 
managed at the project level (eg Portal, DCAE/Acumos integration, …

Best Regards

Eric

De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] De la part de Catherine LEFEVRE
Envoyé : vendredi 11 octobre 2019 20:58
À : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Objet : [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!!
Importance : Haute

Dear Frankfurt « Owners »,

Thank you for submitting your use cases and your requirements for the Frankfurt 
release.
We are really excited to kick-off our Frankfurt as soon as possible
https://wiki.onap.org/display/DW/Frankfurt+Release+Requirements

The TSC is currently performing some prioritizations based on your inputs and 
EUAG inputs.

It is essential that we collect your additional inputs not later than Oct 15th, 
2019 end of your day
If we do not get them on time then we will postpone your use case/requirements 
to the Guilin Release.


•Use Case / requirements should be reviewed by the Architecture Team 
ASAP

•As you know, we are currently under capacity concerning our Testing 
activities
Therefore a new column has been added “Integration Lead” to identify per use 
case, per requirement.
The Integration Lead will have the following responsibilities:

o   Identify the testers

o   Define the Integration Test Plan for the use case or requirement

o   Develop with his/her testers the automated tests

o   Provide Test Results to the Integration Team



•Provide project’s impact f

[onap-tsc] Locked repo committers removal request

[denghui (L)]

Dear TSC,

I'd like to kindly request your review for one committer removal request for 
the repo of modeling/javatoscachecker
Because the committers decided to not any more update the repo of 
modeling/javatoscachecker, and request to removal their committers name.
https://wiki.onap.org/display/DW/Locked+repo+committers+removal+Request

Thanks a lot for your kind review
Best regards,

DENG Hui

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

View/Reply Online (#5390): https://lists.onap.org/g/onap-tsc/message/5390
Mute This Topic: https://lists.onap.org/mt/33067356/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Modeling project Committer Promotion Requests

[denghui (L)]

Dear TSC,

I'd like to kindly request your review one committer promotion request for the 
repo of modeling/genericparser
Maopeng was the original seed code contributor in genericparser/catalog  of 
VFC, now genericparser/catalog has moved to independent modeling project, 
Maopeng also contributed genericparser/catalog in modeling project.


*Maopeng Zhang, ZTE: 
https://wiki.onap.org/display/DW/Maopeng+Zhang%3A+New+Committer+Promotion+Request+for+Modeling+genericparser

Thanks and regards,

DENG Hui

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

View/Reply Online (#5358): https://lists.onap.org/g/onap-tsc/message/5358
Mute This Topic: https://lists.onap.org/mt/32965143/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Modeling project PTL election result

[denghui (L)]

Modeling Project team,

The election result is here: 
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_a2487f7146c43722
It is my pleasure to announce that I have the honor of serving another year as 
your PTL.

Thank you always for your support, I Look forward to continuing to work with 
you all

DENG Hui


From: denghui (L)
Sent: Thursday, July 25, 2019 7:28 PM
To: onap-tsc@lists.onap.org; ethanly...@vmware.com; zhang.maope...@zte.com.cn; 
'Xinhui Li' ; rj...@att.com; Lingli Deng 
; '郭楚怡' ; 
jessie.jew...@oamtechnologies.com; 'SCAGGS, KEVIN' ; Lishitao 
; yangxu (H) ; Zhaoxing 
; dengyuanhong 
Subject: RE: [onap-tsc] Call for nominations of modeling project PTL 2019-2020


Dear Modeling committers,
I would like to nominate myself to continue as PTL of modeling project.

I have served as the modeling PTL for four releases. As the PTL of modeling, I 
worked with excellent different parser teams to release different parser tools 
which include javatoscachecker, python based nfvparser, and micro-service based 
generic parser.
I am willing to continue to support the parser team to finish their work and to 
do my best to continue to contribute to ONAP.

Best Regards,

DENG Hui


From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of denghui (L)
Sent: Wednesday, July 24, 2019 7:09 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
ethanly...@vmware.com<mailto:ethanly...@vmware.com>; 
zhang.maope...@zte.com.cn<mailto:zhang.maope...@zte.com.cn>; 'Xinhui Li' 
mailto:lxin...@vmware.com>>; 
rj...@att.com<mailto:rj...@att.com>; Lingli Deng 
mailto:denglin...@chinamobile.com>>; '郭楚怡' 
mailto:guoch...@chinamobile.com>>; 
jessie.jew...@oamtechnologies.com<mailto:jessie.jew...@oamtechnologies.com>; 
'SCAGGS, KEVIN' mailto:ks0...@att.com>>; Lishitao 
mailto:lishi...@huawei.com>>; yangxu (H) 
mailto:yang...@huawei.com>>; Zhaoxing 
mailto:meng.zhaoxi...@zte.com.cn>>; dengyuanhong 
mailto:dengyuanh...@chinamobile.com>>
Subject: [onap-tsc] Call for nominations of modeling project PTL 2019-2020

Hello modeling project committers,

As required by ONAP process  
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Annual-2BCommunity-2BElections-23AnnualCommunityElections-2DPTLElections&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m=vPtAEEdY3Cj3YkEYKXUS0l74u93a0jGJm6IQ9eqzeZc&s=jHY3KX62I2qEPxb3UR-YPV8I-yZEui6_hmNlq7SfpiM&e=>,
 the annual ONAP PTL elections have started.

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 26 at 8:00 PM Beijing time.

Regards,

DENG Hui


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

View/Reply Online (#5308): https://lists.onap.org/g/onap-tsc/message/5308
Mute This Topic: https://lists.onap.org/mt/32662423/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Call for nominations of modeling project PTL 2019-2020

[denghui (L)]

Dear Modeling committers,
I would like to nominate myself to continue as PTL of modeling project.

I have served as the modeling PTL for four releases. As the PTL of modeling, I 
worked with excellent different parser teams to release different parser tools 
which include javatoscachecker, python based nfvparser, and micro-service based 
generic parser.
I am willing to continue to support the parser team to finish their work and to 
do my best to continue to contribute to ONAP.

Best Regards,

DENG Hui


From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
denghui (L)
Sent: Wednesday, July 24, 2019 7:09 PM
To: onap-tsc@lists.onap.org; ethanly...@vmware.com; zhang.maope...@zte.com.cn; 
'Xinhui Li' ; rj...@att.com; Lingli Deng 
; '郭楚怡' ; 
jessie.jew...@oamtechnologies.com; 'SCAGGS, KEVIN' ; Lishitao 
; yangxu (H) ; Zhaoxing 
; dengyuanhong 
Subject: [onap-tsc] Call for nominations of modeling project PTL 2019-2020

Hello modeling project committers,

As required by ONAP process  
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Annual-2BCommunity-2BElections-23AnnualCommunityElections-2DPTLElections&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m=vPtAEEdY3Cj3YkEYKXUS0l74u93a0jGJm6IQ9eqzeZc&s=jHY3KX62I2qEPxb3UR-YPV8I-yZEui6_hmNlq7SfpiM&e=>,
 the annual ONAP PTL elections have started.

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 26 at 8:00 PM Beijing time.

Regards,

DENG Hui


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

View/Reply Online (#5289): https://lists.onap.org/g/onap-tsc/message/5289
Mute This Topic: https://lists.onap.org/mt/32582815/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Call for nominations of modeling project PTL 2019-2020

[denghui (L)]

Hello modeling project committers,

As required by ONAP process  
https://wiki.onap.org/display/DW/Annual+Community+Elections#AnnualCommunityElections-PTLElections,
 the annual ONAP PTL elections have started.

Please reply to this email if you would like to self-nominate.  Nominations are 
due by July 26 at 8:00 PM Beijing time.

Regards,

DENG Hui
_._,_._,_


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

View/Reply Online (#5280): https://lists.onap.org/g/onap-tsc/message/5280
Mute This Topic: https://lists.onap.org/mt/32582815/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Modeling project Committer Promotion Requests

[denghui (L)]

for this repo:
onap-gerrit-modeling-genericparser-committers
dengyh  yuanhong   deng 
dengyuanh...@chinamobile.com<mailto:dengyuanh...@chinamobile.com>

I am always asking Jess for her kind help to update this,

Best regards,

DENG Hui


From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Catherine LEFEVRE
Sent: Thursday, July 11, 2019 5:00 PM
To: onap-tsc@lists.onap.org; Jim Baker 
Cc: 'Deng Yuanhong' 
Subject: Re: [onap-tsc] Modeling project Committer Promotion Requests

Thank you Deng Hui for the clarifications.

Based on your inputs, I have cleaned up the wiki page - 
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-Modeling<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DModeling&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=wB2KDlXgGTKrqb9uXGRfMY0cKzFrWPwBAZkN7rMmHSE&s=qaT5rEjoyICQjN5OXOqfD4u74VCEqwkLH2XPqbgMYS4&e=>
Please review it and let me know if any concern.

Congratulations Yuanhong !

Best regards
Catherine

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of denghui (L)
Sent: Thursday, July 11, 2019 10:33 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; Jim Baker 
mailto:jba...@linuxfoundation.org>>
Cc: 'Deng Yuanhong' 
mailto:dengyuanh...@chinamobile.com>>
Subject: Re: [onap-tsc] Modeling project Committer Promotion Requests

Hi Catherine

We have proposed to remove zero contribution early of Dublin stage.,
According to 
https://wiki.onap.org/display/DW/Zero+commit+removal+Request+and+Seperate+the+committer+for+parsers+repo<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Zero-2Bcommit-2Bremoval-2BRequest-2Band-2BSeperate-2Bthe-2Bcommitter-2Bfor-2Bparsers-2Brepo&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=wB2KDlXgGTKrqb9uXGRfMY0cKzFrWPwBAZkN7rMmHSE&s=KSLCdDAfSIli9ZcL7nfQ7Z9B0Vk2z6-MgwXSph9d3do&e=>

We have reported to TSC during the early stage of Dublin, and it haD been 
approved by TSC.

Thanks a lot for your checking
Best regards,

DENG Hui

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Catherine LEFEVRE
Sent: Thursday, July 11, 2019 4:29 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; Jim Baker 
mailto:jba...@linuxfoundation.org>>
Cc: 'Deng Yuanhong' 
mailto:dengyuanh...@chinamobile.com>>
Subject: Re: [onap-tsc] Modeling project Committer Promotion Requests

Good morning Deng Hui,

Looking at the wiki page - 
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-Modeling<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DModeling&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=wB2KDlXgGTKrqb9uXGRfMY0cKzFrWPwBAZkN7rMmHSE&s=qaT5rEjoyICQjN5OXOqfD4u74VCEqwkLH2XPqbgMYS4&e=>
There are currently a lot of committers but only 3 of them have voted.
Maybe the list of committers is no more accurate?
If it is the case then can you please update the wiki accordingly so we can 
proceed?

Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of denghui (L)
Sent: Thursday, July 11, 2019 9:03 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; Jim Baker 
mailto:jba...@linuxfoundation.org>>; Lefevre, 
Catherine 
mailto:catherine.lefe...@intl.att.com>>
Cc: 'Deng Yuanhong' 
mailto:dengyuanh...@chinamobile.com>>
Subject: [onap-tsc] Modeling project Committer Promotion Requests

Dear TSC,

I'd like to kindly ask you to review the one committer promotion request for 
one repo of modeling/genericparser

*Yuanhong Deng,  China Mobile - 
https://wiki.onap.org/display/DW/New+Committer+Promotion+Request+for+Modeling+genericparser<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_New-2BCommitter-2BPromotion-2BRequest-2Bfor-2BModeling-2Bgenericparser&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=X7c3218itmzUga3D93ALb0EyR7vaSzGzGr8rpijVVyw&s=0yuvcgfrYg2_1rfnP_iTsHyOyH69gj4GHu-EeJeOVK4&e=>

Thanks and regards,

DENG Hui


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

View/Reply Online (#5222): https://lists.onap.org/g/onap-tsc/message/5222
Mute This Topic: https://lists.onap.org/mt/32427797/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Modeling project Committer Promotion Requests

[denghui (L)]

Hi Catherine

We have proposed to remove zero contribution early of Dublin stage.,
According to 
https://wiki.onap.org/display/DW/Zero+commit+removal+Request+and+Seperate+the+committer+for+parsers+repo

We have reported to TSC during the early stage of Dublin, and it haD been 
approved by TSC.

Thanks a lot for your checking
Best regards,

DENG Hui

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Catherine LEFEVRE
Sent: Thursday, July 11, 2019 4:29 PM
To: onap-tsc@lists.onap.org; Jim Baker 
Cc: 'Deng Yuanhong' 
Subject: Re: [onap-tsc] Modeling project Committer Promotion Requests

Good morning Deng Hui,

Looking at the wiki page - 
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-Modeling
There are currently a lot of committers but only 3 of them have voted.
Maybe the list of committers is no more accurate?
If it is the case then can you please update the wiki accordingly so we can 
proceed?

Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of denghui (L)
Sent: Thursday, July 11, 2019 9:03 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; Jim Baker 
mailto:jba...@linuxfoundation.org>>; Lefevre, 
Catherine 
mailto:catherine.lefe...@intl.att.com>>
Cc: 'Deng Yuanhong' 
mailto:dengyuanh...@chinamobile.com>>
Subject: [onap-tsc] Modeling project Committer Promotion Requests

Dear TSC,

I'd like to kindly ask you to review the one committer promotion request for 
one repo of modeling/genericparser

*Yuanhong Deng,  China Mobile - 
https://wiki.onap.org/display/DW/New+Committer+Promotion+Request+for+Modeling+genericparser<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_New-2BCommitter-2BPromotion-2BRequest-2Bfor-2BModeling-2Bgenericparser&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=X7c3218itmzUga3D93ALb0EyR7vaSzGzGr8rpijVVyw&s=0yuvcgfrYg2_1rfnP_iTsHyOyH69gj4GHu-EeJeOVK4&e=>

Thanks and regards,

DENG Hui


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

View/Reply Online (#5220): https://lists.onap.org/g/onap-tsc/message/5220
Mute This Topic: https://lists.onap.org/mt/32427797/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Modeling project Committer Promotion Requests

[denghui (L)]

Dear TSC,

I'd like to kindly ask you to review the one committer promotion request for 
one repo of modeling/genericparser

*Yuanhong Deng,  China Mobile - 
https://wiki.onap.org/display/DW/New+Committer+Promotion+Request+for+Modeling+genericparser

Thanks and regards,

DENG Hui

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

View/Reply Online (#5217): https://lists.onap.org/g/onap-tsc/message/5217
Mute This Topic: https://lists.onap.org/mt/32427797/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] URGENT - ONAP Dublin - Remaining Activities

[denghui (L)]

Hi Catherine,

Maopeng has worked it out  and update it now:
https://docs.onap.org/en/dublin/submodules/modeling/toscaparsers.git/docs/nfvparser/release-notes/release-notes.html#modeling-nfv-parser-release-notes

I will close jira ticket asap

Thanks a lot

DENG Hui

From: denghui (L)
Sent: Tuesday, June 25, 2019 5:29 PM
To: onap-tsc@lists.onap.org; onap-rele...@lists.onap.org
Cc: zhang.maope...@zte.com.cn; 'shang.xiaod...@zte.com.cn' 
; Sofia Wallin 
Subject: RE: URGENT - ONAP Dublin - Remaining Activities

Hi Catherine,

Modeling project currently have 4 repos:

1)  Modeling/genericparser

2)  Modeling/javatoscachecker  readonly

3)  Modeling/modelspec

4)  Modeling/toscaparsers

Currently 1,3 have already updated their release notes. And the contributors 
(cc here) of 4  think that they don't have any update in Dublin  release,  so 
don't need to update their release note.

Could you kindly help to advice how we should proceed this?

Thanks a lot for your kind help
Best regards,

DENG hui

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Catherine LEFEVRE
Sent: Tuesday, June 25, 2019 5:02 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>
Subject: [onap-tsc] URGENT - ONAP Dublin - Remaining Activities
Importance: High

Good morning All,

In order to finalize the ONAP Dublin release, we still need to fix the 
following items :
[cid:image001.jpg@01D52C13.E02D65D0]

Can I ask the assignees to fix these documentations issues today (Tuesday June 
25th) so we can ask the TSC to sign-off the release?

Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT&T Labs - Network Cloud & Infrastructure
D2 Platform & Systems Development
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair


Phone: +32 81 84 09 08
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com<mailto:catherine.lefe...@intl.att.com>

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above



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

View/Reply Online (#5150): https://lists.onap.org/g/onap-tsc/message/5150
Mute This Topic: https://lists.onap.org/mt/32201527/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] URGENT - ONAP Dublin - Remaining Activities

[denghui (L)]

Hi Catherine,

Modeling project currently have 4 repos:

1)  Modeling/genericparser

2)  Modeling/javatoscachecker  readonly

3)  Modeling/modelspec

4)  Modeling/toscaparsers

Currently 1,3 have already updated their release notes. And the contributors 
(cc here) of 4  think that they don't have any update in Dublin  release,  so 
don't need to update their release note.

Could you kindly help to advice how we should proceed this?

Thanks a lot for your kind help
Best regards,

DENG hui

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Catherine LEFEVRE
Sent: Tuesday, June 25, 2019 5:02 PM
To: onap-tsc@lists.onap.org; onap-rele...@lists.onap.org
Subject: [onap-tsc] URGENT - ONAP Dublin - Remaining Activities
Importance: High

Good morning All,

In order to finalize the ONAP Dublin release, we still need to fix the 
following items :
[cid:image002.jpg@01D52B7B.4E2384A0]

Can I ask the assignees to fix these documentations issues today (Tuesday June 
25th) so we can ask the TSC to sign-off the release?

Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT&T Labs - Network Cloud & Infrastructure
D2 Platform & Systems Development
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair


Phone: +32 81 84 09 08
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above



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

View/Reply Online (#5143): https://lists.onap.org/g/onap-tsc/message/5143
Mute This Topic: https://lists.onap.org/mt/32201527/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [onap-discuss] Community Coordinators - CALL FOR SELF NOMINATIONS - Ends May 9, 5 PM Pacific

[denghui (L)]

Dear TSC,

I would like to humbly self-nominate myself for the "Network Management" 
Community Coordinator position.

Candidate Name:
*@Hui Deng, denghu...@huawei.com

Company:
*Huawei

Head-shot picture:
[image003.jpg]
Position:
*"Network Management" Community Coordinator

Biography:
*Hui DENG obtained his Doctor degree from Dept. Computer Science and 
Technology at Tsinghua University in 2002. He worked as Principal staff between 
2007 and 2016 in China Mobile. He joined Huawei and is the director of 5G 
Core/MEC/NFV related standard and opensource. He acted as the co-chair of IETF 
MIF working group. And he was the board of director of WBA(Wireless Broadband 
Alliance) between 2012-2014, acted as the board of director of OPNFV between 
2014-2016 and 1st board of chairman of OPEN-O project in Linux Foundation. He 
was the SDO coordinator, co-chair of modeling subcommittee in ONAP between 
2017-2019..

Candidate's Statement:

As the ex-SDO coordinator, we have organized 4 times Multi-SDO ONAP workshop 
before:

External SDOs session in Developer event in 
September

External SDO session in ONAP Forum Dec. 12th, 
2017

Jan 2019 ONAP DDF OPNFV Plugfest 
SDO

Apr. 2019 ONAP M-SDOs 
workshop
Based on my past experience of network management , I am willing to continue to 
help on those topics, and bring the connections between ONAP with those 
SDOs/Opensources...

Thanks a lot

DENG Hui

From: onap-disc...@lists.onap.org 
mailto:onap-disc...@lists.onap.org>> On Behalf Of 
Kenny Paul via Lists.Onap.Org
Sent: Thursday, May 2, 2019 4:57 PM
To: onap-tsc@lists.onap.org
Subject: [onap-discuss] Community Coordinators - CALL FOR SELF NOMINATIONS - 
Ends May 9, 5 PM Pacific

(bcc'd to onap-discuss)

There are currently six Community Coordinator positions open. These positions 
are open to anyone.

  *   
Infrastructure
  *   
AI(ML/DL)
  *   
5G
  *   Cloud 
Native
  *   Edge 
Computing
  *   Network 
Management

Who is eligible to Run: Any Community Member

Who is eligible to Vote: TSC Members

Process:

Self-Nomination Phase
Individuals interested in running for a particular Community Coordinator 
position must reply-all to this email with the specific coordinator position 
you are running for.  Candidates are strongly recommended to include a 
hea

Re: [onap-tsc] Proposed Dublin Architecture Slides

[denghui (L)]

Hi Steve

Agree with your suggestion, this micro-service based TOSCA parser does provide 
the service which is used “IN” VFC and UUI.

Thanks a lot

DENG Hui

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Thursday, April 18, 2019 9:10 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Deng,

Then we could consider to put a TOSCA Parser as a common service.  I don’t 
think that the implementation consideration of whether it’s a mocroservice or 
not influences whether its is considered a commont service (that is the tail 
wagging the dog) or the common library from a *functional* perspective.  The 
consideration is whether it is considered to provide a function (functionality) 
serving other functions, or whether it provides something that is used “IN” 
other functions at this level.

BR,

Steve

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of denghui 
(L)
Sent: Thursday 18 April 2019 14:18
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve

Yang yan’s team is working on micro service based parser in R4 which will be 
used by VFC and UUI,
so maybe it have to  belong to both common library (NFV Parser from 
OPNFV/Openstack) and Common services.( Micro service based)

Thanks a lot for your reminder
Best regards,

DENG Hui

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Stephen Terrill
Sent: Thursday, April 18, 2019 8:13 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Deng,

Modelling is the common libraries to capture it there, could you expand on why 
you feel it should be in the common services instead of the common library?

BR,

Steve

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of denghui 
(L)
Sent: Thursday 18 April 2019 05:13
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve

Could you kindly help to add “Modeling” into the “Common Services” of Dublin 
Architecture diagram.
Thanks a lot for  your help

DENG Hui

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Shankar Narayanan
Sent: Thursday, April 18, 2019 1:05 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Can you please replace the description of OOF with the following, which also 
provides an intuition on the flavors of optimizations that can be supported by 
OOF.

Provides a growing set of core platform optimization services like, 
VNF/PNF/Service placement (HAS), SON optimization (PCI/ANR), Change Scheduling 
(CMSO) etc. OOF platform enables a model-driven approach to creation of new 
optimization services with minimal or little new code development.

Thanks,
Shankar.
--
Shankaranarayanan Puzhavakath Narayanan
Senior Inventive Scientist
Network and Cloud Systems Research
AT&T Labs Research


On Wed, Apr 17, 2019 at 11:41 AM Mandar Sawant 
mailto:ms5...@att.com>> wrote:
Hi Steve,

DMaaP is missing in the description slides.

Here’s the description from one of the previous ppt:

Data movement as a platform (DMaaP) is a premier platform for high performing 
and cost effective data movement services that transports and processes data 
from any source to any target with the format, quality, security, and 
concurrency required to serve the business and customer needs.

Thanks,
Mandar

AT&T Proprietary (Internal Use Only)
Not for use or disclosure outside the AT&T companies except under written 
agreement

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Andreas 
Geissler
Sent: Wednesday, April 17, 2019 2:52 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Cc: adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>; MALAKOV, YURIY 
mailto:ym9...@att.com>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Just some short corrections and question:

  *   Slide 5: missing “c” in lifecyle
  *   Slide 7 SDNC:
In the Note should it be “In Dublin, CDS is a standalone …” and shouldn’t this 
be a note for SDC (Alexis, Yuriy?) ?

Best regards
Andreas

Von: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> Im Auftrag von 
Stephen Terrill
Gesendet: Mittwoch, 17. April 2019 09:21
An: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Betreff: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Eric,

Re: [onap-tsc] Proposed Dublin Architecture Slides

[denghui (L)]

Hi Steve

Yang yan’s team is working on micro service based parser in R4 which will be 
used by VFC and UUI,
so maybe it have to  belong to both common library (NFV Parser from 
OPNFV/Openstack) and Common services.( Micro service based)

Thanks a lot for your reminder
Best regards,

DENG Hui

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Thursday, April 18, 2019 8:13 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Deng,

Modelling is the common libraries to capture it there, could you expand on why 
you feel it should be in the common services instead of the common library?

BR,

Steve

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of denghui 
(L)
Sent: Thursday 18 April 2019 05:13
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve

Could you kindly help to add “Modeling” into the “Common Services” of Dublin 
Architecture diagram.
Thanks a lot for  your help

DENG Hui

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Shankar Narayanan
Sent: Thursday, April 18, 2019 1:05 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Can you please replace the description of OOF with the following, which also 
provides an intuition on the flavors of optimizations that can be supported by 
OOF.

Provides a growing set of core platform optimization services like, 
VNF/PNF/Service placement (HAS), SON optimization (PCI/ANR), Change Scheduling 
(CMSO) etc. OOF platform enables a model-driven approach to creation of new 
optimization services with minimal or little new code development.

Thanks,
Shankar.
--
Shankaranarayanan Puzhavakath Narayanan
Senior Inventive Scientist
Network and Cloud Systems Research
AT&T Labs Research


On Wed, Apr 17, 2019 at 11:41 AM Mandar Sawant 
mailto:ms5...@att.com>> wrote:
Hi Steve,

DMaaP is missing in the description slides.

Here’s the description from one of the previous ppt:

Data movement as a platform (DMaaP) is a premier platform for high performing 
and cost effective data movement services that transports and processes data 
from any source to any target with the format, quality, security, and 
concurrency required to serve the business and customer needs.

Thanks,
Mandar

AT&T Proprietary (Internal Use Only)
Not for use or disclosure outside the AT&T companies except under written 
agreement

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Andreas 
Geissler
Sent: Wednesday, April 17, 2019 2:52 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Cc: adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>; MALAKOV, YURIY 
mailto:ym9...@att.com>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Just some short corrections and question:

  *   Slide 5: missing “c” in lifecyle
  *   Slide 7 SDNC:
In the Note should it be “In Dublin, CDS is a standalone …” and shouldn’t this 
be a note for SDC (Alexis, Yuriy?) ?

Best regards
Andreas

Von: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> Im Auftrag von 
Stephen Terrill
Gesendet: Mittwoch, 17. April 2019 09:21
An: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Betreff: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Eric,

Thanks for the feedback.

  *   POMBA and MUSIC are explained in slides 5-9.  If you mean expand it on 
the main slide – its more a slide real-estate limitation at the moment.

Regarding the colors.  The discussion that we had around them was to have the 
network interacting functions at the bottom and one color and the other 
(runtime) parts another color.  This could be changed of course, but then I 
would like more views as it would be going back on the conversation that we had 
in ArchCom.

BR,

Steve

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Eric 
Debeau
Sent: Wednesday 17 April 2019 08:45
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Stephen,

I believe that we should explain what POMBA and MUSIC are.

For color code, why Holmes is not as the same color as  DCAE ?

I would propose that we use the same color code in ONAP project for 
documentation and any other material

Blue for Design Time
Green for Run Time

  *   Dark Green for controller
  *   Light Green for Common Services

Exact color code should be based on the one used for the PPT template.

Best Regards

Eric

De : onap-tsc@lis

Re: [onap-tsc] Proposed Dublin Architecture Slides

[denghui (L)]

Hi Steve

Could you kindly help to add “Modeling” into the “Common Services” of Dublin 
Architecture diagram.
Thanks a lot for  your help

DENG Hui

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Shankar Narayanan
Sent: Thursday, April 18, 2019 1:05 AM
To: onap-tsc 
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Can you please replace the description of OOF with the following, which also 
provides an intuition on the flavors of optimizations that can be supported by 
OOF.

Provides a growing set of core platform optimization services like, 
VNF/PNF/Service placement (HAS), SON optimization (PCI/ANR), Change Scheduling 
(CMSO) etc. OOF platform enables a model-driven approach to creation of new 
optimization services with minimal or little new code development.

Thanks,
Shankar.
--
Shankaranarayanan Puzhavakath Narayanan
Senior Inventive Scientist
Network and Cloud Systems Research
AT&T Labs Research


On Wed, Apr 17, 2019 at 11:41 AM Mandar Sawant 
mailto:ms5...@att.com>> wrote:
Hi Steve,

DMaaP is missing in the description slides.

Here’s the description from one of the previous ppt:

Data movement as a platform (DMaaP) is a premier platform for high performing 
and cost effective data movement services that transports and processes data 
from any source to any target with the format, quality, security, and 
concurrency required to serve the business and customer needs.

Thanks,
Mandar

AT&T Proprietary (Internal Use Only)
Not for use or disclosure outside the AT&T companies except under written 
agreement

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Andreas 
Geissler
Sent: Wednesday, April 17, 2019 2:52 AM
To: onap-tsc@lists.onap.org
Cc: adetalhoue...@gmail.com; MALAKOV, YURIY 
mailto:ym9...@att.com>>
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Steve,

Just some short corrections and question:

  *   Slide 5: missing “c” in lifecyle
  *   Slide 7 SDNC:
In the Note should it be “In Dublin, CDS is a standalone …” and shouldn’t this 
be a note for SDC (Alexis, Yuriy?) ?

Best regards
Andreas

Von: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> Im Auftrag von 
Stephen Terrill
Gesendet: Mittwoch, 17. April 2019 09:21
An: onap-tsc@lists.onap.org
Betreff: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Eric,

Thanks for the feedback.

  *   POMBA and MUSIC are explained in slides 5-9.  If you mean expand it on 
the main slide – its more a slide real-estate limitation at the moment.

Regarding the colors.  The discussion that we had around them was to have the 
network interacting functions at the bottom and one color and the other 
(runtime) parts another color.  This could be changed of course, but then I 
would like more views as it would be going back on the conversation that we had 
in ArchCom.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Eric 
Debeau
Sent: Wednesday 17 April 2019 08:45
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi Stephen,

I believe that we should explain what POMBA and MUSIC are.

For color code, why Holmes is not as the same color as  DCAE ?

I would propose that we use the same color code in ONAP project for 
documentation and any other material

Blue for Design Time
Green for Run Time

  *   Dark Green for controller
  *   Light Green for Common Services

Exact color code should be based on the one used for the PPT template.

Best Regards

Eric

De : onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] De la part de Stephen Terrill
Envoyé : mercredi 17 avril 2019 08:31
À : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi,

Please find an update incorporating updated text on the DCAE definition from 
Vijay.

Best Regards,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill
Sent: Tuesday 16 April 2019 23:39
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi All,

I missed a comment from Amy, please look at this version instead.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill
Sent: Tuesday 16 April 2019 23:23
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi All,

Thanks for the feedback, the good catches and comments are appreciated.

@Dan, I have added the note
@Ofir, @Seshu

[onap-tsc] Zero commit removal Request and Seperate the committer for parsers repo of Modeling project

[denghui (L)]

Dear TSC and the communities,

In order to avoid the future risk, we will separate java based parser, python 
based parser, and microservice based parser into 3 different repos.
Modeling project current have below 4 repos:

modeling/

modeling/modelspec

modeling/javatoscachecker

modeling/toscaparsers

modeling/genericparser



In this case, we will

https://wiki.onap.org/display/DW/Zero+commit+removal+Request+and+Seperate+the+committer+for+parsers+repo



1) move the committers of javatoscachecker to its new repo javatoscachecker:

rjana


Rittwik


Jana


rj...@att.com


serbanjora


Serban


Jora


sj2...@att.com


2) python based parser committers will be kept and

Zhaoxing


Zhaoxing


Meng


meng.zhaoxi...@zte.com.cn


maopengzhang


maopeng


zhang


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


remove all other committers of toscaparsers repo

AmirLevy


Amir


Levy


a...@cloudify.co


rjana


Rittwik


Jana


rj...@att.com


serbanjora


Serban


Jora


sj2...@att.com


3) remove zero committer from modeling/ based on request from Linux Foundation, 
below are info provided by Linux Foundation

Repo


Name


email


# com


onap-gerrit-modeling-committers


Alexander Vul


alex@intel.com


0


onap-gerrit-modeling-committers


dong hu


don...@raisecom.com


0


onap-gerrit-modeling-committers


Amir Levy


a...@cloudify.co


0


onap-gerrit-modeling-committers


Andrei Kojukhov


andr...@amdocs.com


0


onap-gerrit-modeling-committers


Sandeep Shah


sandeep.sh...@techmahindra.com


0


onap-gerrit-modeling-committers


shitao li


lishi...@huawei.com


0


onap-gerrit-modeling-committers


Rittwik Jana


rj...@att.com


0


Thanks a lot for your checking
Best regards,

DENG Hui

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

View/Reply Online (#4639): https://lists.onap.org/g/onap-tsc/message/4639
Mute This Topic: https://lists.onap.org/mt/29915453/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Collecting related issues for M-SDOs workshop in ONS 2019

[denghui (L)]

Dear community members/PTL/committees/task forces

Based on last week F2F discussion, in order to host an efficient ONAP/M-SDO 
workshop in ONS 2019, we are collecting the input issues from the community 
(projects/committee/task force) before end of January.
After collecting those issues, we will send dedicated topic to related SDO, let 
them help ONAP to resolve those issue during the workshop specifically.

https://wiki.onap.org/display/DW/Collect+issues+in+ONAP+related+to+M-SDOs

Deadline is Jan. 31st eastern time.

thanks a lot for your help
Best regards,

DENG Hui

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

View/Reply Online (#4531): https://lists.onap.org/g/onap-tsc/message/4531
Mute This Topic: https://lists.onap.org/mt/29570750/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Call for SDOs related issues before ONS M-SDOs workshop

[denghui (L)]

Dear community members/PTL/committees/task forces

Based on last week F2F discussion, in order to host an efficient ONAP/M-SDO 
workshop in ONS 2019, we are collecting the input issues from the community 
(projects/committee/task force) before end of January.
After collecting those issues, we will send dedicated topic to related SDO, let 
them help ONAP to resolve those issue during the workshop specifically.

Please fill in below wiki page before Jan. 31st eastern time.
https://wiki.onap.org/display/DW/Collect+issues+in+ONAP+related+to+M-SDOs

thanks a lot for your help
Best regards,

DENG Hui

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

View/Reply Online (#4477): https://lists.onap.org/g/onap-tsc/message/4477
Mute This Topic: https://lists.onap.org/mt/29145655/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Remove inactive modelspec committers in modeling project

[denghui (L)]

Dear TSC and Release manager,

We request to remove inactive committers in modelspec repo of modeling project 
, they have zero commit in 2018

1)  Dong Hu,

2)  Han Yanan

3)  Rittwik Jana

4)  Sandeep Shah

5)  Zhaoxing Meng

6)  Zhong Heliu
Thanks a lot for your help
Best regards,

DENG Hui & Andy

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

View/Reply Online (#4450): https://lists.onap.org/g/onap-tsc/message/4450
Mute This Topic: https://lists.onap.org/mt/29006694/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] ONAP/OSM topic to TSC

[denghui (L)]

Hi Catherine,

Speaking for SDO coordinator, from today M-SDO slot, we have one presentation 
about ONAP/OSM Harmonization made from Amdocs.
There were comments from audience that it should be discussed in TSC level, so 
I am forwarding this request to TSC here for you to consider including this 
into future TSC meeting.

The link of presentation is here:
https://wiki.onap.org/download/attachments/48533526/ONAP_OSM_Harmonization_Status.pptx?api=v2

Thanks a lot for your consideration
Best regards,

DENG Hui

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

View/Reply Online (#4433): https://lists.onap.org/g/onap-tsc/message/4433
Mute This Topic: https://lists.onap.org/mt/28985837/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] SDO‘s Report this afternoon

[denghui (L)]

Here it goes: 
https://nokiameetings.webex.com/nokiameetings/j.php?MTID=m44a810d526a289be6cc5b96eb2a8cd78
4:30pm Paris time

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of Li
Sent: Wednesday, January 9, 2019 3:46 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] SDO‘s Report this afternoon

Hi Deng Hui,


When is this meeting (time), do you have a zoom link for remote joining?

Pls let me know,

Thanks,
-Lm,


From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of denghui (L)
Sent: Wednesday, January 9, 2019 8:33 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Cc: MAYER, ANDREW J mailto:am8...@att.com>>; Nguyenphu, Thinh 
(Nokia - US/Irving) 
mailto:thinh.nguyen...@nokia.com>>; Andrei Kojukhov 
mailto:andrei.kojuk...@amdocs.com>>
Subject: [External][onap-tsc] SDO‘s Report this afternoon


The e-mail below is from an external source. Please do not open attachments or 
click links from an unknown or suspicious origin.

Hello all

We are going to have M-SDO report to ONAP as below agenda this afternoon 4:30pm 
in plenary room: 
Ritchie<https://ddfplugfest19.sched.com/venue/Ritchie+%28200%29>:
https://wiki.onap.org/display/DW/Jan+2019+ONAP+DDF+OPNFV+Plugfest+SDO

Please each presenter to upload your slide in advance, thanks


Agenda:

1) TMF/MEF, Andy

2) ETSI NFV, Thinh

3) ONAP/OSM, Andrei

4) 20190402 Multi-SDO/ZSM/ONAP/OSM workshop call for topics

Feel free to attend , thanks a lot

DENG Hui

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s), are confidential and may be 
privileged. If you are not the intended recipient, you are hereby notified that 
any review, re-transmission, conversion to hard copy, copying, circulation or 
other use of this message and any attachments is strictly prohibited. If you 
are not the intended recipient, please notify the sender immediately by return 
email and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. The company cannot accept responsibility 
for any loss or damage arising from the use of this email or attachment."


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

View/Reply Online (#4431): https://lists.onap.org/g/onap-tsc/message/4431
Mute This Topic: https://lists.onap.org/mt/28984591/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] SDO‘s Report this afternoon

[denghui (L)]

Hello all

We are going to have M-SDO report to ONAP as below agenda this afternoon 4:30pm 
in plenary room: 
Ritchie:
https://wiki.onap.org/display/DW/Jan+2019+ONAP+DDF+OPNFV+Plugfest+SDO

Please each presenter to upload your slide in advance, thanks


Agenda:

1) TMF/MEF, Andy

2) ETSI NFV, Thinh

3) ONAP/OSM, Andrei

4) 20190402 Multi-SDO/ZSM/ONAP/OSM workshop call for topics

Feel free to attend , thanks a lot

DENG Hui

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

View/Reply Online (#4429): https://lists.onap.org/g/onap-tsc/message/4429
Mute This Topic: https://lists.onap.org/mt/28984591/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] ONAP Subcommittee meetings just prior to ONS N.A.

[denghui (L)]

Hi all

I think that it is quite useful to have this joint meeting, probably we could 
have a joint 2 hours session  on Monday morning across Architecture/Use 
Case/Modeling subcommittee for common topics. Later we could have parallel 
sessions of each subcommittee.

By the way, we are considering to have one day Multi-SDO workshop on Tuesday, 
if we allocate modeling subcommittee to Monday, that won’t be any confliction.

Thanks a lot

DENG Hui

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Phil Robb
Sent: Tuesday, January 8, 2019 4:04 PM
To: onap-tsc 
Subject: [onap-tsc] ONAP Subcommittee meetings just prior to ONS N.A.

Hello ONAP TSC:

Given the timing, attendance and success of the Architecture and Modeling 
subcommittee meetings in Montreal last year, we've been thinking that repeating 
such a meeting co-located with ONS (spring in the Bay area of U.S.A., and fall 
in Antwerp, Belgium) this year would be worthwhile.  The timing of these 
meetings will allow subcommittees such as Architecture, Modeling, Use Case, 
etc. to come together to perform the needed pre-work for the El Alto (E) 
release of ONAP.

To prepare for such a meeting at ONS U.S., we will target the 2 days prior to 
the ONS event (Monday & Tuesday, April 1st and 2nd).  I would like to hear from 
Subcommittee Chairpersons on if your group would like to hold a meeting at that 
time.  Please respond to this thread at your earliest opportunity if you would 
like us to find a space for you and please let us know how many people you 
would expect to attend so that we can plan the event accordingly.

Thanks,

Phil.
--
Phil Robb
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb


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

View/Reply Online (#4420): https://lists.onap.org/g/onap-tsc/message/4420
Mute This Topic: https://lists.onap.org/mt/28974089/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Call every night this week

[denghui (L)]

Hello all

I suddenly find out that we still have TSC call tonight, for people who from 
china, we have the call every night from Monday to Thursday this week, from 
9pm-12am.
Maybe this time is fine for European people an Eastern Coast, but it is really 
not good for Chinese who have the family.

I am suggesting to not do this again.

Thanks a lot

DENG Hui

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

View/Reply Online (#4337): https://lists.onap.org/g/onap-tsc/message/4337
Mute This Topic: https://lists.onap.org/mt/28742736/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Need Your Input: El Alto Release DDF the Week of June 10, 2018? #lfn

[denghui (L)]

Just want to mention June 6-9, it’s the dragon boat festival in China,
If we can start earliest from 11th  that will be convenient for those who need 
to do boat racing/rowing competition ☺

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Thursday, December 6, 2018 1:39 AM
To: ONAP-TSC ; onap-rele...@lists.onap.org
Cc: Phil Robb ; Heather Kirksey 
; Brandon Wick ; David 
McBride 
Subject: [onap-tsc] Need Your Input: El Alto Release DDF the Week of June 10, 
2018? #lfn

Based upon the challenges with the Dublin Developer Forum, we are trying to 
plan now for the El Alto DDF.  This will be another joint event with the OPNFV 
Plugfest.

The OPNFV folks are proposing the week of June 10, 2019 which to me seems like 
a good choice.  We are (tentatively) scheduled to drop Dublin on May 23rd based 
upon the proposed schedule and David McBride has cross checked the dates for 
major events and major international holidays that he is aware of. There don't 
seen any conflicts.

Let me know your thoughts or a simple +1, 0 -1.

…And no, a location has not been nailed down yet. :-)


Best Regards,
-kenny

Kenny Paul, Technical Program Manager, The Linux Foundation
kp...@linuxfoundation.org, 510.766.5945
San Francisco Bay Area, Pacific Time Zone




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

View/Reply Online (#4265): https://lists.onap.org/g/onap-tsc/message/4265
Mute This Topic: https://lists.onap.org/mt/28621196/21656
Mute #lfn: https://lists.onap.org/mk?hashtag=lfn&subid=2743226
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Dublin release participation - modeling

[denghui (L)]

Dear TSC,

This is to inform you that the modeling project intends to participate in the 
Dublin release.


BR,
DENG Hui


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

View/Reply Online (#4224): https://lists.onap.org/g/onap-tsc/message/4224
Mute This Topic: https://lists.onap.org/mt/28569882/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [onap-discuss] SDC Update

[denghui (L)]

Same here, definitely will miss u.

Best regards,

DENG Hui

From: onap-disc...@lists.onap.org [mailto:onap-disc...@lists.onap.org] On 
Behalf Of Chaker Al Hakim
Sent: Monday, December 3, 2018 2:04 AM
To: onap-...@lists.onap.org; ONAP-TSC@lists.onap.org
Cc: onap-disc...@lists.onap.org; Merkado, Tomer ; 
Nachmias, Lior ; Sonsino, Ofir 
; Gitelman, Tal ; 
Shlosberg, Yuli ; Amit, Idan 
; EMPOROPULO, VITALIY ; 
Avi Gaffa ; oren...@amdocs.com; WEISS KEIDAR, EINAV 
; halfon@amdocs.com; Lefevre, Catherine 
; micla...@gmail.com
Subject: Re: [onap-discuss] SDC Update

Hi Michael,

I wish you all the best in your new endeavor . You will be missed.

All the best,
Chaker


From: onap-...@lists.onap.org 
[mailto:onap-...@lists.onap.org] On Behalf Of Michael Lando
Sent: Thursday, November 29, 2018 6:53 PM
To: ONAP-TSC@lists.onap.org
Cc: 'onap-...@lists.onap.org' 
mailto:onap-...@lists.onap.org>>; 
onap-disc...@lists.onap.org; Merkado, Tomer 
mailto:tomer.merk...@intl.att.com>>; Nachmias, Lior 
mailto:lior.nachm...@intl.att.com>>; Sonsino, Ofir 
mailto:ofir.sons...@intl.att.com>>; Gitelman, Tal 
mailto:tal.gitel...@intl.att.com>>; Shlosberg, Yuli 
mailto:yuli.shlosb...@intl.att.com>>; Amit, Idan 
mailto:idan.a...@intl.att.com>>; EMPOROPULO, VITALIY 
mailto:vitaliy.emporop...@amdocs.com>>; Avi 
Gaffa mailto:avraham.ga...@amdocs.com>>; 
oren...@amdocs.com; WEISS KEIDAR, EINAV 
mailto:einav.we...@amdocs.com>>; 
halfon@amdocs.com; Lefevre, Catherine 
mailto:catherine.lefe...@intl.att.com>>; 
micla...@gmail.com
Subject: [onap-sdc] SDC Update

Hello,

I Would like to submit my resignation from the PTL position in SDC,
As I am leaving my compony I will no Longer be able to participate in the 
Project.

The committers for SDC are already aware of this change.

With this notification I would also like to open the nominations to replace me 
as the SDC PTL.









BR,

[Michael Lando]

AT&T Network Application Development * NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
***
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com



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

View/Reply Online (#4223): https://lists.onap.org/g/onap-tsc/message/4223
Mute This Topic: https://lists.onap.org/mt/28569180/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] #architecture #modeling summary from Montreal

[denghui (L)]

Done, sorry for forgetting this,

DENG Hui

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Eric Debeau
Sent: Monday, November 19, 2018 10:23 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] #architecture #modeling summary from Montreal

Hi Stephen, Hui and Andy

Can you share the presentation you did during the last TSC meeting about the 
Montreal event ?

Thanks

Best Regards

Eric

_



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.


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

View/Reply Online (#4134): https://lists.onap.org/g/onap-tsc/message/4134
Mute This Topic: https://lists.onap.org/mt/28241703/21656
Mute #modeling: https://lists.onap.org/mk?hashtag=modeling&subid=2743226
Mute #architecture: https://lists.onap.org/mk?hashtag=architecture&subid=2743226
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [Onap-arc] [onap-tsc] F2F meeting - Architecture/modelling - Dublin Release focus

[denghui (L)]

Agree, Look at the current attendee list on the wiki page, only 1 people will 
leave right after 2 days, all of others will stay for 2.5 days.
probably, we need to reach asap to checkto whether he is considering to 
reschedule the trip.

Thanks

DENG Hui

From: onap-...@lists.onap.org [mailto:onap-...@lists.onap.org] On Behalf Of 
Jason Hunt
Sent: Wednesday, October 10, 2018 4:30 AM
To: onap-tsc@lists.onap.org
Cc: onap-...@lists.onap.org
Subject: Re: [Onap-arc] [onap-tsc] F2F meeting - Architecture/modelling - 
Dublin Release focus

Steve,

My only question on merging the tracks is if any architecture subcommittee 
members already planned on a 2 day meeting, since that was what was 
communicated originally.  The 1/2 day was an add-on.


Regards,
Jason Hunt
Distinguished Engineer, IBM

Phone: 314-749-7422
Email: djh...@us.ibm.com
Twitter: @DJHunt




From:"Stephen Terrill" 
mailto:stephen.terr...@ericsson.com>>
To:"onap-...@lists.onap.org" 
mailto:onap-...@lists.onap.org>>, 
"ONAP-TSC@lists.onap.org" 
mailto:ONAP-TSC@lists.onap.org>>
Date:10/09/2018 03:17 PM
Subject:[onap-tsc] F2F meeting - Architecture/modelling - Dublin 
Release focus
Sent by:onap-tsc@lists.onap.org




Hi ONAP ARCHCOM and MODCOM members,

Today there were both the ARCHCOM and MODCOM meetings where some time was spent 
on the focus of the upcoming face-to-face.  I have attempted to capture the 
topics here: 
https://wiki.onap.org/display/DW/Dublin+Architecture+Planning+Meeting.  
Naturally this is subject to input

This covers both the meeting logistics as well as the meeting topics.  These 
will be folded into an agenda at a later date.  Andy/Deng, please also add 
other identified modelling topics that you have. I feel it’s a slightly 
ambitious set of topics for the available time, some concessions may be 
required to produce a workable agenda.

Note: Today it was discussed to spread the architecture and modelling topics 
across the 2.5 days instead of concentrating the topics into specific timeslots 
(unless there is any stronge objection to this).

Best Regards,

Steve.



STEPHEN TERRILL
Senior Expert, Automation and Management
BDGS RDP Architecture & Solutions
Business Unit Digital Services

Ericsson
Ericsson R&D Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com




Legal entity: Ericsson España S.A, compay registration number ESA288568603. 
This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at 
www.ericsson.com/email_disclaimer





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

View/Reply Online (#3859): https://lists.onap.org/g/onap-tsc/message/3859
Mute This Topic: https://lists.onap.org/mt/27155634/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling]Cancel the modeling subcommitee/Service IM/Data Model call this week

[denghui (L)]

Hello all

Due to New Year in Israel, modeling subcommittee would like to cancel below 
calls this week:

1)  modeling subcommittee call , 9am eastern time Tuesday.

2)  Service IM call, 12pm eastern time, Wednesday

3)  Data modeling call, 10am eastern time, Monday

Thanks a lot

DENG Hui

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

View/Reply Online (#3685): https://lists.onap.org/g/ONAP-TSC/message/3685
Mute This Topic: https://lists.onap.org/mt/25499495/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Definition of Subcommittee Membership

[denghui (L)]

I support Steve and Chris about opening for membership, and also support Kenny 
about the concern of inactive members to vote. And I also want to remind there 
another type members (Election only) we also needs to pay attention to.
From my recorded attendee list in recent two months. They are neither attending 
any of meeting, nor contributing any Wiki/Jira/Gerrit. I doubt their votes 
would really help us build a healthy and open contributing environment

Here are my 2 cents to each committee if we can:
1) renew memberships every release to encourage participation and to avoid 
zombies who could stay forever.
2) self-enroll voting member needs to identify his/her own contribution to the 
committee openly.

DENG Hui

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Christopher Donley
Sent: Tuesday, August 28, 2018 5:07 AM
To: ONAP-TSC@lists.onap.org
Subject: Re: [onap-tsc] Definition of Subcommittee Membership

I agree with Steve.  I don't think we want to be too prescriptive about 
subcommittee membership, and we want to be open and welcoming to people who 
will contribute.  We set it up so that subcommittees work on a rough consensus 
basis, and decisions needing a formal vote get raised to the TSC.  You 
mentioned the architecture subcommittee. We usually have about 50 people show 
up on the weekly calls (depending on topics), and additional people participate 
in various task forces or working groups, so I think the membership really is 
in the 72-108 person you cited.  It is worth cleaning up the list, as some 
people have changed companies or have been reassigned, but in general, I am 
comfortable with the idea of self-selected membership.

For the purposes of electing the leadership, I think one "finger guard" we 
could consider is temporarily freezing the membership list prior to the 
commencement of the vote (e.g., voters are those listed on the wiki as of two 
weeks prior to the date of the vote, or whatever interval we decide).  This 
would eliminate a last-minute rush to sign up, and would more accurately 
reflect the people who have been active in the group without discouraging 
future participants.

Chris
From: mailto:ONAP-TSC@lists.onap.org>> on behalf of 
Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>
Reply-To: "ONAP-TSC@lists.onap.org" 
mailto:ONAP-TSC@lists.onap.org>>
Date: Monday, August 27, 2018 at 1:48 PM
To: "ONAP-TSC@lists.onap.org" 
mailto:ONAP-TSC@lists.onap.org>>
Subject: Re: [onap-tsc] Definition of Subcommittee Membership

Hi Kenny,

I appreciate the effort that you are putting in regarding the elections and 
encoring communication via email list membership.

I wonder, though,  whether we are looking at this from the optimal perspective 
and context.  I’d be happy to hear from other sub-committee chairs here.  My 
reflection is that we had to bring items back to the TSC for decision, where 
formal membership was required.   So for me, working on a consensus basis was 
based upon the views both expressed in the meetings and what I considered may 
have been expressed if active members were absent.   This was to say, that the 
actual operations of the sub-committee isn’t missing the concept of membership 
and instead appreciates views and contribution.  The need arises when it comes 
to selecting the chairperson (as that is the only real formal voting).Lets 
not let that need complicate the day-to-day operations.Normally I would 
side with formality as that tends to play out better in the long run, but I am 
urging that we introduce formality to solve the necessary issues and see if we 
can use the evolving culture here.

BR,

Steve


PS – I will admit I have not been good at keeping a record of sub-committee 
meeting attendance.


From: ONAP-TSC@lists.onap.org 
mailto:ONAP-TSC@lists.onap.org>> On Behalf Of Kenny 
Paul
Sent: Monday, August 27, 2018 5:25 PM
To: ONAP-TSC@lists.onap.org
Subject: Re: [onap-tsc] Definition of Subcommittee Membership

Hi Steve,

The points you've raised are the same ones that prompted my email. Anyone is 
always welcome at any Subcommittee meeting either as an active participant, 
accidental tourist, interested party or concerned onlooker. They do not have to 
be on the wiki membership roster or the mailing list to attend a meeting.

However, even if they passively attend a meeting and do perform work behind the 
scenes, they would be missing any and all of the email-based discussions for 
the subcommittee.


As mentioned, I haven't really looked into Seccom yet so I don't know its 
status, but in a more general sense attendance records for the subcommittee 
meetings seem to be sparse or non-existent. Without such records is not 
possible to identify people on the membership roster who may be passively 
listening to the meetings at a minimum. There is no way to differentiate them 
from

[onap-tsc] [Modeling] Next week call will be chaired by Andy

[denghui (L)]

Hello all

Due to my schedule next week, I won't be available for next week call. And Andy 
has agreed to kindly help to chair the call of modeling subcommittee next week.
Please feel free to contact with him about your proposal of next week agenda.

Many thanks for Andy's help
Best regards,

DENG Hui

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

View/Reply Online (#3621): https://lists.onap.org/g/ONAP-TSC/message/3621
Mute This Topic: https://lists.onap.org/mt/24612979/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [modeling] Call for nominations: modeling subcommitee Chair and Vice Chair

[denghui (L)]

Hello Modelers

I would like nominate myself as a candidate of chair and vice chair of modeling 
subcommittee.

The goal of next year of modeling subcommittee needs to achieve the following 
goals
1) The internal data model design based on consensus.
2) Resource information model design, especially align with Data model.
3) Service model design with help from Architecture committee and impacted 
projects.
4) Infrastructure modeling design together with Multicloud in order to support 
Azure, K8S, .. et al.
5) Support other model spec from other committees like close loop policy, data 
collection VES .. et al.
6) Clarify more detail of the high level requirement together with use case 
committee and impacted projects.

If I were elected,  I would do my best to lead the group in taking the 
following opportunities for modeling subcommittee
1) Since the market of NFV has already taken off, most of them are based on 
SDOs, I would bring theirs experience into ONAP which could help ONAP become 
more success.
2) There are many standard delegate's involvement at the moment, I would revise 
some current process to better transfer SDO delegate's involvement into 
productive deliverables for ONAP community.
3) I would like to establish more mutual communication and setup activities 
with other SDOs like: ETSI NFV, TMF, MEF, ONF, IETF .. et al.

Below are my short Bio.
Hui DENG obtained his Doctor degree from Dept. Computer Science and Technology 
at Tsinghua University in 2002. He worked as chief researcher in Hitachi 
(China) R&D Cooperation from 2002 to 2007, and worked as Principal staff 
between 2007 and 2016 in China Mobile. He joined Huawei and working on NFV 
related topic since 2016. He acted as the co-chair of IETF MIF working group. 
And he was the board of director of WBA(Wireless Broadband Alliance) between 
2012-2014, acted as the board of director of OPNFV between 2014-2016 and 1st 
board of chairman of OPEN-O project in Linux Foundation. He is the current 
chair of modeling subcommittee in ONAP.

2017 - 2018 Chair of modeling subcommittee, ONAP
2016 - 2016 1st Board of Chairman, OPEN-O
2014 - 2016 Board of Director (officer), OPNFV
2012 - 2014 Board of Director, WBA(Wireless Broadband Alliance)
2009 - 2016 Co-chair, MIF(Multiple Interfaces) WG, IETF
2016 - ETSI NFV ISG coordinator of Huawei

Professional experience
2016 - Now Chief NFV Strategy Officer, Huawei
2007 - 2016 Principal Staff, China Mobile
2002 - 2007 Chief Researcher, Hitachi


From: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> 
[mailto:ONAP-TSC@lists.onap.org] On Behalf Of denghui (L)
Sent: Tuesday, July 31, 2018 11:13 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: [onap-tsc] [modeling] Call for nominations: modeling subcommitee Chair 
and Vice Chair

Hello all

Based on today modeling subcommittee call, we have decided the following 
consensus for the election of modeling subcommittee
https://wiki.onap.org/display/DW/Modeling+Subcommittee+Election<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Modeling-2BSubcommittee-2BElection&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3UIWLh7P2rAFm1qdZ7jMYQ&m=fYPrSce5nFNyqgTvCYIi3JeW0zAkWPjkxxLU1URlVek&s=Jsvl4N827SR8fidxWGa-JJpiB196vc3qyhs1d9wKnB4&e=>

This is the self-nomination phase and will end in 2 business weeks: Thursday 
Aug 14th 2018
Please identify clearly whether you are interested in Chair, VC or both of them.

Please aware of members of modeling subcommittee is locked,
https://wiki.onap.org/display/DW/Members<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Members&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3UIWLh7P2rAFm1qdZ7jMYQ&m=fYPrSce5nFNyqgTvCYIi3JeW0zAkWPjkxxLU1URlVek&s=NFYW-ld4JkJStHostl_YsfYze9kpn6r2UirRBN4pYqI&e=>
We don't allow anybody add his name after today modeling subcommittee call 
20180731 10am eastern time

Thanks a lot for your help

Best regards,

Deng Hui



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

View/Reply Online (#3610): https://lists.onap.org/g/ONAP-TSC/message/3610
Mute This Topic: https://lists.onap.org/mt/23904334/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] Poll on ONS EU modeling meetup

[denghui (L)]

Hello all



Based on last modeling subcommittee call, we will poll how many people will 
attend this event:

https://wiki.onap.org/display/DW/201809+ONS+EU+Modeling+meetup+poll



We will check how many people and who will attend this event then decide what 
we could decide,

please fill in your name at the link if you plan to attend,



Thanks a lot



DENG Hui


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

View/Reply Online (#3602): https://lists.onap.org/g/ONAP-TSC/message/3602
Mute This Topic: https://lists.onap.org/mt/24239522/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] Call for nominations: modeling subcommitee Chair and Vice Chair

[denghui (L)]

Hello all

Based on today modeling subcommittee call, we have decided the following 
consensus for the election of modeling subcommittee
https://wiki.onap.org/display/DW/Modeling+Subcommittee+Election

This is the self-nomination phase and will end in 2 business weeks: Thursday 
Aug 14th 2018
Please identify clearly whether you are interested in Chair, VC or both of them.

Please aware of members of modeling subcommittee is locked,
https://wiki.onap.org/display/DW/Members
We don't allow anybody add his name after today modeling subcommittee call 
20180731 10am eastern time

Thanks a lot for your help

Best regards,

Deng Hui


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

View/Reply Online (#3553): https://lists.onap.org/g/ONAP-TSC/message/3553
Mute This Topic: https://lists.onap.org/mt/23904334/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss][onap-tsc] PTL Election announcement for ONAP Multi VIM/Cloud project

[denghui (L)]

+1 for both of you

From: onap-disc...@lists.onap.org [mailto:onap-disc...@lists.onap.org] On 
Behalf Of Xinhui Li
Sent: Thursday, July 26, 2018 7:00 PM
To: onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Subject: [onap-discuss][onap-tsc] PTL Election announcement for ONAP Multi 
VIM/Cloud project

Dear TSC and ONAP community,

It is my pleasure to announce the result of Multi VIM/Cloud PTL election for 
R3.  Bin Yang ran as the only candidate and has been confirmed by the voting 
results of committers at: 
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_949d2520dce241dd.

Congratulations Bin Yang!

Taking this opportunity, I would like to thank the TSC and the ONAP community 
for your support to Multi VIM/Cloud project.  Bin Yang has been participating 
in the Multi VIM/Cloud project from the very beginning and he is a strong 
community leader. I am confident our project will continue its success under 
Bin Yang’s leadership.  Your continuous support to him and this team will be 
greatly appreciated.

To ensure the success of the project and a smooth transition, I will remain to 
be a committer of Multi VIM/Cloud to help as much as possible.

Best wishes and thanks!
Xinhui Li


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

View/Reply Online (#3501): https://lists.onap.org/g/ONAP-TSC/message/3501
Mute This Topic: https://lists.onap.org/mt/23743083/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] PTL Election for modeling project - Result

[denghui (L)]

Dear ONAP TSC,

Based on the process of annual community elections for PTL described on 
https://wiki.onap.org/display/DW/Annual+Community+Elections, here’s the voting 
result for modeling project:
1. DENG Hui  (Condorcet方法优胜者: 胜出所有其他投票选项)

2. Abstain  负于 DENG Hui，差距为 8�C0


I have updated the Voting Results History page: 
https://wiki.onap.org/display/DW/Voting+Results+History . Thank you for your 
support!

Regards,

DENG Hui


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

View/Reply Online (#3499): https://lists.onap.org/g/ONAP-TSC/message/3499
Mute This Topic: https://lists.onap.org/mt/23814152/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] SDC review documentation of high level requirement

[denghui (L)]

Hello modelers

This is the bridge info for Wednesday 10am eastern time meeting.

Thanks for your join

DENG Hui

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

View/Reply Online (#3495): https://lists.onap.org/g/ONAP-TSC/message/3495
Mute This Topic: https://lists.onap.org/mt/23804004/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 15.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
ATTENDEE;CN="denghui (L)";RSVP=TRUE:mailto:denghu...@huawei.com
ATTENDEE;CN='anatoly.katz...@att.com';RSVP=TRUE:mailto:anatoly.katzman@att.
	com
ATTENDEE;CN="LANDO, MICHAEL";RSVP=TRUE:mailto:ml6...@intl.att.com
CLASS:PUBLIC
CREATED:20180724T153100Z
DESCRIPTION:Join from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/
	137904496 <https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F137904
	496&sa=D&usd=2&usg=AFQjCNHWLm-MNCNZh9JQ8TByZ7QBGA_nzQ> \nOr iPhone one-tap
	 (US Toll): +14086380968\,137904496# or +16465588656\,137904496#\nOr Telep
	hone:\nDial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)\nMeeti
	ng ID: 137 904 496\nInternational numbers available: https://zoom.us/zoomc
	onference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a <https://www.google.com/url?q
	=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3Dmi-ad1sMLWlXByAKLio5vDnd9JYq
	UR_a&sa=D&usd=2&usg=AFQjCNGUpQlMWM7Hx42afMT3U-kpQiPOMA> \n\n
DTEND;TZID="China Standard Time":20180725T23
DTSTAMP:20180724T152441Z
DTSTART;TZID="China Standard Time":20180725T220000
LAST-MODIFIED:20180724T153100Z
LOCATION:https://zoom.us/j/137904496
ORGANIZER;CN="denghui (L)":mailto:denghu...@huawei.com
PRIORITY:5
SEQUENCE:0
SUMMARY;LANGUAGE=zh-cn:SDC review documentation of high level requirement
TRANSP:OPAQUE
UID:04008200E00074C5B7101A82E0089048457FA523D401000
	01000B540D30B76592E4080200A19A899E195
X-ALT-DESC;FMTTYPE=text/html:\n\n\n\n\n\n\n\n\nJoin from PC\, Mac\, L
	inux\, iOS or Android: https://zoom.us/j/137904496\n\nOr iPhone one-tap (US Toll): +14086380968\,137904496# or 
	+16465588656\,137904496#\n\nOr Telephone:\nDial: +
	1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)\nMeeting ID: 137 904 496\nInternation
	al numbers available: 
	https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5v
	Dnd9JYqUR_a\n\n\n\n\n
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-APPTLASTSEQUENCE:1
X-MS-OLK-APPTSEQTIME:20180724T152441Z
X-MS-OLK-AUTOFILLLOCATION:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR

Re: [onap-tsc] #modeling Mapping between Modeling and Casablanca R3 requirements

[denghui (L)]

Hi Gildas

I had added a column here and fill in the PTL's feedback on the limited 
requirements.
https://wiki.onap.org/display/DW/ONAP+R3+Modeling+High+Level+Requirements

thanks for your help

DENG Hui

From: Gildas Lanilis
Sent: Thursday, July 19, 2018 11:45 PM
To: denghui (L) 
Cc: ONAP-TSC@lists.onap.org; onap-disc...@lists.onap.org; GILBERT, MAZIN E 
(MAZIN E) 
Subject: #modeling Mapping between Modeling and Casablanca R3 requirements

Hi Deng,

This is to follow up on the need to understand "what else" is required from a 
Modelling perspective for Casablanca Release.
Could you help into performing the mapping between the list in "ONAP R3 
Modeling Level 
Requirements<https://wiki.onap.org/display/DW/ONAP+R3+Modeling+High+Level+Requirements>"
 and the "Casablanca Release 
Requirements<https://wiki.onap.org/display/DW/Casablanca+Release+Requirements>"?
So far what has been approved for the Scope of Casablanca is documented 
here<https://wiki.onap.org/download/attachments/34375712/ONAP%20Casablanca%20M1%20Status%20Summary%20Version5.pdf?version=1&modificationDate=1532014370813&api=v2>.

I would recommend to add a column in the "ONAP R3 Modeling Level 
Requirements<https://wiki.onap.org/display/DW/ONAP+R3+Modeling+High+Level+Requirements>"
 indicating which Casablanca Release Requirement it refers to.
The plan is to review and discuss this with PTLs during Monday PTL meeting at 6 
am PDT.

Let me know if I can help.

Thanks,
Gildas

[HuaweiLogowithName]
Gildas Lanilis
ONAP Release Manager
Santa Clara CA, USA
gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>
Mobile: 1 415 238 6287


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

View/Reply Online (#3488): https://lists.onap.org/g/ONAP-TSC/message/3488
Mute This Topic: https://lists.onap.org/mt/23745408/21656
Mute #modeling: https://lists.onap.org/mk?hashtag=modeling&subid=2743226
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [onap-discuss] [modeling] Minutes of SDC review of high level requirement

[denghui (L)]

Information model has been presented and approved by modeling subcommittee, but 
Data Model hasn’t,
please work with SDC to improve the DM design and come back to modeling 
subcommittee when you are ready.

Thanks a lot

DENG Hui

From: Lando,Michael [mailto:ml6...@intl.att.com]
Sent: Monday, July 23, 2018 12:57 AM
To: huang.zhuo...@zte.com.cn; yangxu (H)
Cc: denghui (L); onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Subject: RE: Re: [onap-tsc] [onap-discuss] [modeling] Minutes of SDC review of 
high level requirement

The issue is reusability you need to review all the definitions you are trying 
to create and I identify the component that are already available.

Based on my review I see duplications in the node type so my answer is this 
need to be reviewed again.

In addition I am still not clear if this was presented to the modeling 
subcommittee and did it get approved by them?








BR,

[Michael Lando]

AT&T Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com<mailto:michael.la...@intl.att.com>

From: huang.zhuo...@zte.com.cn 
Sent: Thursday, July 19, 2018 03:55
To: yang...@huawei.com; Lando,Michael 
Cc: denghu...@huawei.com; onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Subject: 答复: Re: [onap-tsc] [onap-discuss] [modeling] Minutes of SDC review of 
high level requirement




Hello all,



 Thanks Yang XU for clarifying about the state of Wan Connection.

 To Michael, if we leverage the relationship types and capability 
types which are already existed and remove the new ones which might be 
duplicate and just leave the node types and data type introduced in wiki page 
(https://wiki.onap.org/display/DW/Design-Time+Data+Model%3A+WAN+Service),<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Design-2DTime-2BData-2BModel-253A-2BWAN-2BService-29-2C&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=K8FkF7f3Qm2IxaQ2WlIm2W9BPRXvKKKUUoYEmw0CUsg&s=pfIvFnD4SjoGtFtOulHN3UYSsOfLYbqrAlOC2zp7Qwc&e=>
  is it good enough for SDC to support Wan Connection in release 3?



Best Regards!













黄卓垚huangzhuoyao



职位position
承载网管开发部/有线研究院/有线产品经营部Strategy & IT-IT Dept.


[cid:image002.gif@01D422A0.B7055A00]

[cid:image003.gif@01D422A0.B7055A00]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R&D Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755    F: +86 755 
M: +86 xxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=K8FkF7f3Qm2IxaQ2WlIm2W9BPRXvKKKUUoYEmw0CUsg&s=CGEZTdwpHrL1NPbO3ElGqjzQXJokLKZALRIayTto50k&e=>


原始邮件
发件人：yangxu(H) mailto:yang...@huawei.com>>
收件人：denghui (L) 
mailto:denghu...@huawei.com>>onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
 
mailto:onap-disc...@lists.onap.org>>ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
 mailto:ONAP-TSC@lists.onap.org>>
日 期 ：2018年07月18日 23:52
主 题 ：Re: [onap-tsc] [onap-discuss] [modeling] Minutes of SDC review of high 
level requirement
Hi Hui and all,

Regarding the last bullet, AFAIK, the WAN connection has been agreed in release 
2 and moved from service IM clean page to resource IM clean page according to 
participants' suggestion that the WAN connection should be considered as 
resource.

Best regards,
Xu
发件人：denghui (L)
收件人：onap-disc...@lists.onap.org,ONAP-TSC@lists.onap.org<mailto:onap-disc...@lists.onap.org,ONAP-TSC@lists.onap.org>,
时间：2018-07-18 22:33:37
主 题：[onap-discuss] [modeling] Minutes of SDC review of high level requirement

Hello all

Please find the recorded meeting session here:
https://wiki.onap.org/display/DW/2018+2H+Modeling+sub-committee+meeting+agenda+and+minutes<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_2018-2B2H-2BModeling-2Bsub-2Dcommittee-2Bmeeting-2Bagenda-2Band-2Bminutes&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=K8FkF7f3Qm2IxaQ2WlIm2W9BPRXvKKKUUoYEmw0CUsg&s=NmSzgEv4tx5x2Ja1cjw3Bccr2pMVgnTOMcP5D_IUKBo&e=>


the meeting minutes are list below:

1) 20180719 9am, the last review from SDC before TSC meeting, will try to 
invite PTLs from SDC/SO/A&AI, the meeting bridge will be sent out tomorrow.

2) Service descriptor/resource composite/PNF/PNF instance/network 
Service/SD-WAN/Element group/Multicloud need to be reviewed tomorrow

3)  the committee will ask the approval for Implementation and documentation 
par

[onap-tsc] Withdraw modeling report to TSC this week

[denghui (L)]

Hello TSC and modelers.

Because concern raised in the list about our this week consensus report.
I plan to withdraw this week report and had another round discussion in next 
week modeling subcommittee call.

Thanks a lot

DENG Hui

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

View/Reply Online (#3456): https://lists.onap.org/g/ONAP-TSC/message/3456
Mute This Topic: https://lists.onap.org/mt/23744648/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] Today SDC/SO/A&AI high level requirement review call bridge

[denghui (L)]

Hello, owners,

Thanks Michael for yesterday review, today, let's have another round of review 
before TSC call at 9am Eastern time

Hi Seshu and Jimmy

Could you also kindly help to join this call since there are some requirements 
need your help to review

Thanks a lot for your help
Best regards,

DENG Hui

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

View/Reply Online (#3443): https://lists.onap.org/g/ONAP-TSC/message/3443
Mute This Topic: https://lists.onap.org/mt/23742760/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

--- Begin Message ---
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=denghui (L):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=denghui (L
 ):MAILTO:denghu...@huawei.com
DESCRIPTION;LANGUAGE=zh-CN:Join from PC\, Mac\, Linux\, iOS or Android: htt
 ps://zoom.us/j/137904496 <https://www.google.com/url?q=https%3A%2F%2Fzoom.
 us%2Fj%2F137904496&sa=D&usd=2&usg=AFQjCNHWLm-MNCNZh9JQ8TByZ7QBGA_nzQ> \nOr
  iPhone one-tap (US Toll): +14086380968\,137904496# or +16465588656\,13790
 4496#\nOr Telephone:\nDial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (
 US Toll)\nMeeting ID: 137 904 496\nInternational numbers available: https:
 //zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a <https://www.g
 oogle.com/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3Dmi-ad1sMLWlXB
 yAKLio5vDnd9JYqUR_a&sa=D&usd=2&usg=AFQjCNGUpQlMWM7Hx42afMT3U-kpQiPOMA> \n\
 n
SUMMARY;LANGUAGE=zh-CN:SDC/SO/AAI review high level requirement
DTSTART;TZID=China Standard Time:20180719T21
DTEND;TZID=China Standard Time:20180719T22
UID:04008200E00074C5B7101A82E008C0F08421C81ED401000
 01000903D1000362106448E0590B747256406
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180719T075849Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=zh-CN:https://zoom.us/j/137904496
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1949075486
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
--- End Message ---

[onap-tsc] [modeling] new proposal to change TSC report consensus slide wording

[denghui (L)]

Hello Modelers,

I have received comments from Andy and Andrei after the meeting about our 
consensuses slide, as below, according to their proposal, 3 changes are listed 
below:
1) Clarify On-Boarding and the Internal ONAP models are distinct
2) remove "align with R3 IM"
3) removing the statement "(backward compatible with onboarding model)

According to our recorded session
https://wiki.onap.org/display/DW/2018+2H+Modeling+sub-committee+meeting+agenda+and+minutes

I re-listen to the recorded session 20180717, I did ask any objection to the 
final consensus in the end.
only Michela raised the  comments to remove 3rd bullet.  I did explain the 
reason, and didn't hear any objection from Michela any more.

In this case, my judge would be from our session
3) is not yet a 100% consensuses assuming Michela not reponse in time,  but 1) 
and 2) are 2 new proposals to change the existing consensus

So I am asking the modeling subcommittee here whether you agree to add 1) and 
remove 2)
If there is no any objection before TSC call, I will revise them as this 
proposal.

Thanks a lot

DENG Hui




From: Andrei Kojukhov [mailto:andrei.kojuk...@amdocs.com]
Sent: Thursday, July 19, 2018 4:10 AM
To: MAYER, ANDREW J mailto:am8...@att.com>>; denghui (L) 
mailto:denghu...@huawei.com>>; Lingli Deng 
mailto:denglin...@chinamobile.com>>
Cc: 'eric.deb...@orange.com' 
mailto:eric.deb...@orange.com>>; Mark Gibson 
mailto:mar...@amdocs.com>>; 'Mehmet Toy' 
mailto:mehmet@verizon.com>>; 'Alex Vul' 
mailto:alex@intel.com>>; 'Davis, Nigel' 
mailto:nda...@ciena.com>>; 'Ranganathan, Raghu' 
mailto:rra...@ciena.com>>; 'Priya TG' 
mailto:priy...@netcracker.com>>; WECHSLER, CHESLA C 
mailto:cw1...@att.com>>; KATZMAN, ANATOLY 
mailto:ak4...@intl.att.com>>; LANDO, MICHAEL 
mailto:ml6...@intl.att.com>>; HALLAHAN, RYAN 
mailto:rh1...@att.com>>; Lingli Deng 
mailto:denglin...@chinamobile.com>>
Subject: RE: Minutes from Today's Meeting

Andy, Denghui, Lingli

I tend to agree with Andy. What I captured from a meeting screen is quickly 
adding sentences to a reporting slide by a chair because of lack of time.
There is obviously a room for making mistakes and inaccurate wording.

BR

Andrei

From: MAYER, ANDREW J mailto:am8...@att.com>>
Sent: Wednesday, July 18, 2018 10:30 PM
To: denghui (L) mailto:denghu...@huawei.com>>; Lingli 
Deng mailto:denglin...@chinamobile.com>>
Cc: 'eric.deb...@orange.com' 
mailto:eric.deb...@orange.com>>; Andrei Kojukhov 
mailto:andrei.kojuk...@amdocs.com>>; Mark Gibson 
mailto:mar...@amdocs.com>>; 'Mehmet Toy' 
mailto:mehmet@verizon.com>>; 'Alex Vul' 
mailto:alex@intel.com>>; 'Davis, Nigel' 
mailto:nda...@ciena.com>>; 'Ranganathan, Raghu' 
mailto:rra...@ciena.com>>; 'Priya TG' 
mailto:priy...@netcracker.com>>; WECHSLER, CHESLA C 
mailto:cw1...@att.com>>; KATZMAN, ANATOLY 
mailto:ak4...@intl.att.com>>; LANDO, MICHAEL 
mailto:ml6...@intl.att.com>>; HALLAHAN, RYAN 
mailto:rh1...@att.com>>; Lingli Deng 
mailto:denglin...@chinamobile.com>>
Subject: RE: Minutes from Today's Meeting

Denghui,

We appreciate that you captured some of the major points that were agreed to 
during the Modeling Sub-committee call.

We do have a few questions that need clarification on the TSC readout:

  *   How was the agreement captured that the VNF Descriptor model for 
On-Boarding and the Internal ONAP models are distinct? We reached consensus on 
this point multiple times during the Modeling Sub-committee call, but it is not 
listed. Please reflect this important point.
  *   During the call there did not seem to be clear consensus with the 
statement "align with R3 IM". Based on the recording we all agreed that we need 
keep the Information Modeling and Data Modeling aligned during the 
collaborative work on the internal data model for R4 and beyond. However, since 
it was not a clear agreement, please remove "align with R3 IM"
  *   Please consider removing the statement "(backward compatible with 
onboarding model)".  Based on the recording, it wasn't clear during the call 
that we had community consensus on this particular statement.

Best Regards,
Andy

Andy Mayer, Ph.D. | PMTS, D2.0 Integration | AT&T Labs | Phone: +1 (732) 
420-9945 | am8...@att.com<mailto:am8...@att.com>



From: denghui (L)
Sent: Wednesday, July 18, 2018 11:16 AM
To: 'onap-disc...@lists.onap.org' ; 
'ONAP-TSC@lists.onap.org' 
Subject: [modeling] Meeting minutes, slides and video recorded available for 
modeling subcommittee call yesterday

Hello all

Please kindly help to review yesterday meeting minutes, slides, and video 
recorded as below link:
https://w

[onap-tsc] [modeling] Minutes of SDC review of high level requirement

[denghui (L)]

Hello all

Please find the recorded meeting session here:
https://wiki.onap.org/display/DW/2018+2H+Modeling+sub-committee+meeting+agenda+and+minutes


the meeting minutes are list below:

1) 20180719 9am, the last review from SDC before TSC meeting, will try to 
invite PTLs from SDC/SO/A&AI, the meeting bridge will be sent out tomorrow.

2) Service descriptor/resource composite/PNF/PNF instance/network 
Service/SD-WAN/Element group/Multicloud need to be reviewed tomorrow

3)  the committee will ask the approval for Implementation and documentation 
part, not for low priority and experiemental

4) WAN connection need modeling subcommittee review and approval

Thanks a lot

DENG Hui

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

View/Reply Online (#3405): https://lists.onap.org/g/ONAP-TSC/message/3405
Mute This Topic: https://lists.onap.org/mt/23671444/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] SDC review high level requirement on Wednesday

[denghui (L)]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=denghui (L):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-disc...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=ONAP-TSC@l
 ists.onap.org:MAILTO:ONAP-TSC@lists.onap.org
DESCRIPTION;LANGUAGE=zh-CN:Hello owners\nDue to time limitation\, we can’
 t go through all high level requirements\, we plan to ask the help of SDC 
 PTL to review it again today.\nPlease help to join it\nThanks a lot\nDENG 
 Hui\n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/1379
 04496<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F137904496&s
 a=D&usd=2&usg=AFQjCNHWLm-MNCNZh9JQ8TByZ7QBGA_nzQ>\nOr iPhone one-tap (US T
 oll): +14086380968\,137904496# or +16465588656\,137904496#\nOr Telephone:\
 nDial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)\nMeeting ID:
  137 904 496\nInternational numbers available: https://zoom.us/zoomconfere
 nce?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a<https://www.google.com/url?q=https%
 3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3Dmi-ad1sMLWlXByAKLio5vDnd9JYqUR_a&sa
 =D&usd=2&usg=AFQjCNGUpQlMWM7Hx42afMT3U-kpQiPOMA>\n\n\n
SUMMARY;LANGUAGE=zh-CN:[modeling] SDC review high level requirement on Wedn
 esday
DTSTART;TZID=China Standard Time:20180718T21
DTEND;TZID=China Standard Time:20180718T22
UID:04008200E00074C5B7101A82E008F0C28514C81ED401000
 01000903D1000362106448E0590B747256406
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180718T105925Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=zh-CN:https://zoom.us/j/137904496
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-294488094
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR

[onap-tsc] [modeling] Meeting minutes, slides and video recorded available for modeling subcommittee call yesterday

[denghui (L)]

Hello all

Please kindly help to review yesterday meeting minutes, slides, and video 
recorded as below link:
https://wiki.onap.org/display/DW/2018+2H+Modeling+sub-committee+meeting+agenda+and+minutes

thanks a lot for your checking
Best regards

DENG Hui

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

View/Reply Online (#3394): https://lists.onap.org/g/ONAP-TSC/message/3394
Mute This Topic: https://lists.onap.org/mt/23627002/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [modeling] High level requirement reviewed by PTLs and SDC

[denghui (L)]

Hello owners of requirements,

Thanks PTL meeting time and theirs kind comments, we have moved 3+5 out of high 
level requirement into other table.
For the left of those requirements, please help to join the dedicated 
discussion today with SDC after modeling subcommittee call

>From yesterday, PTL and TSC has strong concern about modeling requirement 
>bring additional work besides of M1 requirement.
Please each owner identify with impacted PTL, whether your requirement in the 
scope of M1 of that impact projects,
if not, that requirement will also have to be moved into lower priority for 
future release other than R3.

As SDC suggested in the list, each of owner, please help to prepare and explain 
your requirement

Thanks a lot

DENG Hui


From: denghui (L)
Sent: Monday, July 16, 2018 4:46 PM
To: onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Cc: 'Lando,Michael' ; 'anatoly.katz...@att.com' 

Subject: [modeling] High level requirement reviewed by PTLs and SDC

Hello, owners of requirements

I have sent you a private email last week about today PTL's meeting that you 
will kindly help to explain your proposed high requirement to PTLs,
whether impacted PTLs agree it and allocate the implementation resource to 
support it
If impacted PTLs agree, this requirement will stay in R3 high level 
requirement, otherwise, it will move to lower priority category.

Since there are so many high level requirements related to SDC, if today PTL 
session time is not enough,
SDC PTLs could help to discuss it on Tuesday again right after modeling 
subcommittee call, we can use the same bridge of modeling subcommittee on 
Tuesday.

Thanks a lot for your attendance
Best regards,

DENG Hui

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

View/Reply Online (#3385): https://lists.onap.org/g/ONAP-TSC/message/3385
Mute This Topic: https://lists.onap.org/mt/23530210/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] High level requirement reviewed by PTLs and SDC

[denghui (L)]

Hello, owners of requirements

I have sent you a private email last week about today PTL's meeting that you 
will kindly help to explain your proposed high requirement to PTLs,
whether impacted PTLs agree it and allocate the implementation resource to 
support it
If impacted PTLs agree, this requirement will stay in R3 high level 
requirement, otherwise, it will move to lower priority category.

Since there are so many high level requirements related to SDC, if today PTL 
session time is not enough,
SDC PTLs could help to discuss it on Tuesday again right after modeling 
subcommittee call, we can use the same bridge of modeling subcommittee on 
Tuesday.

Thanks a lot for your attendance
Best regards,

DENG Hui

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

View/Reply Online (#3379): https://lists.onap.org/g/ONAP-TSC/message/3379
Mute This Topic: https://lists.onap.org/mt/23530210/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Progress report about Modeling R3 VNFD DM 2 options discussion

[denghui (L)]

Dear TSC,

Last week, modeling subcommittee report two options to TSC, and the 
recommendations from TSC received are make further clarification of 2options, 
especially:
*Impact on functional requirement/non functional requirements
*Impact on influenced projects
*Impact on Integrations/existing use cases
The report 0705 slides are here: 
https://wiki.onap.org/display/DW/TSC+2018-07-05+Meeting+Agenda

Modeling subcommittee had several round internal and different level discussion 
and yesterday modeling subcommittee call made below recommendations:
https://wiki.onap.org/display/DW/2018+2H+Modeling+sub-committee+meeting+agenda+and+minutes
*Because option 1 is not yet full specified, it needs more time to 
design, implement and be verified
*Option 1 will provide stable data model (based on vCPE) by M2 model 
freeze and having this new DM in R3
*Option 2 : R2 resource DM as the baseline  (ONAP R2+ Design-Time 
Resource DM clean 
version
 ) by M2 model freeze.
VNFD should be at least modeled based on SOL001 and reference the latest ETSI 
NFV SOL001 GS v2.5.1
*By M2, modeling subcommittee will compare 2 options and bring them 
back to TSC
*Option 1 and 2 will work together to try to converge as well.
*We will not make comparison before this time.

Those recommendations may change before TSC meeting during committee list 
discussion this week.
We will upload tentative slide to the TSC 0712 agenda asap

Thanks a lot for your review
Best regards,

DENG Hui

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

View/Reply Online (#3355): https://lists.onap.org/g/ONAP-TSC/message/3355
Mute This Topic: https://lists.onap.org/mt/23242493/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] Call for agreement on obsoleting some attributes/datatypes of the resource IM

[denghui (L)]

Hello IM modelers,

According to yesterday call, resource IM team would like to call for agreement 
on obsoleting some attributes/datatypes of the resource IM.
The reason for obsoleting those artifacts is that their functionalities are 
covered by HPA related attributes and thus redundant in the model.
Detailed information of the proposal can be found at 
https://wiki.onap.org/display/DW/Obsolete+Legacy+Attributes.

Agreement that needs to be reached across the modeling subcommittee is:

*   Agree on marking the proposed attributes/datatypes as "obsolete" in the 
clean version of the resource IM

*   The format of such marking will follow the same way as the conclusion 
of lifecycle stereotype proposal

Deadline for this call is July 17th, PST 00:00. Please comment on the mailing 
list if you have any concerns.

Please note that it's also suggested to submit the same proposal to ETSI after 
agreement reached in the subcommittee, this will be discussed offline.

Thanks a lot

DENG Hui


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

View/Reply Online (#3354): https://lists.onap.org/g/ONAP-TSC/message/3354
Mute This Topic: https://lists.onap.org/mt/23242212/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] Call for owner of R3 Modeling high level requirement

[denghui (L)]

Hello modelers,

According to yesterday call, we would like to call for owner for each high 
level requirement.
https://wiki.onap.org/display/DW/2018+2H+Modeling+sub-committee+meeting+agenda+and+minutes

The responsibility of owner are shown as below:

1)  Coordinate both IM and DM model spec commitment.

2)  Coordinate code implement those requirements

3)  Coordinate the impacted project about those requirement.

4)  Report to modeling subcommittee about the progress regularly.

If you would like kindly help to volunteer to contribute, please fill in your 
name in the column of owner of each high level requirement.
https://wiki.onap.org/display/DW/ONAP+R3+Modeling+High+Level+Requirements

if there is no owner for the requirements, we will downgrade the priority and 
each drop those requirements.
Based on the input, we will report to TSC on the result this week.

Thanks a lot for your kind help
Best regards

DENG Hui

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

View/Reply Online (#3353): https://lists.onap.org/g/ONAP-TSC/message/3353
Mute This Topic: https://lists.onap.org/mt/23242167/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[denghui (L)]

Dear ONAP community,

I am willing to self-nominate for the PTL role of ONAP modeling project to help 
this move forward

I have established ONAP modeling project and played PTL role since its 
beginning.
The coordination of modeling subcommittee to support their repo will also be 
very important modeling project's job.

About myself:
https://wiki.onap.org/pages/viewpage.action?pageId=5736142

Many thanks

DENG Hui

From: onap-disc...@lists.onap.org [mailto:onap-disc...@lists.onap.org] On 
Behalf Of denghui (L)
Sent: Friday, July 6, 2018 9:12 AM
To: onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Hello all,

Due to US National holiday, let's extend the self-nomination period to July 
10th 2018 10:00 EST
Thanks a lot

DENG Hui


On Jul 4, 2018, at 2:14 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Dear ONAP Community and ONAP TSC,

As mandated by ONAP process, PTL elections must be held at least once a year.
You can read more details here: 
https://wiki.onap.org/display/DW/Annual+Community+Elections<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Annual-2BCommunity-2BElections&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Oej6QUk5p2KdqNEWySpOHA&m=aqtE2C1ZdfxIEpvFpsi-ywKvepAjMEEvXvpyXwKvr7o&s=1VOSZREkf7OvEcmx6COn9S0Mz80ACCfrmsVXjmhZwZs&e=>

if you are interested in this position, I invite you to submit your 
self-nomination for ONAP modeling project.

Important dates:
---
You have 2 days to submit your self-nomination from receipt of this email. (End 
by July 6th 2018 10:00 IST)

Election duration: July 6th 2018 12:00 IST -  July 11th 2018 12:00 IST
(from CVIS system, private email will be sent to all committers email id 
mentioned 
athttps://wiki.onap.org/display/DW/Resources+and+Repositories<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=XBYNhzlk2jx6nSVGWpJjJUhpTLxHynkr7bh6Vp5VOXU&s=odKqVMZCdJUsygPKUpW7Gk3KS-ALAv3Pe3CO5I_82Ls&e=>
 )

Election result: July 11th 2018 (will be announced in onap-discuss and onap-tsc 
mailing lists)



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

View/Reply Online (#3344): https://lists.onap.org/g/ONAP-TSC/message/3344
Mute This Topic: https://lists.onap.org/mt/23163968/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] Papyrus working branch for modeling

[denghui (L)]

Hello modelers

I have created a working branch (R3workingbranch) which will help papyrus 
contributors could submit papyrus files to Gerrit, folder name will be 
/modelspec/papyrus

Please kindly remember to submit the correct place by : git checkout 
R3workingbranch

Thanks a lot for your help

DENG Hui

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

View/Reply Online (#3343): https://lists.onap.org/g/ONAP-TSC/message/3343
Mute This Topic: https://lists.onap.org/mt/23209083/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[denghui (L)]

Hi Jessie,

I check this again, Epics shows the correct plan for people who could submit 
their RST spec here, Story for resources are not correct which reflect your 
comments, I talked with YANG Xu, he by mistaken create those stories, I have 
asked him to close those story and set it “won’t do”,

Thanks a lot for your checking
Best regards,

DENG Hui

From: jessie jewitt [mailto:jessie.jew...@oamtechnologies.com]
Sent: Tuesday, July 10, 2018 3:08 AM
To: onap-discuss ; Vul, Alex 
Cc: denghui (L) ; Brian Hedstrom 
; GILBERT, MAZIN E (MAZIN E) 
; ONAP-TSC@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Deng Hui-
 My question to you this morning was this. I have understood that the 
following info on this page: Casablanca Modeling 
M1<https://wiki.onap.org/pages/viewpage.action?pageId=35524278> was what was 
approved by the TSC for Casablanca M1. This page includes all of our high-level 
requirements (as Epics/Stories) as specified by the modeling subcommittee that 
have NOT yet been approved by the committee. So how did they get approved by 
the TSC?
-Jessie

On Fri, Jul 6, 2018 at 5:58 AM, Alex Vul 
mailto:alex@intel.com>> wrote:
Dear all,

Agree with Brian. The scope of the modeling project, as it was agreed upon, was 
to focus on modeling related tools. Modeling specifications and their curation 
was always part of the modeling subcommittee work.

Recall that when modeling subcommittee was formed, the intents was for 
individual projects to create their own relevant information and data models 
and to work with the modeling subcommittee on their adoption across other 
projects.




From: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> 
[mailto:ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>] On Behalf Of 
denghui (L)
Sent: Friday, July 6, 2018 05:21
To: Brian Hedstrom 
mailto:brian.hedst...@oamtechnologies.com>>

Cc: GILBERT, MAZIN E (MAZIN E) 
mailto:ma...@research.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Hi Brian,

I have just created a modeling governance page which explains the relationship 
among modeling subcommittee, modeling project and SDO coordinators.
https://wiki.onap.org/display/DW/Modeling+Governance
https://wiki.onap.org/display/DW/ONAP+Modeling+Governance

The same page which is under both modeling project and modeling subcommittee. I 
hope this page could help to answer your questions. Apologize that I haven’t 
done this early.

Thanks a lot for your kind review
Best regards,

DENG Hui

From: Brian Hedstrom [mailto:brian.hedst...@oamtechnologies.com]
Sent: Friday, July 6, 2018 3:55 AM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: GILBERT, MAZIN E (MAZIN E) 
mailto:ma...@research.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Deng,
What do you mean by "modelspec"?  The modeling project has the following scope 
and deliverables (I don't see Modeling Specifications listed which I thought 
was part of the Modeling Subcommittee):
Also, I didn't see your response to Mazin's question: Are you holding an 
election at the same time for the Chair subcommittee?
Scope:
•Modeling tools and converters
•Code - parsers (unified API interfaces) and tools (translators)
•Support Use cases of ONAP: vCPE, vVoLTE, vFW, et al.
Deliverables for release 1

Parsers and translators:
•Tosca Parsers
•YANG Parsers
•        Tosca to Heat
•YANG to Tosca

Thanks
Brian

On Thu, Jul 5, 2018 at 7:48 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hi Mazin

I guess that you know that PTL couldn’t remove the committer, I sent email to 
every committer after Release 1,
two of them email’s are not reachable, one agree to step down, so that’s the 
reason we removed 3 of them after the vote of all committers.
Others replied and said that they would like to continue.

Current committers are not only for tosca parser , but also for modelspec.

Thanks a lot

DENG Hui

From: GILBERT, MAZIN E (MAZIN E) 
[mailto:ma...@research.att.com<mailto:ma...@research.att.com>]
Sent: Thursday, July 5, 2018 9:20 PM

To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Thanks. I am assuming the project is based on the repo that is supporting the 
Tosca Parsers,
and you are tracking active committers.

Are you h

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[denghui (L)]

Hi Kenny

Based on my recollection from Linux Foundation, those committer have to step 
down by themselves.
I did send email to every committer after release 1, only 3 of them agree to 
step down, all others prefer to stay, do you have any advice how to handle this?
There are also lots of people who contribute the commit in R2, but not list 
here since they didn’t request as the committer.

Thanks a lot for your advice
Best regards

DENG Hui

From: Kenny Paul [mailto:kp...@linuxfoundation.org]
Sent: Tuesday, July 10, 2018 2:00 AM
To: denghui (L) ; Brian Hedstrom 

Cc: GILBERT, MAZIN E (MAZIN E) ; 
onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Hi Deng Hui,

Perhaps I'm missing something, but if I look in gerrit I see the following. 
There are a number of people with no activity as a Committer.

toscaparsers Committers listed as per INFO.yaml

Last +2Name
-
Jun 12 Hui Deng
Mar 28 Zhaoxing Meng
Nov 6   Rittwik Jana
Sep 7   maopeng zhang
NoneAmir Levy
NoneSerban Jora

Source: 
https://gerrit.onap.org/r/#/q/project:modeling/toscaparsers+status:merged



Modelspec Committers listed as per INFO.yaml

Last +2Name
-
Jun 4   Hui Deng
Apr 12 Lingli Deng
Apr 12 Zhaoxing Meng
Apr 10 maopeng zhang
Nov 9  Rittwik Jana
nonedong hu
nonehan yanan
noneshitao li
noneSandeep Shah
nonezhong heliu

source: https://gerrit.onap.org/r/#/q/project:modeling/modelspec++status:merged



Thanks!
-kenny


From: mailto:ONAP-TSC@lists.onap.org>> on behalf of 
"denghui (L)" mailto:denghu...@huawei.com>>
Date: Monday, July 9, 2018 at 1:15 AM
To: Brian Hedstrom 
mailto:brian.hedst...@oamtechnologies.com>>
Cc: "GILBERT, MAZIN E (MAZIN E)" 
mailto:ma...@research.att.com>>, 
"onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, 
"ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>" 
mailto:ONAP-TSC@lists.onap.org>>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Hi Brian,

The Gerrit committers are different from Wiki page major contributors, they are 
contributing to Gerrit rst file for documentation based on the clean wiki page.

We are discussing to create papyrus folder from R3, once that has been done, 
then contributors who commit to Gerrit, those who are major contributor will be 
elected to as new committer by the existing committers, this is current LFN’s 
policy

Thanks for your review
Best regards,

DENG Hui

From: Brian Hedstrom [mailto:brian.hedst...@oamtechnologies.com]
Sent: Saturday, July 7, 2018 3:38 AM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: GILBERT, MAZIN E (MAZIN E) 
mailto:ma...@research.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Regarding the following statement:
For modelspec doc, the committers: lingli deng, donghu, hanyanan, shitao li, 
maopeng zhang, Rittwik Jana, Sandeep Shah, Zhaoxing Meng, Zhong heliu

I don't feel this is an accurate list.  Since there is a lot of confusion about 
what's being done under the Modeling Project versus the Modeling Subcommittee, 
I feel that the list of committers above is omitting all the committers who've 
been working on the various Information Models and Data Models (for example, 
the VNF Package Model Sub-project efforts).  And as my earlier email asked, I'm 
not clear what is meant by modelspec.  Our committed resource, Jessie, for 
example has made significant model contributions, in addition to several 
resources from AT&T (among others as well).

Thanks
Brian

On Thu, Jul 5, 2018 at 8:44 PM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hi Mazin

Inline please == >

From: GILBERT, MAZIN E (MAZIN E) 
[mailto:ma...@research.att.com<mailto:ma...@research.att.com>]
Sent: Friday, July 6, 2018 6:58 AM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Thanks Deng.

Still need more clarification.

1. Are you running the Chair election for the Modeling subcommittee as well.
If so, please make a clear distinction between that and the project PTL 
election.
== > I have already sent email yesterday , there will be different election for 
committ

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[denghui (L)]

Hi Brian,

The Gerrit committers are different from Wiki page major contributors, they are 
contributing to Gerrit rst file for documentation based on the clean wiki page.

We are discussing to create papyrus folder from R3, once that has been done, 
then contributors who commit to Gerrit, those who are major contributor will be 
elected to as new committer by the existing committers, this is current LFN’s 
policy

Thanks for your review
Best regards,

DENG Hui

From: Brian Hedstrom [mailto:brian.hedst...@oamtechnologies.com]
Sent: Saturday, July 7, 2018 3:38 AM
To: denghui (L) 
Cc: GILBERT, MAZIN E (MAZIN E) ; 
onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Regarding the following statement:
For modelspec doc, the committers: lingli deng, donghu, hanyanan, shitao li, 
maopeng zhang, Rittwik Jana, Sandeep Shah, Zhaoxing Meng, Zhong heliu

I don't feel this is an accurate list.  Since there is a lot of confusion about 
what's being done under the Modeling Project versus the Modeling Subcommittee, 
I feel that the list of committers above is omitting all the committers who've 
been working on the various Information Models and Data Models (for example, 
the VNF Package Model Sub-project efforts).  And as my earlier email asked, I'm 
not clear what is meant by modelspec.  Our committed resource, Jessie, for 
example has made significant model contributions, in addition to several 
resources from AT&T (among others as well).

Thanks
Brian

On Thu, Jul 5, 2018 at 8:44 PM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hi Mazin

Inline please == >

From: GILBERT, MAZIN E (MAZIN E) 
[mailto:ma...@research.att.com<mailto:ma...@research.att.com>]
Sent: Friday, July 6, 2018 6:58 AM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Thanks Deng.

Still need more clarification.

1. Are you running the Chair election for the Modeling subcommittee as well.
If so, please make a clear distinction between that and the project PTL 
election.
== > I have already sent email yesterday , there will be different election for 
committee and project,
The community recommend to finish it by the end of Aug. we will do it.

2. I am concerned that the definition of committers is cloudy here.
You have docs and you have code. Committers who write codes
are not necessarily qualified to review and write code.
Therefore, it is important that you have a PTL who is qualified to commit
and understand code as well.
== > current Gerrit repos has already distinguished them for different right:
For toscaparser repo, the committers : maopeng zhao, Rittwik Jana, Serban Jora, 
Zhaoxing Meng.
For modelspec doc, the committers: lingli deng, donghu, hanyanan, shitao li, 
maopeng zhang, Rittwik Jana, Sandeep Shah, Zhaoxing Meng, Zhong heliu
For who will be PTL, let committers to decide.

Thanks a lot

DENG Hui

Appreciate the clarification.
Mazin




On Jul 5, 2018, at 9:48 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Hi Mazin

I guess that you know that PTL couldn’t remove the committer, I sent email to 
every committer after Release 1,
two of them email’s are not reachable, one agree to step down, so that’s the 
reason we removed 3 of them after the vote of all committers.
Others replied and said that they would like to continue.

Current committers are not only for tosca parser , but also for modelspec.

Thanks a lot

DENG Hui

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Thursday, July 5, 2018 9:20 PM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Thanks. I am assuming the project is based on the repo that is supporting the 
Tosca Parsers,
and you are tracking active committers.

Are you holding an election at the same time for the Chair subcommittee?

Mazin


On Jul 5, 2018, at 8:21 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Mazin

Yes it is modeling project PTL election other than modeling subcommittee.

You may have missed below email which does have the link to repositories
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-Modeling<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DModeling&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=h336thy4AQC9X1JMXCsyYKGnG9RZQiRvWQY-u54zaMI&s=ffAQ4YaMD5X0xX09fOLdQR9a4020jv33Vw3hzajOw

Re: [onap-tsc] Modeling Options Agenda Item Discussed Today at TSC Meeting

[denghui (L)]

Hello Eric,

Slide are available here:
https://wiki.onap.org/display/DW/TSC+2018-07-05+Meeting+Agenda

thanks a lot for kind review

DENG Hui

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Eric Debeau
Sent: Saturday, July 7, 2018 4:15 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Modeling Options Agenda Item Discussed Today at TSC Meeting

Hello

Where can we get the slides ?

I want to remind that we are in an open-source project to produce some code to 
answer service provider requirements.

I also want to raise some operational concerns about  the question: "Do we 
agree that we don't want the vendors to have to create ONAP-specific 
descriptors that conflict with standards? "
What are the standards ? Heat Orchestration Template is the de facto-standard 
for VNF to be deployed on OpenStack, Helm Chart is the de facto standard to 
deploy VNF to be deployed on K8S.

Using various VNF descriptors will require to get the associated tooling to:
- test VNF deployment on infra (eg it is easy to test VNF deployment on 
OpenStack using Heat template)
- validate VNF descriptor (VNF SDK & VVP tool must be adapted to test these 
various VNF descriptor flavors)

Best Regards

Eric

_



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.


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

View/Reply Online (#3321): https://lists.onap.org/g/ONAP-TSC/message/3321
Mute This Topic: https://lists.onap.org/mt/23175452/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] Call for agreement on lifecycle stereotype

[denghui (L)]

Hello, modelers,

This is a call for agreement on using the lifecycle stereotype according to the 
last call.
Information of the proposal can be found at 
https://wiki.onap.org/display/DW/Lifecycle+Stereotype+Proposal.

Agreements need to be reached across the modeling subcommittee are:

*   Agree on using lifecycle stereotype and following the definitions/state 
machine for the resource IM

*   Agree on adopting the same approach for other modeling areas

Deadline for this call is July 11th, PST 00:00. Please comment on the mailing 
list if you have any concerns.

Best regards,

DENG Hui

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

View/Reply Online (#3320): https://lists.onap.org/g/ONAP-TSC/message/3320
Mute This Topic: https://lists.onap.org/mt/23196969/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[denghui (L)]

Hi Brian,

I have just created a modeling governance page which explains the relationship 
among modeling subcommittee, modeling project and SDO coordinators.
https://wiki.onap.org/display/DW/Modeling+Governance
https://wiki.onap.org/display/DW/ONAP+Modeling+Governance

The same page which is under both modeling project and modeling subcommittee. I 
hope this page could help to answer your questions. Apologize that I haven’t 
done this early.

Thanks a lot for your kind review
Best regards,

DENG Hui

From: Brian Hedstrom [mailto:brian.hedst...@oamtechnologies.com]
Sent: Friday, July 6, 2018 3:55 AM
To: denghui (L) 
Cc: GILBERT, MAZIN E (MAZIN E) ; 
onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Deng,
What do you mean by "modelspec"?  The modeling project has the following scope 
and deliverables (I don't see Modeling Specifications listed which I thought 
was part of the Modeling Subcommittee):
Also, I didn't see your response to Mazin's question: Are you holding an 
election at the same time for the Chair subcommittee?
Scope:
·Modeling tools and converters
·Code - parsers (unified API interfaces) and tools (translators)
·Support Use cases of ONAP: vCPE, vVoLTE, vFW, et al.
Deliverables for release 1

Parsers and translators:
·Tosca Parsers
·YANG Parsers
·Tosca to Heat
·YANG to Tosca

Thanks
Brian

On Thu, Jul 5, 2018 at 7:48 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hi Mazin

I guess that you know that PTL couldn’t remove the committer, I sent email to 
every committer after Release 1,
two of them email’s are not reachable, one agree to step down, so that’s the 
reason we removed 3 of them after the vote of all committers.
Others replied and said that they would like to continue.

Current committers are not only for tosca parser , but also for modelspec.

Thanks a lot

DENG Hui

From: GILBERT, MAZIN E (MAZIN E) 
[mailto:ma...@research.att.com<mailto:ma...@research.att.com>]
Sent: Thursday, July 5, 2018 9:20 PM

To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Thanks. I am assuming the project is based on the repo that is supporting the 
Tosca Parsers,
and you are tracking active committers.

Are you holding an election at the same time for the Chair subcommittee?

Mazin


On Jul 5, 2018, at 8:21 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Mazin

Yes it is modeling project PTL election other than modeling subcommittee.

You may have missed below email which does have the link to repositories
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-Modeling<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DModeling&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=h336thy4AQC9X1JMXCsyYKGnG9RZQiRvWQY-u54zaMI&s=ffAQ4YaMD5X0xX09fOLdQR9a4020jv33Vw3hzajOwBA&e=>
the committers in modeling project are:
Hui Deng
Shitao Li
Rittwik Jana
Bruce Thompson
Maopeng Zhang
Zhaoxing Meng
Amir Levy
Arthur Berezin
Sandeep Shah
Ling Li
Liuhe Zhong
Yannan Han
Hu Dong
Serban Jora
Lingli Deng

I did send email to helpdesk to remove 3 of them from the list before based on 
the confirmation of project:
Bruce Thompson
Arthur Berezin
Ling Li

It seems that they are still here, I will send again to helpdesk
So the final qualified committers are:
Hui Deng
Shitao Li
Rittwik Jana
Maopeng Zhang
Zhaoxing Meng
Amir Levy
Sandeep Shah
Liuhe Zhong
Yannan Han
Hu Dong
Serban Jora
Lingli Deng

Thanks for your checking
Best regards,

DENG Hui


From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Thursday, July 5, 2018 7:35 PM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Deng,

I appreciate you holding an election for the PTL.

For the modeling project PTL election, we need each Chair to ensure they have 
vetted all
active committers before any election is taking place. Can you share the list of
active committers.

As outlined in the website the issue is different for the subcommittee modeling 
Chair.

It seems that you are initiating a PTL election and not a subcommittee modeling 
Chair election.
Please confirm, and share the list of active Committers who will be voting for 
the new PTL.

thanks
mazin







On Jul 4, 2018, at 2:14 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

D

[onap-tsc] [modeling] Time plan discussion for R3 modeling

[denghui (L)]

Hello Modelers

Due to M2 model freeze is quite approaching now, so I made below time plan 
proposal,

Option 1: By M2 July 26 Model Freeze (IM+DM)
*By July 10th, form an interest thread (at least 3 organizations and an 
owner) for each requirement
*By July 17th, finalize requirement description and IM proposal
*By July 20th, TSC approval for high level requirements
*By July 25th, finalize DM proposal
*By July 28th, TSC approval for IM/DM proposal

Option 2: M3 Aug 23 (if we postpone to M3 for model freeze)
*By July 17th, form an interest thread (at least 3 organizations and an 
owner) for each requirement
*By July 31th, finalize requirement description and IM proposal
*By Aug 3th, TSC approval for high level requirements
*By Aug 21th, finalize DM proposal
*By Aug 23 th, TSC approval for IM/DM proposal

Thanks a lot for your review and let's finalize next Tuesday. Escalator to TSC 
on Thursday.

Thanks a lot

DENG Hui

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

View/Reply Online (#3299): https://lists.onap.org/g/ONAP-TSC/message/3299
Mute This Topic: https://lists.onap.org/mt/23170922/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[denghui (L)]

Hi Mazin

Inline please == >

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Friday, July 6, 2018 6:58 AM
To: denghui (L) 
Cc: onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Thanks Deng.

Still need more clarification.

1. Are you running the Chair election for the Modeling subcommittee as well.
If so, please make a clear distinction between that and the project PTL 
election.
== > I have already sent email yesterday , there will be different election for 
committee and project,
The community recommend to finish it by the end of Aug. we will do it.

2. I am concerned that the definition of committers is cloudy here.
You have docs and you have code. Committers who write codes
are not necessarily qualified to review and write code.
Therefore, it is important that you have a PTL who is qualified to commit
and understand code as well.
== > current Gerrit repos has already distinguished them for different right:
For toscaparser repo, the committers : maopeng zhao, Rittwik Jana, Serban Jora, 
Zhaoxing Meng.
For modelspec doc, the committers: lingli deng, donghu, hanyanan, shitao li, 
maopeng zhang, Rittwik Jana, Sandeep Shah, Zhaoxing Meng, Zhong heliu
For who will be PTL, let committers to decide.

Thanks a lot

DENG Hui

Appreciate the clarification.
Mazin





On Jul 5, 2018, at 9:48 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Hi Mazin

I guess that you know that PTL couldn’t remove the committer, I sent email to 
every committer after Release 1,
two of them email’s are not reachable, one agree to step down, so that’s the 
reason we removed 3 of them after the vote of all committers.
Others replied and said that they would like to continue.

Current committers are not only for tosca parser , but also for modelspec.

Thanks a lot

DENG Hui

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Thursday, July 5, 2018 9:20 PM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Thanks. I am assuming the project is based on the repo that is supporting the 
Tosca Parsers,
and you are tracking active committers.

Are you holding an election at the same time for the Chair subcommittee?

Mazin


On Jul 5, 2018, at 8:21 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Mazin

Yes it is modeling project PTL election other than modeling subcommittee.

You may have missed below email which does have the link to repositories
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-Modeling<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DModeling&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=h336thy4AQC9X1JMXCsyYKGnG9RZQiRvWQY-u54zaMI&s=ffAQ4YaMD5X0xX09fOLdQR9a4020jv33Vw3hzajOwBA&e=>
the committers in modeling project are:
Hui Deng
Shitao Li
Rittwik Jana
Bruce Thompson
Maopeng Zhang
Zhaoxing Meng
Amir Levy
Arthur Berezin
Sandeep Shah
Ling Li
Liuhe Zhong
Yannan Han
Hu Dong
Serban Jora
Lingli Deng

I did send email to helpdesk to remove 3 of them from the list before based on 
the confirmation of project:
Bruce Thompson
Arthur Berezin
Ling Li

It seems that they are still here, I will send again to helpdesk
So the final qualified committers are:
Hui Deng
Shitao Li
Rittwik Jana
Maopeng Zhang
Zhaoxing Meng
Amir Levy
Sandeep Shah
Liuhe Zhong
Yannan Han
Hu Dong
Serban Jora
Lingli Deng

Thanks for your checking
Best regards,

DENG Hui


From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Thursday, July 5, 2018 7:35 PM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Deng,

I appreciate you holding an election for the PTL.

For the modeling project PTL election, we need each Chair to ensure they have 
vetted all
active committers before any election is taking place. Can you share the list of
active committers.

As outlined in the website the issue is different for the subcommittee modeling 
Chair.

It seems that you are initiating a PTL election and not a subcommittee modeling 
Chair election.
Please confirm, and share the list of active Committers who will be voting for 
the new PTL.

thanks
mazin









On Jul 4, 2018, at 2:14 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Dear ONAP Community and ONAP TSC,

As mandated by ONAP process, PTL elections must be held at least once a year.
You c

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[denghui (L)]

Hello all,

Due to US National holiday, let's extend the self-nomination period to July 
10th 2018 10:00 EST
Thanks a lot

DENG Hui



On Jul 4, 2018, at 2:14 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Dear ONAP Community and ONAP TSC,

As mandated by ONAP process, PTL elections must be held at least once a year.
You can read more details here: 
https://wiki.onap.org/display/DW/Annual+Community+Elections<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Annual-2BCommunity-2BElections&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Oej6QUk5p2KdqNEWySpOHA&m=aqtE2C1ZdfxIEpvFpsi-ywKvepAjMEEvXvpyXwKvr7o&s=1VOSZREkf7OvEcmx6COn9S0Mz80ACCfrmsVXjmhZwZs&e=>

if you are interested in this position, I invite you to submit your 
self-nomination for ONAP modeling project.

Important dates:
---
You have 2 days to submit your self-nomination from receipt of this email. (End 
by July 6th 2018 10:00 IST)

Election duration: July 6th 2018 12:00 IST -  July 11th 2018 12:00 IST
(from CVIS system, private email will be sent to all committers email id 
mentioned 
athttps://wiki.onap.org/display/DW/Resources+and+Repositories<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=XBYNhzlk2jx6nSVGWpJjJUhpTLxHynkr7bh6Vp5VOXU&s=odKqVMZCdJUsygPKUpW7Gk3KS-ALAv3Pe3CO5I_82Ls&e=>
 )

Election result: July 11th 2018 (will be announced in onap-discuss and onap-tsc 
mailing lists)



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

View/Reply Online (#3297): https://lists.onap.org/g/ONAP-TSC/message/3297
Mute This Topic: https://lists.onap.org/mt/23163968/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[denghui (L)]

Hi Mazin

I guess that you know that PTL couldn't remove the committer, I sent email to 
every committer after Release 1,
two of them email's are not reachable, one agree to step down, so that's the 
reason we removed 3 of them after the vote of all committers.
Others replied and said that they would like to continue.

Current committers are not only for tosca parser , but also for modelspec.

Thanks a lot

DENG Hui

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Thursday, July 5, 2018 9:20 PM
To: denghui (L) 
Cc: onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Thanks. I am assuming the project is based on the repo that is supporting the 
Tosca Parsers,
and you are tracking active committers.

Are you holding an election at the same time for the Chair subcommittee?

Mazin


On Jul 5, 2018, at 8:21 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Mazin

Yes it is modeling project PTL election other than modeling subcommittee.

You may have missed below email which does have the link to repositories
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-Modeling<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DModeling&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=h336thy4AQC9X1JMXCsyYKGnG9RZQiRvWQY-u54zaMI&s=ffAQ4YaMD5X0xX09fOLdQR9a4020jv33Vw3hzajOwBA&e=>
the committers in modeling project are:
Hui Deng
Shitao Li
Rittwik Jana
Bruce Thompson
Maopeng Zhang
Zhaoxing Meng
Amir Levy
Arthur Berezin
Sandeep Shah
Ling Li
Liuhe Zhong
Yannan Han
Hu Dong
Serban Jora
Lingli Deng

I did send email to helpdesk to remove 3 of them from the list before based on 
the confirmation of project:
Bruce Thompson
Arthur Berezin
Ling Li

It seems that they are still here, I will send again to helpdesk
So the final qualified committers are:
Hui Deng
Shitao Li
Rittwik Jana
Maopeng Zhang
Zhaoxing Meng
Amir Levy
Sandeep Shah
Liuhe Zhong
Yannan Han
Hu Dong
Serban Jora
Lingli Deng

Thanks for your checking
Best regards,

DENG Hui


From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Thursday, July 5, 2018 7:35 PM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Deng,

I appreciate you holding an election for the PTL.

For the modeling project PTL election, we need each Chair to ensure they have 
vetted all
active committers before any election is taking place. Can you share the list of
active committers.

As outlined in the website the issue is different for the subcommittee modeling 
Chair.

It seems that you are initiating a PTL election and not a subcommittee modeling 
Chair election.
Please confirm, and share the list of active Committers who will be voting for 
the new PTL.

thanks
mazin








On Jul 4, 2018, at 2:14 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Dear ONAP Community and ONAP TSC,

As mandated by ONAP process, PTL elections must be held at least once a year.
You can read more details here: 
https://wiki.onap.org/display/DW/Annual+Community+Elections<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Annual-2BCommunity-2BElections&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Oej6QUk5p2KdqNEWySpOHA&m=aqtE2C1ZdfxIEpvFpsi-ywKvepAjMEEvXvpyXwKvr7o&s=1VOSZREkf7OvEcmx6COn9S0Mz80ACCfrmsVXjmhZwZs&e=>

if you are interested in this position, I invite you to submit your 
self-nomination for ONAP modeling project.

Important dates:
---
You have 2 days to submit your self-nomination from receipt of this email. (End 
by July 6th 2018 10:00 IST)

Election duration: July 6th 2018 12:00 IST -  July 11th 2018 12:00 IST
(from CVIS system, private email will be sent to all committers email id 
mentioned 
athttps://wiki.onap.org/display/DW/Resources+and+Repositories<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=XBYNhzlk2jx6nSVGWpJjJUhpTLxHynkr7bh6Vp5VOXU&s=odKqVMZCdJUsygPKUpW7Gk3KS-ALAv3Pe3CO5I_82Ls&e=>
 )

Election result: July 11th 2018 (will be announced in onap-discuss and onap-tsc 
mailing lists)




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

View/Reply Online (#3283): https://lists.onap.org/g/ONAP-TSC/message/3283
Mute This Topic: https://lists.onap.org/mt/23163968/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

[denghui (L)]

Mazin

Yes it is modeling project PTL election other than modeling subcommittee.

You may have missed below email which does have the link to repositories
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-Modeling
the committers in modeling project are:
Hui Deng
Shitao Li
Rittwik Jana
Bruce Thompson
Maopeng Zhang
Zhaoxing Meng
Amir Levy
Arthur Berezin
Sandeep Shah
Ling Li
Liuhe Zhong
Yannan Han
Hu Dong
Serban Jora
Lingli Deng

I did send email to helpdesk to remove 3 of them from the list before based on 
the confirmation of project:
Bruce Thompson
Arthur Berezin
Ling Li

It seems that they are still here, I will send again to helpdesk
So the final qualified committers are:
Hui Deng
Shitao Li
Rittwik Jana
Maopeng Zhang
Zhaoxing Meng
Amir Levy
Sandeep Shah
Liuhe Zhong
Yannan Han
Hu Dong
Serban Jora
Lingli Deng

Thanks for your checking
Best regards,

DENG Hui


From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Thursday, July 5, 2018 7:35 PM
To: denghui (L) 
Cc: onap-disc...@lists.onap.org; ONAP-TSC@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Deng,

I appreciate you holding an election for the PTL.

For the modeling project PTL election, we need each Chair to ensure they have 
vetted all
active committers before any election is taking place. Can you share the list of
active committers.

As outlined in the website the issue is different for the subcommittee modeling 
Chair.

It seems that you are initiating a PTL election and not a subcommittee modeling 
Chair election.
Please confirm, and share the list of active Committers who will be voting for 
the new PTL.

thanks
mazin







On Jul 4, 2018, at 2:14 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Dear ONAP Community and ONAP TSC,

As mandated by ONAP process, PTL elections must be held at least once a year.
You can read more details here: 
https://wiki.onap.org/display/DW/Annual+Community+Elections<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Annual-2BCommunity-2BElections&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Oej6QUk5p2KdqNEWySpOHA&m=aqtE2C1ZdfxIEpvFpsi-ywKvepAjMEEvXvpyXwKvr7o&s=1VOSZREkf7OvEcmx6COn9S0Mz80ACCfrmsVXjmhZwZs&e=>

if you are interested in this position, I invite you to submit your 
self-nomination for ONAP modeling project.

Important dates:
---
You have 2 days to submit your self-nomination from receipt of this email. (End 
by July 6th 2018 10:00 IST)

Election duration: July 6th 2018 12:00 IST -  July 11th 2018 12:00 IST
(from CVIS system, private email will be sent to all committers email id 
mentioned 
athttps://wiki.onap.org/display/DW/Resources+and+Repositories<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=XBYNhzlk2jx6nSVGWpJjJUhpTLxHynkr7bh6Vp5VOXU&s=odKqVMZCdJUsygPKUpW7Gk3KS-ALAv3Pe3CO5I_82Ls&e=>
 )

Election result: July 11th 2018 (will be announced in onap-discuss and onap-tsc 
mailing lists)



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

View/Reply Online (#3278): https://lists.onap.org/g/ONAP-TSC/message/3278
Mute This Topic: https://lists.onap.org/mt/23163968/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [onap-discuss] [modeling] ONAP R3 Modeling high level requirements

[denghui (L)]

Hello Jessie

Answer inline == >

From: jessie jewitt [mailto:jessie.jew...@oamtechnologies.com]
Sent: Wednesday, July 4, 2018 3:46 AM
To: denghui (L) 
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: Re: [onap-discuss] [modeling] ONAP R3 Modeling high level requirements

Hello DENG Hui,
  I think it has been beneficial to collect and review the modeling 
requirements for R3. Thank you for doing this. I have a few questions for you, 
if you would be so kind as to answer:

1. The requirements were supposed to be completed, according to the Casablanca 
Release Calendar, on 5/25. I haven't seen a poll, or anything, for the approval 
of these requirements. When do you anticipate they will be officially approved? 
I didn't see anything in the meeting minutes from today's meeting.
==> yesterday it was on the agenda, but due to other topics, we can’t have this 
part of discussion. In this case, we have to have discussion next Tuesday and 
start to poll right after if necessarily. I read through the comments on the 
wiki page, there is only 1 pending comment from your question about the 
consensus of service interest group, I am curious why don＇t you discuss them in 
that interest group, but challenge it in the modeling subcommittee, this way 
really slow down our progress

2. Again, according to the release calendar, we were to have established a 
"modeling plan" by 6/28. Does such a plan exist? If so, could you point me to 
where I can find it?
==> modeling plan is quite align with high level requirement, it will automate 
reflect the plan, we could use same contents for plan.

3. You indicated in the modeling subcommittee meeting this morning that our 
"model freeze" is in 3 weeks. With the requirements not yet agreed, and given 
the number of requirements currently specified, what is your expectation of 
what can actually be accomplished in 3 week's time?
== >  My suggestion is to postpone to M3 other than M2 for modeling freeze, I 
will bring this up to committee for discussion.

== > This is our 1st trial of procedure , we will revise it after this release 
accordingly.
Opensource normally follow 3 steps : plan , freeze and RC (API is not good 
reference for us)
Modeling subcommittee may need to align with them in next release.

Thank you

DENG Hui


Thank you,
Jessie

On Mon, Jun 25, 2018 at 3:15 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hello Kevin and all

I have created a high level requirements wiki page based on the input of 
Beijing event:
https://wiki.onap.org/display/DW/ONAP+R3+Modeling+High+Level+Requirements
Please help to contribute to the spreadsheet as soon as possible,
I also moved Kevin’s draft proposal under this wiki page for your reference:
https://wiki.onap.org/display/DW/Casablanca+High+Level+Modeling+Requirements+-+Draft

We are going to go through this wiki page this Tuesday, as the basis for our 
release planning.

I will create a separate wiki page for release planning of those requirements 
accordingly.

Thanks a lot

DENG Hui



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

View/Reply Online (#3274): https://lists.onap.org/g/ONAP-TSC/message/3274
Mute This Topic: https://lists.onap.org/mt/23037603/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] PTL Election announcement for ONAP modeling project

[denghui (L)]

Dear ONAP Community and ONAP TSC,

As mandated by ONAP process, PTL elections must be held at least once a year.
You can read more details here: 
https://wiki.onap.org/display/DW/Annual+Community+Elections

if you are interested in this position, I invite you to submit your 
self-nomination for ONAP modeling project.

Important dates:
---
You have 2 days to submit your self-nomination from receipt of this email. (End 
by July 6th 2018 10:00 IST)

Election duration: July 6th 2018 12:00 IST -  July 11th 2018 12:00 IST
(from CVIS system, private email will be sent to all committers email id 
mentioned at https://wiki.onap.org/display/DW/Resources+and+Repositories )

Election result: July 11th 2018 (will be announced in onap-discuss and onap-tsc 
mailing lists)

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

View/Reply Online (#3273): https://lists.onap.org/g/ONAP-TSC/message/3273
Mute This Topic: https://lists.onap.org/mt/23036777/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [modeling] ONAP R3 Modeling high level requirements

[denghui (L)]

Hello Kevin and all

I have created a high level requirements wiki page based on the input of 
Beijing event:
https://wiki.onap.org/display/DW/ONAP+R3+Modeling+High+Level+Requirements
Please help to contribute to the spreadsheet as soon as possible,
I also moved Kevin's draft proposal under this wiki page for your reference:
https://wiki.onap.org/display/DW/Casablanca+High+Level+Modeling+Requirements+-+Draft

We are going to go through this wiki page this Tuesday, as the basis for our 
release planning.

I will create a separate wiki page for release planning of those requirements 
accordingly.

Thanks a lot

DENG Hui

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

View/Reply Online (#3203): https://lists.onap.org/g/ONAP-TSC/message/3203
Mute This Topic: https://lists.onap.org/mt/22674362/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Modeling

[denghui (L)]

Sure, we will try

DENG Hui

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Thursday, June 21, 2018 12:20 PM
To: denghui (L) 
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: Re: Modeling

Thanks you. Also please share with the TSC what requirements your subcommittee 
generated so the TSC can assess the different views.

Mazin
On Jun 20, 2018, at 12:08 PM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hi Mazin

We will try to summarize the major disagreements and bring it to TSC in next 2 
weeks.

Thanks a lot

DENG Hui



From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Wednesday, June 20, 2018 11:33 AM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: Modeling

Deng Hui,

Thanks for your presentation today, and I really appreciate the modeling 
committee working together. Lots has been accomplished since R1.

I just wanted to articulate the conversation main points.

1. Modeling approaches for ONAP releases should be approved by the TSC. This 
should be documented and approved no later than M2.

2. If the modeling committee is unable to interlock on a common approach for 
offline, documentation or runtime, then different options should be brought to 
the TSC for review and making a decision.

Modeling directly impacts deployability. Disagreements impacting R3 should be 
documented and brought to the TSC over the next 2 weeks.

Thanks!
Mazin

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

View/Reply Online (#3201): https://lists.onap.org/g/ONAP-TSC/message/3201
Mute This Topic: https://lists.onap.org/mt/22463410/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Modeling

[denghui (L)]

Hi Mazin

We will try to summarize the major disagreements and bring it to TSC in next 2 
weeks.

Thanks a lot

DENG Hui



From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Wednesday, June 20, 2018 11:33 AM
To: denghui (L) 
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: Modeling

Deng Hui,

Thanks for your presentation today, and I really appreciate the modeling 
committee working together. Lots has been accomplished since R1.

I just wanted to articulate the conversation main points.

1. Modeling approaches for ONAP releases should be approved by the TSC. This 
should be documented and approved no later than M2.

2. If the modeling committee is unable to interlock on a common approach for 
offline, documentation or runtime, then different options should be brought to 
the TSC for review and making a decision.

Modeling directly impacts deployability. Disagreements impacting R3 should be 
documented and brought to the TSC over the next 2 weeks.

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

[onap-tsc] [modeling] Call for approval on the “obsolete legacy attributes/datatypes” proposal for the resource IM

[denghui (L)]

Hello all,

This is 1 week’s call for approval on the “obsolete legacy 
attributes/datatypes” proposal for the resource IM.
The intention is to mark several attributes/datatypes of the current model as 
“obsoleted” as their functionalities are covered by some other attributes.
Detailed information of the proposal can be found at: 
https://wiki.onap.org/display/DW/Obsolete+Legacy+Attributes , the proposed 
changes are marked in red.

Thanks a lot for your review
Best regards,

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

[onap-tsc] Casablanca release participation - modeling

[denghui (L)]

Dear TSC,

This email is to inform you that modeling project will to be part of ONAP 
Casablanca release.

Thanks

DENG Hui

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

Re: [onap-tsc] [modeling][cloud infrastructure]

[denghui (L)]

Hello modelers,

We are hoping that  people could raise the discussion point before next Tuesday 
modeling call in this list or wiki page, we will limit one point discussion 
time during our next call.

Thanks a lot

DENG Hui

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GUPTA, ARUN
Sent: Tuesday, May 22, 2018 11:20 PM
To: onap-disc...@lists.onap.org
Subject: [onap-discuss] [modeling][cloud infrastructure]



The Wiki pages for Cloud Infrastructure Modeling in general:
https://wiki.onap.org/pages/viewpage.action?pageId=33065694
and for Cloud Aggregation Classes:
https://wiki.onap.org/display/DW/Cloud+Infrastructure+Aggregate+Representation+Classes

The presentation used in today's (Tuesday May 22) Modeling Committee call is on 
the second page.


-Arun


Arun Gupta
Lead Member of Technical Staff
Domain 2 Architecture and Planning
200 S Laurel Ave - Bldg B, B5-3Z09
Middletown, NJ 07748
P: 732 420 6597
arungu...@att.com




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

[onap-tsc] [modeling] 20180522 meeting minutes of modeling subcommittee

[denghui (L)]

Hello all

This week has many follow-ups, so we post the meeting minutes again in the 
list, thanks
https://wiki.onap.org/display/DW/2018+1HModeling+sub-committee+meeting+agenda+and+minutes
please help to cast your vote on the new meeting time of Resource IM and DM 
respectively asap

thanks a lot

DENG Hui


1) R2 DM progress   Victor   5m

Victor is working with Dejan on this verification, finished today, will wait 
for SDC verification later this week.

2) Service IM   Lingli Deng 5m

M: Wednesday meeting



3) Resource IM  YANG Xu 5m

M:

3.1 ONAP feedback to ETSI last week, some further discussion will be needed in 
ONAP

3.2 please cast your vote on meeting time asap

Meeting Day/Time 
Poll



4) VES 6.0 update   Alok Gupta 10m

slide

M:

4.1 Some concern about the process of thsi spec, never discussed in modeling 
subcommittee, no IM, whehter papryus will be used



5) R3 DM Meeting  Day/Time Poll Anatoly 5m

R3 Data Model Meeting Day/Time 
Poll

M: 5.1 Please help to cast your vote asap



6) Multicloud infomation model  Ramki  25m

The Wiki pages for Cloud Infrastructure Modeling in general:

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

and for Cloud Aggregation Classes:

https://wiki.onap.org/display/DW/Cloud+Infrastructure+Aggregate+Representation+Classes

The presentation used in today's (Tuesday May 22) Modeling Committee call is on 
the second page.

M:

6.1 there was some concern to expose physical location,

6.2 Next week modeling will do it again

6.3 Please feedback in the mailling list on this topic before next week 
modeling call



7) Draft R3 Modeling Requirements Kevin 5m

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

[onap-tsc] [modeling] Help on ONAP R2 Data Modeling verification

[denghui (L)]

Hello all

We have more than 10-20 companies regularly to talk about ONAP modeling , but 
unfortunately we have only 2 coders contributing ONAP R2 modeling code 
contribution.
Victor has worked on this more than 1 week, and felt that he can’t do such huge 
work just by himself, so he has create below jira to invite more contributors

I create JIRA tickets to track the status for R2 DM 
Verification：

1.  
https://jira.onap.org/browse/SDC-1291

2.  
https://jira.onap.org/browse/SDC-1290

3.  
https://jira.onap.org/browse/SDC-1289

4.  
https://jira.onap.org/browse/SDC-1288
  Owner: Dejan from ericsson

5.  
https://jira.onap.org/browse/SDC-1287
  Owner: Dejan from ericsson

6.  
https://jira.onap.org/browse/SDC-1286
  Owner: Victor Gao

If you could help, please come and help on first 3 bullets.
Many thanks for your help

Best regards,

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

[onap-tsc] [modeling] Next week modeling call is cancel due to chinese holiday

[denghui (L)]

Hello all

Next Monday and Tuesday are Chinese holiday, so we cancelled Tuesday call, 
service/resource call will continue on Wednesday and Friday.
Fortunately we have two companies are contributing the code for our release 2 
modeling DM.

I will send the request to LF to cancel it.

Thanks

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

[onap-tsc] [modeling] Request for last call for comment on WAN service proposal

[denghui (L)]

Hello all

Per service call discussion yesterday, this is 2 weeks call for comment on WAN 
service proposal
https://wiki.onap.org/display/DW/WanService

the discussion minutes and slides for related discussions and calls are 
documented here
https://wiki.onap.org/pages/viewpage.action?pageId=28381459

Thanks,

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

[onap-tsc] [modeling] Invite feedback on R3 DM proposal

[denghui (L)]

Hello Modelers,

In order to get sufficient discussion in the beginning other than before the 
deadline, we would like to invite each company to feedback to Anatoly on your 
view.
https://wiki.onap.org/display/DW/Why+does+R3+need+multiple+DMs
Please either send your view in this wiki page or send to the list.

Especially those related company in R2 
Ericsson/Nokia/Netcracker/ZTE/Huawei/Intel/ARM/Amdocs/Operators.
Then we could discuss it again in the coming weekly call,

Thanks a lot

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

[onap-tsc] [modeling] this week modeling call will be cancelled

[denghui (L)]

Hello modelers

Lots of people reach me that due to China SDN/NFV conference, we would like to 
cancel this week regular weekly modeling call

1)  For service call, #1 will be started this Friday

2)  For resource IM, please help to comment on the link: 
https://wiki.onap.org/display/DW/Class+vs+Datatype+Categorization

3)  For resource DM, please help to comment on the link : 
https://wiki.onap.org/display/DW/Why+does+R3+need+multiple+DMs

Thanks a lot for your help
Best regards,

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

[onap-tsc] [modeling] Invite feedback on R3 DM proposal

[denghui (L)]

Hello Modelers,

In order to get sufficient discussion in the beginning other than before the 
deadline, we would like to invite each company to feedback to Anatoly on your 
view.
https://wiki.onap.org/display/DW/Why+does+R3+need+multiple+DMs
Please either send your view in this wiki page or send to the list.

Especially those related company in R2 
Ericsson/Nokia/Netcracker/ZTE/Huawei/Intel/ARM/Amdocs/Operators.
Then we could discuss it again in the coming weekly call,

Thanks a lot

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

[onap-tsc] [modeling] Resource Information Model - Class vs Datatype Categorization call for comments

[denghui (L)]

Dear All,

Here's a call for comment on the class vs datatype categorization issue of the 
resource IM.

Current resource information model 
(https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version) has all 
objects categorized as "class".
There are comments stating that some of them should be "Datatype" instead of 
"Class".

During the resource IM call, the participants have agreed to use the 
categorization in ETSI IFA015 v2.4.1 as a basis for discussion.
More information can be found on the following wiki page:
https://wiki.onap.org/display/DW/Class+vs+Datatype+Categorization

We would like to have one week's time to collect feedback from the community. 
Please comment on the wiki page above if you have any concern with the current 
proposal.
Objects with no comment will be categorized accordingly, and those with 
comments will be discussed in the following calls.

BR,

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

Re: [onap-tsc] Casablanca Timeline

[denghui (L)]

Hi Srini,

Current proposal has already moved frozen time 2 months earlier than R1/R2, to 
be honest, we haven't see any challenges during R1/R2 implementations.
And also modeling plan established is M1, then we freeze it immediately, how 
modeling committee could work.

My recommendation is to let's try current proposal as it is, and come back in 
R3 whether we should improve it.

Thanks a lot for your discussion

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Addepalli, Srinivasa R
Sent: Friday, April 13, 2018 10:17 PM
To: Gildas Lanilis ; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Casablanca Timeline

Yes Gildas.

Since scope, timelines and milestones are all inter-linked, I brought this up. 
Not to put Modeling team in the focus here, it would be good if Model freeze 
happen 4 weeks earlier :).  That will give enough time to move to TOSCA in 
various projects.

Thanks
Srini




From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Thursday, April 12, 2018 1:54 PM
To: Addepalli, Srinivasa R ; 
onap-tsc@lists.onap.org
Cc: TALASILA, MANOOP (MANOOP) ; Bainbridge, David 
; Ethan Lynn ; DRAGOSH, PAMELA L 
(PAM) ; Beejal Shah ; 
friedel.ke...@orange.com; Lefevre, Catherine 
Subject: RE: Casablanca Timeline

Hi Srini,

This is certainly a very good scope question.
As per the ONAP release milestone process, the functionalities scoped in at M1 
"Release Planning" for a  given release have to be implemented by "M4 Code 
Freeze".

Working ahead, whenever possible, is certainly a good approach if timing is an 
issue.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Addepalli, Srinivasa R [mailto:srinivasa.r.addepa...@intel.com]
Sent: Thursday, April 12, 2018 10:55 AM
To: Gildas Lanilis 
mailto:gildas.lani...@huawei.com>>; 
onap-tsc@lists.onap.org
Cc: TALASILA, MANOOP (MANOOP) 
mailto:talas...@research.att.com>>; Bainbridge, 
David mailto:dbain...@ciena.com>>; Ethan Lynn 
mailto:ethanly...@vmware.com>>; DRAGOSH, PAMELA L (PAM) 
mailto:pdrag...@research.att.com>>; Beejal Shah 
mailto:beejal.s...@amdocs.com>>; 
friedel.ke...@orange.com; Lefevre, Catherine 
mailto:cl6...@intl.att.com>>
Subject: RE: Casablanca Timeline

Hi,

I can't make it at 7:00AM PST due to a conflict.

I have one clarification question.

As I understand TOSCA DM Model is expected to be finalized by 08/30.  This 
gives around 3 to 4 weeks' time to complete the implementation in various ONAP 
project to reach code freeze milestone.  My question : Is the expectation that 
all relevant ONAP projects implement logic to enable TOSCA based orchestration 
in Casablanca?

Thanks
Srini


-Original Appointment-
From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Thursday, April 12, 2018 10:48 AM
To: onap-tsc@lists.onap.org
Cc: TALASILA, MANOOP (MANOOP); Bainbridge, David; Ethan Lynn; DRAGOSH, PAMELA L 
(PAM); Beejal Shah; friedel.ke...@orange.com; 
Lefevre, Catherine
Subject: [onap-tsc] Casablanca Timeline
When: Friday, April 13, 2018 7:00 AM-8:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://zoom.us/j/2229355644


Meeting Update: I got multiple requests to arrange this meeting 1 hour earlier 
starting at 7 am PDT. I understand this is kind of short notice and that 
everyone can't make it.
Please post your feedback in wiki at 
https://wiki.onap.org/display/DW/Release+Planning
Thanks,
Gildas
=

Hi All,

This is to follow up with TSC meeting to discuss Casablanca Timeline and the 
following items:
1.  Pair-wise testing
2.  CI-CD
3.  Offset milestone
4.  E2E Deployment code freeze (including upgrade)

In the meantime, feel free to post your comments in wiki page at 
https://wiki.onap.org/display/DW/Release+Planning

Thanks,
Gildas
[??]



Hi there,



Gildas Lanilis is inviting you to a scheduled Zoom meeting.



Join Zoom Meeting



Phone one-tap:

US: +16465588656,,2229355644# or 
+16699006833,,2229355644#



Meeting URL:

https://zoom.us/j/2229355644



Join by Telephone



For higher quality, dial a number based on your current location.



Dial:


US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 
369 0926 (Toll Free)



Meeting ID:

222 935 5644



International numbers
















  << File: ONAPCasablancaTimelineV2.pptx >>  << File: ATT1.txt >>

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

[onap-tsc] [modeling] ONAP Modeling spec timeline changed

[denghui (L)]

Hello modelers

We had twice presentations from Kevin in Model/Arc about proposing modeling 
spec coming out early as below link:
https://wiki.onap.org/download/attachments/16003450/ONAP%20Process%20Proposed%20Updates%202018-03-21.pdf?api=v2
https://wiki.onap.org/display/DW/Proposed+ONAP+Release+Process+Updates+for+Information+and+Data+Modeling

Based on this new proposal, modeling spec will become freeze in M2 deadline, 
that will be about 2 months earlier than our R2 progress especially for DM
In R3 it is about August,

Secondly there are some requirement about code contribution mandate for model 
spec proposal
M2 Note:  Development Commitments for Infomodel Requirements?

Please feel free to let us know if you have comments here.

Thanks a lot

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

[onap-tsc] [modeling] ONAP Sunday afternoon modeling session in ONS 2018 @ Sun Mar 25, 2018 1pm - 7pm (PDT) (denghu...@huawei.com)

[denghui (L)]

This is the bridge for remote presenter on Sunday.

Thanks

DENG Hui
BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 15.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:Romance Standard Time
BEGIN:STANDARD
DTSTART:16011028T03
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010325T02
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ATTACH;ENCODING=BASE64;VALUE=BINARY;X-FILENAME=invite.ics:QkVHSU46VkNBTEVOR
	EFSDQpQUk9ESUQ6LS8vR29vZ2xlIEluYy8vR29vZ2xlIENhbGVuZGFyIDcwLjkwNTQvL0VODQp
	WRVJTSU9OOjIuMA0KQ0FMU0NBTEU6R1JFR09SSUFODQpNRVRIT0Q6UkVRVUVTVA0KQkVHSU46V
	kVWRU5UDQpEVFNUQVJUOjIwMTgwMzI1VDIwMDAwMFoNCkRURU5EOjIwMTgwMzI2VDAyMDAwMFo
	NCkRUU1RBTVA6MjAxODAzMjNUMDAwMzExWg0KT1JHQU5JWkVSO0NOPU9OQVAgTWVldGluZ3MgY
	W5kIEV2ZW50czptYWlsdG86bGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzDQogdWM4Zjc
	2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tDQpVSUQ6MTgzZmZmZTZkYjF0d
	GJ1dThtaW5mdWFlYzRAZ29vZ2xlLmNvbQ0KQVRURU5ERUU7Q1VUWVBFPUlORElWSURVQUw7Uk9
	MRT1SRVEtUEFSVElDSVBBTlQ7UEFSVFNUQVQ9TkVFRFMtQUNUSU9OO1JTVlA9DQogVFJVRTtDT
	j1kZW5naHVpMTJAaHVhd2VpLmNvbTtYLU5VTS1HVUVTVFM9MDptYWlsdG86ZGVuZ2h1aTEyQGh
	1YXdlaS5jb20NCkNSRUFURUQ6MjAxODAzMjNUMDAwMjI0Wg0KREVTQ1JJUFRJT046SGkgdGhlc
	mVcLCBcblxuT05BUCBNZWV0aW5nIDUgaXMgaW52aXRpbmcgeW91IHRvIGEgc2NoZWR1bGVkIFp
	vDQogb20gbWVldGluZy4gXG5cbkpvaW4gZnJvbSBQQ1wsIE1hY1wsIExpbnV4XCwgaU9TIG9yI
	EFuZHJvaWQ6IGh0dHBzOi8vem9vbS51DQogcy9qLzg4MjQ0MjYxOFxuXG5PciBpUGhvbmUgb25
	lLXRhcCA6XG4gICAgVVM6ICsxNjQ2NTU4ODY1NlwsXCw4ODI0NDI2MTgjICBvDQogciArMTY2O
	TkwMDY4MzNcLFwsODgyNDQyNjE4IyBcbk9yIFRlbGVwaG9uZTpcbiAgICBEaWFsKGZvciBoaWd
	oZXIgcXVhbGl0eVwsDQogIGRpYWwgYSBudW1iZXIgYmFzZWQgb24geW91ciBjdXJyZW50IGxvY
	2F0aW9uKTogXG4gICAgICAgIFVTOiArMSA2NDYgNTU4IDg2DQogNTYgIG9yICsxIDY2OSA5MDA
	gNjgzMyAgb3IgKzEgODU1IDg4MCAxMjQ2IChUb2xsIEZyZWUpIG9yICsxIDg3NyAzNjkgMDkyN
	iAoDQogVG9sbCBGcmVlKVxuICAgIE1lZXRpbmcgSUQ6IDg4MiA0NDIgNjE4XG4gICAgSW50ZXJ
	uYXRpb25hbCBudW1iZXJzIGF2YWlsYWJsDQogZTogaHR0cHM6Ly96b29tLnVzL3pvb21jb25mZ
	XJlbmNlP209Q0RZX2Vub2k5RHY0NGp5YzM3V04zRUtCUFpfMjIwbUJcblxuXG5cDQogbi06On4
	6fjo6fjp+On46fjp+On46fjp+On46fjp+On46fjp+On46fjp+On46fjp+On46fjp+On46fjp+O
	n46fjp+On46fjp+On46DQogfjp+On46On46fjo6LVxuUGxlYXNlIGRvIG5vdCBlZGl0IHRoaXM
	gc2VjdGlvbiBvZiB0aGUgZGVzY3JpcHRpb24uXG5cblZpZXcgDQogeW91ciBldmVudCBhdCBod
	HRwczovL3d3dy5nb29nbGUuY29tL2NhbGVuZGFyL2V2ZW50P2FjdGlvbj1WSUVXJmVpZD1NVGd
	6Wm1aDQogbVpUWmtZakYwZEdKMWRUaHRhVzVtZFdGbFl6UWdaR1Z1WjJoMWFURXlRR2gxWVhkb
	GFTNWpiMjAmdG9rPU56SWpiR2x1ZFhobWIzDQogVnVaR0YwYVc5dUxtOXlaMTh4Y20xMFlqVjB
	jSEl6ZFdNNFpqYzJabTFtYkhCc2IyazRPRUJuY205MWNDNWpZV3hsYm1SaGNpNW5iDQogMjluY
	kdVdVkyOXROamxpTnpJMVptUTNZamcwWTJOak1UQXhPR1F6WXpCbVpHUXdZMlppTUdRelpHVTF
	NV1l3TWcmY3R6PUFtZXJpDQogY2ElMkZMb3NfQW5nZWxlcyZobD1lbiZlcz0xLlxuLTo6fjp+O
	jp+On46fjp+On46fjp+On46fjp+On46fjp+On46fjp+On46fjp+DQogOn46fjp+On46fjp+On4
	6fjp+On46fjp+On46fjp+On46fjo6fjp+OjotDQpMQVNULU1PRElGSUVEOjIwMTgwMzIzVDAwM
	DMxMVoNCkxPQ0FUSU9OOmh0dHBzOi8vem9vbS51cy9qLzg4MjQ0MjYxOA0KU0VRVUVOQ0U6MA0
	KU1RBVFVTOkNPTkZJUk1FRA0KU1VNTUFSWTpPTkFQIFN1bmRheSBhZnRlcm5vb24gbW9kZWxpb
	mcgc2Vzc2lvbiBpbiBPTlMgMjAxOA0KVFJBTlNQOk9QQVFVRQ0KRU5EOlZFVkVOVA0KRU5EOlZ
	DQUxFTkRBUg0K
ATTENDEE;CN="denghui (L)";RSVP=TRUE:mailto:denghu...@huawei.com
CLASS:PUBLIC
CREATED:20180323T072236Z
DESCRIPTION:more details » <https://www.google.com/calendar/event?action=V
	IEW&eid=MTgzZmZmZTZkYjF0dGJ1dThtaW5mdWFlYzQgZGVuZ2h1aTEyQGh1YXdlaS5jb20&to
	k=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91
	cC5jYWxlbmRhci5nb29nbGUuY29tNjliNzI1ZmQ3Yjg0Y2NjMTAxOGQzYzBmZGQwY2ZiMGQzZG
	U1MWYwMg&ctz=America%2FLos_Angeles&hl=en&es=0> \n\nONAP Sunday afternoon m
	odeling session in ONS 2018\nWhen	Sun Mar 25\, 2018 1pm – 7pm Pacific Ti
	me	\nWhere	https://zoom.us/j/882442618 (map <https://www.google.com/url?q=
	https%3A%2F%2Fzoom.us%2Fj%2F882442618&sa=D&usd=2&usg=AFQjCNGcNpykg7m1otfbP
	j317UctpeEy2w> )	\nCalendar	denghu...@huawei.com	\nWho	•	kpaul@linuxfoun
	dation.org - creator	\n•	denghu...@huawei.com	\n	\nHi there\, \nONAP Mee
	ting 5 is inviting you to a scheduled Zoom meeting. \nJoin from PC\, Mac\,
	 Linux\, iOS or Android: https://zoom.us/j/882442618 <https://www.google.c
	om/url?q=https%3A%2F%2Fzoom.us%2Fj%2F882442618&sa=D&usd=2&usg=AFQjCNGcNpyk
	g7m1otfbPj317UctpeEy2w> \nOr iPhone one-tap :\nUS: +16465588656\,\,8824426
	18# or +16699006833\,\,882442618# \nOr Telephone:\nDial(for higher quality
	\, dial a number based on your current location): \nUS: +1 646 558 8656 or
	 +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll F
	ree)\nMeeting ID: 882 442 618\nInternational numbers available: https://zo
	om.us/zoomconference?m=CDY_enoi9Dv44jyc37WN3EKBPZ_220mB <https://www.googl
	e.com/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3DCDY_enoi9Dv44jyc3
	7WN3EKBPZ_220mB&

[onap-tsc] [modeling] Venue of ONAP modeling Sunday afternoon workshop has been finalized

[denghui (L)]

Hello all

As you have already know that, we will have Sunday afternoon and Friday morning 
two days workshop
https://wiki.onap.org/display/DW/ONAP+Sunday+afternoon+modeling+session+in+ONS+2018
https://wiki.onap.org/display/DW/ONAP+Friday+morning+modeling+session+in+ONS+2018
Please everybody help to register for those events asap

and the venue of Sunday afternoon will be :
Sheraton Gateway LAX
6101 W Century Blvd
Los Angeles, CA 90045
http://www.sheratonlax.com
Meeting Room: Gateway Ballroom (Lobby Level)

Please know that only coffee and beverages will be served (no lunch).

Many thanks to MEF for kind sponsorship
Best regards,

DENG Hui

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

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

[denghui (L)]

Hello Jessie,

ONAP resource DM proposals have been on table for the long time and discussed 
and polled couple of time about which direction.
I am not familiar about this new work which has never been discussed in our 
committee.

At this moment, the urgent thing is not only do DM spec, but also contribute 
the code to R2, that is the joint JIRA TASK which has been distributed among 5 
companies already.
If you could help to contribute the code, please kindly help to consider to 
contribute the left of them: No.4 and No.7

Thanks a lot for your contribution
Best regards,

DENG Hui

From: jessie jewitt [mailto:jessie.jew...@oamtechnologies.com]
Sent: Friday, March 9, 2018 1:26 AM
To: denghui (L) 
Cc: onap-disc...@lists.onap.org; onap-tsc ; Rittwik 
Jana 
Subject: Re: [onap-discuss] [modeling] ONAP R2 IM to DM design

Hello-
I don't remember this being an action out of the modelling committee 
meeting yesterday. How does it compare to the action item from another meeting 
that Alex, Thinh, Anatoly and myself took to work on the IM to DM model 
mapping, and the mappings that have already been proposed (and commented on) 
here:

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

Could you please clarify.
Thank you,
Jessie

On Thu, Mar 8, 2018 at 4:46 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
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-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-discuss

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

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

[denghui (L)]

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-disc...@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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

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

[denghui (L)]

Hello Andrei,

It's really hard to keep the synchronization between SDO and OSS, they have 
different paces,
ONAP is working for Release time frame restriction.

Thanks a lot

DENG Hui

From: Andrei Kojukhov [mailto:andrei.kojuk...@amdocs.com]
Sent: Thursday, March 8, 2018 8:59 PM
To: denghui (L) ; onap-disc...@lists.onap.org; onap-tsc 

Cc: Rittwik Jana ; Lishitao ; 
MAYER, ANDREW J 
Subject: RE: [modeling] ONAP R2 IM to DM design

Hello Deng Hui, Andy,

As the topics 1 -  6 are more or less covered (or in the process of finalizing) 
by the ETSI GS NFV-SOL001 so it would not be a big deal to re-use the TOSCA 
constructs from there.

However the topic # 7 is not covered (and not planned to be covered) by SOL001 
so to my understanding we really have an issue. I'm aware of existence of TOSCA 
based monitoring definitions done by AT&T team and I was requested to 
contribute it in ETSI SOL but this contribution may take time.

BR

Andrei

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Thursday, March 08, 2018 2:46 PM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Cc: Rittwik Jana mailto:rittwik.j...@gmail.com>>
Subject: [onap-tsc] [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
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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] [modeling] ONAP R2 IM to DM design

[denghui (L)]

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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-discuss] URGENT - Modeling Subcommittee meeting minutes from March 6th meeting...

[denghui (L)]

Hi Thinh

It is output of meeting, but we did hear your disagreement, and we also 
questioned whether you and Nokia could contribute all implementation for SOL001 
into ONAP SDC/VNFSDK/VFC/SO projects or not, we haven’t heard any reply yet.

Thanks a  lot

DENG Hui

From: Nguyenphu, Thinh (Nokia - US/Irving) [mailto:thinh.nguyen...@nokia.com]
Sent: Wednesday, March 07, 2018 11:29 PM
To: Vul, Alex; denghui (L); Gadiyar, Rajesh; Addepalli, Srinivasa R; 
onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Cc: GILBERT, MAZIN E (MAZIN E); Katzman, Anatoly
Subject: RE: [onap-discuss] URGENT - Modeling Subcommittee meeting minutes from 
March 6th meeting...

Hi Deng Hui,

This statement in meeting note is not correct either.

“2) will update onap type with TOSCA NFV profile, and”

We did not agreed to update onap types with TOSCA NFV profile 
(tosca-nfv-profile-wd05-rev03). The tosca-nfv-profile-wd05-rev03 is out of date 
and no long align with ONAP R2 IM. The correct mapping should be SOL001 v.0.6.0 
(a draft is available and  expect to be public available in 3 days from now).

SOL001 v0.6.0 includes update on all of nodes, datatypes, capabilities types 
and HPA with all of the data types. in addition, it has all of the TOSCA types 
for support single deployment too.

Would please update the meeting note and if need further discussion, my 
recommendation is to assign the topic for next week call again.

Regards,
Thinh

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vul, Alex
Sent: Wednesday, March 07, 2018 7:04 AM
To: denghui (L) mailto:denghu...@huawei.com>>; Gadiyar, 
Rajesh mailto:rajesh.gadi...@intel.com>>; Addepalli, 
Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Cc: GILBERT, MAZIN E (MAZIN E) 
mailto:ma...@research.att.com>>; Katzman, Anatoly 
mailto:ak4...@intl.att.com>>
Subject: [onap-discuss] URGENT - Modeling Subcommittee meeting minutes from 
March 6th meeting...

Dear Deng Hui,

The meeting minutes appear to be incorrect…


Item 4) under the 1) DM incorrectly states that…

4) will work on improve R3 modeling spec before end of Beijing release

Extra addition related to IM+(including HPA) will be added later

As I understand it, the above statement alleges that we agreed to postpone the 
HPA modeling extensions until R3. Is this correct?

I am afraid we never agreed to postpone the implementation of HPA until after 
R2. In fact, if I remember correctly, when asked if anyone had any objections 
to implementing HPA in R2, no one on the call raised any objections. Having 
talked to Anatoly, my understanding is that he never agreed to exclude the HPA 
model extensions from R2 either.

Once again, HPA is an agreed upon functional requirement to be implemented in 
ONAP R2. HPA has gone through the public review. HPA information and data model 
extensions need to be considered as part of R2

The HPA modeling extensions are based on the same industry standard information 
model as ONAP IM R2+  �C ETSI IFA011 v2.4.1. The HPA modeling extensions can 
added to either the NFV profile based data model or a ETSI SOL001 based data 
model.

If the community decision is to use the NFV Profile based data model so be it. 
We will add the HPA related data types, node types and attributes to what 
Victor uploaded on the Wiki, under the NFV Profile model and move on. The 
implementation of HPA in R2 is on-going…

In the future, I would suggest that we record the Modeling Subcommittee 
meetings. This way we can avoid any misunderstandings like this from happening…

Kind regards,

Alex Vul
Intel Corporation
20180306 Meeting agenda and Minutes

1) DM: Anatoly Katzman

●Victor’s proposal will be agreed �C TOSCA NFV profile plus R2 IM+

https://<https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile>wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile<https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile>

Note: need to confirm whether onboarding has any issue, if fail then need to 
fall back to R1 solution.

1) will keep onap type and heat type both folders, and

2) will update onap type with TOSCA NFV profile, and

3) will best effort to let 2 use cases use it, if fail, and will fall back to 
heat type , and

4) will work on improve R3 modeling spec before end of Beijing release

Extra addition related to IM+(including HPA) will be added later

2)Resource IM:Xu Yang
3)Service IM/DM:Lingli Deng & Maopeng (Wednesday call)
4)Modeling workshop in ONS 2017

5) If time allows:

  Modeling spec Papyrus:  Jessie Jewitt

  Modeling tools:   Nigel Davis

  Parser:  Atul Purohit

  A&AIJam

Re: [onap-tsc] URGENT - Modeling Subcommittee meeting minutes from March 6th meeting...

[denghui (L)]

Dear Alex

You misunderstand “later” , it doesn’t mean R3, but means later next week.
The slide is final output among us, no word changes.

DENG Hui

From: Vul, Alex [mailto:alex@intel.com]
Sent: Wednesday, March 07, 2018 9:04 PM
To: denghui (L); Gadiyar, Rajesh; Addepalli, Srinivasa R; 
onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Cc: GILBERT, MAZIN E (MAZIN E); Katzman, Anatoly; SHADMI, DAVID
Subject: URGENT - Modeling Subcommittee meeting minutes from March 6th 
meeting...

Dear Deng Hui,

The meeting minutes appear to be incorrect…


Item 4) under the 1) DM incorrectly states that…

4) will work on improve R3 modeling spec before end of Beijing release

Extra addition related to IM+(including HPA) will be added later

As I understand it, the above statement alleges that we agreed to postpone the 
HPA modeling extensions until R3. Is this correct?

I am afraid we never agreed to postpone the implementation of HPA until after 
R2. In fact, if I remember correctly, when asked if anyone had any objections 
to implementing HPA in R2, no one on the call raised any objections. Having 
talked to Anatoly, my understanding is that he never agreed to exclude the HPA 
model extensions from R2 either.

Once again, HPA is an agreed upon functional requirement to be implemented in 
ONAP R2. HPA has gone through the public review. HPA information and data model 
extensions need to be considered as part of R2

The HPA modeling extensions are based on the same industry standard information 
model as ONAP IM R2+  �C ETSI IFA011 v2.4.1. The HPA modeling extensions can 
added to either the NFV profile based data model or a ETSI SOL001 based data 
model.

If the community decision is to use the NFV Profile based data model so be it. 
We will add the HPA related data types, node types and attributes to what 
Victor uploaded on the Wiki, under the NFV Profile model and move on. The 
implementation of HPA in R2 is on-going…

In the future, I would suggest that we record the Modeling Subcommittee 
meetings. This way we can avoid any misunderstandings like this from happening…

Kind regards,

Alex Vul
Intel Corporation
20180306 Meeting agenda and Minutes

1) DM: Anatoly Katzman

●Victor’s proposal will be agreed �C TOSCA NFV profile plus R2 IM+

https://<https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile>wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile<https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile>

Note: need to confirm whether onboarding has any issue, if fail then need to 
fall back to R1 solution.

1) will keep onap type and heat type both folders, and

2) will update onap type with TOSCA NFV profile, and

3) will best effort to let 2 use cases use it, if fail, and will fall back to 
heat type , and

4) will work on improve R3 modeling spec before end of Beijing release

Extra addition related to IM+(including HPA) will be added later

2)Resource IM:Xu Yang
3)Service IM/DM:Lingli Deng & Maopeng (Wednesday call)
4)Modeling workshop in ONS 2017

5) If time allows:

  Modeling spec Papyrus:  Jessie Jewitt

  Modeling tools:   Nigel Davis

  Parser:  Atul Purohit

  A&AIJames Forsyth

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

[onap-tsc] [modeling] ONAP modeling session registration in ONS 2017

[denghui (L)]

Hello all

As we discussed yesterday modeling call, we create two wiki page for 2 onap 
modeling session on Sunday afternoon and Friday monning,
If you are able to attend, please fill in your info to the registration 
spreadsheet, really thanks LFN and MEF sponsor them
Sunday afternoon: 
https://wiki.onap.org/display/DW/ONAP+Sunday+afternoon+modeling+session+in+ONS+2018
Friday morning: 
https://wiki.onap.org/display/DW/ONAP+Friday+morning+modeling+session+in+ONS+2018

Thanks a lot for your help

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

Re: [onap-tsc] [modeling]Poll on modeling workshop in ONS 2018

[denghui (L)]

Reminder

From: denghui (L)
Sent: Wednesday, February 28, 2018 9:33 AM
To: onap-disc...@lists.onap.org; onap-tsc 
Subject: [modeling]Poll on modeling workshop in ONS 2018

Hello all

Please cast your vote on the date of workshop for modeling workshop in ONS 2018
https://doodle.com/poll/a95qs5bg5fwmskdg

Thanks a lot

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