date:20201120

[onap-tsc] 2nd draft of Honolulu schedule available for review #honolulu

2020-11-20 Thread David McBride

Team,

Following several meetings over the last two weeks to clarify the
terminology and milestone tasks for the new release process, we have a new
schedule for your review .

Thanks to @Krzysztof Opasiak  , @Catherine LEFEVRE
 , @Chaker Al-Hakim
 , @VENKATESH KUMAR, VIJAY 
 , @TIMONEY, DAN  , and @Seshu m  for
attending the meetings and providing feedback.

We will be discussing the schedule and the milestone requirements in the
next PTL and TSC meetings.

David

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


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7292): https://lists.onap.org/g/onap-tsc/message/7292
Mute This Topic: https://lists.onap.org/mt/78397915/21656
Mute #honolulu:https://lists.onap.org/g/onap-tsc/mutehashtag/honolulu
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] Promotion of Ramesh as SO committer

2020-11-20 Thread Ranny Haiby (Samsung) via lists.onap.org

+1

Ranny.


From:  on behalf of "Eric Debeau via lists.onap.org" 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Friday, November 20, 2020 at 11:30 AM
To: "onap-tsc@lists.onap.org" , Seshu m 

Subject: Re: [onap-tsc] Promotion of Ramesh as SO committer
Resent-From: 

Hello

+1

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de seshu 
kumar m via lists.onap.org [seshu.kumar.m=huawei@lists.onap.org]
Envoyé : vendredi 20 novembre 2020 17:27
À : Seshu m; onap-tsc
Objet : Re: [onap-tsc] Promotion of Ramesh as SO committer

Dear TSC,



I would like to provide the promotion of Ramesh Parthasarathy as SO project 
committer.



Detailed report on the candidature can be found in the wiki link :



https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BService+Orchestrator%5D+-+11.04.2020



We received 5/6 votes as +1 from the existing commiters of SO collected through 
email.



will be updating the info.yaml file once TSC approves the promotion.



--
Thanks and Regards,
M Seshu Kumar
Lead Architect,
PS, Cloud Network OSDT,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!
---
From:Seshu m 
To:SMOKOWSKI, STEVEN ;BENJAMIN, MAX 
;byung-woo.jun ;Muszkieta, Lukasz 
(Nokia - PL/Wroclaw) ;Chenchuanyu 
;Seshu m 
Date:2020-11-18 18:14:16
Subject:Promotion of Ramesh as SO committer


Dear SO Committers



This is in regards to the promotion of Ramesh Parthasarathy as committer in SO.

You can find the details of his contributions to SO and its integration with 
oom.



https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BService+Orchestrator%5D+-+11.04.2020



Ramesh has been consistent with his contributions to SO and has made 
significant contributions for the project to meet the milestones.



Request to kindly provide your feedback with one of the below options before 
20th November 2020 EOB:

+1 if you agree

0 if you have no opinion

-1 if you don't agree





--
Thanks and Regards,
M Seshu Kumar
Lead Architect,
PS, Cloud Network OSDT,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!
---

_



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

Re: [onap-tsc] Promotion of Ramesh as SO committer

2020-11-20 Thread Eric Debeau via lists.onap.org

Hello

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de seshu
kumar m via lists.onap.org [seshu.kumar.m=huawei@lists.onap.org]
Envoyé : vendredi 20 novembre 2020 17:27
À : Seshu m; onap-tsc
Objet : Re: [onap-tsc] Promotion of Ramesh as SO committer

Dear TSC,

I would like to provide the promotion of Ramesh Parthasarathy as SO project
committer.

Detailed report on the candidature can be found in the wiki link :

https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BService+Orchestrator%5D+-+11.04.2020

We received 5/6 votes as +1 from the existing commiters of SO collected through
email.

will be updating the info.yaml file once TSC approves the promotion.

--
Thanks and Regards,
M Seshu Kumar
Lead Architect,
PS, Cloud Network OSDT,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive this
e-mail in error, please notify the sender by phone or email immediately and
delete it!
---

From:Seshu m
To:SMOKOWSKI, STEVEN ;BENJAMIN, MAX
;byung-woo.jun ;Muszkieta, Lukasz
(Nokia - PL/Wroclaw) ;Chenchuanyu
;Seshu m
Date:2020-11-18 18:14:16
Subject:Promotion of Ramesh as SO committer

Dear SO Committers

