Continued updates to NFS documentation

install/configuring_inventory_file.adoc

@@ -1483,9 +1483,8 @@ terminates.
 [IMPORTANT]
 ====
 Testing shows issues with using the NFS server on RHEL as storage backend
-for the container registry. This includes the OpenShift Container Registry and Quay,
-Cassandra for metrics storage, and ElasticSearch for logging storage. Therefore,
-using NFS to back PVs used by core services is not recommended.
+for the container registry. This includes Cassandra for metrics storage.
+Therefore, using NFS to back PVs used by core services is not recommended.
 
 Cassandra is designed to provide redundancy via multiple independent, instances.
 For this reason, using NFS or a SAN for data directories is an antipattern and
@@ -1619,9 +1618,8 @@ be deleted when the Elasticsearch pod terminates.
 [IMPORTANT]
 ====
 Testing shows issues with using the NFS server on RHEL as storage backend
-for the container registry. This includes the OpenShift Container Registry and Quay,
-Cassandra for metrics storage, and ElasticSearch for logging storage. Therefore,
-using NFS to back PVs used by core services is not recommended.
+for the container registry. This includes ElasticSearch for logging storage.
+Therefore, using NFS to back PVs used by core services is not recommended.
 
 Due to ElasticSearch not implementing a custom deletionPolicy, the use of NFS
 storage as a volume or a persistent volume is not supported for Elasticsearch

scaling_performance/optimizing_storage.adoc

@@ -71,7 +71,7 @@ The following table summarizes the recommended and configurable storage technolo
 .Recommended and configurable storage technology
 [options="header"]
 |===
-|Storage type |ROX footnoteref:[rox,ReadOnlyMany]|RWX footnoteref:[rwx,ReadWriteMany] |Registry|Scaled registry| Metrics|Logging|Apps
+|Storage type |ROX footnoteref:[rox,ReadOnlyMany]|RWX footnoteref:[rwx,ReadWriteMany] |Registry|Scaled registry|Metrics|Logging|Apps
 
 | Block
 | Yes footnoteref:[disk,This does not apply to physical disk, VM physical disk, VMDK, loopback over NFS, AWS EBS, and Azure Disk.]
@@ -87,8 +87,10 @@ The following table summarizes the recommended and configurable storage technolo
 | Yes
 | Configurable
 | Configurable
-| Configurable
-| Configurable
+| Configurable footnoteref:[metrics-warning,For metrics, it is an anti-pattern to use any shared storage and a single volume
+(RWX). By default, metrics deploys with one volume per Cassandra Replica.]
+| Configurable footnoteref:[logging-warning,For logging, using any shared
+storage would be an anti-pattern. One volume per logging-es is required.]
 | Recommended
 
 | Object
@@ -153,9 +155,8 @@ In an {product-title} hosted metrics cluster deployment:
 [IMPORTANT]
 ====
 Testing shows issues with using the NFS server on RHEL as storage backend for
-the container registry. This includes the OpenShift Container Registry and Quay, Cassandra
-for metrics storage, and ElasticSearch for logging storage. Therefore, using NFS
-to back PVs used by core services is not recommended.
+the container registry. This includes the Cassandra for metrics storage.
+Therefore, using NFS to back PVs used by core services is not recommended.
 
 Other NFS implementations on the marketplace might not have these issues.
 Contact the individual NFS implementation vendor for more information on any
@@ -173,9 +174,8 @@ In an {product-title} hosted logging cluster deployment:
 [IMPORTANT]
 ====
 Testing shows issues with using the NFS server on RHEL as storage backend for
-the container registry. This includes the OpenShift Container Registry and Quay, Cassandra
-for metrics storage, and ElasticSearch for logging storage. Therefore, using NFS
-to back PVs used by core services is not recommended.
+the container registry. This includes ElasticSearch for logging storage.
+Therefore, using NFS to back PVs used by core services is not recommended.
 
 Other NFS implementations on the marketplace might not have these issues.
 Contact the individual NFS implementation vendor for more information on any

scaling_performance/scaling_cluster_metrics.adoc

@@ -88,8 +88,9 @@ metrics data, if `USE_PERSISTENT_STORAGE=true` is set during the metrics set up
 process, `PV` will be on top in the network storage, with NFS as the default.
 However, using network storage in combination with Cassandra is not recommended.
 
-If you use a Cassandra database as a datastore for metrics data, see Cassandra
-documentation for their recommendations.
+If you use a Cassandra database as a datastore for metrics data, see the
+link:http://cassandra.apache.org/doc/latest/operating/hardware.html#disks[Cassandra
+documentation] for their recommendations.
 ====