From 3.3, you can define gateways on the other networks. These will be used via
Hi Karli, Normally we configure the host's default gateway on the ovirtmgmt network. If your engine is in the same subnet as all of your hosts, then it's not to define a getway on the ovirtmgmt network. source routing. For example, if you set a gateway on the display network, but leave the gateway blank for the ovirtmgmt network, then you'll see that 'ip route' won't list a default gateway. However, we configure source routing so that all traffic coming in to the display network on the host, will be returned via that network's gateway. You can view source routing rules via: ip rule Then ip route show table %s, for each table listed in ip rule. Assaf Muller, Cloud Networking Engineer Red Hat ----- Original Message ----- From: "Karli Sjöberg" <Karli.Sjoberg@slu.se> To: danken@redhat.com Cc: amuller@redhat.com, fsayd@uncu.edu.ar, users@ovirt.org Sent: Thursday, January 23, 2014 12:00:52 PM Subject: Re: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured" On Thu, 2014-01-23 at 09:34 +0000, Dan Kenigsberg wrote:
On Thu, Jan 23, 2014 at 06:50:59AM +0000, Karli Sjöberg wrote:
One comment to your wiki page: in order to better intergrate with our recent source-routing support (mostly useful for display network), please set GATEWAY only in ifcfg-ovirtmgmt, and remember to set DEFROUTE=no in any other ifcfg that mentions IPADDR so as not to override the default.
Dan.
Does that imply that default gateway is supposed to be on the same net as ovirtmgmt?
Yes, and that's what happening whenever you make changes to ovirtmgmt via Vdsm.
To tell you the truth, that makes me rather uncomfortable since we have set up our ovirtmgmt on a non-routed, "black" net, only used for _mgmt_ (thought that was the point). The display network is set up on a another logcal network, a routed net, which is where we also have the default gateway. Is this now a "wrong/bad" way to go about it? /K