This is in regards to the promotion of Ramesh Parthasarathy as committer in SO.

You can find the details of his contributions to SO and its integration with
oom.

https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BService+Orchestrator%5D+-+11.04.2020

Ramesh has been consistent with his contributions to SO and has made
significant contributions for the project to meet the milestones.

Request to kindly provide your feedback with one of the below options before
20th November 2020 EOB:

+1 if you agree

0 if you have no opinion

-1 if you don't agree

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 (#7290): https://lists.onap.org/g/onap-tsc/message/7290
Mute This Topic: https://lists.onap.org/mt/78392908/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy

Re: [onap-tsc] Promotion of Ramesh as SO committer

2020-11-20 Thread seshu kumar m via lists.onap.org

Dear TSC,

I would like to provide the promotion of Ramesh Parthasarathy as SO project
committer.

Detailed report on the candidature can be found in the wiki link :

https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BService+Orchestrator%5D+-+11.04.2020

We received 5/6 votes as +1 from the existing commiters of SO collected through
email.

will be updating the info.yaml file once TSC approves the promotion.

From:Seshu m
To:SMOKOWSKI, STEVEN ;BENJAMIN, MAX
;byung-woo.jun ;Muszkieta, Lukasz
(Nokia - PL/Wroclaw) ;Chenchuanyu
;Seshu m
Date:2020-11-18 18:14:16
Subject:Promotion of Ramesh as SO committer

Dear SO Committers

This is in regards to the promotion of Ramesh Parthasarathy as committer in SO.

You can find the details of his contributions to SO and its integration with
oom.

https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BService+Orchestrator%5D+-+11.04.2020

Ramesh has been consistent with his contributions to SO and has made
significant contributions for the project to meet the milestones.

Request to kindly provide your feedback with one of the below options before
20th November 2020 EOB:

+1 if you agree

0 if you have no opinion

-1 if you don't agree

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

Re: [onap-tsc] [onap-discuss] [ONAP] CD chains and CSIT tests strongly impacted by dockerhub policy change

2020-11-20 Thread Krzysztof Opasiak via lists.onap.org




On 19.11.2020 18:53, Jessica Wagantall wrote:
> Hi Morgan,
> 
> I brought this concern to Steve Winslow. Let me quote his reply so that 
> there is no confusion:
> 
> "If we are pulling the build image from our nexus solely for internal 
> runs and not making the third party images available to external folks, 
> then I'm not concerned about that."
> "The issue we had talked about with the ONAP teams earlier this year was 
> that we should not be redistributing binary container images / layers 
> that consist of base layers outside the ONAP project. It's okay to point 
> to pulling those base layers from DockerHub or third party sources but 
> we should not be redistributing them ourselves."

Right. So the bottom line is that only LF internal system will be able 
to use nexus as a proxy right?

> 
> Please let me know if this clarifies the concern
> 
> Thanks!
> Jess
> 
> 
> On Wed, Nov 18, 2020 at 11:21 PM  > wrote:
> 
> Hi,
> 
> recently Docker has enabled download rate limits for pull requests
> on Docker Hub.
> Several upstream components used in ONAP are hosted in dockerhub.
> 
> As a consequences lots of CD chains or CSIT tests are now failing
> due to the error:
> "Error response from daemon: toomanyrequests: You have reached your
> pull rate limit. You may increase the limit by authenticating and
> upgrading: https://www.docker.com/increase-rate-limit;
> 
> Some CSIT tests committed patches to use the Nexus3 as a proxy/cache
> for these upstream repositories.
> 
> It has obviously major impacts on integration activities.
> 
> @Jessica do you confirm that it is possible and there is no legal
> issues? as far as I remember it was decided not to host third-party
> dockers for legal issues, caching them is not very different from
> hosting, no?
> 
> As far as I can see Mirantis that acquired the dockerhub activities
> recently is a member of the lfn networking, is there any way to
> discuss with their representatives to see if they could exclude
> community activities from this rate limitation mechanism?
> 
> 
> Regards
> 
> /Morgan
> 
> 
> 
> 
> 
> _
> 
> 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.
> 
> 

-- 
Krzysztof Opasiak
Samsung R Institute Poland
Samsung Electronics


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7287): https://lists.onap.org/g/onap-tsc/message/7287
Mute This Topic: https://lists.onap.org/mt/78385910/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] [OOM] registry.hub.docker.com seems to need authentication now

