This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
cperf [2015/09/28 02:38] Daniel Farrell Create initial wiki, including basic communication info |
cperf [2016/03/15 22:55] (current) Al Morton [Communication] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== SDN Controller Performance Testing (CPerf) ====== | ====== SDN Controller Performance Testing (CPerf) ====== | ||
- | |||
- | //This wiki is under construction // | ||
CPerf is a new OPNFV project focused on SDN controller performance testing. For more information, see the [[https://wiki.opnfv.org/project_proposals/cperf | project proposal]]. | CPerf is a new OPNFV project focused on SDN controller performance testing. For more information, see the [[https://wiki.opnfv.org/project_proposals/cperf | project proposal]]. | ||
- | |||
- | The project infrastructure for CPerf mostly doesn't exist yet. Please have patience and feel free to jump in and contribute anywhere. :) | ||
==== Communication ==== | ==== Communication ==== | ||
- | In accordance with OPNVF's attempts to reduce the number of synchronous meetings (like weekly calls), and because CPerf is just getting started, there isn't currently a dedicated CPerf meeting. | + | === Meetings === |
+ | |||
+ | CPerf has a quick, informal weekly sync meeting. | ||
+ | |||
+ | See the [[https://wiki.opnfv.org/meetings#cperf_meeting | main meetings wiki]] or [[meetings/cperf|meetings/CPerf]]. | ||
When possible, a CPerf representative will attend the [[https://wiki.opnfv.org/meetings/test | OPNFV Test and Performance weekly meeting]]. | When possible, a CPerf representative will attend the [[https://wiki.opnfv.org/meetings/test | OPNFV Test and Performance weekly meeting]]. | ||
- | The current primary communication methods for CPerf are email and IRC. | + | === IRC === |
+ | |||
+ | The best way to reach CPerf contributors is via IRC. Please join #opnfv-cperf on Freenode. The [[https://wiki.opnfv.org/project_proposals/cperf#committers_and_contributors | IRC handles of the committers]] are listed on CPerf's project proposal. | ||
+ | |||
+ | === Email === | ||
People interested in CPerf should subscribe to the [[https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss | opnfv-tech-discuss]] mailing list and (optionally) set a [cperf] tag filter in Mailmain. To use the tag, simply preface email subjects with "[cperf]". | People interested in CPerf should subscribe to the [[https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss | opnfv-tech-discuss]] mailing list and (optionally) set a [cperf] tag filter in Mailmain. To use the tag, simply preface email subjects with "[cperf]". | ||
- | The most relevant IRC channels to CPerf are #opnfv, #opnfv-testperf and #opnfv-cperf on Freenode. The [[https://wiki.opnfv.org/project_proposals/cperf#committers_and_contributors | IRC handles of the committers]] are listed on CPerf's project proposal. | + | === Release C Colorado === |
+ | |||
+ | [[cperf:cperf_project_rel_c| Cperf Release C Plan ]] |