Hmmm, this is becoming difficult .. I have added into the engine the custom hook and understand how that will work. The issue is how can a single NIC use two different bridges ? Example with OVS would be that one requires: em1 -+ ovirtmgmt (bridge) -> management IP (public) + ovs (bridge) -> firewall IP (public) | + vlan 1 + vlan 2 this works fine when using OVS and KVM, without oVirt, so there must be a way to hook the two together without a Neutron appliance. Any thoughts ? Thanks, Phil. ----- Original Message ----- From: "Dan Kenigsberg" <danken@redhat.com> To: "Phil Daws" <uxbod@splatnix.net> Cc: users@ovirt.org Sent: Wednesday, 22 October, 2014 3:54:46 PM Subject: Re: [ovirt-users] oVirt 3.5 & NAT On Wed, Oct 22, 2014 at 03:12:09PM +0100, Phil Daws wrote:
Thanks Dan & Antoni:
I wonder then if I could replace the standard libvirt defined network with an OpenVSwitch one like I have on my dev system? That is just straight KVM with OVS integrated. Maybe a bit more overhead in administration but possibly less than having to spin up a Neutron Appliance.
Once you start to use the vdsm-hook-extnet, all that you need to do is to replace the libvirt-side definition of the "external network". This may well be an OpenVSwitch-based network e.g. http://libvirt.org/formatnetwork.html#elementVlanTag