Merge pull request #13451 from mburke5678/logging-deploy-subscription

Added web console steps to create subscription for logging

Author: mburke5678

logging/efk-logging-deploy.adoc

@@ -18,10 +18,12 @@ The process for deploying the EFK into {prouct-title} involves:
 
 include::modules/efk-logging-deploy-pre.adoc[leveloffset=+1]
 
-include::modules/efk-logging-storage-considerations.adoc[leveloffset=+1]
+include::modules/efk-logging-deploy-subscription.adoc[leveloffset=+1]
 
-include::modules/efk-logging-deploy-memory.adoc[leveloffset=+1]
+include::modules/efk-logging-deploy-storage-considerations.adoc[leveloffset=+1]
 
-include::modules/efk-logging-deploy-certificates.adoc[leveloffset=+1]
+// include::modules/efk-logging-deploy-memory.adoc[leveloffset=+1]
 
-include::modules/efk-logging-deploy-label.adoc[leveloffset=+1]
+// include::modules/efk-logging-deploy-certificates.adoc[leveloffset=+1]
+
+// include::modules/efk-logging-deploy-label.adoc[leveloffset=+1]

modules/efk-logging-deploy-label.adoc

@@ -13,12 +13,14 @@ example:
 
 Using a simple loop:
 
+[source,bash]
 ----
 $ while read node; do oc label nodes $node logging-infra-fluentd=true; done < 20_fluentd.lst
 ----
 
 The following also works:
 
+[source,bash]
 ----
 $ oc label nodes 10.10.0.{100..119} logging-infra-fluentd=true
 ----

modules/efk-logging-deploy-pre.adoc

@@ -17,14 +17,15 @@ Before deploying cluster logging into {product-title} perform the following task
 +
 .. Ensure that you have deployed a router for the cluster.
 +
-** Ensure that you have the necessary persistent storage for Elasticsearch. Note that each Elasticsearch node
+.. Ensure that you have the necessary persistent storage for Elasticsearch. Note that each Elasticsearch node
 requires its own storage volume. 
 
 . Specify a node selector
 +
 In order for the logging pods to spread evenly across your cluster, an empty
 node selector should be used.
 +
+[source,bash]
 ----
 $ oc adm new-project logging --node-selector=""
 ----

modules/efk-logging-storage-considerations.adoc renamed to modules/efk-logging-deploy-storage-considerations.adoc

@@ -2,7 +2,7 @@
 //
 // * logging/efk-logging-deploy.adoc
 
-[id='efk-logging-storage-considerations_{context}']
+[id='efk-logging-deploy-storage-considerations_{context}']
 = Storage considerations for cluster logging and {product-title}
 
 An Elasticsearch index is a collection of shards and its corresponding replica
@@ -68,6 +68,8 @@ Calculating total logging throughput and disk space required for your logging
 environment requires knowledge of your application. For example, if one of your
 applications on average logs 10 lines-per-second, each 256 bytes-per-line,
 calculate per-application throughput and disk space as follows:
+
+[source,bash]
 ----
  (bytes-per-line * (lines-per-second) = 2560 bytes per app per second
  (2560) * (number-of-pods-per-node,100) = 256,000 bytes per second per node

modules/efk-logging-deploy-subscription.adoc

@@ -0,0 +1,23 @@
+// Module included in the following assemblies:
+//
+// * logging/efk-logging-deploy.adoc
+
+[id='efk-logging-deploy-subscription_{context}']
+= Installing the Cluster Logging Operator
+
+You can use the {product-title} console to install cluster logging, which creates the Cluster Logging Operator.
+
+.Procedure
+
+To install cluster logging:
+
+. In the {product-title} console, click *Catalog* -> *Operator Hub*. 
+
+. Choose  *cluster-logging* from the list of available Operators, and click Install.
+
+. On the *Create Operator Subscription* page change the *Target* to the *global-operators* Operator Group. This makes the Operator available to all users and projects that use this OpenShift Container Platform cluster.
+
+. On the *Catalog* → *Installed Operators* page, verify that the ClusterLogging (CSV) eventually shows up and its *Status* ultimately resolves to *InstallSucceeded*.
+
+If it does not, switch to the *Catalog* → *Operator Management* page and inspect the *Operator Subscriptions* and *Install Plans* tabs for any failure or errors under *Status*. Then, check the logs in any Pods in the openshift-operators project (on the *Workloads* → *Pods* page) that are reporting issues to troubleshoot further.
+