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

Fri, 20 Nov 2020 01:51:45 -0800 


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 <[email protected] 
> <mailto:[email protected]>> 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&D Institute Poland
Samsung Electronics


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22497): https://lists.onap.org/g/onap-discuss/message/22497
Mute This Topic: https://lists.onap.org/mt/78360010/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
























					Reply via email to