Rickard Kristiansson wrote:
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.
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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
