Differences

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

--- wiki:vswitch_meeting_minutes [2015/01/22 13:45]
Maryam Tahhan [Jan/14/2015]
+++ wiki:vswitch_meeting_minutes [2015/03/19 11:19] (current)
Maryam Tahhan [THIS PAGE HAS BEEN MOVED TO]
@@ Line 1: / Line 1: @@
-====== Vswitch Performance Characterization Meeting Minutes ======
+====== THIS PAGE HAS BEEN MOVED TO  ======
+https://wiki.opnfv.org/meetings/vsperf
+====== Please help move this page ======
+  * NOTE: Meeting info pages for each project should be moved to the ''[[/meetings/|https://wiki.opnfv.org/meetings/]]'' folder.
+  * Do not place meeting related pages under the ''/wiki'' or ''/project-name'' folders.
+  * ALSO: Project info pages should not be under the ''/wiki'' folder.
+  * Project related pages should be located under the ''/'' (root) folder.
+  * To move your page you should create a new page and update this one with a note stating it has been moved.
 ----
+====== vSwitch Performance Characterization Meeting Minutes ======
+----
+==== Feb/11/2015 ====
+**Mailing List**
+  * We won't be able to setup a separate mailing list, however we have setup a topic (vswitchperf) under the OPNFV tech discuss mailing list that people can subscribe to.
+  * This info is available on the project wiki https://wiki.opnfv.org/characterize_vswitch_performance_for_telco_nfv_use_cases
+**TOIT**
+  * Code is being cleaned up and prep'ed for release
+  * Slides to be sent out by Stephen
+  * Feedback given that tests should have a configurable duration.
+Admin/Infrastructure point of contact for the project: Maryam Tahhan
+**Patch reviews**
+  * One +1 for the intro. Need another committer to +1 to progress that test spec section to the next phase
+  * Review cycle to be reduced to 2 days rather than 3 days
+  * Features to be tested patch rework started today by Maryam Tahhan
+  * Owner column added to patch review wiki (https://wiki.opnfv.org/wiki/vswitchperf_test_spec_review) so that other contributors can also re-work patches.
+  * Patch reviews and rework should be conducted in the order specified in the table (top to bottom).
+**Project Leader**
+  * Will need to select one when the selection process is hardened.
+==== Feb/04/2015 ====
+Minutes:
+  * Stephen Finucane gave an overview/demo of TOIT
+    * TOIT is an OVS test integration framework written in Python that Intel would like to share with the community for re-use  for this  project. [Action: Stephen F. to send out slides].
+    * The framework is generic and licensed under a permissible apache license.
+    * Right now it supports OVS and IXIA: IxOS and IxNetworks but the framework can be easily extended to include other traffic generators and switches.
+    * Community feedback was very positive, an initial commit for the phy-phy test cases is to be made to gerrit. [Action: Stephen F.]
+    * Out of cycle sessions will be setup to walkthrough the code.
+Project updates:
+  * Initial code reviews for test spec are open. The test spec has been broken down into sections and committed to gerrit for review.
+    * Question: why not a single commit? Answer: This is to avoid continuous reviewing sections of a doc that we approve.
+    * In an effort to co-ordinate reviews, so sections of the test spec get pushed to gerrit, open reviews will be documented @https://wiki.opnfv.org/wiki/vswitchperf_test_spec_review
+    * The suggested review cycle is 3 Working days.
+  * Governance model roles for committed and contributor have been updated to the wording from the TSC-Charter (https://wiki.opnfv.org/wiki/vswitchperf_governance_model)
+  * OPNFV lab HW spec for the project can be found here: https://wiki.opnfv.org/wiki/vswitch_work_environment
+    * Question, what happens if we want to get different NICs…? [Action: Maryam to follow up with Trevor Cooper]
+  * Tools:
+    * JIRA has been setup.
+      * Project name is VSPERF.
+      * Please make sure you can access the project and can see the associated issues.
+      * Gerrit now enforces a JIRA tag for commits.
+  * Opens:
+    * Do we need a separate mailing list?
+    * It’s difficult to follow the project updates via the current/generic opnfv-tech-discuss mailing list. [Action: Maryam to follow up with Linux Foundation]
+  * General Wiki updates:
+    * Coding Guidelines : OPNFV Coding Guidelines
+    * OPNFV Developer Resource Page : Getting started with your account, Gerrit and Git
+    * HW Spec (specified above)
+    * Open Gerrit reviews (specified above)
+    * Governance model wording (specified above)
+  * Open Gerrit review for repo structure (https://gerrit.opnfv.org/gerrit/#/c/9/ )
+    * The repo structure review has received a single +1 from one committer. [Action: A committer to review and if applicable provide a second +1 so the patch can committed to our repo]
 ==== Jan/21/2015 ====
@@ Line 38: / Line 108: @@
    * Test spec update:
      * The test spec has been updated with Aihua, Srini and Al’s comments. We propose uploading the test spec to Gerrit in sections for review, for e.g. each test will be a separate review in Gerrit. General sections like the intro and methodology will be submitted as one patch.
 ==== Jan/14/2015 ====

Wiki

User Tools

Site Tools

Differences

Page Tools