Re: [onap-modelingsub] [onap-discuss] Agreements on Montreal offline discussion of Resource IM and Service IM

[denghui (L)]

Hi Kenny and Andy,

All those breakout offline discussion will be discussed in general session 
formally this afternoon, Chesla and Kevin, please join the discussion this 
afternoon from 4:30,

Thanks a lot for your help
Best regards,

DENG Hui

From: MAYER, ANDREW J [mailto:am8...@att.com]
Sent: Tuesday, October 30, 2018 1:14 PM
To: onap-modeling...@lists.onap.org; onap-discuss@lists.onap.org; SCAGGS, KEVIN 
; WECHSLER, CHESLA C ; denghui (L) 

Cc: HALLAHAN, RYAN 
Subject: Re: [onap-modelingsub] [onap-discuss] Agreements on Montreal offline 
discussion of Resource IM and Service IM

Thanks for clearing this up Kenny.
Best Regards,
Andy



From: "Kenny Paul" mailto:kp...@linuxfoundation.org>>
Date: Tuesday, October 30, 2018 at 10:08:32 AM
To: "onap-modeling...@lists.onap.org<mailto:onap-modeling...@lists.onap.org>" 
mailto:onap-modeling...@lists.onap.org>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "SCAGGS, 
KEVIN" mailto:ks0...@att.com>>, "WECHSLER, CHESLA C" 
mailto:cw1...@att.com>>, "'denghui (L)'" 
mailto:denghu...@huawei.com>>
Cc: "HALLAHAN, RYAN" mailto:rh1...@att.com>>
Subject: Re: [onap-modelingsub] [onap-discuss] Agreements on Montreal offline 
discussion of Resource IM and Service IM
Actually that is completely non-negotiable; anything discussed in a breakout 
discussion MUST be taken back to a general, and fully public subcommittee call 
before any decision can be made.

...same song I've been singing for a couple of weeks now. ;-)

Best Regards,
-kenny

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


From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
mailto:onap-discuss@lists.onap.org>> On Behalf Of 
WECHSLER, CHESLA C
Sent: Tuesday, October 30, 2018 8:43 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] Agreements on Montreal offline discussion of 
Resource IM and Service IM

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

Because of the lack of good audio in the breakout sessions (and really, in 
general), I think we can only come out of Montreal with proposals to bring back 
to the normal call for discussion and approval.  Not all key people were able 
to travel to Montreal unfortunately.  Deng, Andy, what do you think?

Chesla



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

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

Re: [onap-discuss] ONAP Support for Secure Communication

[denghui (L)]

Modeling: No

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of gaoweitao
Sent: Thursday, October 18, 2018 11:50 PM
To: onap-discuss@lists.onap.org; amy.zwar...@att.com
Subject: Re: [onap-discuss] ONAP Support for Secure Communication

Hi Amy,

  VNFSDK：No

BR
Victor
发件人：Amy Zwarico
收件人：onap-discuss@lists.onap.org,
时间：2018-10-16 22:18:36
主 题：[onap-discuss] ONAP Support for Secure Communication






PTLs: The security subcommittee is tracking ONAP support of secure 
communication on all ONAP interfaces (typically HTTPS), which is one of the S3P 
requirements. Please respond to this email with a the status of your project’s 
support of secure communication. ("Yes" or "No")

Amy Zwarico, LMTS

Chief Security Office / Enterprise Security Support / Cloud Security Services

AT Services

(205) 613-1667






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

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

[onap-discuss] Joint modeling and architecture meeting during Motreal F2F architecture meeting

[denghui (L)]

Hi, architecture and modeling subcommittee

This is the proposal to have a joint meeting between architecture and modeling 
subcommittee. Based on recent discussion, modeling subcommittee has difficulty 
to move forward on some topics due to lack of the guidance of ONAP architecture.
Since there are many modelers will be in this meeting. In this case we are 
proposing to have a joint meeting right after the architecture meeting on 
Wednesday morning (31st, Oct) for only half day in order to have a better 
alignment of future work.

Please kindly help to stay half  day there if you are interested in this 
follow-up work discussion and we will check whether there is the possibility to 
prepare the remote access bridge.
We will not make any decision in this half day meeting, and will bring 
everything output from this meeting back to our regular modeling subcommittee 
call to confirm again.

Thanks a lot for your attention
Best regards,

DENG Hui


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

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

[onap-discuss] [modeling] Call for agenda 9/18/2018 modeling meeting

[denghui (L)]

Dear Modelers,

Andy and I would like to reformulate our session application based on the wiki. 
Here is the tentative agenda items for this week,
Duration

Agenda Item

Requested by

Notes / Links

START RECORDING

 5

New cochair welcome


Hui Deng  & Andy 
Mayer

 5

 Resource IM report

 Xu Yang



 5

 Service IM report

 Lingli Deng



 5

 DM report

 Anatoly Katzman



 5

 M4 discussion


 Hui Deng & Andy 
Mayer





 ?

 Mehmet Toy





Feel free to add any other items you may have at : 
https://wiki.onap.org/display/DW/Modeling+2018-09-18

Thanks

Co-chairs


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

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

Re: [onap-discuss] [modeling] #modeling Modeling Subcommittee Elections Call for Self-Nominations

[denghui (L)]

Dear Modeling subcommittee

I would like sincerely nominate myself as a candidate of 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 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 – now 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

Thanks a lot

DENG Hui


From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Kenny Paul
Sent: Tuesday, August 21, 2018 4:41 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [modeling] #modeling Modeling Subcommittee Elections 
Call for Self-Nominations

As per Subcommittee Chair 
Elections
 I am officially opening the self-nomination period for the Modeling 
Subcommittee Chair elections.
The nomination period will end on Friday, Aug 24 @ 2:00 Pm Pacific

The members eligible to be a voting member is set to V118 of the Modeling 
Subcommittee Membership Page
I have updated that page, adding a column for Company and a column that says 
"Voting Member", and removing 3 individuals I know are no longer involved with 
ONAP.  One of them never even set up a wiki account.

The "Voting Member" column usage is simple. If you are the person from your 
company that will be casting the vote, then put "Yes" in that column. If not, 
leave it blank.


Who is eligible to Run: Subcommittee members of record (as per v118 of the wiki 
page)

Who is eligible to Vote: Subcommittee members of record (as per v118 of the 
wiki page) AND as controlled within the context of Section 
4.4.1.4
 of the Community Document

Process:

Self-Nomination Phase
When appropriate a call for nominations will be sent by the LF to the 
appropriate distribution list, using the subcommittee's specific email tag.  
Individuals interested in running for the Subcommittee Chair position must 
reply-all to that email with your intention to run.  It is recommended that 
candidates include a biography and statement of intent on why you would be a 
good person to hold this position.
·
·

 *   The nomination phase begins with the receipt of the announcement ( as 
verified by checking the appropriate list in groups.io 
)
 *   The nomination phase ends four (4) full business days after the 
announcement in the same time zone the poll was initiated from

Election Phase
A Condorcet election will be held using the CIVS voting 
system.  All 
subcommittee members (as indicated above) will receive an invitation to vote.
·
·

 *   The election 

Re: [onap-discuss] [Modeling] [0815 Service IM Minutes]

[denghui (L)]

Hi Menglin

For Item 6:, I would suggest to revise it as below:
6: For R4+, the relationship between Service template and Network Service 
Template would bette be guided jointly by Architecture and Modeling 
subcommittee, for NSD in R3, please Maopeng’s help to propose to SDC and check 
whether it could be acceptable in SDC for such new node type.

Thanks a lot

DENG Hui


From: LinMeng [mailto:menglin...@chinamobile.com]

Subject: [onap-discuss] [Modeling] [0815 Service IM Minutes]

Hi all,
This is the minutes of Service IM Call on Wednesday. Please check and make sure 
that we have consensus on it.

1. Yan presents VFC requirements for 
NSD<https://wiki.onap.org/display/DW/Network+Service+Descriptor+Proposal>. VFC 
project implement ETSI NFVO, which needs to consume the NSD. VFC also needs 
standard NSD. VFC would like to receive the NSD from SDC. In the long run, VFC 
also needs to receive NSD from OSS and BSS.
2. YangXu presents NSD updates from the resource IM calls ?Proposed Network 
Service Descriptor 
Model<https://wiki.onap.org/display/DW/Proposed+Network+Service+Descriptor+Model>?.
 From his understanding of previous calls of reousrce IM CALL, NS is a 
composition of VNFs, VLs and topology of how to construct a service, which are 
all in the domain of resource. NS is different from the service we want ONAP to 
handle.
3. From Lingli and Andy's discussion: For IM, we agreed to move NSD to resource 
domain for Casablanca. But for Dublin+, there are considerations on having also 
service domain reflection on resources (including network service).
4. MaoPeng presents NSD 
proposal<https://wiki.onap.org/display/DW/Network+Service+Descriptor+Proposal>: 
NSD requires to do some limitation in NFV resoures composition, not all the SDC 
resources and substitution mappings to NS TOSCA node.
5. Currently we are working on enabling interworking commercial NFVO deployment 
with ONAP community version
6. Agreed to continue with a special service type for network service design 
and distribution to be supported by SDC/SO/VFC for Casablanca.

Best Regards,
Lin
---
孟琳
人工智能和智慧运营研发中心
中国移动通信有限公司研究院
中国北京市西城区宣武门西大街32号（100053）

Meng Lin
Center of AI and Intelligent Operation R
China Mobile Research Institute
No.32 Xuanwumen west street, Xicheng District, Beijing 100053, China

Mobile: +86 13810012241
Email: menglin...@chinamobile.com<mailto:menglin...@chinamobile.com>
-



发件人: mailto:onap-discuss@lists.onap.org>> 代表 
LinMeng mailto:menglin...@chinamobile.com>>
答复: mailto:onap-discuss@lists.onap.org>>, 
mailto:menglin...@chinamobile.com>>
日期: 2018年8月15日 星期三 14:44
收件人: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, Yan Yang 
mailto:yangya...@chinamobile.com>>, "yangxu (H)" 
mailto:yang...@huawei.com>>, maopeng 
mailto:zhang.maope...@zte.com.cn>>, "Katzman, 
Anatoly" mailto:ak4...@intl.att.com>>
抄送: 邓灵莉 mailto:denglin...@chinamobile.com>>, 
"denghui (L)" mailto:denghu...@huawei.com>>
主题: [onap-discuss] [Modeling] [Service IM Agenda]

Hi all,
For today’s service IM call, we will continue the remaining agenda of 
yesterday’s modeling subcommittee call,  will mainly focus on NSD/SD Discussion:

1.  VFC requirements for NSD (Yan Yang<https://wiki.onap.org/display/~yangyan>)

2.  Resource/Service IM decision on NSD  (Xu 
Yang<https://wiki.onap.org/display/~yxpoke>)

3. NSD Proposal (Maopeng Zhang<https://wiki.onap.org/display/~maopengzhang>)

4. Service DM proposal (Anatoly 
Katzman<https://wiki.onap.org/display/~anatoly.katzman>)

5. NSD/SD next step



Thanks!



Best regards,

Lin

---
孟琳
人工智能和智慧运营研发中心
中国移动通信有限公司研究院
中国北京市西城区宣武门西大街32号（100053）

Meng Lin
Center of AI and Intelligent Operation R
China Mobile Research Institute
No.32 Xuanwumen west street, Xicheng District, Beijing 100053, China

Mobile: +86 13810012241
Email: menglin...@chinamobile.com<mailto:menglin...@chinamobile.com>
-





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

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

Re: [onap-discuss] [modeling] DM IG 2018-08-13 call is cancelled #modeling

[denghui (L)]

Hi Anatoly

Last week, during Service IM call, there were suggestion that this needs to be 
further discussed,

1)  Current NSD IM belongs to resource IM other than service IM according 
to the consensus of Service/Resource IM discussion.

2)  VFC needs NS information for their use case.

Let's discuss it today during modeling subcommittee call, I will arrange every 
related statekholder to discuss it, maybe :

1)  VFC requirements for NS (YANG Yan)

2)  Resource/Service IM decision on NSD (Yang Xu)

