<div dir="ltr">On Tue, Jan 10, 2017 at 1:03 PM, Flavio Percoco <span dir="ltr"><<a href="mailto:flavio@redhat.com" target="_blank">flavio@redhat.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="m_756698394356291763gmail-HOEnZb"><div class="m_756698394356291763gmail-h5">On 10/01/17 12:35 +0530, Rabi Mishra wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On Mon, Jan 9, 2017 at 4:45 PM, Flavio Percoco <<a href="mailto:flavio@redhat.com" target="_blank">flavio@redhat.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On 06/01/17 09:34 +0530, Rabi Mishra wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On Fri, Jan 6, 2017 at 4:38 AM, Emilien Macchi <<a href="mailto:emilien@redhat.com" target="_blank">emilien@redhat.com</a>><br>
wrote:<br>
<br>
Greetings Heat folks!<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
My question is simple:<br>
When do you plan to support Glance v2?<br>
<a href="https://review.openstack.org/#/c/240450/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/240450/</a><br>
<br>
The spec looks staled while Glance v1 was deprecated in Newton (and v2<br>
was started in Kilo!).<br>
<br>
<br>
Hi Emilien,<br>
</blockquote>
<br>
I think we've not been able to move to v2 due to v1/v2 incompatibility[1]<br>
with respect to the location[2] property. Moving to v2 would break all<br>
existing templates using that property.<br>
<br>
I've seen several discussions around that without any conclusion.  I think<br>
we can support a separate v2 image resource and deprecate the current one,<br>
unless there is a better path available.<br>
<br>
</blockquote>
<br>
Hi Rabi,<br>
<br>
Could you elaborate on why Heat depends on the location attribute? I'm not<br>
familiar with Heat and knowing this might help me to propose something (or<br>
at<br>
least understand the difficulties).<br>
<br>
I don't think putting this on hold will be of any help. V1 ain't coming<br>
back and<br>
the improvements for v2 are still under heavy coding. I'd probably<br>
recommend<br>
moving to v2 with a proper deprecation path rather than sticking to v1.<br>
<br>
<br>
</blockquote>
Hi Flavio,<br>
<br>
As much as we would like to move to v2, I think we still don't have a<br>
acceptable solution for the question below. There is an earlier ML<br>
thread[1], where it was discussed in detail.<br>
<br>
- What's the migration path for images created with v1 that use the<br>
location attribute pointing to an external location?<br>
</blockquote>
<br></div></div>
Moving to Glance v2 shouldn't break this. As in, Glance will still be able to<br>
pull the images from external locations.<br>
<br>
Also, to be precise more precise, you actually *can* use locations in V2.<br>
Glance's node needs to have 2 settings enabled. The first is<br>
`show_multple_locations` and the second one is a policy config[0]. It's however<br>
not recommended to expose that to end users but that's why it was shielded<br>
behind policies.<br>
<br>
I'd recommend Heat to not use locations as that will require deployers to either<br>
enable them for everyone or have a dedicate glance-api node for Heat.<br>
<br>
All that being said, switching to v2 won't prevent Glance from reading images<br>
from external locations if the image records exist already.<br>
<br>
[0] <a href="https://github.com/openstack/glance/blob/master/etc/policy.json#L16-L18" rel="noreferrer" target="_blank">https://github.com/openstack/g<wbr>lance/blob/master/etc/policy.j<wbr>son#L16-L18</a><span class="m_756698394356291763gmail-"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
While answering the above we've to keep in mind the following constraint.<br>
<br>
- Any change in the image id(new image) would potentially result in nova<br>
servers using them in the template being rebuilt/replaced, and we would<br>
like to avoid it.<br>
<br>
There was a suggestion to allow the 'copy-from'  with v2, which would<br>
possibly make it easier for us. Is that still an option?<br>
</blockquote>
<br></span>
May be, in the long future. The improvements for v2 are still under heavy<br>
development.<span class="m_756698394356291763gmail-"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I assume we can probably use glance upload api to upload the image<br>
data(after getting it from the external location) for an existing image?<br>
Last time i tried to do it, it seems to be not allowed for an 'active'<br>
image. It's  possible I'm missing something here.  We don't have a way at<br>
present,  for a user to upload an image to heat engine( not sure if we<br>
would like do to it either) or heat engine downloading the image from an<br>
'external location' and then uploading it to glance while creating/updating<br>
an image resource.<br>
</blockquote>
<br></span>
Downloading the image locally and uploading it is a workaround, yes. Not ideal<br>
but it's simple. However, you won't need it for the migration to v2, I believe,<br>
since you can re-use existing images. </blockquote><div><br></div><div>AFAIK, we can't do without it, unless 'copy-from' is made available soon, for two reasons.<br></div><div><br><div>-  Image files are always 'external' to heat-engine, unless heatclient is hacked to<br></div><div>push it to the engine along with the templates/environments, which is not something<br></div><div>we would do.<br></div><br></div><div>- To make the existing templates(with location) usable with glance v2 (newer heat versions)<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Heat won't be able to create new images<br>
and have them point to external locations, though, unless the settings I<br>
mentioned above have been enabled.<span class="m_756698394356291763gmail-"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Also, glance location api could probably have been useful here. However, we<br>
were advised in the earlier thread not to use it, as exposing the location<br>
to the end user is perceived as a security risk.<br>
</blockquote>
<br></span>
++<span class="m_756698394356291763gmail-HOEnZb"><font color="#888888"><br>
<br>
Flavio</font></span><div class="m_756698394356291763gmail-HOEnZb"><div class="m_756698394356291763gmail-h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
[1]  <a href="http://lists.openstack.org/pipermail/openstack-dev/2016-May/094598.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pip<wbr>ermail/openstack-dev/2016-May/<wbr>094598.html</a><br>
<br>
<br>
Cheers,<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Flavio<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
[1] <a href="https://wiki.openstack.org/wiki/Glance-v2-v1-client-compatability" rel="noreferrer" target="_blank">https://wiki.openstack.org/wik<wbr>i/Glance-v2-v1-client-compatab<wbr>ility</a><br>
[2] <a href="https://github.com/openstack/heat/blob/master/heat/engine/" rel="noreferrer" target="_blank">https://github.com/openstack/h<wbr>eat/blob/master/heat/engine/</a><br>
resources/openstack/glance/ima<wbr>ge.py#L107-L112<br>
<br>
<br>
As an user, I need Glance v2 support so I can remove Glance Registry<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
from my deployment. and run pure v2 everywhere in my cloud.<br>
<br>
Thanks for your help,<br>
--<br>
Emilien Macchi<br>
<br>
______________________________<wbr>______________________________<br>
______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.op<br>
<a href="http://enstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
<br>
</blockquote>
<br>
<br>
--<br>
Regards,<br>
Rabi Misra<br>
<br>
</blockquote>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscrib" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib</a><br>
e<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</blockquote>
<br>
<br>
--<br>
@flaper87<br>
Flavio Percoco<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
<br>
</blockquote>
<br>
<br>
-- <br>
Regards,<br>
Rabi Misra<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote>
<br>
<br>
-- <br>
@flaper87<br>
Flavio Percoco<br>
</div></div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="m_756698394356291763gmail_signature"><div dir="ltr"><div>Regards,</div>Rabi Misra<div><br></div></div></div>
</div></div>