1:03 p.m.
I am going to be using OVN Geneve overlay networks extensively and I expect a lot of
traffic on the underlay network being used for transmission of the tunnel traffic.
In oVirt the default seems to be that the network "ovirtmgmt" is being used for
the underlay network - which could cause problems for management traffic if vms are
saturating the link with traffic on different OVN overlay networks.
When selecting a specific cluster, selecting "Logical Networks" and pressing the
"Manage Networks" button it is possible to specify that a specific Data Center
Network shall be limited to one or more of the following traffic types:
- VM Network
- Management
- Display Network
- Migration Network
- Gluster Network
- Default Route
Here I miss an option called "Underlay Network for OVN Geneve traffic" or
similar.
Is there a way - e.g. by editing some configuration files on the oVirt engine and on the
oVirt nodes - to divert all overlay Geneve traffic away from the management interface unto
a dedicated network interface?
Carl
3:29 a.m.
The OVN tunnels are set up during host installation, when
only 'ovirtmgmt' is available (no other networks are created
yet).
You can change the tunneling network for a cluster by using
the procedure described below. This will hopefully be integrated
into the UI one day.
1. Go to:
cd /use/share/ovirt-engine/playbooks
2. Execute:
ansible-playbook --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa -i
/usr/share/ovirt-engine-metrics/bin/ovirt-engine-hosts-ansible-inventory
--extra-vars
" cluster_name=<cluster name> ovn_central=<ovn central ip>
ovn_tunneling_interface=<vdsm network name>" ovirt-provider-ovn-driver.yml
Note that this only changes the settings on existing hosts.
If new hosts are added to the cluster, the procedure has to be repeated.
The OVN tunnel network can also be changed on an individual host by
invoking:
vdsm-tool ovn-config <ovn central ip> <tunneling ip or network name>
Marcin
On Sun, Jul 1, 2018 at 7:03 PM, <carlgrundholm(a)gmail.com> wrote:
I am going to be using OVN Geneve overlay networks extensively and I
expect a lot of traffic on the underlay network being used for transmission
of the tunnel traffic.
In oVirt the default seems to be that the network "ovirtmgmt" is being
used for the underlay network - which could cause problems for management
traffic if vms are saturating the link with traffic on different OVN
overlay networks.
When selecting a specific cluster, selecting "Logical Networks" and
pressing the "Manage Networks" button it is possible to specify that a
specific Data Center Network shall be limited to one or more of the
following traffic types:
- VM Network
- Management
- Display Network
- Migration Network
- Gluster Network
- Default Route
Here I miss an option called "Underlay Network for OVN Geneve traffic" or
similar.
Is there a way - e.g. by editing some configuration files on the oVirt
engine and on the oVirt nodes - to divert all overlay Geneve traffic away
from the management interface unto a dedicated network interface?
Carl
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
message/7MX6GKDKNQ7GCIWPEEMH374YIJ3JLDHF/
2365
days inactive
2367
days old
1 comments
2 participants
participants (2)
-
carlgrundholm＠gmail.com -
Marcin Mirecki