-
Story
-
Resolution: Duplicate
-
Medium
-
None
-
None
-
None
-
None
The integration project manifest file is used to generate the heat env. template and contains the source of truth for the docker image tags ONAP should be using.
After going through the manifest, I found that OOM is using the incorrect image tags.
Also after going through the manifest, I found that these images are not being used by OOM. Not sure what these are or where they are used but throwing this in for reference:
image,tag onap/aai/esr-gui,v1.0.0 onap/aai/esr-server,v1.0.0 onap/ccsdk-odl-image,v0.1.0 onap/ccsdk-odlsli-image,v0.1.0 onap/dmaap/dmaap-mr,1.0.1 onap/holmes/engine-management,v1.0.0 onap/holmes/rule-management,v1.0.0 onap/modeling/javatoscachecker,v1.0.0 onap/multicloud/openstack-newton,v1.0.0 onap/multicloud/vio-vesagent,v1.0.0 onap/sdc/sdc-workflow-designer,1.0.0-STAGING-latest onap/sdnc-dmaap-listener-image,v1.2.1 onap/sdnc-ueb-listener-image,v1.2.1 openecomp/sdc-sanity,v1.1.0 onap/org.onap.dcaegen2.collectors.ves.vescollector,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
Manifest:
https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv
Noticed that the tags for master and Amsterdam are exactly the same at the time of raising this.
- is blocked by
-
OOM-412 Handle branching in OOM configuration - 16 Nov
- Closed
- relates to
-
POLICY-674 Docker images names inconsistent between nexus3 and dockerhub (policy-db vs policy-policy-db)
- Closed