At Thu, 24 Apr 2014 15:24:53 +0900,
IWAMOTO Toshihiro wrote:
At Thu, 24 Apr 2014 00:34:36 +0200,
ZZelle wrote:
[1 multipart/alternative (7bit)]
[1.1 text/plain; ISO-8859-1 (7bit)]
Hi Carl,
A clear l3 agent manager interface with hookable methods would clearly
simplify the
-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron][L3] Agent manager customization
Hi Carl,
A clear l3 agent manager interface with hookable methods would clearly
simplify the understanding, the dev/support.
Difficulties:
1. (un)deployment
At Thu, 24 Apr 2014 00:34:36 +0200,
ZZelle wrote:
[1 multipart/alternative (7bit)]
[1.1 text/plain; ISO-8859-1 (7bit)]
Hi Carl,
A clear l3 agent manager interface with hookable methods would clearly
simplify the understanding, the dev/support.
A reasonable set of hook points in the
Hi Carl,
A clear l3 agent manager interface with hookable methods would clearly
simplify the understanding, the dev/support.
Difficulties:
1. (un)deployment method names are associated to the triggering event not
to performed action:
- router deployment is done by _router_added
- router
Cedric,
I'm just getting back from a short vacation. Please excuse the delayed reply.
I have a feeling that this subject may have been discussed in the past
before I was very active in Neutron. So, others may chime in if I'm
missing something.
For the customizations that you're making, it
Hi everyone,
I would like to propose a change to simplify/allow l3 agent manager
customization and i would like the community feedback.
Just to precise my context, I deploy OpenStack for small specific business
use cases and i often customize it because of specific use case needs.
In
