• Date and Time: 6:00am PST / UTC 14:00, Thursday November 19, 2015
• Convener: Bin Hu (AT&T)
• Participants:
  • Al Morton (AT&T)
  • Ana Cunha (Ericsson)
  • Bryan Sullivan (AT&T)
  • Christopher Price (Ericsson)
  • Dan Druta (AT&T)
  • Dave Neary (Red Hat)
  • Debra Scott (OPNFV)
  • Edgar St Pierre (EMC)
  • Ildiko Vancsa (Ericsson)
  • Larry Lamers (VMWare)
  • Mark Szczesniak (Casa)
  • Ulrich Kleber (Huawei)
  • Vikram Dham (Dell)

Team started to discuss the status of review of Blueprints. Dave Neary (RedHat) will send an email to community to look for:
- Update of projects regarding which upstream open source projects are relevant (Code)
- Any Blueprints each project has planned for Mitaka, and we can keep track on (BP)
- Blueprint peer review from OPNFV, if a draft is ready for review

• Upstream Feature Development and Cross-Project Collaboration - TBD
  • Status update on active items
  • Status update on areas of interest
  • Draft Blueprints Discussion
  • Other cross-project topics

None. Security group update will be presented at next meeting

• Project Proposal Discussion
  • Active project proposals
    • OVN for NFV

Vikram (Dell) introduced this project proposal (https://wiki.opnfv.org/_media/ovn-opnfv-summit2015.pdf).

Vikram started with pre-ovn status (i.e. problem statement), and introduced what is ovn. Uli (Huawei) asked if there is an open source project for ovn. Vikram replied yes, and the source code is part of ovs. Dave Neary (RedHat) further indicated that there is no underlay network management. In south bound, it only manages ovs virtual switch, but not the openflow physical switch.

Vikram (Dell) then introduced ovn architecture, and the mapping of logical flows to physical flows. Vikram further shared what is happening in OpenStack, i.e. OpenStack Neutron plugin focuses on OpenStack APIs,and ovn handles solving networking problems. So ovn+OpenStack means agentless lean networking.

Vikram then introduced networking-ovn project in OpenStack, which is the integration points for ovn with Neutron. Vikram further introduced ovn in ETSI NFV Reference Architecture, and the constructs for ETSI NV.

Uli (Huawei) asked if the author has looked at VNFFG project in OPNFV, which may be related to use of Neutron API for SFC. Vikram said that he would look into it. But nonetheless, it has high risk in Mitaka. Uli further suggested to look into ONOSFW project in OPNFV as well. Vikram said that he is not sure how ONOS is working in terms of SFC, and does it support NSH? Uli clarified that he is not suggesting any overlap. But ovn4nfv needs to be aware of those projects (VNFFG and ONOSFW), and including OpenContrail Networking.

Bryan (AT&T) asked what is the relationship between ovn and ONOSFW/Contrail. Vikram explained that Contrail uses its own vRouter instead of ovn, and doesn't use ovs. He is not sure of ONOS.

Chris Price (Ericsson) indicated that ovn is another SDN solution, and an alternative of SDN controllers.

Bryan explained that he thought ovn is merely a L3 on top of ovs. Bryan will start an email thread to look for clarification of ovn as SDN solution.

Vikram further explained that the plan is to support SFC by implementing networking-api in networking-ovn project.

Finally, Vikram introduced the project schedule, committers and contributors, and deliverables for Brahmaputra Release and C Release.

Uli indicated that we are trying to reduce the number of new projects. Can we add analysis of ovn4nfv v.s. ovs4nfv project?

Vikram indicayed that ovs4nfv project is for performance improvement, while ovn4nfv is to introduce new networking feature.

Vikram takes the action to analyze:
- ovn4nfv and ovsnfv
- ovn4nfv and VNFFG
- ovn4nfv and ONOSFW

We will continue to discuss at the next meeting.

Because of Thanksgiving Day holiday next week, this meeting is canceled on 11/26. Next meeting will be on 12/03.

Meeting adjourned.