Open Stack

Folks,

I'm on the ODL TSC (Best equivalent is the OpenStack TC) mailing list and these emails came across today.   It's great to see the board concerned with Product issues, and to be fair, the TSC is more focused on product issues than our TC, but these three emails show how not to mix product issues with Open Source, I think.

First email is on the bottom.

--Rocky

From: tsc-bounces at lists.opendaylight.org [mailto:tsc-bounces at lists.opendaylight.org] On Behalf Of Luis Gomez
Sent: Thursday, March 26, 2015 12:54
To: Chris Price
Cc: board at lists.opendaylight.org; tsc at lists.opendaylight.org
Subject: Re: [OpenDaylight TSC] board requests of the TSC

Hi Chris,

Without entering in the format (I always prefer straight talking than formal talking) I think you summarized very well what the Board tries to communicate to the TSC and the community. I do not know if because of the format I heard people screaming on things that IMHO we should be doing in the TSC for long time. As lets be honest here, I like the bottom-top approach but can anyone tell how many committers and PTLs in ODL have scalability, stability, security and performance, uses cases or become mature at the top of the priority list? I can give example if asked of perf bugs sitting in queues for months and I do not blame projects but TSC (specially myself) for not pushing this enough.

BR/Luis



On Mar 26, 2015, at 11:51 AM, Chris Price <chrispriceab at gmail.com<mailto:chrispriceab at gmail.com>> wrote:

Hi Colin,

Let's kick off the follow up discussion from the TSC call:

While much of this e-mail discussed activities that are both valuable and productive to promote in the community there are components of the e-mail that may be perceived as less so.  Rather that niggle over the nomenclature of the e-mail I might suggest we strip the dialog back to a set of joint objectives for the board and technical community to find ways to achieve.

One way to ask for the steering committee to help steer the community is by agreeing on a common set of objectives and allowing the community (whom we would want to achieve them) to determine the best way of doing that.

As I read this list it does not so much present as a set of objectives as it does a checklist to report on.  Can these points be re-communicated as a set of objectives that the board as stakeholders see's as valuable for the OpenDaylight community to accomplish with some reasoning why?  This could be the starting point for a productive and less divisive dialog.

Maybe the request is to:
                Improve the Stability, Scalability, Security and Performance of the project.
                Evaluate if it is possible to Identify a minimum set of baseline project components to drive to a mature state
                Find ways of focusing the community on the development and improvement of certain use cases per release

If I read the e-mail below accurately.

/ Chris

From: Colin Dixon <colin at colindixon.com<mailto:colin at colindixon.com>>
Date: Thursday 26 March 2015 18:21
To: "tsc at lists.opendaylight.org<mailto:tsc at lists.opendaylight.org>" <tsc at lists.opendaylight.org<mailto:tsc at lists.opendaylight.org>>, "board at lists.opendaylight.org<mailto:board at lists.opendaylight.org>" <board at lists.opendaylight.org<mailto:board at lists.opendaylight.org>>
Subject: [OpenDaylight TSC] board requests of the TSC

Coming out of a recent meeting, the board has made the following requests of the TSC. We'll cover them (or at least start) during today's TSC meeting.

The members of the TSC who also sit on the board will be there to help provide context and we can start thinking about how we can address these requests.

Thanks,
--Colin

* The board seeks to improve Stability, Scalability, Security and Performance (S3P) of future ODL Simultaneous releases, and requests the TSC to create a clear S3P criteria / requirement and metrics to measure S3P in each release.  The board further asks the TSC to update the Project Life Cycle document to support the S3P concept in future releases and as a criteria for upgrading a project to a "Mature" state.

* The board also requests that the TSC recommends a list of projects that constitute the "ODL kernel" (i.e. providing key and essential functionality without which, ODL can't deliver basic functionality, including user expected most basic plugins) for future ODL releases. Proposed list for TSC consideration includes: Controller (including MD-SAL/Yang), OpenFlow plugin, neutron plugin, network virtualization code, AAA, OVSDB and topology

* The board recommends that ODL focuses on the following Use Cases for Lithium and Beryllium releases, (at a minimum): Network Virtualization and Service Chaining. To support this Use Case focus, the board also requests the TSC to define the list of projects and capabilities needed and build tests to validate they adhere to the TSC defined S3P criteria. The board further asks the TSC to work with the ODL Advisory Group to gather their feedback for these use cases, and report to board periodically on its progress on these tasks.

* The board requests the TSC to prepare a plan for shipping the "ODL kernel" and the projects required for the Use Cases (listed below) as "Mature" projects with S3P for the Beryllium release as part of the simultaneous release and advise he board on best effort plan for partially achieving these goals for Lithium. The TSC will provide the board with resources requirement estimate for achieving the goal, as well as a list of expected gaps and suggestions for addressing them.

* The board tasks TSC to create a comprehensive test plan to achieve and validate S3P including identifying the resource needed for Lithium and Beryllium (per "ODL kernel" and targeted Use Cases) and present to the Board for discussion in its next meeting and get the board's support in identifying additional resources. These may include platform performance, datastore and IO performance, per TSC decisions

* The board requests the TSC to recommend a plan for converging future ODL releases, on a small set (ideally one) of projects/technologies essential for the use cases identified for those releases.
_______________________________________________ TSC mailing list TSC at lists.opendaylight.org<mailto:TSC at lists.opendaylight.org> https://lists.opendaylight.org/mailman/listinfo/tsc _______________________________________________
TSC mailing list
TSC at lists.opendaylight.org<mailto:TSC at lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/tsc