Yes, and this is what I’ve done: https://gerrit.onap.org/r/#/c/29063/ :)
It’s working ok now, each deployment will create two zones
$ openstack zone list
+--+-+-++++
| id
Hi Alexis,
You’d better prefix it with a random string similar to what DCAE does:
w6VA.dcaeg2.onap.org.
Which avoid zone name conflicting from different tenants on the same Designate
backend.
Here are the scripts for your to manage the DNS zones. Please list all ZONEs
from all tenants to find
Ah, actually, I might be able to re-use the random-str that was used by DCAE
for their DNS zone. Looking into this now.
> On Jan 24, 2018, at 11:48 AM, Alexis de Talhouët
> wrote:
>
> Gary, all,
>
> Actually, digging and thinking about this, the solution that has
Gary, all,
Actually, digging and thinking about this, the solution that has been
implemented in OOM to support DCAE will not work with a shared DNS Designate
backend, e.g. if multiple ONAP instances are deployed, each one of them need
its own DNS Designate. The reason for that is, to