* Alternating Wednesdays at 9:00 pm US Pacific time 5:00 UTC Thursday (when US Standard Time) / 6:00 UTC Thursday (when US Daylight Saving Time)
Find your local time.

* <Add meeting day/time for alternating week>

* GoToMeeting https://global.gotomeeting.com/join/752333285

* IRC irc.freenode.net

• <IRC channel TBA>
• http://webchat.freenode.net/?channels=opnfv-meeting or use your favorite IRC client

* 5 minute on Scope to check for additions/deletions
* Review of Residential Services topic (MK)
* Time permitting

• Review of Service Use Cases (Andrew S)
• Dividing up the agreed topics so that work can begin

<TBA>

* Review of the Scope
* Review of the Connectivity Services LSO activity in ODL and OPNFV

Project description:
* The NFV movement is largely focused gaining the efficiencies of large data centre compute infrastructure. This is sensible, however to paraphrase the old switching/routing saying … centralize what you can, distribute what you must. Some applications naturally belong at the edge: WAN Acceleration, Content Cacheing, and depending on your philosophy, Firewalling all fall into that category. Other more specialized test applications also need to be at the edge to exercise the portions of the network under test. Similarly many business applications are most efficiently delivered at the edge.
* The purpose of this Requirements Project is to articulate the capabilities and behaviours needed in Edge NFV platforms, and how they interact with centralized NFVI and MANO components of NFV solutions
* MK propose to strike/clarify the use of the word “centralized” since large eNFV scenarios likely can’t be handled by a single NFVI instance
* Appropriate Tunneling for User Traffic across WAN (Ethernet, IP/MPLS) links
* Appropriate Tunneling for Management Traffic across WAN links
* Including reachability requirements to the compute platform
* Extending Multi-DC management to address many small "DC" locations (Jesse interested … "micro DC running on the edge")
* Monitoring Capabilities required for a remote Compute Node
* Squaring Bare Metal with remote survivability and whether IaaS is more appropriate for remote locations
* Include any architecture diagrams or specifications, reference to OPNFV requirements list.
* Jesse: IaaS needs to support VMs and Containers co-existing (Liberty is all about containers) … Google Container Service, AWS Containers … Containers will reside in the VMs
* ML: Landslide product working on Edge … just letting us all know
* MK: is interested in home … so scaling to millions … smaller number of VNFs, larger number of CNs … perhaps service chaining gets simpler
* MK: Cablelabs working with MEF. Very focused at L2 setting up interfaces and formats (whereas his interface) … MK can give overview of this.
* ML: Curious about security aspect across the WAN … how does one secure inter-VNF communication between VNFs in the chain. MK: Authentication of remote nodes to the controller … MK can share what they did at Cablelabs
* Kevin Luehrs Data Plane Optimization (TBD if eNFV needs to specifically address this, or pick up work from other groups … DPACC?)
* We discussed MANO and MK explained that OPNFV was likely to expand scope to address this.
* John pointed out that we need to Define some use cases …

Content
* Kevin shared description of OPNFV Connectivity Services LSO (LSOAPI) project and OpenDaylight UNI Manager project

• MEF ELINE service description
• Defined YANG model to feed into ODL
• Instances were OVS running in Raspberry Pi … and talk to it using OVSDB
• Service model is to connect UNI’s with GRE tunnel
• Connectivity Services LSO is the aspect of this in OPNFV
• Next steps is to migrate to MEF’s latest service model
• Focused on the “SDN aspect of this problem”

* <add agenda here>

* <add minutes here>

Back to ENFV main project page