Merge pull request #13580 from mburke5678/logging-remove-ansible

Removing Ansible from Logging topics

Author: mburke5678

logging/efk-logging-deploy.adoc

@@ -9,9 +9,7 @@ The process for deploying the EFK into {prouct-title} involves:
 
 * Preparing yourself and your environment;
 
-* Editing the Ansible inventory file for your environment;
-
-* Running the logging installer Ansible playbook.
+* Installing the Cluster Logging subscription using the web console.
 
 // The following include statements pull in the module files that comprise
 // the assembly. Include any combination of concept, procedure, or reference
@@ -22,12 +20,8 @@ include::modules/efk-logging-deploy-pre.adoc[leveloffset=+1]
 
 include::modules/efk-logging-storage-considerations.adoc[leveloffset=+1]
 
-include::modules/efk-logging-deploy-variables.adoc[leveloffset=+1]
-
 include::modules/efk-logging-deploy-memory.adoc[leveloffset=+1]
 
 include::modules/efk-logging-deploy-certificates.adoc[leveloffset=+1]
 
-include::modules/efk-logging-deploy-playbook.adoc[leveloffset=+1]
-
 include::modules/efk-logging-deploy-label.adoc[leveloffset=+1]

logging/efk-logging-uninstall.adoc

@@ -5,7 +5,7 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-You can use an Ansible playbook to remove the EFK stack from your {product-title} cluster.
+You can remove cluster logging from your {product-title} cluster.
 
 // The following include statements pull in the module files that comprise
 // the assembly. Include any combination of concept, procedure, or reference

modules/efk-logging-about-elasticsearch.adoc

@@ -12,12 +12,7 @@ You can configure Elasticsearch to make copies of the shards, called _replicas_.
 the Elasticsearch nodes. The *ClusterLogging* Custom Resource allows you to specify the replication policy in the Custom Resource Definition (CRD) to provide data redundancy and resilience to failure.
 
 The Cluster Logging Operator and companion Elasticsearch Operator ensure that each Elasticsearch node is deployed using a unique deployment configuration that includes its own storage volume.
-During installation, you can use the `openshift_logging_es_cluster_size` Ansible variable to specify the number of Elasticsearch nodes.
-Or, you can scale up your existing cluster by modifying the
-`openshift_logging_es_cluster_size` in the inventory file and re-running the
-logging playbook. Additional clustering parameters can be modified and are
-described in *Specifying Logging Ansible Variables*.
-
+You can use the cluster logging Custom Resource to increase the number of Elasticsearch nodes.
 Refer to
 link:https://www.elastic.co/guide/en/elasticsearch/guide/current/hardware.html[Elastic's
 documentation] for considerations involved in choosing storage and
@@ -26,8 +21,7 @@ network location as directed below.
 [NOTE]
 ====
 A highly-available Elasticsearch environment requires at least three Elasticsearch nodes,
-each on a different host, and setting the `openshift_logging_es_number_of_replicas` Ansible variable
-to a value of `1` or higher to create replicas.
+each on a different host.
 ====
 
 For more information, see https://www.elastic.co/products/elasticsearch[Elasticsearch (ES)].

modules/efk-logging-curator-configuration.adoc

@@ -5,7 +5,7 @@
 [id='efk-logging-curator-configuration_{context}']
 = Creating the Curator configuration
 
-The `openshift_logging` Ansible role provides a ConfigMap from which Curator
+The installation provides a ConfigMap from which Curator
 reads its configuration. You may edit or replace this ConfigMap to reconfigure
 Curator. Currently the `logging-curator` ConfigMap is used to configure both
 your ops and non-ops Curator instances. Any `.operations` configurations are

modules/efk-logging-deploy-certificates.adoc

@@ -5,7 +5,7 @@
 [id='efk-logging-deploy-certificates_{context}']
 = Deploying custom certificates
 
-You can specify custom certificates using the following inventory variables
+You can specify custom certificates using the following variables
 instead of relying on those generated during the deployment process. These
 certificates are used to encrypt and secure communication between a user's
 browser and Kibana. The security-related files will be generated if they are not

modules/efk-logging-deploy-memory.adoc

@@ -8,18 +8,9 @@
 By default the amount of RAM allocated to each ES instance is 16GB. You can change this value as needed.
 
 Keep in mind that *half* of this value will be passed to the individual
-elasticsearch pods java processes
+Elasticsearch pods java processes
 link:https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html#_give_half_your_memory_to_lucene[heap
 size].
 
 .Procedure
 
-. Edit the Ansible inventory file, by default *_/etc/Ansible/hosts_*.
-
-. Add or set the openshift_logging_use_ops to true.
-+
-----
-openshift_logging_es_memory_limit=<memory>
-----
-
-. Run the Ansible playbook as shown below.

modules/efk-logging-deploy-playbook.adoc

@@ -11,11 +11,6 @@ Before deploying cluster logging into {product-title} perform the following task
 
 . Be familiar with the following:
 +
-.. An Ansible playbook is available to deploy and upgrade aggregated logging. You
-should familiarize yourself with the {product-title} installation process. The installation process
-includes information for preparing to use Ansible and using the Ansible inventory file to configure
-various areas of cluster logging.
-+
 .. Review the *Storage Considerations for Cluster Logging and {product-title}* to determine how best to configure your deployment.
 
 . Make sure your environment meets the following requirements: