Wiki

Version: 1.0 (Nov 24, 2014)

Project Name:

Faros or TBD

Project repository:

opnfv-repo-faros or opnfv-repo-tbd

Project Categories:

• Documentation
• Integration & Testing
• Collaborative Development

Project Description

This project is the combination of three work threads: testbed governance and policy, reference platform hardware and software definition, and platform tooling. We plan to submit the combined project as a single proposal to TSC.

There are many reasons that community testbeds are important resources to the success of the OPNFV mission. Here are just to name a few (and by no means exhaustive):

• For the broad community to be able to understand, evaluate and try/adopt to use OPNFV's output (e.g. an OPNFV release), we need an open, consistent, repeatable/replicatable reference testbed environment.

• While some of development, testing, benchmarking and use case work may be completed in a simple dev environment, many complex and scale cases require more substantial resources not easily available to an average developer. OPNFV does not plan to own and operate such an infrastructure at this time. Community testbeds are necessary.

• Evaluation and adoption of OPNFV is a complicated process. A reference testbed with well-documented hardware and software components can help to significantly simplify this process for the community.

• Open and consistent testbeds under an OPNFV governance and collaborative model are much more valuable than disjoined testbeds from individual entities.

This project proposes establishing and operating such an OPNFV Testbed Infrastructure.

Scope

• First, this project is to produce a common entry web interface to community testbeds hosted by different parties. This web entry is to be within OPNFV wiki. It should document common information, status, and guides about the testbeds, including governance and policies.

• In order for the testbeds have some basic commonality and portability (to upper layer software), we will define a reference hardware configuration. We will also initially define a "bootstrap" software configuration to get started, and eventually migrate to use OPNFV release(s) coming out of Continuous Integration (CI) project.

• The basic hardware components of the initial version of the testbeds will likely include (only for illustration of scope): x86 servers of relatively recent architectures, relatively high throughput PCIe, 1G and 10G Ethernet Adaptors, local storage, and 1/10G Ethernet switches.

• The basic software components of the bootstrap version may include (only for illustration of scope): Linux OS, Qemu/KVM, OpenStack, OpenVSwitch.

• This project is to produce 1 or more functional OPNFV testbeds. We have at least 1 volunteer party in Asia, Europe and US at this time. The volunteer parties are to create, operate, maintain these testbeds consistent with the common reference and policies.

• Finally, this project should also include a minimum "smoke test' set that can be run regularly to maintain basic operational status and report this status in the common wiki page.

Excluded from this project:

• Performance benchmarks
• Comprehensive functional tests
• VNF use case tests and benchmarks

Dependencies

This project has the following dependencies

• Eventually, the software we use will need to be the output of the CI project.
• We may use tools from other OPNFV projects or from other upstream projects.
• We may use commercial hardware test equipment or non-open-source test software in non-exclusive basis.

Documentation

The primary documentation is the wiki pages, including the user guide for the testbeds.

Committers and Contributors

A partial list at this moment:

• Wenjing Chu, wenjing_chu@dell.com,
• Morgan Richomme morgan.richomme@orange.com,
• Trevor Cooper, trevor.cooper@intel.com,
• C.Donley@cablelabs.com,
• erica.johnson@iol.unh.edu,
• sheng-ann.yu@ericsson.com,
• Qiao Fu, fuqiao@chinamobile.com,

Planned Deliverables

• One or more operational testbeds.
• Wiki pages as web entry for testbed users.
• A reference hardware and software configuration for replicating a testbed.
• A set of software tools for users to access the testbeds.
• Smoke test and tools for running/automating the smoke test.

Proposed Release Schedule

• Nov 26, 2014: Official project proposal submission to TSC.
• Completion of the project phase I: Q1 2015, or aligned with OPNFV Release 1.

— Wenjing Chu 2014/11/24 06:23