Hello again Juan Pablo,
We're aware that the networking (among other things) in oVirt isn't
perfect, we're working on it :) As I had mentioned, the 3.2 release did
improve the network functionality, as well as make it much
user-friendlier, so an upgrade is recommended if possible. Also, in the
up-and-coming 3.3 there's an OpenStack Quantum integration feature that
should enable oVirt users to take advantage of the rich network
topologies offered by Quantum.
As for your current situation, by far your safest choice would be to
configure the VLANs in your switches. However, depending on your VDSM
version, you might be able to enable non-VM networks in your cluster
simply by changing a configuration value in your engine database
(although this would be an unsupported hack and I can't guarantee that
it won't mess anything up).
If interested, I can give you more details on what to change exactly,
but I'm not sure that it will actually solve your problem - you still
won't be able to have two non-VLAN networks on the same NIC, at most
you'll be able to have one non-VM, non-VLAN network residing with VLAN
networks. And I'm not sure even that will work in 3.1.
On 15/05/13 19:42, Juan Pablo Lorier wrote:
I did managed to get the mgmt network tagged so now I can use the same
interface for several networks. The thing now is that I also have two
networks I use for iscsi that I'd like to be able to use in the same
interface (not the mgmt one) in one of the hosts, but as this networks
are in vlan1 untagged, I can't share the same interface. One of the
things to try was marking the network as not VM (to see if I can share
the interface in that scenario as suggested before), but I can't get the
networks to be not-vm.
What I'm doing as a work arround is to have the networks in a tagged
vlan, but again, I can't have two networks in the same vlan :-(, thus,
I'll have to configure two different vlans in my switchers just to be
able to share the interface.
This is not the greatest scenario as network layer tools in linux give
all the needed options, but ovirt seems not to be able to use them yet.
I was evaluating Proxmox prior to move to ovirt and they had this quite
well implemented, I was able to do everything I needed with the network
like with XEN (my actual virt platform) but cluster was not that easy to
get going and I moved. Nothing is perfect :-)
Anyway, I'll keep an eye on ovirt evolution to see if this gets better
before I move to production.
Thank you all for your help, any ideas are always welcome.