Hi Andrey,
We do a have a opensource Neutron based solution for VMware
vCenter-oriented environment in Kilo, please have look in the links below:
https://github.com/stackforge/networking-vsphere(For Kilo release woking in
progress)
https://github.com/hp-networking/ovsvapp(With Juno stable)
On
With correct links:
https://github.com/stackforge/networking-vsphere/tree/master/specs/kilo
https://github.com/stackforge/networking-vsphere/
https://github.com/hp-networking/ovsvapp
On Sun, Jan 25, 2015 at 7:28 PM, Romil Gupta wrote:
> Hi Andrey,
>
> We do a have a opensource Neut
Thanks Bob :)
Its really a nice explanation.
On Fri, Jan 23, 2015 at 1:01 PM, Harish Patil
wrote:
> >
>
> >Hi Harish,
> >
> >Port binding in ML2 is the process by which a mechanism driver (or once
> >
> https://blueprints.launchpad.net/openstack/?searchtext=ml2-hierarchical-po
> >rt-binding
> >
Hi Gary,
I posted the patch-set addressing ML2 plugin
https://review.openstack.org/#/c/130992/ .
I feel it is becoming long chain. It would be great we should first start
approving those patch-sets first rather than approving other bug-fix
related patch-set and ensure that all fulfills i18n trans
Fine for me :)
On Thu, Nov 13, 2014 at 6:08 PM, Gary Kotton wrote:
> Hi,
> A few months back we started to work on a umbrella spec for Vmware
> networking support (https://review.openstack.org/#/c/105369). There are a
> number of different proposals for a number of different use cases. In
> add
Awesome, I like the idea.
On Sat, Feb 14, 2015 at 3:18 PM, Christian Berendt
wrote:
> At the moment there are three columns in the Gerrit overiew page showing
> the status of a review request:
>
> * CR (Code-Review)
> * V (Verified)
> * Workflow (WF).
>
> After a core reviewer +2 (CR) a review r
Hello everyone,
There is regarding the following bug:
https://bugs.launchpad.net/neutron/+bug/1373359
May I know what is the significance of having the '*udp_port'* field in the
*'ml2_vxlan_endpoints*' table in Neutron DB, Do we have any plans in
future that we could use this field for synchroni
taplane between OVS and LinuxBridge which, by
>> > default, don't use the same UDP port for VXLAN.
>> >
>> > It might be useful for a cloud admin which wants to run some nodes
>> > with LB and some others with OVS.
>> >
>> >
>> &g
