vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Example for bronze, silver, gold storage classes: The following .yaml file creates a claim that is named block-storage-pvc of the "ibmc-block-silver" storage class, billed hourly, with a gigabyte size of 24Gi.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: block-storage-pvc
labels:
billingType: "hourly"
region: us-south
zone: dal13
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 24Gi
storageClassName: ibmc-block-silver
* Example for using the custom storage class: The following .yaml file creates a claim that is named block-storage-pvc of the storage class ibmc-block-retain-custom, billed hourly, with a gigabyte size of 45Gi and IOPS of "300".

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: block-storage-pvc
labels:
billingType: "hourly"
region: us-south
zone: dal13
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 45Gi
iops: "300"
storageClassName: ibmc-block-retain-custom
Show more

name
: Enter the name of the PVC.

billingType
: In the metadata labels section, specify the frequency for which your storage bill is calculated, "monthly" or "hourly". The default is "hourly".

region
: In the metadata labels section, specify the region where you want to provision your block storage. If you specify the region, you must also specify a zone. If you don't specify a region, or the specified region is not found, the storage is created in the same region as your cluster. This option is supported only with the IBM Cloud Block Storage plug-in version 1.0.1 or higher.
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 





5. Choose if you want to keep your data after the cluster or the persistent volume claim (PVC) is deleted.



* If you want to keep your data, then choose a retain storage class. When you delete the PVC, only the PVC is deleted. The PV, the physical storage device in your IBM Cloud infrastructure account, and your data still exist. To reclaim the storage and use it in your cluster again, you must remove the PV and follow the steps for [using existing block storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageexisting_block).
* If you want the PV, the data, and your physical block storage device to be deleted when you delete the PVC, choose a storage class without retain.



6. Choose if you want to be billed hourly or monthly. The default setting is hourly billing.







 Setting up encryption for Block Storage for Classic 

You can set up encryption for Block Storage for Classic by using IBM Key Protect.

The following example explains how to create a service ID with the required access roles for Key Protect and your cluster. The credentials of this service ID are used to enable encryption for your Block Storage for Classic volumes.

You can enable encryption by creating a Kubernetes secret that uses your personal API key as long as you have the Reader service access role for your Key Protect instance as well as the Viewer platform access role and the Writer service access role for your cluster.

[Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



1.
* [Oracle](https://cloud.ibm.com/docs/Backup?topic=Backup-OraclepluginOracleplugin)
* [VMware® VRA](https://cloud.ibm.com/docs/Backup?topic=Backup-VRAVRA)



The plug-ins that are listed here are only compatible with Windows® servers, except for the Oracle or VMware® plug-ins. Each agent is available as an add-on to your backup service at no cost.





 How frequently can we back up the data? 

Within Cloud Backup Portal, backups can be made manually, or can be scheduled as a single instance, or to be recurring. Recurring backups can be made daily, weekly, monthly or on a custom schedule and can be updated or canceled at any time.

Highly frequent backups that run several times daily or hourly can cause backup jobs to become corrupted. This corruption occurs because backup vault does not get enough time to run required background maintenance tasks. Backup Jobs take precedence over maintenance tasks. So when backups are done with high frequency, the vault continues to run the backup jobs and cause the number of safe-sets to grow.





 How do the retention schemes work? 

IBM Cloud Backup for Classic allows for data-retention depending on how long you want to roll back to. Daily retention schemes hold data for seven days, while weekly schemes hold data for one month and monthly schemes hold data for one year. At the end of each period, the oldest data set gets rotated out, and the first "delta backup" that was made becomes the oldest available restore point.

You can modify default retention schemes and can create custom retention schemes. It's best to use the default retention schemes as a starting point. When you create a new retention scheme or modify an existing retention, make sure that the Archiving option is not selected. Archiving is not supported.





 What is Delta Technology? 

The first backup is a "seed" (a complete, full backup), the next and subsequent ones are "deltas" (that is, changes only), but they are equivalent to, and still considered a "full backup". That is, you're able to restore all or any files from it.
function addLegalHoldToObject(bucketName, objectName, legalHoldId) {
console.log(Adding legal hold ${legalHoldId} to object ${objectName} in bucket ${bucketName});
return cos.client.addLegalHold({
Bucket: bucketName,
Key: objectId,
RetentionLegalHoldId: legalHoldId
}).promise()
.then(() => {
console.log(Legal hold ${legalHoldId} added to object ${objectName} in bucket ${bucketName}!);
})
.catch((e) => {
console.log(ERROR: ${e.code} - ${e.message}n);
});
}

function deleteLegalHoldFromObject(bucketName, objectName, legalHoldId) {
console.log(Deleting legal hold ${legalHoldId} from object ${objectName} in bucket ${bucketName});
return cos.client.deleteLegalHold({
Bucket: bucketName,
Key: objectId,
RetentionLegalHoldId: legalHoldId
}).promise()
.then(() => {
console.log(Legal hold ${legalHoldId} deleted from object ${objectName} in bucket ${bucketName}!);
})
.catch((e) => {
console.log(ERROR: ${e.code} - ${e.message}n);
});
}
Show more





 Extend the retention period of a protected object 

The retention period of an object can only be extended. It cannot be decreased from the currently configured value.

The retention expansion value is set in one of three ways:



* additional time from the current value (Additional-Retention-Period or similar method)
* new extension period in seconds (Extend-Retention-From-Current-Time or similar method)
* new retention expiry date of the object (New-Retention-Expiration-Date or similar method)
For more information, see the [FAQ](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-block-storage-faqs).

Active replicas and dependent duplicates can block reclamation of the Storage volume. Make sure that the volume is no longer mounted, host authorizations are revoked, replication is canceled, and no dependent duplicates exist before you attempt to cancel the original volume.





 Deleting a storage LUN from the SLCLI 

If you no longer need a specific LUN, you can cancel it at any time.

To cancel a storage LUN, it's necessary to revoke access from any hosts first.

Then, you can use the following command in SLCLI to cancel the storage.

 slcli block volume-cancel --help
Usage: slcli block volume-cancel [OPTIONS] VOLUME_ID

Options:
--reason TEXT An optional reason for cancellation
--immediate Cancels the block storage volume immediately instead of on
the billing anniversary
-h, --help Show this message and exit.

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 (immediate cancellation) or until the anniversary date. Billing for the volume stops immediately. When the reclaim-period expires, the data is destroyed and the volume is removed from the console, too. For more information, see the [FAQ](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-block-storage-faqs).

Active replicas and dependent duplicates can block reclamation of the Storage volume. Make sure that the volume is no longer mounted, host authorizations are revoked, replication is canceled, and no dependent duplicates exist before you attempt to cancel the original volume.





 Deleting a storage LUN from Terraform 

Use the terraform destroy command to conveniently destroy a remote object such as a single volume. The following example shows the syntax of the command.

terraform destroy --target ibm_storage_block.volumeID
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.
* [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-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.

kubectl 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.

kubectl describe storageclass <storageclass_name>

If the reclaim policy says Delete, your PV and the physical storage are removed when you remove the PVC. Note that VPC Block Storage is not removed automatically, even if you used a Delete storage class to provision the storage. 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.

If your storage is charged monthly, you still get charged for the entire month, even if you remove the storage before the end of the billing cycle.
If you don't include this option, the volumeBindingMode is automatically set to Immediate and the block storage instance is created when you create the PVC.

Example for Endurance block storage.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-block-bronze-delayed
parameters:
billingType: hourly
classVersion: "2"
fsType: ext4
iopsPerGB: "2"
sizeRange: '[20-12000]Gi'
type: Endurance
provisioner: ibm.io/ibmc-block
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer

Example for Performance block storage.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-block-performance-storageclass
labels:
kubernetes.io/cluster-service: "true"
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
Scaling Enterprise plan capacity 



 Event Streams capacity 

The Event Streams Enterprise plan lets you to specify throughput and storage capacity when a new instance of the service is created. If after using the service instance, you find that the current capacity configuration of your service instance is not meeting the demands of your solution, throughput and storage capacity can be scaled up to meet demands.

Each base or additional capacity unit includes the following capacity:



* 150 MB/s of throughput capacity.
* 2 TB of storage capacity available for your data retention.



For example, selecting a base capacity unit, one additional capacity unit, and 4 TB of additional storage provides you with the following capacity:



* 300 MB/s of throughput capacity.
* 8 TB of storage capacity for data retention.







 Throughput capacity 

Throughput capacity is the recommended MB/s maximum for producing and consuming messages.

Each capacity unit provides 150 MB/s of throughput capacity. It consists of 75 MB/s data ingress and 75 MB/s data egress capacity.

To scale up throughput capacity, you can add more capacity units. Each extra capacity unit adds 150 MB/s of throughput to your service instance, to a total of 450 MB/s.

The recommended throughput maximum is based on a typical workload and considers the possible impact of operational actions or failure modes, like the loss of an availability zone. If the average throughput exceeds the recommended figure, a loss in performance might be experienced during these conditions. Plan your maximum throughput capacity as two-thirds of the maximum. For example, two-thirds of the 150 MB/s maximum are 100 MB/s. For more information on capacity recommendations and limitations, see [limits and quotas](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-kafka_quotaslimits_enterprise).

Although throughput scaling is independent of storage, for each tier a defined minimum of storage amount is required.





 Storage capacity 

Storage capacity is the amount of storage that is allocated in the service instance for retention of message data.

Storage capacity can be scaled up, independent of throughput capacity, when data retention is important for your architecture.
More information can be found in the [Select Regions and Endpoints](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpoints).





 28 March 2019 

New feature!
: User can use [COS Firewall](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-setting-a-firewallsetting-a-firewall) to restrict access to the data in COS only if request originates from a list of allowed IP addresses.

IAM update
: IAM policies can now grant [public access](https://cloud.ibm.com/docs/cloud-object-storage/iam?topic=cloud-object-storage-iam-public-access) to entire buckets.

New location!
: Buckets can now be created in a Single Data Center configuration in Milan, Italy. More information can be found in the [Select Regions and Endpoints](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-endpoints).





 28 February 2019 

New location!
: Buckets can now be created in a Single Data Center configuration in San Jose, USA. More information can be found in the [Select Regions and Endpoints](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-endpoints).





 18 January 2019 

New location!
: Buckets can now be created in AP Australia region. More information can be found in the [Select Regions and Endpoints](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-endpoints).





 14 December 2018 

New feature!
: Users can use [Immutable Object Storage](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-immutable) to create retention policies that prevent object deletion or modification.

New location!
<Key>soldier-bee</Key>
<LastModified>2016-08-25T17:49:06.006Z</LastModified>
<ETag>"37d4c94839ee181a2224d6242176c4b5"</ETag>
<Size>11</Size>
<StorageClass>STANDARD</StorageClass>
</Contents>
</ListBucketResult>
Show more

--------------------





 List objects in a given bucket (deprecated) 

This API is included for backwards compatibility. See [Version 2](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-compatibility-api-bucket-operationscompatibility-api-list-objects-v2) for the recommended method of retrieving objects in a bucket.

Not all operations are supported in Satellite environments. For details, see [supported Satellite APIs](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-apis-cos-satellite)

A GET request addressed to a bucket returns a list of objects, limited to 1,000 at a time and returned in non-lexographical order. The StorageClass value that is returned in the response is a default value as storage class operations are not implemented in COS. This operation does not make use of operation specific headers or payload elements.

Syntax

GET https://{endpoint}/{bucket-name} path style
GET https://{bucket-name}.{endpoint} virtual host style





 Optional query parameters 



 Name Type Description 

 prefix String Constrains response to object names beginning with prefix. 
 delimiter String Groups objects between the prefix and the delimiter. 
 encoding-type String If unicode characters that are not supported by XML are used in an object name, this parameter can be set to url to properly encode the response. 
 max-keys String Restricts the number of objects to display in the response.
Object Storage provides SDKs for Java, Python, NodeJS, and Go featuring capabilities to make the most of IBM Cloud Object Storage. For information about the features supported by each SDK, see the [feature list](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-sdk-about).
* When a file is uploaded to a cross region bucket using the ‘us-geo’ endpoint, how long is the delay before the file is available at the other US sites?

The data are spread immediately without delay and the uploaded files are available once the write is successful.
* How do I access the reclaimed resources?

Create a new set of credentials to access the restored resources.
* Can I host a website using a Object Storage bucket?

You can use Object Storage bucket to host a static website. For details, see [Hosting Website using COS](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-static-website-tutorial).
* Are REST and cURL commands supported for Object Storage bucket creation using HMAC credentials?

Yes, you should setup an authorization header. For details, see [Using HMAC Signature](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-hmac-signature).
* What kind of IAM authorization is required to edit a bucket's authorized IPs list?

You must have 'Manager' privilege on the bucket to manage the firewall and to set the authorizations.
* Can I convert a single region Object Storage bucket to cross region without having to copy objects?

No, you must copy objects to the target bucket. For details, see [COS Region Copy](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-region-copy).
* Is there a way to verify an object’s integrity during an upload to Object Storage?

Object Storage supports object integrity and ensures that the payload is not altered during transit.
* How can I set a notification when usage in a Object Storage instance is near a certain billing amount?
Delete a bucket’s lifecycle configuration, including expiration 

This implementation of the DELETE operation uses the lifecycle query parameter to examine lifecycle settings for the bucket. All lifecycle rules associated with the bucket will be deleted. Transitions defined by the rules will no longer take place for new objects. However, existing transition rules will be maintained for objects that were already written to the bucket before the rules were deleted. Expiration Rules will no longer exist. An HTTP 404 response will be returned if no lifecycle configuration is present.

Cloud IAM users must have the Writer role to remove a lifecycle policy from a bucket.

Classic Infrastructure Users must have Owner permissions on the bucket to remove a lifecycle policy from a bucket.

Syntax

DELETE https://{endpoint}/{bucket}?lifecycle path style
DELETE https://{bucket}.{endpoint}?lifecycle virtual host style

Example Header Request

DELETE /images?lifecycle HTTP/1.1
Host: s3.us.cloud-object-storage.appdomain.cloud
Date: Wed, 7 Feb 2018 17:50:00 GMT
Authorization: authorization string
Content-Type: text/plain
Content-Length: 305

Using the IBM Cloud® Object Storage SDKs only requires calling the appropriate functions with the correct parameters and proper configuration.

var aws = require('ibm-cos-sdk');
var ep = new aws.Endpoint('s3.us-south.cloud-object-storage.appdomain.cloud');
var config = {
endpoint: ep,
apiKeyId: 'ZRZDoNoUseOLL7bRO8SAMPLEHPUzUL_-fsampleyYE',
ibmAuthEndpoint: 'https://iam.cloud.ibm.com/identity/token',
serviceInstanceId: 'crn:v1:bluemix:public:cloud-object-storage:global:a/<CREDENTIAL_ID_AS_GENERATED>:<SERVICE_ID_AS_GENERATED>::',
};
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. To use a different storage class as your base, see the [storage class reference](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_storageclass_reference).

Create the storage class in the same region and zone as your cluster and worker nodes. To get the region of your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID> and look for the region prefix in the Master URL, such as eu-de in https://c2.eu-de.containers.cloud.ibm.com:11111. To get the zone of your worker node, run ibmcloud ks worker ls --cluster <cluster_name_or_ID>.

Example for Endurance block storage.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-block-silver-mycustom-storageclass
labels:
kubernetes.io/cluster-service: "true"
provisioner: ibm.io/ibmc-block
parameters:
zone: "dal12"
region: "us-south"
type: "Endurance"
iopsPerGB: "4"
sizeRange: "[20-12000]Gi"
reclaimPolicy: "Delete"

Example for Performance block storage.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-block-performance-storageclass
labels:
kubernetes.io/cluster-service: "true"
For details see [cloud-object-storage-region-copy](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-region-copy).





 My COS service is locked. How do I reactivate the COS service? 

Exceeding the data limit for the Lite account is one of the reasons why your account is locked or deactived. The [COS support](https://cloud.ibm.com/unifiedsupport/cases/form) team can help to unlock your account.





 After deleting a Object Storage instance, is it possible to reuse the same bucket names that were part of the deleted COS instance? 

When an empty bucket is deleted, the name of the bucket is held in reserve by the system for 10 minutes after the delete operation. After 10 minutes the name is released for re-use.





 How can I archive and restore objects in Object Storage? 

Archived objects must be restored before you can access them. While restoring, specify the time limit the objects should remain available before being re-archived. For details, see [archive-restore data](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-archive).





 Can I enable Object Storage replication between two different regions for DR purposes? 

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?