logging: clarifications on NFS workaround

[sosiouxme]

Help address https://bugzilla.redhat.com/show_bug.cgi?id=1347666

[ahardin-rh]

s/were/is

[sosiouxme]

alright, no subjunctive then :-)

On Mon, Aug 22, 2016 at 5:10 PM, Ashley Hardin notifications@github.com
wrote:

In install_config/aggregate_logging.adoc
#2703 (comment)
:

@@ -476,9 +476,9 @@ request for that size.
Using NFS storage as a volume or a persistent volume (or via NAS such as
Gluster) is not supported for Elasticsearch storage, as Lucene relies on file
system behavior that NFS does not supply. Data corruption and other problems can
-occur. If NFS storage is a requirement, you can allocate a large file on that
-storage to serve as a storage device and treat it as a local mount on each host.
-For example:
+occur. If NFS storage is a requirement, you can allocate a large file on a
+volume to serve as a storage device and mount it locally on one host.
+For example, if your NFS storage volume were mounted at /nfs/storage:

s/were/is

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openshift/openshift-docs/pull/2703/files/891d4a26abaff1edd11dd449651785ca97c9c807#r75759467,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABz-l3TRbFe0mGGiTx8PzZZmFUNLGhpks5qihA_gaJpZM4JqSLV
.

[ahardin-rh]

Added labels to align with work done in #2599

[ahardin-rh]

Thanks!

[ahardin-rh]

[rev_history]
|xref:../install_config/aggregate_logging.adoc#install-config-aggregate-logging[Aggregating Container Logs]
|Added clarifying details to the Warning box in the xref:../install_config/aggregate_logging.adoc#aggregated-logging-persistent-storage[Persistent Elasticsearch Storage] section regarding the NFS workaround.
%

[tpoitras]

@ahardin-rh @sosiouxme

This PR was marked as Milestone:"Next Release" and with labels for enterprise-3.2 and enterprise-3.1. However, this PR updates a WARNING admonition that was only introduced in #2538 which is marked as Milestone:"Future Release" and is only tagged for enterprise-3.3

If the doc updates from this PR are actually related to enterprise-3.2 and enterprise-3.1 as originally labeled, then:

A) Those updates need to be located somewhere in this topic that is already published to those branches. Otherwise, this cannot be published anywhere but 3.3 docs.

Or,

B) If #2538 applies to 3.2 and 3.1 as well, then it should be labeled as such and published to those branches so that this PR #2703 can be published to them as well.

For now, I have changed the label to enterprise-3.3 and updated the Milestone to "Future Release".

[sosiouxme]

@tpoitras you make a good point; and unfortunately the full admonition (with directions for a workaround) links in to other changes that require 3.3/origin.

The warning about NFS being unsupported still applies in 3.1 and 3.2 though. Can we just include that part:

[WARNING]
====
Using NFS storage as a volume or a persistent volume (or via NAS such as
Gluster) is not supported for Elasticsearch storage, as Lucene relies on file
system behavior that NFS does not supply. Data corruption and other problems can
occur