prepare command needs to discover the versioned tag from the latest tag
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Steve Baker |
Bug Description
For minor updates of containers to work, tags like 'latest' should never be used. However discovering what current version-based tag to use is a manual process. As a consequence upstream CI and development is exclusively using 'latest' anyway.
This can be solved by having the "openstack overcloud container image prepare" command optionally introspect the registry to substitute the stable (latest) tag to a version based tag.
The RDO/kolla build chain sets the label "rdo_version" to the tag that corresponds to the DLRN ref which that container was built from. For example:
docker pull trunk.registry.
docker inspect --format '{{ index .Config.Labels "rdo_version"}}' trunk.registry.
# 184244eb4ad0a5b
As long as every downstream image build pipeline sets their own label which states the version-based tag, the prepare command can have a general tag discovery mechanism which works with images from all sources.
I propose that the "openstack overcloud container image prepare" get a --tag-label argument which when specified will do the following:
- introspect the image in the registry corresponding to the specified --tag
- substitute the --tag tag with the value of the --tag-label label
- use this value for any --env-file or --images-file generated files
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Steve Baker (steve-stevebaker) |
milestone: | none → pike-rc1 |
tags: | added: cont |
tags: |
added: containers upgrade removed: cont |
Changed in tripleo: | |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | pike-rc1 → pike-rc2 |
Changed in tripleo: | |
milestone: | pike-rc2 → queens-1 |
Fix proposed to branch: master /review. openstack. org/498678
Review: https:/