OPNFV currently have 2 PODs available in LF Lab. These PODs have been in use by the OPNFV CI and OPNFV developers in order to handle the CI, setup, configuration, development, and troubleshooting activities.
POD1 has been decomposed in order to have resources for build, virtual deploys and other CI-related activities. This resulted in 6 standalone servers.
POD2 has been and is still in use by CI and developers for the CI, development, and troubleshooting related activities.
It is important to clarify the current use of the resources located in OPNFV LF Lab in order to identify what they should really be used (CI-related activities, etc.) and settle on access rules (who should have the access and for what purpose).
Ideally, the resources located in OPNFV LF Lab should be seen/handled as the reference resources and only CI, infra setup/configuration and troubleshooting work should be done on them. Direct access to them should be kept at minimum. All the project development work should be shifted to OPNFV Community Labs wherever possible.
For questions about access: firstname.lastname@example.org
Please send your access request to email@example.com. The following information should be included …
Name: Company: Approved Project: Project role: Why is access needed: How long is access needed (either a specified time period or define "done"): What specific POD/machines will be accessed: What support is needed from LF admins and LF community support team:
Should further clarifications be needed you may be asked to attend the next Pharos meeting (Weekly meetings logistics: https://wiki.opnfv.org/meetings#pharos_meetings) to discuss your request with the Pharos community.
Once access is approved please follow instructions for setting up VPN access … https://wiki.opnfv.org/get_started/lflab_hosting
Below community members currently have the access to OPNFV LF Lab.
|Member Name||Project and Role||Why the Access is Needed|