multi_cloud : looking up services from keystone catalog - possible issues

[Davanum Srinivas (DIMS)]

Problem #1 : OpenStackClients uses auth_url from RequestContext to look up say Nova Service [1]. Looking at reviews in the blue print [2], i can't seem to find where we pull the auth_url from incoming request (and stuff it into RequestContext) so we look in the correct keystone catalog and not use hard coded auth_* from heat.conf

Problem #2 : get_admin_context creates a RequestContext that does not have access to the auth_url from incoming request, Don't we need to know which stack is running on which keystone/nova? [4]

Thanks,
dims

[1] https://github.com/openstack/heat/blob/master/heat/engine/clients.py#L113
[2] https://blueprints.launchpad.net/heat/+spec/heat-multicloud
[3] https://github.com/openstack/heat/blob/master/heat/common/context.py#L107
[4] https://github.com/openstack/heat/blob/master/heat/engine/service.py#L198

[Steve Baker (steve-stevebaker)]

heat.common.auth_url contains the middleware filter which adds the auth url to the request context, either from the request or from heat.conf.

As an aside, heat-standalone running on a single OpenStack should work, but multicloud development has stalled until blueprint multi-region-support has landed, since multi-cloud is an extension of multi-region and we want to get multi-region working correctly first.