Wiki

• Date and Time: 6:00am PDT / UTC 13:00, Thursday June 25, 2015
• Convener: Bin Hu (AT&T)
• Participants:
  • Al Morton (AT&T)
  • Ana Cunha (Ericsson)
  • Eric Multanen (Intel)
  • Fatih Degirmenci (Ericsson)
  • Gerald Kunzmann (DoCoMo)
  • Ildiko Vancsa (Ericsson)
  • Jonas Bjurel (Ericsson)
  • Jose Pekkarinen
  • Kevin Luehrs (Cable Labs)
  • Larry Lamers (VMWare)
  • Mark D Gray (Intel)
  • Michael Bugenhagen (Century Link)
  • Michael Lynch (Intel)
  • Prakash Ramchandran (Huawei)
  • Praveen Kumar
  • Rajeev Seth (Sonus Networks)
  • Raymond Nugent(Huawei)
  • Stuart Mackie(Juniper)
  • Tim Rozet (RedHat)
  • Ulrich Kleber(Huawei)
  • Yuri Yuan (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
    • Fuel OPNFV

Jonas (Ericsson) introduced this project, which intends to continue the Fuel work originally in BGS.

Uli (Huawei) asked that because most of requirement of installers in Release 2 will be defined in Genesis project, what exactly will Fuel project do? Jonas replied that mostly it will be rebasing and refactoring of build system from Arno.

Uli (Huawei) further asked that Arno release defines the fixed installation on 5 nodes, will Fuel project consider to cover the flexibility of different number of nodes? Or should the flexibility be covered by other projects? Jonas answered that the flexibility is already available in Fuel.

Uli (Huawei) then concerned whether Fuel project has enough / sufficient work to accomplish as a separate project. Jonas said that there will be substantial work to do in Fuel.

The discussion moved on what should be strategic direction in terms of org structure of installer projects - separate projects in OPNFV or sub-projects absorbed by Genesis.

The consensus is that:
- The technical part of Fuel proposal is ready to go
- It needs TSC's discussion and decision on the strategic direction of how to best organize those existing and new installer projects.

• New Collaborative Development project proposals
  • LAR-E Framework

Kevin (Cable Labs) introduced this project proposal.

Stuart (Juniper) asked that because the proposal seems to propose ODL NBI, why is it proposed as an OPNFV project instead of an ODL project? Kevin replied that some work is out of scope of ODL, for example service manager is an orchestration function.

Through the discussion, Kevin agreed to make the following changes:
- Move ODL from Virtual Network to VIM on Figure 2
- Address how to collaborate with other OPNFV projects such as Movie which also focus on NBI
- Address how to integrate with ONF
- Address how to handle other SDN Controllers when ODL is not chosen in the stack

• Admin

Because next week will be the holiday week of July 4th Independence Day in USA, many persons will take vacation. And it is also summer vacation time in Europe. It is anticipated that only very few persons may attend the technical discussion next week. In order to make technical discussion more productive, Bin proposed to cancel the meeting next week on July 2nd.

All agreed to this proposal and meeting on July 2nd will be canceled. Next regular meeting will be on July 9th.

Meeting adjourned.