vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud kp keys -c --instance-id 7mnxxxo8-91xx-23px-q4rs-xxtuv5w6xxx7

For this example, you'd see the following output:

Retrieving keys...

SUCCESS

Key ID                                 Key Name               CRN
ef1gxxxh-ijxx-234x-56k7-xxxxlmnoxxp8   test-key               crn:v1:bluemix:public:
kms:us-south:a/abxx1c2xxxx34x567xxdex891xxx23fx:xxx4g5xx-6789-x1h2-ixxx-3jkl4xxxx567:
key:ef1gxxxh-ijxx-234x-56k7-xxxxlmnoxxp8
cdex12ef-xxxg-3hxx-i456-7xxx8jk9xl12   vsi_encrypt_root_key   crn:v1:bluemix:public:
kms:us-south:a/abxx1c2xxxx34x567xxdex891xxx23fx:xxx4g5xx-6789-x1h2-ixxx-3jkl4xxxx567:
key:cdex12ef-xxxg-3hxx-i456-7xxx8jk9xl12
c12xxxx3-45d6-7efg-xxx8-9xxx12345x6h   vsi_encrypt_key        crn:v1:bluemix:public:
kms:us-south:a/abxx1c2xxxx34x567xxdex891xxx23fx:xxx4g5xx-6789-x1h2-ixxx-3jkl4xxxx567:
key:c12xxxx3-45d6-7efg-xxx8-9xxx12345x6h
[Verifying signatures and MACs](http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html_Toc416959747) C_VerifyRecoverInit No Initializes a verification operation where the data is recovered from the signature. 
 [Verifying signatures and MACs](http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html_Toc416959747) C_VerifyRecover No Verifies a signature on single-part data, where the data is recovered from the signature. 
 [Dual-purpose cryptographic functions](http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html_Toc416959748) C_DigestEncryptUpdate No Continues simultaneous multiple-part digesting and encryption operations. 
 [Dual-purpose cryptographic functions](http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html_Toc416959748) C_DecryptDigestUpdate No Continues simultaneous multiple-part decryption and digesting operations. 
 [Dual-purpose cryptographic functions](http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html_Toc416959748) C_SignEncryptUpdate No Continues simultaneous multiple-part signature and encryption operations.
Referencing specific keys in a secret --env-from-secret NAME:KEY_A,KEY_B where KEY_A,KEY_B are the keys of a key-value pair. If you want to use a different name for a referenced key, use the format NAME:MY_KEY_A=KEY_A,MY_KEY_B=KEY_B. [job create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-create), [job update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-update), [jobrun submit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-submit), [jobrun resubmit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-resubmit) [app create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create), [app update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-update) 
 Referencing specific keys in a configmap --env-from-configmap NAME:KEY_A,KEY_B where KEY_A,KEY_B are the keys of a key-value pair.
Osaka (osa21, osa22, osa23) 166.9.70.6, 166.9.70.8, 166.9.71.8, 166.9.71.10, 166.9.72.9, 166.9.72.10, 166.9.247.41, 166.9.247.75, 166.9.247.107 
 UK South (lon02,lon04, lon05, lon06) 166.9.34.17, 166.9.34.41, 166.9.34.45, 166.9.34.5, 166.9.34.50, 166.9.34.6, 166.9.34.77, 166.9.36.10, 166.9.36.11, 166.9.36.12, 166.9.36.13, 166.9.36.23, 166.9.36.30, 166.9.36.53, 166.9.36.65, 166.9.36.95, 166.9.38.18, 166.9.38.28, 166.9.38.46, 166.9.38.54, 166.9.38.6, 166.9.38.7, 166.9.38.75, 166.9.244.12, 166.9.244.48, 166.9.244.75
Storage class reference 

Review the following ODF storage classes.

The ODF storage classes all support dynamic provisioning and are multizone capable.

ocs-storagecluster-cephfs

ocs-storagecluster-ceph-rbd

ocs-storagecluster-ceph-rbd-encyrpted



