-
Story
-
Resolution: Done
-
Medium
-
None
-
None
As a community we need a consistent way to tag the Docker images so that we can sort them chronologically.
The need is also documented in the wiki.
Current status within Docker
ONAP Nexus 3 which contains ONAP Docker images is structured as below:
What do we Need standardized Docker format
As Docker Snapshot is a cumulative repository, given a version, a keyword and the name of an image, the need is a systematic method to sort chronologically images based on Nexus version field.
This will help to community in providing an automated deployment using tag sets on a standard format.
Proposal
The proposed docker tag format to align across all the teams is the following:
x.y.z-KEYWORD-yyyymmddThhmmssZ |
---|
X.Y.Z follows the Semantic Versionning
KEYWORD: SNAPSHOT or STAGING
Example
1.1.2-SNAPSHOT-20181231T234559Z |
---|
- blocks
-
INT-189 TAG All builds when Deployment CI passes
- Closed
-
LOG-300 CD: OOM framework for continuous E2E deploy validation of tagged commit/merge trigger docker snapshots
- Closed
-
LOG-305 Docker images must merge/build on each commit not daily
- Closed
-
CIMAN-156 Chain docker merge jobs to application merge jobs
- To Do
- duplicates
-
LOG-302 Standard Tags LF repos on gerrit merges - to drive CI/CD tagset
- Closed
- is blocked by
-
POLICY-674 Docker images names inconsistent between nexus3 and dockerhub (policy-db vs policy-policy-db)
- Closed
-
VID-195 Reference dockerhub mariadb docker image instead of nexus3.onap.org
- Closed
- relates to
-
LOG-300 CD: OOM framework for continuous E2E deploy validation of tagged commit/merge trigger docker snapshots
- Closed
-
INT-300 CI-CD For ONAP master branch
- Closed
-
LOG-218 POMBA jar/war/docker artifact versioning review - with LF
- Closed
-
OOM-327 Jenkins job needed to build and publish the One-Click configuration Docker image.
- Closed
-
OOM-1053 Sync docker image images with docker-manifest.csv
- Closed
- links to
- mentioned in
-
Page Loading...