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@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