3)  NSD Proposal (Maopeng)

4)  Service DM proposal (Anatoly)

5)  Next step (all)

If needed, we could discuss it again on Wednesday service IM call

Thanks a lot

DENG Hui

From: Katzman, Anatoly [mailto:ak4...@intl.att.com]
Sent: Monday, August 13, 2018 9:00 PM
To: 'onap-discuss@lists.onap.org' 
Cc: denghui (L) ; LinMeng ; 
MAYER, ANDREW J ; Lando,Michael ; 
Alexander Vul ; Anatoly Katzman ; 
Andrei Kojukhov ; GUPTA, ARUN ; BAXTER, 
ANDREW ; Bill Coan ; HU, BIN 
; Chenchuanyu ; Chuyi Guo 
; BULLARD, GIL ; Eshet, Itamar 
; Jacqueline Beaulac ; 
Janusz Pieczerak ; Jessie S Jewitt 
; SCAGGS, KEVIN ; Lianhao Lu 
; Lingli Deng ; Maopeng Zhang 
; Marek Kukulski ; 
NUTAKKI, MADHU ; Priya TG ; Lishitao 
; Thinh Nguyenphu ; Gaoweitao 
(Victor, MANO) ; WECHSLER, CHESLA C ; 
Xiaodong Shang ; yangxu (H) ; 
Yang Xu (Yang, Fixed Network) ; Zhong Heliu 
; Zhuoyao HUANG <10112...@zte.com.cn>
Subject: [modeling] DM IG 2018-08-13 call is cancelled #modeling

Dear all,

the today meeting of the Data Modeling Interest 
Group<https://wiki.onap.org/display/DW/Data+Model+Interest+Group+2018-08-13+Meeting+Minutes>
 is cancelled.

The plans for this call were to finalize the model of an ONAP service so that 
it would support the following cases:
- ONAP end-to-end service
- ETSI NS
- nested services
We are very close to these goals. The impression after the previous call was 
that the proposed TOSCA 
definitions<https://wiki.onap.org/display/DW/R3+onap.nodes.Service> and 
modeling conventions<https://wiki.onap.org/display/DW/Complex+Service+Example> 
would be able to provide an adequate coverage for all these cases.

Based on this impression, I would like to use this unplanned break time for the 
following activities:
1. improvement of the examples and other explanatory 
materials<https://wiki.onap.org/display/DW/Complex+Service+Example> provided 
with the model. All those who is interested in a better explanation on any 
aspect of the service model, please visit the meeting agenda 
page<https://wiki.onap.org/display/DW/Data+Model+Interest+Group+2018-08-13+Meeting+Minutes>
 and submit your questions in the Q section
2. preparing the ground for the upcoming discussion of Allotted Resource (am 
ONAP model for a share of an external service)

Sorry for the short notice,

Anatoly Katzman


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

