[airship-in-a-bottle] DNS configurable?
Hi all, I'm trying to deploy Airship-in-a-Bottle in a VM on libvirt/KVM. During the "generate genesis" step, the script overwrites /etc/resolve.conf to use the Google DNS servers (8.8.8.8 and 8.8.4.4), but those servers are blocked by our firewall, so FQDNs don't resolve and the script fails. Is there a way to configure the DNS server used or to simply keep the DNS server configured via DHCP? BTW, where are issues/RFEs filed against Airship? In Launchpad? Thanks, Frank
Hello Frank, Issues/RFEs should be filled in StoryBoard: https://storyboard.openstack.org/#!/project/1006 - this one is for Airship-in-a-bottle. Airship StoryBoard Group: https://storyboard.openstack.org/#!/project_group/85 I will check the code in regards to DNS issue tomorrow. Should be fairly easy to fix. Best regards, -- Roman Gorshunov On Thu, Jun 21, 2018 at 6:52 PM, Frank Zdarsky <fzdarsky@redhat.com> wrote:
Hi all,
I'm trying to deploy Airship-in-a-Bottle in a VM on libvirt/KVM.
During the "generate genesis" step, the script overwrites /etc/resolve.conf to use the Google DNS servers (8.8.8.8 and 8.8.4.4), but those servers are blocked by our firewall, so FQDNs don't resolve and the script fails.
Is there a way to configure the DNS server used or to simply keep the DNS server configured via DHCP?
BTW, where are issues/RFEs filed against Airship? In Launchpad?
Thanks,
Frank
_______________________________________________ Airship-discuss mailing list Airship-discuss@lists.airshipit.org http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
Hi Roman, Thanks a lot for the very fast response! And sorry for having been lazy: I should have investigated this a bit more myself. It's possible to configure the DNS server by editing data.dns.upstream_servers and data.dns.upstream_servers_joined in deploy/airship-in-a-bottle/deployment_files/site/demo/networks/common-addresses.yaml Maybe something worth documenting? Best regards, Frank On Thu, Jun 21, 2018 at 7:15 PM Roman Gorshunov <paye600@gmail.com> wrote:
Hello Frank,
Issues/RFEs should be filled in StoryBoard: https://storyboard.openstack.org/#!/project/1006 - this one is for Airship-in-a-bottle. Airship StoryBoard Group: https://storyboard.openstack.org/#!/project_group/85
I will check the code in regards to DNS issue tomorrow. Should be fairly easy to fix.
Best regards, -- Roman Gorshunov
On Thu, Jun 21, 2018 at 6:52 PM, Frank Zdarsky <fzdarsky@redhat.com> wrote:
Hi all,
I'm trying to deploy Airship-in-a-Bottle in a VM on libvirt/KVM.
During the "generate genesis" step, the script overwrites /etc/resolve.conf to use the Google DNS servers (8.8.8.8 and 8.8.4.4), but those servers are blocked by our firewall, so FQDNs don't resolve and the script fails.
Is there a way to configure the DNS server used or to simply keep the DNS server configured via DHCP?
BTW, where are issues/RFEs filed against Airship? In Launchpad?
Thanks,
Frank
_______________________________________________ Airship-discuss mailing list Airship-discuss@lists.airshipit.org http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
-- Frank Zdarsky | NFV&SDN Technology Strategy, Office of the CTO | Red Hat e: fzdarsky@redhat.com | irc: fzdarsky@freenode | m: +49 175 82 11 64 4
Hello Frank, > It's possible to configure the DNS server by editing > data.dns.upstream_servers > and > data.dns.upstream_servers_joined > in > deploy/airship-in-a-bottle/deployment_files/site/demo/networks/common-addresses.yaml Yes, but airship-in-a-bottle uses deploy/airship-in-a-bottle/deployment_files/site/dev/networks/common-addresses.yaml - 'dev' site, instead of 'demo', see https://github.com/openstack/airship-in-a-bottle/blob/master/manifests/common/deploy-airship.sh#L53 script. > Maybe something worth documenting? Sure, it is. I'm thinking of hot to get it properly done. Thank you for the patch! I will comment it later. Best regards, -- Roman Gorshunov
On Fri, Jun 22, 2018 at 3:28 PM Roman Gorshunov <paye600@gmail.com> wrote:
Hello Frank,
It's possible to configure the DNS server by editing data.dns.upstream_servers and data.dns.upstream_servers_joined in
deploy/airship-in-a-bottle/deployment_files/site/demo/networks/common-addresses.yaml Yes, but airship-in-a-bottle uses
deploy/airship-in-a-bottle/deployment_files/site/dev/networks/common-addresses.yaml - 'dev' site, instead of 'demo', see
https://github.com/openstack/airship-in-a-bottle/blob/master/manifests/commo... script.
Good catch, I changed that in patchset 2.
Maybe something worth documenting? Sure, it is. I'm thinking of hot to get it properly done.
Thank you for the patch! I will comment it later.
Best regards, -- Roman Gorshunov
participants (2)
-
Frank Zdarsky
-
Roman Gorshunov