vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you delete the PVC, PV, and the storage instance, the billing cycle stops depending on the billingType that you chose when you provisioned your storage and how you chose to delete the storage.



* When you manually cancel the persistent storage instance from the IBM Cloud console or the ibmcloud sl CLI, billing stops as follows:



* Hourly storage: Billing stops immediately. After your storage is canceled, you might still see your storage instance in the console for up to 72 hours.
* Monthly storage: You can choose between immediate cancellation or cancellation on the anniversary date. In both cases, you are billed until the end of the current billing cycle, and billing stops for the next billing cycle. After your storage is canceled, you might still see your storage instance in the console or the CLI for up to 72 hours.



* Immediate cancellation: Choose this option to immediately remove your storage. Neither you nor your users can use the storage anymore or recover the data.



* Anniversary date: Choose this option to cancel your storage on the next anniversary date. Your storage instances remain active until the next anniversary date and you can continue to use them until this date, such as to give your team time to make backups of your data.



* When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete and you choose to remove the PVC, the PV and the storage instance are immediately removed. For hourly billed storage, billing stops immediately. For monthly billed storage, you are still charged for the remainder of the month. After your storage is removed and billing stops, you might still see your storage instance in the console or the CLI for up to 72 hours.



What do I need to be aware of before I delete persistent storage?
: When you clean up persistent storage, you delete all the data that is stored in it. If you need a copy of the data, make a backup for [file storage](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_backup_restore) or [block storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_backup_restore).

I deleted my storage instance.
If you delete the PVC, PV, and the storage instance, the billing cycle stops depending on the billingType that you chose when you provisioned your storage and how you chose to delete the storage.



* When you manually cancel the persistent storage instance from the IBM Cloud console or the ibmcloud sl CLI, billing stops as follows:



* Hourly storage: Billing stops immediately. After your storage is canceled, you might still see your storage instance in the console for up to 72 hours.
* Monthly storage: You can choose between immediate cancellation or cancellation on the anniversary date. In both cases, you are billed until the end of the current billing cycle, and billing stops for the next billing cycle. After your storage is canceled, you might still see your storage instance in the console or the CLI for up to 72 hours.



* Immediate cancellation: Choose this option to immediately remove your storage. Neither you nor your users can use the storage anymore or recover the data.



* Anniversary date: Choose this option to cancel your storage on the next anniversary date. Your storage instances remain active until the next anniversary date and you can continue to use them until this date, such as to give your team time to make backups of your data.



* When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete and you choose to remove the PVC, the PV and the storage instance are immediately removed. For hourly billed storage, billing stops immediately. For monthly billed storage, you are still charged for the remainder of the month. After your storage is removed and billing stops, you might still see your storage instance in the console or the CLI for up to 72 hours.



What do I need to be aware of before I delete persistent storage?
: When you clean up persistent storage, you delete all the data that is stored in it. If you need a copy of the data, make a backup for [file storage](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_backup_restore) or [block storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_backup_restore).
The body of the request must contain an XML block with the following schema:



 Element Type Children Ancestor Constraint 

 RestoreRequest Container Days, GlacierJobParameters None None 
 Days Integer None RestoreRequest Specified the lifetime of the temporarily restored object. The minimum number of days that a restored copy of the object can exist is 1. After the restore period has elapsed, temporary copy of the object will be removed. 
 GlacierJobParameters String Tier RestoreRequest None 
 Tier String None GlacierJobParameters Optional, and if left blank will default to the value associated with the storage tier of the policy that was in place when the object was written. If this value is not left blank, it must be set to Bulk if the transition storage class for the bucket's lifecycle policy was set to GLACIER, and must be set to Accelerated if the transition storage class was set to ACCELERATED. 



<RestoreRequest>
<Days>{integer}</Days>
<GlacierJobParameters>
<Tier>Bulk</Tier>
</GlacierJobParameters>
</RestoreRequest>

Example request

POST /apiary/queenbee?restore HTTP/1.1
Authorization: {authorization-string}
Content-Type: text/plain
Content-MD5: rgRRGfd/OytcM7O5gIaQ==
Content-Length: 305
Host: s3.us.cloud-object-storage.appdomain.cloud

Example request

POST /apiary/queenbee?restore HTTP/1.1
Authorization: 'AWS4-HMAC-SHA256 Credential={access-key}/{date}/{region}/s3/aws4_request,SignedHeaders=host;x-amz-date;,Signature={signature}'
x-amz-date: {timestamp}
Content-MD5: rgRRGfd/OytcM7O5gIaQ==
Content-Length: 305
Host: s3.us.cloud-object-storage.appdomain.cloud

<RestoreRequest>
<Days>3</Days>
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Long-term retention policy NO NO NO NO 



[7]: Standard is used for active workloads. No charge incurs for data that is retrieved (other than the cost of the operational request itself and public outbound bandwidth).

[8]: Vault is used for cool workloads where data isn't accessed frequently, but a retrieval charge applies for reading data. The service includes a threshold for object size and storage period consistent with the intended use of this service for cooler, less-active data.

[9]: Cold Vault is used for cold workloads where data is primarily archived (accessed every 90 days or less) - a larger retrieval charge applies for reading data. The service includes a threshold for object size and storage period consistent with the intended use of this service: storing cold, inactive data.

[10]: Flex is used for dynamic workloads where access patterns are more difficult to predict.

Objects that are subject to a bucket's Immutable Object Storage retention policy will have expiration actions deferred until the retention policy is no longer enforced.





 Encrypt data with your own key 

By default, all objects that are stored in COS are encrypted by using randomly generated keys and an all-or-nothing-transform (AONT).
"pv":"pvc-d979977d-d79d-77d9-9d7d-d7d97ddd99d7"
: The PV that is associated with the storage instance.

"storageclass":"ibmc-file-gold"
: The type of storage class: bronze, silver, gold, or custom.
11. Remove the physical storage instance.

ibmcloud sl block volume-cancel <classic_block_id>
12. Verify that the physical storage instance is removed.



The deletion process might take up to 72 hours to complete.