View/Reply Online (#11869): https://lists.onap.org/g/onap-discuss/message/11869
Mute This Topic: https://lists.onap.org/mt/24502641/21656
Mute #modeling: https://lists.onap.org/mk?hashtag=modeling=2740164
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[denghui (L)]

Hi Chesla

I have just updated the wiki page based on your recommendation by including 
below link,
https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.4.1.3SubcommitteeChair/ViceChairElections

thanks a lot for your help
Best regards,

DENG Hui

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of C. Wechsler
Sent: Tuesday, July 31, 2018 11:51 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [modeling] Call for nominations: modeling 
subcommitee Chair and Vice Chair


[Sorry for starting new 
topic
 with Confluence access request  - should have replied here]
Hi, Kenny, Deng,

I'm having the same access problem  getting to the link on the page Deng 
created about the subcommittee voting rules.

Both this page:

https://wiki.onap.org/display/DW/Modeling+Subcommittee+Election



and this page referenced from the previous one:

https://wiki.onap.org/display/DW/Subcommittee+Election+Process



give me that "You do not have permission to view this page. Request access 
below, you will receive an email when you've been granted access" message which 
I think Kenny has attributed to a locked page that was deprecated in favor of 
the new rules.



Would you please make sure the links are correct on this page at your earliest 
possible opportunity and send an update to the group?  I think the right place 
to go is 
here
 but I'm not sure and don't want to steer people wrong.



Thanks,

Chesla


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

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

Re: [onap-discuss] [modeling] PTL Election for modeling project - Result

[denghui (L)]

Thank you Chesla.

TSC recommend that the election of the committee should happen after TSC 
election, that is after Aug.15, but have to finish before Aug. 30.
According to this rule, self-nomination should be after 8.15.

Current modeling subcommittee follow Subcommittee Officer Elections which are 
governed under ONAP TSC Charter - 
Pre-LFN#5.4.1Membership
I will try to send confirm email to all current members and clean the inactive 
member asap.

Thanks a lot for your remind
Best regards,

DENG Hui


From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of C. Wechsler
Sent: Thursday, July 26, 2018 5:51 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [modeling] PTL Election for modeling project - 
Result


Congratulations, Deng.
I'd like to get a good understanding of how the Model Subcommittee Chair gets 
elected and when.  I believe you had mentioned August at one point, but is 
there a particular date?  Is there a timeframe for self nominations?  Is there 
a clear understanding of who can nominate and who can vote?  Apologies if this 
is all documented somewhere and I just don't know where.
Thanks!
Chesla


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

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

[onap-discuss] [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 (#11425): https://lists.onap.org/g/onap-discuss/message/11425
Mute This Topic: https://lists.onap.org/mt/23814153/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [modeling] Papyrus working branch for modeling

[denghui (L)]

Chris

In order to build a validation job for papyrus, we need many days/Human 
resource to do this job in order to let papyrus file could follow LF official 
procedure, we also need do maven for it later as well.

I will try to manually merge this commit without the validation.

Thanks a lot

DENG Hui

From: Christopher Donley (Chris)
Sent: Friday, July 13, 2018 10:28 AM
To: onap-discuss@lists.onap.org; jessie.jew...@oamtechnologies.com; denghui (L) 

Subject: Re: [onap-discuss] [modeling] Papyrus working branch for modeling

Hui,

I don't think that repo has a validation job. It will either need to be 
manually validated by a Committer or you'll need to set up a jjb job. Since 
Papyrus generates xml files and not java/python code, I don't think there is a 
jjb job for it, so you may need to do it manually.

Chris

From: denghui (L)
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
jessie.jew...@oamtechnologies.com<mailto:jessie.jew...@oamtechnologies.com>;
Cc: Christopher Donley (Chris);
Subject: RE: [onap-discuss] [modeling] Papyrus working branch for modeling
Time: 2018-07-12 18:15:26

Hi Jessie,

Thanks a lot for your help.

Maybe this is your 1st time to submit to ONAP gerrit,  in order to get 
successfully merged, your commit needs to pass jbuilder check,
Could you kindly help to study from this wiki page about jbuilder : 
https://wiki.onap.org/display/DW/Using+Standard+Jenkins+Job+%28JJB%29+Templates
The recommit it again, then after jbuilder+2, then I could quickly merge this 
commit into the working branch.

Thanks a lot for your help

Best regards,

DENG Hui

From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
[mailto:onap-discuss@lists.onap.org] On Behalf Of Jessie Jewitt
Sent: Friday, July 13, 2018 5:03 AM
To: onap-discuss 
mailto:onap-discuss@lists.onap.org>>; denghui (L) 
mailto:denghu...@huawei.com>>
Subject: Re: [onap-discuss] [modeling] Papyrus working branch for modeling

Deng Hui-
   I uploaded all the Papyrus files to the working branch. There is an 
outstanding issue open in Gerrit for you to approve to commit these files to 
the branch. Could you possibly do this so we can start downloading the model 
for people to work on starting tomorrow?
Thank you,
Jessie

On Tue, Jul 10, 2018 at 1:05 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
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 (#7): https://lists.onap.org/g/onap-discuss/message/7
Mute This Topic: https://lists.onap.org/mt/23209084/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [modeling] Papyrus working branch for modeling

[denghui (L)]

Hi Jessie,

Thanks a lot for your help.

Maybe this is your 1st time to submit to ONAP gerrit,  in order to get 
successfully merged, your commit needs to pass jbuilder check,
Could you kindly help to study from this wiki page about jbuilder : 
https://wiki.onap.org/display/DW/Using+Standard+Jenkins+Job+%28JJB%29+Templates
The recommit it again, then after jbuilder+2, then I could quickly merge this 
commit into the working branch.

Thanks a lot for your help

Best regards,

DENG Hui

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Jessie Jewitt
Sent: Friday, July 13, 2018 5:03 AM
To: onap-discuss ; denghui (L) 

Subject: Re: [onap-discuss] [modeling] Papyrus working branch for modeling

Deng Hui-
   I uploaded all the Papyrus files to the working branch. There is an 
outstanding issue open in Gerrit for you to approve to commit these files to 
the branch. Could you possibly do this so we can start downloading the model 
for people to work on starting tomorrow?
Thank you,
Jessie

On Tue, Jul 10, 2018 at 1:05 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
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 (#0): https://lists.onap.org/g/onap-discuss/message/0
Mute This Topic: https://lists.onap.org/mt/23209084/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] Att: PTL - Languages supported in ONAP

[denghui (L)]

Modeling has two different languages (java and Python) which support 2 
different parsers, they work independently, I think that you have already 
include both of them.

Thanks

DENG Hui

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Arul Nambi
Sent: Wednesday, July 11, 2018 10:07 PM
To: onap-discuss@lists.onap.org
Cc: onap-sec...@lists.onap.org
Subject: [onap-discuss] Att: PTL - Languages supported in ONAP

Hi PTL's/Community,
In the security committee we are looking for the list of languages that needs 
to be supported when we come up with new tools for code coverage and static 
analysis.
Currently we know of

  1.  Java(ofcourse)
  2.  Javascript
We think that we will need PHP and Phyton, but need confirmation from the 
projects(preferably PTLs) about the language support that is needed and the 
name of the project.
There is a query in gerrit which can be used to find projects with certain file 
extensions, but it hard think of all the languauges.
Once we have a complete list I can update the wiki page so that in future we 
will know the languages that we support.
Regards
Arul

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


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

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

Re: [onap-discuss] [modeling] Modeling Project Casablanca M1 Scope

[denghui (L)]

Hi Brian

Hope previous email could answer your questions, thanks a lot for your kind 
review

Best regards,

DENG Hui

From: Brian Hedstrom [mailto:brian.hedst...@oamtechnologies.com]
Sent: Friday, July 6, 2018 5:57 AM
To: onap-discuss 
Cc: denghui (L) ; Gildas Lanilis 

Subject: [modeling] Modeling Project Casablanca M1 Scope

Modeling Subcommittee:

I was reviewing the Casablanca Release 
Deck<https://wiki.onap.org/display/DW/TSC+2018-07-05+Meeting+Agenda?preview=%2F33067338%2F36963870%2FONAP+Casablanca+M1+Status+Summary+Version4.pdf>
 which Gildas presented today on the TSC call and the TSC approved.

In looking at the Modeling Project Casablanca M1 
checklist<https://wiki.onap.org/pages/viewpage.action?pageId=35524278> (R3 
Scope), I noticed that most all of the Epics and Stories are for developing 
service and resource Information Models and Data Models and their mappings.

These items are not part of the Modeling Project 
scope<https://wiki.onap.org/pages/viewpage.action?pageId=3247202>, but are part 
of the Modeling Subcommittee activities.

This has created a lot of confusion as to what the Modeling Project scope and 
responsibility is versus the Modeling Subcommittee. Can we get clarification?

In addition, I (again) recommend we change the name of the modeling project to 
eliminate confusion.  For example, Model Parsers project.

Thanks
--
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oam.technology<http://oam.technology>
brian.hedst...@oamtechnologies.com<mailto:brian.hedst...@oamtechnologies.com>
720-470-7091

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

View/Reply Online (#10923): https://lists.onap.org/g/onap-discuss/message/10923
Mute This Topic: https://lists.onap.org/mt/23168988/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/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-discuss@lists.onap.org; onap-...@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=DwQFAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=h336thy4AQC9X1JMXCsyYKGnG9RZQiRvWQY-u54zaMI=ffAQ4YaMD5X0xX09fOLdQR9a4020jv33Vw3hzajOwBA=>
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-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@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=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=Oej6QUk5p2KdqNEWySpOHA=aqtE2C1ZdfxIEpvFpsi-ywKvepAjMEEvXvpyXwKvr7o=1VOSZREkf7OvEcmx6COn9S0Mz80ACCfrmsVXjmhZwZs=>

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=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=XBYNhzlk2jx6nSVGWpJjJUhpTLxHynkr7bh6Vp5VOXU=odKqVMZCdJUsygPKUpW7Gk3KS-ALAv3Pe3CO5I_82Ls=>
 )

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 (#10874): https://lists.onap.org/g/onap-discuss/message/10874
Mute This Topic: https://lists.onap.org/mt/23036778/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/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-discuss@lists.onap.org; onap-...@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=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=Oej6QUk5p2KdqNEWySpOHA=aqtE2C1ZdfxIEpvFpsi-ywKvepAjMEEvXvpyXwKvr7o=1VOSZREkf7OvEcmx6COn9S0Mz80ACCfrmsVXjmhZwZs=>

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=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=XBYNhzlk2jx6nSVGWpJjJUhpTLxHynkr7bh6Vp5VOXU=odKqVMZCdJUsygPKUpW7Gk3KS-ALAv3Pe3CO5I_82Ls=>
 )

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 (#10853): https://lists.onap.org/g/onap-discuss/message/10853
Mute This Topic: https://lists.onap.org/mt/23036778/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [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-discuss@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 (#10832): https://lists.onap.org/g/onap-discuss/message/10832
Mute This Topic: https://lists.onap.org/mt/22674361/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] [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 (#10829): https://lists.onap.org/g/onap-discuss/message/10829
Mute This Topic: https://lists.onap.org/mt/23036778/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] [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 (#10527): https://lists.onap.org/g/onap-discuss/message/10527
Mute This Topic: https://lists.onap.org/mt/22674361/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] 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-discuss@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-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
mailto:onap-...@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 (#10507): https://lists.onap.org/g/onap-discuss/message/10507
Mute This Topic: https://lists.onap.org/mt/22460897/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] 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-discuss@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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #56955] RE: Beijing Release: Last Mile

[denghui (L)]

Dear Jessica,

Sorry for late,

https://jenkins.onap.org/view/modeling/job/modeling-toscaparsers-javatoscachecker-master-javatoscachecker-release-version-java-daily/209/
https://jenkins.onap.org/view/modeling/job/modeling-toscaparsers-nfvparser-master-nfvparser-release-version-java-daily/127/

thanks

DENG Hui


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, June 6, 2018 1:00 PM
To: denghui (L) 
Cc: Gildas Lanilis ; j...@research.att.com; 
onap-discuss@lists.onap.org; onap-rele...@lists.onap.org; 
rittwik.j...@gmail.com; shang.xiaod...@zte.com.cn; yangya...@chinamobile.com
Subject: [ONAP Helpdesk #56955] RE: [onap-discuss] Beijing Release: Last Mile

Dear Deng, 

Thanks, but I need you to give me the links to the Jenkins jobs that generated 
these please. 

I cannot perform a release without them.

Thanks!
Jess
 
On Tue Jun 05 22:48:45 2018, denghu...@huawei.com wrote:
> Hi Jess,
> 
> This is for modeling part, thanks a lot:
> 
> Javatoscachecker:  /org/onap/modeling/toscaparsers/Checker/1.2.0-
> SNAPSHOT/Checker-1.2.0-20180605.124309-
> 60.jar<https://nexus.onap.org/service/local/repositories/snapshots/con
> tent/org/onap/modeling/toscaparsers/Checker/1.2.0-
> SNAPSHOT/Checker-1.2.0-20180605.124309-60.jar>
> NFVParser:  /org/onap/modeling/toscaparsers/nfvparser/modeling-
> toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-nfvparser-
> 1.1.0-20180329.050338-
> 7.zip<https://nexus.onap.org/service/local/repositories/snapshots/cont
> ent/org/onap/modeling/toscaparsers/nfvparser/modeling-
> toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-nfvparser-
> 1.1.0-20180329.050338-7.zip>
> 
> Deng Hui
> 
> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss- 
> boun...@lists.onap.org] On Behalf Of Jessica Wagantall
> Sent: Wednesday, June 6, 2018 6:16 AM
> To: Gildas Lanilis 
> Cc: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] Beijing Release: Last Mile
> 
> No request received yet also from the modeling team.
> 
> Thanks!
> Jess
> 
> On Tue, Jun 5, 2018 at 3:14 PM, Jessica Wagantall 
> mailto:jwagant...@linuxfoundation.org>
> >
> wrote:
> Dear Gildas,
> 
> Here is an update on the pending items:
> 
> *** MUSIC *** New release version 2.5.5 needed ***
> 
> - Working with Tom on this now. We should be releasing soon.
> Reference: #56927: Music Jar Release 2.5.5
> 
> *** VID *** New clarification from the team ***
> 
> - The request was placed to make a docker release but I noticed
>   their maven artifacts haven't been released for the specific version 
> used
>   to build their docker images. Do we approve a release of those too?
> Reference: #56922: VID docker release
> 
> *** AAF *** Pending Ram's Approval ***
> 
> - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> 8.jar<https://nexus.onap.org/index.html#view-
> repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> Reference: #56662: Artifacts for Release
> 
> No release request yet from multicloud or usecase-ui teams!
> 
> Thanks!
> Jess
> 
> On Mon, Jun 4, 2018 at 12:27 PM, Jessica Wagantall 
> mailto:jwagant...@linuxfoundation.org>
> >
> wrote:
> Thanks a lot for this Gildas,
> 
> Due to the importance of these releases, I will help posting here the 
> blockers we encounter in the RT tickets.
> 
> Here are some blockers:
> 
> *** AAF *** Pending Ram's Approval ***
> 
> - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> 8.jar<https://nexus.onap.org/index.html#view-
> repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> Reference: #56662: Artifacts for Release
> 
> *** DMAAP *** Pending Ram's Approval ***
> 
> - Docker release for onap/dmaap/dmaap-mr:1.1.4
> Reference: #56857: Move docker image to release repository
> 
> *** VFC *** Yan to clarify ***
> 
> - Email sent for 8 maven artifacts to be released, but email mentions 
> also docker images needed and no link to docker images jobs
> - Do we just need to release the maven artifacts? if docker images 
> need release, please update request with corresponding docker links 
> from Jenkins
> Reference: #56821: Please help to release VF-C R2 artifacts to 
> releases repo
> 
> 
> Thanks!
> Jess
> 
> On Mon, Jun 4, 2018 at 7:33 AM, Gildas Lanilis 
> mailto:gildas.lani...@huawei.com>> wrote:

Re: [onap-discuss] [modeling] Need a Quick Summary of MEF & ONS Activity

[denghui (L)]

Both ONF and MEF has been involved in ONAP service modeling discussion, no 
conclusion has been made yet.

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: Monday, June 4, 2018 10:54 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [modeling] Need a Quick Summary of MEF & ONS Activity


Sorry about reaching out to the entire list, but I have a time critical bit of 
info I need for a Board presentation.
I need a quick one-sentence summary of current participation for both ONA and 
MEF.  Looking for a high-level summary, not low level details.
Thanks!

Best Regards,
-kenny

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


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

Re: [onap-discuss] [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-discuss@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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling] Friday morning modeling workshop venue

[denghui (L)]

Hello all

Venue: Intercontinental Los Angeles Downtown, sponsored by Linux Foundation 
Network
Echo Park Meeting Room 5th floor
Date: March 30th
Time: 8am-1pm

Lingli will post agenda later today,

Thanks a lot

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

[onap-discuss] [modeling] Last call for ONAP NS IM

[denghui (L)]

Hello modelers,

According to last Sunday discussions, it seems that NS IM become more stable, 
here is one week call for ONAP NS IM.
https://wiki.onap.org/display/DW/NetworkService

After this call, this version will move into the clean version.

Thanks a lot

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

[onap-discuss] [modeling]modeling call this week is cancelled

[denghui (L)]

Hello modelers,

This week call is cancelled , thanks

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

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [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=MTgzZmZmZTZkYjF0dGJ1dThtaW5mdWFlYzQgZGVuZ2h1aTEyQGh1YXdlaS5jb20
	k=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91
	cC5jYWxlbmRhci5nb29nbGUuY29tNjliNzI1ZmQ3Yjg0Y2NjMTAxOGQzYzBmZGQwY2ZiMGQzZG
	U1MWYwMg=America%2FLos_Angeles=en=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=D=2=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=D=2=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=D=2=AFQjCNHeMpyQmBD-7bInhjDLRut-TgzlLQ> \n\n\n\
	n\nGoing?   Yes <https://www.goo

[onap-discuss] [modeling]Modeling call tomorrow

[denghui (L)]

Reminder, the US entered Daylight Savings Time yesterday.  For those outside 
the US, tomorrow’s modeling call will start one hour earlier.  2100 Beijing time

DENG Hui

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

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [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) <denghu...@huawei.com>
Cc: onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>; Rittwik 
Jana <rittwik.j...@gmail.com>
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) 
<denghu...@huawei.com<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-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-discuss

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

Re: [onap-discuss] [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-discuss@lists.onap.org; 'onap-tsc' <onap-...@lists.onap.org>
Cc: Rittwik Jana <rittwik.j...@gmail.com>; 'Lingli Deng' 
<denglin...@chinamobile.com>
Subject: [modeling] ONAP R2 IM to DM design

Hello all

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

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

The tasks including:
1. VDU: https://jira.onap.org/browse/MODELING-67
2. HPA: https://jira.onap.org/browse/MODELING-68
3. CP: https://jira.onap.org/browse/MODELING-69
4. DeploymentFlavor: https://jira.onap.org/browse/MODELING-70
5. VL: https://jira.onap.org/browse/MODELING-71
6. VNFD: https://jira.onap.org/browse/MODELING-72
7. monitor: https://jira.onap.org/browse/MODELING-73

It's expected that the lead would help provide tosca definitions on the 
contribution page 
(https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile) and
help implement related logic in SDC, APPC/VFC projects.

Thanks a lot

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

Re: [onap-discuss] [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) <denghu...@huawei.com>; onap-discuss@lists.onap.org; onap-tsc 
<onap-...@lists.onap.org>
Cc: Rittwik Jana <rittwik.j...@gmail.com>; Lishitao <lishi...@huawei.com>; 
MAYER, ANDREW J <am8...@att.com>
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 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-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Cc: Rittwik Jana <rittwik.j...@gmail.com<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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [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-discuss@lists.onap.org; onap-...@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) <denghu...@huawei.com<mailto:denghu...@huawei.com>>; Gadiyar, 
Rajesh <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>>; Addepalli, 
Srinivasa R 
<srinivasa.r.addepa...@intel.com<mailto:srinivasa.r.addepa...@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Cc: GILBERT, MAZIN E (MAZIN E) 
<ma...@research.att.com<mailto:ma...@research.att.com>>; Katzman, Anatoly 
<ak4...@intl.att.com<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:

Re: [onap-discuss] 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-discuss@lists.onap.org; onap-...@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

  AJames Forsyth

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

Re: [onap-discuss] [modeling] Resource TOSCA Data model

[denghui (L)]

Hi Michela

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michela Bevilacqua
Sent: Wednesday, March 7, 2018 1:09 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [modeling] Resource TOSCA Data model

Hi,
I share some questions about Resource TOSCA data model as follow up of the 
today´s ONAP  modeling subcommittee meeting


1)  Assuming the discussion we had today during the ONAP modeling 
subcommittee about OASIS TOSCA NFV or SOL001 is limited to the VNF onboarding 
model. What is the TOSCA data model used by SDC to generate the VNF and service 
descriptors to be shared with the ONAP run time component ?
== >  this is not correct, for R2 it cover everwhere, there is a proposal 
talking about R3 model which will cover onboarding, but it needs further 
discussion


2)  Assuming the discussion we had today during the ONAP modeling 
subcommittee about OASIS TOSCA NFV or SOL001 is limited to the VNF onboarding 
model.  I expect that the VNF onboarding model needs implementation only in SDC.
  == > no


3)  Assuming OASIS TOSCA NFV profile (v004) is a subset of ETSI SOL001 
without features as HPA and monitoring parameters, if OASIS TOSCA NFV profile 
will be preferred for VNF onboarding model, will SOL001 used to introduce HPA 
and Monitoring parameters or …. ?
   == > ONAP TOSCA NFV profile will include HPA.


4)  If OASIS TOSCA NFV profile will be preferred for in R2, do we expect to 
move to SOL001 in R3 ? IN other word, are we only delaying SOL001 support of 1 
release or …?



  == > no decision yet, will be discussed during R3. Maybe ONAP and ETSI NFV 
board level relationship also related.



Thanks



DENG Hui




BR
Michela








From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Nguyenphu, Thinh 
(Nokia - US/Irving)
Sent: den 5 mars 2018 22:14
To: jessie jewitt 
>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [modeling] Data model mapping using SOL001

Hi Jessie,

Your summary below shows there are a lot of inconsistency of TOSCA types naming 
convention with IFA011.  I fully acknowledge it. SOL WG is in the process of 
cleaning it up with these guidelines:

  *   SOL001 Type naming convention is UpperCamelCase.
  *   SOL001 properties naming convention is lowercase_underscored or 
snake_case.
  *   SOL001 shall not include postfixes of “d”, “D”, “Desc”, “Descr” of type 
or properties names.
  *   SOL001 shall not include prefixes of “vnf” of properties names, like 
vnfdid, vnfProvider, vnfProductName, vnfSoftwareVersion, 
vnfdVersion,vnfProductInfoName, vnfProductinfoDescription.

The inconsistence issues should be resolved with the next version of SOL001 
(v0.6.0).

Meanwhile, I have created a wiki page to show all of the ONAP R2 Resource IM 
attributes (clean version wiki page) map to SOL001 (TOSCA model) data model, 
https://wiki.onap.org/pages/viewpage.action?pageId=25436710.  (see SOL001 
Mapping column).  The mapping table shows that all of ONAP Resource IM 
attributes are mapped into TOSCA types with detail.  Except for any of new 
attributes (“orange” highlighted text) are not yet defined.

Perhaps, I can introduce this page at Modeling sub_committee on Tuesday call.

Thinh

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of jessie jewitt
Sent: Friday, March 02, 2018 1:20 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [modeling] Data model mapping using SOL001

This message is particularly directed to Anatoly, Alex, and Thinh, as we have 
an action item to map ONAP IM to DM. If one of you could respond, I'd 
appreciate it.

My understanding is that SOL001 is mapping the VNFD model to TOSCA. They 
indicate they are mapping the  ETSI NFV elements listed below into TOSCA types 
(page 12).

I'm not clear why they chose the elements they did, as they don't all 
correspond to the VNFD model which is defined in the ETSI "VnfTemplateModule" 
of the model.

Also, the actual ETSI elements named do not correspond to exactly what is 
defined in the model (they probably just got sloppy, but they should pay 
attention to detail).

Here's the list of the currently defined elements that they map
1. VNF   -   Shouldn't this be Vnfd? The Vnf is defined in the VnfModule of the 
model. Also, the element is called Vnf and not VNF.
2. VDU   -   OK, but it should be Vdu, not VDU.
3. Cpd  -Maybe ok? It is defined in the CommonTemplateModule as an abstract 
class. You don't instantiate abstract classes, so you will never have an 
instance. Do you have TOSCA types that represent abstract classes? Also, they 
don't map other abstract classes such as VirtualLinkDesc, so 

[onap-discuss] [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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [modeling]Poll on modeling workshop in ONS 2018

[denghui (L)]

Reminder

From: denghui (L)
Sent: Wednesday, February 28, 2018 9:33 AM
To: onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>
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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [modeling] Reminder for information model related votes (Naming Convention & Meeting Time)

[denghui (L)]

Just remind everybody, for 1st poll , there are 3 options:

Option 1: be consistent with ETSI IFA011 naming convention; give feedback to 
ETSI about the new proposals and make change to ONAP according to the result

Option 2: make changes in ONAP IM and keep a mapping (e.g., in the description 
of the class/attribute) of ETSI names with ONAP ones

Option 3: Option 2 + feedback to ETSI about the changes

Please help to cast your vote

Thanks

DENG Hui

From: yangxu (H)
Sent: Wednesday, February 28, 2018 1:22 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss][modeling] Reminder for information model related votes 
(Naming Convention & Meeting Time)

Hello all,

There're two votes ongoing related to information model design and the deadline 
is approaching.

If you haven't voted, please see the following wiki pages and provide your 
opinions.
https://wiki.onap.org/display/DW/Naming+Convention+Poll
https://wiki.onap.org/display/DW/Meeting+Time+Poll

Best regards,
Xu
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling]Poll on modeling workshop in ONS 2018

