vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Content-MD5 String Required: The base64 encoded 128-bit MD5 hash of the payload, which is used as an integrity check to ensure that the payload wasn't altered in transit. 



The body of the request must contain an XML block with the following schema:



 Element Type Children Ancestor Constraint 

 ObjectLockConfiguration Container ObjectLockEnabled, Rule None Limit 1. 
 ObjectLockEnabled String None ObjectLockConfiguration The only valid value is ENABLED. 
 Rule Container DefaultRetention ObjectLockConfiguration Limit 1 
 DefaultRetention Container Days, Mode, Years Rule Limit 1. 
 Days Integer None DefaultRetention The number of days that you want to specify for the default retention period. Cannot be combined with Years. 
 Mode String None DefaultRetention Only COMPLIANCE is supported at this time. 
 Years Integer None DefaultRetention The number of years that you want to specify for the default retention period. Cannot be combined with Days. 



Example request

This request lists the objects inside the "apiary" bucket.

GET /apiary HTTP/1.1
Content-Type: text/plain
Host: s3.us.cloud-object-storage.appdomain.cloud
Authorization: Bearer {token}

Example response

HTTP/1.1 200 OK
Date: Wed, 24 Aug 2016 17:36:24 GMT
X-Clv-Request-Id: 9f39ff2e-55d1-461b-a6f1-2d0b75138861
Accept-Ranges: bytes
Server: Cleversafe/3.9.0.115
X-Clv-S3-Version: 2.5
x-amz-request-id: 9f39ff2e-55d1-461b-a6f1-2d0b75138861
Content-Type: application/xml
Content-Length: 909

<ObjectLockConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<ObjectLockEnabled>ENABLED</ObjectLockEnabled>
<Rule>
ibmc-vpc-block-metro-retain-custom Custom Custom Based on IOPS SSD Retain WaitForFirstConsumer 
 ibmc-vpc-block-metro-retain-general-purpose 3 3 10 GiB - 16 TB SSD Retain WaitForFirstConsumer 







 VMware Storage CSI Driver 

Review the Satellite storage classes for VMware storage. You can describe storage classes in the command line with the oc describe sc <storage-class-name> command.



Table 16. Storage class reference for VMware storage

 Storage class name Default Read IOPS per GB Default Write IOPS per GB Size range (per disk) Hard disk Reclaim policy Volume Binding Mode 

 sat-vsphere-vsan-block-metroDefault XX XX XX GB - XX TB XXX Delete WaitForFirstConsumer 
 sat-vsphere-vsan-block X X XX GB - XXX GB XXX Delete Immediate
* The [ibmcloud cr retention-policy-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_policy_list) command lists the image retention policies for your account.



For more information, see [Retaining images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention).

You can restore deleted images from the trash
: All deleted images are stored in the trash for 30 days.

The following commands are available for you to use to restore images:



* The [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command displays all images in the trash in your IBM Cloud account. Images remain in the trash for 30 days after deletion.
* The [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command restores a deleted image from the trash.



For more information, see [Listing images in the trash](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_list_trash) and [Restoring images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_restore).





 1 August 2019 

ibmcloud cr retention-run command is available
: The ibmcloud cr retention-run command cleans up your namespaces by retaining images for each repository within a namespace in Container Registry by applying specified criteria. All other images in the namespace are deleted.

For more information, see [ibmcloud cr retention-run](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_run) and [Retaining images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention).





 25 July 2019 

IBM Cloud Activity Tracker available for Container Registry
* If you want the PV, the data, and your physical Block Storage for VPC device to be deleted when you delete the PVC, choose a storage class without retain.





4. Create a configuration file to define your persistent volume claim and save the configuration as a YAML file.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: <pvc_name> Enter a name for your PVC.
spec:
accessModes:
- ReadWriteOnce ReadWriteOnce is the only supported access mode. You can mount the PVC to one pod on one worker node in the cluster at a time.
resources:
requests:
storage: 10Gi Enter the size. Make sure that the size is supported in the profile that you chose.
storageClassName: <storage_class> Enter the storage class name that you selected earlier.
5. Create the PVC in your cluster.

oc apply -f pvc.yaml
6. Verify that your PVC is created and bound to the PV. This process can take a few minutes.

oc describe pvc <pvc_name>

Example output

Name: mypvv
Namespace: default
StorageClass: ibmc-vpc-block-5iops-tier
Status: Bound
Volume:
Labels: <none>
Annotations: oc.kubernetes.io/last-applied-configuration: {"apiVersion":"v1","kind":"PersistentVolumeClaim","metadata":{"annotations":{},"name":"csi-block-pvc-good","namespace":"default"},"spec":{...
volume.beta.kubernetes.io/storage-provisioner: vpc.block.csi.ibm.io
Finalizers: [kubernetes.io/pvc-protection]
Capacity: 10Gi
Access Modes:
VolumeMode: Filesystem
Events:
Type Reason Age From Message
A successful request returns a 200 response.

In the event that the RetainUntilDate values is not beyond any existing value, the operation will fail with a 403 Access Denied.





 Add or remove a legal hold for an object 

The Object Lock configuration is provided as XML in the body of the request. New requests will overwrite any existing replication rules that are present on the object, provided the RetainUntilDate is farther in the future than the current value.



 Header Type Description 

 Content-MD5 String Required: The base64 encoded 128-bit MD5 hash of the payload, which is used as an integrity check to ensure that the payload wasn't altered in transit. 



The body of the request must contain an XML block with the following schema:



 Element Type Children Ancestor Constraint 

 LegalHold Container Status None Limit 1. 
 Status String None LegalHold Supported values are ON or OFF (case-sensitive) 



This example will retain any new objects for at least until March 12, 2023.

curl -X "PUT" "https://$BUCKET.s3.$REGION.cloud-object-storage.appdomain.cloud/?legalHold&versionId=$VERSION_ID" 
-H 'Authorization: Bearer $TOKEN' 
-H 'Content-MD5: FMh6GxizXUBRaiDuB0vtgQ==' 
-H 'Content-Type: text/plain; charset=utf-8' 
-d $'<LegalHold>
<Status>ON</Status>
</LegalHold>'

A successful request returns a 200 response.







 SDK examples 

The following examples make use of the IBM COS SDKs for Python, Node.js, and Go, as well as a Terraform script, although the implementation of object versioning should be fully compatible with any S3-compatible library or tool that allows for the setting of custom endpoints. Using third-party tools requires HMAC credentials in order to calculate AWS V4 signatures. For more information on HMAC credentials, [see the documentation](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-main).



 Python
def complete_multipart_upload_with_retention(bucket_name, object_name, upload_id, retention_period):
print("Completing multi-part upload for object {0} in bucket {1}n".format(object_name, bucket_name))

cos.complete_multipart_upload(
Bucket=bucket_name,
Key=object_name,
MultipartUpload={
"Parts":[{
"ETag": part"ETag"],
"PartNumber": 1
}]
},
UploadId=upload_id,
RetentionPeriod=retention_period
)

print("Multi-part upload completed for object {0} in bucket {1}n".format(object_name, bucket_name))

def upload_file_with_retention(bucket_name, object_name, path_to_file, retention_period):
print("Uploading file {0} to object {1} in bucket {2}n".format(path_to_file, object_name, bucket_name))

args = {
"RetentionPeriod": retention_period
}

cos.upload_file(
Filename=path_to_file,
Bucket=bucket_name,
Key=object_name,
ExtraArgs=args
)

print("File upload complete to object {0} in bucket {1}n".format(object_name, bucket_name))

function putObjectAddLegalHold(bucketName, objectName, legalHoldId) {
console.log(Add legal hold ${legalHoldId} to ${objectName} in bucket ${bucketName} with a putObject operation.);
return cos.putObject({
Bucket: bucketName,
Key: objectName,
Body: 'body',
RetentionLegalHoldId: legalHoldId
}).promise()
.then((data) => {
* The maximum number of days that data is archived includes events for the past 7 days when the instance has a 7 day search plan.





For example, you have a service plan of 30 days. You configured the instance 10 days ago. You enable archiving on the 10th day. The archiving process generates multiple files. Each file includes events for the period of time indicated as part of its name. If there is no data, the archive file for that period is empty.

Each IBM Cloud Activity Tracker instance has its own archiving configuration.

The following figure shows a high-level view of the different components that are integrated when archiving events:

![High-level view archiving events](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/archive.png)

The IBM Cloud Object Storage instance is provisioned within the context of a resource group. The IBM Cloud Activity Tracker instance is also provisioned within the context of a resource group. Both instances can be grouped under the same resource group or in different ones.

IBM Cloud Activity Tracker uses a service ID to communicate with the IBM Cloud Object Storage service.



* The service ID that you create for an IBM Cloud Object Storage instance is used by IBM Cloud Activity Tracker to authenticate and access the IBM Cloud Object Storage instance.
* You can assign specific access policies to the service ID that restrict permissions on the IBM Cloud Object Storage instance. Restrict the service ID to only have writing permissions on the bucket where you plan to archive the events.
* You can also restrict the IP addresses that are allowed to manage the bucket.



Archiving in an EU-managed location: You must configure a bucket that complies with the EU-managed and GDPR regulations.





 Viewing archived events by using the SQL Query service 

Data Engine provides a serverless, no-ETL solution to easily query data stored in COS. [Learn more](https://cloud.ibm.com/docs/sql-query?topic=sql-query-overview).
provisioner: ibm.io/ibmc-block
parameters:
billingType: "hourly"
classVersion: "2"
sizeIOPSRange: |-
"[20-39]Gi:[100-1000]"
"[40-79]Gi:[100-2000]"
"[80-99]Gi:[100-4000]"
"[100-499]Gi:[100-6000]"
"[500-999]Gi:[100-10000]"
"[1000-1999]Gi:[100-20000]"
"[2000-2999]Gi:[200-40000]"
"[3000-3999]Gi:[200-48000]"
"[4000-7999]Gi:[300-48000]"
"[8000-9999]Gi:[500-48000]"
"[10000-12000]Gi:[1000-48000]"
type: "Performance"
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
Show more





 Specifying the zone and region 

If you want to create your block storage in a specific zone, you can specify the zone and region in a customized storage class.

Use the customized storage class if you use the IBM Cloud Block Storage plug-in version 1.0.0 or if you want to [statically provision block storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageexisting_block) in a specific zone. In all other cases, [specify the zone directly in your PVC](https://cloud.ibm.com/docs/containers?topic=containers-block_storageadd_block).

The following .yaml file customizes a storage class that is based on the ibm-block-silver non-retaining storage class: the type is "Endurance", the iopsPerGB is 4, the sizeRange is "[20-12000]Gi", and the reclaimPolicy is set to "Delete". The zone is specified as dal12.
Data resiliency Regional Regional Regional Regional 
 Retention policy [15] NO NO NO NO 
 Expiration policy ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 Long-term retention policy NO NO NO NO 



[15]: Currently, you cannot use your own key with a bucket that has a retention policy configured.

Use the customer-managed encryption model to manage and control the key that is used to encrypt data at-rest.

[After you designate a root key in Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-create-root-keys) and [grant access between your services](https://cloud.ibm.com/docs/key-protect?topic=key-protect-integrate-servicesgrant-access), you can enable envelope encryption for a specified storage bucket by using the IBM Cloud Object Storage GUI.
An hourglass or clock icon next to the device name in the UI indicates that it’s in a waiting period. The minimum 24-hour waiting period gives you a chance to void the cancel request if needed.
* Which NFS versions are supported?

Both NFSv3 and NFSv4.1 are supported in the IBM Cloud® environment. NFSv4.2 is not supported.

Use NFSv3 protocol when possible. NFSv3 supports safe asynchronous writes and is more robust at error handling than the previous NFSv2. It supports 64-bit file sizes and offsets, allowing clients to access more than 2 GB of file data.

NFSv3 natively supports no_root_squash that allows root clients to retain root permissions on the NFS share. You can enable this feature in NFSv4.1, by editing the domain information and running the rpcidmapd or a similar service. For more information, see [Implementing no_root_squash for NFS](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingLinuxnorootsquash).

When File Storage for Classic is used in a VMware® deployment, NFSv4.1 might be the better choice for your implementation. For more information about the different features of each version and what is supported by VMware®, see [NFS Protocols and ESXi](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-8A929FE4-1207-4CC5-A086-7016D73C328F.html).
* Can VAAI and HW acceleration be enabled in our VMware deployments?

No. Currently, vStorage for API Array Integration and Hardware acceleration are not supported.
* What happens to the drives that are decommissioned from the cloud data center?

When drives are decommissioned, IBM destroys them before they are disposed of. The drives become unusable. Any data that was written to that drive becomes inaccessible.
The policy applies to the new objects uploaded but does not affect existing objects on a bucket. For details, see [Add or manage an archive policy on a bucket](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-archivearchive-add).





 Can I unzip a file after I upload it? 

A feature to unzip or decompress files is not part of the service. For large data transfer, consider using Aspera high-speed transfer, multi-part uploads, or threads to manage multi-part uploads. See [Store large objects](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-large-objects).





 Can I create a bucket, in the same or different region, with a deleted bucket name? 

A bucket name can be reused as soon as 15 minutes after the contents of the bucket have been deleted and the bucket has been deleted. Then, the objects and bucket are irrevocably deleted and can not be restored.

If you do not first empty and then delete the bucket, and instead [delete or schedule the Object Storage service instance for deletion](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-provisiondeleting-a-service-instance), the bucket names will be held in reserve for a [default period of seven (7) days until the account reclamation process](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_reclamations) is completed. Until the reclamation process is complete, it is possible to restore the instance, along with the buckets and objects. After reclamation is complete, all buckets and objects will be irrevocably deleted and can not be restored, although the bucket names will be made available for new buckets to reuse.





 Why do CredentialRetrievalError occur while uploading data to Object Storage or while retrieving credentials? 

CredentialRetrievalError can occur due to the following reasons:
Refer to [Topologies](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-topologies) for infrastructure resources provisioned and to [Pricing](https://www.ibm.com/cloud/vpc/pricing) for the associated cost.
* Can I use the tile to upgrade WebSphere Application Server after initial installation?

No, you can use the tile only for one installation. After the initial installation, it is your responsibility to manage and upgrade the installation.



Integration Event Streams



* How do I use Kafka APIs to create and delete topics?

If you're using a Kafka client at 0.11 or later, or Kafka Streams at 0.10.2.0 or later, you can use APIs to create and delete topics. We've put some restrictions on the settings allowed when you create topics. Currently, you can modify the following settings only:

cleanup.policy
: Set to delete (default), compact or delete,compact

retention.ms
: The default retention period is 24 hours. The minimum is 1 hour and the maximum is 30 days. Specify this value as multiples of hours.

Note: In the Enterprise plan, you can set this to any value.

retention.bytes
: The maximum size a partition (which consists of log segments) can grow to before we discard old log segments to free up space.

Note: Enterprise: Set to any value between 100 KiB and 2 TiB. Standard: Set to any value between 100 KiB and 1 GiB.

segment.bytes
: The segment file size for the log.

Note: Enterprise: Set to any value between 100 KiB and 2 TiB. Standard: Set to any value between 100 KiB and 512 MiB.

segment.index.bytes
: The size of the index that maps offsets to file positions.

Note: Enterprise: Set to any value between 100 KiB and 1 TiB. Standard: Set to any value between 100 KiB and 100 MiB.

segment.ms
: See the steps in [Why am I still seeing charges for block storage devices after deleting my cluster](https://cloud.ibm.com/docs/containers?topic=containers-ts_storage_clean_volume).





 Cleaning up persistent storage 

Remove the PVC, PV, and the storage instance from your IBM Cloud account to avoid further charges for your persistent storage.

Before you begin:



* Make sure that you backed up any data that you want to keep.
* [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



To clean up persistent data:



1. List the PVCs in your cluster and note the NAME of the PVC, the STORAGECLASS, and the name of the PV that is bound to the PVC and shown as VOLUME.

oc get pvc

Example output

NAME STATUS VOLUME CAPACITY ACCESSMODES STORAGECLASS AGE
claim1-block-bronze Bound pvc-06886b77-102b-11e8-968a-f6612bb731fb 20Gi RWO ibmc-block-bronze 78d
claim-file-bronze Bound pvc-457a2b96-fafc-11e7-8ff9-b6c8f770356c 4Gi RWX ibmc-file-bronze-retain 105d
claim-file-silve Bound pvc-1efef0ba-0c48-11e8-968a-f6612bb731fb 24Gi RWX ibmc-file-silver 83d
2. Review the ReclaimPolicy and billingType for the storage class.

oc describe storageclass <storageclass_name>

If the reclaim policy says Delete, your PV and the physical storage are removed when you remove the PVC. If the reclaim policy says Retain, or if you provisioned your storage without a storage class, then your PV and physical storage are not removed when you remove the PVC. You must remove the PVC, PV, and the physical storage separately.
container-registry.retention.analyze [ibmcloud cr retention-policy-set](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_policy_set) Set a policy to clean up your namespaces by retaining only container images that meet your criteria.<br><br>[ibmcloud cr retention-run](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_run) Clean up your namespaces by retaining only container images that meet your criteria. Reader, Manager<br><br>To run ibmcloud cr retention-run and ibmcloud cr retention-policy-set you must have Manager, or both Reader and Writer. 
 container-registry.retention.get View the image retention policy for a namespace by using the API, see [IBM Cloud Container Registry API](https://cloud.ibm.com/apidocs/container-registry). Reader, Manager 
 container-registry.retention.set [ibmcloud cr retention-policy-set](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_policy_set) Set a policy to clean up your namespaces by retaining only container images that meet your criteria. Writer, Manager 
 container-registry.retention.list [ibmcloud cr retention-policy-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_policy_list) List the image retention policies for your account. Reader, Manager 









 Assigning access to Container Registry in the console 

You can use one of the following options to assign access in the console:



* Access policies per user. You can manage access policies per user from the Manage > Access (IAM) > Users page in the console. For more information about the steps to assign IAM access, see [Managing access to resources](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources&interface=uiaccess-resources-console).
* Access groups.
When the volume is canceled, the request is followed by a 24-hour reclaim wait period. You can still see the volume in the console during those 24 hours. Billing for the volume stops immediately. When the reclaim period expires, the data is destroyed and the volume is removed from the console, too.





 Measuring IOPS 

IOPS is measured based on a load profile of 16-KB blocks with random 50 percent reads and 50 percent writes. Workloads that differ from this profile might experience poor performance. To improve performance, you can try adjusting the host settings or [enabling Jumbo frames](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-jumboframes).





 What happens when I use a smaller block size for measuring performance? 

Maximum IOPS can be obtained even if you use smaller block sizes. However, the throughput is less in this case. For example, a volume with 6000 IOPS has the following throughput at various block sizes:



* 16 KB * 6000 IOPS == 93.75 MB/sec
* 8 KB * 6000 IOPS == 46.88 MB/sec
* 4 KB * 6000 IOPS == 23.44 MB/sec







 Is the allocated IOPS enforced by instance or by volume? 

IOPS is enforced at the volume level. Said differently, two hosts connected to a volume with 6000 IOPS share that 6000 IOPS.





 Does the volume need to be pre-warmed to achieve expected throughput? 

Pre-warming is not needed. You can observe the specified throughput immediately upon provisioning the volume.





 Can more throughput be achieved if a faster Ethernet connection is used? 

Throughput limits are set at a per-volume level. That limit cannot be increased by using a faster Ethernet connection. However, with a slower Ethernet connection, your bandwidth can be a potential bottleneck.





 Do firewalls and security groups impact performance? 

It's best to run storage traffic on a VLAN, which bypasses the firewall. Running storage traffic through software firewalls increases latency and adversely affects storage performance.





 How do I route File Storage for Classic traffic to its own VLAN interface and bypass a firewall?