Open Stack

image-create seems like a pretty glaring omission. Do you know why it
hasn't been implemented in glance API v2?

Lorin


On Tue, Aug 6, 2013 at 2:54 PM, Belmiro Moreira <
moreira.belmiro.email.lists at gmail.com> wrote:

> Hi,
> 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).
> For example image-create is not there…
>
> cheers,
> Belmiro
>
>
> On Aug 5, 2013, at 18:04 , Jay Pipes <jaypipes at gmail.com> wrote:
>
> > On 08/05/2013 11:54 AM, Juan José Pavlik Salles wrote:
> >> Thanks Jay! How can i be sure about the API version my clients are
> >> using? So far i think my only glance clients are keystone and nova.
> >
> > 1) Set OS_IMAGE_API_VERSION=2 in your various RC files.
> > 2) Provide api_version=2 when communicating with the glanceclient
> >
> > Easy way to determine if removing glance-registry will work for you:
> >
> > 1) Shut down glance-registry processes.
> > 2) Wait to see if your helpdesk phone starts ringing. :)
> >
> > Best,
> > -jay
> >
> >> 2013/8/5 Jay Pipes <jaypipes at gmail.com <mailto:jaypipes at gmail.com>>
> >>
> >>    On 08/05/2013 08:11 AM, Juan José Pavlik Salles wrote:
> >>
> >>        Hi guys, i've a little and maybe easy question for you. I'm
> >>        deploying
> >>        grizzly in a few servers and i'd like to know if a really need
> >>        glance-registry as a service to use glance-api. I've read that i
> >>        don't
> >>        need it if i use glance-api V2, is that correct? I could check
> >>        my api
> >>        version and switch to V2 and get rid of it.
> >>
> >>
> >>    I recently wondered the same question when we were deploying
> >>    Grizzly. After a cursory look through the code, it seems like the
> >>    Glance Registry is still used if a call comes in to the v1/ API. So,
> >>    if any of your clients still use the v1/ API, and you include the
> >>    v1/ API in your glance-api-paste.ini pipelines, you will need to
> >>    keep glance-registry in place.
> >>
> >>    Best,
> >>    -jay
> >>
> >>
> >>    _________________________________________________
> >>    OpenStack-operators mailing list
> >>    OpenStack-operators at lists.__openstack.org
> >>    <mailto:OpenStack-operators at lists.openstack.org>
> >>
> http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-operators
> >>    <
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>
> >>
> >>
> >>
> >>
> >> --
> >> Pavlik Salles Juan José
> >
> >
> > _______________________________________________
> > 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
>



-- 
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130806/d8ba0097/attachment.html>