External DNS Resolution

Registered by Carl Baldwin

This blueprint builds from where the Internal DNS Resolution blueprint leaves
off. That one reconciles the Nova VM name with the hostname assigned by
Neutron DHCP and with a DNS name that can be used to lookup the host using
Neutron's internal DNS. The next step is to integrate DNSaaS so that instances
can be found using their instance names plus a DNS domain name from outside the
cloud.

Blueprint information

Status:
Complete
Approver:
Carl Baldwin
Priority:
High
Drafter:
Carl Baldwin
Direction:
Approved
Assignee:
Miguel Lavalle
Definition:
Approved
Series goal:
Accepted for mitaka
Implementation:
Implemented
Milestone target:
milestone icon mitaka-3
Started by
Kyle Mestery
Completed by
Armando Migliaccio

Related branches

Sprints

Whiteboard

Feb-18-2016(armax): code complete, nova integration complete. Doc pending (https://review.openstack.org/#/c/280957/)

Feb 2, 2016 (carl_baldwin): The functionality for this blueprint has merged. There is some technical debt to clean up. Shall we keep this blueprint open for the technical debt, or close it and use bugs to pick up the debt?

Jan-24-2016(armax): The Neutron side is feature complete. Developer doc is inline, but this needs operator docs. Also Nova change [1] missed the opportunity to get in Mitaka.

[1] https://review.openstack.org/#/c/271578/

Dec-07-2015(armax): feature complete, needs tests and docs.

September-21 (mestery): Moving to Mitaka, per discussion.

Sept-2-2015(armax): most likely RC1 at this point.

August-26 (mestery): If this doesn't land by Liberty-3, I'd be up for getting this a FFE.

Gerrit topic: https://review.openstack.org/#q,topic:bp/external-dns-resolution,n,z

Addressed by: https://review.openstack.org/88624
    Integrate DNS resolution with an external DNS service

Addressed by: https://review.openstack.org/212213
    External DNS driver reference implementation

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.