User Tools

Site Tools


opnfv_platform_characterization

This is an old revision of the document!


Project Name:

  • Proposed name for the project: OPNFV Platform Characterization
  • Proposed name for the repository: tbd
  • Project Categories: Integration & Testing

Project description:

The OPNFV Platform Characterization project targets functional and performance testing of OPNFV releases on community agreed platform configurations as a reference for evaluating and developing NFVI solutions.

A set of prioritized use-cases will provide focus and drive individual projects with either of the following approaches …

  • OPNFV Platform - VNF deployment testing (NFV use-cases with focus on functional testing)
  • OPNFV Platform - Performance Benchmarking (micro or macro benchmarks with focus on platform performance and stability)

Scope:

  • Describe the problem being solved by project
  • Specify any interface/API specification proposed,
  • Specify testing and integration:
  • Debugging and Tracing
  • Unit/Integration Test plans
  • Client tools developed for status shows etc.
  • 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

Testability: ''(optional, Project Categories: Integration & Testing)''

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

Documentation: ''(optional, Project Categories: Documention)''

  • API Docs
  • Functional block description

Dependencies:

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

Committers and Contributors:

  • Name of and affiliation of the maintainer
  • Names and affiliations of the committers
  • Any other contributors

Planned deliverables

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

Proposed Release Schedule:

  • When is the first release planned?
  • Will this align with the current release cadence
opnfv_platform_characterization.1415251010.txt.gz · Last modified: 2014/11/06 05:16 by Trevor Cooper