Ceph FS storage class details.
The first column contains a feature of the storage class. The second column contains a brief description of the feature.

 Feature           Description 

 Supported access  rwx         
 Volume mode       File        
 Performance       High        
 Consistency       Strong      
 Resiliency        High        
 Scalability       Multizone   
 Encryption        At rest
JP-OSA 163.68.67.128/28 <br>163.68.67.96/29 <br>163.68.79.32/27 <br>163.69.66.168/29 <br>163.69.67.112/28 <br>163.69.70.64/27 <br>163.73.67.176/29 <br>163.73.67.192/28 <br>163.73.69.96/27 
 JP-TOK 128.168.75.32/28 <br>128.168.75.8/29 <br>128.168.98.0/27 <br>161.202.255.64/27 <br>165.192.84.8/29 <br>165.192.97.96/27 <br>169.56.11.208/28 <br>169.56.51.232/29 
 US-EAST 169.47.20.160/27 <br>169.55.109.112/29 <br>169.55.122.192/28 <br>169.59.131.160/27 <br>169.59.146.192/26 <br>169.60.112.72/29 <br>169.60.82.240/28 <br>169.62.28.160/28 <br>169.62.3.80/29 <br>169.62.46.192/27 <br>52.116.95.64/26 <br>52.117.71.128/26 
 AU-SYD 130.198.66.144/28 <br>130.198.80.152/29 <br>135.90.73.96/29 <br>135.90.78.192/28 <br>135.90.94.96/27 <br>168.1.115.192/27 <br>168.1.213.32/27 <br>168.1.213.72/29 <br>168.1.41.96/28