[denghui (L)]

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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling] ONAP modeling subcommittee call meeting minutes

[denghui (L)]

Hello all

The meeting minutes is here:
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings
copy below

I am sending out poll on day of modeling workshop today

Best regards,

DENG Hui
20180227 Meeting agenda and Minutes

Deadline for modeling spec is M3: Mar. 7th

Implementation of model spec will be before M4

Modeling workshop is needed during ONS 2018, poll on Sunday or Friday

1)DM:   Anatoly Katzman (Anatoly is absent due to traveling, Deng 
Hui help to lead the discussion)

1.1) AT suggest to keep Heat support , agreed

1.2) two tosca proposal on the table

   a) 
https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile

   b) 
https://wiki.onap.org/display/DW/Data+Model+Compliance+with+ETSI

Consensus a) will be R2, b) will be a new proposal for R3+  (Intel question 
whether we need b) proposal)

   Intel: support SOL001/TOSCA NFV DM or code contributor

   ARM: support SOL001

   AT(Andy) support TOSCA NFV DM for onboarding,  along with Heat

   Nokia:  support SOL001, code contributor(check)

   Ericsson: support SOL 001/TOSCA NFV DM ,code(check)

   Netcracker?

   Huawei support SOL001/TOSCA NFV DM code contributor

   ZTE:  support SOL001/TOSCA NFV DM code contributor

   China Mobile support TOSCA NFV DM code contributor

Comments:

a) current ONAP IM is more than IFA 11, we need to follow ONAP spec

b) China Mobile question on SOL001 IPR issue, OASIS TOSCA is more IPR 
friendly.

2)Resource IM: Xu Yang

  community agreed to do majority vote for the not agreed attributes in the 
end.

  YANG Xu will organize the call on wednesday and thursday, then put vote 
spreedsheet on the wiki about the left issues. End of vote will be Monday

  company who disagree with some attbiutes will be recorded



3)Service IM:Lingli Deng/Maopeng Zhang

  Lingli and Maopeng will make R2 proposal asap.



4) Others (no time to discuss)

  Parser:Atul Purohit

  Modeling tools: Nigel Davis,

  Modeling spec Papyrus: Jessie Jewitt

  A James Forsyth

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

Re: [onap-discuss] [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to ETSI NFV ISG

[denghui (L)]

Hello modelers

Below page has been created:
https://wiki.onap.org/display/DW/20180225+Progress+summary

feel free to comment if any update are needed.

Thanks a lot

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of denghui (L)
Sent: Sunday, February 25, 2018 8:48 AM
To: Stephen Terrill <stephen.terr...@ericsson.com>; 
onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>
Cc: Rittwik Jana <rittwik.j...@gmail.com>
Subject: Re: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to 
ETSI NFV ISG

Hi Steven

Your suggestion sounds reasonable, I will do wiki and send an informal email to 
the ETSI NFV list before next Monday

Best regards,

DENG Hui

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Friday, February 23, 2018 4:07 PM
To: denghui (L) <denghu...@huawei.com<mailto:denghu...@huawei.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Cc: Rittwik Jana <rittwik.j...@gmail.com<mailto:rittwik.j...@gmail.com>>
Subject: RE: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to 
ETSI NFV ISG

Hi Deng,

In the previous TSC when there was a discussion about liaisons it was pointed 
out that some work was required as there is no liaison relationship 
established, I guess that hasn't happened.  When it comes to the liaisons that 
say "please take consideration of my work" they don't mean much as the real 
work has to be driven by the work items etc by the participants there.  I 
assume that the goal of the LS is to have a place to raise the issue of 
evolution of the specs.  You could acthieve that by having a status wiki in 
modelling and a friendly informal email to the etsi lists pointing to it.

BR,

Steve

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, February 22, 2018 1:23 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Cc: Rittwik Jana <rittwik.j...@gmail.com<mailto:rittwik.j...@gmail.com>>
Subject: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to ETSI 
NFV ISG

Hello all

Based on email discussion, enclosed draft liaison from modeling subcommittee to 
ETSI NFV ISG is as the enclosed.

Thanks a lot for you review

Best regards,

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

Re: [onap-discuss] [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to ETSI NFV ISG

[denghui (L)]

Hi Steven

Your suggestion sounds reasonable, I will do wiki and send an informal email to 
the ETSI NFV list before next Monday

Best regards,

DENG Hui

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Friday, February 23, 2018 4:07 PM
To: denghui (L) <denghu...@huawei.com>; onap-discuss@lists.onap.org; onap-tsc 
<onap-...@lists.onap.org>
Cc: Rittwik Jana <rittwik.j...@gmail.com>
Subject: RE: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to 
ETSI NFV ISG

Hi Deng,

In the previous TSC when there was a discussion about liaisons it was pointed 
out that some work was required as there is no liaison relationship 
established, I guess that hasn't happened.  When it comes to the liaisons that 
say "please take consideration of my work" they don't mean much as the real 
work has to be driven by the work items etc by the participants there.  I 
assume that the goal of the LS is to have a place to raise the issue of 
evolution of the specs.  You could acthieve that by having a status wiki in 
modelling and a friendly informal email to the etsi lists pointing to it.

BR,

Steve

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, February 22, 2018 1:23 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Cc: Rittwik Jana <rittwik.j...@gmail.com<mailto:rittwik.j...@gmail.com>>
Subject: [onap-tsc] [modeling]Liaison from ONAP modeling subcommittee to ETSI 
NFV ISG

Hello all

Based on email discussion, enclosed draft liaison from modeling subcommittee to 
ETSI NFV ISG is as the enclosed.

Thanks a lot for you review

Best regards,

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

[onap-discuss] [modeling]Liaison from ONAP modeling subcommittee to ETSI NFV ISG

[denghui (L)]

Hello all

Based on email discussion, enclosed draft liaison from modeling subcommittee to 
ETSI NFV ISG is as the enclosed.

Thanks a lot for you review

Best regards,

DENG Hui
<>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling] 20180213 modeling subcommittee Meeting Minutes

[denghui (L)]

Hello all

Modeling subcommittee has been questioned when will our modeling DM spec come 
out, below are our meeting minutes this week.

Hi Kenny, We are going to cancel next week modeling subcommittee call due to 
china new year, thanks a lot for your help

-
20180213 modeling subcommittee Meeting agenda and Minutes
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

1)  Resource IM YANG Xu
there is no consensus whether we need to follow ETSI NFV naming convention or 
change into ONAP naming.
Two polls will be set to decide the naming convention and future meeting time. 
The polls close on Feb 28th.
https://wiki.onap.org/display/DW/Meeting+Time+Poll
https://wiki.onap.org/display/DW/Naming+Convention+Poll

