Skip to content

Follow-up edits to PR#2599 #2607

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ahardin-rh merged 1 commit into from
Aug 4, 2016
Merged

Follow-up edits to PR#2599 #2607

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions install_config/aggregate_logging.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -419,7 +419,8 @@ Elasticsearch deployment configuration.
The best-performing volumes are local disks, if it is possible to use
them. Doing so requires some preparation as follows.

. The relevant service account must be given the privilege to mount and edit a local volume, as follows:
. The relevant service account must be given the privilege to mount and edit a
local volume, as follows:
+
====
----
Expand All @@ -430,7 +431,8 @@ $ oadm policy add-scc-to-user privileged \
this service account.
====

. Each Elasticsearch replica definition must be patched to claim that privilege, for example:
. Each Elasticsearch replica definition must be patched to claim that privilege,
for example:
+
----
$ for dc in $(oc get deploymentconfig --selector logging-infra=elasticsearch -o name); do
Expand All @@ -444,7 +446,7 @@ $ for dc in $(oc get deploymentconfig --selector logging-infra=elasticsearch -o
the local storage, and should not move around even if those nodes are
taken down for a period of time. This requires giving each Elasticsearch
replica a node selector that is unique to the node where an administrator
has allocated storage for it. xref:#logging-node-selector[See below
has allocated storage for it. xref:logging-node-selector[See below
for directions on setting a node selector].

. Once these steps are taken, a local host mount can be applied to each replica
Expand Down Expand Up @@ -472,9 +474,9 @@ $ for dc in $(oc get deploymentconfig --selector logging-infra=elasticsearch -o
----
endif::openshift-enterprise[]

If using host mounts is impractical or
undesirable, it may be necessary to attach block storage as a
xref:../architecture/additional_concepts/storage.adoc#persistent-volume-claims[PersistentVolumeClaim])
If using host mounts is impractical or undesirable, it may be necessary to
attach block storage as a
xref:../architecture/additional_concepts/storage.adoc#persistent-volume-claims[PersistentVolumeClaim]
as in the following example:

----
Expand Down