2020-11-20 Thread Sylvain Desbureaux via lists.onap.org

Sorry for the spam but it means that for now, we should have issue only with 
rate limit, no authentication issue.

it's still a big pain on our side (OOM and gating) as we hit the rate limit all 
the time, and thus we can't really test but it's less critical than what I said 
earlier

De : onap-disc...@lists.onap.org [onap-disc...@lists.onap.org] de la part de 
Sylvain Desbureaux via lists.onap.org 
[sylvain.desbureaux=orange@lists.onap.org]
Envoyé : vendredi 20 novembre 2020 08:55
À : onap-rele...@lists.onap.org; onap-disc...@lists.onap.org
Cc : onap-tsc@lists.onap.org; dmcbr...@linuxfoundation.org; Kenny Paul; 
jwagant...@linuxfoundation.org
Objet : [onap-discuss] [OOM] registry.hub.docker.com seems to need 
authentication now

Hello,
it seems (although some people had this particular issue long time ago) that 
"registry.hub.docker.com" needs now authentication in contrary to "docker.io" 
:-(.
It wasn't the case at least a couple of weeks ago.

Unfortunately, it's used in several places in OOM, for a lot of releases.

That means that ALL ONAP deployments via OOM (El Alto, Frankfurt, Guilin, 
Master and the older ones) are broken now.

I'm doing my best to mitigate the issue (I've created a JIRA: 
https://jira.onap.org/browse/OOM-2636) but of course, it doesn't help at the 
end of the release (and it's on top of dockerhub rate limit...)

Regards,
Sylvain



_

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.




_

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 (#7286): https://lists.onap.org/g/onap-tsc/message/7286
Mute This Topic: https://lists.onap.org/mt/78384850/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] [OOM] registry.hub.docker.com seems to need authentication now

2020-11-20 Thread Sylvain Desbureaux via lists.onap.org

Hello,
it's actually a bit more complicated than that:

for docker "official" images, registry.hub.docker.com has a different behavior 
than docker.io

with busybox:

docker pull busybox:1.32 --> WORKS
docker pull library/busybox:1.32 --> WORKS
docker pull docker.io/busybox:1.32 --> WORKS
docker pull docker.io/library/busybox:1.32 --> WORKS
docker pull registry.hub.docker.com/library/busybox:1.32 --> WORKS

BUT:

docker pull registry.hub.docker.com/busybox:1.32 --> authentication required


De : onap-disc...@lists.onap.org [onap-disc...@lists.onap.org] de la part de 
Sylvain Desbureaux via lists.onap.org 
[sylvain.desbureaux=orange@lists.onap.org]
Envoyé : vendredi 20 novembre 2020 08:55
À : onap-rele...@lists.onap.org; onap-disc...@lists.onap.org
Cc : onap-tsc@lists.onap.org; dmcbr...@linuxfoundation.org; Kenny Paul; 
jwagant...@linuxfoundation.org
Objet : [onap-discuss] [OOM] registry.hub.docker.com seems to need 
authentication now

Hello,
it seems (although some people had this particular issue long time ago) that 
"registry.hub.docker.com" needs now authentication in contrary to "docker.io" 
:-(.
It wasn't the case at least a couple of weeks ago.

Unfortunately, it's used in several places in OOM, for a lot of releases.

That means that ALL ONAP deployments via OOM (El Alto, Frankfurt, Guilin, 
Master and the older ones) are broken now.

I'm doing my best to mitigate the issue (I've created a JIRA: 
https://jira.onap.org/browse/OOM-2636) but of course, it doesn't help at the 
end of the release (and it's on top of dockerhub rate limit...)

Regards,
Sylvain



_

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.




_

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 (#7285): https://lists.onap.org/g/onap-tsc/message/7285
Mute This Topic: https://lists.onap.org/mt/78384850/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] 2nd draft of Honolulu schedule available for review #honolulu

Re: [onap-tsc] Promotion of Ramesh as SO committer

Re: [onap-tsc] Promotion of Ramesh as SO committer

Re: [onap-tsc] Promotion of Ramesh as SO committer

Re: [onap-tsc] [onap-discuss] [ONAP] CD chains and CSIT tests strongly impacted by dockerhub policy change

Re: [onap-tsc] [OOM] registry.hub.docker.com seems to need authentication now

Re: [onap-tsc] [OOM] registry.hub.docker.com seems to need authentication now

7 matches

Site Navigation

Mail list logo

Footer information