User Tools

Site Tools


project_proposals:cperf

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
project_proposals:cperf [2015/08/20 08:05]
Daniel Farrell [Scope] Readability
project_proposals:cperf [2015/09/02 17:58]
Daniel Farrell [Committers and Contributors] Add docs clarifying what we expect from committers
Line 7: Line 7:
 ==== Project description ==== ==== Project description ====
  
-The Controller Performance Testing (cperf) project will serve as a performance testing environment for NFV, with a specific focus on the controller portion of the stack.+The Controller Performance Testing (cperf) project will serve as a performance testing environment for the SDN controller portion of the large, realistic, automated deployments required by OPNFV.
  
 The newly created OpenDaylight Performance Group, which consists of the upstream ODL perf testing community, has committed to bootstrapping the effort. Because of the group'​s background, the initial focus will be ODL, but the cperf project explicitly hopes to leave the controller part of the test matrix open and will welcome collaboration with other controller communities. The newly created OpenDaylight Performance Group, which consists of the upstream ODL perf testing community, has committed to bootstrapping the effort. Because of the group'​s background, the initial focus will be ODL, but the cperf project explicitly hopes to leave the controller part of the test matrix open and will welcome collaboration with other controller communities.
Line 35: Line 35:
 Project Leader Project Leader
   * Daniel Farrell (dfarrell@redhat.com,​ IRC: dfarrell07)   * Daniel Farrell (dfarrell@redhat.com,​ IRC: dfarrell07)
 +
 +We give committer rights based a history of contributions over time. We typically at least expect committers to have:
 +
 +  * Contributed a substantial number of quality patches to relevant upstream projects.
 +  * Given quality code reviews to relevant upstream projects over an extended period of time.
 +  * Shown a solid understanding of the relevant version control, issue tracking, continuous integration and project governance systems.
  
 Committers Committers
Line 51: Line 57:
   * Kailash Khalasi (kkhalasi@iix.net)   * Kailash Khalasi (kkhalasi@iix.net)
   * Venkatrangan Govindarajan (venkatrangang@hcl.com)   * Venkatrangan Govindarajan (venkatrangang@hcl.com)
-  * Vasanthan Balasubram(vasanthan_balasubram@dell.com)+  * Vasanthan Balasubram (vasanthan_balasubram@dell.com) 
 +  * Zhanghaoyu (zhanghaoyu7@huawei.com)
 ==== Planned Deliverables ==== ==== Planned Deliverables ====
  
Line 64: Line 71:
 ** Repo name: ** cperf \\ ** Repo name: ** cperf \\
 ** Project Category: ** Integration & Testing \\ ** Project Category: ** Integration & Testing \\
-** Lifecycle State: ** Proposed ​\\+** Lifecycle State: ** Incubation ​\\
 ** Primary Contact: ** Daniel Farrell \\ ** Primary Contact: ** Daniel Farrell \\
 ** Project Lead: ** Daniel Farrell \\ ** Project Lead: ** Daniel Farrell \\
Line 75: Line 82:
 Jamo Luhrsen, jluhrsen@redhat.com,​ IRC: jamoluhrsen \\ Jamo Luhrsen, jluhrsen@redhat.com,​ IRC: jamoluhrsen \\
 Marcus Williams, marcus.williams@intel.com,​ IRC: mgkwill \\ Marcus Williams, marcus.williams@intel.com,​ IRC: mgkwill \\
-** Link to TSC approval: ** Not yet approved ​\\  +Tim Rozet, trozet@redhat.com,​ IRC: trozet \\ 
-** Link to approval of additional submitters: ** Not yet approved ​\\+** Link to TSC approval: ** [[http://​ircbot.wl.linuxfoundation.org/​meetings/​opnfv-meeting/​2015/​opnfv-meeting.2015-09-01-13.59.log.html | TSC vote]] ​\\  
 +** Link to approval of additional submitters: ** None \\
project_proposals/cperf.txt · Last modified: 2015/09/02 18:16 by Daniel Farrell