Hi Guys (& Gals),
Newbie hand-holding question:
I've been reading documentation and reading and watching tutorials on
using OVS, and I think I've got this all AOK (although I do suspect that
I'm not quite 100% there yet), but what I'd really find useful is if
someone could have a quick look at this and tell me if I've missed any
glaring "gotchas" that are going to put me into a world of "ovs hell"
hurt, *before* I go ahead and instigate the changes/setup I'm about to make.
So thanks in advance :-)
The Current Situation
* A new (physical) server with three NICs (eno1, eno2, eno3), plus an
IPMI NIC (for OOB management if required)
* eno1 & 2 are currently 802.3ad bonded (bond0).
* There are three Vlans (1, 2, & 3) sitting on top of bond0 - bond0.1,
bond0.2, & bond0.3
* Vlan 1 is used as a "DMZ" network.
* Vlan 2 is used as the "main" network where all the internal servers
live.
* Vlan 3 is used as a "data transfer" isolated network between VM
hosting servers (like this one) and the SAN.
* The server itself currently has a Vlan 2 ip address (for "In-Band"
management, updates, etc, etc, etc).
* The server also has a Vlan 3 ip address for data transfers.
* eno3 is on an isolated LAN (for management data transfer purposes)
with a completely different ip address from the 3 Vlans.
* Open vSwitch v2.16.5 is installed
* The server is running Rocky Linux 8.6
* Everything is working, everything can ping everything that it
should, and is prevented from pinging everything that it shouldn't.
The Desired Situation
* Have OVS bonded using eno1 and eno2
* Have a port for the server on vlan 2
* Have another port for the server on vlan 3
* VMs will have taps on vlan 1 or 2 as appropriate
* VMs may also have taps on vlan 3 as required
The Proposed Config
* Remove the existing eno1, eno2, and bond0 configurations, along with
bond0.1, bond0.2, bond0.3
* Institute the following:
~~~
ovs-vsctl add-br ovs-br0
ovs-vsctl add-bond ovs-br0 ovs-bd0 eno1 eno2 lacp=active
ovs-vsctl add-port ovs_br0 eth1 tag=2
ovs-vsctl add-port ovs_br0 eth2 tag=3
ovs-vsctl add-port ovs_br0 tap<N> tag=1 <As required>
ovs-vsctl add-port ovs_br0 tap<N> tag=2 <As required>
ovs-vsctl add-port ovs_br0 tap<N> tag=3<As required>
~~~
The idea of the above is that the server will use eth1 & 2 to connect to
vlan 2 & 3 (as it does now), while the VMs will use the taps.
So, is the above all good, or is there a gaping hole that I'm not seeing
that is going to cause me to spend my entire weekend rebuilding the
server? :-)
Cheers
Dulux-Oz
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
