• 1.x Various: May need to be rationalized w/ new Tech Steering document
• 1.9 Roadmap: This section needs perpetual maintenance (strongly consider moving the roadmap out of the RM, altogether)
• MVP: RA Compliance/traceability matrices and methodology
• MVP: Still needs a crisp executive summary identifying the problem statement, and the two key methodologies employed to address them (VNF Abstraction and a common NFVI)

• Needs a community aligned list of workloads the platform is intended to support and their priority, which can then be used as a basis for resource allocation and for weighting “suggestions” (notably “The public cloud does it this way, so we should too.”; understood, but we need an objective basis. Right now, it becomes a subjective debate)
• MVP: Align and execute on Prague proposal to suspend the Compute Intensive flavor, and supplement it by removing over-subscription from the Basic flavour
• Flesh out quantitative details about supported workloads

• Needs tighter coupling w/ Container paradigm (i.e. decoupling from VM-based VNF)
• Needs a general review. Given the experience we’ve gained, can be made more succinct and more usable by a VNF developer
• Need to clearly explain slicing (and contrast to Tenant) from CNTT perspective
• Template attributes should be vetted w/ underlying capabilities, rationalized for duplication (i.e. CNTT value add, vs. what’s already in HEAT) and expanded to integrate Container paradigms
• Data Model - Create actual schema(s) and data model(s) for CNTT-specific information (potentially in an appendix)
• Shared w/ RM-Ch4: Need to define virtual networking strategy and related attributes/parameters (workload level)

• MVP: Integrate more Container paradigms/support
• Flesh out Generic Fabric Model (Fabric, Underlay and Overlay level (i.e. Infra, not workload)
• Research and enhance storage performance extensions using performance per unit of storage model (i.e. IOPs/GB)
• MVP: Hardware Profiles and Performance
  • Objectives/Requirements
  • Guidelines
  • What level of granularity
  • Validation/Auditing
  • Proposals or white paper on how we plan to achieve deterministic performance from the reference model w/o having to specify hardware to down to a very granular level (e.g. w/o SKUs, clock speeds, etc.)
• MVP: Clarify diagrams and language around T-Shirts, Flavors and IT relationships
• Policies for Non-Conforming Technologies // assumes supporting frameworks are ratified
  • SRIOV policy
  • SmartNIC policy*
  • Live Migration policy
  • *includes Tomas’ concept of driving SmartNIC industry to standard, cloud-friendly ABI
• Shared w/ RM-Ch3: Need to define virtual networking strategy and related attributes/parameters (workload level).
• 4.2.2: need to consider aggregate network bandwidth instead of per Interface bandwidth.

• Integrate cloud native concepts w/ sw profile (i.e. how abstraction and workload portability is maintained)
• Update s/w profile, pending suspension of Compute Intensive IT
• MVP: Rationalize s/w profile to IT mapping after removal of third IT
• MVP: Audit chapter alignment w/ RM-Ch4
• Incorporate VNF Profile Generations/Evolution (once ratified), designing and describing linkage/relationship to h/w profiles

• MVP: Flesh out initial Enabler Services

• Worthy of review by SMEs for suggestions of areas to incorporate and/or refine

• Generic  qualification model (i.e. NFVI and VNF)
  • Badging types (requirements in RC)
  • Methodology to support N-3 VNF Rls Profiles
• Overview of badging methodology
  • Base-lining testbed before VNF qualification
  • VNF testing without prior knowledge
  • Plumbing testbed for supplier testing of VNF functionality, after VNF badging.
• Overview of novel VNF-related concepts
  • Reference VNF (aka Golden VNF)
  • NFVI characterization, and correction coefficients for normalizing performance
• What is out of scope for CNTT (e.g., VNF functional testing, performance, scalability, HA, etc.)

• Create Generic Installer Model

• Needs a strategy/purpose review and new commitment from original or new contributors to continue on it

• Update OpenStack version based on newer version.

• Remove 1.6 as this will be moved into Overall Roadmap.
• Remove CI (as this has been decided to be parked for a bit and picked up later).

• Start filling Traceability Column.

• Remove 3.6 as Traceability is in Ch02.

• Remove 4.7 as Traceability is in Ch02

• Drive initial content.

• Drive initial content.

• Confirm that the CI/CD Scripting works (Natural bi-product of lab install success)

• RI supports RC
• Define pass, compliance, verification, validation

• 1.3 scope: clarify scope as per Prague discussion.
• 1.4 remove Roadmap (this will be /should be covered in the overall CNTT Roadmap)

• 2.2 Remove as it is not necessary.
• 2.3 add in a table with reference numbers.
•  2.4 This should be removed or moved to Chapter 4 (Lab requirement) and improve diagram as it is low quality. Do we need an example section?

• 3.1 clarify the intention of the chapter (to be able to create a PDF/IDF from the content of the chapter)
• It will be better to simplify the presentation of the content here (metadata driven approach will be recommended)
• To make it simple to create PDF/IDF from the chapter.
• 3.4 it mixes requirement, with architecture with state. (need to clean up and remove any duplications). Remove any reference to functest or certification or test cases, this should be all about the state of NFVI.

• Need a Topology Diagram.
• Need Networking/Switching Requirements.

• 5.2 Add more installer general requirement (e.g. the need for it to be opensource, the result of it needs to be opensource).
• 5.3: needs to agree if this is something we need to have in CNTT. (ongoing discussion in OPNFV about it)

Create a Cookbook for Labs (how to access labs, types of labs available, etc)

• A lot of clean-ups needed.
• Not mix labs with installation (Chapter 6 deals with labs)
• 7.2, 7.3, 7.4 will need to move to Chapter 6 since they are lab related.
• 7.6, 7.7 (clarify difference between deployment validation and development validation).
• This should be sanity check and not extensive testing.

Need some initial content (are there no gaps? )

RC-1 Finalize TC Req Mapping & Close TC Gaps

• Performance is not MVP for April

RC-1 test suite is created

• Identify and Close Gaps in TCs
• Performance is not MVP for April
• Supporting OvS-DPDK in RI-1
• Test suite details

• Define pass, compliance, verification, validation

Restructure to remove confusion (https://github.com/cntt-n/CNTT/pull/961)