Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: OpenStack: Operators

glance-registry in grizzly

 

 

OpenStack operators RSS feed   Index | Next | Previous | View Threaded


jjpavlik at gmail

Aug 5, 2013, 5:11 AM

Post #1 of 9 (55 views)
Permalink
glance-registry in grizzly

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.

Cheers!

--
Pavlik Salles Juan José


jaypipes at gmail

Aug 5, 2013, 7:48 AM

Post #2 of 9 (53 views)
Permalink
Re: glance-registry in grizzly [In reply to]

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
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


jjpavlik at gmail

Aug 5, 2013, 8:54 AM

Post #3 of 9 (53 views)
Permalink
Re: glance-registry in grizzly [In reply to]

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.


2013/8/5 Jay Pipes <jaypipes [at] gmail>

> 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<OpenStack-operators [at] lists>
> http://lists.openstack.org/**cgi-bin/mailman/listinfo/**
> openstack-operators<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>
>



--
Pavlik Salles Juan José


jaypipes at gmail

Aug 5, 2013, 9:04 AM

Post #4 of 9 (53 views)
Permalink
Re: glance-registry in grizzly [In reply to]

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 <mailto:jaypipes [at] gmail>>
>
> 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
> <mailto:OpenStack-operators [at] lists>
> 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
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


moreira.belmiro.email.lists at gmail

Aug 6, 2013, 11:54 AM

Post #5 of 9 (48 views)
Permalink
Re: glance-registry in grizzly [In reply to]

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> 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 <mailto:jaypipes [at] gmail>>
>>
>> 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
>> <mailto:OpenStack-operators [at] lists>
>> 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
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


_______________________________________________
OpenStack-operators mailing list
OpenStack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


lorin at nimbisservices

Aug 6, 2013, 12:56 PM

Post #6 of 9 (48 views)
Permalink
Re: glance-registry in grizzly [In reply to]

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> 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> 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 <mailto:jaypipes [at] gmail>>
> >>
> >> 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
> >> <mailto:OpenStack-operators [at] lists>
> >>
> 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
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators [at] lists
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com


gabe.westmaas at RACKSPACE

Aug 6, 2013, 4:21 PM

Post #7 of 9 (48 views)
Permalink
Re: glance-registry in grizzly [In reply to]

You should be able to upload images to glance v2 just fine, however, nova has not yet been set up to use (optionally) glance v2 API so you can't create an image by creating an image via nova api - or get images from glance using nova using the v2 api, which is important for building servers!

Work is being done to make it so you can do so, but I think right now if you have a nova and glance, you have to have v1 enabled. I've CC'd a couple devs who may have more info about the progress being made there.

Gabe

On Aug 6, 2013, at 2:56 PM, Lorin Hochstein <lorin [at] nimbisservices<mailto:lorin [at] nimbisservices>> wrote:

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<mailto:moreira.belmiro.email.lists [at] gmail>> 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<mailto:jaypipes [at] gmail>> 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<mailto:jaypipes [at] gmail> <mailto:jaypipes [at] gmail<mailto:jaypipes [at] gmail>>>
>>
>> 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<http://openstack.org/>
>> <mailto:OpenStack-operators [at] lists<mailto:OpenStack-operators [at] lists>>
>> 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<mailto:OpenStack-operators [at] lists>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


_______________________________________________
OpenStack-operators mailing list
OpenStack-operators [at] lists<mailto:OpenStack-operators [at] lists>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com<http://www.nimbisservices.com/>
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators [at] lists<mailto:OpenStack-operators [at] lists>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


jjpavlik at gmail

Aug 6, 2013, 5:35 PM

Post #8 of 9 (48 views)
Permalink
Re: glance-registry in grizzly [In reply to]

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
El ago 6, 2013 5:05 p.m., "Lorin Hochstein" <lorin [at] nimbisservices>
escribió:

> 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> 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> 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 <mailto:jaypipes [at] gmail>>
>> >>
>> >> 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
>> >> <mailto:OpenStack-operators [at] lists>
>> >>
>> 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
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators [at] lists
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
>
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators [at] lists
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


lorin at nimbisservices

Aug 6, 2013, 5:41 PM

Post #9 of 9 (48 views)
Permalink
Re: glance-registry in grizzly [In reply to]

Gabe:

Does the glance CLI support image-create with the v2 API?

I don't see a do_image_create method in
python-glanceclient/glanceclient/v2/shell.py. I see the
glanceclient.v2.images.Controller.create method, but it doesn't look like
anything calls it in v2/shell.py.

Lorin


On Tue, Aug 6, 2013 at 7:21 PM, Gabe Westmaas
<gabe.westmaas [at] rackspace>wrote:

> You should be able to upload images to glance v2 just fine, however, nova
> has not yet been set up to use (optionally) glance v2 API so you can't
> create an image by creating an image via nova api - or get images from
> glance using nova using the v2 api, which is important for building
> servers!
>
> Work is being done to make it so you can do so, but I think right now if
> you have a nova and glance, you have to have v1 enabled. I've CC'd a couple
> devs who may have more info about the progress being made there.
>
> Gabe
>
>
> On Aug 6, 2013, at 2:56 PM, Lorin Hochstein <lorin [at] nimbisservices>
> wrote:
>
> 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> 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> 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 <mailto:jaypipes [at] gmail>>
>> >>
>> >> 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
>> >> <mailto:OpenStack-operators [at] lists>
>> >>
>> 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
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators [at] lists
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
>
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators [at] lists
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>


--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com

OpenStack operators RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.