Re: [onap-discuss] TR : [onap-tsc] [IMPORTANT] OOM status update for RC0

[Krzysztof Opasiak via lists.onap.org]

Hi Kenny,

On 29.03.2021 19:17, Kenny Paul wrote:
> The most important thing we all need to remember is that everyone is working 
> very hard to ultimately achieve the same goal.
> 
> In an opensource world changes are most often influenced from the bottom up 
> rather than instituted from the top down.  How long a process change takes is 
> going to vary greatly based upon a number of factors that may or may not be 
> in the direct control of the community members trying to implement the change.
> 
> Consider the fact that ONAP is one of relatively few truly global open source 
> projects.  We are not unique in that aspect, but it creates far larger 
> challenges than any regionally or culturally centric OSS projects would ever 
> need to consider beyond just the simple time-zone issue we face.  Add in the 
> fact that ONAP developers are primarily company provided resources rather 
> than being  a group of purely volunteer individual contributors and our 
> challenges are even more difficult because you have a vast array of company 
> norms and policies  that may also need to be navigated to implement a change.
> 
> Here in the US what is perfectly acceptable for a F2F business meeting on the 
> West Coast may be completely unacceptable when that same meeting is held on 
> the East Coast.  Years ago I made that exact error at an internal company 
> meeting I was attending.  I knew how company meetings operated out here and 
> assumed that it was that way everywhere else in the company.  I was very, 
> very wrong with that assumption and ended up embarrassing my Director and VP 
> as a result.   Needless to say this took a long time to recover from 
> career-wise.
> 
> Patience when working in a global community is a prerequisite and our most 
> valuable asset as communication styles, business cultures and regional 
> cultures around the world are very different than our own.

I fully agree with all what you wrote above!

Ultimately we are all passengers who would like to get to our final 
station, nevertheless not all of us needs to take the same train.

When the train is broken, no one can get anywhere so everyone needs to 
wait and do their best to repair the train. As soon as the train is 
operational it should be moving according to the schedule.

Every passenger is different and independent. Everyone may have a 
different tempo, different additional duties, different size of 
suitcase, different limitations but everyone has a freedom to choose the 
course from the timetable which suits him the most and plan his or her 
journey accordingly. Nevertheless to take that train one needs to be on 
the platform on time, if not then the train just moves forward but no 
one is excluding that passenger from reaching his final destination. He 
just needs to wait a little bit and take the next train.

Obviously TSC is the body that creates timetables for our trains so it's 
also up to TSC to decide how long the train can wait at any point. In my 
opinion it's not an easy role and a really tough decision as every 
minute of waiting allow more late comers to take the train but in the 
same time it also delays all the passengers that are inside the train 
and makes their journey unpredictable. (Maybe next time we've 10 other 
passengers arriving late, speculating that it doesn't make any sense to 
be on time as the train will always wait for them?)

I've a very limited knowledge about the World so I'm not sure how it 
looks in other countries but in Poland there is a lot of jokes about our 
trains that are often delayed and a lot of admiration for ultra-punctual 
Japanese railway transport.

> 
> Thanks!
> -kenny
> 
> 
> 
> -Original Message-
> From: onap-tsc@lists.onap.org  On Behalf Of 
> Krzysztof Opasiak via lists.onap.org
> Sent: Monday, March 29, 2021 3:28 AM
> To: Xu Ran ; Catherine LEFEVRE 
> ; Dong Wang 
> Cc: Alexander Mazuruk ; DESBUREAUX Sylvain TGI/OLN 
> ; onap-tsc ; 
> morgan.richo...@orange.com; marcin.przyb...@nokia.com; Kuzmicki,Krzysztof 
> (Nokia - PL/Wroclaw) ; Closset,Christophe 
> ; Bartek Grzybowski 
> ; HARDY Thierry TGI/OLN 
> ; michal.jagie...@t-mobile.pl; Geissler, Andreas 
> ; fu.guangr...@zte.com.cn; RAJEWSKI Lukasz O-PL 
> ; Paweł Wieczorek ; 
> Lasse Kaihlavirta ; FREEMAN, BRIAN D 
> ; bin.y...@windriver.com; TIMONEY, DAN ; 
> MAHER, RANDA ; HAHN III, JIM ; Seshu m 
> ; Toine Siebelink ; 
> krishna.moort...@wipro.com; onap-disc...@lists.onap.org
> Subject: Re: [onap-discuss] TR : [onap-tsc] [IMPORTANT] OOM status update for 
> RC0
> 
> Hi Xu Ran,
> 
> On 29.03.2021 03:40, Xu Ran wrote:
>> Dear Opasiak and Catherine,
>>
>> I have noticed that the block thing of UUI’s merge into OOM is:
>>
>> https://protect2.fireeye.com/v1/url?k=072c4f49-58b77645-072dc406-000babff3563-8875456a004bfcbf=1=3baf245c-daee-4505-94b6-9ca68385b9c9=https%3A%2F%2Fgerrit.onap.org%2Fr%2Fc%2Foom%2F%2B%2F118930
>> > 

