[onap-tsc] FW: Step down from MultiCloud project

[Yang, Bin via lists.onap.org]

Re-send it, since it was rejected due to my subscription status to this mail 
list.

From: Yang, Bin
Sent: 2023年4月21日 9:58
To: onap-tsc@lists.onap.org
Cc: onap-...@lists.onap.org; Mudiganti, Seshu Kumar 
; Hellmann, Gil 
; Gao, Litao ; HUANG, 
HAIBIN (haibin.hu...@intel.com) 
Subject: Step down from MultiCloud project

Dear ONAP TSC,

Due to my changes of Role and Responsibility in Wind River, I would like to 
update you that I am stepping down from the PTL position of ONAP MultiCloud 
Project. And I am happy to support anyone who is willing to step in to lead 
this project forward.

It has been a tremendous and amazing journey with ONAP community and I am very 
proud that I had the chance to contribute to its success, I wish you will 
continue to achieve more accomplishment and make the open source world even 
more better.

Thank you so much!

B.R.
Bin



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

Re: [onap-tsc] Cancel the TSC Meeting this week?

[Yang Bin]

+1 for canceling it

From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul
Sent: 2022年4月12日 8:46
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Cancel the TSC Meeting this week?

[Please note: This e-mail is from an EXTERNAL e-mail address]
Hi TSC,

As you know this week is ONEEF, starting tomorrow.   The three days have 
different start times to accommodate NAR, APAC and EMEA respectively.
https://events.linuxfoundation.org/open-networking-and-edge-exec-forum/

Thursday’s event overlaps with the TSC call with a number of topics such as 
SDOs which I know are of interest to many in the TSC leadership.
So even though this is not a developer centric event, would it make sense to 
cancel this week’s TSC call?

Thoughts?

Thanks!
-kenny




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

[onap-tsc] Proxy for this week

[Yang Bin]

Dear TSC,

I will have a conflict meeting on this Thursday’s TSC call, Jackie on cc list 
will join the call as my proxy, thanks.

B.R.
Bin



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

[onap-tsc] [Onap-arc] RE: ONAP Architecture Review Request for MultiCloud

[Yang Bin]

Resend this with tagged subject.

From: onap-tsc@lists.onap.org  On Behalf Of Yang Bin
Sent: 2021年11月29日 11:19
To: onap-tsc@lists.onap.org; onap-...@lists.onap.org
Subject: [onap-tsc] ONAP Architecture Review Request for MultiCloud

Dear Arch. Subcommittee,

Though there will be no architectural changing for MultiCloud in Jakarta 
release, I would like to request your help to evaluate if still need an 
architecture review for MultiCloud in Jakarta release,  please help create jira 
ticket and propose date for this review if needed?

Thanks.

B.R.
Bin




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

[onap-tsc] ONAP Architecture Review Request for MultiCloud

[Yang Bin]

Dear Arch. Subcommittee,

Though there will be no architectural changing for MultiCloud in Jakarta 
release, I would like to request your help to evaluate if still need an 
architecture review for MultiCloud in Jakarta release,  please help create jira 
ticket and propose date for this review if needed?

Thanks.

B.R.
Bin



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

Re: [onap-tsc] ONAP TSC SELF-NOMINATIONS OPEN - Ends Sept 21, 2021

[Yang Bin]

Dear ONAP Community,

I would like to nominate myself as a TSC member of the ONAP community 
representing Wind River.

I have been participating ONAP since its inception and engaged in various 
community activities. I have been contributed to the success of ONAP Releases 
with the contributions to Multi-VIM/Cloud project development, Pair-wise 
testing, Integration Testing, Wind River/Intel Integration Lab supporting, CMCC 
and China Telecom Open Lab supporting. I have been developing demos with ONAP 
and showcasing them during various events including ONS, MWC. with these 
experience, I identified generic functional requirement referred as Centralized 
representation and consist ID of cloud regions which has been one of ONAP 
functional requirements in Casablanca and Dublin Releases. I also shared my 
experiences and best practices of using ONAP through ONAP wiki, email list, and 
hotline meetings.

If I have the honor to serve as ONAP TSC Member again, I will contribute to the 
collaboration and alignment between ONAP and O-RAN from O2 interfaces 
perspective.

Thanks for your support.

Best regards,

Bin Yang


From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul
Sent: 2021年9月7日 23:11
To: 'onap-tsc' 
Subject: [onap-tsc] ONAP TSC SELF-NOMINATIONS OPEN - Ends Sept 21, 2021

[Please note: This e-mail is from an EXTERNAL e-mail address]
Dear ONAP Community,
If you are interested in running for a seat on the TSC, please read all of this 
information carefully
Nominations for seats on the ONAP TSC are officially open. Up to 25 seats on 
the TSC are now available.
Who is eligible to Run:

  *   Any Active Community 
Members
 as measured at 14:00 UTC, Tuesday, September 7, 2021.   The ONAP Technical 
Community 
Documents
 defines an Active Community Member as anyone from the ONAP community with 
twenty (20) or more measurable contributions during the previous 12-month 
period, inclusive of code merged, code reviews performed, wiki page edits, 
(creation, modification, comments or attachments) or JIRA activities (creation, 
modification, comment or closure).
  *   There are no restrictions to the number of people from a company or group 
of companies that may run for an available seat.
Self-Nomination Phase

  *   Interested individuals MUST REPLY-ALL TO THIS ORIGINAL EMAIL with your 
intention to run no later than 23:59 UTC, September 21, 2021
  *   It is recommended that candidates include a small head-shot, a short 
biography and statement of intent on why you would be a good person to hold a 
seat on the TSC.
  *   Please also fill in the 2021 TSC Election Candidates wiki 
page
 with that same information.
Election Phase

  *   Any Active Community Members as of 14:00 UTC, Tuesday, September 7, 2021 
is eligible to vote.
  *   A Condorcet election will be held using the OpaVote 
system
 (due to recent changes to CIVS). The election shall consist of a single stack 
ranked vote of all candidates.
  *   Active Community Members will receive an invitation to vote from OpaVote.
  *   The election phase will begin with the distribution of the poll via email 
from the application
  *   The election phase will end two (2) weeks later in the same time zone the 
poll was initiated from
  *   Only the top ranked candidates from any single company or group of 
related companies will be elected; if the top 5 vote getters are all from the 
same company, only the person with the highest number of votes out of all 5 
will be elected from that company.
  *   The LF will update the Voting Results 
History
  page with their name, date, and link to the publicly viewable results and 
send an email to the onap-tsc distribution list.

Thanks!
-kenny




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

[onap-tsc] [ONAP] [MultiCloud] Committer changes

[Yang Bin]

Dear TSC

There are some changes regarding the committers of MultiCloud project:

Yue Liexiang has stepped down from committer role, I appreciate his great 
contribution to MultiCloud project.

Konrad Banka from Samsung has been voted as new committer, please refer to 
https://civs1.civs.us/cgi-bin/results.pl?id=E_2a4ec0d21e9e20a3 for vote result.

I would like to request your approval to the vote result, the request is put on 
wiki: https://wiki.onap.org/pages/viewpage.action?pageId=103420246

thanks.

B.R.
Bin

MultiCloud PTL




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

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

[Yang Bin]

Hi Huabing,

 Thanks for your great contribution and help!  Best wishes to your 
future endeavors!

B.R.
Bin

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

[Please note this e-mail is from an EXTERNAL e-mail address]
Dear TSC and all,

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

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

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

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

Regards,
Huabing Zhao



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

[onap-tsc] Cancel MultiCloud Weekly meeting on August 26

[Yang Bin]

Dear team,

   Due to PTO, I would like to cancel our weekly meeting tonight, 
please drop me message if you have any urgent issue to discuss.

Thanks.
B.R.
Bin

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

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

Re: [onap-tsc] Architecture Reviews tracking spreadsheet

[Yang Bin]

Hi Chaker,

   I just update the architecture page : 
https://wiki.onap.org/pages/viewpage.action?pageId=84642252 , could you help 
arrange a time slot to review it over next weekly meeting ?

Thanks
B.R.
Bin

From: Yang, Bin
Sent: Thursday, February 13, 2020 9:11 PM
To: Chaker Al-Hakim ; Jimmy Forsyth via 
Lists.Onap.Org ; Mandar Sawant via 
Lists.Onap.Org ; matthieu.geereba...@orange.com; 
bhara...@research.att.com; TALASILA, MANOOP ; 
Sonsino, Ofir ; Ittay ; 
Gaoweitao (Victor, Cloudify Network OSDT) ; 
steven.st...@att.com
Cc: onap-...@lists.onap.org; onap-tsc@lists.onap.org
Subject: RE: Architecture Reviews tracking spreadsheet

Hi Chaker,

   Though MultiCloud has no architectural changes in F release, I 
would like to go through the review process as well, could you put agenda for  
that in next Arch subcom weekly meeting?

Thanks

From: Chaker Al-Hakim 
mailto:chaker.al.ha...@futurewei.com>>
Sent: Monday, February 10, 2020 11:43 AM
To: Jimmy Forsyth via Lists.Onap.Org 
mailto:jf2512=att@lists.onap.org>>; Mandar 
Sawant via Lists.Onap.Org 
mailto:ms5838=att@lists.onap.org>>; 
matthieu.geereba...@orange.com<mailto:matthieu.geereba...@orange.com>; 
bhara...@research.att.com<mailto:bhara...@research.att.com>; Yang, Bin 
mailto:bin.y...@windriver.com>>; TALASILA, MANOOP 
mailto:talas...@research.att.com>>; Sonsino, Ofir 
mailto:ofir.sons...@intl.att.com>>; Ittay 
mailto:ittay.st...@att.com>>; Gaoweitao (Victor, Cloudify 
Network OSDT) mailto:victor@huawei.com>>; 
steven.st...@att.com<mailto:steven.st...@att.com>
Cc: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Architecture Reviews tracking spreadsheet

Dear PTL's,

This is to update you on the status of the Architecture reviews of all the ONAP 
components that are participating in the Frankfurt Release based on the M1 list 
of Projects that was approved by the TCS on Nov. 14, 2019
The attached tracking spreadsheet reflects the status of all the projects that 
have been reviewed and approved by the ArchCom. The spreadsheet also shows the 
projects that are part of the release and have yet to either present the 
Component changes/Architecture Changes or officially documented that their 
changes don't have any impact on the component/Platform architecture.

Please review the spreadsheet and update the corresponding Jira to document the 
reasons your component does not require an Architecture review. This will serve 
as an official paper trail that can be referenced in the future.
Should there be another Jira that is related to the same topic just add a 
reference to it in the ArchCom jira listed in the spreadsheet.

Regards,
Chaker

This e-mail and any attachments may contain confidential information from 
Futurewei/Huawei, which are intended only for the person or entity whose email 
address appears above. Any use of the information attached or contained herein 
in any way (including, but not limited to, total or partial disclosure, 
reproduction, or any unapproved dissemination) by persons other than the 
intended recipient(s) is prohibited. If you have received this e-mail in error, 
please notify the sender by phone or response email immediately and delete this 
original message.



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

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

Re: [onap-tsc] MultiCloud lifecycle review request

[Yang Bin]

Dear TSC,

I updated the maturity review wiki page as suggested, please help review it.

https://wiki.onap.org/display/DW/Project+Maturity+Review+for+MultiCloud

Thanks

From: Yang, Bin
Sent: Monday, July 6, 2020 6:17 PM
To: onap-tsc@lists.onap.org
Subject: MultiCloud lifecycle review request

Dear TSC,

I'd like to ask for a lifecycle review for MultiCloud project.
Please find the relevant wiki page here:  
https://wiki.onap.org/display/DW/Project+Maturity+Review+for+MultiCloud,

Thanks,
B.R.
Bin


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

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

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

[Yang Bin]

Dear TSC,

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

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

Thanks,

B.R.
Bin

From: Yang, Bin
Sent: Tuesday, July 21, 2020 10:26 AM
To: 'Sood, Ritu' ; Zhang, Xiaohua 
; 'Huang, Haibin' ; 
'Xinhui Li' ; '岳烈骧 (yueliexi...@chinamobile.com)' 
; 'Multanen, Eric W' 
Subject: Result of MultiCloud PTL election in 2020

Dear committers,

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

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

B.R.
Bin

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

Dear guys,

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

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

B.R.
Bin

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

Dear committers,

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

Thanks,
B.R.
Bin


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

Dear Multi-VIM/Cloud committers,

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

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

B.R.
Bin Yang



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

Dear Committers of MultiCloud project,

Please nominate yourself for the PTL role of the MultiCloud project if you are 
interested.

The nomination window will be open till 6:00pm Beijing Time, July 13th, 2020

Than

[onap-tsc] self-nomination for MultiCloud PTL, RE: MultiCloud PTL election in 2020

[Yang Bin]

Dear Multi-VIM/Cloud committers,

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

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

B.R.
Bin Yang



