Re: [onap-discuss] [OpenLab] DNS Designate zone for simpledemo.onap.org

2018-01-25 Thread Alexis de Talhouët 
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   | name   
 | type| serial | status | action |
+--+-+-++++
| 4e404684-c8c3-4b3c-b594-0575b7e8dd4b | 9rMR.simpledemo.onap.org.  
 | PRIMARY | 1516828782 | ACTIVE | NONE   |
| f891fe28-eec7-4c27-9ec8-b1993537477c | 
9rMR.dcaeg2.adetalhouet.oom.amsterdam.onap.org. | PRIMARY | 1516828945 | ACTIVE 
| NONE   |
+--+-+-++++

Alexis 

> On Jan 25, 2018, at 1:37 AM, Yang, Bin  wrote:
> 
> 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 
> .”, 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": "","domain": {"name": "Default"}, "password": " password>"}}},"scope":{"project":{"domain":{"name":"Default"},"name": " 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.00",
>  "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.00",
>  "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,84777126Mobile +86,13811391682Fax +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  
> '--description=DNS zone bridging DCAE and OOM' --type=PRIMARY 
> 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

Re: [onap-discuss] [OpenLab] DNS Designate zone for simpledemo.onap.org

2018-01-24 Thread Yang, Bin 
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.”, 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": 
"","domain": {"name": "Default"}, "password": ""}}},"scope":{"project":{"domain":{"name":"Default"},"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.00",
 "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.00",
 "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,84777126Mobile +86,13811391682Fax +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 
'--description=DNS zone bridging DCAE and OOM' --type=PRIMARY 
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

Re: [onap-discuss] [OpenLab] DNS Designate zone for simpledemo.onap.org

2018-01-24 Thread Alexis de Talhouët 
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 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 > > 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  
>> '--description=DNS zone bridging DCAE and OOM' --type=PRIMARY 
>> 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

Re: [onap-discuss] [OpenLab] DNS Designate zone for simpledemo.onap.org

2018-01-24 Thread Alexis de Talhouët 
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  
> 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  
> '--description=DNS zone bridging DCAE and OOM' --type=PRIMARY 
> 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