[Openstack-operators] How to handle updates of public images?

Louis Taylor kragniz at gmail.com
Sat Feb 7 20:35:32 UTC 2015

On Sat, Feb 07, 2015 at 10:36:55AM -0800, Igor Bolotin wrote:
> Going back to the idea of archiving images and not allowing launch of new
> VMs and hiding archived images by default in Horizon/CLI (maybe still can
> list/show if requested, possibly admin function only). Would it make sense
> to propose this as a blueprint for the next release?

There is currently a spec under review [1] for a new type of image which covers
some of the usecases in this thread. Momentumn has fallen off on working on it,
but with a little luck it should be in the Kilo release. Further comments and
feedback on that spec may be helpful in moving it along and getting it ready in

The basic idea is that the old images are moved from being public images to
'community' images, which remain bootable, but not visible in normal user


[1] https://review.openstack.org/#/c/124050/11
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150207/2e7b137e/attachment.pgp>

More information about the OpenStack-operators mailing list