From: onap-disc...@lists.onap.org  On Behalf Of 
Yang Bin
Sent: Monday, July 6, 2020 6:36 PM
To: onap-tsc@lists.onap.org; onap-disc...@lists.onap.org
Cc: Sood, Ritu ; Zhang, Xiaohua 
; Huang, Haibin ; Xinhui 
Li ; 岳烈骧 (yueliexi...@chinamobile.com) 
; Multanen, Eric W ; 
Yang, Bin 
Subject: [onap-discuss] MultiCloud PTL election in 2020

Dear Committers of MultiCloud project,

Please nominate yourself for the PTL role of the MultiCloud project if you are 
interested.

The nomination window will be open till 6:00pm Beijing Time, July 13th, 2020

Thanks.

B.R.
Bin


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

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

[onap-tsc] MultiCloud PTL election in 2020

[Yang Bin]

Dear Committers of MultiCloud project,

Please nominate yourself for the PTL role of the MultiCloud project if you are 
interested.

The nomination window will be open till 6:00pm Beijing Time, July 13th, 2020

Thanks.

B.R.
Bin

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

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

[onap-tsc] MultiCloud lifecycle review request

[Yang Bin]

Dear TSC,

I'd like to ask for a lifecycle review for MultiCloud project.
Please find the relevant wiki page here:  
https://wiki.onap.org/display/DW/Project+Maturity+Review+for+MultiCloud,

Thanks,
B.R.
Bin


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

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

Re: [onap-tsc] Committer Promotion Request for MultiCloud

[Yang Bin]

Dear TSC,

Please kindly process this committer promotion request for MultiCloud project.

Thanks

From: onap-tsc@lists.onap.org  On Behalf Of Yang Bin
Sent: Thursday, June 18, 2020 11:32 AM
To: onap-tsc@lists.onap.org
Cc: onap-disc...@lists.onap.org
Subject: [onap-tsc] Committer Promotion Request for MultiCloud

Dear ONAP TSC,

MultiCloud project had renewed the status of committers commitments, and 
confirmed that the following committers resigned from committer roles: @Ethan 
Lynn<mailto:ethanly...@vmware.com> 
@zhanganb...@chinamobile.com<mailto:zhanganb...@chinamobile.com> @Sudhakar 
Reddy<mailto:sudhakar.re...@amdocs.com>, @Kamineni, Kiran 
K<mailto:kiran.k.kamin...@intel.com>, I appreciate their great contributions in 
past releases and look forward to their kindly help in future.


Then existing committers nominated and voted for Eric Multanen as a new 
committer of MultiCloud project, the detail can be found at following wiki page:
https://wiki.onap.org/pages/viewpage.action?pageId=84653845

Please kindly approve this promotion.

Thanks


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

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

[onap-tsc] Committer Promotion Request for MultiCloud

[Yang Bin]

Dear ONAP TSC,

MultiCloud project had renewed the status of committers commitments, and 
confirmed that the following committers resigned from committer roles: @Ethan 
Lynn 
@zhanganb...@chinamobile.com @Sudhakar 
Reddy, @Kamineni, Kiran 
K, I appreciate their great contributions in 
past releases and look forward to their kindly help in future.


Then existing committers nominated and voted for Eric Multanen as a new 
committer of MultiCloud project, the detail can be found at following wiki page:
https://wiki.onap.org/pages/viewpage.action?pageId=84653845

Please kindly approve this promotion.

Thanks
_._,_._,_

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

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

Re: [onap-tsc-vote] [onap-tsc] ONAP Intern Project Review

[Yang Bin]

+1 both

获取 Outlook for Android


发件人: onap-tsc-v...@lists.onap.org  代表 Kenny Paul 

发送时间: 2020年3月14日星期六 上午3:21
收件人: onap-tsc-v...@lists.onap.org
抄送: onap-tsc@lists.onap.org
主题: Re: [onap-tsc-vote] [onap-tsc] ONAP Intern Project Review

(bcc’d to onap-tsc for visibility)

Dear TSC Members,
These two intern projects were approved by the TSC yesterday:

  *   ETSI NFV APIs conformance test for OVP 
https://wiki.lfnetworking.org/x/DwH_AQ
  *   Modeling/etsicatalog  https://wiki.lfnetworking.org/x/CQH_AQ
 *   Approved with the provisions:  change spec from 2.5.1 to 2.7.1 and add 
“Alignment with the CNF task force where applicable”   (I’ve made the required 
changes to the proposal)

The following two projects were reviewed by the TSC during the meeting, edited 
and are now up for approval - Voting ends 5pm pacific, March 17th

  *   ONAP Automation Testing - Portal/SDC 
https://wiki.lfnetworking.org/x/uwAQAg
  *   ONAP Security Requirements �C SDC https://wiki.lfnetworking.org/x/uQAQAg

#VOTE Does the TSC approve the “ONAP Automation Testing - Portal/SDC” and the 
“ONAP Security Requirements �C SDC” projects to be part of the 2020 Mentorship 
Program?
Please respond with:
   +1  “Both”or +1 by project name
0“Both”or  0 by project name
-1  “Both”or -1  by project name


From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul 
via Lists.Onap.Org
Sent: Tuesday, March 10, 2020 6:02 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ONAP Intern Project Review

Hi TSC Members,

There have been 2 project proposals submitted by ONAP for the 2020 Mentorship 
Program.

In addition I have just been made aware of 2 additional intern projects that 
are desired which will be submitted tonight my time.
The good news is that after conferring with the Mentorship Program Manager, we 
should still be able to get all 4 ONAP projects funded, ---PROVIDED---  that 
the ONAP TSC reviews and approves all of them no later than 5pm pacific, March 
17th.

Of critical importance here is that the scope for all of our intern projects is 
clear and concise.

  *   If projects are too broad or vaguely defined, a perspective intern is 
unlikely to understand what the project is about, which will deter students 
from applying.
  *   If the proposal is overly optimistic about what an intern can effectively 
achieve in a short couple of months, it sets unrealistic expectations for them 
during the application phase.

The net results of either of those scenarios is a “fail” on the part of the TSC 
as it relates to the Mentorship Program that could adversely impact both our 
funding and participation in the program the following year.  We need to make 
sure that y’all are clear about these and in agreement on the expectations.

I am adding a proposal review to this week’s TSC call, but knowing that we 
still have a lot of M4 work we may not got to reviewing them.
PLEASE take a look at the  two proposals listed above (which have been posted 
for a couple of weeks now) and note any concerns as comments on the respective 
page, either in-line or at the bottom.

Thanks!
-kenny




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

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

Re: [onap-tsc] Vote by TSC on proposed exception process

[Yang Bin]

+1

From: onap-tsc@lists.onap.org  On Behalf Of David 
McBride
Sent: Thursday, February 20, 2020 4:13 AM
To: onap-tsc 
Subject: [onap-tsc] Vote by TSC on proposed exception process

Team,

Just a reminder that the TSC will be voting on the proposed exception process 
on Thursday, Feb 19.

If you have not yet reviewed the process, please take a few minutes to examine 
the following links:

  *   Form
  *   Process
Let me know if you have any questions.

David

--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
IRC: dmcbride


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

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

Re: [onap-tsc] Architecture Reviews tracking spreadsheet

[Yang Bin]

Hi Chaker,

   Though MultiCloud has no architectural changes in F release, I 
would like to go through the review process as well, could you put agenda for  
that in next Arch subcom weekly meeting?

Thanks

From: Chaker Al-Hakim 
Sent: Monday, February 10, 2020 11:43 AM
To: Jimmy Forsyth via Lists.Onap.Org ; Mandar 
Sawant via Lists.Onap.Org ; 
matthieu.geereba...@orange.com; bhara...@research.att.com; Yang, Bin 
; TALASILA, MANOOP ; 
Sonsino, Ofir ; Ittay ; 
Gaoweitao (Victor, Cloudify Network OSDT) ; 
steven.st...@att.com
Cc: onap-...@lists.onap.org; onap-tsc@lists.onap.org
Subject: Architecture Reviews tracking spreadsheet

Dear PTL's,

This is to update you on the status of the Architecture reviews of all the ONAP 
components that are participating in the Frankfurt Release based on the M1 list 
of Projects that was approved by the TCS on Nov. 14, 2019
The attached tracking spreadsheet reflects the status of all the projects that 
have been reviewed and approved by the ArchCom. The spreadsheet also shows the 
projects that are part of the release and have yet to either present the 
Component changes/Architecture Changes or officially documented that their 
changes don't have any impact on the component/Platform architecture.

Please review the spreadsheet and update the corresponding Jira to document the 
reasons your component does not require an Architecture review. This will serve 
as an official paper trail that can be referenced in the future.
Should there be another Jira that is related to the same topic just add a 
reference to it in the ArchCom jira listed in the spreadsheet.

Regards,
Chaker

This e-mail and any attachments may contain confidential information from 
Futurewei/Huawei, which are intended only for the person or entity whose email 
address appears above. Any use of the information attached or contained herein 
in any way (including, but not limited to, total or partial disclosure, 
reproduction, or any unapproved dissemination) by persons other than the 
intended recipient(s) is prohibited. If you have received this e-mail in error, 
please notify the sender by phone or response email immediately and delete this 
original message.



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

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

Re: [onap-tsc] ONAP TSC Chair Nominations 2019

[Yang Bin]

Congratulations @Catherine

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Saturday, December 07, 2019 4:43 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] ONAP TSC Chair Nominations 2019

Congratulations to Catherine on being reelected as our ONAP TSC Chair!
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4356f527d488649e
I will be setting up the Vice-Chair elections shortly.

-kenny

From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul 
via Lists.Onap.Org
Sent: Monday, December 2, 2019 12:29 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] ONAP TSC Chair Nominations 2019

There is only one candidate for the ONAP TSC Chair election: Catherine LeFevre 
(AT&T).

Ballots have been distributed to TSC members.  Voting ends 12:30 pacific 
Friday, Dec. 6

Thanks!
-kenny


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

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

Re: [onap-tsc] Milestone Exception Process Timing Vote - Ends Wed., Nov 20 @ noon Pacific

[Yang Bin]

+1

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Friday, November 15, 2019 3:30 AM
To: onap-tsc-v...@lists.onap.org
Subject: [onap-tsc] Milestone Exception Process Timing Vote - Ends Wed., Nov 20 
@ noon Pacific

