1. End User Advisory Group (EUAG) Monthly Meeting
October 25, 2016

2. Antitrust Compliance Notice
OPNFV meetings involve participation by industry competitors, and it is the intention of OPNFV to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
Examples of types of actions that are prohibited at OPNFV meetings and in connection with OPNFV activities are described in the OPNFV Antitrust Policy. If you have questions about these matters, please contact your company counsel, or if you are a member of OPNFV, feel free to contact Lee Gesmer or Andrew Updegrove, of the firm of Gesmer Updegrove LLP, which provides legal counsel to OPNFV.
checklist
OPNFV Confidential

3. Agenda Antitrust Notice (1 minute)
Introductions & Round Robin (15 minutes)
Minutes Approval (1 minute)
EUAG Member Roster (1 minute)
OPNFV Release Process (20 minutes)
Polestar Framework Review (10 minutes)
C&C Readout Summary (5 minutes)
Pain Points Discussion
VNF Onboarding (5 minutes)
NS instantiation with VM placement optimization (17 minutes)
Invocation/Deletion of Services on OPNFV Reference Platform (17 minutes)
Versioning APIs and consistency across releases (17 minutes)
Meeting Schedule (5 minutes)
Any Other Business (5 minutes)
OPNFV/OpenDaylight Reception Reminder (1 minute)
OPNFV Confidential

4. Introductions & Round Robin: Open Source & OPNFV
We’d like to hear from each EUAG Member on the following:
Characterize your organization is using/not using OPNFV (e.g. observing, PoCs, testing, etc.)
What is the biggest misunderstanding of OPNFV in your organization?
OPNFV Confidential

5. Minutes Approval
Minutes from the last EUAG Meeting were posted to the EUAG Wiki Page here:
+Group
Comments/objections/additions to the minutes?
OPNFV Confidential

6. EUAG Member Roster Member Company Bryan Sullivan AT&T Jeff Finkelstein
Cox
Jong Han Park
SK Telecom
Steven Wright
Herbert Damker
Deutsche Telecom
Sungho Jo
Toby Ford
Klaus Martiny
Serge Manning
Sprint
Vijay Kumaraguruthasan
Bell Canada
Gerald Kunzmann*
DOCOMO Euro-Labs
Samer Salah Mahoud
STC (advisor)
Milind Bhagwat
British Telecom
Carlos Matos
Fidelity
Karim Rabie*
Don Clarke
CableLabs
Hajime Miyamoto
KDDI Corp.
Cecilia Corbi
Telecom Italia
Randy Levensalor
Kenichi Ogaki
Johan Gustawsson
Telia
Tetsuya Nakamura
Masanori Miyazawa
KDDI Labs
Diego Lopez
Telefonica
Lingli Deng
China Mobile
Uzair Firoze
Liberty Global
David Amzallag
Vodafone
Chuan Jia
China Unicom
Ashiq Khan*
NTT DOCOMO
Kodi Atuchukwu
Junjie Tong
Kazuaki Obana*
Guy Meador
Morgan Richomme
Orange
OPNFV Confidential
*New since the last call

7. Release Process Overview
David McBride
Sr. Release Manager, OPNFV

8. Projects
OPNFV is made up of many projects:
Features
Test Frameworks
Requirements Development
Documentation
For example, OPNFV Danube (current release cycle) includes 40 projects
Projects must make a proposal to the TSC, which then votes on whether to include the project
Once approved by the TSC, projects must declare their intent to participate in each release
OPNFV Confidential

9. Scenarios
Feature projects must be deployed in order to be used and tested. Scenarios are the vehicle for this.
A scenario includes:
An installer (i.e. Apex, Fuel, Compass, Joid, or Daisy)
A set of upstream components (e.g. OpenStack, Open Daylight, ONOS, etc.)
A configuration
Scenarios must be defined as part of project release planning
Feature project teams must associate with one or more scenarios
In order to minimize scenario proliferation, project teams are encouraged to partner with existing scenarios, rather than create new scenarios
OPNFV Confidential

10. Scenarios Each scenario includes a scenario owner:
Ensure that scenario is enabled in OPNFV CI
Coordinate with associated installer and project teams to diagnose and resolve build, deployment, and test issues
Ensure that scenario documentation is completed
OPNFV Confidential

11. Danube Release Schedule
OPNFV Confidential

12. Polestar Framework Review
Slides TBD
OPNFV Confidential

13. C&C Readout Summary
Compliance/verification program (CVP) describes plan to test/measure OPNFV Value proposition for service providers, vendors, and OPNFV
CVP is NOT certification
CVP is compliance testing instead of certification; CVP tests functionalities instead of performance. Long term this may change.
Tied to releases (Danube, E-release, etc.)
Testing hardware & software platforms
Primarily self-testing but 3rd party labs allowed
Two-proposed levels (initial): OPNFV-Ready & OPNFV-Based
Seeking OPNFV Board approval this week, to be launched early 2017
OPNFV Confidential

14. Paint Points Discussion
Guidance on the prioritization, sequencing, and precise use stories and scenario(s) of user pain points
As of (10/28/16): 26 pain points listed
Based on the last call and recent wiki additions, current pain points to discuss:
VNF Onboarding
NS instantiation with VM placement optimization
Invocation/Deletion of Services on OPNFV Reference Platform
Versioning APIs and Consistency Across Releases
Fine-grained Security Policy (if time)
Additional thoughts/input?
OPNFV Confidential

15. Pain Point: VNF Onboarding
VNF onboarding feedback from the last call
Level of detail on wiki likely sufficient for now, but tech community feedback needed
Initial focus should be on VNF package
Future discussions:
Service onboarding
VNF deployment constraints and VNF options
VNF onboarding discussion continues on MANO working group & models project:
EUAG Members welcome to follow/contribute discussions there
OPNFV Confidential

16. Paint Point: NS Instantiation with VM Placement Optimization
NFVIaaS type service Invocation/Deletion
One of the distinctions between NFV and cloud computing is the distributed and localized nature of the NFVI. These services may be invoked in a location independent manner, constrained within specific boundaries or targeted to specific physical locations. since the NFVIaaS service user  may be different entity to the NFVIaaS service operator, this implies a need for authentication as well as validation of underlying resource availability. 
VNPaaS type Service Invocation/Deletion
VNFaaS type Service Invocation/Deletion
Does is adequately cover end-to-service instantiation/invocation?
Additional thoughts/input?
OPNFV Confidential

17. Paint Point: Invocation/Deletion of Services on OPNFV Reference Platform
Linked to multi sites and/or cloud native application
There are already some solutions but not lots of clear guidelines/rules
Placement within one VIM: Some solutions exist to take into account affinity/anti-affinity rules, EPA requirements
Multi-site deployment:
Geography of data centers
Network topologies within and between data centers
Latency requirements from access networks and other resources
Capacities needed/allocated at each site
Vendor placements rules if any
Redundancy requirements (e.g., N:1)
Recovery procedures in case of failure
Should be automated, e.g. create operator deployment “policy” or rules to be input to the Orchestration system
Additional thoughts/input?
OPNFV Confidential

18. Paint Point: Versioning APIs and Consistency Across Releases
Combining “Versioning” with “Skip release(s) when upgrading a (live) system”
Linked to CI/CD + API backwards compatibility, upgrade from version A to version B must not require manual operations especially for critical components. Moreover it shall be possible to skip intermediate version and upgrade only stable version not necessarily from version N to N+1
To upgrade OpenStack a huge amount of integration efforts and testing is required
OpenStack releases on a 6-month cadence and users may want to choose a yearly or even bi-yearly upgrade of my systems. Ideally, such system upgrades shall be done “live”, i.e. without the need shut down everything running on the older release.
We may also want to consider the option of live/rolling upgrades for OPNFV
Additional thoughts/input?
OPNFV Confidential

19. Paint Point: Fine-grained Security Policy
Discuss broadly if time allows
OPNFV Confidential

20. Meeting Schedule Proposed Schedule:
November EUAG Meeting: Virtual (Tues, Nov 16)
Poll sent to determine best time
December EUAG Meeting: Virtual (Wed, Dec 7)
2017 dates (January – June) to be sent soon
OPNFV Confidential

21. Any Other Business
OPNFV Confidential

22. OPNFV / OpenDaylight Reception
Come join the OPNFV and OpenDaylight communities for drinks and a sampling of local tapas on the beach!
When: October 25 - Tonight! 19: :00
Where: Boo Restaurant and Beach Club - Terrace, Espigó de Bac de Roda, 1. Platja de la Nova Mar Bella (1.7 km from OpenStack Conference Center)
OPNFV Confidential

23. Thank You!