Thanks, Mars. That looks very helpful, I will give it a try. Thanks Harry
-----邮件原件----- 发件人: Mars Toktonaliev (Nokia - US/Irving) [mailto:mars.toktonal...@nokia.com] 发送时间: 2018年2月27日 23:57 收件人: huangxiangyu <huangxiang...@huawei.com>; Alexis de Talhouët <adetalhoue...@gmail.com> 抄送: onap-discuss@lists.onap.org 主题: Re: [onap-discuss] 答复: [OOM] nameserver issue Hi Harry, You can follow this instructions: https://docs.openstack.org/designate/latest/contributor/devstack.html After installation has been completed/verified, you can configure same VM to act as a DNS forwarder. Below is a sample configuration from our lab: root@designate:~# cat /etc/bind/named.conf.options include "/etc/bind/rndc.key"; options { directory "/var/cache/bind"; allow-new-zones yes; dnssec-validation auto; listen-on port 53 { 10.203.157.79; }; forwarders { 8.8.8.8; 8.8.4.4; }; forward only; allow-query { any; }; recursion yes; minimal-responses yes; }; controls { inet 10.203.157.79 port 953 allow { 10.203.157.79; } keys { "rndc- key"; }; }; root@designate:~# You'll have to replace 10.203.157.79 with your IP and restart bind service after updating configuration. Hope this helps. BR Mars On Tue, 2018-02-27 at 06:48 +0000, huangxiangyu wrote: > Thanks for reply, Alexis. I was asking why nameserver in ONAP pods is > always set to 10.43.0.10. I found there is a pod named heat- > bootstrap-xxxx which is supposed to manage DCAE deployment. And this > pod will install some package like openstack client which is used in > entrypoint.sh to do some preparation work before DCAE VMs are created. > Problem is this 10.43.0.10 can’t be reached so DCAE deploy can’t be > carried out. > > However, I do feel confused about how to set up a working Designate. > The guide https://onap.readthedocs.io/en/amsterdam/guides/onap-develo > per/settingup/install-designate.html?highlight=designate have some > instruction but I still don't get how to set Designate to forward > request to internet. Can you provide some steps in details? The > OpenStack Designate documentation seems more introductory to use > 127.0.0.1. > > Thanks > Harry > > 发件人: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] > 发送时间: 2018年2月26日 20:51 > 收件人: huangxiangyu <huangxiang...@huawei.com> > 抄送: Joe Kidder <joe.kid...@5thlayer.com>; onap-discuss@lists.onap.org > 主题: Re: [onap-discuss] [OOM] nameserver issue > > 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 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.o > > nap.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 <huangxiangyu5@huawei.c > > > om> 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-xxxx 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 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
