This wiki page is dedicated to planning the OPNFV community test-bed infrastructure. This includes labs hosted by community companies as well as the OPNFV Linux Foundation lab.

Planning Etherpad … https://etherpad.opnfv.org/p/pharos_brahmaputra

The Pharos project team needs to define deliverables and milestones for Brahmaputra. Please feel free to edit this page with comments and suggestions.

There are 3 sub-pages dedicated to:

• Pharos specification (requirements for Pharos compliance)
• Lab infrastructure (tools for management and testing)
• Lab management (process and support)

Below notes are suggestions for Brahmaputra scope and deliverables (details will be captured on dedicated pages) …

1. Pharos specification (requirements for Pharos compliance)

  
- Expand Arno definition of Pharos
  - Naming conventions
  - Template for consistent view of each lab (Compute, Network, Storage specifications)
  - Requirements vs optional aspects
  - Define a uniform way to access with get-started / user guide
  - Actual specification (hardware, networks, ...)
- Define a sandbox environment/s for developers (vs. the full test-environment)
  - Can we define a virtual environment to get started?
  - Can we define a small scale bare-metal environment for community labs to host or for anybody who wants to setup a test-bed with minimum cost/effort?
- Create a formal definition of a "Pharos compliant" lab
  - Compliance checklist
  - Acceptance tests (tools, scripts)
  - Infrastructure access and user guides
  - json or yaml format to describe hardware, tooling related to testbed?
  - Deploy templates - specifies what is required in order to configure each deployment tool/method

2. Lab infrastructure (tools for management and testing)

- MAAS pilot
- User vs test environment (tools and configurations)
- Tenant vs bare metal (tools and configurations)
- Remote access infrastructure 
  - Open-VPN
  - Connection to Jenkins
- Dashboards for tracking community labs capability, availability, utilization

3. Lab management (process and support)

- Community labs
  - One person for each lab to support (SLA ... availability, etc.) 
  - Lab teams
    - Understand other labs
    - Help other lab owners
    - Dedicated IRC channel
- Linux Foundation lab
  - Define how we will use the LF infra post Arno … compiling/building/packaging/testing?
  - Support plan
  - Capacity expansion plan?