Differences

This shows you the differences between two versions of the page.

--- pharos_rls_b_support [2015/11/02 23:43]
Trevor Cooper
+++ pharos_rls_b_support [2016/02/09 21:21] (current)
Jack Morgan
@@ Line 1: / Line 1: @@
-====== Lab management and support ======
+====== Community Lab Support ======
-===== Pharos Governance and Usage Policies =====
+We use **Jira** for initiating and tracking lab support requests, including ... requests for POD access, connectivity, add/remove hardware, network configuration and POD issues. See below for how to submit a request.
+====POD Access====
-OPNFV community hosted lab environments are made available for advancing maturity of OPNFV solutions through collaborative development and testing projects ... including, functionality, performance and interoperability testing.
+Access to each environment is granted at the discretion of the lab owner. Each lab maintains there own lab description, capabilities (Pharos provides templates) and any specifics regarding remote access, network topology, user guides, install procedures, etc.
-Access to each environment is granted at the discretion of the lab administrator. Each lab maintains a Wiki page with procedure to get credentials, network architecture, user guides, testbed inventory and specs (hardware, bare metal capabilities, available tooling) as well as particular usage policies.
+While lab resources are managed at the POD level by owners, prioritization and resource contentions issues may be referred to the TSC if needed.
-Infrastructure users are encouraged to share results, learnings and provide suggestions for improvements that can benefit other projects and the community.
+====Communication====
-A Pharos dashboard is being developed to provide visibility of projects executing on community test-beds. The Pharos project will also disseminate test results so other test-beds can recreate test-cases using different combinations of hardware/software.
+For communication with Pharos community and lab support we use __//IRC channel//__ **#opnfv-pharos**
-Policies
+====Requesting Support or reporting an issue====
-Intellectual Property
+. Create a new issue in Jira with type **Task** (https://jira.opnfv.org/projects/PHAROS/summary)
-  * Specific tests by members using proprietary components shall notify test-bed administrator and project lead of any intellectual property and conditions of usage (e.g. licenses required)
+. Assign **Priority** as: Blocker; Critical; Major; Minor; Trivial
-  * ...
+. Select applicable release **Version**: e.g. Brahmaputra
-Resource reservations are managed at the test-bed level by individual testbed administrators. Prioritization and resource contentions are referred to the TSC as necessary.
+. Use **Component** to assign as:
+    a) POD Access Request (Request to add/remove an individuals (VPN) access for a community lab)
+    b) POD Connectivity Request (Request to add/remove lab firewall rules to connect POD to remote service e.g. CI)
+    c) POD Hardware Request (Request to add/remove POD hardware e.g. NIC, memory, ...)
+    d) POD Network Request (Request to add/remove/change POD or Host network configuration)
+    e) POD Issue (Report an issue with a POD for the lab owner to troubleshoot)
+. **Assign** to appropriate lab owner (See  here https://wiki.opnfv.org/pharos?&#community_test_labs for current lab owner). If you are not sure it will be assigned to Pharos PTL by default (they will re-assign appropriate ownership but this may delay your request)
+. Be sure to specify which **Lab and POD** you are working with.
+Note: Please provide your gpg key when requesting VPN access so your user name and password can be sent securely.

Wiki

User Tools

Site Tools

Differences

Page Tools