FYI, I pushed code review for the blueprint. The patch is missing unitest
and tempest. It's only submitted for discussion.
The patch implements two-step commit process similar to ML2, but it's not
intended to solve all race conditions. Another thing I think worth
discussing is how to work with
Let me try to clarify things a bit.
At Fri, 25 Oct 2013 08:44:05 +0900,
Itsuro ODA wrote:
Hi Gray,
Thanks for your response.
Our plan is as follows:
* LVS driver is one of lbaas provider driver.
It communicates with l3_agent instead of lbaas_agent.
LVS agent part will reside in the
I just wrote a short spec on the wiki page and link it to the blueprint. I
should have done this when we registered the BP.
Please let me know if you have any question.
Thanks,
Gary
On Thu, Oct 24, 2013 at 5:35 PM, Gary Duan gd...@varmour.com wrote:
Hi, Geoff,
This is because I haven't
Hi,
I've registered a BP for L3 router service integration with service
framework.
https://blueprints.launchpad.net/neutron/+spec/l3-router-service-type
In general, the implementation will align with how LBaaS is integrated with
the framework. One consideration we heard from several team
Hi,
We are going to implement 2-arm type lbaas using LVS, and have submitted
the following BPs.
https://blueprints.launchpad.net/neutron/+spec/lbaas-support-routed-service-insertion
https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-driver
Hi, Oda-san,
Thanks for your response.
L3 agent function should remain the same, as one driver implementation of
L3 router plugin.
My understanding is your lbaas driver can be running on top of L3 agent and
LVS' own routing services. Is my understanding correct?
Thanks,
Gary
On Thu, Oct 24,
Gary,
In the context of the nvp plugin we use a mechanism for enabling 'advanced'
capabilities of a router leveraging a 'router_service_type' extension.
this allow us to configure two types of routers, one which does just L3
forwarding, NAT and a few other things, and another one which also has
Hi Gray,
Thanks for your response.
Our plan is as follows:
* LVS driver is one of lbaas provider driver.
It communicates with l3_agent instead of lbaas_agent.
* For l3_agent side, I think the implementation is same as
fwaas. L3NATAgent inherits like LVSL3AgentRpcCallback
class added which
I’m getting a “Not allowed here” error when I click through to the BP. (Yes,
I’m subscribed.)
On Oct 24, 2013, at 11:56 AM, Gary Duan gd...@varmour.com wrote:
Hi,
I've registered a BP for L3 router service integration with service framework.
Hi, Geoff,
This is because I haven't added spec to the BP yet.
Gary
On Thu, Oct 24, 2013 at 4:51 PM, Geoff Arnold ge...@geoffarnold.com wrote:
I’m getting a *“**Not allowed here”* error when I click through to the
BP. (Yes, I’m subscribed.)
On Oct 24, 2013, at 11:56 AM, Gary Duan
10 matches
Mail list logo
