summaryrefslogtreecommitdiffstats
path: root/docs/release/release-notes/lab-description/index.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/release/release-notes/lab-description/index.rst')
-rw-r--r--docs/release/release-notes/lab-description/index.rst9
1 files changed, 8 insertions, 1 deletions
diff --git a/docs/release/release-notes/lab-description/index.rst b/docs/release/release-notes/lab-description/index.rst
index 3782829f..aed596e2 100644
--- a/docs/release/release-notes/lab-description/index.rst
+++ b/docs/release/release-notes/lab-description/index.rst
@@ -13,7 +13,14 @@ network topologies. Compute, network and storage specifications with network top
required to help developers use lab resources efficiently while minimizing support needs. This also
greatly assists with troubleshoting. It is the responsibility of the lab owner to keep individual
lab documents updated and determine appropriate level of detail that is exposed publicly through
-the Wiki or maintained in a secure Pharos repo with controlled access.
+the Wiki or maintained in a secure Pharos repo
+`securedlab <https://gerrit.opnfv.org/gerrit/#/admin/projects/securedlab>`_ with controlled access.
+To avoid deplicated content, it is suggested to directly include the rst docs in the wiki.
+
+Before Danube release, securedlab is only opened for Infra WG committers and installer projects's
+contributors. Since Euphrates release, it is opened for all the contributors of Pharos project, if
+you are the owner of a community lab, please ask helpdesk to become a Pharos contributor in order
+to submit your PDF to the securedlab repo.
The goal of the Pharos Project is automation of resource provisioning. This requires machine
readable inventory and network configuration files that follow common format.