I only use names for storage, but didn't have entries for the engine
yet, So I think ssh was slow since it couldn't do reverse DNS lookups
against the engine where my consoles are coming from. Thanks for the
input. I wanted to verify before testing since this is a production
environment. It seems like even the XMLRPC code must try and do a
reverse DNS against the engine as well, not just ssh. Seems like the
engine hosts also needs said hosts file as well..
On Mon, Apr 14, 2014 at 8:23 AM, René Koch <rkoch(a)linuxland.at> wrote:
On 04/14/2014 03:08 PM, Jeremiah Jahn wrote:
>
> So like the nut job I am, I host my dns server on a virtual machine
> that is now hosted by ovirt, I also have a few gateway machine in
> there as well for routing traffic between internal networks. With
> virt-manager, DNS rarely seemed to be an issue. I'd connect to a host
> IP, and bring up the vm, no problem. Ovirt on the other hand takes
> forever if dns is down. So i've passed around a /etc/hosts file to
> resolve any ip address that ovirt might be looking for while dns is
> out. I'd like to verify at an abstract level, what needs to be in
> said file, to keep everything from timing out, or just taking forever.
>
> name and FQDN of each host
> name and FQDN of engine host
> name and FQDN of each storage domain.
>
> Is this enough, or are there other places/things the ovirt node and
> hosts might be trying to resolve?
Afaik this should be enough.
Just remember that e.g. ssh login will still be slow if the DNS server isn't
reachable as you have to wait until it reaches a timeout.
My oVirt setup doesn't have any DNS entry - just the hosts and engine in
/etc/hosts. But I don't use DNS names at all only IP addresses...
Regards,
René
>
> thanks,
> -jj-
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>