Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-432

Migrate to R1 release artifacts for docker images across all component values.yaml

    Details

    • Type: Task
    • Status: Closed
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      OOM-432, OOM-328 and OOM-438 can all be done together

      Was thinking that we need a review of all our component values.yaml files – and a rework of docker_prepull.sh – the grep refactor of this delegated a couple days ago

      https://jira.onap.org/browse/OOM-328

       

      will raise one to check the yamls

       see

      https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv 

      – as yesterday we ran into an issue where one internal system experienced issues with the openecomp to onap refactor as expected – but other systems – evidently not running the latest images/wars did not

      https://jira.onap.org/browse/OOM-426

      https://jira.onap.org/browse/OOM-425

       see also OOM-432

       

      From: Sauvageau, David david.sauvageau@bell.ca
      Sent: Wednesday, November 15, 2017 18:17
      To: Roger Maitland <Roger.Maitland@amdocs.com>; Choquette, Marc-Alexandre <m.a.choquette@bell.ca>; Michael O'Brien <Frank.Obrien@amdocs.com>; Mike Elliott <Mike.Elliott@amdocs.com>
      Subject: Fwd: [Onap-release] Critical Action: After LF has moved your artifact into Nexus...

       

      Fyi

      Envoyé de mon iPhone

      Début du message transféré :

      Expéditeur: Gildas Lanilis <gildas.lanilis@huawei.com>
      Date: 15 novembre 2017 à 18:14:33 UTC−5
      Destinataire: "onap-release@lists.onap.org" <onap-release@lists.onap.org>
      Cc: "PLATANIA, MARCO  (MARCO)" <platania@research.att.com>, Jessica Wagantall <jwagantall@linuxfoundation.org>, "eric.debeau@orange.com" <eric.debeau@orange.com>
      Objet: [Onap-release] Critical Action: After LF has moved your artifact into Nexus...

      Hi PTLs,

       

      As we speak, there is still a significant amount of Docker Images that have not updated the Docker Manifest at https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv

      There should NOT BE ANY “STAGING” word in that file but a simple “vx.y.z”.

      Please once LF has moved the Docker artifact do not forget to:

       

      This is critical as the Docker Manifest and Heat Template are the source of truth for a successful deployment.

       

      List of staging in Docker https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv

       

      image,tag

      onap/aai/esr-gui,1.0.0-STAGING-latest

      onap/aai/esr-server,1.0.0-STAGING-latest

      onap/admportal-sdnc-image,1.2-STAGING-latest

      onap/ccsdk-dgbuilder-image,0.1-STAGING-latest

      onap/ccsdk-odl-image,0.1-STAGING-latest

      onap/ccsdk-odlsli-image,0.1-STAGING-latest

      onap/clamp,v1.1.0

      onap/cli,v1.1.0

      onap/data-router,1.1-STAGING-latest

      onap/holmes/dsa,1.0.0-STAGING-latest

      onap/holmes/engine-management,v1.0.0

      onap/holmes/rule-management,v1.0.0

      onap/modeling/javatoscachecker,latest

      onap/model-loader,1.1-STAGING-latest

      onap/msb/msb_apigateway,1.0.0-STAGING-latest

      onap/msb/msb_discovery,1.0.0-STAGING-latest

      onap/oom/kube2msb,1.0.0-STAGING-latest

      onap/org.onap.dcaegen2.collectors.ves.vescollector,v1.1.0

      onap/org.onap.dcaegen2.deployments.bootstrap,v1.1.0

      onap/org.onap.dcaegen2.platform.cdapbroker,v4.0.0

      onap/org.onap.dcaegen2.platform.configbinding,v1.2.0

      onap/org.onap.dcaegen2.platform.deployment-handler,v1.1.0

      onap/org.onap.dcaegen2.platform.inventory-api,v1.2.0

      onap/org.onap.dcaegen2.platform.policy-handler,v1.1.0

      onap/org.onap.dcaegen2.platform.servicechange-handler,v1.0.0

      onap/policy/policy-db,v1.1.0

      onap/policy/policy-drools,1.1.0

      onap/policy/policy-nexus,1.1.0

      onap/policy/policy-pe,1.1.0

      onap/portal-apps,v1.3.0

      onap/portal-db,v1.3.0

      onap/portal-wms,v1.3.0

      onap/sdnc-image,1.2-STAGING-latest

      onap/search-data-service,1.1-STAGING-latest

      onap/sparky-be,1.1-STAGING-latest

      onap/vfc/catalog,1.0.2-STAGING-latest

      onap/vfc/emsdriver,1.0.1-STAGING-latest

      onap/vfc/gvnfmdriver,1.0.1-STAGING-latest

      onap/vfc/jujudriver,1.0.0-STAGING-latest

      onap/vfc/nfvo/svnfm/huawei,1.0.2-STAGING-latest

      onap/vfc/nfvo/svnfm/nokia,1.0.2-STAGING-latest

      onap/vfc/nslcm,1.0.2-STAGING-latest

      onap/vfc/resmanagement,1.0.0-STAGING-latest

      onap/vfc/vnflcm,1.0.1-STAGING-latest

      onap/vfc/vnfmgr,1.0.1-STAGING-latest

      onap/vfc/vnfres,1.0.1-STAGING-latest

      onap/vfc/wfengine-activiti,1.0.0-STAGING-latest

      onap/vfc/wfengine-mgrservice,1.0.0-STAGING-latest

      onap/vfc/ztesdncdriver,1.0.0-STAGING-latest

      onap/vfc/ztevmanagerdriver,1.0.2-STAGING-latest

      onap/vnfsdk/refrepo,1.0.0

      openecomp/aai-resources,1.1-STAGING-latest

      openecomp/aai-traversal,1.1-STAGING-latest

      openecomp/appc-image,v1.2.0

      openecomp/mso,1.1-STAGING-latest

      openecomp/sdc-backend,1.1-STAGING-latest

      openecomp/sdc-elasticsearch,1.1-STAGING-latest

      openecomp/sdc-frontend,1.1-STAGING-latest

      openecomp/sdc-kibana,1.1-STAGING-latest

      openecomp/sdc-sanity,1.1-STAGING-latest

      openecomp/vid,v1.1.0

       

       

      Thanks,

      Gildas

      ONAP Release Manager

      1 415 238 6287

       

      From: Gildas Lanilis
      Sent: Wednesday, November 08, 2017 6:27 PM
      To: 'onap-release@lists.onap.org' <onap-release@lists.onap.org>
      Subject: After LF has moved your artifact into Nexus...

       

      Hi PTLs,

       

      One point of clarification on moving artifacts into Nexus.

      After LF has moved the artifacts into Nexus, you still need to declare or update the version number for your respective artifacts in the java and docker version manifest at https://git.onap.org/integration/tree/version-manifest/src/main/resources

       

      That is the only way for the other teams to know which upstream version they are depending on.

       

      This whole procedure is explained in details at https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process

       

      Let me know if you have any questions.

        Attachments

          Issue Links

          # Subject Branch Project Status CR V

            Activity

              People

              • Assignee:
                adetalhouet Alexis de Talhouët
                Reporter:
                michaelobrien Michael O'Brien
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: