Wiki

• Proposed name for the project: Platform tooling
• Proposed name for the repository: repo-name
• Project Categories: (Documentation, Requirements, Integration & Testing, Collaborative Development)

• High level description of test bed tooling and infrastructure project. We are to support these goals:

1. provide a documented baseline using release candidates of opnfv hw/sw ingredients
2. release testing of OPNFV's official releases
3. provide a "sandbox" for developer testing

• Include any architecture diagrams or specifications

1. The first diagram shows a high level working model for release testing and how this project may interact with other projects

• Describe the problem being solved by project

1. support both micro/macro level testing, virtual infrastructure level or VNFC or VNF level testing
2. can host multi-origin/multi-vendor VNFs, i.e. compositions of vnfc's
3. support regression, functional, and performance/benchmark testing
4. covers both hw and sw components

The test bed tooling functionality will cover:

1. Access tools: ID/authentication
2. Access tools: Web access
3. Access tools: Console access
4. Access tools: Reservation / multi-user/tenant
5. On-boarding of vnf/vnfc tools
6. Test automation tools
7. Diagnostic, logging, monitoring tools
8. Test load generators, benchmark tools: sw, hw
9. Test VNFs, target or auxiliary
10. inter-testbed connectivity emulation, if needed
11. stand-alone nfvc connectivity emulation, if needed
12. documentation, api reference, test reports

• Specify any interface/API specification proposed

The following diagram shows the high level reference of the test beds and view of the interfaces:

• Specify testing and integration:

Release candidates are delivered from CI project. We need to work out a release candidate cadence in practice to (i) have stability of the test bed for developers who are rely on a stable environment, and (ii) meet the need of testing the latest release candidate. A suitable cadence needs to be worked out, or a rolling scheme.

• Debugging and Tracing

Debugging and tracing are part of main deliverables for all in scope testing.

• Unit/Integration Test plans

Test plans of platform level and tool level instrumentation will be covered in this project. It is assumed that a sister VNF test case project will produce higher level use cases.

• Client tools developed for status shows etc.

Covered in this project includes tools that may go to a developer's client, e.g. for emulation of certain network connectivity. Most of other "client" tools may be supported with web UI.

• Identity a list of features and functionality will be developed.
• Identify what is in or out of scope. So during the development phase, it helps reduce discussion.
• Describe how the project is extensible in future

• Specify testing and integration like interoperability, scalability, high availablity
• What QA and test resources will be available?

• API Docs
• Functional block description

• Identify similar projects is underway or being proposed in OPNFV or upstream project
• Identify any open source upstream projects and release timeline.
• Identify any specific development be staged with respect to the upstream project and releases.
• Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications.
• If project is an integration and test, identify hardware dependency.

• Name of and affiliation of the maintainer: Wenjing Chu (Dell)
• Names and affiliations of the committers
• Any other contributors

• Described the project release package as OPNFV or open source upstream projects.
• If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables.

• When is the first release planned?

This will be part of the first release.

• Will this align with the current release cadence?

Yes.