(bcc' to onap-tsc for visibility)

As evidenced by today's call the Milestone Exception Process ( 
https://lists.onap.org/g/onap-tsc-vote/topic/40467217#1262 ) approved by the 
TSC last week (https://lists.onap.org/g/onap-tsc/message/5592) is certainly 
needed. My recommendation to the TSC when the process was approved was to make 
it effective beginning with Frankfurt M2. I didn't see any follow-ups to that 
suggestion, so I am initiating a vote:

VOTE: Does the TSC approve implementing the Milestone Exception Process 
beginning with Frankfurt M2?
+1, 0, -1

Thanks!
-kenny



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

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

Re: [onap-tsc] image_compare.20190909.R1.xlsx

[Yang Bin]

Hi Jim,

Below is the updated releases for multicloud. Thanks


multicloud

onap/multicloud/framework

1.4.0

8/13/2019

NO

1.41 in repo

multicloud/charts/multicloud-azure

onap/multicloud/azure

1.2.4

5/30/2019

YES

multicloud/charts/multicloud-fcaps

onap/multicloud/openstack-fcaps

1.3.4

5/28/2019

No

1.4.1

multicloud/charts/multicloud-k8s

onap/multicloud/k8s

0.4.0

5/30/2019

No

0.5.0

multicloud/charts/multicloud-lenovo

onap/multicloud/openstack-lenovo

1.3.4

5/28/2019

Yes

De-scoped

multicloud/charts/multicloud-pike

onap/multicloud/openstack-pike

1.3.4

5/28/2019

No

1.4.1

multicloud/charts/multicloud-starlingx

onap/multicloud/openstack-starlingx

1.3.4

5/28/2019

No

1.4.1

multicloud/charts/multicloud-vio

onap/multicloud/vio

1.3.1

4/29/2019

No

1.4.1

multicloud/charts/multicloud-windriver

onap/multicloud/openstack-windriver

1.3.4

5/28/2019

No

1.4.1



Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Prudence Au
Sent: Friday, September 13, 2019 10:07 PM
To: onap-tsc
Subject: Re: [onap-tsc] image_compare.20190909.R1.xlsx

Hi Jim,

Here are the updated images for POMBA:
pomba/charts/pomba-aaictxbuilder

onap/pomba-aai-context-builder

1.4.0

2019-04-06

YES

1.5.1

pomba/charts/pomba-contextaggregator

onap/pomba-context-aggregator

1.4.0

2019-04-06

YES

1.5.1

pomba/charts/pomba-data-router

onap/data-router

1.3.3

2019-01-24

NO

pomba/charts/pomba-elasticsearch

elasticsearch/elasticsearch

6.6.2

No

pomba/charts/pomba-kibana

kibana/kibana

6.6.2

No

pomba/charts/pomba-networkdiscovery

onap/network-discovery

1.5.1

2019-05-01

No

pomba/charts/pomba-networkdiscoveryctxbuilder

onap/pomba-network-discovery-context-builder

1.4.0

2019-04-06

YES

1.5.1

pomba/charts/pomba-sdcctxbuilder

onap/pomba-sdc-context-builder

1.4.0

2019-04-06

YES

1.5.1

pomba/charts/pomba-sdncctxbuilder

onap/pomba-sdnc-context-builder

1.4.0

2019-04-06

YES

1.5.1

pomba/charts/pomba-search-data

onap/search-data-service

1.3.1

2018-10-10

No

pomba/charts/pomba-servicedecomposition

onap/service-decomposition

1.5.1

2019-05-01

No

pomba/charts/pomba-validation-service

onap/validation

1.3.1

2018-11-15

No

Thanks,
Prudence



From: onap-tsc@lists.onap.org  on behalf of Jim Baker 

Sent: September 9, 2019 7:02 PM
To: onap-tsc 
Subject: [onap-tsc] image_compare.20190909.R1.xlsx

Attention PTLs:
Please review the attached spreadsheet for your El Alto deliveries. If you have 
any updates, please let me know.
Jim

-- Forwarded message -
From: FREEMAN, BRIAN D mailto:bf1...@att.com>>
Date: Mon, Sep 9, 2019 at 10:15 AM
Subject: image_compare.20190909.R1.xlsx
To: Jim Baker mailto:jba...@linuxfoundation.org>>, 
morgan.richo...@orange.com 
mailto:morgan.richo...@orange.com>>
Cc: LEFEVRE, CATHERINE 
mailto:catherine.lefe...@intl.att.com>>


Use the Script tab.



This data is from oom:master on 9.9.2019 and nexus3 query to the release 
repository to check for Last-Modified date (which should be the same as Release 
date)



If there is a blank it means the nexus3 query failed - likely due to it not 
being resident on nexus3.



Its a new script so there may be missing images but I think it is generally 
accurate.



Could we send to ptl's for update that were not provided on the call.



I will re-run this for next weeks PTL call..



Brian




--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007
This email and the information contained herein is proprietary and confidential 
and subject to the Amdocs Email Terms of Service, which you may review at 
https://www.amdocs.com/about/email-terms-of-service


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

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

[onap-tsc] Brief on multicloud-azure security issue

[Yang Bin]

Dear TSC,

As requested during last TSC call, I would like to brief the security 
vulnerability issue of multicloud-azure component.

Background:
Given the ONAP architecture, multicloud services are all internal services 
which are typically utilized by other ONAP components (SO, OOF, VFC, APPC).  
multicloud-azure component is a plugin service in multicloud which mediate 
azure cloud to ONAP. It is deployed on demand and runs as a standalone service 
as well.
This plugin service has been introduced since Beijing release, and gone through 
Casablanca and Dublin Releases (with sonar coverage waiver). Now there are 
security issues to be scrutinized (and resolved if applicable) , but we are 
lacking of resource to commit to help on that.

Reported security issues:

Multicloud-azure is based on python 2 and Django framework and utilize several 
python packages. The following packages are reported with security issue:
Django 1.9.6
azure-common 1.1.14
djangorestframework 3.3.3
httplib2 0.9.2
requests 2.14.0

However, that does not imply the multicloud-azure component are impacted since 
there are chances that multicloud-azure does not utilize the API/Fucntionality 
of those package which result in security issue. Hence we need further 
investigation to multicloud-azure source code to figure out whether or not the 
reported security issue are false positive here.

I believe the clm report are confidential due to some policy, hence not public 
available to community, but the detail of those reported security issue are 
public available , so I copied the links and share them with our team member as 
below. Hopefully someone would like to help if not too overwhelming.

For those having the permission to view the report, here is the link:
https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/applicationReport/onap-multicloud-azure/1dbdc9b12f3f4f21b0d8f1b92f919e57/policy

The repo is : https://gerrit.onap.org/r/admin/repos/multicloud/azure
The released docker images: onap/multicloud/azure

Thanks

Public links to the reported security issue:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9013
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14234
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18074
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20060
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9014
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7401
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14232
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14233
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14235
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6975
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6186
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12794
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7233
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7234
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14574
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3498
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14042
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8331
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14042
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11236
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9740
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7536
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7537
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12781

There are bunch of sonartype issues which I cannot find out the public links :
https://community.sonatype.com/t/sonatype-2019-0115-primefaces-issue/1915

sonatype-2014-0026 Django (py2.py3-none-any) 1.9.6 (.whl) Open
sonatype-2016-0107 Django (py2.py3-none-any) 1.9.6 (.whl) Open
sonatype-2019-0133 Django (py2.py3-none-any) 1.9.6 (.whl) Open
sonatype-2016-0610 Django 1.9.6 (.tar.gz) Open
sonatype-2019-0280 djangorestframework (py2.py3-none-any) 3.3.3 (.whl) Open
sonatype-2017-0050 Django (py2.py3-none-any) 1.9.6 (.whl) Open
sonatype-2017-0051 Django (py2.py3-none-any) 1.9.6 (.whl) Open
sonatype-2016-0129 djangorestframework (py2.py3-none-any) 3.3.3 (.whl) Open
sonatype-2017-0565 httplib2 0.9.2 (.tar.gz) Open



Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993


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

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

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

[Yang Bin]

Hi,

I figured out how to update the doc submodule and the patch was submitted:

https://gerrit.onap.org/r/#/c/doc/+/90494/

@Eric,  Thanks for your help

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-rele...@lists.onap.org [mailto:onap-rele...@lists.onap.org] On 
Behalf Of Yang Bin
Sent: Tuesday, June 25, 2019 9:13 PM
To: Catherine LEFEVRE; onap-tsc@lists.onap.org; onap-rele...@lists.onap.org
Subject: Re: [Onap-release] URGENT - ONAP Dublin - Remaining Activities

Hi Catherine,

I wish I could help but I have limited knowledge on doc update/merge/cherry 
pick, is there any guidance on that?

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

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

Good morning All,

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

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

Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

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


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

TEXTING and DRIVING... It Can Wait

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



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



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

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

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

[Yang Bin]

Hi Catherine,

I wish I could help but I have limited knowledge on doc update/merge/cherry 
pick, is there any guidance on that?

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

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

Good morning All,

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

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

Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

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


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

TEXTING and DRIVING... It Can Wait

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



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



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

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

Re: [onap-tsc] k8s Cloud Region Support code merge follow up

[Yang Bin]

Hi Kiran,

One more thing, I didn't find out the released version of docker image for 
multicloud k8s plugin:  
https://nexus3.onap.org/#browse/search=keyword%3Dmulticloud:7f6379d32f8dd78ffbc31d640deb8dd0

Please release the docker image and update the image tag with the released one  
in the values.yaml,

https://gerrit.onap.org/r/#/c/85992/5/kubernetes/multicloud/charts/multicloud-k8s/values.yaml
image: onap/multicloud/k8s:0.1.0-SNAPSHOT


Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Yang, Bin
Sent: Monday, May 06, 2019 10:12 AM
To: 'Deng, Yipan'; onap-tsc@lists.onap.org
Cc: Kamineni, Kiran K; Sood, Ritu; Addepalli, Srinivasa R
Subject: RE: k8s Cloud Region Support code merge follow up

Hi Yipan, Kiran,

I just reviewed the patch, I think it looks okay to me as far as the missing of 
nodeport declaration can be fixed.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Deng, Yipan [mailto:yipan.d...@intel.com]
Sent: Sunday, May 05, 2019 3:04 PM
To: onap-tsc@lists.onap.org; Yang, Bin
Cc: Kamineni, Kiran K; Sood, Ritu; Addepalli, Srinivasa R
Subject: k8s Cloud Region Support code merge follow up

Dear TSC, Bin, and OOM team,

As a follow up to the TSC call on Thursday on k8s cloud region support code 
merge request,


1.  Adding helm chart for multicloud-k8s: 
https://gerrit.onap.org/r/#/c/85992/ (Owner: Kiran Kamineni):

a.  Impact analysis: Bin could you please help us to assess if there is any 
impact to Multi-Cloud project prior Monday PTL meeting?

2.  Adding helm chart for etcd: https://gerrit.onap.org/r/#/c/86211/ 
(Owner: Ritu Sood):

a.  Ritu had updated the patch to make sure the Helm Chart aligned with 
ONAP standard.

b.  Impact analysis: only k8s plug-in project will be using it and no 
impact to other projects, it is just a helm chart sitting in the repository.

Regards,
Yipan






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

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

Re: [onap-tsc] k8s Cloud Region Support code merge follow up

[Yang Bin]

Hi Yipan, Kiran,

I just reviewed the patch, I think it looks okay to me as far as the missing of 
nodeport declaration can be fixed.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Deng, Yipan [mailto:yipan.d...@intel.com]
Sent: Sunday, May 05, 2019 3:04 PM
To: onap-tsc@lists.onap.org; Yang, Bin
Cc: Kamineni, Kiran K; Sood, Ritu; Addepalli, Srinivasa R
Subject: k8s Cloud Region Support code merge follow up

Dear TSC, Bin, and OOM team,

As a follow up to the TSC call on Thursday on k8s cloud region support code 
merge request,


1.  Adding helm chart for multicloud-k8s: 
https://gerrit.onap.org/r/#/c/85992/ (Owner: Kiran Kamineni):

a.  Impact analysis: Bin could you please help us to assess if there is any 
impact to Multi-Cloud project prior Monday PTL meeting?

2.  Adding helm chart for etcd: https://gerrit.onap.org/r/#/c/86211/ 
(Owner: Ritu Sood):

a.  Ritu had updated the patch to make sure the Helm Chart aligned with 
ONAP standard.

b.  Impact analysis: only k8s plug-in project will be using it and no 
impact to other projects, it is just a helm chart sitting in the repository.

Regards,
Yipan






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

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

Re: [onap-tsc] !!! ONAP Dublin - Call for Action !!!

[Yang Bin]

Hi Jim,

That testing is part of original testing plan, and I am looking for claim this 
a new feature in Dublin Release.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Jim Baker [mailto:jba...@linuxfoundation.org]
Sent: Monday, April 22, 2019 9:01 PM
To: Yang, Bin
Cc: Yang Xu (Yang, Fixed Network) (yang@huawei.com); Catherine LEFEVRE; 
onap-rele...@lists.onap.org; onap-usecase...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: Re: !!! ONAP Dublin - Call for Action !!!

Hi Bin,
Thanks for the testing approach for multi-cloud. Since it is not  realized it 
will be moved to OUTPLAN for the release. Are you looking for that additional 
testing to claim a new feature OR just for future reference? Please let me know.
Jim

On Mon, Apr 22, 2019 at 1:50 AM Yang, Bin 
mailto:bin.y...@windriver.com>> wrote:
Hi Jim, Yang Xu,

I had a following up action by last TSC call on the update of functional 
requirement of “Consistent ID of a Cloud Region”, it is yellow since OOF does 
not realize it in Dublin release.

However, I assume it could be tested without oof in certain test cases, e.g. vFW

I try to explain a little bit how the test case could be done:
Assume: there are 2 clouds, or 1 cloud with 2 tenants.
Step1 : With curl commands to AAI or ESR GUI portal, onboard 2 cloud region 
with : same cloud-region-id (e.g. RegionOne), but different cloud-owner (e.g. 
CloudOwner1, CloudOwner2, respectively)
Step 2:  With VID GUI portal, these 2 cloud regions should be populated in the 
dropdown list, deploy 2 service instances to different cloud region respectively
Step 3: Observe the created heat stacks on respective cloud regions


The idea was described at Test Plan 2: vFW Use Case covering"Consistent ID of 
Cloud Region" from 
https://wiki.onap.org/display/DW/Use+Case+Tracking+in+Dublin+Release

Hope this is clear, please let me know how I can help further.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org> 
[mailto:onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>] 
On Behalf Of Catherine LEFEVRE
Sent: Thursday, April 18, 2019 11:18 PM
To: 'onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>'; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [Onap-usecasesub] !!! ONAP Dublin - Call for Action !!!
Importance: High

Dear Use Case/Functional and Non-Functional Owners,

I want to inform you about a decision that the TSC took during the TSC call on 
4/18.

TSC agreed that, if no feedback provided to Jim by 4/22 EOD,  any requirement 
(use case, functional requirement, non-functional requirement), currently 
marked in yellow/(red), not due to testing blockers/issues,
will be moved to the Dublin POC section a.k.a no more be part of the official 
release.

Please take immediate action and talk to Jim – thank you !

Best regards
Catherine

[cid:image001.jpg@01D4F9B6.739F4990]

Catherine Lefèvre
AVP Software Development & Engineering

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


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

TEXTING and DRIVING… It Can Wait

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



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




--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007

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

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

Re: [onap-tsc] !!! ONAP Dublin - Call for Action !!!

[Yang Bin]

Hi Jim, Yang Xu,

I had a following up action by last TSC call on the update of functional 
requirement of "Consistent ID of a Cloud Region", it is yellow since OOF does 
not realize it in Dublin release.

However, I assume it could be tested without oof in certain test cases, e.g. vFW

I try to explain a little bit how the test case could be done:
Assume: there are 2 clouds, or 1 cloud with 2 tenants.
Step1 : With curl commands to AAI or ESR GUI portal, onboard 2 cloud region 
with : same cloud-region-id (e.g. RegionOne), but different cloud-owner (e.g. 
CloudOwner1, CloudOwner2, respectively)
Step 2:  With VID GUI portal, these 2 cloud regions should be populated in the 
dropdown list, deploy 2 service instances to different cloud region respectively
Step 3: Observe the created heat stacks on respective cloud regions


The idea was described at Test Plan 2: vFW Use Case covering"Consistent ID of 
Cloud Region" from 
https://wiki.onap.org/display/DW/Use+Case+Tracking+in+Dublin+Release

Hope this is clear, please let me know how I can help further.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-usecase...@lists.onap.org [mailto:onap-usecase...@lists.onap.org] On 
Behalf Of Catherine LEFEVRE
Sent: Thursday, April 18, 2019 11:18 PM
To: 'onap-rele...@lists.onap.org'; onap-usecase...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: [Onap-usecasesub] !!! ONAP Dublin - Call for Action !!!
Importance: High

Dear Use Case/Functional and Non-Functional Owners,

I want to inform you about a decision that the TSC took during the TSC call on 
4/18.

TSC agreed that, if no feedback provided to Jim by 4/22 EOD,  any requirement 
(use case, functional requirement, non-functional requirement), currently 
marked in yellow/(red), not due to testing blockers/issues,
will be moved to the Dublin POC section a.k.a no more be part of the official 
release.

Please take immediate action and talk to Jim - thank you !

Best regards
Catherine

[cid:image002.jpg@01D4F922.7EC3EA40]

Catherine Lefèvre
AVP Software Development & Engineering

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


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

TEXTING and DRIVING... It Can Wait

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



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



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

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

Re: [onap-tsc] Dublin risks

[Yang Bin]

Hi Jim,

I just update the wiki to inform you and the community of the risk from 
multicloud team: a multicloud component named multicloud azure plugin might not 
be able to meet S3P and security requirement in Dublin due to lack of resource.

The mitigation plan is to postpone it to next release.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of Jim 
Baker
Sent: Thursday, March 28, 2019 11:52 PM
To: onap-tsc
Subject: [onap-tsc] Dublin risks

Folks,
Just a reminder to revisit the Dublin 
Risks page and update/add 
program risks. By keeping this up to date, we allow others in the community to 
understand AND lend a hand where possible. Thanks for keeping this list current!
Best regards,

--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007


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

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

[onap-tsc] Committer promotion requests for MultiCloud

[Yang Bin]

Dear TSC,

Based on the contribution in Casablanca Release, Existing committers of 
MultiCloud Project have nominated and voted for new committers in Dublin 
Release, According to the Technical Chart, Xiaohua Zhang and Ritu Sood got 
majority approval from existing committers, thereby I request the approval from 
TSC to accept them as new committers to MultiCloud Project, the evidence could 
be found at https://wiki.onap.org/pages/viewpage.action?pageId=60883801

Note: The short link to biterg stats does not work very well, for your 
convenience , the snapshot of biterg stats is also embedded into that wiki page:

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993
_._,_._,_

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

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

Re: [onap-tsc] [multicloud] removing committers on MultiCloud project

[Yang Bin]

Hi TSC,

According to the process: https://wiki.onap.org/display/DW/INFO.yaml+Guidelines

Removing committers from a project needs approval from TSC as well? Please help 
clarify , thanks

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Yang Bin
Sent: Monday, February 18, 2019 2:17 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] [multicloud] removing committers on MultiCloud project

Dear TSC,

This is to inform you of the removing below 2 MultiCloud committers as they had 
requested to step down from the committer position from Dublin Release.

Yun Huang  cloudhuan...@gmail.com Beijing, China. UTC +8:00

Ke Lianglok...@163.comBeijing, China. UTC +8:00

I would appreciate their great contribution to MultiCloud project!

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Martial
Sent: Thursday, February 07, 2019 9:57 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] removing committers on CLAMP project due to long inactivity

Hello tsc,

This mail is to inform you of the below 2 CLAMP committers because they were 
inactive on the project for the last 6 month.

Repo

Name

email

# com

onap-gerrit-clamp-committers

Pierre Close

pierre.cl...@intl.att.com<mailto:pierre.cl...@intl.att.com>

0

onap-gerrit-clamp-committers

xinyuan wang

wang.xinyu...@zte.com.cn<mailto:wang.xinyu...@zte.com.cn>

0



Br,
Martial (CLAMP PTL)


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

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

[onap-tsc] [multicloud] Request approval for the Multi-VIM, Multi-cloud project scope change.

[Yang Bin]

Dear TSC,

   I would like to request the approval for this Multi-VIM/Cloud 
project change which has been endorsed by the ARC subcommittee: 
https://wiki.onap.org/pages/viewpage.action?pageId=50201143.

Please let me know your comments/concerns if any.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Wednesday, February 13, 2019 5:09 AM
To: onap-tsc@lists.onap.org; Yang, Bin
Subject: [onap-tsc] Multi-VIM, Multi-cloud project scope.

Hi TSC,

At the last DDF as the compossible infrastructure was included in the 
multi-VIM/Multi-cloud project, the project definition needs an updated.  As per 
what we have stated, that requires an review from ArchCom, and ArchCom 
recommends it for approval.  There was, however, one question - and that was 
whether the project name should remain as Multi-Vim/Mult-cloud or just be 
multi-cloud.  We said that this is not an architecture question, but for the 
TSC.

Here is a link to the updated project definition, which now needs TSC approval: 
https://wiki.onap.org/pages/viewpage.action?pageId=50201143

BR,

Steve

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

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com<http://www.ericsson.com/>

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

Our commitment to Technology for 
Good<http://www.ericsson.com/thecompany/sustainability-corporateresponsibility> 
and Diversity and 
Inclusion<http://www.ericsson.com/thecompany/diversity-inclusion> contributes 
to positive change.
Follow us on: Facebook<https://www.facebook.com/ericsson> 
LinkedIn<https://www.linkedin.com/company/ericsson> 
Twitter<https://twitter.com/Ericsson>

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer<https://www.ericsson.com/en/legal/privacy/email-disclaimer>


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

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

[onap-tsc] [multicloud] removing committers on MultiCloud project

[Yang Bin]

Dear TSC,

This is to inform you of the removing below 2 MultiCloud committers as they had 
requested to step down from the committer position from Dublin Release.

Yun Huang  cloudhuan...@gmail.com Beijing, China. UTC +8:00

Ke Lianglok...@163.comBeijing, China. UTC +8:00

I would appreciate their great contribution to MultiCloud project!

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Martial
Sent: Thursday, February 07, 2019 9:57 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] removing committers on CLAMP project due to long inactivity

Hello tsc,

This mail is to inform you of the below 2 CLAMP committers because they were 
inactive on the project for the last 6 month.

Repo

Name

email

# com

onap-gerrit-clamp-committers

Pierre Close

pierre.cl...@intl.att.com

0

onap-gerrit-clamp-committers

xinyuan wang

wang.xinyu...@zte.com.cn

0



Br,
Martial (CLAMP PTL)

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

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

[onap-tsc] Update scope of MultiCloud project to cover Composable Disaggregate Infrastructure

[Yang Bin]

Dear TSC, ARC subcommittee, and all

As suggested during the TSC meeting in DDF Paris, I had drafted the updated 
scope of Multi-VIM/Cloud project to request approval from TSC (Changes are 
highlighted in red on the wiki page: 
https://wiki.onap.org/pages/viewpage.action?pageId=50201143 )

   Please review and feel free to comment, I would like to request 
a timeslot during ARC subcommittee on Feb 12th to get endorsement of ARC 
subcommittee before requesting approval of TSC.

Thanks.

BTW, I will be on vacation due to Chinese holiday in next 8 days, I will check 
the email and respond to your questions occasionally.

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

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

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

[onap-tsc] Dublin release participation - Multi-VIM/Cloud

[Yang Bin]

Dear TSC,

   This is to inform you that Multi-VIM/Cloud project intends to 
participate in the ONAP Dublin Release.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993


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

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

Re: [onap-tsc] URGENT: ONAP Casablanca RC2 Vote

[Yang Bin]

+1

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Wednesday, November 28, 2018 1:05 AM
To: onap-tsc-v...@lists.onap.org
Subject: [onap-tsc] URGENT: ONAP Casablanca RC2 Vote

(bcc to onap-tsc list for general visibility)

We were just about to go to a vote on RC2 when everyone was dropped from the 
bridge. Unable to regain quorum following the disconnect, an email vote must be 
taken.

Does the TSC approve the recommendations made during the Nov. 27th TSC RC2 
Review meeting that all projects pass the RC2 milestone?
+1, 0, -1




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

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

Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

[Yang Bin]

OK, I am ok with that, thanks for the explanation.

BTW, could you share some pointers w.r.t. the new BB, especially “With these 
new flows, at assignment stage, all the required ressources would get resolved 
by SDNC and stored in SDNC GR-API,” I would like to understand what the flow is 
at the assignment stage, and check if multicloud could help on that.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Alexis de Talhouet
Sent: Friday, October 12, 2018 10:18 AM
To: onap-tsc@lists.onap.org
Cc: onap-discuss; Seshu m; TIMONEY, DAN
Subject: Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

We re not trying to fulfill this requirement; although we are very aware of it. 
It is planned for Dublin, and won’t get in Casablanca; this is not the 
intention.
We’re not either changing any of the existing behaviour.
I’m not proposing any solution here, simply asking for an API waiver as we need 
to add a field in GR-API yang to get rid of the hard coded cloud owner in the 
new SO BB. The solution has been there before, it’s just lack of time before 
API freeze, and in this matter, introducing a regression.

Background:
SO and SDNC added respectively new Building Blocks and support for GR-API, in 
order to avoir having to perform the manual preload step. With these new flows, 
at assignment stage, all the required ressources would get resolved by SDNC and 
stored in SDNC GR-API, so at creation stage, all SO has to do is query SDNC to 
gets the resources to use, and proceed with creation.
What was uncover late is SO new BBs are using a hard coded cloud owner. The 
change is simply to allow having that cloud owner configurable. It is a 
small/quick fix in order to provide somewhat of a feature parity between former 
SO flow and new SO flows.

I’m asking the TSC for an API waiver as we're pass API freeze and this is an 
API change, in some ways.  If you want to discuss more in detail that 
functionality, I’ll be happy to explain over a meeting.
My intention is to have a quick turnaround on the API change waiver request. I 
hope TSC will be able to see the urgency in that matter, given RC0, so we don’t 
debate too much on a requirement, as as stated before, we’re not trying to 
fulfil any; simply to fix a regression.

Thanks,
Alexis

On Oct 11, 2018, at 9:04 PM, Yang Bin 
mailto:bin.y...@windriver.com>> wrote:
Hi Alexis, Dan,

   I am not sure if you are aware the ONAP functional requirement 
about the “Centralized Representation and Consistent Identification of Cloud 
Regions In 
ONAP<https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP>”
 
https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP

   The functional requirement consists of 2 important changes:
1, remove any hardcoded/redundant representation of a single cloud region, the 
hard-coded cloud-sites in SO configuration file is exactly what is  targeting 
to be refactored. Now this part is on track of pairwise testing between 
SO/MultiCloud .
2, apply the usage of ID of a cloud region in a consistent way , the agreement 
is that the composite keys: {cloud-owner}/{cloud-region-id} will be applied 
whenever ONAP component wants to refer to a cloud region. This part requires 
the API changes between VID/SO/SDNC and other related projects. It is  a 
stretch goal in Casablanca, perhaps we can get it done in Dublin Release.

   I do believe both of 2 changes above might be related to your 
proposal. I would like to discuss a little bit about the issue and your 
proposal so that maybe we can come up with more comprehensive/consistent 
solution to get things (API changes) done at one time.

   If you don’t mind, we can start with several questions:
   1, why should the Cloud-Owner be provisioned to SDNC with 
REST-API?
I guess your proposal is to provision the “Cloud Owner” instead of having it 
being hard-coded . I agree with you that it should not be hard-coded, but why 
should the Cloud-Owner be provisioned to SDNC with REST-API?
IMHO, “Cloud-Owner” (and the cloud-region-id ) should be selected either by 
user via VID portal or by OOF according to policy. In that case, the ID  of the 
selected cloud region ({cloud-owner}/{cloud-region-id} ) should be passed to 
SO/SDNC/etc. through rest API.

2, Will SDNC use the ID  of the selected cloud region to retrieve information 
from AAI?
   This question is to help me understand what the interactions are 
between SDNC and AAI

3, Will SDNC use the ID  of the selected cloud region to retrieve information 
from underlying VIM/Cloud instance (e.g. OpenStack instance)?
   Th

Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

[Yang Bin]

Hi Alexis, Dan,

I am trying to understand the changes of the patch:
https://gerrit.onap.org/r/#/c/67413/1/generic-resource-api/model/src/main/yang/GENERIC-RESOURCE-API.yang

If I am not get it wrong, this changes of this patch is only to add 
“cloud-owner” as part of SDNC rest API  with witch SO will have to provide the 
“cloud owner” along with “aic-cloud-region”?In that case I do think this is 
the reasonable change and consistent to the functional requirement of 
“consistent ID of cloud regions”.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Yang Bin
Sent: Friday, October 12, 2018 9:04 AM
To: onap-tsc@lists.onap.org; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hi Alexis, Dan,

   I am not sure if you are aware the ONAP functional requirement 
about the “Centralized Representation and Consistent Identification of Cloud 
Regions In 
ONAP<https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP>”
 
https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP

   The functional requirement consists of 2 important changes:
1, remove any hardcoded/redundant representation of a single cloud region, the 
hard-coded cloud-sites in SO configuration file is exactly what is  targeting 
to be refactored. Now this part is on track of pairwise testing between 
SO/MultiCloud .
2, apply the usage of ID of a cloud region in a consistent way , the agreement 
is that the composite keys: {cloud-owner}/{cloud-region-id} will be applied 
whenever ONAP component wants to refer to a cloud region. This part requires 
the API changes between VID/SO/SDNC and other related projects. It is  a 
stretch goal in Casablanca, perhaps we can get it done in Dublin Release.

   I do believe both of 2 changes above might be related to your 
proposal. I would like to discuss a little bit about the issue and your 
proposal so that maybe we can come up with more comprehensive/consistent 
solution to get things (API changes) done at one time.

   If you don’t mind, we can start with several questions:
   1, why should the Cloud-Owner be provisioned to SDNC with 
REST-API?
I guess your proposal is to provision the “Cloud Owner” instead of having it 
being hard-coded . I agree with you that it should not be hard-coded, but why 
should the Cloud-Owner be provisioned to SDNC with REST-API?
IMHO, “Cloud-Owner” (and the cloud-region-id ) should be selected either by 
user via VID portal or by OOF according to policy. In that case, the ID  of the 
selected cloud region ({cloud-owner}/{cloud-region-id} ) should be passed to 
SO/SDNC/etc. through rest API.

2, Will SDNC use the ID  of the selected cloud region to retrieve information 
from AAI?
   This question is to help me understand what the interactions are 
between SDNC and AAI

3, Will SDNC use the ID  of the selected cloud region to retrieve information 
from underlying VIM/Cloud instance (e.g. OpenStack instance)?
   This question would help me understand if there is interaction 
between SDNC and underlying VIM/Cloud instance

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: .https://gerrit.onap.org/r/#/c/67413/

Regards,
Alexis


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

Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

[Yang Bin]

Hi Alexis, Dan,

   I am not sure if you are aware the ONAP functional requirement 
about the “Centralized Representation and Consistent Identification of Cloud 
Regions In 
ONAP”
 
https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP

   The functional requirement consists of 2 important changes:
1, remove any hardcoded/redundant representation of a single cloud region, the 
hard-coded cloud-sites in SO configuration file is exactly what is  targeting 
to be refactored. Now this part is on track of pairwise testing between 
SO/MultiCloud .
2, apply the usage of ID of a cloud region in a consistent way , the agreement 
is that the composite keys: {cloud-owner}/{cloud-region-id} will be applied 
whenever ONAP component wants to refer to a cloud region. This part requires 
the API changes between VID/SO/SDNC and other related projects. It is  a 
stretch goal in Casablanca, perhaps we can get it done in Dublin Release.

   I do believe both of 2 changes above might be related to your 
proposal. I would like to discuss a little bit about the issue and your 
proposal so that maybe we can come up with more comprehensive/consistent 
solution to get things (API changes) done at one time.

   If you don’t mind, we can start with several questions:
   1, why should the Cloud-Owner be provisioned to SDNC with 
REST-API?
I guess your proposal is to provision the “Cloud Owner” instead of having it 
being hard-coded . I agree with you that it should not be hard-coded, but why 
should the Cloud-Owner be provisioned to SDNC with REST-API?
IMHO, “Cloud-Owner” (and the cloud-region-id ) should be selected either by 
user via VID portal or by OOF according to policy. In that case, the ID  of the 
selected cloud region ({cloud-owner}/{cloud-region-id} ) should be passed to 
SO/SDNC/etc. through rest API.

2, Will SDNC use the ID  of the selected cloud region to retrieve information 
from AAI?
   This question is to help me understand what the interactions are 
between SDNC and AAI

3, Will SDNC use the ID  of the selected cloud region to retrieve information 
from underlying VIM/Cloud instance (e.g. OpenStack instance)?
   This question would help me understand if there is interaction 
between SDNC and underlying VIM/Cloud instance

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: .https://gerrit.onap.org/r/#/c/67413/

Regards,
Alexis


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

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

[onap-tsc] Invitation: TSC Meeting (updated March 22, 2018) @ Weekly from 7am to 8:30am on Thursday (PDT) (onap-tsc@lists.onap.org)

[Yang Bin]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID: 1
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=ONAP Meetings and Events;SENT-BY="MAILTO:bin.y...@windriver.com"
 :MAILTO:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.goog
 le.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-tsc@l
 ists.onap.org:MAILTO:onap-tsc@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jphelps@li
 nuxfoundation.org:MAILTO:jphe...@linuxfoundation.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Huang, Yun"
 :MAILTO:yun.hu...@windriver.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Gooch, Ste
 phen":MAILTO:stephen.go...@windriver.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=agrimberg@
 linuxfoundation.org:MAILTO:agrimb...@linuxfoundation.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jwagantall
 @linuxfoundation.org:MAILTO:jwagant...@linuxfoundation.org
ATTACH:CID:EF318D601067A64681E4F61150356C2C@local
ATTACH:CID:BE35C2F8778AEA47AEC9E6A11E352422@local
DESCRIPTION;LANGUAGE=zh-CN:\n\nmore details »\n\nTS
 C Meeting (updated March 22\, 2018)\nWhenWeekly from 7am to 8:30am on 
 Thursday Pacific Time\nWhere   https://zoom.us/j/661303200 (map)\nCalendaronap-...@lists.onap.or
 g\nWho •   kp...@linuxfoundation.org - creator\n•   Andrew
  Grimberg\n•   jphe...@linuxfoundation.org\n•   jwagantall@lin
 uxfoundation.org\n•   onap-tsc@lists.onap.org\n\nONAPmeet1 is inviti
 ng you to a scheduled Zoom meeting.\n\nJoin from PC\, Mac\, Linux\, iOS or
  Android: https://zoom.us/j/661303200\n\nOr iPhone one-tap :\nUS: +16465588656\,\,661
 303200# or +16699006833\,\,661303200#\nOr Telephone:\nDial(for higher 
 quality\, dial a number based on your current location):\nUS: +1 6
 46 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 36
 9 0926 (Toll Free)\nMeeting ID: 661 303 200\nInternational numbers
  available: https://zoom.us/zoomconference?m=FHWF11_wwIutwd1PAi_vsotA5bQ6k
 CLh\nGoing?   All events in this series:   Yes - Maybe - No
 more options »
 \nInvitation from Google Calendar\n\nYou
  are receiving this courtesy email at the account onap-tsc@lists.onap.org 
 because you are an attendee of this event.\n\nTo stop receiving future upd
 ates for this event\, decline this event. Alternatively you can sign up fo
 r a Google account at https://www.google.com/calendar/ and control your no
 tification settings for your entire calendar.\n\nForwarding this invitatio
 n could allow any recipient to modify your RSVP response. Learn More.\n
SUMMARY;LANGUAGE=zh-CN:[onap-tsc] Invitation: TSC Meeting (updated March 22
 \, 2018) @ Weekly from 7am to 8:30am on Thursday (PDT) (onap-...@lists.ona
 p.org)
DTSTART;TZID= 1:20181004T07
DTEND;TZID= 1:2

Re: [onap-tsc] TSC Seat Vanacy

[Yang Bin]

Hi Catherine and TSC member,

Oct. 1st- 7th will be national holiday of China, So I would suggest that 
postpone the deadline by 1 week, Thanks.

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Catherine LEFEVRE
Sent: Wednesday, September 26, 2018 7:53 AM
To: ONAP-TSC@lists.onap.org
Subject: Re: [onap-tsc] TSC Seat Vanacy

Good morning TSC members,

I have reviewed the feedback that you have provided so far.

We are all in alignment to enhance the TSC Chart to address how to handle a 
vacancy.

It would be good to learn from other open source communities about how they are 
dealing with such situation while we are considering our ONAP ecosystem: 
reserved seats for operators and non-reserved seats.
We should not re-invent the wheel unnecessarily, there are certainly common 
patterns for some scenarios that you have listed.

I also recommend that we set a deadline to finalize the TSC chart addendum.
Therefore, on Oct 4th, we, the TSC, should present to the ONAP community our 
TSC chart amendment and then immediately act accordingly.
Stephen has already started to draft a new proposal that could be used as our 
starting point.
Jason was also making some suggestions considering our ONAP structure.

As a short-term solution, some of you have suggested that Huawei is identifying 
a proxy.
I believe this is indeed a great temporary solution so the new TSC can continue 
to operate as expected.
Chris, can you please confirm who will be your proxy? Thank you.

TSC members – let me know if you disagree otherwise let’s move forward and work 
on our TSC Chart add-on.

Many thanks and regards
Catherine

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Sunday, September 23, 2018 6:43 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] TSC Seat Vanacy

I wanted to follow up on the discussion regarding a special election due to 
Chris taking a new job.  One of the first questions asked was, "What does the 
Charter say?"  Neither the Charter or Community Document says anything about a 
vacancy. In the absence of any specific language, the default should be to 
honor what language there is.  Currently the Community Document says:

4.1.1.2 Size and Structure
The TSC shall consist of eighteen (18) seats
Nine (9) seats on the TSC are to be reserved for Operators
Only one (1) person from any company, or group of related companies (as defined 
in section 4.4.4.1) may be a member at any given time.

As such, my guidance to the TSC is to immediately authorize a special election 
using the criteria currently defined in the Community Document, plain and 
simple.

There were a several alternatives to a special election which have been 
suggested. While it is well within the TSC's right to pursue any of these 
alternatives, all must be thoroughly scrutinized through the lens of fairness, 
trust, and responsibility to the community.


  *   Leaving the seat vacant until the next election cycle
It took 6 months to debate and vote on membership criteria, and another full 
month to run an election. Leaving the seat vacant until the next scheduled 
election implies that after all that work the TSC doesn't care about being 
fully functional.  This would be a huge hit to the community's trust of the TSC.


  *   Delay any decision on an election until the TSC amends the Community 
Document to address how to handle a vacancy
This is marginally better than leaving the seat vacant, because who knows how 
long amending the Community Document might take. I would encourage the TSC to 
take up amending the Community Document to cover one or more of the operational 
and governance gaps that exist, however it is unfair to the ONAP community to 
hold the recently vacated seat hostage to those discussions.


  *   Have Chris appoint his replacement
When the TSC was comprised of only appointed individuals doing this would have 
been fine course of action. In fact, there were a couple instances back in 
March where this occurred. Now that we have moved from an appointed TSC to an 
elected TSC, such an appointment by a member is completely inappropriate.


  *   Make the next runner up in the August election the new TSC member
While true the seat does not belong to Huawei, it would be exceeding unfair to 
them, especially as the 2nd largest contributor to the Project, to suddenly be 
out in the cold with absolutely no chance to even compete for a seat they once 
held.

I don't like creating work for myself and a TCS election is indeed a great deal 
of work. The thought of having to run a new election is mind-numbing but I 
welcome it gladly because it is absolutely the right thing to do.

I recommend a one week nomination period, and a one week voting period. (The 
prior election was lengt

Re: [onap-tsc] [tsc][esr] ESR related working handover

[Yang Bin]

Hi Lizi,

Indeed, it has been really a pleasure journey to work with you.

Best wishes on your future endeavors .

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Huabing Zhao
Sent: Thursday, August 30, 2018 9:56 PM
To: ONAP-TSC@lists.onap.org
Cc: lv.bo...@zte.com.cn
Subject: Re: [onap-tsc] [tsc][esr] ESR related working handover

Dear Lizi,

Thanks for your great contributions to the community.

It has been a pleasure working with you, and I wish you all the best in the 
future.

Best regards,
Huabing

On Thu, Aug 30, 2018, 10:02 AM LiZi 
mailto:li.z...@zte.com.cn>> wrote:

Dear TSC,

It is a pleasant and awesome experience to working with the members in ONAP 
community. But today it is my pity to say that for my personal job changes, I 
will not continue to contribute in ONAP community. If you have any issues about 
ESR, please contact my colleague Lv 
Bo(lv.bo...@zte.com.cn).



Sorry for the inconvenience,

LiZi










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

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

[onap-tsc] Promotion of new committers for Multi-VIM/Cloud project

[Yang Bin]

Dear TSC,

According to  ONAP Technical Community 
Document, 
Section 3.2.2.1 "Adding Committers" and current practice of adding new 
committers in other ONAP projects, Andrew Philip has stepped down as committer 
of Multi-VIM/Cloud Project, and remaining committers of Multi-VIM/Cloud project 
thus nominated and voted for promotion of 5 new committers: Yun Huang,Ethan 
Lynn, Victor Morales, Haibin Huang, Sudhakar Reddy. Please refer to 
https://wiki.onap.org/pages/viewpage.action?pageId=38109905  for record. This 
is FYI for TSC.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993


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

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

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Yang Bin]

