Document URL: https://docs.openshift.com/enterprise/3.1/install_config/aggregate_logging.html

Section Number and Name: Pre-deployment (https://docs.openshift.com/enterprise/3.1/install_config/aggregate_logging.html#pre-deployment-configuration)

Describe the issue: 

The whole manual fails on several points by using vague and no guiding descriptions (such as saying "sufficient volumes for elasticsearch cluster storage) - what is sufficient? How would a user know?

The guide creates a projec which uses a --node-selector and has the following note:

"The selector in the example is optional. It can be used to specify a region or other selector you would like to use to restrict where the logging infrastructure deploys."

This does not significantly explain the purpose of the selector. The selector limits the nodes fluentd can use, ergo what nodes logging can be done on. The selector in other words, needs to select every node that will run pods which needs logging. Assuming a customer would understand at this point, that fluentd needs to run on every node that needs to aggregate logs is false.

Suggestions for improvement: 
Provide use cases for use of a selector. Ie. separate logging implementations, one for dev, one for prod etc. Or otherwise show why a selector would come in play. Otherwise, the default should be NOT to use a selector.

Additional information: 

The customer also needs to execute "oc project logging" after running the command. The following sections around service accounts and deployments needs to be tied to the namespace for logging.