2)  Data modeling Anatoly Katzman
DENG Hui: modeling subcommittee have to finalize the 1st draft version by M3 
deadline, in this case, we need to allow solutions only 1 week, and make the 
decision on Feb. 28th.
DENG Hui: there are two solutions on the table now: Monolithic VDU design and 
TOSCA NFV profile, we are not make decision today, but would get basic impress 
what company would like to follow:
Vendors:
1) Ericsson  vote for  of ETSI NFV Profile
2) ZTE   vote for  ETSI SOL NFV profile
3) Huawei vote for  ETSI NFV profile
4) Nokia --no one on call
5) Netcracker (Priya TG) vote for ETSI NFV Profile
Operators:
1) AT: Monolithic VDU
2) China Mobile: lacking information to do an informed comparison hence no 
strong opinion to any specific proposal currently. The options on the table 
should firstly meet the requirement as a unified DM in the community with 
consistency to the IM and implementable in Beijing release cadence with vendors 
support. It would be better if we could align with SDO in the same time.
Next step:
a) check whether we have 3rd solution or not in a week
b) make decision on Feb.27th

3) Modeling tool poll(Jessie)
1) use github for papyrus revision
fine from IM's team (Kevin, Andy, Lingli, and YANG Xu)
Anyway, polling will end by the end of Feb.

Best regards,

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

Re: [onap-discuss] [modeling] Whether How and when we should move to Github for modeling spec update process

[denghui (L)]

Hi Brian

Yes, could you kindly help to do it under modeling tools wiki page?

Thanks a lot for your help
Best regards,

DENG Hui

From: Brian Hedstrom [mailto:brian.hedst...@oamtechnologies.com]
Sent: Friday, February 2, 2018 11:12 PM
To: denghui (L) <denghu...@huawei.com>
Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org P 
<onap-...@lists.onap.org>; jessie jewitt <jessie.jew...@oamtechnologies.com>
Subject: Re: [modeling] Whether How and when we should move to Github for 
modeling spec update process

Hi Deng,
I'm in favor of using Git for model development.
Do we want to add a Poll page to the wiki to track participant voting on this 
topic?

Thanks
Brian

On Wed, Jan 31, 2018 at 7:31 PM, denghui (L) 
<denghu...@huawei.com<mailto:denghu...@huawei.com>> wrote:
Hello modeling subcommittee,

Many Thanks to Jessie’s kind presentation on GitHub for Papyrus model.
https://wiki.onap.org/display/DW/Modeling+sub-committee+Contributions
https://wiki.onap.org/download/attachments/16003450/GitHub%20for%20Papyrus%20Model.pptx?api=v2

Due to time limitation, we would like to discussion in the list together with 
the communities whether, how and when we should move to Github to manage the 
modeling spec update process.

Thanks a lot for your advice
Best regards,

DENG Hui



--
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oam.technology<http://oam.technology>
brian.hedst...@oamtechnologies.com<mailto:brian.hedst...@oamtechnologies.com>
720-470-7091
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [modeling]Modeling call next week

[denghui (L)]

Hi Kenny

From latest program: https://wiki.onap.org/display/DW/VF2F+Feb.+5-8%2C+2017
We are starting from 9:30am eastern time , which is 10:30pm Beijing time

Thanks  a lot for your reminder

Best regards,

DENG Hui

From: Kenny Paul [mailto:kp...@linuxfoundation.org]
Sent: Saturday, February 3, 2018 3:29 AM
To: denghui (L) <denghu...@huawei.com>
Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org P 
<onap-...@lists.onap.org>; Rittwik Jana <rittwik.j...@gmail.com>; 邓灵莉 
<denglin...@chinamobile.com>
Subject: Re: [modeling]Modeling call next week

Hi Deng,
I'll cxl next week's call even though these requests should always be routed 
throgh the wiki page
Meeting Requests, Changes, Hosting & 
Recording<https://wiki.onap.org/pages/viewpage.action?pageId=8231933>

I don’t understand the sentence that follows however. Not sure if this is a 
request for a change, or what the intent is.
>> we will have our modeling subcommittee session on Wednesday 9am eastern 
>> time, 10pm Beijing time.

Thanks!

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>
510.766.5945


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

Hello all

Our modeling subcommittee call will be cancelled next week due to vf2f,

Hi Kenny,

could you kindly help to cancel next week call, thanks a lot

and we will have our modeling subcommittee session on Wednesday 9am eastern 
time, 10pm Beijing time.

1)  Resource IM Xu Yang

2)  Service IM Maopeng Zhang

3)  Data modeling Anatoly

4)  Centralized Parser Atul

5)  Modeling tools Nigel

6) Projects follow up modeling spec discussion (Modeling contact from each 
Project)

Let me know if you have any other suggestions.



Thanks a lot



DENG Hui



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

[onap-discuss] [modeling]Modeling call next week

[denghui (L)]

Hello all

Our modeling subcommittee call will be cancelled next week due to vf2f,

Hi Kenny,

could you kindly help to cancel next week call, thanks a lot

and we will have our modeling subcommittee session on Wednesday 9am eastern 
time, 10pm Beijing time.

1)  Resource IM Xu Yang

2)  Service IM Maopeng Zhang

3)  Data modeling Anatoly

4)  Centralized Parser Atul

5)  Modeling tools Nigel

6) Projects follow up modeling spec discussion (Modeling contact from each 
Project)
Let me know if you have any other suggestions.

Thanks a lot

DENG Hui

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

[onap-discuss] [modeling] Whether How and when we should move to Github for modeling spec update process

[denghui (L)]

Hello modeling subcommittee,

Many Thanks to Jessie's kind presentation on GitHub for Papyrus model.
https://wiki.onap.org/display/DW/Modeling+sub-committee+Contributions
https://wiki.onap.org/download/attachments/16003450/GitHub%20for%20Papyrus%20Model.pptx?api=v2

Due to time limitation, we would like to discussion in the list together with 
the communities whether, how and when we should move to Github to manage the 
modeling spec update process.

Thanks a lot for your advice
Best regards,

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

[onap-discuss] [modeling] the training videos of Papyrus have been updated

[denghui (L)]

Hello all

Many thanks to Nigel who has kindly help to update all videos, please feel free 
to study them online.
https://wiki.onap.org/display/DW/Modeling+tools

Best regards,

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

[onap-discuss] remove the committer whose email is invalid

[denghui (L)]

Hello all

Does anybody know that I could remove the committer if that email address is 
not valid anymore?

Thanks a lot for your advice

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

[onap-discuss] [modeling] Papyrus trianing video

[denghui (L)]

Hello all

The video is posted here, please feel free to study it for our future IM design.
https://wiki.onap.org/display/DW/Modeling+tools
https://zoom.us/recording/play/hifhg4gm8ZqlA-LkeM9qqsNiG3JMq4qdeFilqdKXK6wcYabYufNH86MhaTlEjJHY

Thanks again for Nigel Davis's kind help on this

Best regards,

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

[onap-discuss] [modeling] ONAP modeling tool Papyrus trianing session

[denghui (L)]

Hello all

We are very honor to invite Nigel Davis to give a tutorial about Papyrus which 
will be used for ONAP Info modeling.
Since Modeling subcommittee is full of schedule every week. We arrange this 
tutorial on this Friday VNFSDK Modeling sub-team session.
https://wiki.onap.org/display/DW/2017-12-22+Meeting+notes

Andy, could you kind help to post zoom ID and time here?

Please come and join us
Best regards,

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

[onap-discuss] [modeling] ONAP Modeling workshop notes

[denghui (L)]

Hello All

ONAP Modeling workshop minutes

1   Service IM: back to service(customer facing service)/service 
component(resource facing service, e.g. network service)/resource/resource 
component layering class diagram, not using composite/decorative pattern for 
Beijing, translate into papyrus format based on agreed clean version.

2   Resource IM: For design time model, agreed to work on a subset of 
IFA011 for Beijing (i.e. remove internalCP as show in the discussion page), 
agreed to add hierarchy for CP inheritance, agreed to work on the latest 
version of IFA011 (v2.3.1). For run time model, agreed to refactor some of the 
attributes (e.g., ip addresses).

3   Design time DM: Agreed on Service and Resource hierarchy, while both 
service and resource can leverage substitution mapping mechanism to realize 
self-recursion aggregation or composition relations if needed by the IM.

4   Runtime DM A will update NFV related API? in order to align with 
Information model, and notify the related project accordingly

5   Agreed to work on a concrete example to show how ONAP IM maps to ONAP 
DM.

6   R2 will be based on TOSCA simple profile 1.1 other than 1.2, but may 
need to consider some special feature of 1.2 if needed by the use case

7   Each DF should be described in a single TOSCA Service template (VNFD) 
and considered as a single VNF, in Beijing release, one VNF package will only 
contain one VNFD

8   R2+ Modeling spec naming convention will use the low camel for 
attribute names, will consider to add naming convention check during M1/M4

9   WiKi will be used for Modeling spec intermediate version,  Readthedoc 
will be used for published version

10Michela volunteer to start to work on the common terminologies for ONAP 
modeling

11Modeling spec will be migrate to Papyrus asap, needs to decide version 
number and setup the timeline to proceed it

12Use Jira/backlog to track the work asap

Thanks for your checking
Best regards

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

[onap-discuss] SDO slides in ONAP Forum this week

[denghui (L)]

Hello all

Please check the enclosed slide for SDOs, thanks a lot for your checking
https://wiki.onap.org/display/DW/External+SDO+session+in+ONAP+Forum+Dec.+12th%2C+2017

Really thanks MEF/TMF/ETSI NFV/OASIS TOSCA/IETF/ONF for kind help

Thursday workshop slide will be posted on Thursday program page.

Best regards,

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

[onap-discuss] [modeling] ONAP modeling workshop program

[denghui (L)]

Hello all

There is a small change to let Kevin present first about IM then let SDO to 
discuss it later.
https://wiki.onap.org/display/DW/ONAP+Modeling+Workshop+Program

Thanks a lot

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

[onap-discuss] [modeling]Zoom ID for ONAP modeling workshop

[denghui (L)]

Hello all

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/349619781
 Or iPhone one-tap : US: +16699006833,,349619781# or +16465588656,,349619781# 