Dear ONAP Community,



I would like to humbly self-nominate for the ONAP TSC election.



I have been participating ONAP since its inception and engaged in various 
community activities. I have been contributed to the success of ONAP Amsterdam 
release and Beijing Release with the contributions to Multi-VIM/Cloud project 
development, Pair-wise testing, Integration Testing, Wind River/Intel 
Integration Lab supporting, CMCC and China Telecom Open Lab supporting. I have 
been developing demos with ONAP and showcasing them during various events 
including ONS, MWC 2018. with these experience, I identified generic functional 
requirement referred as Centralized representation and consist ID of cloud 
regions which has been one of ONAP functional requirements in Casablanca 
Release. I also shared my experiences and best practices of using ONAP through 
ONAP wiki, email list, and hotline meetings. As a core committer and PTL of 
ONAP Multi-VIM/Cloud project, I have been presented my insight and the vision 
of ONAP Multi-VIM/Cloud during OPNVF,ONS and ONAP events. To facilitate the end 
to end automation of orchestration and close loop control I have proposed 
various features to Multi-VIM/Cloud project which will be designed them 
properly and delivered them in time.



I would like to run for a seat of ONAP TSC and contribute to the the success of 
ONAP by expanding its capability of orchestrating workloads to various VIMs or 
Clouds in a cloud agnostic way.



My Bitergia Stats can be found at:

https://onap.biterg.io/goto/8b4f6c15e6b47caeef679a065fb36cc0



Short Bio:



Bin Yang is a solution architect from Wind River and dedicated to support ONAP 
community. He has more than 13 year experience in software design & development 
for Telecom industry. He has solid knowledge and skill for OpenStack, Operating 
System, and Silicon. He demonstrated his expertise and passion for Open Source 
community with the success of OPEN-O MultiVIM project as PTL, ONAP 
Multi-VIM/Cloud as core committer and PTL. He loves this ONAP community since 
he can not only have achievement with the success of this community, but also 
make many friends who are great and talent persons.



Bin Yang holds a BS in computer science and technology from Huangzhong 
University of Science and Technology in China.



My head-shot:



[Machine generated alternative text:]


Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Wednesday, July 18, 2018 8:03 AM
To: onap-tsc
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions
  Active Community Member: Anyone from the ONAP community with twenty (20) or 
more measurable contributions during the previous 12-month period, inclusive of 
code merged, code reviews performed, wiki page edits, or JIRA activities



Self-Nomination Phase

Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this).
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.

As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates wiki 
page with that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their sea

Re: [onap-tsc] [Onap-release] [ptl][jira] Propose alignment on 1 Jira workflow

[Yang Bin]

+1

It will be great that if you can upload this slide to wiki so that we can refer 
to when discussing over weekly meetings.

(Multi-VIM/Cloud PTL)

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-rele...@lists.onap.org [mailto:onap-rele...@lists.onap.org] On 
Behalf Of Taka Cho
Sent: Friday, July 27, 2018 3:51 AM
To: Dhananjay Pavgi; Shankar Narayanan; DRAGOSH, PAM
Cc: MAHER, RANDA; onap-rele...@lists.onap.org; onap-tsc; 
onap-disc...@lists.onap.org
Subject: Re: [onap-tsc] [Onap-release] [ptl][jira] Propose alignment on 1 Jira 
workflow

+1

Taka

From: onap-rele...@lists.onap.org [mailto:onap-rele...@lists.onap.org] On 
Behalf Of Dhananjay Pavgi
Sent: Thursday, July 12, 2018 11:28 PM
To: Shankar Narayanan ; DRAGOSH, PAM 

Cc: MAHER, RANDA ; onap-rele...@lists.onap.org; onap-tsc 
; onap-disc...@lists.onap.org
Subject: Re: [onap-tsc] [Onap-release] [ptl][jira] Propose alignment on 1 Jira 
workflow

+1

thanks & regards,
Dhananjay Pavgi
+91 98220 22264

From: ONAP-TSC@lists.onap.org 
mailto:ONAP-TSC@lists.onap.org>> On Behalf Of Shankar 
Narayanan
Sent: Thursday, July 12, 2018 10:26 PM
To: Pamela Dragosh mailto:pdrag...@research.att.com>>
Cc: MAHER, RANDA mailto:rx1...@att.com>>; 
onap-rele...@lists.onap.org; onap-tsc 
mailto:onap-tsc@lists.onap.org>>; 
onap-disc...@lists.onap.org
Subject: Re: [onap-tsc] [Onap-release] [ptl][jira] Propose alignment on 1 Jira 
workflow

+1

Thanks,
Shankar.

On Thu, Jul 12, 2018 at 12:43 PM Pamela Dragosh 
mailto:pdrag...@research.att.com>> wrote:
+1

Pam Dragosh
ONAP Policy PTL

From: mailto:onap-rele...@lists.onap.org>> on 
behalf of "MAHER, RANDA" mailto:rx1...@att.com>>
Date: Monday, July 9, 2018 at 9:46 AM
To: "onap-rele...@lists.onap.org" 
mailto:onap-rele...@lists.onap.org>>
Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>, 
"onap-disc...@lists.onap.org" 
mailto:onap-disc...@lists.onap.org>>
Subject: Re: [Onap-release] [ptl][jira] Propose alignment on 1 Jira workflow

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

This topic was discussed on today’s PTL call.  I am resending email so you 
don’t have to dig for it.
Please provide your feedback if you’re in agreement or if you have any 
questions.
The goal is to align on a single workflow in ONAP.

Also, another topic raised during PTL call, but not part of the attached 
proposal, but I wanted to note it here:

• We should align on the set of Jira issue types that will be used 
across the projects to ensure issues don’t fall through the cracks.

• Today, most projects use: Epics, Stories (& sub-tasks available 
within story),  Tasks, Bugs

• There are some projects that also use New Feature

• What is the set we want to support for ONAP projects?

Thanks, Randa

From: onap-rele...@lists.onap.org 
[mailto:onap-rele...@lists.onap.org] On 
Behalf Of MAHER, RANDA
Sent: Monday, June 25, 2018 9:30 PM
To: onap-rele...@lists.onap.org
Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>; 
onap-disc...@lists.onap.org
Subject: [Onap-release] [ptl][jira] Propose alignment on 1 Jira workflow

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

One of the items in the Beijing Retrospective was confusion over the two 
separate Jira workflows in play today.
I would like to submit the following for consideration to align on ONE Jira 
workflow.  This is low hanging fruit and an easy enough change to implement  to 
progress on addressing one of the concerns raised during Lesson’s Learned 
discussions.

I believe the attached workflow is flexible enough to handle the uniqueness of 
ONAP as well as not introduce overhead for teams.

Please review attached slides and provide your +1 if you agree to the proposal.

Thanks,
Randa
APPC PTL







Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at 
http://www.techmahindra.com/Disclaimer.html
 externally 
http://tim.techmahindra.com/tim/disclai

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

[Yang Bin]

Dear Xinhui, MultiCloud contributors/committers and all the community,

It's always been awesome experience to working with you. Thanks for the great 
help and trust.

With this great honor and responsibility I will do my best to contribute to the 
success of MultiCloud and ONAP.

Best Regards,

Bin

在 2018年7月26日，19:01，Xinhui Li mailto:lxin...@vmware.com>> 写道：

Dear TSC and ONAP community,

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

Congratulations Bin Yang!

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

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

Best wishes and thanks!
Xinhui Li


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

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

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

[Yang Bin]

Dear Multi-VIM/Cloud committers,

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

With more than 13 year experience in Telecom industry in software design & 
development. I have been the PTL of OPEN-O MultiVIM project and active 
committer of ONAP Multi-VIM/Cloud project for ONAP Amsterdam Release and 
Beijing Release. I have been working diligently with all 
committers/contributors to propose, design, implement and deliver important 
features of this project and support the pairwise testing and integration 
testing which contributed a lot to the success of ONAP releases.

I will continue to keep my commitment to this Multi-VIM/Cloud project and also 
this ONAP community to collaborate with all committers and contributors to add 
more features and values to Multi-VIM/Cloud which will contribute to the future 
success of ONAP community.

Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

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

Dear 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

I invite you to submit your self-nomination for ONAP Multi VIM/Cloud project if 
you are interested in this position.

You have to submit your self-nomination from receipt of this email and to July 
23th 2018 10:00 IST

Election duration: July 23th 2018 12:00 IST -  July 26th 2018 12:00 IST
Private email will be sent to all committers email id mentioned at 
https://wiki.onap.org/display/DW/Resources+and+Repositories
 by CVIS system.

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

Thanks,
Xinhui


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

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

Re: [onap-tsc][onap-discuss]Questions about Security Requirements for Casablanca: is CADI the only option to enable RBAC?

[Yang Bin]

Hi Jonathan,

   Appreciate your explanation. Glad to know Python CADI has been 
touched , hope it will be available sometime.

   But integration with CADI requires effort and knowledge to 
understand the whole workflow, and debug/maintain effort as well. It will be 
great if AAF team could come up with solution similar to k8s “side-cars” 
approach. I understand the “side-cars” is not applicable to HEAT deployed ONAP 
, but this will not be the only missing feature compared to OOM, resilience is 
only available with OOM, not heat, correct? If I captured the HEAT/OOM mode 
discussion correctly, HEAT mode is only for testing purpose from Casablanca 
release, which implies the released ONAP will have OOM mode only.

Thanks

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: GATHMAN, JONATHAN C [mailto:jg1...@att.com]
Sent: Wednesday, June 27, 2018 6:15 PM
To: Stephen Terrill; Yang, Bin; onap-tsc; onap-sec...@lists.onap.org
Cc: onap-disc...@lists.onap.org
Subject: Re: [onap-tsc][onap-discuss]Questions about Security Requirements for 
Casablanca: is CADI the only option to enable RBAC?

Greetings, Bin,
  Secure calls using Python is different depending on the Environment.   
However, remember that for Casablanca, we are still on the hook for “HEAT” as 
well as OOM (where “OOM” is Kubernetes).

  If in Kubernetes, there is an effort underway to create a Security 
Microservice, and K8 provides for “Side-Cars” that can be created.  I do not 
think there will be enough time for these for Casablanca.

  AAF is entirely RESTful, with standard HTTP/S authentications.  Any language 
could call, but there needs to be Caching in calls to avoid superfluous network 
traffic, AAF Load.

  CADI Framework is written for Java, but has patterns for this behavior that 
can be used.

  There is such a CADI framework for JavaScript, which we may be able to have 
added into EComp sometime.

  I do have several people on my AT&T Team who have Python experience and have 
expressed interest in building a Python client.

Summary:
  We have an effort with others, working on defining K8 solutions which 
alleviate language issues, but that doesn’t help HEAT or anything else outside 
of K8.

  Language specific CADI can be built, and there have been several requests for 
Python.  Python CADI is not committed for Casablanca, though I have some folks 
with interest in doing such work.

--
Jonathan Gathman
Principled-System Architect
ATO Tech Dev/SEAT/Platform Architecture and Technology Management

AT&T Services, Inc.
2349 Oaker, Arnold, MO 63010
m  314-550-3312  |  
jonathan.gath...@us.att.com<mailto:jonathan.gath...@us.att.com>


From: Stephen Terrill 
Date: Wednesday, June 27, 2018 at 3:04 AM
To: "Yang, Bin" , onap-tsc , 
"onap-sec...@lists.onap.org" , "GATHMAN, JONATHAN 
C" 
Cc: "onap-disc...@lists.onap.org" 
Subject: RE: [onap-tsc][onap-discuss]Questions about Security Requirements for 
Casablanca: is CADI the only option to enable RBAC?

Hi Bin,

I am looping in the onap-seccom distribution list as well.

@Jonathan, what guidance would you provide for Bin regarding use CAD with 
python?

Best Regards,

Steve.

From: Yang, Bin 
Sent: Wednesday, June 27, 2018 5:57 AM
To: Stephen Terrill ; onap-tsc 

Cc: onap-disc...@lists.onap.org
Subject: [onap-tsc][onap-discuss]Questions about Security Requirements for 
Casablanca: is CADI the only option to enable RBAC?

Dear TSC and Security Subcommittee,

As part of S3P requirement, the CII Silver badge requires:

  *   Level 2: CII Silver badge, plus:
 *   All internal/external system communications shall be able to be 
encrypted.
 *   All internal/external service calls shall have common role-based 
access control and authorization with CADI

If I understand correctly, CADI is an SDK/framework from AAF. And integration 
with CADI needs AAF SDK which is only available with java binding, is that 
correct?

As you know some ONAP projects are python based and it is a great 
challenge/burden for us to develop a python based CADI SDK. So this could be a 
risk need TSC/Security subcommittee’s attention, especially in case that TSC 
makes it a mandatory requirement for Casablanca.

On the other hand, I am wondering what is the real intention with this security 
requirement. If the role-based access control is the key pursuit, then we 
should explore other alternatives.
Before diving into the specific alternatives, I would like touch a little bit 
the different requirements between a “Role” for end-user and “Role” for 
internal service entities.

  *   A role for end-user could be dynamically maintained/assigned since the 
