Hi Simon Would you mind expanding a little more on your setup?
Specifically what is being used underneath. thanks ilya On 4/14/17 9:11 AM, Simon Weller wrote: > I'd strongly suggest you consider using the native VXLAN support for KVM. It > works extremely well and we run it in production. > > > - Si > > > > > ________________________________ > From: Dag Sonstebo <dag.sonst...@shapeblue.com> > Sent: Friday, April 14, 2017 10:57 AM > To: users@cloudstack.apache.org > Subject: Re: OVS Plugin > > Hi Imran, > > OVS is the same as GRE tunnelling, which you will have as an isolation method > for guest networking – see > http://docs.cloudstack.apache.org/en/latest/networking/ovs-plugin.html. > > Please let us know how you get on – especially how your hypervisor nodes cope > with CPU load once the GRE tunnels start growing in numbers (historically > this has not scaled well). > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue > > On 13/04/2017, 21:37, "Imran Ahmed" <im...@eaxiom.net> wrote: > > Dear Team, > > I have setup cloudstack 4.9 with KVM hypervisor and advanced networking on > CentOS7. Also we installed and setup openvswitch on the hypervisors (KVM) > hosts. > > Below are traffic labels for kvm > > Cloudbr0 for management > Cloudbr1 for guest > Cloudbr2 for public > > After configuring the zone, pod , cluster, host, primary and secondary > storages we wanted to enable the OVS plugin under service providers for > the > guest network. > > However OVS is not shown in the list. > > Please suggest what could be wrong here. > > Kind regards, > > Imran > > > > > dag.sonst...@shapeblue.com > www.shapeblue.com<http://www.shapeblue.com> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > >
