Once upon a time, Sandro Bonazzola <sbonazzo@redhat.com> said:
Unfortunately, it seems like Ovirt 3.4 does not support installing self-hosted engine on bond + vlan. I tried 3.5 but there were to much bug to be usable and the project is set to be deployed in 2 months.
should be available via: http://gerrit.ovirt.org/#/c/29730/ ?
Yes, it's available in 3.4.3[1]. However, looks like VDSM has some issue with the network [2][3]
As far as I can tell, "hosted-engine --deploy" still fails if you try to use a VLAN on top of a bond, in both 3.4 and 3.5 (I just tried again with a clean install of the latest 3.5 snapshot). The deploy script dies when it tries to configure the management bridge. vdsm.log ends with this (bond0 definately already exists): Thread-16::ERROR::2014-07-23 08:40:59,436::API::1363::vds::(addNetwork) unknown nic: bond0 Traceback (most recent call last): File "/usr/share/vdsm/API.py", line 1361, in addNetwork supervdsm.getProxy().addNetwork(bridge, options) File "/usr/share/vdsm/supervdsm.py", line 50, in __call__ return callMethod() File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda> **kwargs) File "<string>", line 2, in addNetwork File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in _callmethod raise convert_to_error(kind, result) ConfigNetworkError: (23, 'unknown nic: bond0') If I manually create the ovirtmgmt bridge first, I can install a 3.5-snapshot hosted engine, although the install gets stuck at the end on "Still waiting for VDSM host to become operational". It results in an install that thinks the ovirtmgmt network is unsynchronized and can't be synchronized because the network is being used (of course, it is being used by the engine). -- Chris Adams <cma@cmadams.net>