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 [email protected] 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 <[email protected]> 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 <[email protected]> > >> 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: [email protected] > >> > >> 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 > >> [email protected] > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > >> > >> > >> _______________________________________________ > >> OpenStack-operators mailing list > >> [email protected] > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > _______________________________________________ > > OpenStack-operators mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
