<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Yep. Migration is just a resize (from flavor to same flavor).
Instance disk transferred by scp/rsync.<br>
<br>
<div class="moz-cite-prefix">On 10/09/2014 05:36 AM, Joe Topjian
wrote:<br>
</div>
<blockquote
cite="mid:CA+y7hvj_Z_0SsGJ6Yfdy-SYBbZYZojaXD3Er7+rq2yTCgt5GQg@mail.gmail.com"
type="cite">
<div dir="ltr">Ah - so it sounds like the issue might be local to
just non-live/cold migration? The type that requires SSH key
exchange? That's what resizing uses behind the scenes, so it
makes sense that it would fail as well.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Oct 8, 2014 at 8:30 PM, George
Shuklin <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:george.shuklin@gmail.com" target="_blank">george.shuklin@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">We using Havana, with raw images and non-live
migration (rsync/scp on halted VMs).</p>
<p dir="ltr">Migration happens, but during instance start
nova-compute fail to find image locally and in glance.</p>
<p dir="ltr">I saw Icehouse patch to made a copy of image
from original host but it looks too slow for me (for the
raw disk of instance booted from snapshot it gonna be
double migration time).</p>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_quote">On Oct 8, 2014 8:19 PM, "Joe
Topjian" <<a moz-do-not-send="true"
href="mailto:joe@topjian.net" target="_blank">joe@topjian.net</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">We just ran some tests on our
production Icehouse environment and can confirm
that:
<div><br>
</div>
<div>* Snapshotting an instance based on a deleted
image works</div>
<div>* Snapshotting an instance based on a
public-turned-private image works</div>
<div>* Block migration of an instance based on a
deleted image works</div>
<div><br>
</div>
<div>This environment does not utilize _base
images.</div>
<div><br>
</div>
<div>We didn't do any resizing tests as we do not
have our environment configured to allow it. At
the moment, if a user tries resizing they
receive an error message. It's not a friendly
way to disable an action so we plan on just
removing the option from Horizon altogether.</div>
<div><br>
</div>
<div>We also tested the following with an older
Grizzly environment that supports live
migration:</div>
<div><br>
</div>
<div>* Snapshotting an instance based on a deleted
image (and base image) works</div>
<div>* Live migrating an instance based on a
deleted image (and base image) works</div>
<div><br>
</div>
<div>Resizing is not supported in this environment
as well.</div>
<div><br>
</div>
<div>I'm curious about your environment where
these actions are failing for you?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Joe</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Oct 7, 2014 at
3:03 PM, George Shuklin <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:george.shuklin@gmail.com"
target="_blank">george.shuklin@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">Yep, this bug is still
actual. Resize, migration and so on does not
work if original image is deleted. And 'I will
never remove any public image' will not helps,
because if user restore instance from snapshot
and remove snapshot it will cause error too.
That looks stupid in the light of (our) raw
disk format, where 'base copy' just never
used.<br>
<br>
Error is harmless and can be fixed by<br>
<br>
nova reset-state --active UUID<br>
(optionally)<br>
nova stop UUID<br>
nova start UUID<br>
<br>
But it's still annoying because user can not
fix it own instance without administrator
intervention.<br>
<br>
We have plans to fix it for havana (it cause
disturbance for as and inconvenience for our
customers), but fix will not be accepted by
upstream (they drops upstream support ASAP),
so I think we should switch to old-style
maillist based patch RFC.<br>
<br>
On 10/07/2014 10:16 PM, Jan van Eldik wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
Hi,<br>
<br>
Please note the issue reported in <a
moz-do-not-send="true"
href="https://bugs.launchpad.net/nova/+bug/1160773"
target="_blank">https://bugs.launchpad.net/nova/+bug/1160773</a>:
"Cannot resize instance if base image is not
available"<br>
<br>
AFAIK it is still the case that instances
cannot be resized or migrated<br>
once the image from which it has been
created has been deleted.<br>
<br>
cheers, Jan<br>
<br>
On 10/07/2014 09:01 PM, Abel Lopez wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
Right, and I think the best thing about
marking a deprecated image private is that<br>
new instances can’t select that image
unless the tenant is an image-member of
it.<br>
So if a specific tenant has some “real
valid” need to use the old version (I
can’t imagine why), they could find it in
“Project Images” instead of “Public”.<br>
<br>
On Oct 7, 2014, at 11:57 AM, Sławek
Kapłoński <<a moz-do-not-send="true"
href="mailto:slawek@kaplonski.pl"
target="_blank">slawek@kaplonski.pl</a>>
wrote:<br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
Hello,<br>
<br>
Yes, I agree that this is not big
problem when there is info "Image not
found"<br>
in horizon but I saw this discussion and
I thought that I will ask about that<br>
:) It would be nice to have some other
info like for example: "Image 1<br>
(archived)" or something like that :)<br>
<br>
---<br>
Best regards<br>
Sławek Kapłoński<br>
<a moz-do-not-send="true"
href="mailto:slawek@kaplonski.pl"
target="_blank">slawek@kaplonski.pl</a><br>
<br>
Dnia wtorek 07 październik 2014 18:21:13
piszesz:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
I've never worried about "Image not
Found", as its only a UI concern. IMO<br>
it lets the users know something has
changed. Totally optional, and the<br>
same effect can be gained by just
renaming it -OLD and leaving it
public.<br>
At some point, it still needs to be
removed.<br>
<br>
On Tuesday, October 7, 2014, Sławek
Kapłoński <<a
moz-do-not-send="true"
href="mailto:slawek@kaplonski.pl"
target="_blank">slawek@kaplonski.pl</a>>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
Hello,<br>
<br>
I use Your solution and I made old
images as private in such change but<br>
then<br>
there is one more problem: all
instances spawned from that old
images are<br>
have<br>
in horizon info about image: "not
found".<br>
Do You maybe know how to solve that?<br>
<br>
---<br>
Best regards<br>
Sławek Kapłoński<br>
<a moz-do-not-send="true"
href="mailto:slawek@kaplonski.pl"
target="_blank">slawek@kaplonski.pl</a>
<a class="moz-txt-link-rfc2396E" href="javascript:;"><javascript:;></a><br>
<br>
Dnia wtorek, 7 października 2014
10:05:57 Abel Lopez pisze:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
You are correct, deleted images
are not deleted from the DB,
rather<br>
their<br>
row has ‘deleted=1’, so specifying
the UUID of another image already
in<br>
glance for a new image being
upload will end in tears.<br>
<br>
What I was trying to convey was,
when Christian is uploading a new
image<br>
</blockquote>
<br>
of<br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
the same name as an existing
image, the UUID will be different.
IMO, the<br>
correct process should be:<br>
1. Make desired changes to your
image.<br>
2. Rename the existing image (e.g.
Fedora-20-OLD)<br>
3. (optional) Make the old image
private ( is-public 0 )<br>
4. Upload the new image using the
desired name (e.g. Fedora-20 or
like<br>
Fedora-20-LATEST )<br>
<br>
Obviously I assume there was
testing for viability of the image
before<br>
it<br>
was uploaded to glance.<br>
<br>
For more information, be sure to
catch my talk on Tuesday 9am at
the<br>
</blockquote>
<br>
summit.<br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
On Oct 7, 2014, at 9:58 AM, George
Shuklin <<a
moz-do-not-send="true"
href="mailto:george.shuklin@gmail.com"
target="_blank">george.shuklin@gmail.com</a><br>
</blockquote>
<br>
<a class="moz-txt-link-rfc2396E" href="javascript:;"><javascript:;></a>> wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
As far as I know, it is not
possible to assign uuid from
deleted image<br>
</blockquote>
</blockquote>
<br>
to<br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
the new one, because deleted
images keeps their metadata in
DB.><br>
<br>
On 09/26/2014 04:43 PM, Abel
Lopez wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
Glance images are immutable.
In order to update it, you
should do as<br>
</blockquote>
</blockquote>
</blockquote>
<br>
you<br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
are doing, but then rename the
old image, then upload the
updated<br>
one.<br>
Take note of the UUID as well.<br>
<br>
On Friday, September 26, 2014,
Christian Berendt <<br>
</blockquote>
</blockquote>
</blockquote>
<br>
<a moz-do-not-send="true"
href="mailto:berendt@b1-systems.de"
target="_blank">berendt@b1-systems.de</a>
<a class="moz-txt-link-rfc2396E" href="javascript:;"><javascript:;></a>><br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
wrote: I'm trying to update
the contents of an image, but
it looks<br>
</blockquote>
</blockquote>
</blockquote>
<br>
like<br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
it is not working at all.<br>
<br>
First I upload a test image:<br>
<br>
---snip---<br>
# dd if=/dev/urandom
of=testing.img bs=1M count=10<br>
# glance image-create
--disk-format raw
--container-format bare<br>
--name<br>
TESTING --file testing.img<br>
---snap---<br>
<br>
Now I want to overwrite the
contents of this image:<br>
<br>
---snip---<br>
# dd if=/dev/urandom
of=testing.img bs=1M count=20<br>
# glance image-update --file
testing.img TESTING<br>
---snap---<br>
<br>
After this call the size of
the image is still the same
like before<br>
(10485760 bytes).<br>
<br>
I do not have issues in the
logfiles of glance-api and<br>
</blockquote>
</blockquote>
</blockquote>
<br>
glance-registry.<br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
What am I doing wrong?<br>
<br>
Is it not possible to update
the contents of an image?<br>
<br>
Christian.<br>
<br>
-- <br>
Christian Berendt<br>
Cloud Solution Architect<br>
Mail: <a
moz-do-not-send="true"
href="mailto:berendt@b1-systems.de"
target="_blank">berendt@b1-systems.de</a>
<a class="moz-txt-link-rfc2396E" href="javascript:;"><javascript:;></a><br>
<br>
B1 Systems GmbH<br>
Osterfeldstraße 7 / 85088
Vohburg / <a
moz-do-not-send="true"
href="http://www.b1-systems.de"
target="_blank">http://www.b1-systems.de</a><br>
GF: Ralph Dehner /
Unternehmenssitz: Vohburg /
AG: Ingolstadt,HRB<br>
3537<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing
list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org"
target="_blank">OpenStack-operators@lists.openstack.org</a>
<a class="moz-txt-link-rfc2396E" href="javascript:;"><javascript:;></a><br>
</blockquote>
</blockquote>
</blockquote>
<br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
<br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
_______________________________________________<br>
OpenStack-operators mailing
list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org"
target="_blank">OpenStack-operators@lists.openstack.org</a>
<a class="moz-txt-link-rfc2396E" href="javascript:;"><javascript:;></a><br>
</blockquote>
</blockquote>
</blockquote>
<br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
<br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org"
target="_blank">OpenStack-operators@lists.openstack.org</a>
<a class="moz-txt-link-rfc2396E" href="javascript:;"><javascript:;></a><br>
</blockquote>
</blockquote>
<br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
<br>
</blockquote>
</blockquote>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org"
target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote>
<br>
<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org"
target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
</blockquote>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org"
target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote>
<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org"
target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>