Hi all,
I 've finished migration from 4.4.4 to 4.4.9 and I'm facing a strange
issue with routing table on my hosts: all IP addressed interfaces (and
in particular gluster and migration ones that requiere an IP) are not
part of the "254" or "0" usual ip rule.
for instance:
[root@fuego ~]# nm
Hello I created a cluster of ovirt 4.4 with 5 servers, I have a diferent
gateway, ovirtmgmt and display network. In 4.4 routing is managed from network
manager. Network manager seems to "forget" and recreate the route each time. So
I cannot connect to the virtual machines console unless I run a
ll the tagged vlans working?
From: Edward Haas [mailto:eh...@redhat.com]
Sent: Sunday, May 6, 2018 7:34 AM
To: Justin Zygmont
Cc: users@ovirt.org
Subject: Re: [ovirt-users] routing
Not sure if I understand what you are asking here, but the need for a gateway
per network has emerged from the n
Not sure if I understand what you are asking here, but the need for a
gateway per network has emerged from the need to support other host
networks (not VM networks) beside the management one.
As an example, migration and storage networks can be defined, each passing
dedicated traffic (one for stora
I don't understand why you would want this unless the ovirtnode itself was
actually the router, wouldn't you want to only have an IP on the management
network, and leave the rest of the VLANS blank so they depend on the router to
route the traffic:
NIC1 -> ovirt-mgmt - gateway set
NIC2 -> VL
5 matches
Mail list logo