[onap-tsc] LFN Webinar Tomorrow: "NFV Deployments and the Path Ahead: An Operator Perspective"

[Brandon Wick]

LFN Community:
This is a reminder that we'll be hosting the following LFNWebinar tomorrow,
Tuesday, March 30th, 8:00 AM PT. Register here.
NFV Deployments and the Path Ahead: An Operator Perspective
Beth Cohen, Verizon; Lei Huang, China Mobile; and Randy Levensalor, CableLabs

With the drive to deploy 5G, network slicing, and the dramatic changes in
network service delivery due to the global pandemic, 2020 was the year that many
carriers started large NFV deployments; indicating the continuing maturation and
acceptance of virtualized networking workloads, NFV architectures, and cloud
infrastructures in general. As these deployments ramp up and expand, it is time
to focus on tools needed for deployment in a common, shared, programmable, and
automated manner. There remain significant challenges, however, to achieving
this vision.
The LFN End User Advisory Group (EUAG) is publishing an NFV Testing and
Automation White Paper to illustrate key insights on the state of NFV automated
testing, current gaps, and industry recommendations. In this webinar, industry
experts from the EUAG: Beth Cohen, Verizon; Lei Huang, China Mobile; and Randy
Levensalor, CableLabs will discuss the white paper key findings and answer
questions.

Register here.

Best,
Brandon Wick
Senior Integrated Marketing ManagerThe Linux Foundation
bw...@linuxfoundation.org+1.917.282.0960


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7668): https://lists.onap.org/g/onap-tsc/message/7668
Mute This Topic: https://lists.onap.org/mt/81702253/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-discuss] TR : [onap-tsc] [IMPORTANT] OOM status update for RC0

[Kenny Paul]

The most important thing we all need to remember is that everyone is working 
very hard to ultimately achieve the same goal.

In an opensource world changes are most often influenced from the bottom up 
rather than instituted from the top down.  How long a process change takes is 
going to vary greatly based upon a number of factors that may or may not be in 
the direct control of the community members trying to implement the change. 

Consider the fact that ONAP is one of relatively few truly global open source 
projects.  We are not unique in that aspect, but it creates far larger 
challenges than any regionally or culturally centric OSS projects would ever 
need to consider beyond just the simple time-zone issue we face.  Add in the 
fact that ONAP developers are primarily company provided resources rather than 
being  a group of purely volunteer individual contributors and our challenges 
are even more difficult because you have a vast array of company norms and 
policies  that may also need to be navigated to implement a change.

Here in the US what is perfectly acceptable for a F2F business meeting on the 
West Coast may be completely unacceptable when that same meeting is held on the 
East Coast.  Years ago I made that exact error at an internal company meeting I 
was attending.  I knew how company meetings operated out here and assumed that 
it was that way everywhere else in the company.  I was very, very wrong with 
that assumption and ended up embarrassing my Director and VP as a result.   
Needless to say this took a long time to recover from career-wise.

Patience when working in a global community is a prerequisite and our most 
valuable asset as communication styles, business cultures and regional cultures 
around the world are very different than our own. 

Thanks!
-kenny



