If there is a DNS designate endpoint available, then we can disable this. Thanks, Kranthi
On 1/22/18, 2:01 PM, "[email protected] on behalf of Gary Wu" <[email protected] on behalf of [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", 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 to resolve in this VM? Thanks, Gary -----Original Message----- From: [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]> Cc: [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 _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
