[openstack-dev] [glance] Queens PTG: Thursday summary

Belmiro Moreira moreira.belmiro.email.lists at gmail.com
Wed Sep 27 12:40:44 UTC 2017

Hi Blair,
In the past we used the tabs but latest Horizon versions use the visibility
column/search instead.
The issue is that we would like the old images to continue to be
discoverable by everyone and have a image list that only shows the latest
If the images continue to be public they will be shown by the CLIs in the
default image-list. In our case the list was very long.

We are now using the “community” visibility to hide the old images from the
default image list. But it’s not ideal.
I will move the old spec about image lifecycle to glance.


On Wed, 27 Sep 2017 at 00:25, Blair Bethwaite <blair.bethwaite at gmail.com>

> Hi Belmiro,
> On 20 Sep. 2017 7:58 pm, "Belmiro Moreira" <
> moreira.belmiro.email.lists at gmail.com> wrote:
> > Discovering the latest image release is hard. So we added an image
> property "recommended"
> > that we update when a new image release is available. Also, we patched
> horizon to show
> > the "recommended" images first.
> There is built in support in Horizon that allows displaying multiple image
> category tabs where each takes contents from the list of images owned by a
> specific project/tenant. In the Nectar research cloud this is what we rely
> on to distinguish between "Public", "Project", "Nectar" (the base images we
> maintain), and "Contributed" (images contributed by users who wish them to
> be tested by us and effectively promoted as quality assured). When we
> update a "Nectar" or "Contributed" image the old version stays public but
> is moved into a project for deprecated images of that category, where
> eventually we can clean it up.
> > This helps our users to identify the latest image release but we
> continue to show for
> > each project the full list of public images + all personal user images.
> Could you use the same model as us?
> Cheers,
> b1airo
> __________________________________________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170927/453576e6/attachment.html>

More information about the OpenStack-dev mailing list