-Original Message-
From: onap-tsc@lists.onap.org  On Behalf Of Krzysztof 
Opasiak via lists.onap.org
Sent: Monday, March 29, 2021 3:28 AM
To: Xu Ran ; Catherine LEFEVRE 
; Dong Wang 
Cc: Alexander Mazuruk ; DESBUREAUX Sylvain TGI/OLN 
; onap-tsc ; 
morgan.richo...@orange.com; marcin.przyb...@nokia.com; Kuzmicki,Krzysztof 
(Nokia - PL/Wroclaw) ; Closset,Christophe 
; Bartek Grzybowski 
; HARDY Thierry TGI/OLN 
; michal.jagie...@t-mobile.pl; Geissler, Andreas 
; fu.guangr...@zte.com.cn; RAJEWSKI Lukasz O-PL 
; Paweł Wieczorek ; Lasse 
Kaihlavirta ; FREEMAN, BRIAN D 
; bin.y...@windriver.com; TIMONEY, DAN ; MAHER, 
RANDA ; HAHN III, JIM ; Seshu m 
; Toine Siebelink ; 
krishna.moort...@wipro.com; onap-disc...@lists.onap.org
Subject: Re: [onap-discuss] TR : [onap-tsc] [IMPORTANT] OOM status update for 
RC0

Hi Xu Ran,

On 29.03.2021 03:40, Xu Ran wrote:
> Dear Opasiak and Catherine,
> 
> I have noticed that the block thing of UUI’s merge into OOM is:
> 
> https://gerrit.onap.org/r/c/oom/+/118930
>  abff3793-f7ea0549a854ee69=1=26b28653-b4cf-4482-aed3-4b5732aa0935
> =https%3A%2F%2Fgerrit.onap.org%2Fr%2Fc%2Foom%2F%2B%2F118930>
> https://gerrit.onap.org/r/c/oom/+/119124
>  abff3793-1e123c16f51c1874=1=26b28653-b4cf-4482-aed3-4b5732aa0935
> =https%3A%2F%2Fgerrit.onap.org%2Fr%2Fc%2Foom%2F%2B%2F119124>
> 
> 
> They’re all related to the new NLP server, however, since there’re 
> some several problems appearing in these two commits, we accept the 
> result to delay this new part to Istanbul release. We’ll abandon these 
> two commits and make further changes. And the H release plan of UUI 
> will *NOT* include this part.

No need to abandon. You can always squash the two and move ahead with a new 
patchset on one of the reviews;)

> 
> As for the commit:
> https://gerrit.onap.org/r/c/oom/+/119844
>  abff3793-15fb88f07d0c1278=1=26b28653-b4cf-4482-aed3-4b5732aa0935
> =https%3A%2F%2Fgerrit.onap.org%2Fr%2Fc%2Foom%2F%2B%2F119844>
> 
> 
> This commit only contains the changes of E2E slicing service which are 
> some minor ones.

Yes + there is an implementation of NLP server introduced by commit 
7643cc5b373b167000d676c48d741e830081f3ab but I expect that as NLP is delayed to 
Istanbul then this is just disabled by default?

> We hope that OOM team can review this change and merge it. If there’s 
> any problem with the E2E part, we’ll be free to change.
>   And also, Doctor @Dong Wang is the sponsor of the new NLP part, he 
> is also available to response the problem of this part.
> 
> We will attend today’s PTL meeting to make some more explanation, hope 
> we can reach an agreement.

Gating seems to be fine on those patches. My only concern, that I expressed in 
the ticket is what is the rationale for not providing this container update 
before the deadline which is M3?

Your REQ tickets say that you don't expect a need to update OOM configuration 
for this release...


> 
> 
> B.R.
> 

Re: [onap-discuss] TR : [onap-tsc] [IMPORTANT] OOM status update for RC0

[Catherine LEFEVRE]

Good morning Xu,

Thank you so much for your feedback.
I believe that’s the right thing to do.
I will also help to stabilize the release.
Let’s focus on 
https://gerrit.onap.org/r/c/oom/+/119844
 as suggested.

Many thanks & regards
Catherine


From: Xu Ran 
Sent: Monday, March 29, 2021 3:40 AM
To: k.opas...@samsung.com; Lefevre, Catherine ; 
Dong Wang 
Cc: Alexander Mazuruk ; DESBUREAUX Sylvain TGI/OLN 
; onap-tsc ; Lefevre, 
Catherine ; morgan.richo...@orange.com; 
marcin.przyb...@nokia.com; Kuzmicki,Krzysztof ; 
Closset, Christophe ; Bartek Grzybowski 
; HARDY Thierry TGI/OLN 
; michal.jagie...@t-mobile.pl; Geissler, Andreas 
; fu.guangr...@zte.com.cn; RAJEWSKI Lukasz O-PL 
; Paweł Wieczorek ; Lasse 
Kaihlavirta ; FREEMAN, BRIAN D 
; bin.y...@windriver.com; TIMONEY, DAN ; MAHER, 
RANDA ; HAHN III, JIM ; Seshu m 
; Toine Siebelink ; 
krishna.moort...@wipro.com; onap-disc...@lists.onap.org
Subject: Re: [onap-discuss] TR : [onap-tsc] [IMPORTANT] OOM status update for 
RC0

Dear Opasiak and Catherine,

I have noticed that the block thing of UUI’s merge into OOM is:

https://gerrit.onap.org/r/c/oom/+/118930
https://gerrit.onap.org/r/c/oom/+/119124

They’re all related to the new NLP server, however, since there’re some several 
problems appearing in these two commits, we accept the result to delay this new 
part to Istanbul release. We’ll abandon these two commits and make further 
changes. And the H release plan of UUI will NOT include this part.

As for the commit:
https://gerrit.onap.org/r/c/oom/+/119844

This commit only contains the changes of E2E slicing service which are some 
minor ones. We hope that OOM team can review this change and merge it. If 
there’s any problem with the E2E part, we’ll be free to change.
 And also, Doctor @Dong Wang is the sponsor of the new NLP part, he is also 
available to response the problem of this part.

We will attend today’s PTL meeting to make some more explanation, hope we can 
reach an agreement.


B.R.
-
Xu Ran
China Mobile Research Institute
No.32 Xuanwumen west street,Xicheng District, Beijing 100053, China

Mobile: +86 15010868144
Email:  xuran...@chinamobile.com
-

On 03/27/2021 03:05，Krzysztof Opasiak via 
lists.onap.org
 wrote：
Dear Catherine,

On 26.03.2021 19:13, Lefevre, Catherine wrote:
Dear OOM Team,

David and I we are trying to understand what it is left from OOM Backlog
that the project team(s) need to consider before the next PTL call (3/29)

We understand from the TSC call (3/25) - SO, SDNC and UUI had an action
but it was not clear that there were other projects.

Here is our understanding and the path to move forward.

After the following items are solved then we need to stabilize the
release and no more accept any OOM code submission except

for *versioning, documentation and show stoppers blocking E2E Testing.*

#1 UUI

Remaining code submitted to change version is
"https://gerrit.onap.org/r/c/oom/+/119844
"

I have reviewed it and did not notice anything wrong so I believe it is
ready to merge

The UUI action was related to:
https://gerrit.onap.org/r/c/oom/+/118930
https://gerrit.onap.org/r/c/oom/+/119124

Not the patch that you linked above. The one that you linked has been
created *yesterday* 40 mins before the TSC meeting 

[onap-tsc] Doc PTL announcement

[Sofia Wallin]

Dear TSC,
I am happy to announce Thomas Kulik as new ONAP doc PTL.

Please see the updated “Voting results history page”,
https://wiki.onap.org/display/DW/Voting+Results+History#VotingResultsHistory-PTLElections

Best regards,
Sofia


From:  on behalf of "Sofia Wallin via lists.onap.org" 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Thursday, 11 February 2021 at 17:13
To: "onap-tsc@lists.onap.org" 
Subject: [onap-tsc] Stepping down as Doc PTL

Dear TSC,
After leading the ONAP doc project for 2+ years it is time to let someone else 
step up and evolve the project further.
With this email I’m stepping down as PTL for the ONAP doc project.

Nominations are open and we have initiated a conversation within the project. I 
will continue until March 31st and I’m hoping to announce a new PTL within 
short.

Thank you to everyone, is has been a lot of fun working with the community and 
to lead the documentation project.

Best regards,
Sofia



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7664): https://lists.onap.org/g/onap-tsc/message/7664
Mute This Topic: https://lists.onap.org/mt/81690435/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]
-=-=-=-=-=-=-=-=-=-=-=-