opnfv-orange
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
opnfv-orange [2015/10/10 15:27] Eric Debeau |
opnfv-orange [2016/03/16 10:09] (current) David Blaisonneau [Testbed description] |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| Access to the laboratory is granted by the laboratory administrator. The procedure to get credentials, the documentation (architecture, user guide), the testbed inventory (hardware, bare metal capabilities, available tooling) and the local policy (physical access, specific code of conduct) are described in the page below. | Access to the laboratory is granted by the laboratory administrator. The procedure to get credentials, the documentation (architecture, user guide), the testbed inventory (hardware, bare metal capabilities, available tooling) and the local policy (physical access, specific code of conduct) are described in the page below. | ||
| - | Members are encouraged to share as many results as possible. The results of community tests would be collected into the Pharos dashboard. The Pharos project will disseminate the test results so any testbed of the federation could replay and consolidate test campaigns with different combination of hardware/software. | + | Members are encouraged to share as many results as possible. The results of community tests would be collected into the [[https://wiki.opnfv.org/pharos|Pharos]] dashboard. The [[https://wiki.opnfv.org/pharos|Pharos project]] will disseminate the test results so any testbed of the federation could replay and consolidate test campaigns with different combination of hardware/software. |
| Specific tests by members using proprietary components to help improving the overall quality of the OPNFV solution are possible. Members participating in such interoperability event, dry run, practice run, certification wave, wave rehearsals must not (either before, during or after the scheduled development lab use or interoperability event, dry run, practice run, certification wave, wave rehearsal or while performing daily tasks at any of Orange test development laboratories): | Specific tests by members using proprietary components to help improving the overall quality of the OPNFV solution are possible. Members participating in such interoperability event, dry run, practice run, certification wave, wave rehearsals must not (either before, during or after the scheduled development lab use or interoperability event, dry run, practice run, certification wave, wave rehearsal or while performing daily tasks at any of Orange test development laboratories): | ||
| Line 74: | Line 74: | ||
| * Disk: 2xIntel SSD DC S3500 480GB | * Disk: 2xIntel SSD DC S3500 480GB | ||
| * NIC: Default + Intel Eth [[http://ark.intel.com/products/58954/Intel-Ethernet-Converged-Network-Adapter-X540-T2|X540T2]] | * NIC: Default + Intel Eth [[http://ark.intel.com/products/58954/Intel-Ethernet-Converged-Network-Adapter-X540-T2|X540T2]] | ||
| + | |||
| + | === Network Design === | ||
| + | |||
| + | * [[opnfv-orange-pod2|Lannion Pod2]] | ||
| === VNFs === | === VNFs === | ||
| Line 89: | Line 93: | ||
| * [[opnfv-orange-paris|Installation OPNFV Orange Paris]] | * [[opnfv-orange-paris|Installation OPNFV Orange Paris]] | ||
| - | * [[https://github.com/Orange-OpenSource/opnfv/|Installation OPNFV Orange Lannion]] | + | * Installation OPNFV Orange Lannion: Joid procedure |
opnfv-orange.1444490833.txt.gz ยท Last modified: 2015/10/10 15:27 by Eric Debeau
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
