Order of priorities
- Field Trial + RC (functional tests with Field Trial participants)
- RI + RC (function tests within the RI lab environment)
- Additional RC testing (hardware validation, performance, etc.)
What is the Field Trial
- The first step towards CNTT Adoption
- Prove that the RC tests work at a basic level (functional testing)
- Work with key NVFi vendors (targeting Mirantis, Redhat)
How will the Field Trial work
- CNTT to document the process (pending PR at https://github.com/cntt-n/CNTT/tree/master/doc)
- For example...
- How will CNTT (OPNFV) operate
- What will the participants need to do
- What are the survey questions
- For example...
- Participants to setup their environments (or use community lab), then run the functional tests
- Participants to complete a survey list of questions (many answers will be optional, including the test results)
What is still needed for the Field Trial
- Completed CNTT process document at Github
- Agreement with NFVi vendors
- Finalize RI Cookbook
- requirements for running in private lab
- requirements for running in community lab
- RC Cookbook
- Test case mapping to RA (requirements) - RC Ch 3
- How to run the test cases - RC Ch 7 ?
- Plan for test results
- Display results in graphical format (consider who has access to view ?)
- Allow vendor to submit results for badging
When will the Field Trial run
- Late April - into May
- Originally intended to coincide with ONES
- Pending talks with NFVi vendors
What about the existing efforts in CNTT / OPNFV
- RI and RC efforts will continue to move forward in parallel
- RI - Focus on issues such as: Cookbook / Design / Lab setup and fixes
- RC - Continue enhancing test suites, getting test results to dashboard (Dovetail)
- People
- WSL-RI: Raja Jayachandran has been nominated
- James Gu (existing OPNFV-Airship proxy PTL)
- Other types of testing can be included in the future Badging process
Next steps
- Raja to connect with Fu Qiao (WSL RI + RC alignment)
- Raja to work through RI - Issues and PRs
- Raja and James will work together to clarify possible issues in community areas Airship, Openstack Helm, Treasuremap and others
- Work through section "What is still needed for the Field Trial"
- What resources are needed to help towards the Field Trial priority
Detailed Plan / Close Gaps
- Close gaps
- Alignment plan between Field Trial team, RI, RC, OPNFV
- Staffing needs
High Level Item | Tasks | Notes | Staffing needs | |
---|---|---|---|---|
CNTT | OPNFV | |||
| ||||
2. Agreement with NFVi vendors | ||||
3. Finalize RI Cookbook | ||||
a. requirements for running in private lab | ||||
b. requirements for running in community lab | ||||
4. RC Cookbook | ||||
a. Test case mapping to RA (requirements) - RC Ch 3 | ||||
b. How to run the test cases - RC Ch 7 ? | ||||
5. Plan for test results | ||||
a. Display results in graphical format (consider who has access to view ?) | ||||
b. Allow vendor to submit results for badging |
Additional Point
- Al - OPNFV has done this before, through badging process.
- Vendor feedback @ ONS 2018 - how to include performance, because their customers are asking for this.
- Also what about High Availability (HA).
- Security scenarios need proper attention.
- Rabi - CNTT has defined a single OSTK-based configuration, which helps limit the scenarios.
- The approach taken provides the framework in which additional testing can be added.
- WSL RC can help drive the right focus in the RC test plan.