Open Stack

Salvatore Orlando <sorlando at nicira.com> wrote on 11/18/2014 04:15:35 PM:

> From: Salvatore Orlando <sorlando at nicira.com>
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev at lists.openstack.org>
> Date: 11/18/2014 04:19 PM
> Subject: Re: [openstack-dev] [Neutron][L2 Agent][Debt] Bootstrapping
> an L2 agent debt repayment task force
>
> I think we should also get rid of some nonsenses in the way events
> are processed by the l2 agent. Carl did something similar for the l3
agent.
> In the past release cycle I put some patches to avoid event
> starvation or to prevent the same event to be processed multiple
> times, but I did not address the root cause of the issue.
>
> This is probably already in the etherpad under the bullet "ovsdb
> monitor improvements". It seems the current assignee is Terry, but I
> guess nobody would mind If I submit a spec for it just to assess
> what are the point of conflicts with other tasks, and then maybe
> either I or Terry do the actual work.
>
> Regarding the modular l2 agent, I think that was the one item for
> which the consensus was to defer. Not because it wasn't deemed
> important. I think the concern here was that it was a major
> refactoring which pretty much would have blocked all other
> activities. But I am happy to reconsider or find a strategy to
> ensure the modular l2 agent could fit into kilo plans.
>


I was not aware of this development regarding Modular L2 Agent. It wasn't
obvious from the etherpad but that is understandable. There is so much you
can capture in an etherpad. Thanks for clarifying it promptly.



> Salvatore
>
> On 18 November 2014 19:32, Mohammad Banikazemi <mb at us.ibm.com> wrote:
> I had done some work on looking at L2 agents and identifying how we
> may want to go about creating a Modular L2 Agent framework to make
> the agent code more modular, avoid code replication across multiple
> L2 agents, and to make adding new features and writing new agents
> (if/when necessary) easier. I will be happy to take a stab at
> writing the blueprint/spec based on that work and what is specified
> in the etherpad [1].
>
> I had to take a few weeks off from work and therefore had to miss
> the Summit; This happened right around the time that "paying our
> technical debts" was becoming a common phrase in Neutron (for good
> reasons) and from what I can gather from the etherpad [1] the scope
> for this effort may have expanded and there are others who have
> volunteered to work on various aspects of this effort. So, if there
> are others who want to start the "task force" by writing this
> blueprint/spec, that is perfectly fine with me. If not, I will be
> happy to get that started.
>
> Best,
>
> Mohammad (banix)
>
>
>
> [image removed] Carl Baldwin ---11/18/2014 12:19:00 PM---At the
> recent summit, we held a session about debt repayment in the Neutron
> agents [1].  Some work w
>
> From: Carl Baldwin <carl at ecbaldwin.net>
> To: OpenStack Development Mailing List
<openstack-dev at lists.openstack.org>
> Date: 11/18/2014 12:19 PM
> Subject: [openstack-dev] [Neutron][L2 Agent][Debt] Bootstrapping an
> L2 agent debt repayment task force
>
>
>
>
> At the recent summit, we held a session about debt repayment in the
> Neutron agents [1].  Some work was identified for the L2 agent.  We
> had a discussion in the Neutron meeting today about bootstrapping that
> work.
>
> The first order of business will be to generate a blueprint
> specification for the work similar, in purpose, to the one that is
> under discussion for the L3 agent [3].  I personally am at or over
> capacity for BP writing this cycle.  We need a volunteer to take this
> on coordinating with others who have been identified on the etherpad
> for L2 agent work (you know who you are) and other volunteers who have
> yet to be identified.
>
> This "task force" will use the weekly Neutron meeting, the ML, and IRC
> to coordinate efforts.  But first, we need to bootstrap the task
> force.  If you plan to participate, please reply to this email and
> describe how you will contribute, especially if you are willing to be
> the lead author of a BP.  I will reconcile this with the etherpad to
> see where gaps have been left.
>
> I am planning to contribute as a core reviewer of blueprints and code
> submissions only.
>
> Carl
>
> [1] https://etherpad.openstack.org/p/kilo-neutron-agents-technical-debt
> [2] http://eavesdrop.openstack.org/meetings/networking/2014/
> networking.2014-11-18-14.02.html
> [3] https://review.openstack.org/#/c/131535/
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141118/2e021d45/attachment.html>