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, > > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users