openstack team mailing list archive

[Brian Waldon <bcwaldon@xxxxxxxxx>]

I filed this documentation bug - https://bugs.launchpad.net/glance/+bug/1054168. I'll send out what I write up later today.


On Sep 20, 2012, at 11:38 PM, Sam Morrison wrote:

> Thanks Brian, just read through your post.
> 
> I'm still a little confused with the whole v2/v1 api?
> 
> We currently have an Essex cloud in production. When we upgrade to Folsom should we be using v1 or v2 api?
> If I use the v2 api I don't need glance-registry at all? Is glance registry going away?
> glance-api should/should not point to the same DB as glance-registry?
> If you have multiple glance-apis they all need to talk to the same DB?
> 
> Sam
> 
> 
> 
> On 21/09/2012, at 3:14 PM, Brian Waldon <bcwaldon@xxxxxxxxx> wrote:
> 
>> This is an important point to bring up. I wrote about this in my Essex -> Folsom migration writeup, but I failed to mention it in the actual Glance documentation. I'll fix that.
>> 
>> To give you the answer you're looking for - the v2 API is being implemented in such way that it doesn't depend on glance-registry. In Grizzly, you'll see this become more flexible, but for now you're stuck either configuring the sql params in glance-api or disabling the v2 API altogether (enable_v2_api=False).
>> 
>> Waldon
>> 
>> 
>> On Sep 20, 2012, at 9:28 PM, Sam Morrison wrote:
>> 
>>> Have just started playing with Folsom and when configuring glance-api it now requires a database.
>>> 
>>> Just wondering if this is meant to be a separate DB to glance-registry or is it meant to point to the same one?
>>> Couldn't find any information about this in the docs.
>>> 
>>> 
>>> Thanks,
>>> Sam
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>> 
>