opnfv_testbed_infrastructure
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
opnfv_testbed_infrastructure [2014/12/01 21:29] Trevor Cooper |
opnfv_testbed_infrastructure [2015/01/15 06:27] (current) Trevor Cooper |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== OPNFV Project Proposal: Testbed Infrastructure ==== | ==== OPNFV Project Proposal: Testbed Infrastructure ==== | ||
| - | Version: 1.0 (Nov 24, 2014) | + | Version: 1.0 (Dec 2, 2014) |
| **Project Name: ** | **Project Name: ** | ||
| Line 11: | Line 11: | ||
| **Project repository:** | **Project repository:** | ||
| - | opnfv-repo-pharos or opnfv-repo-tbd | + | pharos |
| **Project Categories:** | **Project Categories:** | ||
| - | * Documentation | ||
| * Integration & Testing | * Integration & Testing | ||
| - | * Collaborative Development | + | |
| **Project Description** | **Project Description** | ||
| Line 23: | Line 22: | ||
| This project proposes developing a test-bed framework for creating a federated NFV test capability that will be hosted by a number of companies in the OPNFV community. We have at least 1 volunteer party in each of Asia, Europe and US at this time. The volunteer parties will be responsible to setup, operate, and maintain these test-beds in a way that is consistent with the proposed OPNFV test-bed framework. | This project proposes developing a test-bed framework for creating a federated NFV test capability that will be hosted by a number of companies in the OPNFV community. We have at least 1 volunteer party in each of Asia, Europe and US at this time. The volunteer parties will be responsible to setup, operate, and maintain these test-beds in a way that is consistent with the proposed OPNFV test-bed framework. | ||
| + | {{ :opnfv-test.jpg?600 }} | ||
| 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): | 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): | ||
| Line 56: | Line 56: | ||
| //Reference platform hardware and software definition// | //Reference platform hardware and software definition// | ||
| - | * In order for the testbeds have some 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. | + | * In order for the testbeds have some 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 (see [[get_started|Project: Bootstrap/Get started!]] project), 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 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. | ||
| Line 79: | Line 79: | ||
| This project has the following dependencies | This project has the following dependencies | ||
| - | * Eventually, the software we use will need to be the output of the CI project. | + | * Eventually, the software we use will need to be the output of the [[get_started:get_started_project_proposal|Get Started/Bootstrap]] or [[octopus:project_proposal|CI project]]. |
| * We may use tools from other OPNFV projects or from other upstream projects. | * 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. | * We may use commercial hardware test equipment or non-open-source test software in non-exclusive basis. | ||
| Line 90: | Line 90: | ||
| ** Committers and Contributors ** | ** Committers and Contributors ** | ||
| - | A partial list at this moment: | + | Committers: |
| * Wenjing Chu, wenjing_chu@dell.com, | * Wenjing Chu, wenjing_chu@dell.com, | ||
| * Morgan Richomme <morgan.richomme@orange.com>, | * Morgan Richomme <morgan.richomme@orange.com>, | ||
| * Trevor Cooper, trevor.cooper@intel.com, | * Trevor Cooper, trevor.cooper@intel.com, | ||
| + | * Qiao Fu, fuqiao@chinamobile.com | ||
| + | * Sean Chen (s.chen@huawei.com) | ||
| + | |||
| + | Contributors: | ||
| * C.Donley@cablelabs.com, | * C.Donley@cablelabs.com, | ||
| * erica.johnson@iol.unh.edu, | * erica.johnson@iol.unh.edu, | ||
| - | * sheng-ann.yu@ericsson.com, | + | * Kuppuswamy, Prabu <Prabu.Kuppuswamy@spirent.com> |
| - | * Qiao Fu, fuqiao@chinamobile.com, | + | * Saikrishna M Kotha <saikrishna.kotha@xilinx.com> |
| + | * Eugene Yu (yuyijun@huawei.com) | ||
| ** Planned Deliverables ** | ** Planned Deliverables ** | ||
| Line 107: | Line 113: | ||
| * A set of software tools for users to access the testbeds. | * A set of software tools for users to access the testbeds. | ||
| * Smoke test and tools for running/automating the smoke test. | * Smoke test and tools for running/automating the smoke test. | ||
| + | * A repository for storing and sharing test artifacts | ||
| ** Proposed Release Schedule ** | ** Proposed Release Schedule ** | ||
| Line 114: | Line 121: | ||
| + | {{ :test-bed-timeline.png?nolink&900 |}} | ||
opnfv_testbed_infrastructure.1417469360.txt.gz · Last modified: 2014/12/01 21:29 by Trevor Cooper
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
