Gary, Have you properly configured those parameters in the onap-parameters.yaml file:
DNSAAS_API_VERSION: "" DNSAAS_REGION: "" DNSAAS_KEYSTONE_URL: "" DNSAAS_TENANT_ID: "" DNSAAS_TENANT_NAME: "" DNSAAS_USERNAME: "" DNSAAS_PASSWORD: “" Those need to reflect the OpenStack instance providing DNS Designate. The OpenLab is configured so the tenant names are replicated, but the tenant ID is not the same. Please double check this. OpenLab has two instances. http://10.12.25.2 on which you deploy ONAP, and http://10.12.25.5 providing DNS Designate support. To get your tenant id for a given tenant name, log in the http://10.12.25.5 instance. Based on those variables, we will setup the DNS-openrc-v2.sh <https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/config/docker/init/src/config/dcaegen2/heat/DNS-openrc-v2.sh;h=9c9e3f06346b32e6a6cdc7e8e53ddcc90b3e5399;hb=refs/heads/amsterdam> and DNS-openrc-v3.sh <https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/config/docker/init/src/config/dcaegen2/heat/DNS-openrc-v3.sh;h=eebf8357e1fa6e55b2ff83c60bc775a69b9b16ad;hb=refs/heads/amsterdam> files to be used to authenticate to the OpenStack (see line 156 <https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/config/docker/init/src/config/dcaegen2/heat/entrypoint.sh;h=bbf47a9bac6b98e6bd52ae3e8af309816097464a;hb=refs/heads/amsterdam>), enabling the pod to use the openstack cli instead of multicloud. I understand this is by-passing the multicloud apis, but it was easier for me to set this up. Any contribution to change this is welcome :) But my hope is, this will go away when OOM will provide DNS Designate itself (see OOM-588 <https://jira.onap.org/browse/OOM-588>) so ppl won’t have to provide it in their infra. I have tested this in OpenLab, under the OOM tenant, it can authenticate fine. The issue is, I’m facing this issue now: ++ openstack zone create [email protected] '--description=DNS zone bridging DCAE and OOM' --type=PRIMARY simpledemo.onap.org. -f=yaml -c id Zone simpledemo.onap.org. doens't exist, creating ... ++ awk '{ print $2} ' Unable to create zone because another tenant owns a subzone of the zone Regarding the `sed: can’t read /opt/robot/vm_properties.py: No such file or directory`, thanks for reporting this, it’s an oversight, sorry about that. Working on too many things at the same time. Fix here: https://gerrit.onap.org/r/#/c/29039/ Regarding the robot log, you can use the init_robot tag that let you then browse the robot logs through the browser at http://<k8s-host>:30209/logs/ I didn’t know ppl where going in the persisted data. But probably I should revert this change to persist the logs again. Thanks, Alexis > On Jan 24, 2018, at 10:42 AM, Gary Wu <[email protected]> wrote: > > Sorry, one more thing: since yesterday I can no longer retrieve the robot > test logs from /dockerdata-nfs/onap/robot/eteshare/logs/. Not sure if this > is related either. > > Thanks, > Gary > > From: Gary Wu > Sent: Tuesday, January 23, 2018 6:13 PM > To: 'Alexis de Talhouët' <[email protected] > <mailto:[email protected]>> > Cc: 'BRIAN D FREEMAN' <[email protected] <mailto:[email protected]>>; 'PLATANIA, > MARCO (MARCO)' <[email protected] > <mailto:[email protected]>>; '[email protected] > <mailto:[email protected]>' <[email protected] > <mailto:[email protected]>> > Subject: RE: [onap-discuss] [OOM] DCAE config in windriver > > Incidentally I’m also getting this error from entrypoint.sh; not sure if it’s > related to this set of changes: > > sed: can’t read /opt/robot/vm_properties.py: No such file or directory > > Thanks, > Gary > > From: Gary Wu > Sent: Tuesday, January 23, 2018 4:41 PM > To: 'Alexis de Talhouët' <[email protected] > <mailto:[email protected]>> > Cc: BRIAN D FREEMAN <[email protected] <mailto:[email protected]>>; PLATANIA, MARCO > (MARCO) <[email protected] <mailto:[email protected]>>; > [email protected] <mailto:[email protected]> > Subject: RE: [onap-discuss] [OOM] DCAE config in windriver > > Hi Alexis, > > Despite having DNS_PROXY_ENABLE turned on, I’m observing the following: > > dcaegen2/heat/entrypoint.sh repeatedly tries to configure Designate directly > via “openstack recordset” commands and failing with authentication errors. > Is this supposed to be happening? The multicloud proxy endpoint seems to be > properly configured in onap_dcae.env, but this endpoint doesn’t seem to be > used by entrypoint.sh so I’m not sure how the DNS record requests are > supposed to get into the proxy. > > Because of the DNS record creation issue above, the dcae-bootstrap VM is > still stuck due to inability to resolve “vm1.aai.simpledemo.onap.org > <http://vm1.aai.simpledemo.onap.org/>”. > > Thanks, > Gary > > > From: Alexis de Talhouët [mailto:[email protected] > <mailto:[email protected]>] > Sent: Tuesday, January 23, 2018 9:34 AM > To: Gary Wu <[email protected] <mailto:[email protected]>> > Cc: BRIAN D FREEMAN <[email protected] <mailto:[email protected]>>; PLATANIA, MARCO > (MARCO) <[email protected] <mailto:[email protected]>>; > [email protected] <mailto:[email protected]> > Subject: Re: [onap-discuss] [OOM] DCAE config in windriver > > Right, as I said, expect this to be merged in a couple of hours. > > Thanks, > Alexis > > > On Jan 23, 2018, at 12:29 PM, Gary Wu <[email protected] > <mailto:[email protected]>> wrote: > > The first patch depends on the second, but the second has not yet been merged > yet? I guess I should wait for the second one to merged first? > > Thanks, > Gary > > From: Alexis de Talhouët [mailto:[email protected] > <mailto:[email protected]>] > Sent: Tuesday, January 23, 2018 8:53 AM > To: Gary Wu <[email protected] <mailto:[email protected]>> > Cc: BRIAN D FREEMAN <[email protected] <mailto:[email protected]>>; PLATANIA, MARCO > (MARCO) <[email protected] <mailto:[email protected]>>; > [email protected] <mailto:[email protected]> > Subject: Re: [onap-discuss] [OOM] DCAE config in windriver > > Gary, > > This patch fixes the OOM to enable proxy DNS designate setup: > https://gerrit.onap.org/r/#/c/28933/ <https://gerrit.onap.org/r/#/c/28933/> > > I’ve tested in my environment, it’s working. > > Please try again when you have some time. Note, the onap-parameters.yaml have > changed a little bit to enable this. See https://gerrit.onap.org/r/#/c/28591/ > <https://gerrit.onap.org/r/#/c/28591/> > > Expect this to be merge in a couple of hours. > > Thanks, > Alexis > > > On Jan 22, 2018, at 3:57 PM, Alexis de Talhouët <[email protected] > <mailto:[email protected]>> wrote: > > Gary, > > OOM doesn’t yet support the proxied solution. This is being worked on; until > this is not fix, you cannot use Wind-River lab to deploy OOM with DCAENGEN2. > Expect the fix to be submit in the next couple of days. > > Thanks, > Alexis > > > On Jan 22, 2018, at 3:17 PM, Gary Wu <[email protected] > <mailto:[email protected]>> wrote: > > Hi Alexis, > > Yes, I’m able to deploy DCAEGEN2 on a (non-Wind River) system with Designate > installed. My question is specifically on the Wind River lab. Can we use > Designate there? So far what I see is “public endpoint for dns service in > RegionOne region not found”, so it seems like we cannot. Or is there a > special Designate endpoint/config available? > > Has anyone successfully deployed OOM with DCAEGEN2 in the Wind River lab, > with or without the proxy solution? > > Thanks, > Gary > > > From: Alexis de Talhouët [mailto:[email protected] > <mailto:[email protected]>] > Sent: Monday, January 22, 2018 11:58 AM > To: Gary Wu <[email protected] <mailto:[email protected]>> > Cc: BRIAN D FREEMAN <[email protected] <mailto:[email protected]>>; PLATANIA, MARCO > (MARCO) <[email protected] <mailto:[email protected]>>; > [email protected] <mailto:[email protected]> > Subject: Re: [onap-discuss] [OOM] DCAE config in windriver > > Hi Gary, > > I noticed the proxy solution that DCAEGEN2 offers is not fully working yet > with OOM. What is working is having DCAE on the same OpenStack as DNS > Designate. I’m currently in the process of addressing this. > > Regarding your question about how "vm1.aai.simpledemo.onap.org > <http://vm1.aai.simpledemo.onap.org/> gets resolves, we create a zone in > Designate for simpledemo.onap.org <http://simpledemo.onap.org/>, see > https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/config/docker/init/src/config/dcaegen2/heat/entrypoint.sh;h=85c5ee2b131458f7f25cab3c8efc4071b22775f5;hb=refs/heads/amsterdam > > <https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/config/docker/init/src/config/dcaegen2/heat/entrypoint.sh;h=85c5ee2b131458f7f25cab3c8efc4071b22775f5;hb=refs/heads/amsterdam> > And we added a reverse proxy so the lookup returns the IP of the K8S host > running the reverse-proxy, and the service port are opened. > > See bellow design implemented: > > <image001.jpg> > > > Thanks, > Alexis > > > > On Jan 22, 2018, at 2:00 PM, Gary Wu <[email protected] > <mailto:[email protected]>> wrote: > > Hi Alexis and Brian, > > How should we currently spin up DCAEGEN2 using OOM in Wind River lab? > > I assume we're supposed to set DNSAAS_PROXY_ENABLE to "true". However, when > this is done, my dcae-dcae-boostrap VM gets stuck on wait_for_aai_ready() > since it's unable to resolve the hostname "vm1.aai.simpledemo.onap.org > <http://vm1.aai.simpledemo.onap.org/>", and none of the DNSAAS-related code > in dcae_vm_init.sh gets triggered since they only occur after > wait_for_aai_ready(). > > Is there additional config/init that we're supposed to do to get > vm1.aai.simpledemo.onap.org <http://vm1.aai.simpledemo.onap.org/> to resolve > in this VM? > > Thanks, > Gary > > -----Original Message----- > From: [email protected] > <mailto:[email protected]> > [mailto:[email protected] > <mailto:[email protected]>] On Behalf Of Alexis de Talhouët > Sent: Monday, January 22, 2018 6:48 AM > To: BRIAN D FREEMAN <[email protected] <mailto:[email protected]>> > Cc: [email protected] <mailto:[email protected]> > Subject: Re: [onap-discuss] [OOM] DCAE status in non-openstack clouds ? > > Brian, > > DCAE deployment in Amsterdam is coupled to OpenStack cloud, and we’re not in > the process of supporting other cloud for now. > This could be an enhancement for Beijing, if DCAE still runs in VMs. And if > we do such implementation, we should leverage Multicloud interfaces to do so. > > Prior to this, we should flush out the requirement of DCAE deployment on > different type of cloud, what are the implications and so on. > > Alexis >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
