On Tue, Mar 19, 2013 at 11:51 PM, Nathanael Burton < nathanael.i.bur...@gmail.com> wrote:
> On Tue, Mar 19, 2013 at 11:39 PM, Lorin Hochstein < > lo...@nimbisservices.com> wrote: > >> Hi All: >> >> I was doing a Folsom deployment from scratch, and when I tried to launch >> an instance my compute host failed to connect to the glance server to >> download the image, instead it tried to connect to itself. >> >> I can resolve this by putting "glance_host=<ip>" into nova.conf. But I'd >> prefer if my compute host fetched this information from keystone rather >> than hard-code (hard-configure?) like this. >> >> I assume that I don't have the right config in nova.conf (a template for >> that file is here: < >> https://github.com/lorin/openstack-ansible/blob/folsom/playbooks/templates/etc/nova/nova.conf>). >> However, tracing through the nova code, I couldn't figure out where it was >> that the compute host was supposed to connect to keystone to get the right >> endpoint for glance. >> >> Where in the nova Folsom code does the nova-compute service query the >> keystone service catalog to get the endpoint for glance? >> >> > Lorin, > > I don't believe nova pulls the glance endpoint from keystone's service > catalog. I believe it's based on FLAGS.glance_api_servers here > https://github.com/openstack/nova/blob/stable/folsom/nova/image/glance.py#L73 > > Nate > > OK, so I'm not crazy, that means that I really do need to do something like: glance_api_servers=192.168.206.130:9292 or (since the default port is used) glance_host=192.168.206.130 Lorin
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
