E.4. Verifying if Gluster Block is Setup as Backend

Execute the following commands to verify if gluster block is setup as the backend for loging and metrics:

To get an overiew of the infrastructure, execute the following command:

oc get pods -n logging -o jsonpath='{range .items[*].status.containerStatuses[*]}{"Name: "}{.name}{"\n  "}{"Image: "}{.image}{"\n"}{"  State: "}{.state}{"\n"}{end}'

# oc get pods -n logging -o jsonpath='{range .items[*].status.containerStatuses[*]}{"Name: "}{.name}{"\n  "}{"Image: "}{.image}{"\n"}{"  State: "}{.state}{"\n"}{end}'

Copy to Clipboard

Toggle word wrap

To get the details of all the persistent volume claims, execute the following command:
```
oc get pvc
```
```
# oc get pvc
```
Copy to Clipboard Toggle word wrap
To get the details of the pvc, execute the following command:
```
oc describe pvc <claim_name>
```
```
# oc describe pvc <claim_name>
```
Copy to Clipboard Toggle word wrap
Verify the volume is mountable and that permissions allow read/write. Also, PVC claim name should match the dynamically provisioned gluster block storage class.
For more information refer, https://access.redhat.com/documentation/en-us/openshift_container_platform/3.6/html/installation_and_configuration/install-config-aggregate-logging-sizing.

Voltar ao topo

Este conteúdo não está disponível no idioma selecionado.

E.4. Verifying if Gluster Block is Setup as Backend

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Tornando o open source mais inclusivo

Sobre a Red Hat

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links