On 09/23/2013 01:53 PM, René Koch (ovido) wrote:
On Mon, 2013-09-23 at 12:50 +0200, Rickard Kristiansson wrote:
Thanks Michael,
I'm still trying to get my head around this, but I can't see how I configure the networks on the engine? For nodes and AOI it's OK, but in my case I am running the engine as a separate server which is not a node and does not show up as a Host in the GUI.
Does your engine really need access to the storage? ovirtmgmt network should be sufficient in most cases.
You can configure the network of engine using your favorite editor and edit/create /etc/sysconfig/network-scripts/ifcfg-* files...
I'd avoid doing this, changing network config behind the engine's back is not supported and may cause re-config on reboot on which Rickard originally complained.
Regards, René
Or do I need to add the engine as a host in the GUI as well, to be able to configure it?
______________________________________________________________________ Från: "Michael Pasternak" <mpastern@redhat.com> Till: "Rickard Kristiansson" <rickard@sanuksystems.com> Kopia: users@ovirt.org Skickat: måndag, 23 sep 2013 12:21:40 Ämne: Re: [Users] Multiple network interfaces on engine?
Hi,
I want to use two network interfaces connected to different networks in Engine (3.3), where one is for ovirtmgmt and one is for a separate storage network. It works fine for a minute or so after rebooting Engine, but then
On 09/23/2013 12:54 PM, Rickard Kristiansson wrote: the configuration is changed by Engine, connecting both interfaces to bond0 and losing connectivity (as
obviously you can't bond those two interfaces when they are connected to separate physical networks..). What is the mechanism doing this,
please see this [1].
[1] http://www.ovirt.org/Features/Design/Network/SetupNetworks
and it is possible to disable this automatic network bonding on the engine so that we can use separate networks on the network interfaces..?
attaching logs would help, but i guess it happen cause you did not saved your host network config, i.e when host got rebooted, it performs roll-back to old config, this is actually disaster recovery mechanism.
Rickard
**
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--
Michael Pasternak RedHat, ENG-Virtualization R&D
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Michael Pasternak RedHat, ENG-Virtualization R&D