Or Telephone: Dial(for higher quality, dial a number based on your current 
location)? US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll 
Free) or +1 855 880 1246 (Toll Free) Meeting ID: 349 619 781 International 
numbers available: 
https://zoom.us/zoomconference?m=LF_IFaE8tqx1uINPhUk2FGmc_M9ohwO1

Thanks

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

[onap-discuss] [modeling] ONAP Modeling Workshop on Thursday

[denghui (L)]

Hello all

Tomorrow workshop venue address is:

Huawei Technologies

Checkin: Bldg B

Meeting Venue: Bldg C 1F-05 Training Room

2330 Central Expressway

Santa Clara,  CA 95050

Check-in Instruction:
1) All attendees must use self sign in system to check in at the main reception 
desk located at Bldg B lobby.
For any external guests who bring in their own laptops must sign a laptop 
registration form at the sign in, name tag will be issued afterwards.

2) Follow the conference sign to the meeting room in Bldg C.

Time

Topic

Prime

09:00 - 09:05

Host welcome and facility

Huawei

09:05 - 09:10

 ONAP President

Yacheng Wang

09:10 - 10:50

SDO Session

09:10 - 09:30

MEF

John

09:30 - 09:50

TMF

John Wilmes

09:50 - 10:10

 ONF

Nigel

10:10 - 10:30

ETSI NFVETSI NFV

Andrei and Shitao

10:30 - 10:50

OASIS TOSCA

Shitao & Alex

10:50 - 11:00

Break

11:00 - 12:00

CIM discussion

Lingli/Andy/John

12:00 - 13:00

Lunch

13:00 - 14:00

Resource Session

Andy & David & Yangxu

13:00 - 13:30

Resource IM

13:00 - 14:00

Resource DT DM

14:00 - 15:00

Service Session

Lingli & Maopeng & David

14:00 - 14:30

Service IM

14:30 - 15:00

Service DT DM

15:00 - 15:30

RT DM A

Jimmy & Yangxu & Maopeng

 15:30 - 16:00

Close Loop Automation Model

 Ron Shacham

 16:00 - 16:30

MultiVIM FCAPS Model

 Xinhui Li

 16:30 - 17:00

Wrapup


Looking forward to seeing you tomorrow
Best regards,

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

[onap-discuss] [Modeling] Modeling session today - Update

[denghui (L)]

Hello all



There is one mistake, updated again

1)  11:20 Considerations of Modelling Evolution in ONAP 


Michela Bevilacqua

Room: Auditorium

https://onapbeijing2017.sched.com/event/D5pe/considerations-of-modelling-evolution-in-onap


2)  1:45pm- 3:15pm Modeling subcommittee for R2+ SPEC
https://onapbeijing2017.sched.com/event/D7Kv/modeling-subcommittee-for-r2model

Room: 152

Agenda:

DM - David (30min)

IM/DM progress report -Lingli (20min)

IM new proposal, - Kevin (30min)


3)  3:30 - 4:15

Modeling NFV Deployment Flavor discussion

https://onapbeijing2017.sched.com/event/00c8844e7f69f2ef7a12b1f359792d39/Modeling+Deployment+Flavor+in+Modeling+Subcommittee
Room: 174


4)  4:15 - 4:50 Deployment Flavor for NFV Modeling - Challenges and Trends 

https://onapbeijing2017.sched.com/event/DAHm

Pyria T.G

Room: 152

Anyway, we have workshop tomorrow,
https://wiki.onap.org/display/DW/ONAP+Modeling+Workshop+20171214+Registration+Page

Thanks a lot for your attendance
Best regards,

DENG Hui

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

[onap-discuss] [Modeling] Modeling session today

[denghui (L)]

Hello all

This is the day before tomorrow workshop, today session related to modeling 
will be :


1)  11:20 Considerations of Modelling Evolution in ONAP 

Michela Bevilacqua
Room: Auditorium


2)  1:45pm- 3:15pm Modeling subcommittee for R2+ SPEC

Room: 152

Agenda:

DM - David (30min)

IM/DM progress report -Lingli (20min)

IM new proposal, - Kevin (30min)


3)  3:30 - 4:15

Modeling NFV Deployment Flavor discussion
Room: 175


4)  4:15 - 4:50 Deployment Flavor for NFV Modeling - Challenges and Trends 


Pyria T.G

Room: 152

Anyway, we have workshop tomorrow,
https://wiki.onap.org/display/DW/ONAP+Modeling+Workshop+20171214+Registration+Page

Thanks a lot for your attendance
Best regards,

DENG Hui

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

[onap-discuss] [modeling] A Runtime for VNF and VNFC Instance

[denghui (L)]

Hi Jimmy and Chesla

https://wiki.onap.org/display/DW/Run+Time+Model+Clean+Version

Yang Xu

Please add description of mandatory and optional on the wiki page
Please help to review it?

Thanks

DENG Hui

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

[onap-discuss] [modeling] today modeling teleconf is cancelled.

[denghui (L)]

Hello all

Apologize for not considering thanks giving holiday, lots of people are still 
not yet return back, so we will cancel this week teleconf.

Best regards,

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

Re: [onap-discuss] Modeling Project doc missing

[denghui (L)]

Thank you, Eric

From: eric.deb...@orange.com [mailto:eric.deb...@orange.com]
Sent: Thursday, November 16, 2017 4:09 PM
To: denghui (L); DeWayne Filppi; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Modeling Project doc missing

Hello

I will help DeWayne

Eric
De : denghui (L) [mailto:denghu...@huawei.com]
Envoyé : jeudi 16 novembre 2017 03:16
À : DeWayne Filppi; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc : DEBEAU Eric IMT/OLN
Objet : RE: [onap-discuss] Modeling Project doc missing

Hi Eric

Since you contributed this part document, do you want to help Aria by including 
them?

Thanks

DENG Hui

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of DeWayne Filppi
Sent: Thursday, November 16, 2017 12:52 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] Modeling Project doc missing

