Hi everyone, Thank you all, you've been very helpfull. I have one more question; How do I get a network not to be a VM network. If I create a new one, the VM option is ticked and grayed so I can't untick it. The same thing with an already created network. Sorry for all this questions, but though I've managed to find out by myself other stuff like vsdm changing multipath.conf, I haven't found much documentation on network configuration (this kind of stuff). Regards, _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

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(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

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(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

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,

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,

From: "Juan Pablo Lorier" <jplorier(a)gmail.com&gt; To: "Lior Vernia" <lvernia(a)redhat.com&gt; Cc: users(a)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(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users