On 10 June 2014 18:18, Irena Berezovsky ire...@mellanox.com wrote:
Hi Luke,
Very impressive solution!
Thanks for the kind words!
I do not think there is a problem to keep agent out of the tree in a short
term, but would highly recommend to put it upstream in a longer term.
You will
Hi Luke,
Please see my comments inline.
BR,
Irena
From: Luke Gorrie [mailto:l...@tail-f.com]
Sent: Monday, June 09, 2014 12:29 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][ml2] Too much shim rest proxy
mechanism drivers in ML2
On 6
Hi Irena,
Thanks for the very interesting perspective!
On 10 June 2014 10:57, Irena Berezovsky ire...@mellanox.com wrote:
*[IrenaB] The DB access approach was previously used by OVS and
LinuxBridge Agents and at some point (~Grizzly Release) was changed to use
RPC communication.*
That is
] [Neutron][ml2] Too much shim rest proxy
mechanism drivers in ML2
Hi Irena,
Thanks for the very interesting perspective!
On 10 June 2014 10:57, Irena Berezovsky
ire...@mellanox.commailto:ire...@mellanox.com wrote:
[IrenaB] The DB access approach was previously used by OVS and LinuxBridge
On 6 June 2014 10:17, henry hly henry4...@gmail.com wrote:
ML2 mechanism drivers are becoming another kind of plugins. Although
they can be loaded together, but can not work with each other.
[...]
Could we remove all device related adaption(rest/ssh/netconf/of... proxy)
from these mechanism
