7.4. Verifying if Gluster Block is Setup as Backend

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

To get an overview 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, see https://access.redhat.com/documentation/en-us/openshift_container_platform/3.10/html-single/configuring_clusters/#install-config-aggregate-logging-sizing.

Torna in cima

Questo contenuto non è disponibile nella lingua selezionata.

7.4. Verifying if Gluster Block is Setup as Backend

Formazione

Prova, acquista e vendi

Community

Informazioni sulla documentazione di Red Hat

Rendiamo l’open source più inclusivo

Informazioni su Red Hat

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links