Thanks for your responses but the ui is not an option for me as i am dealing with loads of systems. in 3.5 ovirt used to just accept the bridge as it was and incorporate it, i am just wondering if i am facing a bug or a feature at the moment. Charles Kozler schreef op 2016-11-28 15:48:
Thats what I used to do as well then on oVirt 4 it started screwing with the the bond as well so I ended up just dumbing it down and figured using the UI after the fact would be OK. I cant remember exactly what would happen but it would be stupid little things like routing would break or something.
On Mon, Nov 28, 2016 at 9:43 AM, Simone Tiraboschi <stirabos@redhat.com [8]> wrote:
On Mon, Nov 28, 2016 at 3:42 PM, Charles Kozler <ckozleriii@gmail.com [7]> wrote:
What Ive been doing since oVirt 4 is just configuring one NIC manually when I provision the server (eg: eth0, em1, etc) and then let oVirt do the bridge setup. Once the engine is up I login to the UI and I use it to bond the NICs in whatever fashion I need (LACP or active-backup). Any time I tried to configure ovirtmgmt manually it seemed to "annoy" the hosted-engine --deploy script
This is fine. Another thing you could do is manually creating the bond and then having hosted-engine-setup creating the management bridge over your bond.
On Mon, Nov 28, 2016 at 9:33 AM, Simone Tiraboschi <stirabos@redhat.com [6]> wrote:
On Mon, Nov 28, 2016 at 12:24 PM, <joost@familiealbers.nl [3]> wrote:
Hi All,
In our ovirt 3.5 setup. i have always setup the ovirtmgmt bridge manually . The bridge consisted of 2 nics
Id have /etc/vdsm/vdsm.conf list net_persist = ifcfg
When i then deployed the host from the ovirt ui or api it would install and would display the network setup correctly in the ui.
On ovirt 4. (vdsm-4.18.15.3-1.el7.centos.x86_64) I seem unable to follow the same approach.
In the engine logs i get among other things
If the interface ovirtmgmt is a bridge, it should be torn-down manually.
the interface is indeed a bridge with two nics which i would like to keep this way.
On the host vdsm.log i get limited info,
when start a python terminal to obtain netinfo i get this
>> from vdsm.tool import unified_persistence >> unified_persistence.netswitch.netinfo() Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch.py", line 298, in netinfo _netinfo = netinfo_get(compatibility=compatibility) File
"/usr/lib/python2.7/site-packages/vdsm/network/netinfo/cache.py",
line 109, in get return _get(vdsmnets) File
"/usr/lib/python2.7/site-packages/vdsm/network/netinfo/cache.py",
line 101, in _get report_network_qos(networking) File
"/usr/lib/python2.7/site-packages/vdsm/network/netinfo/qos.py",
line 46, in report_network_qos iface, = host_ports ValueError: too many values to unpack
As it appears the line in question does not like to deal with a list of nics i think. but either way.
Is in ovirt 4 the ability to use the ovirtmgmt bridge with multiple nics removed?
But do you need a bridge or a bond?
If so what can i do to stick to what we have done in the past.
Thanks.
_______________________________________________ Users mailing list Users@ovirt.org [1] http://lists.ovirt.org/mailman/listinfo/users [2]
_______________________________________________ Users mailing list Users@ovirt.org [4] http://lists.ovirt.org/mailman/listinfo/users [5]
Links: ------ [1] mailto:Users@ovirt.org [2] http://lists.ovirt.org/mailman/listinfo/users [3] mailto:joost@familiealbers.nl [4] mailto:Users@ovirt.org [5] http://lists.ovirt.org/mailman/listinfo/users [6] mailto:stirabos@redhat.com [7] mailto:ckozleriii@gmail.com [8] mailto:stirabos@redhat.com