The ARIA REST API is contributed code to the ONAP project; ARIA includes a 
Python library and CLI.  Runtime ARIA in ONAP lives in a container ( 
https://gerrit.onap.org/r/gitweb?p=so.git;a=blob;f=packages/docker/src/main/docker/docker-files/Dockerfile.aria).
  Also contributed to ONAP is a Java binding for this REST API (  
https://gerrit.onap.org/r/gitweb?p=so.git;a=tree;f=aria/aria-rest-java-client). 
 The Java binding doesn't model TOSCA itself, it just provides a Java binding 
for the REST API.  Note that the REST API provides for fetching the parsed 
model representation as JSON, but that call isn't in the Java binding (yet).   
There has been talk about moving the ARIA work out of SO and into the Common 
Controller SDK, which I think makes some sense.
Currently the container isn't pushing properly to the Docker repo, but if you 
want to look, a recent version lives on Dockerhub as cloudifyco/aria:0.1.1.

DeWayne

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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

Re: [onap-discuss] Modeling Project doc missing

[denghui (L)]

Hi Eric

Since you contributed this part document, do you want to help Aria by including 
them?

Thanks

DENG Hui

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of DeWayne Filppi
Sent: Thursday, November 16, 2017 12:52 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Modeling Project doc missing

The ARIA REST API is contributed code to the ONAP project; ARIA includes a 
Python library and CLI.  Runtime ARIA in ONAP lives in a container ( 
https://gerrit.onap.org/r/gitweb?p=so.git;a=blob;f=packages/docker/src/main/docker/docker-files/Dockerfile.aria).
  Also contributed to ONAP is a Java binding for this REST API (  
https://gerrit.onap.org/r/gitweb?p=so.git;a=tree;f=aria/aria-rest-java-client). 
 The Java binding doesn't model TOSCA itself, it just provides a Java binding 
for the REST API.  Note that the REST API provides for fetching the parsed 
model representation as JSON, but that call isn't in the Java binding (yet).   
There has been talk about moving the ARIA work out of SO and into the Common 
Controller SDK, which I think makes some sense.
Currently the container isn't pushing properly to the Docker repo, but if you 
want to look, a recent version lives on Dockerhub as cloudifyco/aria:0.1.1.

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

[onap-discuss] [modeling] Please help to register ONAP Modeling workshop on Dec. 14th Thursday

[denghui (L)]

Hello all

Please don't do poll any more , just register here:
https://wiki.onap.org/display/DW/ONAP+Modeling+Workshop+20171214+Registration+Page

Please register before Dec. 8th, registrations will be closed on that day. The 
room will be only limited to 50 people.
If we reach that number before that Dec. 8th, then the registration page will 
also be closed.


Please indicate if your have any food preference like Vegetarian, or others,

if you don't want disclose it on the webpage, please email to me 
(denghu...@huawei.com) and May 
(may.c...@huawei.com)

Thanks a lot for your attendance
Best regards,

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

[onap-discuss] ONAP Modeling R2+ A

[denghui (L)]

Hi Jimmy,

As we are working on R2 modeling, there are questions regarding A service 
modeling at  https://wiki.onap.org/pages/viewpage.action?pageId=16004631

Would you kindly help to clarify them?

Thanks a lot for your help

DENG Hui


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

[onap-discuss] ONAP R2+ IM discussion

[denghui (L)]

Hi Kevin and Andy,

As we are working on R2 modeling, there are questions regarding ECOMP IM 
service/resource modeling at  
https://wiki.onap.org/pages/viewpage.action?pageId=16004631

Would you help to clarify them?

BTW, I recall that you planned to release an updated version of ECOMP IM model 
on Oct 31.
It would be helpful if you could share the doc and add a link at the modeling 
working space.

Thanks,
DENG Hui

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

[onap-discuss] [modeling] ONAP Modeling workshop final decision

[denghui (L)]

Hello all

According to doodle poll, there are 25 people prefer Thursday and 10 people 
prefer Tuesday. https://doodle.com/poll/8m5nhagvqkfw2uag

Because time is so urgent, thanks TSC meeting suggestion, let's do below 
arrangement:

1)  Half day or 2 hours ONAP modeling workshop on Tuesday ( For those 
people's topic who are not able to attend Thursday workshop)

2)  1 day ONAP modeling workshop on Thursday

I do believe more people will attend this workshop, will setup the registration 
page asap to accommodate the meeting room and Lunch on Thursday.

Thanks a lot for your attendance
Best regards,

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

[onap-discuss] [Modeling] ONAP Modeling workshop proposal -- doodle poll

[denghui (L)]

Hello all

I created a doodle poll to check it again:
https://doodle.com/poll/8m5nhagvqkfw2uag

thanks a lot for your input.

Best regards,

DENG Hui

From: Vul, Alex [mailto:alex@intel.com]
Sent: Thursday, November 2, 2017 11:56 PM
To: denghui (L) <denghu...@huawei.com>; onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Cc: 'Rittwik Jana' <rittwik.j...@gmail.com>
Subject: RE: [Modeling] ONAP Modeling workshop proposal

Hi,

I think this is a really good idea, provided the workshop participants are 
up-to-speed on what we have been doing, where we need to be going and can hit 
the ground running. As you said, time is of the essence…

Kind regards,

Alex Vul
Intel Corporation

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, November 2, 2017 8:50 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Cc: 'Rittwik Jana' <rittwik.j...@gmail.com<mailto:rittwik.j...@gmail.com>>
Subject: [onap-tsc] [Modeling] ONAP Modeling workshop proposal

Hello all

Modeling subcommittee is in the very tight schedule, plan to have R2 modeling 
ready by December and intends to call for feedback from SDOs and identify 
potential cooperation areas. And many SDOs propose to collaborate with ONAP 
such as MEF/TMF/ETSI NFV, and in order to avoid the confliction with other 
sessions in Forum, propose to have 1 day workshop right after Forum.

Program could be:
u ONAP modeling overview
u SDOs input & feedback
u Collaboration discussion

Time: Dec. 14th 2017 (Thursday ）
Location: Because Intel and Cablelabs can’t host it on Thursday, suggest Huawei 
office in Santa Clara

Please kindly help to feedback by the end of this Friday, we are seeking for 
whether there is a serious issue or not.

Thanks a lot for your contribution
Best regards,

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

[onap-discuss] [Modeling] ONAP Modeling workshop proposal

[denghui (L)]

Hello all

Modeling subcommittee is in the very tight schedule, plan to have R2 modeling 
ready by December and intends to call for feedback from SDOs and identify 
potential cooperation areas. And many SDOs propose to collaborate with ONAP 
such as MEF/TMF/ETSI NFV, and in order to avoid the confliction with other 
sessions in Forum, propose to have 1 day workshop right after Forum.

Program could be:
u ONAP modeling overview
u SDOs input & feedback
u Collaboration discussion

Time: Dec. 14th 2017 (Thursday ）
Location: Because Intel and Cablelabs can’t host it on Thursday, suggest Huawei 
office in Santa Clara

Please kindly help to feedback by the end of this Friday, we are seeking for 
whether there is a serious issue or not.

Thanks a lot for your contribution
Best regards,

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

[onap-discuss] [modeling]RE: [onap-tsc] Usecase subcommittee meeting 23/10/2017 (wide discussion of Network Slicing)

[denghui (L)]

This is a reminder email to modeling subcommittee, 5G use case would like to 
invite modeling subcommittee to join their discussion next week,

Thanks

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Friday, October 20, 2017 5:43 PM
To: onap-usecase...@lists.onap.org; onap-...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org
Subject: [onap-tsc] Usecase subcommittee meeting 23/10/2017 (wide discussion of 
Network Slicing)

Hi all,

Here is agenda for Monday’s meeting.

1.   Short overview of R1 vVoLTE and R-vCPE status and needs

2.   Beijing Release, 5G and network slicing – the next level of details. 
We invite architecture and modelling subcommittees representatives along with a 
different projects representatives to participate and provide their view and 
comments

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.jpg@01D349CC.C14ECF80]


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

Re: [onap-discuss] Weekly Report from modeling subcommittee

[denghui (L)]

Hi

The slide is always on the wiki page
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

DENG hui

From: Vul, Alex [mailto:alex@intel.com]
Sent: Thursday, October 19, 2017 9:54 AM
To: denghui (L) <denghu...@huawei.com>; onap-...@lists.onap.org; onap-discuss 
<onap-discuss@lists.onap.org>
Subject: RE: Weekly Report from modeling subcommittee

Hi,

Can you please publish the slides that were shown during the meeting?

Thanks in advance,

Alex


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: Wednesday, October 18, 2017 6:52 PM
To: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>; onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-tsc] Weekly Report from modeling subcommittee

Hi

This week we reviewed the modeling design principle and guideline, the draft 
version has been review for 1st round, hope we could finalize it based on 2nd 
round review in this week.
One of core idea is ONAP R2+ modeling will use SDC DM and ECOMP IM as the 
starting point

Best regards,

DENG Hui

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen Terrill
Sent: Thursday, October 19, 2017 4:12 AM
To: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> P 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Cc: onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>
Subject: [onap-tsc] Weekly Report from security subcommittee

Hi,

Here is the report from the security sub-committee to the TSC.

This week we reviewed more updates to the S3P requirements from a security 
perspective to align on the per release text from the security sub-committee 
perspective (the per project was fine).

Discussions on how to use coverity for the static code scanning continue

The topic of credential management is progressing.  The idea is to firm up the 
proposal for recommendation promptly.  The current proposal can be found in 
section 2 of 
https://wiki.onap.org/display/DW/ONAP+security+Recomendation+Developement . 
Comments from the community are most appreciated.

Best Regards,

Steve.

[?? Ericsson]<http://www.ericsson.com/>
STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>
www.ericsson.com<http://www.ericsson.com>


[?? 
http://www.ericsson.com/current_campaign]<http://www.ericsson.com/current_campaign>

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<http://www.ericsson.com/email_disclaimer>

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

[onap-discuss] Weekly Report from modeling subcommittee

[denghui (L)]

Hi

This week we reviewed the modeling design principle and guideline, the draft 
version has been review for 1st round, hope we could finalize it based on 2nd 
round review in this week.
One of core idea is ONAP R2+ modeling will use SDC DM and ECOMP IM as the 
starting point

Best regards,

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: Thursday, October 19, 2017 4:12 AM
To: onap-...@lists.onap.org P 
Cc: onap-sec...@lists.onap.org
Subject: [onap-tsc] Weekly Report from security subcommittee

Hi,

Here is the report from the security sub-committee to the TSC.

This week we reviewed more updates to the S3P requirements from a security 
perspective to align on the per release text from the security sub-committee 
perspective (the per project was fine).

Discussions on how to use coverity for the static code scanning continue

The topic of credential management is progressing.  The idea is to firm up the 
proposal for recommendation promptly.  The current proposal can be found in 
section 2 of 
https://wiki.onap.org/display/DW/ONAP+security+Recomendation+Developement . 
Comments from the community are most appreciated.

Best Regards,

Steve.

[?? Ericsson]
STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R 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


[?? 
http://www.ericsson.com/current_campaign]

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

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

[onap-discuss] [modeling] RE: ARC Call this week

[denghui (L)]

Hello all

Just remind that is the invite to modeling subcommittee, in the Arc call next 
Tuesday, they will discuss about external controller issue,
Please help to attend it,

Thanks a lot

DENG Hui
From: onap-arc-boun...@lists.onap.org 
[mailto:onap-arc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Sunday, October 15, 2017 8:45 PM
To: Christopher Donley (Chris) 
>; 
onap-...@lists.onap.org; 
onap-...@lists.onap.org
Cc: Nagarajan, Ramesh A. 
>
Subject: Re: [Onap-arc] ARC Call this week

Thanks, Chris,

Just to highlight that we also ask modelling subcommittee representatives and 
all relevant projects representatives to participate as Ramesh will present 
External Controller concept. The relevant slides are uploaded under 
https://wiki.onap.org/display/DW/ONAP+external+controller+integration

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3460B.B7218C10]

From: onap-arc-boun...@lists.onap.org 
[mailto:onap-arc-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris)
Sent: Sunday, October 15, 2017 3:35 PM
To: onap-...@lists.onap.org
Subject: [Onap-arc] ARC Call this week

Team,

Steve Terrill will host the ARC call this week, as I'll be on a plane during 
our call.

We have two topics on the preliminary agenda:

*R2 architecture (Parviz)

*External Controller (Alla)

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

[onap-discuss] [Modeling] Invite comments on modeling design principles and guideline

[denghui (L)]

This is reminder, deadline will be this Sunday.

Thanks a lot

DENG Hui

From: denghui (L)
Sent: Wednesday, October 11, 2017 3:24 AM
To: onap-discuss <onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org>
Subject: [Modeling] Invite comments on modeling design principles and guideline

Hello all,

We have create a page which list the modeling design principles and guidelines 
for R2+ as below
https://wiki.onap.org/display/DW/ONAP+Modeling+Design+Principles+and+Guidelines

Many thanks to Rittwik, David and Lingli for initial contribution,
and there were some comments and revision from last Modeling teleconf.

We plan to close this on Oct. 15, this Sunday, please kindly help to post your 
comments either this thread or on the wiki page.

Thanks again
Best regards,

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

[onap-discuss] [Modeling] Invite comments on modeling design principles and guideline

[denghui (L)]

Hello all,

We have create a page which list the modeling design principles and guidelines 
for R2+ as below
https://wiki.onap.org/display/DW/ONAP+Modeling+Design+Principles+and+Guidelines

Many thanks to Rittwik, David and Lingli for initial contribution,
and there were some comments and revision from last Modeling teleconf.

We plan to close this on Oct. 15, this Sunday, please kindly help to post your 
comments either this thread or on the wiki page.

Thanks again
Best regards,

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

[onap-discuss] [modeling] modeling design principals and guideline

[denghui (L)]

Hello all

Based on the summary of our F2F meeting, please send your suggestions to David, 
Lingli and Rittwik asap within this week.
They agree to kindly help to coordinate this work, many thanks for their help

-By Oct 15: set guidelines and principals
*Methodology of developing R2 IM/DM
*e.g. create a high-level class diagram, specify how to add extensions, 
and how to define namespaces
*E.g. best efforts to derive from TOSCA Simple Profile 1.2 normaltives


Best regards,

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

[onap-discuss] External SDOs session slides during last week event

[denghui (L)]

Hello all

Below link include the slides presented during last week,
https://wiki.onap.org/display/DW/External+SDOs+session+in+Developer+event+in+September

Many thanks to those who kindly help to present in our event

Best regards,

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

[onap-discuss] [modeling] teleconf of modeling project/subcommittee this week is cancelled

[denghui (L)]

Hello all

You might know that 1 billion Chinese people are taking vocation this week all 
together, so considering the hard life in china are not easy, please allow us 
to cancel this week teleconf for modeling project.

Hi Kenny, would you mind to kindly help us to send meeting cancel to the list? 
Thanks a lot for your kind help again

Best regards,

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

[onap-discuss] [Modeling] Session this afternoon will start on time at 3pm

[denghui (L)]

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

Re: [onap-discuss] Schedule Changes for the Paris-Saclay Face to Face meeting - Thursday Sept: 28th

[denghui (L)]

Just follow up , we have invited vice chair of ETSI NFV ISG, Bruno (Orange ) to 
introduce the consideration of how both ONAP and ETSI NFV may work together.
We also have other standard bodies contact point like Oasis Tosca/TMF/3GPP 
SA2/SA5 speech. Thanks them for contribution here.

https://wiki.onap.org/display/DW/External+SDOs+session+in+Developer+event+in+September

Please join us in the plenary room at 9am.

Thanks a lot

DENG Hui

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Thursday, September 28, 2017 7:45 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Schedule Changes for the Paris-Saclay Face to Face 
meeting - Thursday Sept: 28th

Hello:

For those wanting to attend sessions at the Paris Saclay developer event today, 
we have made some schedule changes from yesterday.  To accommodate the travel 
schedules of some of the Project Technical Leaders and TSC members, we've moved 
the Amsterdam M4 Milestone review to begin at 10am CET and run until 3pm CET 
with a break for lunch between 11:30am and 12:30pm CET.   For the full schedule 
please see the wiki page here:  
https://wiki.onap.org/display/DW/Agenda+for+M4+Review

To accommodate this change in the M4 timing, we've recently moved sessions that 
had been in those slots to other times during the day.  Please double check the 
Event wiki page for updates on the Thursday sessions that you want to attend.

https://wiki.onap.org/display/DW/ONAP+Paris+Event+Schedule+September+25-28%2C+2017

Sorry for this last minute change.

Best,

Phil.
--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling]zoom number for now

[denghui (L)]

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

Re: [onap-discuss] [onap-tsc] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

[denghui (L)]

Andrei and Alex

Our key modeling implementers will not be available with enough time this 
afternoon after TSC meeting, that will be really hard to discuss it.
So we have no choice only this morning

Thanks for your understanding

DENG Hui


From: Andrei Kojukhov [mailto:andrei.kojuk...@amdocs.com]
Sent: Wednesday, September 27, 2017 10:05 AM
To: Vul, Alex <alex@intel.com>; denghui (L) <denghu...@huawei.com>; 
onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>
Subject: RE: [onap-tsc] [onap-discuss] [Modeling] Modeling subcommittee F2F 
Cont. on Wednesday

Dear Deng Hui,

I would also keep the meeting as it was originally planned later today so the 
VNF-SDK Modeling team will be involved.

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 Vul, Alex
Sent: Wednesday, September 27, 2017 9:58 AM
To: denghui (L) <denghu...@huawei.com<mailto:denghu...@huawei.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: Re: [onap-tsc] [onap-discuss] [Modeling] Modeling subcommittee F2F 
Cont. on Wednesday

Deng Hui,

The R2 VNF modeling work is being led by Andy as part of the VNF SDK project 
being driven by Chris. I think it would be good for the folks who doing the 
model definition to actually hear the inputs... :) Otherwise, I don't see the 
point...

Kind regards,

Alex

From: denghui (L) [mailto:denghu...@huawei.com]
Sent: Wednesday, September 27, 2017 12:50 AM
To: Vul, Alex <alex@intel.com<mailto:alex@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: RE: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on 
Wednesday

Alex,

we have already heard yesterday feedback from Chris Donley Andy, VNFSDK & 
Architecture, ,
and now we need to move on and would expect more from the implementers side.

Thanks

DENG Hui

From: Vul, Alex [mailto:alex@intel.com]
Sent: Wednesday, September 27, 2017 9:45 AM
To: denghui (L) <denghu...@huawei.com<mailto:denghu...@huawei.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: RE: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on 
Wednesday

Hi,

I don't see how we the critical mass to do this. If you want the feedback to be 
heard, you need to include the people who are working on the VNF models, 
including those who are leading the work - Chris, Andy, others. Chris is on 
stage presenting. Andy is asleep...

My two cents,

Alex

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Wednesday, September 27, 2017 12:32 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

Hello all

We haven't finished yesterday session, let's continue 10:30-11:30 this morning 
in the meeting room (Algebre), 2nd floor.
Agenda would be :

1)  SDC feedback to VNF modeling

2)  VFC feedback to VNF modeling

3)  Summary of VNF Modeling

