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 accommodate DCAE VM resolution of .simpledemo.onap.org hosts (aai, msb, sdc, policy), OOM creates a simpledemo.onap.org. zone in which it will create the A record and a bunch of CNAME, as it was done in the DNS VM. The thing is, that simpledemo.onap.org zone will have records pointing to a given instance of ONAP, and you cannot have multiple zones sharing the same zone. Which means, we need https://gerrit.onap.org/r/#/c/28347/ for Amsterdam ASAP so OOM can be used in the OpenLab. That patch basically instantiate a small OpenStack in OOM with only the support for keystone and designate. This way, no need to rely on infrastructure dns designate support.
Alexis > On Jan 24, 2018, at 11:19 AM, Alexis de Talhouët <adetalhoue...@gmail.com> > wrote: > > Greetings, > > I’m trying to add a DNS zone in the DNS Designate of OpenLab, but I’m getting > the following failure: > > openstack zone create --email=o...@onap.org <mailto:email=o...@onap.org> > '--description=DNS zone bridging DCAE and OOM' --type=PRIMARY > simpledemo.onap.org <http://simpledemo.onap.org/>. > Unable to create zone because another tenant owns a subzone of the zone > > Can I get assistance with this? > > Thanks, > Alexis
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