end-users are created/deleted/updated during run-time. In that case some UI is 
needed and I guess this is what AAF/CADI is doing, correct?
  *   A role for service-entity is another story

Re: [onap-tsc][onap-discuss]Questions about Security Requirements for Casablanca: is CADI the only option to enable RBAC?

[Yang Bin]

Hi Srini,

   I believe for multicloud the access rules based on URI/HTTP 
header values are pretty enough. If ISTIO CA and RBAC could help that would be 
great relief.

Thanks for the comment.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Srini
Sent: Wednesday, June 27, 2018 5:45 PM
To: Stephen Terrill; Yang, Bin; onap-tsc; onap-sec...@lists.onap.org; GATHMAN, 
JONATHAN C
Cc: onap-disc...@lists.onap.org
Subject: Re: [onap-tsc][onap-discuss]Questions about Security Requirements for 
Casablanca: is CADI the only option to enable RBAC?

Hi Bin,

As Ramki mentioned in the wiki page, ISTIO CA and ISTIO RBAC may be good enough 
for Multi-Cloud.  But to be sure, it is good to know from Multi-Cloud team on 
what kind of APIs are present and what kind of restrictions the team thinks it 
should provide to various consumers of Multi-Cloud.   If the access rules are 
based on the URI & HTTP request header values, then ISTIO RBAC is good enough. 
But, if the access rules are based on HTTP body data, then you need to rethink 
about ISTIO RBAC or rethink about putting that data part of URI and HTTP 
request header.

Thanks
Srini




From: Yang, Bin mailto:bin.y...@windriver.com>>
Sent: Wednesday, June 27, 2018 5:57 AM
To: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: [onap-tsc][onap-discuss]Questions about Security Requirements for 
Casablanca: is CADI the only option to enable RBAC?

Dear TSC and Security Subcommittee,

As part of S3P requirement, the CII Silver badge requires:
*Level 2: CII Silver badge, plus:
-All internal/external system communications shall be able to be 
encrypted.
-All internal/external service calls shall have common role-based 
access control and authorization with CADI

If I understand correctly, CADI is an SDK/framework from AAF. And integration 
with CADI needs AAF SDK which is only available with java binding, is that 
correct?

As you know some ONAP projects are python based and it is a great 
challenge/burden for us to develop a python based CADI SDK. So this could be a 
risk need TSC/Security subcommittee's attention, especially in case that TSC 
makes it a mandatory requirement for Casablanca.

On the other hand, I am wondering what is the real intention with this security 
requirement. If the role-based access control is the key pursuit, then we 
should explore other alternatives.
Before diving into the specific alternatives, I would like touch a little bit 
the different requirements between a "Role" for end-user and "Role" for 
internal service entities.

  *   A role for end-user could be dynamically maintained/assigned since the 
end-users are created/deleted/updated during run-time. In that case some UI is 
needed and I guess this is what AAF/CADI is doing, correct?
  *   A role for service-entity is another story. The role for a service-entity 
should be designed at day 0 and configured during deployment time. And should 
be kept intact during the life cycle of the whole system (ONAP in this case). 
Hence there is no need to create/update/delete the role for a service-entity.

If my understanding/assumption is correct, I believe those services which does 
not expose API/UI to end-users should control the access based on the "role for 
service-entity" because their API consumers are service-entities, not end-users.
e.g. MultiCloud services's consumers are SO/VFC/APPC/etc. No end-user should 
access the MulitCloud APIs directly. Hence the access control based on the 
"role for service-entity" should be enough and will be provisioned during 
deployment.
In this case ISTIO's RBAC could be an alternative, which fullfil the 
requirement of RBAC, while offering following beneficts:
   1, leverage the ongoing effort with regarding to ISTIO for 
service mesh.
   2, Reuse the same infrastructure to fulfill requirement w.r.t. 
"All internal/external system communications shall be able to be encrypted"
3, OOM/Kubernetes based/managed, easy to configure/maintain.
   4, Projects are not impacted at all, no code change, no API 
change, etc. No SDK development/integration needed.


This is my 2 cents.  Please let me know if I got anything wrong/incomplete.

Thanks.


Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993



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

View/Reply Online (#3221): https://lists.onap.org/g/ONAP-TSC/message/3221
Mute This Topic: https://lists.onap.org/mt/22

[onap-tsc][onap-discuss]Questions about Security Requirements for Casablanca: is CADI the only option to enable RBAC?

[Yang Bin]

Dear TSC and Security Subcommittee,

As part of S3P requirement, the CII Silver badge requires:
*Level 2: CII Silver badge, plus:
-All internal/external system communications shall be able to be 
encrypted.
-All internal/external service calls shall have common role-based 
access control and authorization with CADI

If I understand correctly, CADI is an SDK/framework from AAF. And integration 
with CADI needs AAF SDK which is only available with java binding, is that 
correct?

As you know some ONAP projects are python based and it is a great 
challenge/burden for us to develop a python based CADI SDK. So this could be a 
risk need TSC/Security subcommittee's attention, especially in case that TSC 
makes it a mandatory requirement for Casablanca.

On the other hand, I am wondering what is the real intention with this security 
requirement. If the role-based access control is the key pursuit, then we 
should explore other alternatives.
Before diving into the specific alternatives, I would like touch a little bit 
the different requirements between a "Role" for end-user and "Role" for 
internal service entities.

*A role for end-user could be dynamically maintained/assigned since the 
end-users are created/deleted/updated during run-time. In that case some UI is 
needed and I guess this is what AAF/CADI is doing, correct?

*A role for service-entity is another story. The role for a 
service-entity should be designed at day 0 and configured during deployment 
time. And should be kept intact during the life cycle of the whole system (ONAP 
in this case). Hence there is no need to create/update/delete the role for a 
service-entity.

If my understanding/assumption is correct, I believe those services which does 
not expose API/UI to end-users should control the access based on the "role for 
service-entity" because their API consumers are service-entities, not end-users.
e.g. MultiCloud services's consumers are SO/VFC/APPC/etc. No end-user should 
access the MulitCloud APIs directly. Hence the access control based on the 
"role for service-entity" should be enough and will be provisioned during 
deployment.
In this case ISTIO's RBAC could be an alternative, which fullfil the 
requirement of RBAC, while offering following beneficts:
   1, leverage the ongoing effort with regarding to ISTIO for 
service mesh.
   2, Reuse the same infrastructure to fulfill requirement w.r.t. 
"All internal/external system communications shall be able to be encrypted"
3, OOM/Kubernetes based/managed, easy to configure/maintain.
   4, Projects are not impacted at all, no code change, no API 
change, etc. No SDK development/integration needed.


This is my 2 cents.  Please let me know if I got anything wrong/incomplete.

Thanks.


Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993


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

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

Re: [onap-tsc] [onap-discuss] Usecase subcommittee meeting on 11/06/2018: the agenda

[Yang, Bin]

Hi Alla,

   The wiki page is applied with restriction so that only program 
committee are allowed to edit, please help add the following link to the 
suecase subcommittee session, thanks.

https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement?preview=/33063881/33063934/ConsistentRepresentationAndIdentificationOfCloudRegion.pptx


Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Saturday, June 09, 2018 2:03 AM
To: onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc
Subject: [onap-discuss] Usecase subcommittee meeting on 11/06/2018: the agenda

Hi all,

Here is agenda for the upcoming meeting:


1.   Check whether all comments provided for CCVPN and Change management 
(incl. alignment with PNF support) were addressed ; in this case, endorse these 
use cases/functional requirements for Casablanca

1.   Preparation for f2f meeting in Beijing:

a.   We will review your presentations - each one should take apprx. 10 
minutes, the same one used for Casablanca's endorsement can be used (or 
modified to fit into time slot/to include most recent added details). Please 
put it under  
https://wiki.onap.org/display/DW/Casablanca+Release+Developers+Forum+Session+Proposals
 , Usecase subcommittee session


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D40174.8FC16F80]
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

[Yang, Bin]

Hi Dom,

   Appreciate your information and support on this proposal, sorry 
that I missed that and didn’t reach out to you for having your feedback. I will 
update my slides and wiki to reflect this important point.

Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: LUNANUOVA, DOMINIC (DOMINIC) [mailto:d...@research.att.com]
Sent: Monday, May 14, 2018 8:38 PM
To: Alla Goldner; Yang, Bin
Cc: onap-disc...@lists.onap.org; onap-usecase...@lists.onap.org; onap-tsc
Subject: RE: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Bin,
Another component that should align with the consistent representation of cloud 
regions is DMaaP.
Currently, we use an abstraction called “dcaeLocation”  as a handle for 
coordination of deployed DMaaP resources and DMaaP clients (pubishers and 
subscribers).  The base behavior supported results in DMaaP clients utilizing 
the “closest” DMaaP resource by referencing this common handle value.
To best align with your plan, I think we need to deprecate “dcaeLocation” and 
introduce “cloudRegion” (following AAI convention).
This would also emphasize that DMaaP can be used independent of DCAE.

-Dom

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Saturday, May 12, 2018 8:56 AM
To: Yang, Bin 
Cc: onap-disc...@lists.onap.org; onap-usecase...@lists.onap.org; onap-tsc 

Subject: Re: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Bin,
Yes, of course, Centralized Representation and Consistent Identification of 
Cloud Regions In ONAP was presented and discussed and can be brought for 
approval by the TSC. In this case, this is already generalized functional 
requirement, and, indeed, in a very good shape requirements and status wise, 
btw, also highly demanded by the Service Providers provided their opinions on 
priorities.

Please upload short description to 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+approval<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Casablanca-2Buse-2Bcases-2Bproposals-2Bfor-2Bapproval&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=TTiyLt3NmHhqJbSZsYv8tdAqTAgC-wtEx8NKq2P__08&m=2zds9XfwWJcy1aubzE9jbyhtY-LEPdKYAdcnjxvMIv4&s=ekId5B5GS2kvhQ8Kfg_pa6ilby_zm8xf0tP0NEZcpWU&e=>
 as soon as possible.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EBE3.C2E864F0]

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Saturday, May 12, 2018 3:32 PM
To: Alla Goldner mailto:alla.gold...@amdocs.com>>
Cc: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc mailto:onap-tsc@lists.onap.org>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: RE: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Alla,


   My proposal is “Centralized Representation and Consistent 
Identification of Cloud Regions In 
ONAP<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Centralized-2BRepresentation-2Band-2BConsistent-2BIdentification-2Bof-2BCloud-2BRegions-2BIn-2BONAP&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=TTiyLt3NmHhqJbSZsYv8tdAqTAgC-wtEx8NKq2P__08&m=2zds9XfwWJcy1aubzE9jbyhtY-LEPdKYAdcnjxvMIv4&s=XOosxB2tX2yHHy0-xVTUFx_OOctIVVAjwnDkHwsF4QE&e=>”,
 I presented during ONS usecase subcommittee session and I double check with 
all related PTLs after that, and got positive feedback to support that. I put 
the proposal at : 
https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Centralized-2BRepresentation-2Band-2BConsistent-2BIdentification-2Bof-2BCloud-2BRegions-2BIn-2BONAP&d=DwMFJg&c=LFYZ-o9_HUMeMTSQicvjIg&r=TTiyLt3NmHhqJbSZsYv8tdAqTAgC-wtEx8NKq2P__08&m=2zds9XfwWJcy1aubzE9jbyhtY-LEPdKYAdcnjxvMIv4&s=XOosxB2tX2yHHy0-xVTUFx_OOctIVVAjwnDkHwsF4QE&e=>

Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Alla Goldner [mailto:alla.gold...@amdocs.com]
Sent: Saturday, May 12, 2018 6:56 PM
To: Yang, Bin
Cc: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc; onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: RE: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Bin,

What is functional requirement you are talking about? Can you share more 
details?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EBE3.C2E864F0]

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Saturday, May 12, 2018 1:54 PM
To: 

Re: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

[Yang, Bin]

Thanks for the quick confirmation, I just upload the slides to that wiki page. 
Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Alla Goldner [mailto:alla.gold...@amdocs.com]
Sent: Saturday, May 12, 2018 8:56 PM
To: Yang, Bin
Cc: onap-usecase...@lists.onap.org; onap-tsc; onap-disc...@lists.onap.org
Subject: RE: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Bin,
Yes, of course, Centralized Representation and Consistent Identification of 
Cloud Regions In ONAP was presented and discussed and can be brought for 
approval by the TSC. In this case, this is already generalized functional 
requirement, and, indeed, in a very good shape requirements and status wise, 
btw, also highly demanded by the Service Providers provided their opinions on 
priorities.

Please upload short description to 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+approval as 
soon as possible.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EA46.20D6BA70]

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Saturday, May 12, 2018 3:32 PM
To: Alla Goldner 
Cc: onap-usecase...@lists.onap.org; onap-tsc ; 
onap-disc...@lists.onap.org
Subject: RE: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Alla,


   My proposal is “Centralized Representation and Consistent 
Identification of Cloud Regions In 
ONAP<https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP>”,
 I presented during ONS usecase subcommittee session and I double check with 
