[onap-tsc] ONAP TSC Chair Nominations 2019

[Kenny Paul]

Hello TSC Members,

 

As per last year's agreement
(https://wiki.onap.org/display/DW/TSC+2018-09-13)  the Chair and Vice-Chair
elections for the TSC will be conducted as sequential election events. This
email kicks off the TSC Chair election.

 

The nomination period will end on Wednesday, Nov. 27 @ 13:00 Pacific

--

Who is eligible to Run: TSC Members

Who is eligible to Vote: TSC Members

Process:

Self Nomination Phase
Individuals interested in running for the TSC Chair position must reply-all
to this email with your intention to run.  It is recommended that candidates
provide a statement of intent as to why you would be a good person to serve
as the ONAP TSC Chair.

*   The nomination phase begins with the receipt of the announcement (
as verified by checking the list in groups.io   )
*   The nomination phase ends Wednesday, Nov. 27 @ 13:00 Pacific

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

*   The election phase will begin on with the distribution of the CIVS
poll via email
*   The election phase will end four (4) full business days later in the
same time zone the poll was initiated from

 

 

Thanks!

-kenny

 


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

View/Reply Online (#5696): https://lists.onap.org/g/onap-tsc/message/5696
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] Reorg of subcommittee pages on ONAP Wiki?

[Alla Goldner]

+1

Sent from Nine

From: Kenny Paul 
Sent: Thursday, 21 November 2019 11:41
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Reorg of subcommittee pages on ONAP Wiki?

Hello everyone,

Currently all the subcommittee pages are direct children of the TSC page. To 
clean things up a bit I would like to realign the subcommittee landing pages 
under a parent subcommittee page.

Proposed structure:  TSC Home -> Subcommittee Home -> Subc-A, Subc-B, Subc-C, …

Thoughts?

Thanks!
-kenny


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 (#5695): https://lists.onap.org/g/onap-tsc/message/5695
Mute This Topic: https://lists.onap.org/mt/61117266/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] Reorg of subcommittee pages on ONAP Wiki?

[Amy Zwarico]

+1 to Kenny and Krzysztof

-Original Message-
From: onap-tsc@lists.onap.org  On Behalf Of Krzysztof 
Opasiak via Lists.Onap.Org
Sent: Thursday, November 21, 2019 2:32 PM
To: onap-tsc@lists.onap.org; Kenny Paul (kp...@linuxfoundation.org) 

Subject: Re: [onap-tsc] Reorg of subcommittee pages on ONAP Wiki?

Hi Kenny,

On 21.11.2019 20:40, Kenny Paul wrote:
> Hello everyone,
> 
> Currently all the subcommittee pages are direct children of the TSC 
> page. To clean things up a bit I would like to realign the 
> subcommittee landing pages under a parent subcommittee page.
> 
> Proposed structure:  TSC Home -> Subcommittee Home -> Subc-A, Subc-B, 
> Subc-C, .
> 
> Thoughts?

Sounds like a good idea as long as we don't break any links;)

--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics




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

View/Reply Online (#5694): https://lists.onap.org/g/onap-tsc/message/5694
Mute This Topic: https://lists.onap.org/mt/61117266/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] Reorg of subcommittee pages on ONAP Wiki?

[Krzysztof Opasiak via Lists.Onap.Org]

Hi Kenny,

On 21.11.2019 20:40, Kenny Paul wrote:

Hello everyone,

Currently all the subcommittee pages are direct children of the TSC 
page. To clean things up a bit I would like to realign the subcommittee 
landing pages under a parent subcommittee page.


Proposed structure:  TSC Home -> Subcommittee Home -> Subc-A, Subc-B, 
Subc-C, …


Thoughts?


Sounds like a good idea as long as we don't break any links;)

--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics

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

View/Reply Online (#5693): https://lists.onap.org/g/onap-tsc/message/5693
Mute This Topic: https://lists.onap.org/mt/61117266/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] Reorg of subcommittee pages on ONAP Wiki?

[Stephen Terrill via Lists.Onap.Org]

+1

From: onap-tsc@lists.onap.org  On Behalf Of Chaker 
Al-Hakim via Lists.Onap.Org
Sent: Thursday, 21 November 2019 20:50
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Reorg of subcommittee pages on ONAP Wiki?

Hi Kenny,

Even though I am no longer a member of the TSC  I do like your idea. In 
addition, and at the same level as the subcommittee  page, you may want to 
consider a place holders for "Task Force", "Special Projects", "TCC" , etc..

Regards,
Chaker


From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Kenny 
Paul via Lists.Onap.Org
Sent: Thursday, November 21, 2019 2:40 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Reorg of subcommittee pages on ONAP Wiki?

Hello everyone,

Currently all the subcommittee pages are direct children of the TSC page. To 
clean things up a bit I would like to realign the subcommittee landing pages 
under a parent subcommittee page.

Proposed structure:  TSC Home -> Subcommittee Home -> Subc-A, Subc-B, Subc-C, 
...

Thoughts?

Thanks!
-kenny



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

View/Reply Online (#5692): https://lists.onap.org/g/onap-tsc/message/5692
Mute This Topic: https://lists.onap.org/mt/61117266/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] Prague co-meeting with CNTT

[Stephen Terrill via Lists.Onap.Org]

Hi Jim,

It would be helpful if you could elaborate on what you saw as the most 
significant intersecting topics  as the term “solution deployment” is quite a 
large scope -  Actually – it would be great if there were suggestions from CNTT 
on the questions that have where ONAP could help – orchestration is clear – but 
beyond that it wasn’t obvious from the last joint meeting nor in the meeting 
planning , then I think the time allocation can be considered.

BR,

Steve



From: onap-tsc@lists.onap.org  On Behalf Of Jim Baker 
via Lists.Onap.Org
Sent: Thursday, 21 November 2019 20:29
To: onap-tsc 
Cc: Lincoln Lavoie ; Rabi, Abdel, Vodafone Group 
; COTTRELL, MARK ; BELTRAN, JONATHAN 
; TENNANT, RICK 
Subject: [onap-tsc] Prague co-meeting with CNTT

Greetings!
With the Prague f2f meeting looming, I wanted to reach out to the ONAP 
community and plan the CNTT interactions in Prague. We can allocate 2-3 hours 
of time to this collaboration if we can come up with an appropriate agenda. 
While CNTT is chartered to specify the Common NFVI, the CNTT community is 
concerned about the time to solution deployment - which includes VNFs and 
orchestrators. Since ONAP contributes to both VNF validation and orchestration, 
it would make sense to focus our attentions there...

Please respond to all on this email with your ideas for topics. Once I get a 
set of ideas, I'll consolidate and share back to you and offer up a discussion 
time (if needed) for the agenda planning. Please focus on discussion topics 
that need inputs/discussion, NOT on presentation that tend to be one-way 
conversations. Also, while I suggested an obvious area of interest, many other 
areas are fertile for topics: security, solution stack testing, etc. are all 
welcome!

LFN Developer and Testing Forums is the place where the community comes 
together and is one of the key benefits of LFN membership - let's make it 
count! ALL ideas are welcome - this is a community brain-storming session - so 
bring your ideas!
Kind regards,
Jim


--
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 (#5691): https://lists.onap.org/g/onap-tsc/message/5691
Mute This Topic: https://lists.onap.org/mt/61115299/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] Reorg of subcommittee pages on ONAP Wiki?

[Chaker Al-Hakim]

Hi Kenny,

Even though I am no longer a member of the TSC  I do like your idea. In 
addition, and at the same level as the subcommittee  page, you may want to 
consider a place holders for "Task Force", "Special Projects", "TCC" , etc..

Regards,
Chaker


From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul 
via Lists.Onap.Org
Sent: Thursday, November 21, 2019 2:40 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Reorg of subcommittee pages on ONAP Wiki?

Hello everyone,

Currently all the subcommittee pages are direct children of the TSC page. To 
clean things up a bit I would like to realign the subcommittee landing pages 
under a parent subcommittee page.

Proposed structure:  TSC Home -> Subcommittee Home -> Subc-A, Subc-B, Subc-C, 
...

Thoughts?

Thanks!
-kenny



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

View/Reply Online (#5690): https://lists.onap.org/g/onap-tsc/message/5690
Mute This Topic: https://lists.onap.org/mt/61117266/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] Reorg of subcommittee pages on ONAP Wiki?

[Kenny Paul]

Hello everyone,

 

Currently all the subcommittee pages are direct children of the TSC page. To
clean things up a bit I would like to realign the subcommittee landing pages
under a parent subcommittee page.

 

Proposed structure:  TSC Home -> Subcommittee Home -> Subc-A, Subc-B,
Subc-C, .

 

Thoughts?

 

Thanks!

-kenny

 


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

View/Reply Online (#5689): https://lists.onap.org/g/onap-tsc/message/5689
Mute This Topic: https://lists.onap.org/mt/61117266/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] Prague co-meeting with CNTT

[Jim Baker]

Greetings!
With the Prague f2f meeting looming, I wanted to reach out to the ONAP
community and plan the CNTT interactions in Prague. We can allocate 2-3
hours of time to this collaboration if we can come up with an appropriate
agenda. While CNTT is chartered to specify the Common NFVI, the CNTT
community is concerned about the time to *solution deployment* - which
includes VNFs and orchestrators. Since ONAP contributes to both VNF
validation and orchestration, it would make sense to focus our attentions
there...

Please respond to all on this email with your ideas for topics. Once I get
a set of ideas, I'll consolidate and share back to you and offer up a
discussion time (if needed) for the agenda planning. Please focus on
discussion topics that need inputs/discussion, NOT on presentation that
tend to be one-way conversations. Also, while I suggested an obvious area
of interest, many other areas are fertile for topics: security, solution
stack testing, etc. are all welcome!

LFN Developer and Testing Forums is the place where the community comes
together and is one of the key benefits of LFN membership - let's make it
count! ALL ideas are welcome - this is a community brain-storming session -
so bring your ideas!
Kind regards,
Jim


-- 
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 (#5688): https://lists.onap.org/g/onap-tsc/message/5688
Mute This Topic: https://lists.onap.org/mt/61115299/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [ONAP] [Integration] Request for 3 new repositories to manage baseline docker images

[Morgan Richomme via Lists.Onap.Org]

Hi XinHui

I open a new ticket for the creation of 3 new repositories aiming to
host Dockerfiles to build refeence docker images to be used as baseline
images (Alpine 11 + Java11 and Alpine11 + Python3) by the other ONAP
projects.
- integration/docker/onap-baseline
- integration/docker/onap-java11
- integration/docker/onap-python3.7 

https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-18325

Could you validate this request?

Regards

Morgan

NB: I did not find neither the infra-coordinator nor XinHui when
sharing the ticket. 


_

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

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


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

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

Re: [onap-tsc] SDC Committer Promotion Request

[Catherine LEFEVRE]

Thanks Oren - based on your feedback - I approve the request
Congratulations Ilana !

KR
catherine

From: Oren Kleks [mailto:oren.kl...@amdocs.com]
Sent: Thursday, November 21, 2019 3:30 PM
To: Lefevre, Catherine ; 
onap-tsc@lists.onap.org; infrastructure-coordina...@onap.org
Cc: Nachmias, Lior ; Ilana Paktor 

Subject: Re: [onap-tsc] SDC Committer Promotion Request

Catherine,

Einav Weiss Kedar is on a maternity leave.
The rest of the committers received at least two reminders regarding this poll.

Best Regards,
Oren


From: Lefevre, Catherine 
mailto:catherine.lefe...@intl.att.com>>
Sent: Thursday, November 21, 2019 2:00 PM
To: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>>; 
infrastructure-coordina...@onap.org 
mailto:infrastructure-coordina...@onap.org>>
Cc: Nachmias, Lior 
mailto:lior.nachm...@intl.att.com>>; Oren Kleks 
mailto:oren.kl...@amdocs.com>>; Ilana Paktor 
mailto:ilana.pak...@amdocs.com>>
Subject: RE: [onap-tsc] SDC Committer Promotion Request


Thank you Xinhui.

Although I do not deny the great contribution from Ilana.

Only 8 committers have voted and I see 10 SDC Committers in the list.

Do we know why we are missing two votes? Thanks



Can you also review logging and DCAE Committer's requests ? thanks.



Best regards

Catherine



From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Xinhui Li via Lists.Onap.Org
Sent: Wednesday, November 20, 2019 1:14 PM
To: onap-tsc@lists.onap.org; 
infrastructure-coordina...@onap.org
Cc: Nachmias, Lior 
mailto:lior.nachm...@intl.att.com>>; Oren Kleks 
mailto:oren.kl...@amdocs.com>>; Ilana Paktor 
mailto:ilana.pak...@amdocs.com>>
Subject: Re: [onap-tsc] SDC Committer Promotion Request



Thanks, The provided data is complete and accurate.



@TSC

Please review and raise your suggestion if any. I will follow up with LF 
accordingly.



XINHUI



From: mailto:onap-tsc@lists.onap.org>> on behalf of 
"Catherine LEFEVRE via Lists.Onap.Org" 
mailto:catherine.lefevre=intl.att@lists.onap.org>>
Reply-To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>
Date: Wednesday, November 20, 2019 at 5:55 PM
To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>, 
"infrastructure-coordina...@onap.org"
 
mailto:infrastructure-coordina...@onap.org>>
Cc: "Nachmias, Lior" 
mailto:lior.nachm...@intl.att.com>>, Oren Kleks 
mailto:oren.kl...@amdocs.com>>, Ilana Paktor 
mailto:ilana.pak...@amdocs.com>>
Subject: Re: [onap-tsc] SDC Committer Promotion Request



Add Xihui, our Infrastructure coordinator



From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Sonsino, Ofir
Sent: Wednesday, November 20, 2019 9:29 AM
To: onap-tsc@lists.onap.org
Cc: Nachmias, Lior 
mailto:lior.nachm...@intl.att.com>>; Oren Kleks 
mailto:oren.kl...@amdocs.com>>; Ilana Paktor 
mailto:ilana.pak...@amdocs.com>>
Subject: [onap-tsc] SDC Committer Promotion Request



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

Dear TSC,



I'd like to promote Ilana Paktor as a committer for SDC project.



Please find the relevant wiki page describing Ilana's contributions and 
background:

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

[onap-tsc] Frankfurt Project Status - M1 Complete

[Kenny Paul]

Today the TSC finalized their approval of the M1 milestone as complete for
the Frankfurt [1]

 

Projects meeting the M1 provisions

AAI, AAF, APPC, CLAMP, CCSDK, DCAE, DMaaP; ExtAPI, Integration,  Modeling,
MUSIC, MSB, MutliCloud, OOF, OOM, Policy, PORTAL, SNDC, SDC, SO, UUI, VF-C,
VID, VNFReqs, VVP, VNFSDK

 

Projects not meeting the M1 provisions:

CLI, HOLMES, LOGGING

 

[1] v.70 of Frankfurt Milestone Status
 

 

Thanks!

-kenny

 


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

View/Reply Online (#5685): https://lists.onap.org/g/onap-tsc/message/5685
Mute This Topic: https://lists.onap.org/mt/61093692/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] Lab closure clarification

[Pamela Dragosh]

+1 to move the date to Jan 21. The arch review takes time for projects to 
prepare, especially if they have changes. Lab closure makes it tough to 
pairwise test, as some teams may be ready to do so at that time.

Pam

From:  on behalf of "Stephen Terrill via 
Lists.Onap.Org" 
Reply-To: "onap-tsc@lists.onap.org" 
Date: Thursday, November 21, 2019 at 10:32 AM
To: "onap-tsc@lists.onap.org" 
Subject: Re: [onap-tsc] Lab closure clarification

Hi David,

I think it will help ( - certainly Jan 9th seems very challenging); and it 
depends on the community as well – additional meetings can be called – I want 
to highlight it for the overall planning; previously we did about 4 projects a 
meeting (1/2 hour each) – meaning about 7-8 meetings worth.  I wanted to 
highlight that now so that I don’t get to the start the start of January and 
try to review everything in one week.

BR,

Steve

From: onap-tsc@lists.onap.org  On Behalf Of David 
McBride via Lists.Onap.Org
Sent: Thursday, 21 November 2019 15:05
To: onap-tsc 
Subject: Re: [onap-tsc] Lab closure clarification

Thanks, Steve.

Are you saying that the proposed schedule change to Jan 21 will not allow 
enough time for the project level arch review? Please advise.

David

On Wed, Nov 20, 2019 at 2:19 PM Stephen Terrill via 
Lists.Onap.Org
 
mailto:ericsson@lists.onap.org>>
 wrote:
Hi David,

Not on the topic of the lab closure – but on the topic of the M2/M3 milestone- 
One thing to keep in mind – for M2/M3 there should be a project level 
architecture review.  This time I would like to see that we approve the 
architecture description for each project in the project architecture review – 
the update of these 
(https://wiki.onap.org/display/DW/ONAP+Architecture+Component+Description+-+Frankfurt)
 – I will send out instructions.  I can only assume that it will take a few 
weeks to process the review.

Best Regards,

Steve.

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of David 
McBride via 
Lists.Onap.Org
Sent: Friday, 15 November 2019 23:46
To: onap-tsc mailto:onap-tsc@lists.onap.org>>; Brian 
Freeman mailto:bf1...@att.com>>
Subject: Re: [onap-tsc] Lab closure clarification

Brian,

Yes, I agree.

Please excuse my ignorance as I climb the learning curve with ONAP, but could 
you explain in more detail specifically what functionality is being lost during 
the move?  Thanks.

David

On Fri, Nov 15, 2019 at 11:39 AM Brian Freeman 
mailto:bf1...@att.com>> wrote:
Yipan,

Staring on Jan 6th seems like a very reasonable start date. We would plan for a 
week as you suggest just in case.
I assume all the data will be preserved (cinder volumes, vm’s and stacks etc) ?
Will we need to help gracefully shutdown things in advance ?

Probably need to have a planning session on anything we can do to help ensure 
success as tenants :)

David,

We need to make sure that M2/M3 is after Jan 14th . Right now per 
https://wiki.onap.org/display/DW/Release+Planning%3A++Frankfurt
 I think its January 9th.

Brian




From: onap-tsc@lists.onap.org

答复: [onap-tsc] Committer Promotion Request for [usecase-ui]

[Shen Tao]

Dear Catherine

 

I’ve updated wiki page about UUI resources.

Tomorrow I’ll modify committer list for UUI repositories.

 

Best regards,

Tao

 

 

发件人: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] 代表
Catherine LEFEVRE
发送时间: 2019年11月15日 18:21
收件人: onap-tsc@lists.onap.org; shentao; 'David McBride'
抄送: '徐冉（研究院）'
主题: Re: [onap-tsc] Committer Promotion Request for [usecase-ui]

 

Good morning Tao,

 

Based on the fact that both Amichai and Xin Jin are no more active
contributor.

I approve your committer request.

Please do not forget to update the wiki page accordingly �C thanks

https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepo
sitories-UsecaseUI
 

 

Congratulations Ran Xu !

 

Best regards

Catherine

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of
Lefevre, Catherine
Sent: Thursday, November 14, 2019 11:43 PM
To: shentao ; 'David McBride'
; onap-tsc@lists.onap.org
Cc: '徐冉（研究院）' 
Subject: Re: [onap-tsc] Committer Promotion Request for [usecase-ui]

 

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

Good morning Tao,

 

My apologies for the delayed response.

 

I have reviewed your request.

 

Looking at the following wiki page, I have noticed that Amichai, Xin Jin are
also committers but did not vote.

https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepo
sitories-UsecaseUI
 

 

Are they still contributing to your projects? I do not think Amichai does
but what about Xin Jin?

If Xin Jin is still an active committer then can you ask Xin Jin to vote?

 

Many thanks & regards

Catherine

 

From: shentao [mailto:shen...@chinamobile.com] 
Sent: Wednesday, November 06, 2019 5:30 AM
To: 'David McBride' ; Lefevre, Catherine
; onap-tsc@lists.onap.org
Cc: '徐冉（研究院）' 
Subject: Committer Promotion Request for [usecase-ui]

 

Dear TSC,

 

The usecase-ui team would like to promote Ran Xu as a new committer.

The supporting page can be found:
https://wiki.onap.org/display/DW/New+Committer+Promotion+Request
 

 

Best regards,

Tao

 

 

-

沈涛

中国移动通信有限公司研究院--人工智能和智慧运营研发中心

中国北京市西城区宣武门西大街32号（100053）

 

Shen Tao

China Mobile Research Institute

No.32 Xuanwumen west street,Xicheng District, Beijing 100053, China

 

Tel: +86 15801696688-34070

Mobile: +86 13521591389

Email:  shen...@chinamobile.com

-

 




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

View/Reply Online (#5683): https://lists.onap.org/g/onap-tsc/message/5683
Mute This Topic: https://lists.onap.org/mt/61080323/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] Lab closure clarification

[Stephen Terrill via Lists.Onap.Org]

Hi David,

I think it will help ( - certainly Jan 9th seems very challenging); and it 
depends on the community as well – additional meetings can be called – I want 
to highlight it for the overall planning; previously we did about 4 projects a 
meeting (1/2 hour each) – meaning about 7-8 meetings worth.  I wanted to 
highlight that now so that I don’t get to the start the start of January and 
try to review everything in one week.

BR,

Steve

From: onap-tsc@lists.onap.org  On Behalf Of David 
McBride via Lists.Onap.Org
Sent: Thursday, 21 November 2019 15:05
To: onap-tsc 
Subject: Re: [onap-tsc] Lab closure clarification

Thanks, Steve.

Are you saying that the proposed schedule change to Jan 21 will not allow 
enough time for the project level arch review? Please advise.

David

On Wed, Nov 20, 2019 at 2:19 PM Stephen Terrill via 
Lists.Onap.Org
 
mailto:ericsson@lists.onap.org>>
 wrote:
Hi David,

Not on the topic of the lab closure – but on the topic of the M2/M3 milestone- 
One thing to keep in mind – for M2/M3 there should be a project level 
architecture review.  This time I would like to see that we approve the 
architecture description for each project in the project architecture review – 
the update of these 
(https://wiki.onap.org/display/DW/ONAP+Architecture+Component+Description+-+Frankfurt)
 – I will send out instructions.  I can only assume that it will take a few 
weeks to process the review.

Best Regards,

Steve.

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of David 
McBride via 
Lists.Onap.Org
Sent: Friday, 15 November 2019 23:46
To: onap-tsc mailto:onap-tsc@lists.onap.org>>; Brian 
Freeman mailto:bf1...@att.com>>
Subject: Re: [onap-tsc] Lab closure clarification

Brian,

Yes, I agree.

Please excuse my ignorance as I climb the learning curve with ONAP, but could 
you explain in more detail specifically what functionality is being lost during 
the move?  Thanks.

David

On Fri, Nov 15, 2019 at 11:39 AM Brian Freeman 
mailto:bf1...@att.com>> wrote:
Yipan,

Staring on Jan 6th seems like a very reasonable start date. We would plan for a 
week as you suggest just in case.
I assume all the data will be preserved (cinder volumes, vm’s and stacks etc) ?
Will we need to help gracefully shutdown things in advance ?

Probably need to have a planning session on anything we can do to help ensure 
success as tenants :)

David,

We need to make sure that M2/M3 is after Jan 14th . Right now per 
https://wiki.onap.org/display/DW/Release+Planning%3A++Frankfurt
 I think its January 9th.

Brian




From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Yipan 
Deng
Sent: Friday, November 15, 2019 2:17 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Lab closure clarification

Hi David & TSC,

For Intel/Windriver Integration Lab located at Intel campus in Oregon, 
currently we are looking at moving the physical Lab starting from Jan. 6th, 
2020 for about a week (or shorter). During that period of time, there won’t be 
any remote access to the lab.

We tentatively shooting for this window considering the New Year holiday impact 
and believed this might create the least disruption to the ONAP community. 
Please feel free to let us know if you have different opinion and we are open 
for community feedbacks on lab move window.

Thanks,
Yipan
Intel ONAP/Akraino PM

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of David 
McBride
Sent: Friday, November 15, 2019 9:05 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Lab closure clarification

Who can provide detailed input about these events?

For both, we need to know:

  *   Start date
  *   Duration
  *   Degree of confidence in timing
  *   Scope of impact
David

On Thu, Nov 14, 2019 at 11:06 AM Brian Freeman 
mailto:bf1...@att.com>> wrote:
Two different events but need to undertand the timing with the latest Frankfurt 
schedule to assess impact.

Brian


From: onap-tsc@lists.onap.org 
mailto:

Re: [onap-tsc] Lab closure clarification

[David McBride]

Thanks, Steve.

Are you saying that the proposed schedule change to Jan 21 will not allow
enough time for the project level arch review? Please advise.

David

On Wed, Nov 20, 2019 at 2:19 PM Stephen Terrill via Lists.Onap.Org
 wrote:

> Hi David,
>
>
>
> Not on the topic of the lab closure – but on the topic of the M2/M3
> milestone- One thing to keep in mind – for M2/M3 there should be a project
> level architecture review.  This time I would like to see that we approve
> the architecture description for each project in the project architecture
> review – the update of these (
> https://wiki.onap.org/display/DW/ONAP+Architecture+Component+Description+-+Frankfurt)
> – I will send out instructions.  I can only assume that it will take a few
> weeks to process the review.
>
>
>
> Best Regards,
>
>
>
> Steve.
>
>
>
> *From:* onap-tsc@lists.onap.org  *On Behalf Of *David
> McBride via Lists.Onap.Org
> *Sent:* Friday, 15 November 2019 23:46
> *To:* onap-tsc ; Brian Freeman 
> *Subject:* Re: [onap-tsc] Lab closure clarification
>
>
>
> Brian,
>
>
>
> Yes, I agree.
>
>
>
> Please excuse my ignorance as I climb the learning curve with ONAP, but
> could you explain in more detail specifically what functionality is being
> lost during the move?  Thanks.
>
>
>
> David
>
>
>
> On Fri, Nov 15, 2019 at 11:39 AM Brian Freeman  wrote:
>
> Yipan,
>
>
>
> Staring on Jan 6th seems like a very reasonable start date. We would plan
> for a week as you suggest just in case.
>
> I assume all the data will be preserved (cinder volumes, vm’s and stacks
> etc) ?
>
> Will we need to help gracefully shutdown things in advance ?
>
>
>
> Probably need to have a planning session on anything we can do to help
> ensure success as tenants :)
>
>
>
> David,
>
>
>
> We need to make sure that M2/M3 is after Jan 14th . Right now per
> https://wiki.onap.org/display/DW/Release+Planning%3A++Frankfurt
> 
> I think its January 9th.
>
>
>
> Brian
>
>
>
>
>
>
>
>
>
> *From:* onap-tsc@lists.onap.org  *On Behalf Of *Yipan
> Deng
> *Sent:* Friday, November 15, 2019 2:17 PM
> *To:* onap-tsc@lists.onap.org
> *Subject:* Re: [onap-tsc] Lab closure clarification
>
>
>
> Hi David & TSC,
>
>
>
> For Intel/Windriver Integration Lab located at Intel campus in Oregon,
> currently we are looking at moving the physical Lab starting from Jan. 6th,
> 2020 for about a week (or shorter). During that period of time, there won’t
> be any remote access to the lab.
>
>
>
> We tentatively shooting for this window considering the New Year holiday
> impact and believed this might create the least disruption to the ONAP
> community. Please feel free to let us know if you have different opinion
> and we are open for community feedbacks on lab move window.
>
>
>
> Thanks,
>
> Yipan
>
> Intel ONAP/Akraino PM
>
>
>
> *From:* onap-tsc@lists.onap.org  *On Behalf Of *David
> McBride
> *Sent:* Friday, November 15, 2019 9:05 AM
> *To:* onap-tsc 
> *Subject:* Re: [onap-tsc] Lab closure clarification
>
>
>
> Who can provide detailed input about these events?
>
>
>
> For both, we need to know:
>
>- Start date
>- Duration
>- Degree of confidence in timing
>- Scope of impact
>
> David
>
>
>
> On Thu, Nov 14, 2019 at 11:06 AM Brian Freeman  wrote:
>
> Two different events but need to undertand the timing with the latest
> Frankfurt schedule to assess impact.
>
>
>
> Brian
>
>
>
>
>
> *From:* onap-tsc@lists.onap.org  *On Behalf Of *Kenny
> Paul
> *Sent:* Thursday, November 14, 2019 2:02 PM
> *To:* onap-tsc@lists.onap.org
> *Subject:* [onap-tsc] Lab closure clarification
>
>
>
> From the minutes today Srini brought up the Intel lab closure in January.
>
> Brian asked a schedule question resulting from the Windriver lab closure.
>
>
>
> In this context, one in the same or 2 different events?
>
>
>
> Thanks!
>
> -kenny
>
>
>
>
>
>
> --
>
> *David McBride*
>
> Release Manager
>
> Linux Foundation Networking (LFN)
>
> Mobile: +1.805.276.8018
>
> Email/Google Talk: dmcbr...@linuxfoundation.org
>
> IRC: dmcbride
>
>
>
>
> --
>
> *David McBride*
>
> Release Manager
>
> Linux Foundation Networking (LFN)
>
> Mobile: +1.805.276.8018
>
> Email/Google Talk: dmcbr...@linuxfoundation.org
>
> IRC: dmcbride
>
> 
>
>

-- 
*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 (#5681): https://lists.onap.org/g/onap-tsc/message/5681
Mute This Topic: https://lists.onap.org/mt/57995264/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 Election Results

[Milind Jalwadi]

Dear TSC members,

I would like to sincerely thank you all for your support. Heartiest 
Congratulations and best wishes to the new TSC!

I echo what Catherine has said that we all need to ensure ONAP becomes a 
reference implementation for SDN / NFV. Our ONAP engagement and contribution 
shall continue with this objective.

Best Wishes once again to the entire TSC team.

Thanks,
Milind

From: onap-tsc@lists.onap.org  On Behalf Of Catherine 
LEFEVRE via Lists.Onap.Org
Sent: Thursday, November 21, 2019 3:23 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] ONAP TSC Election Results

Dear ONAP Community,

I would like to thank again the TSC members who are departing Stephen Terrill, 
Chaker Al-Hakim, Milind Jawaldi and Yan Chen.
I hope you will continue to remain engaged as contributing members in ONAP.

For the new TSC members - Ciaran Johnson, Ranny Haiby, Seshu Kumar and ZongHe 
Huang - Welcome on Board !
I would like to extend my congratulations for being elected to serve.
The Community relies on us to ensure that ONAP will continue to be the 
reference automation platform for Software Defined Network.

Best regards
Catherine

From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Kenny Paul
Sent: Wednesday, November 20, 2019 7:12 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ONAP TSC Election Results

(bcc'd to onap-discuss)

I am pleased to announce the results of the ONAP Technical Steering Committee 
election.

As a reminder to all, here is what the TSC is responsible for all technical 
oversight of the open source Project as per the Technical Charter of  ONAP 
Project a Series of LF Projects, LLC. This includes:

* Coordinating the technical direction of the Project

* Approving project or system proposals (including, but not limited to, 
incubation, deprecation, and changes to scope)

* Organizing sub-projects and removing projects

* Creating sub-committees or working groups to focus on cross-project 
technical issues and requirements

* Appointing representatives to work with other open source or open 
standards communities

* Establishing community norms, workflows, issuing releases, and 
security issue reporting policies

* Establishing, maintaining and modifying policies to ensure the 
integrity, vetting and security of the ONAP Project code base

* Approving and implementing policies and processes for contributing 
code and coordinating with the Series Manager to resolve matters that may arise

* Discussing, seeking consensus, and where necessary, voting on 
technical matters relating to the code base that affect multiple projects

* Coordinating any marketing, events, or communications regarding the 
Project with the LF Projects Manager or their designee

* Establishing work flow procedures for the submission, approval, and 
closure/archiving of projects

* Setting requirements for the promotion of Contributors to Committer 
status, as applicable

* Amending, adjusting, refining and/or eliminating the roles of 
Contributors/Committers, and create new roles, and publicly document any roles

* Establishing the size, makeup and procedure for determining voting 
members of the TSC


Section 4.3 of the ONAP Technical Community Document also highlights the 
following in the context of the Technical Charter:

  *   Defining ONAP's release vehicles (such as a Coordinated Release) that 
align with the Project' mission,
  *   Fostering cross-project collaboration,
  *   Serving as ONAP's primary technical liaison body with other consortiums 
and groups,
  *   Developing an architecture,
  *   Setting simultaneous release dates,
  *   Defining release quality standards,
  *   Defining technical best practices and community norms (including the 
establishment and maintenance of a Development Process),
  *   Monitoring technical progress,
  *   Mediating technical conflicts between Committers and PTLs,
  *   Organizing inter-project collaboration,
  *   Coordinating technical community engagement with the end-user community.

The new membership is effective immediately.
Alphabetical by Name.  Reserved seats in Bold

Alexis de Talhouet
Bell Canada
Alla Goldner
Amdocs
Andreas Geissler
Deutsche Telekom
Bin Yang
Windriver
Catherine Lefevre
AT&T
 Ciaran Johnston
Ericsson
Davide Cherubini
Vodafone
Eric Debeau
Orange
Jason Hunt
IBM
Lingli Deng
China Mobile
Murat Turpcu
Turk Telekom
Ning So
Reliance Jio
Ranny Haiby
Samsung
Seshu Kumar
Huawei
Srini Addepalli
Intel
Timo Perala
Nokia
Viswa Kumar Skand Priya
Verizon
ZongHe Huang
China Telecom

Official results: 
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_fd493be64cce6c89

Re: [onap-tsc] SDC Committer Promotion Request

[Catherine LEFEVRE]

Thank you Xinhui.
Although I do not deny the great contribution from Ilana.
Only 8 committers have voted and I see 10 SDC Committers in the list.
Do we know why we are missing two votes? Thanks

Can you also review logging and DCAE Committer’s requests ? thanks.

Best regards
Catherine

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Xinhui Li via Lists.Onap.Org
Sent: Wednesday, November 20, 2019 1:14 PM
To: onap-tsc@lists.onap.org; infrastructure-coordina...@onap.org
Cc: Nachmias, Lior ; Oren Kleks 
; Ilana Paktor 
Subject: Re: [onap-tsc] SDC Committer Promotion Request

Thanks, The provided data is complete and accurate.

@TSC
Please review and raise your suggestion if any. I will follow up with LF 
accordingly.

XINHUI

From: mailto:onap-tsc@lists.onap.org>> on behalf of 
"Catherine LEFEVRE via Lists.Onap.Org" 
mailto:catherine.lefevre=intl.att@lists.onap.org>>
Reply-To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>
Date: Wednesday, November 20, 2019 at 5:55 PM
To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>, 
"infrastructure-coordina...@onap.org"
 
mailto:infrastructure-coordina...@onap.org>>
Cc: "Nachmias, Lior" 
mailto:lior.nachm...@intl.att.com>>, Oren Kleks 
mailto:oren.kl...@amdocs.com>>, Ilana Paktor 
mailto:ilana.pak...@amdocs.com>>
Subject: Re: [onap-tsc] SDC Committer Promotion Request

Add Xihui, our Infrastructure coordinator

From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Sonsino, Ofir
Sent: Wednesday, November 20, 2019 9:29 AM
To: onap-tsc@lists.onap.org
Cc: Nachmias, Lior 
mailto:lior.nachm...@intl.att.com>>; Oren Kleks 
mailto:oren.kl...@amdocs.com>>; Ilana Paktor 
mailto:ilana.pak...@amdocs.com>>
Subject: [onap-tsc] SDC Committer Promotion Request

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

I’d like to promote Ilana Paktor as a committer for SDC project.

Please find the relevant wiki page describing Ilana’s contributions and 
background:
https://wiki.onap.org/pages/viewpage.action?pageId=71838001
As well as SDC existing committers votes for Ilana:
https://www.surveymonkey.com/results/SM-7VYBB7YW7/

Thanks,
Ofir


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

View/Reply Online (#5679): https://lists.onap.org/g/onap-tsc/message/5679
Mute This Topic: https://lists.onap.org/mt/60777589/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] TSC Meetings - Monthly Update and Agenda (Nov 21st) #tsc

[Catherine LEFEVRE]

Dear ONAP Community,

It has been a long time since we published our ONAP TSC News.
Here we go ...

Key Highlights
•   New ONAP TSC
o   Thank you to our departed TSC Members - Stephen Terrill, Chaker 
Al-Hakim, Milind Jawaldi and Yan Chen
o   Welcome to Ciaran Johnson, Ranny Haiby, Seshu Kumar and ZongHe Huang
•   Congratulations to Pam Dragosh – re-elected Control Loop Subcommittee 
Chair
•   Congratulations to our new committers Ran Xu (UUI) Arthur 
Martella (OOF) and Kevin 
Smokowski , KAPIL 
SINGAL (CCSDK)
•   El-Alto release was publicly launched on October 31st, 2019 - 
https://www.onap.org/software - Way to Go ONAP Community !
•   Frankfurt Release Status
o   All projects listed in green on (v. 58) of Frankfurt Milestone 
Status are 
approved for M1 (i.e AAI, AAF, APPC, CLAMP, CCSDK, DCAE, DMaaP; ExtAPI, 
Integration, Modeling, MUSIC, MSB, MutliCloud, OOM, Policy, SNDC, SDC, SO, 
VF-C, VID, VNFReqs, VVP, VNFSDK )
o   TSC approves the NO GO as documented in (v. 63) of Frankfurt Milestone 
Status (i.e. NO 
GO- no impact on use cases/requirements: CLI, HOLMES, LOGGING => Re-use El Alto 
containers except if any blocking issue are identified during the Frankfurt 
testing cycle by the Integration Team. Any other finding (security, 
non-blocking issue) should be documented in the Frankfurt Release Note)
•   TSC approved
o   the Proposal for PNF software version in PNF upgrade in Frankfurt 
release
o   the POC definition - https://lists.onap.org/g/onap-tsc-vote/message/1242
o   the Frankfurt prioritization - Frankfurt Release 
Requirements
o   the Milestone Exception Process  - 
https://lists.onap.org/g/onap-tsc/message/5592
o   Implementing the Milestone Exception Process beginning with Frankfurt 
M2  https://lists.onap.org/g/onap-tsc-vote/message/1298
•   TSC Meeting will be canceled on Nov 28th, 2019
•   Linux Foundation office holiday closures from Nov 28th through Nov 
29th, 2019
•   CSIT jjb cleaning planned on December 3rd, 2019

Here are the Urgent Tasks to be completed within the next 2-3 weeks:
•   El Alto Retrospective – Task Lead: David McBride
•   Architecture Chair Election – Task Lead: Kenny Paul
•   Security Release Assessment Proposal – Task Lead: Pawel Pawlak
•   TSC Chair Election – Task Lead: Kenny Paul
•   TSC Vote on Use Cases Subcommittee Evolution – Task Lead: Catherine 
Lefèvre
•   TSC Vote on the Project/Component Lifecycle 
Discussion
 with the TAC Team – Task Lead: Catherine Lefèvre
•   TSC Vote on El-Alto Community Awards proposal – Task Lead: Catherine 
Lefèvre

Our latest TSC Meeting Notes have been posted:
•   10/24: https://wiki.onap.org/display/DW/TSC+2019-10-24 including latest 
Edge Update
•   10/31: https://wiki.onap.org/display/DW/TSC+2019-10-31 including latest 
3GPP ORAN Update
•   11/7: https://wiki.onap.org/display/DW/TSC+2019-11-07
•   11/14: https://wiki.onap.org/display/DW/TSC+2019-11-14
Next TSC Call
The next TSC agenda has been reviewed on Wednesday, Nov 20th, 2019 - 
https://wiki.onap.org/display/DW/TSC+2019-11-21
Major topics:
o   Welcome our elected TSC Members
o   TCC Generic Network Management Update
o   Frankfurt M1 Follow-up
o   TAC/LFN Board Update
TSC Calendar
https://lists.onap.org/g/onap-tsc/calendar

2019 TSC Decisions
https://wiki.onap.org/display/DW/2019+TSC+Decisions

TSC Dashboard:
https://jira.onap.org/secure/RapidBoard.jspa?projectKey=TSC&rapidView=163

TSC Chat
https://lists.onap.org/g/onap-tsc/chats

Upcoming Event(s):
•   TSC Meetings will be canceled on Dec 25th, 2019 and Jan 1st, 2020
•   Linux Foundation office holiday closures from Dec. 23rd through Jan 
3rd, 2020
•   ONAP/CNTT F2F Event in January 13-16th, 2020
o   Registration 
https://events19.linuxfoundation.org/events/lf-net

Re: [onap-tsc] ONAP TSC Election Results

[Catherine LEFEVRE]

Dear ONAP Community,

I would like to thank again the TSC members who are departing Stephen Terrill, 
Chaker Al-Hakim, Milind Jawaldi and Yan Chen.
I hope you will continue to remain engaged as contributing members in ONAP.

For the new TSC members - Ciaran Johnson, Ranny Haiby, Seshu Kumar and ZongHe 
Huang - Welcome on Board !
I would like to extend my congratulations for being elected to serve.
The Community relies on us to ensure that ONAP will continue to be the 
reference automation platform for Software Defined Network.

Best regards
Catherine

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Wednesday, November 20, 2019 7:12 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ONAP TSC Election Results

(bcc'd to onap-discuss)

I am pleased to announce the results of the ONAP Technical Steering Committee 
election.

As a reminder to all, here is what the TSC is responsible for all technical 
oversight of the open source Project as per the Technical Charter of  ONAP 
Project a Series of LF Projects, LLC. This includes:

*Coordinating the technical direction of the Project

*Approving project or system proposals (including, but not limited to, 
incubation, deprecation, and changes to scope)

*Organizing sub-projects and removing projects

*Creating sub-committees or working groups to focus on cross-project 
technical issues and requirements

*Appointing representatives to work with other open source or open 
standards communities

*Establishing community norms, workflows, issuing releases, and 
security issue reporting policies

*Establishing, maintaining and modifying policies to ensure the 
integrity, vetting and security of the ONAP Project code base

*Approving and implementing policies and processes for contributing 
code and coordinating with the Series Manager to resolve matters that may arise

*Discussing, seeking consensus, and where necessary, voting on 
technical matters relating to the code base that affect multiple projects

*Coordinating any marketing, events, or communications regarding the 
Project with the LF Projects Manager or their designee

*Establishing work flow procedures for the submission, approval, and 
closure/archiving of projects

*Setting requirements for the promotion of Contributors to Committer 
status, as applicable

*Amending, adjusting, refining and/or eliminating the roles of 
Contributors/Committers, and create new roles, and publicly document any roles

*Establishing the size, makeup and procedure for determining voting 
members of the TSC


Section 4.3 of the ONAP Technical Community Document also highlights the 
following in the context of the Technical Charter:

  *   Defining ONAP's release vehicles (such as a Coordinated Release) that 
align with the Project' mission,
  *   Fostering cross-project collaboration,
  *   Serving as ONAP's primary technical liaison body with other consortiums 
and groups,
  *   Developing an architecture,
  *   Setting simultaneous release dates,
  *   Defining release quality standards,
  *   Defining technical best practices and community norms (including the 
establishment and maintenance of a Development Process),
  *   Monitoring technical progress,
  *   Mediating technical conflicts between Committers and PTLs,
  *   Organizing inter-project collaboration,
  *   Coordinating technical community engagement with the end-user community.

The new membership is effective immediately.
Alphabetical by Name.  Reserved seats in Bold

Alexis de Talhouet

Bell Canada

Alla Goldner

Amdocs

Andreas Geissler

Deutsche Telekom

Bin Yang

Windriver

Catherine Lefevre

AT&T

 Ciaran Johnston

Ericsson

Davide Cherubini

Vodafone

Eric Debeau

Orange

Jason Hunt

IBM

Lingli Deng

China Mobile

Murat Turpcu

Turk Telekom

Ning So

Reliance Jio

Ranny Haiby

Samsung

Seshu Kumar

Huawei

Srini Addepalli

Intel

Timo Perala

Nokia

Viswa Kumar Skand Priya

Verizon

ZongHe Huang

China Telecom


Official results: 
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_fd493be64cce6c89


Thanks!
-kenny



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

View/Reply Online (#5677): https://lists.onap.org/g/onap-tsc/message/5677
Mute This Topic: https://lists.onap.org/mt/60965239/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] Please help to change the status for "E2E Network Slicing" Requirement for TSC's review and vote

[LinMeng]

Dear Catherine and David,

 

For “E2E” Network Slicing requirement,

We’ve already updated and replied to TSC concerns about EXT-API both on 
Frankfurt release requirement and on the Jira REQ-158.

1.  We can deliver the features for Frankfurt even without EXT-API;

2.  The impact in External API for Frankfurt is only minimal impact, the 
resources has been identified and the impacts will be committed.

Could you please kindly help to change the “TSC M1 Approval Recommendation”to 
“YES”, and change “M1 Scorecard”to “Green”?

 

Except for the current scope for SO and EXT-API, we also sincerely request for 
a brief discussion on inclusion of functional enhancements in OOF and UUI 
within the scope on today’s TSC call.

 

 

Best regards& Many thanks,

Lin

---

 

 

 


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

View/Reply Online (#5676): https://lists.onap.org/g/onap-tsc/message/5676
Mute This Topic: https://lists.onap.org/mt/61075487/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]
-=-=-=-=-=-=-=-=-=-=-=-