DNS Driver
A DNS driver will be responsible for creating CNAME records pointing to a provider's access_url returned.
The first implementation of the DNS driver will be using Rackspace's Cloud DNS API.
The Manager Driver will be responsible for calling the DNS Driver as part of the create service and delete service calls.
The configuration should allow for operators who don't wish to use an intermediary DNS record, in which case the access_url link returned to the user will be passed through from the provider. For those who use the DNS Driver, the access_url will be returned based on the CNAME record created.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Amit Gandhi
- Direction:
- Approved
- Assignee:
- Obulapathi
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
- Implemented
- Milestone target:
- kilo-1
- Started by
- Amit Gandhi
- Completed by
- Amit Gandhi
Related branches
Related bugs
Sprints
Whiteboard
Rackspace Cloud DNS has a 500 record limit.
Look into Openstack Designate
Gerrit topic: https:/
Addressed by: https:/
Added new DNS driver stub
Work Items
Dependency tree
* Blueprints in grey have been implemented.