User Tools

Site Tools


Minutes of Technical Community Discussion on July 16, 2015

  • Date and Time: 6:00am PDT / UTC 13:00, Thursday July 16, 2015
  • Convener: Bin Hu (AT&T)
  • Participants:
    • Ana Cunha (Ericsson)
    • Brian Ketchum (Spirent)
    • Brian Smith (Bell Canada)
    • Bryan Sullivan (AT&T)
    • Dan Druta (AT&T)
    • Eric Multanen (Intel)
    • Gang Chi (Huawei)
    • Juha Oravainen (Nokia)
    • Kevin Luehrs (Cable Labs)
    • Kubi / Jean.Gaoliang (Huawei)
    • Larry Lamers (VMWare)
    • Malla Reddy Sama (DoCoMo)
    • Manuel Rebellon (Sandvine)
    • Mark D Gray (Intel)
    • Michael Godley (Intel)
    • Narinder Gupta (Canonical)
    • Parviz Yegani (Juniper)
    • Pasi Vaananen (Stratus)
    • Patrick Liu (Huawei)
    • Prakash Ramchandran (Huawei)
    • Praveen Kumar
    • Shuai Chen (Huawei)
    • Stuart Mackie(Juniper)
    • Ulrich Kleber(Huawei)
    • Weidong Chao (Huawei)
    • Wenjuan Dong (ZTE)
    • Yuanzhen (Janice) Li (ZTE)
  • Upstream Feature Development and Cross-Project Collaboration
    • Status update on active items

No update from community

  • Status update on areas of interest

No update from community

  • Draft Blueprints Discussion
    • TBD
  • Other cross-project topics

No update from community. Bin will look into details of the projects

  • Project Proposal Discussion
  • New Integration project proposals

Author was not present. Postponed.

Author was not present. Postponed.

Hongbo Tian (Huawei) introduced this proposal.

Bryan (AT&T) asked that since this proposal is test and performance focused, how is it related to other efforts such as vSwitch Performance test? Uli (Huawei) answered that the test results from other projects will be taken into this project. And this project will analyze the test results and identify the bottlenecks. Of course, this project will have our own tests as well if not covered by other projects.

Manuel (Sandvine) indicated that it is a very important project. We need to manage the cycles when we look for bottleneck in network and find bottlenecks. Hongbo said that the framework will resolve the cycle need.

Bryan (AT&T) further asked what will be produced as the result of this project? Will there be some tools? If a report of bottleneck is produced, will you produce any Blueprints for upstream to address the bottlenecks?

Hongbo indicated that a framework, a set of tools and code developed will be used to test and produce the result, which is a report of identified bottlenecks. Once bottlenecks are found, we will talk to relevant projects for improvement. There will be a list of issues where bottleneck appears. If we can, we will give suggestions and work with other projects and upstream community to address those bottlenecks.

Bryan (AT&T) asked if those tools will be used in labs or production environment. Hongbo answered that the original motivation is to find bottlenecks before production. So we currently are not focusing on production, but focusing on labs in order to address bottlenecks before production. This focus may change in the future.

Bryan (AT&T) asked if the project intends to use existing tools. Hongbo said that the project will reuse existing tools as many as it can. New tools will be developed if there is no existing tools available.

Bryan (AT&T) asked if those existing tools are already part of OPNFV today, or will they be brought in. Hongbo said that the project will bring in those tools, and develop new tools if not available.

Bryan suggested to add the list of existing tools on the proposal.

Manuel suggested to have a special Q&A session to address further comments.

The group agreed:
- A list of existing tools, and some other improvements need to be added in the proposal wiki page
- Hongbo will dial in with a better audio device next week
- Manuel will initiate a discussion in mailing list with his further comments
- Have a Q&A session of this proposal as the first agenda item next week

  • New Integration project proposals

Weidong (Huawei) introduced this proposal.

Uli gave background information that the work of Compass installer has been agreed on April 9 (, but as part of BGS effort. Because BGS is being restructured to Genesis as an umbrella of all installers, and installers are now worked as separate projects, we need to have a specific project for current Compass installer work. Compass project will support Genesis requirements.

Malla (DoCoMo) asked what is the difference between Compass and Escalator. Uli indicated that Escalator is for upgrading, and Compass is for installation.

Group agreed to recommend this proposal for TSC creation review.

Mark Gray (Intel) introduced this project.

Prakash (Intel) asked if this project would consider the integration with SDN (OVN), and whether to support any unique protocol (e.g. a new NIC procotol in OVN). Mark responded that the project intends to get input from OPNFV, and improve OVS in OVS community. So as long as OPNFV gives input of requirement, if it is related to OVS, we will address in OVS community.

Stuart (Juniper) asked if this project will work as liaison with installer projects. Mark indicated that it will be liaison with installers, get input and requirement, and then liaison with OVS. Bin indicated its role is like a bridge between OPNFV and OVS for the OVS performance improvement.

Mark further introduced that userspace OVS as experimental tag. This experimental tag will not be removed in 2.4. Perhaps in 2.5, but TBD.

The group agreed that this proposal is quite mature technically, and recommend for TSC creation review.

Stuart (Juniper) introduced this proposal. Parviz also gave some background information.

Due to time constraint, the meeting ended when the Test meeting started at 7am PDT. The discussion will continue next week.

Meeting adjourned.

wiki/tc_minutes_20150716.txt · Last modified: 2015/07/16 19:20 by Bin Hu