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 the one named 
“simpledemo.onap.org<http://simpledemo.onap.org>.”, and delete it . Otherwise 
you have to use some other zone name which will not conflict with this one.



### maintain designate zone

export KEYSTONE_EP=http://10.12.25.5:5000

export TOKEN=$(curl -i -X POST $KEYSTONE_EP/v3/auth/tokens -H "Content-Type: 
application/json" -H "Accept: application/json" -H "User-Agent: simpletool" -d  
'{"auth": {"identity": {"methods": ["password"],"password": {"user": {"name": 
"<your user name>","domain": {"name": "Default"}, "password": "<your 
password>"}}},"scope":{"project":{"domain":{"name":"Default"},"name": "<your 
tenant name>" } }}}'  2>&1 | grep X-Subject-Token | sed "s/^.*: //")

export DNS_EP=http://10.12.25.5:9001

curl -v -s  -H "Content-Type: application/json" -H "X-Auth-Token: $TOKEN" -X 
GET $DNS_EP/v2/zones |json_pp

{
   "zones" : [
      {
         "email" : "l...@research.att.com",
         "attributes" : {},
         "created_at" : "2018-01-24T14:41:29.000000",
         "type" : "PRIMARY",
         "transferred_at" : null,
         "description" : null,
         "links" : {
            "self" : 
"http://127.0.0.1:9001/v2/zones/93f4c9db-49e0-4662-8d32-4f1e8f9e2688";
         },
         "masters" : [],
         "pool_id" : "794ccc2c-d751-44fe-b57f-8894c9f5c842",
         "name" : "w6VA.dcaeg2.onap.org.",
         "action" : "NONE",
         "project_id" : "8b8ef50b050c47269fd4375aa2c7f7cd",
         "updated_at" : "2018-01-24T16:46:04.000000",
         "id" : "93f4c9db-49e0-4662-8d32-4f1e8f9e2688",
         "serial" : 1516812347,
         "ttl" : 3600,
         "status" : "ACTIVE",
         "version" : 46
      }
   ],
   "metadata" : {
      "total_count" : 1
   },
   "links" : {
      "self" : "http://127.0.0.1:9001/v2/zones";
   }
}

curl -v -s  -H "Content-Type: application/json" -H "X-Auth-Token: $TOKEN" -X 
GET $DNS_EP/v2/zones/93f4c9db-49e0-4662-8d32-4f1e8f9e2688

curl -v -s  -H "Content-Type: application/json" -H "X-Auth-Token: $TOKEN" -X 
DELETE $DNS_EP/v2/zones/93f4c9db-49e0-4662-8d32-4f1e8f9e2688



Best Regards,
Bin Yang,    Solution Readiness Team,    Wind River
Direct +86,10,84777126    Mobile +86,13811391682    Fax +86,10,64398189
Skype: yangbincs993

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Thursday, January 25, 2018 12:19 AM
To: onap-discuss
Subject: [onap-discuss] [OpenLab] DNS Designate zone for simpledemo.onap.org

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

Reply via email to