Topic Leader(s)
Topic Description
75m, Scot Steele
Topic Overview
Deep Dive: Interoperability Challenges
- Part 4: CNF Interoperability Challenges between workload/platform and orchestrator/workload
- CNI – is this the only answer?
- Other networking frameworks (eg., Istio, Envoy)?
- Networking abstraction – how do we push this past the goal line, publish, and test?
- Data Plane
- If performance tuning is a source of interop issues, how do we address these?
- Are data plane issues as opaque to workloads as claimed (should we do a survey, or testing experiment to have non-anecdotal data)?
Slides & Recording
No slides
Minutes
what does it take for the function to interoperate with the platform?
CNI in it's current form is not the answer
Platforms should support an option to allow for other networking interfaces
Are there to many solutions?
Is there a DeFacto standard? CNI is but it doesn't support all of the needed functions
Kubernetes - V4/V6
Some plugins have addressed (e.g. Multus)
Multi pod interfaces where all interfaces are equal
Would a project focused on the issue (ref: Doctor from OPNFV) If so it would likely be under Anuket
Multi-homed requirements needed for Telco
Victor Morales - Samsung
electrocucaracha/gw-tester: GW Tester demo (github.com)
Work is organized by use cases
Nodus: https://github.com/akraino-edge-stack/icn-nodus
Can it support needed?
Review of Doctor project on collaboration -
Action Items
- Discussion on Cloud Networking CNI feature requirements
- Create a new project in Anuket to resolve the issue? Ask Victor Morales to participate.
- Evangelize the Mission statement (intervention?)
- Bob Monkman - potential of Intel supporting
- Anuket to discuss a "task force" - potentially based on the Doctor Project
- Scot Steele to review Dr. project to look at collaboration