ibmcloud sl block volume-list
In addition to the object_count field returned by the [Read Bucket Metadata API](https://cloud.ibm.com/apidocs/cos/cos-configuration), the API response body contains several new fields associated with versioning:



* noncurrent_object_count: Number of non-current object versions in the bucket in int64 format.
* noncurrent_bytes_used: Total size of all non-current object versions in the bucket in int64 format.
* delete_marker_count: Total number of delete markers in the bucket in int64 format.



As mentioned, versioning can only be enabled or suspended. If for any reason there is a desire to completely disable versioning, then it is necessary to migrate the contents of the bucket to a new bucket that does not have versioning enabled.





 Interactions 

The IBM COS implementation of the S3 APIs for versioning is identical to the AWS S3 APIs for versioning, with a few differences.



 Archiving and expiring versioned objects 

Lifecycle configurations are permitted in a version-enabled bucket. However, unlike Amazon S3, new versions are subject to the archive rule in the same manner as regular objects. Objects are given a transition date when they are created, and are archived on their individual transition date, regardless of whether they are current or non-current versions. Overwriting an object does not affect the transition date of the previous version, and the new (current) version will be assigned a transition date.

It is not possible to use NoncurrentVersionTransition rules to archive only non-current versions of objects in a lifecycle configuration.





 Immutable Object Storage (WORM) 

The IBM COS implementation of Immutable Object Storage (i.e. retention policies) is not permitted in buckets with versioning enabled. Attempts to create a retention policy will fail, as will attempts to enable versioning on a bucket with an retention policy. IBM COS does not support AWS S3 APIs for object locking, retention, or legal holds.







 Supported S3 APIs 

The following set of REST APIs can interact with versioning in some way:



* GET Object
* HEAD Object
* DELETE Object
Storage classes that don't have retain in the title have a reclaim policy of Delete. Example: ibmc-file-bronze.



 10 IOPs tier 

Name
: ibmc-vpc-block-10iops-tier
: ibmc-vpc-block-retain-10iops-tier
: ibmc-vpc-block-metro-10iops-tier
: ibmc-vpc-block-metro-retain-10iops-tier
: ibmc-vpcblock-odf-10iops
: ibmc-vpcblock-odf-ret-10iops

File system
: ext4

Corresponding Block Storage for VPC tier
: [10 IOPS/GB](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers)

Volume binding mode
: ibmc-vpc-block-10iops-tier: Immediate
: ibmc-vpc-block-retain-10iops-tier: Immediate
: ibmc-vpc-block-metro-10iops-tier: WaitForFirstConsumer
: ibmc-vpc-block-metro-retain-10iops-tier: WaitForFirstConsumer
: ibmc-vpcblock-odf-10iops: WaitForFirstConsumer
: ibmc-vpcblock-odf-ret-10iops: WaitForFirstConsumer

Reclaim policy
: ibmc-vpc-block-10iops-tier: Delete
: ibmc-vpc-block-retain-10iops-tier: Retain
: ibmc-vpc-block-metro-10iops-tier: Delete
: ibmc-vpc-block-metro-retain-10iops-tier: Retain
: ibmc-vpcblock-odf-10iops: Delete
: ibmc-vpcblock-odf-ret-10iops: Retain

Billing
: Hourly





 5 IOPs tier 

Name
: ibmc-block-retain-bronze: Retain





 Silver 

Name
: ibmc-block-silver
: ibmc-block-retain-silver

Type
: Endurance storage

File system
: ext4

IOPS per gigabyte
: 4

Size range in gigabytes
: 20-12000 Gi

Hard disk
: SSD

Reclaim policy
: ibmc-block-silver: Delete
: ibmc-block-retain-silver: Retain





 Gold 

Name
: ibmc-block-gold
: ibmc-block-retain-gold

Type
: Endurance storage

File system
: ext4

IOPS per gigabyte
: 10

Size range in gigabytes
: 20-4000 Gi

Hard disk
: SSD

Reclaim policy
: ibmc-block-gold: Delete
: ibmc-block-retain-gold: Retain





 Custom 

Name
: ibmc-block-custom
: ibmc-block-retain-custom

Type
: Performance File system
: ext4

IOPS and size
: Size range in gigabytes / IOPS range in multiples of 100



* 20-39 Gi / 100-1000 IOPS
* 40-79 Gi / 100-2000 IOPS
* 80-99 Gi / 100-4000 IOPS
* 100-499 Gi / 100-6000 IOPS
* 500-999 Gi / 100-10000 IOPS
* 1000-1999 Gi / 100-20000 IOPS
* 2000-2999 Gi / 200-40000 IOPS
* 3000-3999 Gi / 200-48000 IOPS
* 4000-7999 Gi / 300-48000 IOPS
* 8000-9999 Gi / 500-48000 IOPS
* 10000-12000 Gi / 1000-48000 IOPS



Hard disk
: The IOPS to gigabyte ratio determines the type of hard disk that is provisioned. To determine your IOPS to gigabyte ratio, you divide the IOPS by the size of your storage.
Yes, it is possible to configure buckets for automated [replication of objects to a destination bucket](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-replication-overview).





 How can I track events in Object Storage? 

The Object Storage Activity Tracker service records user-initiated activities that change the state of a service in Object Storage. For details, see [IBM Cloud Activity Tracker](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-at-events).





 How can I setup notifications when objects are updated or written to a bucket? 

Use [Cloud Functions for object storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-functions) to setup an Event Source (notification).





 Does Object Storage have rate limits when writing to or reading from buckets? 

Yes, Object Storage has rate limiting. For details, see [COS support](https://cloud.ibm.com/unifiedsupport/cases/form).





 Is Object Storage HIPAA compliant to host PHI data? 

Yes, Object Storage is HIPAA compliant.





 Is there any option in Object Storage to enable accelerate data transfer? 

Object Storage offers [Aspera](https://www.ibm.com/cloud/object-storage/aspera) service for high speed data transfer.





 How can I compare various attributes of an object in two different buckets? 

Use [Rclone](https://rclone.org/commands/rclone_check). It enables you to compare various attributes.





 What is the default retention period for buckets? 

There is no default retention period applied. You can set it while creating the bucket.





 Can we add a retention policy to an existing bucket? 

Yes, [Retention policies](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-immutableimmutable-sdk-add-policy) can be added to an existing bucket; however, the retention period can only be extended.
Only tagged images are analyzed and, if the images don't meet the criteria, they are deleted. If the option isn't specified, all tagged and untagged images are analyzed and, if the images don't meet the criteria, they are deleted.

--images
: Determines how many images to keep within each repository in the specified namespace. The newest images are retained. The age of images is determined by their build date. IMAGECOUNT is the number of images that you want to retain in each repository for the namespace.





 Example 

Retain the newest 20 images within each repository, in the namespace birds.

ibmcloud cr retention-run --images 20 birds

For more information about how to use the ibmcloud cr retention-run command, see [Retaining images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention).







 ibmcloud cr trash-list 

Displays all images in the trash in your IBM Cloud account. You can also see the number of remaining days until the image is removed from the trash. The number of remaining days until removal is rounded up. For example, if the time until removal is 2 hours, it shows as 1 day. Images remain in the trash for 30 days after they are deleted from your live repository.

If you want to restore an image from the trash, run the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/cli?topic=cli-containerregclibx_cr_image_restore) command, see [Restoring images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_restore).

ibmcloud cr trash-list [--restrict NAMESPACE] [--json]



 Prerequisites 

To find out about the required permissions, see [Access roles for using Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_using).





 Command options 

--restrict NAMESPACE
: (Optional) Limit the output to display only images in the specified namespace.
You are still charged for your storage instance. Also, if you deleted your cluster in an unhealthy state, the storage might still exist even if you chose to remove it.

How do I delete the storage when I want to keep my cluster?
: When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete, you can remove the PVC to start the deletion process of your persistent storage. Your PVC, PV, and storage instance are automatically removed.
: For storage that was [statically provisioned](https://cloud.ibm.com/docs/containers?topic=containers-kube_conceptsstatic_provisioning), VPC Block Storage, or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, you must manually remove the PVC, PV, and the storage instance to avoid further charges.

How does the billing stop after I delete my storage?
: Depending on what storage components you delete and when, the billing cycle might not stop immediately. If you delete the PVC and PV, but not the storage instance in your IBM Cloud account, that instance still exists and you are charged for it.

If you delete the PVC, PV, and the storage instance, the billing cycle stops depending on the billingType that you chose when you provisioned your storage and how you chose to delete the storage.



* When you manually cancel the persistent storage instance from the IBM Cloud console or the ibmcloud sl CLI, billing stops as follows:



* Hourly storage: Billing stops immediately. After your storage is canceled, you might still see your storage instance in the console for up to 72 hours.
* Monthly storage: You can choose between immediate cancellation or cancellation on the anniversary date. In both cases, you are billed until the end of the current billing cycle, and billing stops for the next billing cycle. After your storage is canceled, you might still see your storage instance in the console or the CLI for up to 72 hours.



* Immediate cancellation: Choose this option to immediately remove your storage. Neither you nor your users can use the storage anymore or recover the data.



* Anniversary date: Choose this option to cancel your storage on the next anniversary date.
For storage that was [statically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsstatic_provisioning), or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, the PVC and the PV are removed when you delete the cluster, but your storage instance and your data remain. You are still charged for your storage instance. Also, if you deleted your cluster in an unhealthy state, the storage might still exist even if you chose to remove it.

How do I delete the storage when I want to keep my cluster?
: When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete, you can remove the PVC to start the deletion process of your persistent storage. Your PVC, PV, and storage instance are automatically removed.
: For storage that was [statically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsstatic_provisioning), or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, you must manually remove the PVC, PV, and the storage instance to avoid further charges.

How does the billing stop after I delete my storage?
: Depending on what storage components you delete and when, the billing cycle might not stop immediately. If you delete the PVC and PV, but not the storage instance in your IBM Cloud account, that instance still exists and you are charged for it.

If you delete the PVC, PV, and the storage instance, the billing cycle stops depending on the billingType that you chose when you provisioned your storage and how you chose to delete the storage.



* When you manually cancel the persistent storage instance from the IBM Cloud console or the ibmcloud sl CLI, billing stops as follows:



* Hourly storage: Billing stops immediately. After your storage is canceled, you might still see your storage instance in the console for up to 72 hours.
* Monthly storage: You can choose between immediate cancellation or cancellation on the anniversary date.
: (Optional) Retain all untagged images when the retention policy is being processed. Only tagged images are analyzed and, if the images don't meet the criteria, they are deleted. If the option isn't specified, all tagged and untagged images are analyzed and, if the images don't meet the criteria, they are deleted.

--images
: Determines how many images to keep within each repository in the specified namespace. The newest images are retained. The age of images is determined by their build date. IMAGECOUNT is the number of images that you want to retain in each repository for the namespace. To return a policy to the default state that keeps all the images, set IMAGECOUNT to All.





 Examples 

Set a policy that retains the newest 20 images within each repository in the namespace birds.

ibmcloud cr retention-policy-set --images 20 birds

Set the policy back to the default state so that you keep all your images in the namespace birds.

ibmcloud cr retention-policy-set --images All birds

For more information about how to use the ibmcloud cr retention-policy-set command, see [Retaining images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention).







 ibmcloud cr retention-run 

Cleans up a namespace by retaining a specified number of images for each repository within a namespace in IBM Cloud Container Registry. All other images in the namespace are deleted.

You can choose whether to exclude all untagged images from the total number of images that you decide to retain.

Where an image, within a repository, is referenced by multiple tags, that image is counted only once. Newest images are retained. Age is determined by when the image was created, not when it was pushed to the registry.