diff options
| author |   Lusheng Ji <lji@research.att.com> | 2017-11-01 13:49:33 -0400 |
|---|---|---|
| committer | Lusheng Ji <lji@research.att.com> | 2017-11-01 13:53:03 -0400 |
| commit | 74cb51c88f99f9128d43f4645c6f2aa86163d43b (patch) | |
| tree | 4f2dd8aed9d854f832cf5a7df5435e75b8ec6300 /heat/ONAP/onap_openstack_nofloat.yaml | |
| parent | 5d9f3b5b32a107ec482f7192118891a000baf566 (diff) | |
Add support for DNS zone fusion
This submission address the "fusion" between DNS service zones
between DCAE and rest of ONAP R1. In ONAP R1 each ONAP deployment
runs its own private DNS server; DCAE use Designate DNS as a Service.
The VMs on both sides need to be able to communicate with each other
by hostnames. This submission modifies the ONAP private DNS server
so it uses the DNS server behind the Designate as the forwarder. For
ONAP->DCAE communication, host names will be resolved by Designate DNS
server; for DCAE->ONAP communication, since DCAE VMs also use the ONAP
private DNS server as first name server, it is not a problem.
Issue-Id: DCAEGEN2-187
Change-Id: Ia54cd41f33b446d406a69868598ae1a8c0cdea8d
Signed-off-by: Lusheng Ji <lji@research.att.com>
Diffstat (limited to 'heat/ONAP/onap_openstack_nofloat.yaml')
0 files changed, 0 insertions, 0 deletions