Re: [ovirt-users] oVirt 3.5.3 Host Network Interfaces
Dear Michael
We actually created the ovirtmgmt and the bond manually upfront and then
in the ³Setup Hosts Network² we basically did this again (including
setting the IP address), regarding the bonding in the gluster network we
did not have a problem, you just drag one interface onto the other and
then select the bonding mode, where you can also go for bonding mode TLB
or ALB if you choose ³custom² or just LACP if you have switches that
support this.
Step by Step:
- set the engine to maintenance and shut it down
- configure the bond on the 2 nics for the ovirtmgmt bridge ( em1+em2 ->
bond0 -> ovirtmgmt )
- configure the IP on the bridge
- reboot the server and see whethter it comes up correctly
- remove maintenance and let engine start
- Set up the ovirtmgmt in hosts networks but do not forget to set IP and
Gateway as well.
Though it should work without this hassle (if the bonding mode on the
switch and server is compatible) but this way it is easy to get server and
switch in the same mode and working without having to do anything in ovirt
first.
Hope that helps
Regards
Soeren
On 02/07/15 00:31, "users-bounces(a)ovirt.org on behalf of Prof. Dr. Michael
Schefczyk" <users-bounces(a)ovirt.org on behalf of michael(a)schefczyk.net>
wrote:
Dear All,
Having set up a Centos 7 server with Gluster, oVirt 3.5.3 and hosted
engine according to
https://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/,
I was hoping that the NIC management and particularly NIC bond/bridge
capabilities would have improved a bit. My server has four NICs, two
connected to the LAN and two to an adjacent server to be used as a
Gluster network between the two servers. My aim is to use NIC bonding for
two NICs each.
Via the engine, I would like to use Hosts -> Network Interfaces -> Setup
Host Networks. As I use hosted engine, I cannot set the only host to
maintenance mode. At least during normal operations, however, I am
neither able to change the ovirt bridge from DHCP to static IP nor create
a bond consisting of the two LAN facing NICs. In each case I get, "Error
while executing action Setup Networks: Network is currently being used".
Editing the network scripts manually is not an option either, as that
does not survive a reboot. Contrary to this real view, everything should
be easily configurable according to section 6.6 of the oVirt
administration guide.
One workaround approach could be to temporarily move one NIC connection
from the adjacent server to the LAN or even temporarily swap both pairs
of NICs and edit interfaces while they are not in use. Is this really the
way forward? Should there not be a more elegant approach not requiring
physically plugging NIC connections just to work around such issue?
Regards,
Michael