Is a dedicated oVirt mgmt VLAN still needed for oVirt host nodes?
We have an oVirt environment that I inherited. One is running 3.4.0 and one is running 3.5.0. Seem in both cases the prior administrator stated that a dedicated VLAN was necessary for oVirt mgmt. That is, we could not run multiple tagged VLANs on a nic for a given oVirt host node. Does any of this make sense? Is this true? Is it still true for more contemporary versions of oVirt? My problem is that our nodes are blades and I only have two physical nics per blade. In our network for redundancy we need to have the two nics have the same VLANs so that things failover ok. Which means we have to share the oVirt mgmt network on the same wire. That's the ideal. Currently we have a whole nic on the blade just for oVirt management. Is this a requirement?
It will all work using different VLAN tags on the same physical nics. At least in 3.5.x that’s the case, we don’t have a 3.4.x install so I can’t speak to that. You’ll want to watch your NFS and migration traffic though. Make sure you don’t overrun the bandwidth for management traffic or you’re going to have a bad day. -Patrick
On Sep 14, 2015, at 10:08 AM, ccox@endlessnow.com wrote:
We have an oVirt environment that I inherited. One is running 3.4.0 and one is running 3.5.0.
Seem in both cases the prior administrator stated that a dedicated VLAN was necessary for oVirt mgmt. That is, we could not run multiple tagged VLANs on a nic for a given oVirt host node.
Does any of this make sense? Is this true? Is it still true for more contemporary versions of oVirt?
My problem is that our nodes are blades and I only have two physical nics per blade. In our network for redundancy we need to have the two nics have the same VLANs so that things failover ok. Which means we have to share the oVirt mgmt network on the same wire. That's the ideal.
Currently we have a whole nic on the blade just for oVirt management. Is this a requirement?
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Il 15/Set/2015 05:10, <ccox@endlessnow.com> ha scritto:
We have an oVirt environment that I inherited. One is running 3.4.0 and one is running 3.5.0.
Seem in both cases the prior administrator stated that a dedicated VLAN was necessary for oVirt mgmt. That is, we could not run multiple tagged VLANs on a nic for a given oVirt host node.
Does any of this make sense? Is this true? Is it still true for more contemporary versions of oVirt?
My problem is that our nodes are blades and I only have two physical nics per blade. In our network for redundancy we need to have the two nics have the same VLANs so that things failover ok. Which means we have to share the oVirt mgmt network on the same wire. That's the ideal.
Hy, My opinion: ovirt-engine supports configuration of the ovirtmgmt as a non-vm network, untagged. And on top of that nic (bond in your possible specific case) configure all of the VLANs. If you configure it as a vm network and want to put on the bond other networks too, then you have to configure both the ovirtmgmt and the other ones as tagged VLANs, you cannot mix tagged and untagged in this case. Or at least it was so that I remained in terms of configuration. Valid for 3.4 and 3.5, i think. Can anyone of the net part maintainers confirm? Other useful configurations, in term of bonding and related considerations (mtu, ecc): http://www.ovirt.org/Bonding_VLAN_Bridge https://access.redhat.com/solutions/43070 Gianluca
On 09/15/2015 03:28 PM, Gianluca Cecchi wrote:
Il 15/Set/2015 05:10, <ccox@endlessnow.com <mailto:ccox@endlessnow.com>> ha scritto:
We have an oVirt environment that I inherited. One is running 3.4.0 and one is running 3.5.0.
Seem in both cases the prior administrator stated that a dedicated VLAN was necessary for oVirt mgmt. That is, we could not run multiple tagged VLANs on a nic for a given oVirt host node.
Does any of this make sense? Is this true? Is it still true for more contemporary versions of oVirt?
My problem is that our nodes are blades and I only have two physical nics per blade. In our network for redundancy we need to have the two nics have the same VLANs so that things failover ok. Which means we have to share the oVirt mgmt network on the same wire. That's the ideal.
Hy, My opinion:
ovirt-engine supports configuration of the ovirtmgmt as a non-vm network, untagged. And on top of that nic (bond in your possible specific case) configure all of the VLANs. If you configure it as a vm network and want to put on the bond other networks too, then you have to configure both the ovirtmgmt and the other ones as tagged VLANs, you cannot mix tagged and untagged in this case. Or at least it was so that I remained in terms of configuration. Valid for 3.4 and 3.5, i think. Can anyone of the net part maintainers confirm?
The import oVirt setup is 3.4 based.. so it's important that we can run all the vlans on the same nic for that version. Thanks to any who can verify or confirm.
participants (4)
-
ccox＠endlessnow.com -
Christopher Cox
-
Gianluca Cecchi -
Patrick Russell