"lease_duration": 0,
"data": {
"algorithm": "RSA",
"common_name": "example.com",
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2021-06-03T20:50:11Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0:secret:be4a0846-4cb5-3bfa-bab5-10a44dfc3e85",
"description": "Extended description for my secret.",
"expiration_date": "2021-06-04T15:25:44Z",
"id": "be4a0846-4cb5-3bfa-bab5-10a44dfc3e85",
"intermediate_included": false,
"issuer": "US Texas Austin Example Corp. Example Org example.com",
"key_algorithm": "SHA256-RSA",
"labels": [
"dev",
"us-south"
],
"last_update_date": "2021-06-03T20:50:11Z",
"name": "test-imported-certificate-in-group",
"private_key_included": true,
"secret_group_id": "339c026a-ac0f-1ea1-3d43-99adf871b49a",
"secret_type": "imported_cert",
"serial_number": "fc:22:29:7e:57:25:8a:05",
You can display logs of all the instances of a job run or display logs of a specific instance of a job run. In this example, display the logs of the writerjob1 job run. Notice in the output that the username and password keys of the full secret mydatabasesec are displayed. Secret values are added to the environment decoded.

ibmcloud ce jobrun logs --jobrun writerjob1

Example output

Getting jobrun 'writerjob1'...
Getting instances of jobrun 'writerjob1'...
Getting logs for all instances of job run 'writerjob1'...
OK
[...]

certificate=-----BEGIN CERTIFICATE--------
asdf;aksjdflkajsdflkjasldkfjalskdjflaksjdflk
-----END CERTFICIATE----------
password=abcd
username=reader
[...]
5. Create the mydatabasesec-writer secret and specify the key-value pairs for a username and password by using the --from-literal option.

ibmcloud ce secret create --name mydatabasesec-writer --from-literal username=writer --from-literal password=wxyz
6. View details about the mydatabasesec-writer secret by using the secret get command. The values for the password and username keys of the secret are encoded.

ibmcloud ce secret get -n mydatabasesec-writer

Example output

Getting generic secret 'mydatabasesec-writer'...
OK

Name: mydatabasesec-writer
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 14s
3b4b0511-00df-48e6-ad65-fad35bb6ce17 my-test-key-13

3d683d56-d340-40cb-b8b6-605dcfded01f my-test-key-15
3ee0d859-2968-4444-8e4d-3d28614f055c my-test-key-10
54dd2745-7718-487f-85e6-a67e758dd945 my-test-key-17
62090ba8-7363-408e-9edc-aa9fb69c09be my-test-key-12
768c9ceb-368b-46f7-9b1d-be211e036fe1 my-test-key-4

87679194-52d0-42af-81e1-bffd64f87315 my-test-key-7
90138be5-1dd1-4eea-b7c1-73cc8609e7f7 my-test-key-19
b70f62a1-4d52-4526-91a9-ce47bf14c2a5 my-test-key-1
b8794334-eea6-4c0d-8fe1-8086300b13f7 my-test-key-6
bc459a2f-56cb-445e-b4ee-9d1866b57560 my-test-key-11

cc7faf46-43cf-43b2-be98-7d1815371639 my-test-key-8
cf0a3d8b-4856-4aa5-be6a-88cca465eab0 my-test-key-20
df530c55-39c0-44e8-b7db-397593f70d90 my-test-key-3
Further details on these changes are in the Elastic documentation on the [removal of mapping types](https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html).







 Retrieve and update user passwords 



 Retrieve Elasticsearch user passwords 

A restore to Elasticsearch 7.17 invalidates existing user passwords. Existing user passwords must be reset after the restore. Follow this procedure to list all users and change user passwords.

First, run the [ibmcloud plug-in update](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_settingsibmcloud_plugin_update) command:

ibmcloud plugin update cloud-databases

Then, log in to your IBM Cloud® account:

ibmcloud login -a cloud.ibm.com -r <region> --sso

Next, run the user-list command with the --help flag. This command outputs various options for your account's user list.

ibmcloud cloud-databases es user-list --help

The user-list command output looks like:

ibmcloud cloud-databases es user-list --help
NAME:
user-list, ul - List all users from the database internal credential store.

USAGE:
ibmcloud cdb elasticsearch user-list (NAME|ID) (ADMIN_PASSWORD) [--json] [-c DIRECTORY] [--api-version]

OPTIONS:
--json, -j --json, -j Results as JSON.
--certroot, -c --certroot value, -c value Certificate Root. (default: "< >") [$CERTROOT]
--api-version, -v --api-version value, -v value API Version used for request.

Before running the command to update user passwords, ensure that you have updated the admin password.
the Signature=[A3:48:B6:1F:63:07:00:38:7F:A4:9E:98:81:CE:78:18:31:B1:EE:3E:45:81:7C:5F:18:C1:4D:1E:C8:A9:FD:95:94:B6:0F:CB:97:8D:A8:F1:E0:BB:AB:9A:51:82:86:7D:CB:71:60:47:FD:D9:D1:B5:26:81:69:C9:CD:84:5D:0C]
the SHA256 fingerprint=[75:90:01:22:B4:C7:75:71:4B:F1:26:97:4D:D9:53:2D:04:A4:4F:F4:96:D5:ED:BD:17:C1:8B:69:2C:2A:38:5A]
-------------------------------------------------------------------
Confirm to connect to the server? [y/N]> y

OK

Continue connecting to the server...

Configuring the public key of the admin...

The new generated key pair:
+-------------------------------------------------------------+------------+---------------------------------------------------------+
Vk1CTUdBMVVFQ2hNTVJHbG5hVU5sY25RZ1NXNWpNUmt3RndZRFZRUUxFeEIzDQpkM2N1WkdsbmFX
VEFlRncweE16QXpNRGd4TWpBd01EQmFGdzB5TXpBek1EZ3hNakF3TURCYU1FMHhDekFKQmdOVkJB
WVRBbFZUDQpNUlV3RXdZRFZRUUtFd3hFYVdkcFEyVnlkQ0JKYm1NeEp6QWxCZ05WQkFNVEhrUnBa
For example: export FLAG=$(if "$(uname -s)" == "Linux" ] ! ! ; then echo "-w 0"; else echo "-b 0"; fi)
cat $HOME/fabric-ca-client/peer-admin/msp/signcerts/cert.pem | base64 $FLAG
This command prints a string that is similar to the following example: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUNuRENDQWtPZ0F3SUJBZ0lVTXF5VDhUdnlwY3lYR2sxNXRRY3hxa1RpTG9Nd0NnWUlLb1pJemowRUF3SXcKYURFTTlEKaFhTTzRTWjJ2ZHBPL1NQZWtSRUNJQ3hjUmZVSWlkWHFYWGswUGN1OHF2aCtWSkhGeHBLUnQ3dStHZDMzalNSLwotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==
Copy this string to the "admincerts" field under the component section in the configuration file.<-- </section "id="section-provide-the-signcert-of-your-organization-administrator" "> --><-- <section "id="section-csr" "> --> CSR (Certificate Signing Request) hosts You have the option of providing a custom domain to your component by using the "csr" section of the components file. "csr": {
"hosts": ""] ! !
}
This section is provided for advanced users to specify a custom hostname that can be used to communicate with the peer.
now().plusHours(1) ?>."
}
],
"response_type": "text",
"selection_policy": "sequential"
}
]
}
}

Result if it is 8 AM: One hour from now is 09:00:00.

To get the time 30 minutes ago, specify the following expression:

{
"output": {
"generic": [
{
"values":
{
"text": "A half hour before @sys-time is <? @sys-time.minusMinutes(30) ?>."
}
],
"response_type": "text",
"selection_policy": "sequential"
}
]
}
}

Result if the time captured by the @sys-time entity is 8 AM: A half hour before 08:00:00 is 07:30:00.

To reformat the time that is returned, you can use the following expression:

{
"output": {
"generic": [
{
"values":
{
"text": "6 hours ago was <? now().minusHours(6).reformatDateTime('h:mm a') ?>."
}
],
"response_type": "text",
"selection_policy": "sequential"
}
]
}
}

Result if it is 2:19 PM: 6 hours ago was 8:19 AM.



 Working with time spans 

To show a response based on whether today's date falls within a certain time frame, you can use a combination of time-related methods. For example, if you run a special offer during the holiday season every year, you can check whether today's date falls between November 25 and December 24 of this year. First, define the dates of interest as context variables.
<time>.plusSeconds(n) Returns the time n secons after the specified time. 



where <time> is specified in the format HH:mm:ss.

To get the time an hour from now, specify the following expression:

{
"output": {
"generic": [
{
"values":
{
"text": "One hour from now is <? now().plusHours(1) ?>."
}
],
"response_type": "text",
"selection_policy": "sequential"
}
]
}
}

Result if it is 8 AM: One hour from now is 09:00:00.

To get the time 30 minutes ago, specify the following expression:

{
"output": {
"generic": [
{
"values":
{
"text": "A half hour before @sys-time is <? @sys-time.minusMinutes(30) ?>."
}
],
"response_type": "text",
"selection_policy": "sequential"
}
]
}
}

Result if the time captured by the @sys-time entity is 8 AM: A half hour before 08:00:00 is 07:30:00.

To reformat the time that is returned, you can use the following expression:

{
"output": {
"generic": [
{
"values":
{
"text": "6 hours ago was <? now().minusHours(6).reformatDateTime('h:mm a') ?>."
}
],
"response_type": "text",
"selection_policy": "sequential"
}
]
}
}

Result if it is 2:19 PM: 6 hours ago was 8:19 AM.



 Working with time spans
Replace <reclamation_ID> with the value that you retrieved in the previous step.







 Restoring a deleted service instance 

If you haven't permanently deleted your instance, you can restore it during the 7-day reclamation period.



1. View which service instances are available for restoration.

ibmcloud resource reclamations

From the list of available instances, copy the reclamation ID of the Secrets Manager instance that you want to restore.
2. Restore the reclamation.

ibmcloud resource reclamation-restore <reclamation_ID>

Replace <reclamation_ID> with the value that you retrieved in the previous step.
(7 * (2460601000L))).format('yyyy-MM-dd') ?>"
}
}

After reformatting the date, the result is 2018-01-26. Now, you can use an expression like @sys-date.after($week_from_today) in a response condition to compare a date specified in user input to the date saved in the context variable.

The following expression calculates the time 3 hours from now.

{
"context": {
"future_time": "<? new Date(new Date().getTime() + (3 * (60601000L)) -
(5 * (60601000L))).format('h:mm a') ?>"
}
}

The (60601000L) value represents an hour in milliseconds. This expression adds 3 hours to the current time. It then recalculates the time from a UTC time zone to EST time zone by subtracting 5 hours from it. It also reformats the date values to include hours and minutes AM or PM.







 Numbers 

These methods help you get and reformat number values.

For information about system entities that can recognize and extract numbers from user input, see [@sys-number entity](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-system-entitiessystem-entities-sys-number).

If you want the service to recognize specific number formats in user input, such as order number references, consider creating a pattern entity to capture it. See [Creating entities](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-entities) for more details.

If you want to change the decimal placement for a number, to reformat a number as a currency value, for example, see the [String format() method](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-methodsjava.lang.String).



 toDouble()
The speaker might be reading a six-digit number from an identification card, for example, and pause to confirm the number.

The first example uses the default pause interval of 0.8 seconds:

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/wav" --data-binary @{path}audio-file.wav "{url}/v1/recognize"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: audio/wav" --data-binary @{path}audio-file.wav "{url}/v1/recognize"

Because the pause is greater than the default interval, the service splits the transcript at the pause. The confidence of both results is 0.99, so transcription accuracy is very good despite the pause.

{
"result_index": 0,
"results": [
{
"alternatives":
{
"confidence": 0.99,
"transcript": "one two three "
}
],
"final": true
},
{
"alternatives":
{
"confidence": 0.99,
"transcript": "four five six "
}
],
"final": true
}
]
}
Show more

But suppose speech recognition is performed with a grammar that expects the user to speak six digits in a single-phrase response. Because the service splits the transcript at the one-second pause, the results are empty. The grammar is applied to each final result, but neither result, "one two three" nor "four five six", contains six digits.

The second example uses the same audio but sets the end_of_phrase_silence_time to 1.5 seconds:

IBM Cloud
The {timeframe} units can be hour, minute, or second.



The following table illustrates the information that each attribute captures from the user input.



@sys-time attributes

 Attribute Type Example 

 @sys-time string For the input 6:30 PM, returns 18:30:00. 
 @sys-time.alternatives array If a user says The meeting is at 5, the system calculates the time as 5:00:00 or 5 AM and saves that as the @sys-time. However, the user might have meant 17:00:00 or 5 PM. The system also saves the later time as an alternative time value. If the user enters The meeting is at 5pm, then @sys-time is set to 17:00:00, and no alternative value is created because there is no AM and PM confusion. 
 @sys-time.calendar_type string For any time mention, returns GREGORIAN. 
 @sys-time.granularity string If the input is now, returns instant. For 3 o'clock or noon, returns hour. For 17:00:00, returns second. 
 @sys-time.hour number If the input contains 5:30:10 PM, it returns17 to represent 5 PM. 
 @sys-time.literal string For the input, The store closes at 8PM, returns at 8PM. 
 @sys-time.location array For the input, The store closes at 8PM, returns [17, 23]. 
 @sys-time.minute number If the input mentions the time 5:30:10 PM, returns 30. If no minutes are specified, then this helper returns 0. 
 @sys-time.part_of_day string If the input is this morning, returns two @sys-time values, 6:00:00 and 12:00:00. Also returns a range_link object with time-from and time-to role types. 
 @sys-time.range_link string For the input Are you open from 9AM to 11AM, two @sys-time entities are detected. Each @sys-time entity that is detected has a range_link property in its output.
The {timeframe} units can be hour, minute, or second.



The following table illustrates the information that each attribute captures from the user input.



