Hi, Is VM Network grayed out in "Assign/Unassign Networks" windows in clusters tab or is it grayed out in "Edit Logical Network" in data centers tab? Afaik you have to define vm network for a data center not for a cluster... Regards, René On 05/13/2013 10:22 PM, Juan Pablo Lorier wrote:

Hi Itamar,

I've read the doc you pointed (actually I didn't look before in red hat, just in ovirt world) but in the manual, vm option is not grayed as in my 3.1 management engine. Do I have to tune something in the config so new networks are not VM networks by default? Regards, _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Hello Juan Pablo, If I'm correctly reading the configuration values in my database, non-VM (AKA bridgless networks) are only enabled for 3.2 datacenters/clusters onwards, so if upgrading is an option that should do the trick. Otherwise, if it's important enough and you're feeling gutsy, it MIGHT be possible to hack your way into enabling it for your cluster. It's actually funny that you see this option in a version of oVirt that doesn't support it - I'm not familiar with the history of the feature, but maybe the checkbox had been added prior to the feature being introduced. Yours, Lior. On 14/05/13 18:21, Juan Pablo Lorier wrote:

Hi René

It's grayed in both DC edit and cluster assign/unassign, and even when I create a new network, I can't choose it not to be a VM network. Regards, _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

I went over the thread again, do I understand correctly that you've managed to get ovirtmgmt VLAN-tagged and working? That's the hard part, once there you should be able to tag all other networks through the oVirt engine quite easily. What Moti and I said about a non-VM network living together with VLANs was relevant to oVirt 3.2, it might not be true for 3.1 (Moti is more experienced than me, he might be able to confirm Thurday). So VLANs are probably your best shot. Is there a concrete problem that you're facing right now? Again, the configuration of VLAN networks from the engine should work alright without requiring you to configure the hosts manually. Lior. On 14/05/13 21:45, Juan Pablo Lorier wrote:

Hi Lior,

Thanks for the tip. I don't know if I can move to 3.2 as the centos repos are not there yet and I'm not quite sure of moving (compile 3.2) to a version without "stable" dependencies for a system almost in production. I'm trying to move stuff into vlans so I can share the interfaces. I'd like to know if I can configure network stuff manually in the host so ovirt won't change it when network configuration is made from the manager. Network management seems not to be very flexible in this version. Regards,

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. Yours, Lior. On 15/05/13 19:42, Juan Pablo Lorier wrote:

Hi Lior

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. Regards,

Late to the party, but I've raised this documentation bug to try and catch your issue. https://bugzilla.redhat.com/show_bug.cgi?id=980360 Can you have a look please Juan, and feel free to add/correct. Thanks. Tim Hildred, RHCE, RHCVA Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred ----- Original Message -----

From: "Juan Pablo Lorier" <jplorier@gmail.com> To: "Lior Vernia" <lvernia@redhat.com> Cc: users@ovirt.org Sent: Thursday, May 16, 2013 9:24:31 PM Subject: Re: [Users] Vlan interface on top of bonding

Hi Lior,

Thank you very much for your help. I'm sure things are improving and fast thanks to the great job of the ovirt team. Right now I think that using VLans is going to be the safest choice to me. I plan to move the plataform into production before end of month so I'll stick to stable stuff. I'll take a look into quantum as I don't know anything about it and may be of use. Regards, _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users