[Openstack] horizon nova endpoint usage question

Wyllys Ingersoll Wyllys.Ingersoll at evault.com
Thu May 9 23:34:34 UTC 2013


Will do, thanks.



On May 9, 2013, at 7:26 PM, "Gabriel Hurley" <Gabriel.Hurley at nebula.com<mailto:Gabriel.Hurley at nebula.com>> wrote:

If that config option is not being respected for the Nova API calls that’s a bug. Please file a ticket on Launchpad so we can track fixing it.

Thanks!


-          Gabriel

From: Openstack [mailto:openstack-bounces+gabriel.hurley=nebula.com at lists.launchpad.net] On Behalf Of Wyllys Ingersoll
Sent: Thursday, May 09, 2013 1:19 PM
To: openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Subject: [Openstack] horizon nova endpoint usage question


The Horizon UI novaclient method requests nova endpoints from the service catalog without specifying an endpoint_type parameter.  Would it be more correct for those requests to default to the 'internalURL' instead?   There are use cases where the publicURL is not exposed or defined, but if you leave publicURL undefined it causes some operations to fail because the code assumes the  publicURL is always present and valid.

The default for horizon-keystone service requests is to use the 'internalURL' and can be configured by the OPENSTACK_ENDPOINT_TYPE parameter in local_settings.py, but that doesn't seem to apply to any of the horizon-nova operations.  Perhaps it should, or another parameter could be created to affect horizon-nova interactions.

-Wyllys Ingersoll
 Evault

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130509/ecedc9ba/attachment.html>


More information about the Openstack mailing list