<p>So i should keep v1 API and glance-registry just to avoid headaches with nova, seems a good reason to me. Once i get confortable with the deploy i'll start working on deleting unused services/apis</p>
<div class="gmail_quote">El ago 6, 2013 5:05 p.m., "Lorin Hochstein" <<a href="mailto:lorin@nimbisservices.com">lorin@nimbisservices.com</a>> escribió:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">image-create seems like a pretty glaring omission. Do you know why it hasn't been implemented in glance API v2?<div><br></div><div>Lorin</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Aug 6, 2013 at 2:54 PM, Belmiro Moreira <span dir="ltr"><<a href="mailto:moreira.belmiro.email.lists@gmail.com" target="_blank">moreira.belmiro.email.lists@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
before moving to glance API v2 make sure that you don't need something that is not implement yet in the glance client (for the case you use it).<br>
For example image-create is not there…<br>
<br>
cheers,<br>
Belmiro<br>
<div><div><br>
<br>
On Aug 5, 2013, at 18:04 , Jay Pipes <<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>> wrote:<br>
<br>
> On 08/05/2013 11:54 AM, Juan José Pavlik Salles wrote:<br>
>> Thanks Jay! How can i be sure about the API version my clients are<br>
>> using? So far i think my only glance clients are keystone and nova.<br>
><br>
> 1) Set OS_IMAGE_API_VERSION=2 in your various RC files.<br>
> 2) Provide api_version=2 when communicating with the glanceclient<br>
><br>
> Easy way to determine if removing glance-registry will work for you:<br>
><br>
> 1) Shut down glance-registry processes.<br>
> 2) Wait to see if your helpdesk phone starts ringing. :)<br>
><br>
> Best,<br>
> -jay<br>
><br>
>> 2013/8/5 Jay Pipes <<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a> <mailto:<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>>><br>
>><br>
>> On 08/05/2013 08:11 AM, Juan José Pavlik Salles wrote:<br>
>><br>
>> Hi guys, i've a little and maybe easy question for you. I'm<br>
>> deploying<br>
>> grizzly in a few servers and i'd like to know if a really need<br>
>> glance-registry as a service to use glance-api. I've read that i<br>
>> don't<br>
>> need it if i use glance-api V2, is that correct? I could check<br>
>> my api<br>
>> version and switch to V2 and get rid of it.<br>
>><br>
>><br>
>> I recently wondered the same question when we were deploying<br>
>> Grizzly. After a cursory look through the code, it seems like the<br>
>> Glance Registry is still used if a call comes in to the v1/ API. So,<br>
>> if any of your clients still use the v1/ API, and you include the<br>
>> v1/ API in your glance-api-paste.ini pipelines, you will need to<br>
>> keep glance-registry in place.<br>
>><br>
>> Best,<br>
>> -jay<br>
>><br>
>><br>
>> _________________________________________________<br>
>> OpenStack-operators mailing list<br>
>> OpenStack-operators@lists.__<a href="http://openstack.org" target="_blank">openstack.org</a><br>
>> <mailto:<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a>><br>
>> <a 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>
>> <<a 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>
>><br>
>><br>
>><br>
>> --<br>
>> Pavlik Salles Juan José<br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
> <a 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>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a 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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Lorin Hochstein<br><div>Lead Architect - Cloud Services</div><div>Nimbis Services, Inc.</div><div><a href="http://www.nimbisservices.com" target="_blank">www.nimbisservices.com</a></div>
</div>
</div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a 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></div>