project_proposals:cperf
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
project_proposals:cperf [2015/08/12 15:03] Daniel Farrell [Committers and Contributors] |
project_proposals:cperf [2015/09/02 18:16] (current) Daniel Farrell [Committers and Contributors] Attempt to answer some committer/contributor FAQ, refactor that section's layout |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ==== Project description ==== | ==== Project description ==== | ||
| - | The Controller Performance Testing (cperf) project will serve as a full-stack 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. | ||
| - | The cperf project also hopes to build a community that fosters collaboration between benchmarking experts from academic/standards backgrounds and the upstream engineers who implement actual perf benchmarks in modern CI environments. | + | The cperf project also hopes to serve as a community that fosters collaboration between benchmarking experts from academic/standards backgrounds and the upstream engineers who implement actual perf benchmarks in modern CI environments. |
| ==== Scope ==== | ==== Scope ==== | ||
| - | Simply stated, the Controller Performance Testing project's scope is to build performance tests for SDN controllers in the large, automated deployments supported by OPNFV. | + | The Controller Performance Testing project's scope is to build performance tests for SDN controllers in realistic, large, automated deployments. |
| Cperf, in the spirit of OPNFV's upstream-first focus, will work to solve problems primarily in the relevant upstream communities. For example, when creating OpenDaylight performance tests, cperf will consume and contribute to the [[https://wiki.opendaylight.org/view/CrossProject:Integration_Group | OpenDaylight Integration Team]]'s Python and Robot test libraries vs re-implementing that logic. When deploying OpenDaylight in a complex automated deployment, cperf will leverage the ODL [[https://wiki.opendaylight.org/view/Project_Proposals:Integration_Packaging | Integration/Packaging]] project's automated deployment tools as well as OPNFV's subsequent OpenStack integrations (via [[https://wiki.opnfv.org/get_started | BGS/Genesis]] and subsequent projects). | Cperf, in the spirit of OPNFV's upstream-first focus, will work to solve problems primarily in the relevant upstream communities. For example, when creating OpenDaylight performance tests, cperf will consume and contribute to the [[https://wiki.opendaylight.org/view/CrossProject:Integration_Group | OpenDaylight Integration Team]]'s Python and Robot test libraries vs re-implementing that logic. When deploying OpenDaylight in a complex automated deployment, cperf will leverage the ODL [[https://wiki.opendaylight.org/view/Project_Proposals:Integration_Packaging | Integration/Packaging]] project's automated deployment tools as well as OPNFV's subsequent OpenStack integrations (via [[https://wiki.opnfv.org/get_started | BGS/Genesis]] and subsequent projects). | ||
| Line 33: | Line 33: | ||
| ==== Committers and Contributors ==== | ==== Committers and Contributors ==== | ||
| - | Project Leader | + | === Project Leader === |
| * Daniel Farrell (dfarrell@redhat.com, IRC: dfarrell07) | * Daniel Farrell (dfarrell@redhat.com, IRC: dfarrell07) | ||
| - | Committers | + | === Committers === |
| * Daniel Farrell (dfarrell@redhat.com, IRC: dfarrell07) | * Daniel Farrell (dfarrell@redhat.com, IRC: dfarrell07) | ||
| * Luis Gomez (ecelgp@gmail.com, IRC: LuisGomez) | * Luis Gomez (ecelgp@gmail.com, IRC: LuisGomez) | ||
| Line 43: | Line 45: | ||
| * Tim Rozet (trozet@redhat.com, IRC: trozet) | * Tim Rozet (trozet@redhat.com, IRC: trozet) | ||
| - | Contributors | + | 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. | ||
| + | |||
| + | === Contributors === | ||
| * Sandeep Gangadharan (sandeep.gangadharan@hp.com) | * Sandeep Gangadharan (sandeep.gangadharan@hp.com) | ||
| * Al Morton (acmorton@att.com) | * Al Morton (acmorton@att.com) | ||
| * Carol Sanders (carolsand@gmail.com) | * Carol Sanders (carolsand@gmail.com) | ||
| + | * Nitin Agarwal (nitinagarwal3006@gmail.com) | ||
| * Praveen Mala (praveen.mala@intel.com) | * Praveen Mala (praveen.mala@intel.com) | ||
| * 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) | ||
| + | |||
| + | You don't have to be an "official" Contributor to contribute to cperf! The people above have documented that they explicitly hope to contribute to cperf, but that's optional - all contributions are equally welcome. | ||
| + | |||
| + | You don't need to ask permission to add yourself to the list of contributors above. | ||
| ==== Planned Deliverables ==== | ==== Planned Deliverables ==== | ||
| Line 63: | Line 78: | ||
| ** 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 74: | Line 89: | ||
| 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.1439391780.txt.gz · Last modified: 2015/08/12 15:03 by Daniel Farrell
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
