Doc updates for London

Arch diagram updates
Remove MOD/design components
Remove cloudify based deployment
Standardize deployment steps for DCAE current Ms
Misc updates

onap-gerrit-review: -changelog-or-release-file-missing
onap-gerrit-review: -no-nl-ending-on-files
onap-gerrit-review: -missing-setup-py
onap-gerrit-review: -changelog-missing

Change-Id: I99c6c8e870fa2f54af0a9d26267d0fb6901c74a9
Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>
Issue-ID: DCAEGEN2-3360
Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>

4 files changed, 2 insertions, 82 deletions

diff --git a/docs/sections/services/ves-hv/architecture.rst b/docs/sections/services/ves-hv/architecture.rst
index e71bf6a3..4634f131 100644
--- a/docs/sections/services/ves-hv/architecture.rst
+++ b/docs/sections/services/ves-hv/architecture.rst
@@ -7,7 +7,7 @@ High-level architecture of HV-VES
 =================================
 
 HV-VES Collector is a part of DCAEGEN2. Its goal is to collect data from xNF (PNF/VNF) and put the data on a given Kafka topic.
-High Volume Collector is deployed with DCAEGEN2 via OOM Helm charts and Cloudify blueprints.
+High Volume Collector is deployed with DCAEGEN2 via OOM Helm charts.
 
 Input messages come from TCP interface and Wire Transfer Protocol. Each frame includes Google Protocol Buffers (GPB) encoded payload.
 Based on information provided in CommonEventHeader, domain messages are validated and published to specific Kafka topic.
diff --git a/docs/sections/services/ves-hv/installation.rst b/docs/sections/services/ves-hv/installation.rst
deleted file mode 100644
index 4b7eb238..00000000
--- a/docs/sections/services/ves-hv/installation.rst
+++ /dev/null
@@ -1,76 +0,0 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-
-.. _installation:
-
-HV-VES Cloudify Installation
-============================
-
-Starting from ONAP/Honolulu release, HV-VES is installed with a DCAEGEN2-Services Helm charts.
-This installation mechanism is convenient, but it doesn`t support all HV-VES features (e.g. CMP v2 certificates, and IPv4/IPv6 dual stack networking). This description demonstrates, how to deploy HV-VES collector using Cloudify orchestrator.
-
-Setting insecure mode for testing
----------------------------------
-
-HV-VES application is configured by default to use TLS/SSL encryption on TCP connection. 
-
-Accessing bootstrap container with Kubernetes command line tool
----------------------------------------------------------------
-
-To find bootstrap pod, execute the following command:
-
-::
-
-    kubectl -n <onap namespace> get pods | grep bootstrap
-
-To run command line in bootstrap pod, execute:
-
-::
-
-    kubectl -n <onap namespace> exec -it <bootstrap-pod-name> bash
-
-
-Install HV-VES collector using Cloudify blueprint inputs
----------------------------------------------------------
-
-1. If You have a running HV-VES instance, uninstall HV-VES and delete current deployment:
-
-:: 
-
-    cfy executions start -d hv-ves uninstall
-    cfy deployments delete hv-ves 
-
-2. Create new deployment with inputs from yaml file (available by default in bootstrap container):
-
-:: 
-
-    cfy deployments create -b hv-ves -i inputs/k8s-hv_ves-inputs.yaml hv-ves
-
-In order to disable the TLS security, override the 'secuirty_ssl_disable' value in the deloyment:
-
-::
-
-    cfy deployments create -b hv-ves -i inputs/k8s-hv_ves-inputs.yaml -i security_ssl_disable=True hv-ves
-
-To verify inputs, You can execute: 
-
-:: 
-
-    cfy deployments inputs hv-ves
-
-3. Install HV-VES deployment:
-
-:: 
-
-    cfy executions start -d hv-ves install
-
-
-Using external TLS certificates obtained using CMP v2 protocol
---------------------------------------------------------------
-
-In order to use the X.509 certificates obtained from the CMP v2 server (so called "operator`s certificates"), refer to the following description:
-
-.. toctree::
-    :maxdepth: 1
-
-     Enabling TLS with external x.509 certificates <../../tls_enablement>
diff --git a/docs/sections/services/ves-hv/run-time-configuration.rst b/docs/sections/services/ves-hv/run-time-configuration.rst
index 830ed664..4da0b10d 100644
--- a/docs/sections/services/ves-hv/run-time-configuration.rst
+++ b/docs/sections/services/ves-hv/run-time-configuration.rst
@@ -48,7 +48,4 @@ For more information, see :ref:`supported_domains`.
 Providing configuration during OOM deployment
 ---------------------------------------------
 
-The configuration is created from HV-VES Cloudify blueprint by specifying **application_config** node during ONAP OOM/Kubernetes deployment. Example of the node specification:
-
-.. literalinclude:: resources/blueprint-snippet.yaml
-    :language: yaml
+The configuration is created from HV-VES Helm charts defined under **applicationConfig**  during ONAP OOM/Kubernetes deployment. 
diff --git a/docs/sections/services/ves-hv/troubleshooting.rst b/docs/sections/services/ves-hv/troubleshooting.rst
index 36510355..c7b6a291 100644
--- a/docs/sections/services/ves-hv/troubleshooting.rst
+++ b/docs/sections/services/ves-hv/troubleshooting.rst
@@ -213,7 +213,6 @@ They can be changed by specifying ``security.keys.trustStore`` or ``security.key
 
 For testing purposes there is possibility to use plain TCP protocol. In order to do this navigate with your browser to consul-ui service and than pick KEY/VALUE tab. Select dcae-hv-ves-collector and change ``security.sslDisable`` to true. Update of configuration should let start TCP server without SSL/TLS configured.
 
-In order to disable TLS/SSL by overriding Cloudify blueprint inputs, see :ref:`running_insecure`.
 
 ====