v3 Region API

Registered by Dolph Mathews on 2013-04-24

A region is currently an attribute of an endpoint, which are only provided to clients after authenticating.

- Regions should support first-class CRUD operations on /v3/regions
- Regions should be hierarchical with an optional reference to a parent region
- It should be possible to request an unauthenticated service catalog from keystone (a vanilla deployment may only return a single identity endpoint in such a catalog).

Related Havana summit etherpad: https://etherpad.openstack.org/havana-availability-zone-and-region-management

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
None
Direction:
Approved
Assignee:
Jay Pipes
Definition:
Approved
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
Thierry Carrez on 2013-06-25
Completed by
Dolph Mathews on 2014-01-17

Related branches

Sprints

Whiteboard

Related blueprint to publish the catalog independently from auth (although the response may be based on the user's auth): https://blueprints.launchpad.net/keystone/+spec/catalog-optional

Related use case described by https://blueprints.launchpad.net/keystone/+spec/service-relationships

API: https://review.openstack.org/#/c/27563/ (abandoned)
API: https://review.openstack.org/#/c/54215/ (approved)

Gerrit topic: https://review.openstack.org/#q,topic:bp/first-class-regions,n,z

Addressed by: https://review.openstack.org/63570 (approved)
    Implements regions resource in 3.2 Catalog API

(?)

Work Items

Work items:
Add /regions resource to v3 API spec in identity-api: TODO
Add simple templated and KVS backends for region resource in keystone: TODO
Add SQL backend for region resource in keystone: TODO

This blueprint contains Public information 
Everyone can see this information.