Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 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 ====

21 Attendees

Summary:
   *  Repo structure proposal review update:
     * Aihua has made the first commit that will allow us to review the repo structure using Gerrit. The URL for review is https://gerrit.opnfv.org/gerrit/#/c/9 .
     * Timeline for this review: All comments must be submitted by: Tuesday 27th January 2015. [Action: vswitchperf committers]
   * Governance model review:
     * Lots of good questions here and discussion about the model.
     * The following updates need to be added to the model [Action: Maryam]
       * Role of reviewer to be defined
       * Integrate features/bugs with JIRA upfront
         * This would mean implicit addition of JIRA tags to commits to ensure they are associated with a planned item, or a fix for a known issue…
         * Will allow us to have agreement on changes upfront
         * Make sure it’s Gerrit enforced.
     * Follow up with Linux Foundation to make sure committers/reviewers, contributors and maintainers have the appropriate +1, +2 options for code review. [Action: Maryam/Mike]
   * Test-bed infrastructure 
     * When will we have access to the lab?
       * Access not available yet, work is ongoing to get the lab fully operational. 
       * Part of the lab will be dedicated to the vSwitch characterization project.
       * Project specific requirements are necessary to provide an accurate date for accessibility to the Lab. [Action: Maryam] Put together a proposal for community review at the next weekly sync.
   * Git Tags:
     * What tags will we use for various projects?
       * This will be dependent on the switches we use. The Suggestion would be to use the tag for latest stable release of a particular switch and take the appropriate tags (that the switch is compatible with) for any other projects the switch is dependent on. For example the current stable release for OVS is 2.3.1 and it’s compatible with DPDK 1.7.1… [Action: Maryam] Propose tags for community review at the next weekly sync.
   * Tools update 
     * IRC
       * IRC channel has been setup freenode (https://freenode.net/)
       * IRC channel: #opnfv-vswitchperf http://webchat.freenode.net/?channels=opnfv-vswitchperf
       * Meetbot has been integrated so minutes will automatically appear @ http://meetbot.opnfv.org/meetings/opnfv-vswitchperf/2015/ 
       * This info can also be found in the meeting details on the project wiki https://wiki.opnfv.org/wiki/vswitch_perf_characterization_meetings 
     * Bug tracking tool supported by Linux Foundation is JIRA, the project will integrate with this.
   * 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 ====

**Attendees**: Approx. 25 attendees 

**Notes**: 
  * **Opens

**
[Action]:  Mike to put in place IRC channel for next week’s meeting

Where do we store artifacts like VM images? Consensus that they really do not belong in GIT….

[Action]: Mike to raise this at Performance and Test group meeting on how to resolve as it won’t be a problem specific to this project. 

Raised today (Jan 15th); P&G group have taken an action to make a proposal on how to handle this project-wide

  * **Comments on Repo Structure proposal
**
Need directory for test specification (+ 1 by Aihua)

Plan not to include the source code in the repo but just to clone the Tags (+1 by Aihua)

Other comments: included in Aihua’s Google Docs review

[Action]: Aihua to present status of review at next week’s project meeting

  * **Project Repo and Development tools
**
Git Review in conjunction with Gerrit is set up as part of repo creation by Linux Foundation

This is being used in Huawei (GitReview). Operationally similar to GitPush. No objections to using this

Project Development Tools – what candidates? 

Code review: Gerrit… no objections

Bug tracking: Could use GitHub bug tracker (assuming we are building on GitHub – need to confirm with Linux Foundation) Alternative could be to use Bugzilla.

Bryan Sullivan has experience of GitHub Bug tracker – seems to be pretty effective +1

Bugzilla is acceptable fallback if GitHub bug tracker not available (Bryan again). 

Need to ensure we can enforce a mechanism that makes it clearly visible what bugs are being fixed (Gene Snider)

Ideally we should not re-invent the wheel, let’s use as much default from Linux Foundation as possible, unless consensus exists that it’s not acceptable

  * **Test Specification draft 
**
Maryam presented the structure of the test spec

Bryan: is there anything there from QoS perspective? No….Need to get feedback from community here.

Al Morton (AT&T): Happy to contribute to some parts of this. Mike to add Al as a contributor [done]

Al to send out links to some IETF benchmarking/performance RFCs and drafts [done]

  * **Governance structure
**
We need to agree a Governance and Review structure!

We are doing some trailblazing here from OPNFV perspective which may serve the benefit of the whole community

[Action]: Maryam to provide a detailed proposal to the mailing list on a Governance Model
Wiki

User Tools

Site Tools

Page Tools
