...
- Generic Fabric Model (GFM)
- [RM] Networking Strategy (Issue #960)
- [RM] Long Term requirements for SDN, Fabric and Networking #1037
- The following is proposed for Baldy MVP
- Executive Summary
- CNTT approach to the fabric // i.e. define for flexibility in ultimate implementation
- Initial Objectives // i.e. what we want the GFM to achieve for CNTT (and why) Ex.:
- The implementation of Networking inside the HW Layer should not be visible to the VNF/CNF and should preferably not even be visible to the IaaS/CaaS
- Provide L3 tenant networks, GWs, SDS, etc.
- CLEANLY decouple interface/reference points between CNTT constituencies
- Provide compatibility at demarcation/reference points
- any RA couples to RM
- appropriate RI couples to RA
- Operator can create or procure a compatible fabric, etc.
- Provide a catalog of APIs, and their respective domains, capabilities and intent, to facilitate ease of integration w/ a wide selection of fabric implementations
- Provide ability for any number of Operator-specific fabrics to power an RA/RI/VI
- Enables RC's ability to realize their deliverables
- Clearly documents responsibilities of each CNTT constituency
- Your ideas here!
- Provide enough mechanics for contributors to create coherent requirements
- What are the buckets // Tech, RM, RAx, RIx, etc.
- Examples of what goes in each bucket // Exec Summary & approach (Tech); generic/high-level requirements (RM), detailed requirements (RA), Sample imp to support RC (RI), etc.
- Your ideas here!
- Executive Summary
...