Uploaded image for project: 'CI-Management'
  1. CI-Management
  2. CIMAN-239

Nexus3 - Migrate teams to start deploying images in DockerHub

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None
    • None

      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.

            jwagantall jwagantall
            jwagantall jwagantall
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: