Open Stack

+1 to revision information in tags. If you don't have it, depending on when containers start, you could have different versions of software with/without bug fixes running on the same cluster without an easy way to know.

We've seen this with libvirt versions being 1.x in some builds and 2.x in fresher builds.

We can still keep around the unrevisioned tags too for folks that don't want to deal with the revision numbers. in which case, the unrevisioned 4.0.0 tag would map to the newest revisioned tag, say 4.0.0-2 and would have the same behavior then as is today.

Thanks,
Kevin
________________________________________
From: Michał Jastrzębski [inc007 at gmail.com]
Sent: Wednesday, April 12, 2017 3:59 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [kolla] Tags, revisions, dockerhub

My dear Kollegues,

Today we had discussion about how to properly name/tag images being
pushed to dockerhub. That moved towards general discussion on revision
mgmt.

Problem we're trying to solve is this:
If you build/push images today, your tag is 4.0
if you do it tomorrow, it's still 4.0, and will keep being 4.0 until
we tag new release.

But image built today is not equal to image built tomorrow, so we
would like something like 4.0.0-1, 4.0.0-2.
While we can reasonably detect history of revisions in dockerhub,
local env will be extremely hard to do.

I'd like to ask you for opinions on desired behavior and how we want
to deal with revision management in general.

Cheers,
Michal

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev