E.2. Enabling Gluster Block Storage as Backend for Logging
Follow the tasks mentioned below to enable Gluster Block Storage as backend for logging:
- To enable logging in Openshift Container platform, see https://access.redhat.com/documentation/en-us/openshift_container_platform/3.6/html-single/installation_and_configuration/#install-config-aggregate-logging
- The
openshift_logging_es_pvc_dynamicansible variable has to be set to true.[OSEv3:vars] openshift_logging_es_pvc_dynamic=true
For example, a sample set of variables for openshift_logging_ are listed below.openshift_logging_es_pvc_dynamic=true openshift_logging_es_pvc_size=5G openshift_logging_es_cluster_size=3 openshift_logging_es_memory_limit=4G openshift_logging_es_number_of_replicas=2 openshift_logging_es_nodeselector={'region' : 'infra'} openshift_logging_curator_nodeselector={'region' : 'infra'} openshift_logging_kibana_nodeselector={'region' : 'infra'} - Run the Ansible playbook. For more information, see .https://access.redhat.com/documentation/en-us/openshift_container_platform/3.6/html-single/installation_and_configuration/#install-config-aggregate-logging
- To verify, execute the following command:
# oc get pods -n openshift-logging
Note
For more information regarding logging storage considerations, see https://access.redhat.com/documentation/en-us/openshift_container_platform/3.6/html-single/installation_and_configuration/#install-config-aggregate-logging-sizing-guidelines-storage.
