FEEDBACK INSTRUCTIONS:
The below list published as of 1/23/2020 as a Straw Man. This list requires clarification of WS & allocation of resource assignments. Once Work Stream and or owning Leads are assigned, they 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". (See example in 2nd row below)
- Item is targeted for future release, indicate as "Future".
- Item is not targeted for any release/future release, 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
| 14 | OVP (VNFs) | Key Stakeholders | Work Stream (Realigned) | Lead | Target Date | Status | Notes |
|---|
| Rethink / Revise to more telco acceptable tests | CNTT, OVP, OPNFV |
|
|
|
|
|
| NFVI Badging Strategy and Design | CNTT, OVP, OPNFV |
|
|
|
|
|
| NFVI Badging Rollout | CNTT, OVP, OPNFV |
|
|
|
|
|
| VNF Badging Strategy and Design | CNTT, OVP, OPNFV |
|
|
|
|
|
| VNF Badging Rollout | CNTT, OVP, OPNFV |
|
|
|
|
|
|
|
|
|
|
|
|
|
| 15 | OVP 2.0 (VNFs change to CNFs) | Key Stakeholders | Work Stream (Realigned) | Lead | Target Date | Status | Notes |
|---|
| Define Mission and Scope more tightly | CNTT, CNCF TUG, and regulatory - 3GPP |
|
|
|
|
|
| Regroup and refine on objectives | CNTT, CNCF TUG, and regulatory - 3GPP |
|
|
|
|
|
| Review draft | CNTT, CNCF TUG, and regulatory - 3GPP |
|
|
|
|
|
| Immediate blueprints, test plan draft | CNTT, CNCF TUG, and regulatory - 3GPP |
|
|
|
|
|
| Cloud-Native Badging Strategy | CNTT, CNCF TUG, and regulatory - 3GPP |
|
|
|
|
|
|
|
|
|
|
|
|
|
| 16 | OPNFV 2.0 (Related) | Key Stakeholders | Work Stream (Realigned) | Lead | Target Date | Status | Notes |
|---|
| Project vetting | CNTT, OPNFV TSC |
|
|
|
| make sure the projects are relevant |
| What is the TSC role and purpose in life? | CNTT, OPNFV TSC |
|
|
|
|
|
| Solicit SPC help in re-thinking mission/vision/strategy | CNTT, OPNFV TSC |
|
|
|
|
|
| Re-Organize TSC for action | CNTT, OPNFV TSC |
|
|
|
| To manage transformational requests |
| Plan CNTT/OPNFV intereactions | CNTT, OPNFV TSC |
|
|
|
| TSC attendance on CNTT calls |
| Integrated roadmap process to define/describe long-term directions | CNTT, OPNFV TSC |
|
|
|
|
|
| Define a detailed/specific set of metrics/conditions to be ready for CNTT | CNTT, OPNFV TSC |
|
|
|
|
|
|
|
|
|
|
|
|
|
| 17 | Friendly Trials - Alpha Launch Planning - NFVIs |
|
|
|
|
|
|
|---|
| 17.1 | Onboarding/Adoption(Badging) Journey | Key Stakeholders | Work Stream (Realigned) | Lead | Target Date | Status | Notes |
|---|
| Outline/define of what is needed in Friendly trial from RC1/OVP | CNTT, OPNFV, OVP, Trial Participants |
|
| Feb |
|
|
| Define scope & requirements | CNTT, OPNFV, OVP, Trial Participants |
|
| Feb |
| Clear roles and responsibilities. |
| Define end-to-end badging 'user' journey MVP | CNTT, OPNFV, OVP, Trial Participants |
|
| Feb |
|
|
| Design launch plan | CNTT, OPNFV, OVP, Trial Participants |
|
| Feb |
|
|
| Initial test-badging aligned with CNTT/OVP expectations | CNTT, OPNFV, OVP, Trial Participants |
|
| Mar |
|
|
| Provide lab and test cases to participants | CNTT, OPNFV, OVP, Trial Participants |
|
| Mar |
18
|
|
|
|
|
|
|
|
|
|
| 17.2 | Infrastructure / Lab Support ("Back Office") | Key Stakeholders | Work Stream (Realigned) | Lead | Target Date | Status | Notes |
|---|
| Secure lab participation/capacity/diversity for Friendly trials' | CNTT, OPNFV, OVP, Labs, Trial Participants |
|
| Feb |
|
|
| Define MVP support model / structure for trials | CNTT, OPNFV, OVP, Labs, Trial Participants |
|
| Mar |
19
|
|
|
|
|
|
|
|
|
|
| 17.3 | Trial Participation | Key Stakeholders | Work Stream (Realigned) | Lead | Target Date | Status | Notes |
|---|
| Confirm trial participants and SPOCs | CNTT, OPNFV, OVP, Trial Participants |
|
| Jan |
| RedHat, Ericcson, Nokia, Cononical, VMWare |
| Define expectections, what's needed, roles & responsibilities | CNTT, OPNFV, OVP, Trial Participants |
|
| Feb |
|
|
| Kickoff Meeting / Preparations | CNTT, OPNFV, OVP, Trial Participants |
|
| Feb |
20
|
|
|
|
|
|
|
|
|
|
| 17.4 | Value Demonstration / Activities | Key Stakeholders | Work Stream (Realigned) | Lead | Target Date | Status | Notes |
|---|
| Define consistencies needed | CNTT, OPNFV, OVP, Trial Participants |
|
| Feb |
| Effort/how long to turn up / turn down? # of TC failures reported, etc. |
| Cookbook validation (usage, steps, etc.) | CNTT, OPNFV, OVP, Trial Participants |
|
| Mar |
| Goal is reduce friction in lab & test onboarding process |
| Capture defect reduction benchmarks / define targets | CNTT, OPNFV, OVP, Trial Participants |
|
| Mar |
| How many NFVI/VVNF initial deploy defects before CNTT? how many defects after? |
| Prepare for and perform analysis during trials | CNTT, OPNFV, OVP, Trial Participants |
|
| Apr |
| e.g. recurrance of defects, debugging, engineering and design impacts, duplicative defects, correlative. |
| Capture and analyze trial feedback | CNTT, OPNFV, OVP, Trial Participants |
|
| May |
|
|
| Quantify results / benefits / opptys for improvement | CNTT, OPNFV, OVP, Trial Participants |
|
| May |
21
|
|
|
|
|
|
|
|
|
|
| 18 | Beta Launch Planning - VNFs |
|
|
|
|
|
|
|---|
| 18.1 | Trial Participation | Key Stakeholders | Work Stream (Realigned) | Lead | Target Date | Status | Notes |
|---|
| Recruit and Confirm trial participants and SPOCs | CNTT, OPNFV, OVP, Trial Participants |
|
| Jan |
|
|
| Define expectations, what's needed, roles & responsibilities | CNTT, OPNFV, OVP, Trial Participants |
|
| Feb |
|
|
| Kickoff Meeting / Preparations | CNTT, OPNFV, OVP, Trial Participants |
|
| Mar |
|
|