Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Nexus3 - Migrate teams to start deploying images in DockerHub

Description

Objectives:
1 - Allow teams to manage their own releases. Teams will be on charge to tag  and/ releases their own images as they need.
2 - Allow multi architecture support (x86 + arm64).
3 - More official/public visibility of ONAP releases.
 
Stakeholders:
1 - Tech teams for each component
2 - Releng (Jessica / Bengt)
3 - TSC to approve the migration
4 - ONAP consumers
 
Challenges:
1 - Currently we have all releases in DockerHub, we will not transfer any Snapshots. Teams will need
     to adjust their dependencies before pushing to DockerHub. New Snapshots only will be pushed.
2 - DockerHub performance. Teams will depend on that which is not on LF's hands. (Internally we can 
     set up a mirror or a proxy to help out)
3 - DockerHub does not support separate repos like Nexus3 does. (Should not be a problem, but worth 
     mentioning it)
4 - Any security issues? Confirmed, no.
5 - Jenkins jobs changes and tech team's source code adjustments.
 
Actions:
1 - LF to develop the needed Jenkins templates and documentation.
2 - Tech teams to adjust source code registry references from Nexus3 to DockerHub.
3 - LF/Tech teams to coordinate the migration for their components.

Attachments

2

blocks

is blocked by

relates to

Activity

Show:

Jessica Gonzalez April 9, 2019 at 7:28 PM

Thanks Paul. Yes.. we can start with that convention for now. 

In parallel, I have updated more work being done with Martin in https://lf-onap.atlassian.net/browse/CIMAN-229 which focuses on the Nexus3 work. 

 

Thanks!

Jess

Former user April 5, 2019 at 11:09 AM
Edited

Hi

Regarding the dockerhub naming of the arm64 images (onap{arm64/arch64}/${docker-image-name} as oposed to onap/docker-image-name-${arm64/arch64], I think we should try to propose one of the variants whatever it is (let's say onap${arm64/arch64}/docker-image-name) than to ask all the tech teams how they prefer, just for the sake of uniformity.

 

Best Regards,

Paul

Jessica Gonzalez April 3, 2019 at 5:05 PM

The current progress got diverted to internal conversations with Paul and Martin, my apologies for that. 

 

Martin suggested an approach to unblock CI/CD efforts by configuring the Nexus3 ports to allow for ARM architecture to use the releases and

snapshots registries. 

This work is under review here https://gerrit.onap.org/r/#/c/83906/ and it is currently implemented in the Sandbox.

The testing in the sandbox is still ongoing as of today + hopefully a meeting in person with the team.

 

 

Thanks

Jess

Former user March 15, 2019 at 6:35 PM

This ticket was originally logged as an LF Helpdesk ticket:
https://rt.linuxfoundation.org/SelfService/Display.html?id=67224
That LF ticket captured the root issue we encountered as a blocker for Dublin.

Jessica Gonzalez February 13, 2019 at 8:09 PM

In parallel, I am working on developing the verify and merge jobs for docker images:

https://gerrit.linuxfoundation.org/infra/#/c/14561/

 

 

Done

Details

Assignee

Reporter

Priority

Created February 13, 2019 at 8:03 PM
Updated April 1, 2020 at 6:18 PM
Resolved April 1, 2020 at 6:18 PM