<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I filed this documentation bug - <a href="https://bugs.launchpad.net/glance/+bug/1054168">https://bugs.launchpad.net/glance/+bug/1054168</a>. I'll send out what I write up later today.<div><br></div><div><br><div><div>On Sep 20, 2012, at 11:38 PM, Sam Morrison wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Thanks Brian, just read through your post.<br><br>I'm still a little confused with the whole v2/v1 api?<br><br>We currently have an Essex cloud in production. When we upgrade to Folsom should we be using v1 or v2 api?<br>If I use the v2 api I don't need glance-registry at all? Is glance registry going away?<br>glance-api should/should not point to the same DB as glance-registry?<br>If you have multiple glance-apis they all need to talk to the same DB?<br><br>Sam<br><br><br><br>On 21/09/2012, at 3:14 PM, Brian Waldon <<a href="mailto:bcwaldon@gmail.com">bcwaldon@gmail.com</a>> wrote:<br><br><blockquote type="cite">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.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">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).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Waldon<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Sep 20, 2012, at 9:28 PM, Sam Morrison wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Have just started playing with Folsom and when configuring glance-api it now requires a database.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Just wondering if this is meant to be a separate DB to glance-registry or is it meant to point to the same one?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Couldn't find any information about this in the docs.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Thanks,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Sam<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><br></div></blockquote></div><br></div></body></html>