Hi Christopher, Your understanding of the terms is correct. A small clarification - Hosts are mostly referred to as nodes when running oVirt Node, a custom Linux distribution purposely made to be used as a host in oVirt.
As for your question: DEFROUTE=yes/no in the hosts' ifcfg files control the default gateway of the host. Currently, by design, the management network's gateway (Which sounds like your management network doesn't have?) will be kept as the host's default gateway. This was done to make sure that the engine maintains connectivity to its hosts. oVirt 3.3 introduced a feature called multiple gateways which may assist you. If you configured a gateway on the public network (Either statically via oVirt or via DHCP), then all traffic into the hosts through their public network NIC will be returned via that nic, *even though* the host's default gateway is ovirtmgmt's gateway. To clarify further: The current behavior is that the host's default gateway is ovirtmgmt's gateway. This controls traffic originating from *within* the host such as communications with storage. Incoming traffic, however, such as traffic originating from users from outside of the datacenter, will be returned via the device that the traffic came in on. If that doesn't work for you, and you feel like you need to control the host's default gateway via oVirt, then please file an RFE. I can't guarantee a timeline or that it will ultimately make it in the product, but the RFE will be carefully taken into account when designing future versions. ----- Original Message ----- From: "Christopher Geddings" <chris.geddi...@duke.edu> To: users@ovirt.org Sent: Monday, November 11, 2013 8:40:33 PM Subject: [Users] Default route on hosts Before I ask my question, I want to make sure I'm using the right terms: engine == the system that manages the ovirt environment. Runs the web interface, etc host(s) == the physical machine(s) the engine uses to deploy virtual machines on. Sometimes referenced as a node? vm(s) == the guest systems that are controlled by the engine and run on the hosts, that do the stuff you present to the world at large, whatever your world at large would be. Is that correct? In my environment, I have a customer facing network and another network that's on a set of isolated switches. I desire to use the isolated network as the management network, and am naming the other network "public" in the web management interface. In the interface, I see these labeled as ovirtmgmt and public, for the management network (private) and the customer facing network (public). >From what I can tell from poking at the configuration files, and from a couple >references in other threads, the 'DEFROUTE' setting in the ifcfg-* files gets set to 'yes' only for the ovirtmgmt network, not for any other bridged network. I can override this by hand as I deploy hosts, but am hoping for a way to do so within the ovirt management framework, so I have less bits that can go wrong. Is there a way for me to get the DEFROUTE set to no for the ovirtmgmt interface and to yes on the public interface as I deploy hosts? Is there a reason I'm not seeing for avoiding this behavior? --Chris _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
