From d8ed4f63a5af8f8836c8951623e6760ddb15710e Mon Sep 17 00:00:00 2001 From: Julien Date: Mon, 11 Sep 2017 22:15:11 +0800 Subject: Update contents in E release correct some information like: links and descriptions delete unuseful information JIRA: PHAROS-311 Change-Id: I1fceaa13fbff540bcd3f314f4653c7cc8c485091 Signed-off-by: Julien --- docs/release/release-notes/lab-description/index.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'docs/release/release-notes/lab-description/index.rst') diff --git a/docs/release/release-notes/lab-description/index.rst b/docs/release/release-notes/lab-description/index.rst index 23b675ae..191b08fc 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 `_ 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. -- cgit 1.2.3-korg