Baldy - CNTT Technology Actions
- speedwyre
FEEDBACK INSTRUCTIONS:
The below list published as of 1/23/2020 as a Straw Man. Work Stream and or owning Leads are requested to update their high-level actions as per the following method.
In the far left column:
Item is targeted for Baldy Release indicate as "Baldy".
Item is targeted for future release, indicate as "Backlog".
Item is not related to a release, indicate as "Other".
Item is not targeted for any release/future release/other, indicate as "Cancel".
Add and or rearrange items in your works stream as is appropriate.
In all other columns
Edit, modify as appropriate for activities listed
Try to keep it high-level (e.g. Agile 'story' level or higher)
7 | Reference Model | Key Stakeholders | Work Stream | Lead | Target Date | Status | Notes |
|---|---|---|---|---|---|---|---|
Finalize on a Exception Criteria / List / Process | CNTT, OPNFV, OVP | ||||||
Mechanism to incorporate exceptions into RAx | CNTT, OPNFV, OVP | ||||||
8 | Reference Architecture 1 | Key Stakeholders | Work Stream | Lead | Target Date | Status | Notes |
Reach consensus on use of NFVI Exposure utilities (mentioned by Sukdev) | CNTT, OPNFV, OVP | ||||||
Finalize on architectural related Security Principles | |||||||
9 | Reference Architecture 2 | Key Stakeholders | Work Stream | Lead | Target Date | Status | Notes |
Collaborate w/CNCF to address gaps in RA2 | CNTT, CNCF TUG, OVP 2.0, OPNFV | ||||||
CNIs (Containerized Network Interfaces) for Telco's (See Gergely) | CNTT, CNCF TUG, OVP 2.0, OPNFV | ||||||
10 | Reference Implementation 1 | Key Stakeholders | Work Stream | Lead | Target Date | Status | Notes |
Resolve CI/CD software deployment blockers | CNTT, OPNFV | ||||||
Demonstrate repeatable deployment and validations using Intel labs | CNTT, OPNFV | ||||||
Establish Standard Descriptor File format & process | CNTT, OPNFV | ||||||
Refine Cookbook with automation tooling framework (info) | CNTT, OPNFV | ||||||
Implement Hardware Validation Utility | CNTT, OPNFV | ||||||
Implement Manifest Validation Utility | CNTT, OPNFV | ||||||
11 | Reference Certification 1 | Key Stakeholders | Work Stream | Lead | Target Date | Status | Notes |
Confirm comfort levels with FuncTest, identify and fill gaps as needed | CNTT, OPNFV, OVP | Document and socialize full approach | |||||
Define MVP certification/badging use cases for Friendly Trials | CNTT, OPNFV, OVP | Goal is deploy with minimal level of diversity (test suite run against NFVI-A, NFVI-B, VNF-A, VNF-B, VNF-x, etc. Mix and matched scope. | |||||
Align OVP and CVC teams on badging / certification process changes | CNTT, OPNFV, OVP | ||||||
Enhance Automation Suite, closing gaps in validation | CNTT, OPNFV, OVP | ||||||
Rollout Strategy | CNTT, OPNFV, OVP | Clear roles and responsibilities. | |||||
12 | Reference Implementation 2 | Key Stakeholders | Work Stream | Lead | Target Date | Status | Notes |
Create New Workstream | CNTT, CNCF TUG, OVP 2.0, OPNFV | (Changed by Rabi) | |||||
13 | Reference Certification 2 | Key Stakeholders | Work Stream | Lead | Target Date | Status | Notes |
Create New Workstream | CNTT, CNCF TUG, OVP 2.0, OPNFV | (Changed by Rabi) | |||||