@sys-time attributes

 Attribute Type Example 

 @sys-time string For the input 6:30 PM, returns 18:30:00. 
 @sys-time.alternatives array If a user says The meeting is at 5, the system calculates the time as 5:00:00 or 5 AM and saves that as the @sys-time. However, the user might have meant 17:00:00 or 5 PM. The system also saves the later time as an alternative time value. If the user enters The meeting is at 5pm, then @sys-time is set to 17:00:00, and no alternative value is created because there is no AM and PM confusion. 
 @sys-time.calendar_type string For any time mention, returns GREGORIAN. 
 @sys-time.granularity string If the input is now, returns instant. For 3 o'clock or noon, returns hour. For 17:00:00, returns second. 
 @sys-time.hour number If the input contains 5:30:10 PM, it returns17 to represent 5 PM. 
 @sys-time.literal string For the input, The store closes at 8PM, returns at 8PM. 
 @sys-time.location array For the input, The store closes at 8PM, returns [17, 23]. 
 @sys-time.minute number If the input mentions the time 5:30:10 PM, returns 30. If no minutes are specified, then this helper returns 0. 
 @sys-time.part_of_day string If the input is this morning, returns two @sys-time values, 6:00:00 and 12:00:00. Also returns a range_link object with time-from and time-to role types. 
 @sys-time.range_link string For the input Are you open from 9AM to 11AM, two @sys-time entities are detected. Each @sys-time entity that is detected has a range_link object in its output.
Re-creating custom models, especially custom acoustic models, from saved data can take a significant amount of time. Maintaining parallel service configurations in multiple locations can eliminate the turnaround time associated with disaster recovery.



 Disaster recovery for custom language models 

For custom language models, you need to maintain and be prepared to re-create and restore your custom language models and their corpora, grammars, and custom words. You also need to be prepared to retrain your custom language models on their data and words resources.



 Backing up custom language models 

Preserve the following information about your custom language models:



* A list of all of your custom language models and their definitions. To list information about your custom models:



* Use the GET /v1/customizations method to list information about all custom models.
* Use the GET /v1/customizations/{customization_id} method to list information about a specified custom model.



For more information, see [Listing custom language models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-manageLanguageModelslistModels-language).
* Copies of all corpus text files that you add to your custom language models. To list information about the corpora for your custom models:



* Use the GET /v1/customizations/{customization_id}/corpora method to list all corpora for a custom model.
* Use the GET /v1/customizations/{customization_id}/corpora/{corpus_name} method to list information about a specified corpus for a custom model.



For more information, see [Listing corpora for a custom language model](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-manageCorporalistCorpora).
* Copies of all grammar files that you add to your custom language models. To list information about the grammars for your custom models:



* Use the GET /v1/customizations/{customization_id}/grammars method to list information about all grammars for a custom model.
rook-ceph-rgw-ocs-storagecluster-cephobjectstore-a-7f7f6df9rv6h 1/1 Running 0 3m44s
rook-ceph-rgw-ocs-storagecluster-cephobjectstore-b-554fd9dz6dm8 1/1 Running 0 3m41s



4. List the ODF storage classes.

oc get sc

Example output

NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
localblock kubernetes.io/no-provisioner Delete WaitForFirstConsumer false 107s
localfile kubernetes.io/no-provisioner Delete WaitForFirstConsumer false 107s
ocs-storagecluster-ceph-rbd openshift-storage.rbd.csi.ceph.com Delete Immediate true 87s
ocs-storagecluster-ceph-rgw openshift-storage.ceph.rook.io/bucket Delete Immediate false 87s
ocs-storagecluster-cephfs openshift-storage.cephfs.csi.ceph.com Delete Immediate true 88s
sat-ocs-cephfs-gold openshift-storage.cephfs.csi.ceph.com Delete Immediate true 2m46s
sat-ocs-cephrbd-gold openshift-storage.rbd.csi.ceph.com Delete Immediate true 2m46s
sat-ocs-cephrgw-gold openshift-storage.ceph.rook.io/bucket Delete Immediate false 2m45s
sat-ocs-noobaa-gold openshift-storage.noobaa.io/obc Delete Immediate false 2m45s
5. List the persistent volumes and verify that your MON and OSD volumes are created.

oc get pv

Example output

NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE