User Tools

Site Tools


platform_tooling

This is an old revision of the document!


Project Name:

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

Project description:

  • 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
  4. support both micro/macro level testing, virtual infrastructure level or VNFC or VNF level testing
  5. can host multi-origin/multi-vendor VNFs, i.e. compositions of vnfc's
  6. support regression, functional, and performance/benchmark testing
  7. covers both hw and sw components
  • 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

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: W.Chu (Dell)
  • 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?

This will be part of the first release.

  • Will this align with the current release cadence?

Yes.

platform_tooling.1414175414.txt.gz · Last modified: 2014/10/24 18:30 by Wenjing Chu