anchor.diff:  
   [IMPORTANT]
   ====
  -These solutions are a work in progress. As packaging improvements are made these
  -instructions will be simplified.
  -====
  +These solutions are a work in progress. As packaging improvements are made,
  +these instructions will be simplified.
  +====
  +endif::[]
  +ifdef::openshift-enterprise[]
  +As an OpenShift administrator, you may want to view the logs from all containers
  +in one user interface. The currently supported method for aggregating container
  +logs in OpenShift Enterprise is link:#using-a-centralized-file-system[using a
  +centralized file system]. Additional supported methods are planned for inclusion
  +in future releases.
  +
  +[NOTE]
  +====
  +As packaging improvements are made, these instructions will be simplified.
  +====
  +endif::[]
   
   [[using-a-centralized-file-system]]
   
   == Using a Centralized File System
   
  -This option reads all container logs and forwards them to a central server for
  -storage on the file system. This solution requires less resources and requires
  -less management than the link:#using-elasticsearch[*Elasticsearch* option], but
  -the logs are not indexed and searchable.
  +This method reads all container logs and forwards them to a central server for
  +storage on the file system.
  +ifdef::openshift-origin[]
  +This solution requires less resources and requires less management than the
  +link:#using-elasticsearch[*Elasticsearch* option], but the logs are not indexed
  +and searchable.
  +endif::[]
   
   [[installing-fluentd-td-agent-on-nodes]]
   === Installing fluentd (td-agent) on Nodes
  
positive.code: 
  . link:#creating-an-elasticsearch-cluster[Creating an *Elasticsearch* cluster]
  . link:#creating-logging-pods[Creating logging pods]
  . link:#creating-the-kibana-search[Creating the *Kibana* service]
  
  [[creating-an-elasticsearch-cluster]]
  
  
negative.code: 
  == Overview
  
  ifdef::openshift-origin[]
  As an OpenShift administrator, you may want to view the logs from all containers
  in one user interface. There are two options for aggregating container logs,
  depending on user requirements:
  