• B: 1.x Various: May need to be rationalized w/ new Tech Steering document

• A: 1.9 Roadmap: This section needs perpetual maintenance (strongly consider moving the roadmap out of the RM, altogether)

• A: RA Compliance/traceability methodology 

• A: 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)

• B: 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)
• A: Align and execute on Prague proposal to park the Compute Intensive flavor, and supplement it by removing "over-subscription?" from the Basic flavour
• C: Flesh out quantitative details about supported workloads. (nice to have)

• A: Needs tighter coupling w/ Container paradigm (i.e. decoupling from VM-based VNF)
  • flavours for example might not be applicable to containers(CPU and memory, disc we want to find a way for containers) - possibly Ch04
  • harmonisation of template in Model.
• C: Needs a general review. Given the experience we’ve gained, can be made more succinct and more usable by a VNF developer
• C: Need to clearly explain slicing (and contrast to Tenant) from CNTT perspective
• B: 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
• B: Data Model - Create actual schema(s) and data model(s) for CNTT-specific information (potentially in an appendix)
• A: Shared w/ RM-Ch4: Need to define virtual networking strategy and related attributes/parameters (workload level)

• A: Integrate more Container paradigms/support
• A: Flesh out Generic Fabric Model (Fabric, Underlay and Overlay level (i.e. Infra, not workload)
• C: Research and enhance storage performance extensions using performance per unit of storage model (i.e. IOPs/GB)
• A) MVP: Hardware Profiles and Performance.
  • Objectives/
• • 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.)
• A: Clarify diagrams and language around T-Shirts, Flavors and IT relationships
• A: 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
• A: 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.

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

• B: Flesh out initial Enabler Services

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

• A: Cleanup to Ch08
  • 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.)

• C: Create Generic Installer Model

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

A: RA-1 cleanup (ch content complete 80%, issue closure)

Update OpenStack version based on newer version. (let continue discussion TSC call)

• 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).

Update RA-1 Ch02: Requirements

Align RM and RA-1 Requirements.

Review Networking Section and suggest Improvements

Ch03: 

Ch04: 

Create content for RA-1 Ch06: Security: Create security requirements list

Create updated ToC and Content for RA-1 Ch07: Operations and Life Cycle Management

• 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)

MVP: Define Conformance

MVP: Replace Certification w/ Conformance

1.7 Results Collation & Presentation - write section on where/how results will be normalized, collated, and presented

1.8 Governance - expand to include LCM, define partnerships and expectations from these partners as to what info or support is exchanged, or provided

MVP: Replace Certification w/ Conformance

2.6 Entry & Exit Criteria - review for completeness, and reach consensus from the community that criteria satisfies objectives for CNTT (as intake to testing, and delivery to telcos)

2.7.3.3 Test Results - community review and consensus needed on collation and portal requirements; need to identify and document portal, or dashboard, used for results presentation

2.7.4 Badging - need alignment with OVP / CVC on badging steps and expectations; need alignment to add Xtesting as an alternative to Dovetail 

MVP: Replace Certification w/ Conformance

3.5 Software & Hardware Reference - content needs to be written to identify requirements for testing Software Configuration/Profiles, and Hardware Configuration/Profiles.  

3.6 Options & Extensions - content needs to be written to create requirements for testing/evaluating Options and Extensions available and configured.  

3.8.2 Resiliency Measurements - need to be written

3.9 Test Cases - remove (move) to Ch 4