4)  OSM modeling comparison

Apologies to US remote attendees, we couldn't conflict with TSC meeting in the 
afternoon.

Thanks a lot for your attending
Best regards,

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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

[denghui (L)]

Alex,

we have already heard yesterday feedback from Chris Donley Andy, VNFSDK & 
Architecture, ,
and now we need to move on and would expect more from the implementers side.

Thanks

DENG Hui

From: Vul, Alex [mailto:alex@intel.com]
Sent: Wednesday, September 27, 2017 9:45 AM
To: denghui (L) <denghu...@huawei.com>; onap-discuss@lists.onap.org; onap-tsc 
<onap-...@lists.onap.org>
Subject: RE: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on 
Wednesday

Hi,

I don't see how we the critical mass to do this. If you want the feedback to be 
heard, you need to include the people who are working on the VNF models, 
including those who are leading the work - Chris, Andy, others. Chris is on 
stage presenting. Andy is asleep...

My two cents,

Alex

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: Wednesday, September 27, 2017 12:32 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: [onap-discuss] [Modeling] Modeling subcommittee F2F Cont. on Wednesday

Hello all

We haven't finished yesterday session, let's continue 10:30-11:30 this morning 
in the meeting room (Algebre), 2nd floor.
Agenda would be :

1)  SDC feedback to VNF modeling

2)  VFC feedback to VNF modeling

3)  Summary of VNF Modeling

4)  OSM modeling comparison

Apologies to US remote attendees, we couldn't conflict with TSC meeting in the 
afternoon.

Thanks a lot for your attending
Best regards,

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

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[denghui (L)]

Gildas,


6. 
modeling/toscaparsers/nfvparser
These codes are all based on python, do they still need SONAR work?

Thanks a  lot

DENG Hui

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Wednesday, September 20, 2017 6:53 AM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention


Thanks Jess for the effort. Let's continue our journey. I found other entries 
that requires work.



1. Common Logging Library. 
Looks like this is related to commit for aai/logging-service at 
https://gerrit.onap.org/r/#/c/11289/ Not sure why this is still in Sonar. The 
Daily Jenkins Jobs has passed 
https://jenkins.onap.org/view/aai/job/aai-logging-service-master-release-version-java-daily/
 Ideas?

All the entries below are not correct and required your help.

2. Distribution

3. DMaaP Bus Controller UI 
(parent)

4. Ecomp Portal SDK Project 
(parent)

5. ECOMP Portal SDK Project 
(parent)

6. 
modeling/toscaparsers/nfvparser

7. inventory-api should 
be under dcaegen2/platform

8. MSO main project 
should be removed

9. OpenStack Java SDK

10. Parent POMs

11. SDN-C Adaptors

12. SDN-C Core Components

13. SDN-C Core Components - 
rootpom

14. SDN-C Java Plugins

15. SDN-C Northbound APIs

16. SDN-C OAM

17. VID Parent Project



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287





-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Tuesday, September 19, 2017 2:45 PM
To: Gildas Lanilis >
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention



Dear Gildas,



Here are more updates from my side:

- Removed "blueprints"

- Demo-aggregator removed, template to use no-sonar needs merge in gerrit: 
http://gerrit.onap.org/r/13601

- "model-loader" belongs to aai-model-loader. This was pre-onap rename when we 
were using openecomp. Removed it.

- "ncomp" removed

- "ONAP Operations Manager" removed

- "oparent" removed, template to use no-sonar needs merge in gerrit: 
http://gerrit.onap.org/r/13603

- Will try to reply soon to these 2 broken jobs since the tech teams have not 
reported them, but I contact them with what I see they have wrong in their pom 
files:

  - 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-distribution-master-release-version-java-daily/

  - 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-parent-master-release-version-java-daily/

- "dcae" removed

- "Portal (parent)" removed

- Items in your #7 are part of the items that I thought I fix but they are not 
updating. I have a possible cause and was able to fix 1 of them, will upload 
the same fix for the rest.





Thanks!

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

Re: [onap-discuss] [onap-tsc] Please Pick The Sessions You Want To Attend in Paris

[denghui (L)]

Hi Kenny,

How could people add theirs name?

1)  Leader will under each topic create a new "Interested: " to let people 
input their name

2)  at the bottom of page to add name and interested topics list?

Thanks a lot for your instruction
Best regards,

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Tuesday, September 12, 2017 5:06 PM
To: onap-discuss@lists.onap.org; onap-tsc 
Subject: [onap-tsc] Please Pick The Sessions You Want To Attend in Paris

Please remember to go to the Topics page and start adding your name to the 
specific topics you would be primarily interested in.  We will use the level of 
interest in a particular topic to help us with scheduling and setting the 
agenda for Paris.

https://wiki.onap.org/display/DW/September+26-28+Topics

Thanks!

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

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

Re: [onap-discuss] [SDC][VNFSDK][VFC]Some questions on CSAR structure

[denghui (L)]

Hi David

I haven’t see those questions been answered, they would like to understand 
what’s is mandatory or optional for import and output CSAR package according to 
: https://wiki.onap.org/display/DW/Csar+Structure

Thanks a lot for your kind help
Best regards,

DENG Hui

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaoweitao (Victor, 
MANO)
Sent: Tuesday, September 05, 2017 10:34 PM
To: LANDO, MICHAEL; SHADMI, DAVID
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] [SDC][VNFSDK][VFC]Some questions on CSAR structure

Hi Michael, David,

I saw the link on the wiki about the CSAR package for SDC 
input/output: https://wiki.onap.org/display/DW/Csar+Structure
As we discussed in Last Friday, I have couple of questions here:

1.   We agree have a vendor-specific zip file under Artifacts folder and 
should the wiki page update for support this?

2.   I don't see the requirement of “Informational” and “Deployment” folder 
on the meeting. Does SDC have some special requirement /restriction on this or 
these folders will added during SDC onboard VNF CSAR package?

3.   What’s the difference between “VF-C TOSCA NAME”‘s “Informational” and 
“Deployment” folders and ROOT’s “Informational” and “Deployment” folder? Could 
these folders be optional?

4.   By the way, could you help us clarify usage of Metadata and Manifest 
in SDC? Cause I think we already got the consensus on choosing Option1(with 
metadata as R1 selection), I think manifest is duplicate functionality (find 
the entry point for VNF main service template) with metadata in R1.

In my understanding, last Friday we got the consensus is like this as VNF CSAR 
for SDC input:

[cid:image004.png@01D326F1.AECE0EF0]






















Please correct me if any mistake or misunderstanding.
BR
Victor

*
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使
用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通
知发件人并删除本邮件！
*

*
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person
or entity whose address is listed above. Any use of the information contained 
herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s)
is prohibited. If you receive this e-mail in error, please notify the sender by 
phone or email immediately and delete it!
*



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

Re: [onap-discuss] How to commit the files about WAN modeling?

[denghui (L)]

Hi, Zhuoyao

For modeling code, have you decided together with David about whether to build 
WAN resrouce in SDC based on VF or VL? You could upload to SDC to check whether 
their committers agree or not.

For modeling spec, once it is finalized in modeling committee, it will be kept 
in the repo of modeling project.

Thanks

DENG Hui

From: huang.zhuo...@zte.com.cn [mailto:huang.zhuo...@zte.com.cn]
Sent: Wednesday, August 23, 2017 9:55 AM
To: denghui (L) <denghu...@huawei.com>; ml6...@intl.att.com
Cc: Patrick Liu <patrick@huawei.com>; yuan@zte.com.cn; 
meng.zhaoxi...@zte.com.cn; zhang.maope...@zte.com.cn; 
denglin...@chinamobile.com; onap-discuss@lists.onap.org
Subject: How to commit the files about WAN modeling?


Hi, DengHui and Michael

Would you please help me about this issue? I don't know how to commit 
the files about WAN modeling. Should I push them to SDC gerrit, or modeling 
gerrit, or somewhere else?

Thank you very much!











黄卓垚huangzhuoyao



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


[cid:image001.gif@01D31C20.E8F15E60]

[cid:image002.gif@01D31C20.E8F15E60]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R 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<http://www.zte.com.cn/>


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

[onap-discuss] [modeling][sdc][so][vfc][vnfsdk]ONAP naming convention options

[denghui (L)]

Hello all

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

Thank you all for your comments.

Best regards,

DENG Hui

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

[onap-discuss] [modeling][sdc][vfc][so][vnfsdk][sdnc][uui] Agenda of modeling project/subcommittee for tomorrow teleconf

[denghui (L)]

Hello all

This Thursday is the deadline for freezing of API, normally it means freezing 
of modeling spec for R1. We can't always delay until the deadline for code 
freezing :)
even tomorrow was planned for modeling project, we will borrow most time from 
modeling project to discuss the status of interface and modeling spec, to check 
whether we need additional call in this week.


1)  Modeling project, (only 1 tosca parser is on the repo for VFC, UUI 
hasn't confirmed yet)



2)  Check the status of interface and modeling spec

Interfaces

a)   VNFSDK-SDC

b)   SDC-SO

c)SDC-VFC

d)   SO-VFC

e)   SO-SDNC
Modeling specs
1.a) VNFD (skip for R1?)
1.b) SD
1.c) NSD
1.d) WAN spec
1.e) vnf package (skip for R1)



3)  ONAP modeling namespace

Thanks a lot

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

[onap-discuss] Modeling subcommittee minutes and slide

[denghui (L)]

Hello Halfon, zhuoyao, chuanyu

Could you kindly help to upload your slide yesterday to the meeting minutes 
wiki page for modeling committee?
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

Thanks a lot for your help

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