Re: [Users] Multiple network interfaces on engine?

OK. Maybe I'm asking for something irrelevant, but to answer René's question; The use case is that there are two separate physical networks for general IP and storage IP, and Engine seems to require to be able to reach the NFS server to validate the connection when configuring mapping. So to be able to configure a NFS server, the Engine needs to be connected also to the storage network.

It worked fine after manually tweaking the sysconfig/network-scripts, but this config was then shortly overridden by Engine discovering and trying to use the second NIC for bonding with ovirtmgmt.

------------------------------------------------------------------------ *Från: *"Michael Pasternak" <mpastern(a)redhat.com&gt; *Till: *"Rickard Kristiansson" <rickard(a)sanuksystems.com&gt;, users(a)ovirt.org, "Oved Ourfalli" <ovedo(a)redhat.com&gt; *Kopia: *"Ohad Levy" <olevy(a)redhat.com&gt; *Skickat: *måndag, 23 sep 2013 13:35:40 *Ämne: *Re: [Users] Multiple network interfaces on engine? On 09/23/2013 02:23 PM, Rickard Kristiansson wrote: > Hmm.. yes, I do have the storage network configured in DC and Cluster, and also attached to all my hypervisors. > The question is just how I also attach it to the Engine server, as this isn't visible as a node in the GUI? i think this could be done with puppet, afaik some work for integrating it to oVirt been done lately, though not sure if it's already available, oved? > > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > *Från: *"Michael Pasternak" <mpastern(a)redhat.com&gt; > *Till: *"Rickard Kristiansson" <rickard(a)sanuksystems.com&gt; > *Kopia: *users(a)ovirt.org, "\"René \"Koch (ovido)\"\"" <r.koch(a)ovido.at&gt; > *Skickat: *måndag, 23 sep 2013 13:20:06 > *Ämne: *Re: [Users] Multiple network interfaces on engine? > > On 09/23/2013 01:50 PM, 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. >> Or do I need to add the engine as a host in the GUI as well, to be able to configure it? > > IIUC your question, you have various options: > > 1. GUI > 2. SDKs > 3. CLI > > you need to create network in DC, attach it to cluster, attach to host NIC/s (if you want it to be > atomic operation, i.e you expect connectivity loss during the operation/s, setupnetworks should be used, > otherwise you can use attach-network dialogues in UI) > >> >> >> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- >> *Från: *"Michael Pasternak" <mpastern(a)redhat.com&gt; >> *Till: *"Rickard Kristiansson" <rickard(a)sanuksystems.com&gt; >> *Kopia: *users(a)ovirt.org >> *Skickat: *måndag, 23 sep 2013 12:21:40 >> *Ämne: *Re: [Users] Multiple network interfaces on engine? >> >> On 09/23/2013 12:54 PM, Rickard Kristiansson wrote: >>> 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 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(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >> >> >> -- >> >> Michael Pasternak >> RedHat, ENG-Virtualization R&D >> > > > -- > > Michael Pasternak > RedHat, ENG-Virtualization R&D > -- Michael Pasternak RedHat, ENG-Virtualization R&D _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users