Open Stack

It would be nice to have an archive status for images, where brand new
instances may not be launched off it, but where it may be used as a
reference for existing instances and snapshots.

Not sure about other folks, but we just keep piling up the old images, and
they have to remain public. There's no preventing folks from launching off
those old crusty images.

Warren

On Tue, Oct 7, 2014 at 2:21 PM, Abel Lopez <alopgeek at gmail.com> wrote:

> I've never worried about "Image not Found", as its only a UI concern. IMO
> it lets the users know something has changed. Totally optional, and the
> same effect can be gained by just renaming it -OLD and leaving it public.
> At some point, it still needs to be removed.
>
>
> On Tuesday, October 7, 2014, Sławek Kapłoński <slawek at kaplonski.pl> wrote:
>
>> Hello,
>>
>> I use Your solution and I made old images as private in such change but
>> then
>> there is one more problem: all instances spawned from that old images are
>> have
>> in horizon info about image: "not found".
>> Do You maybe know how to solve that?
>>
>> ---
>> Best regards
>> Sławek Kapłoński
>> slawek at kaplonski.pl
>>
>> Dnia wtorek, 7 października 2014 10:05:57 Abel Lopez pisze:
>> > You are correct, deleted images are not deleted from the DB, rather
>> their
>> > row has ‘deleted=1’, so specifying the UUID of another image already in
>> > glance for a new image being upload will end in tears.
>> >
>> > What I was trying to convey was, when Christian is uploading a new
>> image of
>> > the same name as an existing image, the UUID will be different. IMO, the
>> > correct process should be:
>> > 1. Make desired changes to your image.
>> > 2. Rename the existing image (e.g. Fedora-20-OLD)
>> > 3. (optional) Make the old image private ( is-public 0 )
>> > 4. Upload the new image using the desired name (e.g. Fedora-20 or like
>> > Fedora-20-LATEST )
>> >
>> > Obviously I assume there was testing for viability of the image before
>> it
>> > was uploaded to glance.
>> >
>> > For more information, be sure to catch my talk on Tuesday 9am at the
>> summit.
>> > On Oct 7, 2014, at 9:58 AM, George Shuklin <george.shuklin at gmail.com>
>> wrote:
>> > > As far as I know, it is not possible to assign uuid from deleted
>> image to
>> > > the new one, because deleted images keeps their metadata in DB.>
>> > > On 09/26/2014 04:43 PM, Abel Lopez wrote:
>> > >> Glance images are immutable. In order to update it, you should do as
>> you
>> > >> are doing, but then rename the old image, then upload the updated
>> one.
>> > >> Take note of the UUID as well.
>> > >>
>> > >> On Friday, September 26, 2014, Christian Berendt <
>> berendt at b1-systems.de>
>> > >> wrote: I'm trying to update the contents of an image, but it looks
>> like
>> > >> it is not working at all.
>> > >>
>> > >> First I upload a test image:
>> > >>
>> > >> ---snip---
>> > >> # dd if=/dev/urandom of=testing.img bs=1M count=10
>> > >> # glance image-create --disk-format raw --container-format bare
>> --name
>> > >> TESTING --file testing.img
>> > >> ---snap---
>> > >>
>> > >> Now I want to overwrite the contents of this image:
>> > >>
>> > >> ---snip---
>> > >> # dd if=/dev/urandom of=testing.img bs=1M count=20
>> > >> # glance image-update --file testing.img TESTING
>> > >> ---snap---
>> > >>
>> > >> After this call the size of the image is still the same like before
>> > >> (10485760 bytes).
>> > >>
>> > >> I do not have issues in the logfiles of glance-api and
>> glance-registry.
>> > >>
>> > >> What am I doing wrong?
>> > >>
>> > >> Is it not possible to update the contents of an image?
>> > >>
>> > >> Christian.
>> > >>
>> > >> --
>> > >> Christian Berendt
>> > >> Cloud Solution Architect
>> > >> Mail: berendt at b1-systems.de
>> > >>
>> > >> B1 Systems GmbH
>> > >> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
>> > >> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB
>> 3537
>> > >>
>> > >> _______________________________________________
>> > >> OpenStack-operators mailing list
>> > >> OpenStack-operators at lists.openstack.org
>> > >>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>> > >>
>> > >>
>> > >> _______________________________________________
>> > >> OpenStack-operators mailing list
>> > >> OpenStack-operators at lists.openstack.org
>> > >>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>> > >
>> > > _______________________________________________
>> > > OpenStack-operators mailing list
>> > > OpenStack-operators at lists.openstack.org
>> > >
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20141007/4634452e/attachment.html>