Audience: internal or external
Goals: to identify where projects fit in the open source landscape, identify similarities and gaps of projects, in that landscape and look for dependencies and touchpoints between projects.
- Describe the functionality of each project
- Describe the interfaces
Tentative delivery date March-31/2020
1. Work group members and areas of expertise
Name | FD.IO | ONAP | OPNFV | ODL | Open Switch | SNAS | PNDA | Tungsten Fabric |
---|---|---|---|---|---|---|---|---|
Ranny Haiby(lead) | ++++ | + | ||||||
+ | + | + | ++++ | |||||
++++ | + | + | ||||||
+++ | + | |||||||
+ | + | + | + | |||||
++ | ++++ | |||||||
++++ | + | + | ||||||
++++ - Expert knowledge
+++ - Very good knowledge
++ - Good knowledge
+ - Some knowledge
<blank> - Heard about it, but not sure what it does exactly
2. Architecture diagram
External landscape:
Internal Architecture:
3. White paper outline
- Introduction
- Industry trends, open source in networking, etc.
- Reasoning for the need for LFN
- Goals of LFN
- LFN landscape
- Definition of the various layers and domains
- Mapping of projects to domains
- Brief project overview
For each <project> in <LFN> describe (goals, technologies, key features, etc.)
- Inter-relations and interfaces
- Inter dependencies
- Integration points
- Functional flows
- E2E use cases
- How do all (or some of) the projects work together to provide an E2E solution to a use case.