This is an old revision of the document!
This wiki page is dedicated to planning the OPNFV community test-bed infrastructure for Brahmaputra. This includes labs hosted by community companies and the Linux Foundation lab. The Pharos project team needs to define deliverables and milestones for.
Weekly meetings logistics: https://wiki.opnfv.org/meetings#pharos_meetings
Pharos theme for release B … Connected community labs with visible capability and deployment/usage monitoring … with … connectivity between LF Foundation (Central) and all community lab … and … ability to view and observe resources available to the OPNFV community at-a-glance.
Planning Etherpad … https://etherpad.opnfv.org/p/pharos_brahmaputra
Tasks are tracked on Jira
Tasks … https://jira.opnfv.org/browse/PHAROS-53?jql=project%20%3D%20PHAROS%20and%20labels%20%3D%20R2
Dashboard … https://jira.opnfv.org/browse/PHAROS/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
Sub-pages are dedicated to:
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?