8fabf5f6f9
This adds a scheduler to central to decide what pool to place a newly created zone in. Change-Id: Ie4146212209fa4b22bc271e3f4ce76104090ac9b
2.0 KiB
Pools
Contents:
pools/scheduler
Overview
In designate we support the concept of multiple "pools" of DNS Servers.
This allows operators to scale out their DNS Service by adding more pools, avoiding the scalling problems that some DNS servers have for number of zones, and the total number of records hosted by a single server.
This also allows providers to have tiers of service (i.e. the difference between GOLD vs SILVER tiers may be the number of DNS Servers, and how they are distributed around the world.)
In a private cloud situation, it allows operators to separate internal and external facing zones.
To help users create zones on the correct pool we have a "scheduler" that is responsible for examining the zone being created and the pools that are availible for use, and matching the zone to a pool.
The filters are plugable (i.e. operator replaceable) and all follow a simple interface.
The zones are matched using "zone attributes" and "pool attributes". These are key: value pairs that are attached to the zone when it is being created, and the pool. The pool attributes can be updated by the operator in the future, but it will not trigger zones to be moved from one pool to another.
Note
Currently the only zone attribute that is accepted is the pool_id attribute. As more filters are merged there will be support for dynamic filters.