Use service catalog to get endpoint URLs

Registered by Pushkar Umaranikar on 2017-04-08

This blueprint has been superseded. See the newer blueprint "Use keystoneauth1 Adapter for endpoints (partial)" for updated plans.

Nova uses API endpoints to establish communication with other services like
Cinder, Glance and Neutron. These endpoints are currently part of nova
configuration file. Ideally, rather than hardcoding these URL's values in
configuration file, use the service catalog to provide discoverability
for those.

Blueprint information

Status:
Complete
Approver:
Matt Riedemann
Priority:
Medium
Drafter:
Pushkar Umaranikar
Direction:
Needs approval
Assignee:
Eric Fried
Definition:
Superseded
Series goal:
None
Implementation:
Needs Code Review
Milestone target:
None
Started by
Matt Riedemann on 2017-04-19
Completed by
Eric Fried on 2017-09-01

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/use-service-catalog-for-endpoints,n,z

Addressed by: https://review.openstack.org/454983
    Use service catalog to get endpoint URLs

We should probably track the glance changes that raj_singh was already doing under this blueprint:

https://review.openstack.org/#/c/412634/

But this is approved for Pike now. -- mriedem 20170417

Addressed by: https://review.openstack.org/457746
    Fix old terminology

Addressed by: https://review.openstack.org/457747
    Implement use-service-catalog-for-endpoints differently

Addressed by: https://review.openstack.org/458257
    WIP/PoC: nova.utils.get_service_url(group)

Gerrit topic: https://review.openstack.org/#q,topic:bp/has,n,z

Addressed by: https://review.openstack.org/461481
    Updates for [glance]api_servers and ksa

This is dependent on a keystoneauth release and the final release for non-client libraries is the week of July 17 so things are getting very tight here. -- mriedem 20170713

Addressed by: https://review.openstack.org/487471
    Add requirement for os-service-types

Addressed by: https://review.openstack.org/487581
    Centralize keystoneauth1 Adapter conf option setup

Addressed by: https://review.openstack.org/487621
    WIP: Use service catalog (and discovery) for cinder endpoints

Addressed by: https://review.openstack.org/488137
    nova.utils.get_endpoint_data()

Addressed by: https://review.openstack.org/489666
    DNM: Refactor get_endpoint_data to accept service_type

Addressed by: https://review.openstack.org/490057
    WIP Use auth from context for glance api servers

There are still open changes for this and we're past the feature freeze for Pike, so I'm going to defer this to Queens. Please submit the spec for Queens in the nova-specs repo and make sure to update it in case anything in the design has changed. -- mriedem 20170803

Gerrit topic: https://review.openstack.org/#q,topic:bp/use-service-catalog-for-blueprints,n,z

Addressed by: https://review.openstack.org/492247
    Use ksa adapter for placement conf & requests

Gerrit topic: https://review.openstack.org/#q,topic:bp/use-ksa-adapter-for-endpoints,n,z

Addressed by: https://review.openstack.org/500190
    Spec: Use keystoneauth1 Adapter for endpoints

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.