Feature Overview 

Private DNS zones for RHOSO deployments. Current designated support for DNS is limited to global DNS zones, which are visible and apply at the cluster level. 

Private DNS zones are applicable/relevant for VPC deployments. RHOSO can currently support most of the functionality for VPC implementation with the assumption that Openstack project be considered as equivalent to VPC. However private DNS zones is a feature gap in the VPC story for RHOSO. Following are the list of requirements for the functional operation. 

1. The ability to create private DNS servers that can be mapped to or unmapped from one or more neutron networks.
2. Each private DNS server can have zero or more zones.
3. Queries from instances on a network with one or more private DNS zones must query the private DNS server for records in the private DNS zones. Requests for other zones should be handled as they are today.
4. Queries from instances outside of a network that is mapped to the private DNS server are not possible.
5. Private DNS zones must support wildcard DNS recordsets, with exact matches taking priority.
6. Private DNS zones must support the following record types: A, AAAA, CNAME, MX, NS, PTR, SOA, SRV, and TXT.
7. Private DNS servers, zones, and recordsets must be owned by the same project as the networks they are mapped to.
8. There must be quota management for the maximum number of private DNS servers, zones, and recordsets.

Goals

• Ability to configure and deploy private DNS zones at the tenant level with capabilities as listed above as part of DNSaaS (Designate)

Requirements 

Done - Acceptance Criteria 

• Functional Operation of the feature
• Testing with multiple tenants at the same time to support the operations of the use cases defined 
• Regression and automation for the test suites
• Documentation for new feature overview, workflow, configuration, troubleshooting 
• Release Notes

Use Cases 

Use Case 1: Communication within the VPC without going to external network or internet

Use Case 2: Backup/Failover without any code change for service endpoint or disruption

Use Case 3: Accessing Cloud Services without going to external services (DNS)

Documentation Considerations 

• Documentation for new feature overview, workflow, configuration, troubleshooting 

Background and Strategic Fit 

Tactical - Explicit customer requests from existing strategic customers

Strategic - Strengthens the VPC value proposition with potential to acquire more customers and market share from competition. 

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

Reference: Design Options Document