dynamic pool management

Registered by Jet

This blueprint proposes a clear differentiation of public and private pool to address the need of split horizon DNS. To allow scalability for tens of thousands of tenants who has the private versions of their DNS zones, we need to let one pool manager service be able to manage all pools, and the private pools should be able to be created through REST API, in addition to static
configurations in *designate.conf* file.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Jet
Direction:
Needs approval
Assignee:
Jet
Definition:
Approved
Series goal:
None
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.