yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #68392
[Bug 1707860] Re: Ironic driver should use internal endpoints
Reviewed: https://review.openstack.org/488137
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0a8f019be0f75005929724df3238b0a1ed49c88d
Submitter: Jenkins
Branch: master
commit 0a8f019be0f75005929724df3238b0a1ed49c88d
Author: Eric Fried <efried@xxxxxxxxxx>
Date: Wed Apr 19 17:03:17 2017 -0500
nova.utils.get_ksa_adapter()
Provide a new method:
nova.utils.get_ksa_adapter(service_type, ks_auth=None, ks_session=None,
min_version=None, max_version=None))
...to configure a keystoneauth1 Adapter for a service. The Adapter, and
its component keystoneauth1 artifacts not passed into the method, are
loaded based on options in the conf group corresponding to the specified
service_type.
The ultimate goal is to replace the various disparate mechanisms used by
different services to do endpoint URL and version discovery. In Queens,
the original mechanisms will still take precedence, but (other than
[glance]api_servers - see the spec) will be deprecated. In Rocky, the
deprecated options will be removed.
This change incorporates the above utility into endpoint discovery for
glance and ironic. Future change sets will do the same for other
services (cinder, neutron, placement).
Change-Id: If625411f40be0ba642baeb02950f568f43673655
Partial-Implements: bp use-ksa-adapter-for-endpoints
Closes-Bug: #1707860
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1707860
Title:
Ironic driver should use internal endpoints
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Currently `client_wrapper` doesn't specify `os_endpoint_type` when
creating ironic client which defaults to 'publicURL'. This causes
nova-compute to use public endpoints from catalog for ironic api
access. This in turn causes problems as nova-compute nodes don't need
to have public interfaces and ironic services can be running on remote
nodes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1707860/+subscriptions
References