all related PTLs after that, and got positive feedback to support that. I put 
the proposal at : 
https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP

Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Alla Goldner [mailto:alla.gold...@amdocs.com]
Sent: Saturday, May 12, 2018 6:56 PM
To: Yang, Bin
Cc: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc; onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: RE: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Bin,

What is functional requirement you are talking about? Can you share more 
details?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EA46.20D6BA70]

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Saturday, May 12, 2018 1:54 PM
To: Alla Goldner mailto:alla.gold...@amdocs.com>>
Cc: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc mailto:onap-tsc@lists.onap.org>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: Re: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Alla,

What about functional requirement proposal?  Should we do the same for 
approval or having another session ?  Thanks

Bin

在 2018年5月12日，02:43，Alla Goldner 
mailto:alla.gold...@amdocs.com>> 写道：
Hi all,

Link to the use case proposals is here: 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+approval.



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, May 11, 2018 7:58 AM
To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc mailto:onap-tsc@lists.onap.org>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: [onap-discuss] e2e use cases for approval by the TSC

Hi all,

As we didn’t have any time left for use case discussion and approval during 
yesterday’s TSC meeting and likely will not have till the launch of Beijing due 
to urgent Beijing related discussions, the meeting decision was that we will 
host e2e use case approval discussions during Usecase subcommittee meetings on 
Monday, 4 pm CET.


1.   All use case authors �C please make sure you distributed your 
presentations for approval. So far, we’ve received 5G group, Edge Automation 
and auto Scaling out

2.   Kenny, as agreed, please make sure all PTLs aware the discussion will 
take place during Use case subcommittee meeting

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




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 st

Re: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

[Yang, Bin]

Hi Alla,


   My proposal is “Centralized Representation and Consistent 
Identification of Cloud Regions In 
ONAP<https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP>”,
 I presented during ONS usecase subcommittee session and I double check with 
all related PTLs after that, and got positive feedback to support that. I put 
the proposal at : 
https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP

Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Alla Goldner [mailto:alla.gold...@amdocs.com]
Sent: Saturday, May 12, 2018 6:56 PM
To: Yang, Bin
Cc: onap-usecase...@lists.onap.org; onap-tsc; onap-disc...@lists.onap.org
Subject: RE: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Bin,

What is functional requirement you are talking about? Can you share more 
details?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EA30.55E028C0]

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Saturday, May 12, 2018 1:54 PM
To: Alla Goldner 
Cc: onap-usecase...@lists.onap.org; onap-tsc ; 
onap-disc...@lists.onap.org
Subject: Re: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Alla,

What about functional requirement proposal?  Should we do the same for 
approval or having another session ?  Thanks

Bin

在 2018年5月12日，02:43，Alla Goldner 
mailto:alla.gold...@amdocs.com>> 写道：
Hi all,

Link to the use case proposals is here: 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+approval.



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, May 11, 2018 7:58 AM
To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc mailto:onap-tsc@lists.onap.org>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
Subject: [onap-discuss] e2e use cases for approval by the TSC

Hi all,

As we didn’t have any time left for use case discussion and approval during 
yesterday’s TSC meeting and likely will not have till the launch of Beijing due 
to urgent Beijing related discussions, the meeting decision was that we will 
host e2e use case approval discussions during Usecase subcommittee meetings on 
Monday, 4 pm CET.


1.   All use case authors �C please make sure you distributed your 
presentations for approval. So far, we’ve received 5G group, Edge Automation 
and auto Scaling out

2.   Kenny, as agreed, please make sure all PTLs aware the discussion will 
take place during Use case subcommittee meeting

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




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-TSC mailing list
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-tsc
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

[Yang, Bin]

Hi Alla,

What about functional requirement proposal?  Should we do the same for 
approval or having another session ?  Thanks

Bin

在 2018年5月12日，02:43，Alla Goldner 
mailto:alla.gold...@amdocs.com>> 写道：

Hi all,

Link to the use case proposals is here: 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+approval.



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, May 11, 2018 7:58 AM
To: onap-usecase...@lists.onap.org; 
onap-tsc mailto:onap-tsc@lists.onap.org>>; 
onap-disc...@lists.onap.org
Subject: [onap-discuss] e2e use cases for approval by the TSC

Hi all,

As we didn’t have any time left for use case discussion and approval during 
yesterday’s TSC meeting and likely will not have till the launch of Beijing due 
to urgent Beijing related discussions, the meeting decision was that we will 
host e2e use case approval discussions during Usecase subcommittee meetings on 
Monday, 4 pm CET.


1.   All use case authors �C please make sure you distributed your 
presentations for approval. So far, we’ve received 5G group, Edge Automation 
and auto Scaling out

2.   Kenny, as agreed, please make sure all PTLs aware the discussion will 
take place during Use case subcommittee meeting

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




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

Re: [onap-tsc] [tsc]Vote: ONAP Deployment Proposal for Amsterdam Release

[Yang, Bin]

Hi Roger,

   I observed that multicloud was marked as ‘Deployment Spec 
Complete” as well as ‘Container Up’.
Maybe I am out of conversation between you and Xinhui, and I am not sure if you 
knew that for R1, MultiCloud consists of 4 microservices, hence 4 containers: 
Multicloud broker, Multicloud plugin for OpenStack Ocata, Multicloud plugin for 
Mitaka (Wind River’s release), Multicloud plugin for VMware VIO.
I am not sure if all of them are deployed via OOM,  could you help check that? 
And if something were missing, could you do me a favor to add missing ones or 
let me know how I can help.

Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Roger Maitland
Sent: Monday, September 25, 2017 6:13 PM
To: Yunxia Chen; onap-tsc
Subject: Re: [onap-tsc] [tsc]Vote: ONAP Deployment Proposal for Amsterdam 
Release

Helen, the OOM status was not up to date on the page you listed (there are many 
status pages).  I’ve updated your page and created the following summary ( 
https://wiki.onap.org/display/DW/OOM+Deployment+Status ):
[cid:image001.png@01D335F4.1B1E76B0]

As mentioned by Yury and Borislav, the AAI configuration used by OOM has been 
validated by the AAI team.  If the VM deployment has these extra components you 
might want to confirm they are needed in a VM deployment.

We did see the change to dgbuilder and are adapting.

Although DCAE gen 1 isn’t officially part of the Amsterdam release the OOM has 
containerized DCAE gen 1 such that it can be used for ONAP validation while 
DCAE gen 2 is in development.

OOM has been able to pull in some of the Consul monitoring originally targeted 
at the Beijing release.  The Consul servers are up and the message router is 
reporting green so we have a good start.  Note that Consul monitoring is 
effectively a continuous health check that is visible in the Consul UI.

Cheers,
Roger

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Yunxia Chen
Sent: Friday, September 22, 2017 5:08 PM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] [tsc]Vote: ONAP Deployment Proposal for Amsterdam 
Release

The latest update for ONAP installation testing inside Integration Lab as of 
09/22, 2:30 PM EST, (the whole team works very fast ☺, that is very good!)

From the wiki below (which have code needed to be installed for Amsterdam 
release for our best knowledge), there are 17 (16 + ROBOT) (be careful, these 
are NOT all the project), namely: AAI, APPC, CLAMP, DCAE GEN2 + HOLMES, MESSAGE 
ROUTER (DMAAP), ROBOT, MSB, MULTI-VIM, UUI, POLICY, PORTAL, SDNC, SDC, SO, VFC, 
VID, VNFSDK.

https://wiki.onap.org/display/DW/ONAP+Installation+Strategy+for+Release+A

Projects currently in Heat: 16.
Projects currently in OOM: 14.

For Heat, all those OpenECOMP components have been tested for a while, any 
issues right now functionalities wise should not depend on the heat 
installation, while the test for OPEN-O components added recently is going on. 
The OPEN-O containers are all up, but we haven’t tested if they work as 
expected (have asked the teams to check, from my OPEN-O integration experience, 
I know it should be fine since it is almost exactly the same as before from env 
perspective)

We can’t tell about stability of installation via OOM, we noticed the following 
gaps in OOM though:

  *   Three AAI containers are missing, namely attos/dmaap, docker_file_kafka, 
wurstmeister_zookeeper. These containers are also in the Message Router 
component, so we don’t know if the OOM team redirected AAI to talk to that bus. 
If so, that should be fine;
  *   The dgbuilder image used in APPC and SDNC is old. That is no longer in 
use. There’s a new one called onap/ccsdk-dgbuilder-image/0.1-STAGING-latest;
  *   The configuration of DCAE GEN1 controller may be broken because it 
expects to create CDAP/Postgrees/Collector components, while in the OOM-based 
approach CDAP/Postgrees/Collector are created by OOM. This will not be an issue 
when DCAE GEN1 will be replaced with DCAE GEN2.

Marco and Yang, please add your comments since you are continuing testing them 
at this moment as well. (I am off heading to Paris)

Thank you and see you at Paris,

Helen Chen


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer

[onap-tsc] [onap-discuss] ONAP Project: Registration for May Developer Event

[Yang, Bin]

Dear Annie and TSC members,

   ONAP has been doing a very good job to automate the 
deployment/management of VNFs as well as the ONAP services themselves over the 
cloud, I think It is worth to think about how different versions of OpenStack 
as well as other vendors? VIMs(e.g. VMware VIO) could adapt to support ONAP as 
well as the VNFs. From this perspective, it might be reasonable to abstract the 
interfaces as well as the information models between ONAP service and the 
infrastructure to :
1, catalog the NFVI capabilities from the perspective of ONAP, so that VNF 
providers could make assumptions the runtime context while designing/developing 
VNFs.
2, Enable the ONAP certificate &  compliance tests of NFVI vendors/providers
3, Decouple ONAP from specific NFVI while making the possibility of ONAP to 
evolve to leverage new capabilities of NFVI, e.g. enabling  ONAP to utilize the 
EPA (Enhanced Platform Awareness) features that the NFVI offers for some 
performance critical VNFs .


I would like to propose to initiate the conversation on this topic on ONAP 
Developer Event. Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc-bounces at lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gadiyar, Rajesh
Sent: Wednesday, April 12, 2017 2:46 PM
To: Sauvageau, David; Annie Fisher; onap-tsc at lists.onap.org
Subject: Re: [onap-tsc] [onap-discuss] ONAP Project: Registration for May 
Developer Event

Architecture Deep Dive, Code Merge Strategy, Release Planning and some initial 
discussions on project proposals are all good topics for the May F2F.

However, if at all possible, I would like to request that we hold these 
sessions during the later part of that week (at least avoid Day 1). A few of us 
have conflicts during Day 1 due to commitments at the NFV Congress and will be 
able to make it to NJ mid-week.

Regards,
Rajesh

From: mailto:onap-tsc-bounces at 
lists.onap.org>> on behalf of "Sauvageau, David" mailto:david.sauvag...@bell.ca>>
Date: Tuesday, April 11, 2017 at 7:30 PM
To: Annie Fisher mailto:afisher at 
linuxfoundation.org>>, "onap-tsc at lists.onap.org" mailto:onap-tsc at lists.onap.org>>
Subject: Re: [onap-tsc] [onap-discuss] ONAP Project: Registration for May 
Developer Event

Hi Annie & TSC members,

I would like to propose some kind of a hackathon during the Developer event in 
order to really make it a developer-focused event.

I believe that architecture, code merger strategy and release planning is 
definitely required for that session but if we are to regroup 75-100 developers 
and architects together then we should probably leverage the opportunity to 
have them to start working together.

We could propose an agenda where day 1 is targeted for general audience in 
order to discuss high-level architecture, merging strategy, release planning 
etc, but maybe there could be a parallel track for a hackathon during days 2-3 
or something. We could even have limited ECOMP+Open-O integration POCs at the 
end of the event.

Thoughts?

From: mailto:onap-discuss-bounces at 
lists.onap.org>> on behalf of Annie Fisher mailto:afis...@linuxfoundation.org>>
Date: Monday, April 10, 2017 at 8:23 PM
To: "onap-tsc at lists.onap.org" mailto:onap-tsc at lists.onap.org>>, "onap-discuss at 
lists.onap.org" mailto:onap-discuss at lists.onap.org>>
Subject: [onap-discuss] ONAP Project: Registration for May Developer Event

[line image 1]

ONAP Project Developer Event
May 2 - 4, 2017
AT&T Labs Research, Middletown, NJ
Link to register:  https://www.regonline.com/ONAPDeveloper
Note: instructions for obtaining necessary visa letters as well at hotel 
information may be found by clicking this link.

Proposed Agenda/Subject Areas to be covered*:
Framework for code merger of Open-O and ECOMP code including:
- Agreement on Principles of merging the code
- Target applications to support in Release 1
- Consolidated Target Architecture of merged code for release 1
- Code modification & implementation methods for merging the code
- Other work to be done for first release
- Target date for first release
- Release cadence
.. *and more...


Annie Fisher, MPA CSM
Program Manager, The Linux Foundation
Location & Time-zone: San Francisco, CA, PST
web: https://www.linuxfoundation.org/
email: afisher at linuxfoundation.org
-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 45522 bytes
Desc: image001.png
URL: