OpenStack Identity (keystone)

Provide a DNS backend to the Service Catalog

Registered by Adam Young

DNS is the standard way to do most of the operations that the Keystone Catalog needs to perform. IN order to move toward standardizing how Open Stack and DNS interoperate, Keystone will be able to store the the Service Catalog in DNS.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Not
Drafter:
Adam Young
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Not started
Milestone target:
None
Completed by
Lance Bragstad

Related branches

Sprints

Whiteboard

Rather than "store the Service Catalog in DNS" I'd suggest simply "reading the Service Catalog from DNS" to avoid a chicken and egg problem between keystone setup and the catalog backend being expected to be a client of moniker -dolph

We can certainly do a "read Only" backend first. I think we would want to be able to update records in DNS via DNS update second, and then Moniker would be an alternative protocol as a third phase. -Adam

let's limit the scope of this bp to read-only then as it's obviously easier to achieve; crud calls against the catalog can raise 501/403 as appropriate

(lbragstad): It's been a while since this has been updated. I think the use case is still applicable and we should continue the conversation in openstack/keystone-specs [0], where we can discuss it in greater detail.

[0] http://specs.openstack.org/openstack/keystone-specs/specs/template.html

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.