Gary, This patch fixes the OOM to enable proxy DNS designate setup: 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/ Expect this to be merge in a couple of hours. Thanks, Alexis > On Jan 22, 2018, at 3:57 PM, Alexis de Talhouët <adetalhoue...@gmail.com> > 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 <gary.i...@huawei.com >> <mailto:gary.i...@huawei.com>> 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:adetalhoue...@gmail.com >> <mailto:adetalhoue...@gmail.com>] >> Sent: Monday, January 22, 2018 11:58 AM >> To: Gary Wu <gary.i...@huawei.com <mailto:gary.i...@huawei.com>> >> Cc: BRIAN D FREEMAN <bf1...@att.com <mailto:bf1...@att.com>>; PLATANIA, >> MARCO (MARCO) <plata...@research.att.com >> <mailto:plata...@research.att.com>>; onap-discuss@lists.onap.org >> <mailto:onap-discuss@lists.onap.org> >> 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 <gary.i...@huawei.com >> <mailto:gary.i...@huawei.com>> 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: onap-discuss-boun...@lists.onap.org >> <mailto:onap-discuss-boun...@lists.onap.org> >> [mailto:onap-discuss-boun...@lists.onap.org >> <mailto:onap-discuss-boun...@lists.onap.org>] On Behalf Of Alexis de Talhouët >> Sent: Monday, January 22, 2018 6:48 AM >> To: BRIAN D FREEMAN <bf1...@att.com <mailto:bf1...@att.com>> >> Cc: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> >> 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 onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
