+++ This bug was initially created as a clone of Bug #1519709 +++

+++ This bug was initially created as a clone of Bug #1519706 +++

**********************************************************************
Description of problem:
When ops is enabled, there is still a .operations index in non-ops kibana, when we click the .operations index, the kibana was tring to search records. that is wrong. We should use ops kibana to view operation logs.  the .operations index should be deleted in non-ops elasticsearch and kibana

Version-Release number of selected component (if applicable):
logging-elasticsearch/images/v3.6.173.0.63-12
logging-elasticsearch/images/v3.6.173.0.63-12
logging-auth-proxy/images/v3.6.173.0.63-11
logging-fluentd/images/v3.6.173.0.63-11

How reproducible:
always

Steps to Reproduce:
1.  Deploy logging and enable ops elasticsearch

openshift_logging_install_logging=true
openshift_logging_image_prefix=registry.example.com/openshift3/
openshift_logging_namespace=logging
openshift_logging_es_cluster_size=1
openshift_logging_es_memory_limit=1Gi

openshift_logging_use_ops=true
openshift_logging_es_ops_memory_limit=1Gi
openshift_logging_es_ops_cluster_size=1


openshift_logging_use_mux=true
openshift_logging_use_mux_client=true




2. cluster-admin search records in non-ops kibana

Actual results:
There is a .operations index.

Expected results:
There isn't .operations index.


Additional info:
**********************************************************************