Change the release name to Guilin

Change-Id: I6ebb658881877cc13fb4bb77dc836c6af36ba3b3
Issue-ID: HOLMES-377
Signed-off-by: GuangrongFu <fu.guangrong@zte.com.cn>
(cherry picked from commit 5d2981cb85027565936dbb7ce2597f1edb6fe472)

diff --git a/docs/conf.yaml b/docs/conf.yaml
index ab59281..189e1d0 100644 (file)
--- a/docs/conf.yaml
+++ b/docs/conf.yaml
@@ -3,5 +3,5 @@ project_cfg: onap
 project: onap
 
 # Change this to ReleaseBranchName to modify the header
-default-version: latest
+default-version: guilin
 #

diff --git a/docs/platform/architecture.rst b/docs/platform/architecture.rst
index 4acda61..39bb8d1 100644 (file)
--- a/docs/platform/architecture.rst
+++ b/docs/platform/architecture.rst
@@ -5,7 +5,7 @@
 Holmes Architecture
 -------------------
 
-Basically, Holmes itself is an independent component in ONAP, which means it could be deployed as an ONAP-level component. In the Beijing release, Holmes is more generally a DCAE analytic application. It is deployed by DCAE and run as an analytic application on top of it. Also, it could be considered as a filter of the Policy component because it reduces the number of the input messages of Policy.
+Basically, Holmes itself is an independent component in ONAP, which means it could be deployed as an ONAP-level component. In the Guilin release, Holmes is more generally a DCAE analytic application. It is deployed by DCAE and run as an analytic application on top of it. Also, it could be considered as a filter of the Policy component because it reduces the number of the input messages of Policy.
 
 .. image:: images/overall-architecture-in-onap.png
 

diff --git a/docs/platform/configuration.rst b/docs/platform/configuration.rst
index 4a1faa3..f3308e7 100644 (file)
--- a/docs/platform/configuration.rst
+++ b/docs/platform/configuration.rst
@@ -4,5 +4,5 @@
 Configuration
 -------------
 
-No machanism for customized configurtions is provided in the El Alto release. Such functionalities will be provided in the future if necessary.
+No machanism for customized configurtions is provided in the Guilin release. Such functionalities will be provided in the future if necessary.
 

diff --git a/docs/platform/consumedapis.rst b/docs/platform/consumedapis.rst
index 6d803d1..7b06e0e 100644 (file)
--- a/docs/platform/consumedapis.rst
+++ b/docs/platform/consumedapis.rst
@@ -4,7 +4,7 @@
 Consumed APIs
 -------------
 
-In the Amsterdam release, Holmes mainly depends on the APIs provided by DCAE, A&AI, DMaaP and MSB.
+In the Guilin release, Holmes mainly depends on the APIs provided by DCAE, A&AI, DMaaP and MSB.
 
 DCAE
 ^^^^

diff --git a/docs/platform/human-interfaces.rst b/docs/platform/human-interfaces.rst
index 4021206..fd5409a 100644 (file)
--- a/docs/platform/human-interfaces.rst
+++ b/docs/platform/human-interfaces.rst
@@ -7,7 +7,7 @@ Human Interfaces
 Target Users
 ^^^^^^^^^^^^
 
-The human interfaces provided in the Beijing release by Holmes is intended for the developers rather than the end users.
+The human interfaces provided in the Guilin release by Holmes is intended for the developers rather than the end users.
 
 Interface Type
 ^^^^^^^^^^^^^^

diff --git a/docs/platform/installation.rst b/docs/platform/installation.rst
index baf36ef..1b8d51e 100644 (file)
--- a/docs/platform/installation.rst
+++ b/docs/platform/installation.rst
@@ -4,7 +4,7 @@
 Installation
 ------------
 
-In the El Alto release, Holmes is deployed as an analytic application by the DCAE controller. So the users do not have to install it on their own.
+In the Guilin release, Holmes is deployed as an analytic application by the DCAE controller. So the users do not have to install it on their own.
 
 In case the users want to deploy Holmes independently, the steps for the installation is as follows.
 

diff --git a/docs/platform/log-and-diagnostic-info.rst b/docs/platform/log-and-diagnostic-info.rst
index bc14b8b..9a09b8e 100644 (file)
--- a/docs/platform/log-and-diagnostic-info.rst
+++ b/docs/platform/log-and-diagnostic-info.rst
@@ -4,7 +4,7 @@
 Logging & Diagnostic Information
 ---------------------------------
 
-In the El Alto release, the logs are kept inside the docker containers, which means that you can get the log information only when the docker is still running. 
+In the Guilin release, the logs are kept inside the docker containers, which means that you can get the log information only when the docker is still running. 
 
 Where to Access Information
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^