[Users] Multiple network interfaces on engine?

[Rickard Kristiansson]

OK, thanks. Then I'm happy with the explanations that it is supposed to work the way I initially expected.. 
That all operations are actually carried out on the nodes is good news, and should solve all worries. 

I'll go back and see what is actually going wrong on the engine and try to fix it. 
I'd love to reinstall the engine, but as I can't find any documentation on how to reliably move configs from one engine to another, and I was brave enough to already put ovirt into production with a number of hypervisors, I'm somewhat limited to what I can/dare to do. 


----- Ursprungligt meddelande -----



I have also more than one interface in my Engine but never had this problem, I don't have a ovirtmgmt network on my Engine hosts thats not needed. I can understand the need for the engine server to have a nic/ip in the managment network AND a nic/ip in the storage network. I also have a separate access/public network and ilo network. 
It looks like you have a bond defined somewhere and it looks like you have vdsm running on your engine server. 

Just looking at my two engine servers and none has more than one ip. The one in the test setup doesn't even have storage assigned and doesn't need it. It sends mount commands to the hosts which DO have a separate storage network. My engine hosts don't host the iso/export domains so don't need to be in the storage network. 

If you have the possibility, go back to a bare machine with NetworkManager turned off and network turned on. Make sure networking is working as expected, eth0=ip in managment, eth1= ip in storage. Install/setup ovirt-engine-setup, don't install vdsm (gets installed if you do allinone!) and things should 'just' work. 

Regards, 

Joop 


_______________________________________________ 
Users mailing list 
Users at ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130923/2bdbac23/attachment-0001.html>