pharos:lf_lab
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
pharos:lf_lab [2015/10/15 14:35] Fatih Degirmenci created |
pharos:lf_lab [2015/10/29 18:22] (current) Trevor Cooper [Clarifying current use identifying future use of OPNFV LF Lab] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== OPNFV LF Lab ====== | + | ====== OPNFV Linux Foundation (LF) Lab ====== |
| - | ===== Available Resources in OPNFV LF Lab ===== | + | ===== Resources in OPNFV LF Lab ===== |
| - | 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, development, and troubleshooting activities. | + | 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. |
| - | [[https://wiki.opnfv.org/get_started/lflab_hosting#pod1 POD1]] has been decomposed in order to have resources for build, virtual deploys and other CI-related activities. This resulted in 6 standalone servers. | + | [[https://wiki.opnfv.org/get_started/lflab_hosting#pod1 | POD1]] has been decomposed in order to have resources for build, virtual deploys and other CI-related activities. This resulted in 6 standalone servers. |
| - | [[https://wiki.opnfv.org/get_started/lflab_hosting#pod2 POD2]] has been and is still in use by CI and developers for the work CI and development related activities. | + | [[https://wiki.opnfv.org/get_started/lflab_hosting#pod2 | POD2]] has been and is still in use by CI and developers for the CI, development, and troubleshooting related activities. |
| - | ===== Clarifying the current use and identifying the future use of OPNFV LF Lab ===== | + | ===== Clarifying current use identifying future use of OPNFV LF Lab ===== |
| - | 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) and settle on access rules (who should have the access). | + | 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 handled as the reference resources and only CI and troubleshooting work should be done on them. All the project development work should be shifted to OPNFV Community Labs. | + | 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. |
| + | |||
| + | ===== Proposal on The Future Use and Access Rules ===== | ||
| + | |||
| + | * Usage Proposal | ||
| + | * Resources located in OPNFV LF Lab shall only be used for CI, infra setup/configuration and troubleshooting purposes. | ||
| + | * No development work is allowed in OPNFV LF Lab. | ||
| + | * Access Rules Proposal | ||
| + | * Limit the direct access to OPNFV LF Lab to only projects/people who need to access the infrastructure for infra setup/configuration and troubleshooting purposes. | ||
| + | * The development work shall only be done on Community Labs. | ||
| + | |||
| + | ===== Requesting Access to Linux Foundation Lab ===== | ||
| + | |||
| + | For questions about access: [[infra-steering@lists.opnfv.org]] | ||
| + | |||
| + | **STEP 1** | ||
| + | |||
| + | Please send your access request to [[infra-steering@lists.opnfv.org]]. 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: | ||
| + | |||
| + | **STEP 2** | ||
| + | |||
| + | 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. | ||
| + | |||
| + | **STEP 3** | ||
| + | |||
| + | Once access is approved please follow instructions for setting up VPN access ... https://wiki.opnfv.org/get_started/lflab_hosting | ||
| + | |||
| ===== OPNFV Community Members with Access to OPNFV LF Lab ===== | ===== OPNFV Community Members with Access to OPNFV LF Lab ===== | ||
| Line 19: | Line 54: | ||
| Below community members currently have the access to OPNFV LF Lab. | Below community members currently have the access to OPNFV LF Lab. | ||
| - | ^ Member Name ^ Project and Role ^ Why the Access is Needed ^ | + | ^ ^ Member Name ^ Project and Role ^ Why the Access is Needed ^ |
| - | | | | | | + | | 1 | arnaud1.morin@orange.com | | | |
| + | | 2 | amaged@cisco.com | | | | ||
| + | | 3 | andrew.caldwell@metaswitch.com | | | | ||
| + | | 4 | cogibbs@cisco.com | | | | ||
| + | | 5 | daniel.smith@ericsson.com | | | | ||
| + | | 6 | dradez@redhat.com | | | | ||
| + | | 7 | fatih.degirmenci@ericsson.com | | | | ||
| + | | 8 | fbrockne@cisco.com | | | | ||
| + | | 9 | joseph.gasparakis@intel.com | | | | ||
| + | | 10 | jonas.bjurel@ericsson.com | | | | ||
| + | | 11 | jorgen.w.karlsson@ericsson.com | | | | ||
| + | | 12 | jose.lausuch@ericsson.com | | | | ||
| + | | 13 | morgan.richomme@orange.com | | | | ||
| + | | 14 | pbandzi@cisco.com | | | | ||
| + | | 15 | phladky@cisco.com | | | | ||
| + | | 16 | stefan.k.berg@ericsson.com | | | | ||
| + | | 17 | szilard.cserey@ericsson.com | | | | ||
| + | | 18 | trozet@redhat.com | | | | ||
pharos/lf_lab.1444919716.txt.gz · Last modified: 2015/10/15 14:35 by Fatih Degirmenci
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
