Re: [onap-discuss] [OOM] nameserver issue

[Alexis de Talhouët]

Harry,

I’m not sure to fully understand the issue wrt dns. Is it when deploying DCAE 
with OOM? If so, here are the requirement:

Have support for DNS Designate, and configure DNS Designate backend to forward 
request to an external DNS to resolve internet facing domain name.

All the VMs will be configured to point to DNS Designate backend IP address, 
which means all the VMs will be able to resolve internal domain (the one for 
dcae vms, and the one for simpledemo.onap.org <http://simpledemo.onap.org/> 
that will be created in DNS Designate during the provisioning of DCAE), and the 
external domains, as DNS Designate will recurse the request if not able to 
resolve.

HTH,
Alexis 

> On Feb 25, 2018, at 9:10 PM, huangxiangyu <huangxiang...@huawei.com> wrote:
> 
> Joe
>  
> Not sure if an onap_dns server steps in at this time. It seems that in ONAP 
> on kubernetes procedure, containers comes first then a heat bootstrap pod 
> will then launch dcae VMs in openstack using heat. I think that’s when a dns 
> server is needed. Anyway, 10.43.0.10 does look like a local dns server,  
> thing is I can’t find this 10.43.0.10  then somehow manipulate it to make 
> containers to connect to internet. Besides, I think I never configure this 
> address to be a local dns server but this address shows up every time when I 
> deploy the OOM.
>  
> Regards
> Harry
>  
> 发件人: Joe Kidder [mailto:joe.kid...@5thlayer.com] 
> 发送时间: 2018年2月25日 9:06
> 收件人: huangxiangyu <huangxiang...@huawei.com>
> 抄送: Michael O'Brien <frank.obr...@amdocs.com>; onap-discuss@lists.onap.org
> 主题: Re: [onap-discuss] [OOM] nameserver issue
>  
> Harry,
>   Do you have an onap_dns server in your setup?  In the heat-based ONAP, it 
> looks like there’s an onap_dns server that provides name resolution for the 
> various components, and then it may use some openstack DNS service called 
> designate to get out to the real world (e.g. 8.8.8.8).  
>   Two things that might come out of that - if you just jump out to 8.8.8.8, 
> you may not get local name resolution.  Secondly, perhaps the 10.43.0.10 is 
> supposed to be the local onap_dns server?  That doesn’t sound like the 
> address defaulted in the heat template for ONAP on O.S., however.
>  
> Joe
>  
> On Feb 24, 2018, at 1:43 AM, huangxiangyu <huangxiang...@huawei.com 
> <mailto:huangxiang...@huawei.com>> wrote:
>  
> Hi Michael
>  
> I’m using OOM Amsterdam branch and found that the nameserver in each 
> container is configured to 10.43.0.10. This address is unreachable and 
> therefore cause package installation failure in pod like heat-bootstrap- 
> under onap-dcaegen2. I can manually change nameserver to 8.8.8.8 to install 
> package but is there a way to configure nameserver to 8.8.8.8 ?
>  
> Thanks
> Harry
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>
> https://lists.onap.org/mailman/listinfo/onap-discuss 
> <https://lists.onap.org/mailman/listinfo/onap-discuss>
>  
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] nameserver issue

[Joe Kidder]

Harry,
  Do you have an onap_dns server in your setup?  In the heat-based ONAP, it 
looks like there’s an onap_dns server that provides name resolution for the 
various components, and then it may use some openstack DNS service called 
designate to get out to the real world (e.g. 8.8.8.8).  
  Two things that might come out of that - if you just jump out to 8.8.8.8, you 
may not get local name resolution.  Secondly, perhaps the 10.43.0.10 is 
supposed to be the local onap_dns server?  That doesn’t sound like the address 
defaulted in the heat template for ONAP on O.S., however.

Joe

> On Feb 24, 2018, at 1:43 AM, huangxiangyu  wrote:
> 
> Hi Michael
>  
> I’m using OOM Amsterdam branch and found that the nameserver in each 
> container is configured to 10.43.0.10. This address is unreachable and 
> therefore cause package installation failure in pod like heat-bootstrap- 
> under onap-dcaegen2. I can manually change nameserver to 8.8.8.8 to install 
> package but is there a way to configure nameserver to 8.8.8.8 ?
>  
> Thanks
> Harry
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org 
> https://lists.onap.org/mailman/listinfo/onap-discuss 
> 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [OOM] nameserver issue

[huangxiangyu]

Hi Michael

I'm using OOM Amsterdam branch and found that the nameserver in each container 
is configured to 10.43.0.10. This address is unreachable and therefore cause 
package installation failure in pod like heat-bootstrap- under 
onap-dcaegen2. I can manually change nameserver to 8.8.8.8 to install package 
but is there a way to configure nameserver to 8.8.8.8 ?

Thanks
Harry
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss