vania-janet/multiturn-rag-retrieval-data huggingface dataset:
sizeRange: '[20-12000]Gi'
type: Endurance
provisioner: ibm.io/ibmc-file
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer

Example for Performance File Storage for Classic.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-file-performance-storageclass
labels:
kubernetes.io/cluster-service: "true"
provisioner: ibm.io/ibmc-file
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 for multizone clusters 

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

Use the customized storage class if you want to [statically provision File Storage for Classic](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storageexisting_file) in a specific zone.
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))
Show more





 Add or remove a legal hold to or from a protected object 

The object can support 100 legal holds:



* A legal hold identifier is a string of maximum length 64 characters and a minimum length of 1 character. Valid characters are letters, numbers, !, _, ., , (, ), - and \.
* If the addition of the given legal hold exceeds 100 total legal holds on the object, the new legal hold will not be added, a 400 error is returned.
I find that the optimal value for this option is around 50 MB. COS best practices suggest using requests that are multiples of 4 MB, and thus the recommendation is to set this option to 52 (MB).
6. parallel_count=30 sets the maximum number of requests sent concurrently to COS, per single file read/write operation. By default, this is set to 5. For very large objects, you can get more throughput by increasing this value. As with the previous option, keep this value low if you only read a small amount of data of each file.
7. multireq_max=30 When listing a directory, an object metadata request (HEAD) is sent per each object in the listing (unless the metadata is found in cache). This option limits the number of concurrent such requests sent to COS, for a single directory listing operation. By default it is set to 20. Note that this value must be greater or equal to the parallel_count option above.
8. dbglevel=warn sets the debug level to warn instead of the default (crit) for logging messages to /var/log/syslog.







 Limitations 

It is important to remember that s3fs may not be suitable for all applications, as object storage services have high-latency for time to first byte and lack random write access. Workloads that only read big files, like deep learning workloads, can achieve good throughput using s3fs.
File Contents: This is a test file from Node.js code sample!!!
DONE!

Starting multi-part upload for js_large_file_c697db513f8211e9b1228597cf8e3a32.bin to bucket: js.bucket.c697b4403f8211e9b1228597cf8e3a32
Uploading to js_large_file_c697db513f8211e9b1228597cf8e3a32.bin (part 1 of 4)
Uploading to js_large_file_c697db513f8211e9b1228597cf8e3a32.bin (part 2 of 4)
Uploading to js_large_file_c697db513f8211e9b1228597cf8e3a32.bin (part 3 of 4)
Uploading to js_large_file_c697db513f8211e9b1228597cf8e3a32.bin (part 4 of 4)
DONE!

Retrieving bucket contents from: js.bucket.c697b4403f8211e9b1228597cf8e3a32
Item: js_file_c697db503f8211e9b1228597cf8e3a32.txt (47 bytes).
Item: js_large_file_c697db513f8211e9b1228597cf8e3a32.bin (20971520 bytes).
DONE!

Deleting item: js_large_file_c697db513f8211e9b1228597cf8e3a32.bin
Item: js_large_file_c697db513f8211e9b1228597cf8e3a32.bin deleted!
DONE!
OVF packages can be uploaded to a catalog as a vApp template to make the template available to users. For more information, see [Create a vApp template from an OVF file](https://docs.vmware.com/en/VMware-Cloud-Director/10.1/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-5EA412C4-179A-42CF-9B30-1B81C23551E6.html).

Media files, such as ISO disk images and FLP diskette drive images, can be uploaded to a catalog as a media file. For more information, see [Working with media files](https://docs.vmware.com/en/VMware-Cloud-Director/10.1/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-A7530A4B-F782-4848-90FC-BBDE41E3AE85.html).

The maximum import size is 750 GB. Large image files or templates might take extended time to upload. For assistance with files larger than 750 GB, open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).







 Virtual machines 

When you use the tenant portal, you can create a virtual machine (VM) or provision a VM from a template.

For more information, see [Create a new stand-alone virtual machine](https://docs.vmware.com/en/VMware-Cloud-Director/10.1/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-12E43116-1120-45FA-A1E7-AEBEE61373C1.html).



 Customizing virtual machine properties 

You can edit the properties of a VM, including the VM name and description, hardware and network settings, and operating system settings for a guest.
Temporary files size in bytes 

Temporary files size in bytes



Table 19: Temporary files size in bytes metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_temp_bytes_count 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance 







 Total disk space for an instance 

Represents the total amount of disk available to your deployment.



Table 20: Total disk space for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_disk_total_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 







 Transaction commit count 

Transaction commit count



Table 21: Transaction commit count metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_transaction_commit_count 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance 







 Transaction commit rate 

Transaction commit rate



Table 22: Transaction commit rate metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_transaction_commit_rate 
 Metric Type gauge 
 Value Type rate 
 Segment By Service instance 







 Transaction rollback count 

Transaction rollback count



Table 23: Transaction rollback count metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_transaction_rollback_count 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance 







 Transaction rollback rate 

Transaction rollback rate



Table 24: Transaction rollback rate metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_transaction_rollback_rate 
 Metric Type gauge 
 Value Type rate 
 Segment By Service instance 







 Tuples deleted count 

Tuples deleted count



Table 25: Tuples deleted count metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_tuples_deleted_count 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance 







 Tuples deleted rate 

Tuples deleted rate



Table 26: Tuples deleted rate metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_tuples_deleted_rate 
 Metric Type gauge 
 Value Type rate
Make sure that the permissions for the /.ssh/ folder are set to 700 and the permissions for the /.ssh/id_rsa folder are set to 600.
* If your private key is not in the default location, use the following command to specify it in an environment variable:



GIT_SSH_COMMAND='ssh -i/path/to/private_key_file' git clone git@host:owner/repo.git



* To debug this issue by using connection information, add the -v or the -vvv flag to the GIT_SSH_COMMAND environment variable:



GIT_SSH_COMMAND='ssh -vvv git clone git@host:owner/repo.git

GIT_SSH_COMMAND='ssh -vvv -i/path/to/private_key_file' git clone git@host:owner/repo.git





 I tried to fetch changes from my Git Repos and Issue Tracking repo, why am I getting a 504 Gateway Time-out error? 

Your repo is larger than 1 GB. The Git source control management system isn't designed to store large binary files.

 What’s happening 

When I attempt to complete an operation on a Git Repos and Issue Tracking repo (such as a fetch or clone), I receive an error message:

git fetch error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 Gateway Time-out fatal: The remote end hung up unexpectedly

 Why it’s happening 

You have a large repo that is greater than 1 GB. The repo might also contain binary files that require more space than text files that are stored in a compressed format.

 How to fix it 

You can use any of the following methods to resolve this problem:



* Reduce the size of your Git Repos and Issue Tracking repo. For more information about reducing the size of your repo, see [Reducing the repository size using Git](https://docs.gitlab.com/ce/user/project/repository/reducing_the_repo_size_using_git.html).
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/8f06378c-ed0e-481e-b98c-9a6dfbee1ed5/volume_attachments/4cbb38bc-57d5-4121-a796-d5b10cf0810a",
"id": "<4cbb38bc-57d5-4121-a796-d5b10cf0810aAttachment ID>",
"instance": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/8f06378c-ed0e-481e-b98c-9a6dfbee1ed5",
"id": "8f06378c-ed0e-481e-b98c-9a6dfbee1ed5",
"name": "my-instance-1"
},
"name": "my-volume-attachment-1",
"type": "data"
}],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-2",
"name": "us-south-2"
}
}





 Adjust IOPS by specifying a different IOPS tier profile 

Make a PATCH /volumes request and specify the profile parameter and indicate the name or href of the IOPS tier profile.

This example changes a 3 IOPS/GB profile to 5 IOPS/GB profile. In this case, the volume can't exceed 9,600 GB to move to the higher profile.
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>
<DefaultRetention>
<Days>30</Days>
<Mode>COMPLIANCE</Mode>
</DefaultRetention>
</Rule>
</ObjectLockConfiguration>

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







 List canceled/incomplete multipart uploads for a bucket 

A GET issued to a bucket with the proper parameters retrieves information about any canceled or incomplete multipart uploads for 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)

Syntax

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

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-uploads integer Restricts the number of objects to display in the response. Default and maximum is 1,000. 
 key-marker String Specifies from where the listing should begin. 
 upload-id-marker String Ignored if key-marker is not specified, otherwise sets a point at which to begin listing parts above upload-id-marker. 



Example request
Getting started with IBM Cloudant 

The IBM® Cloudant® for IBM Cloud® Getting started tutorial demonstrates how to use the IBM Cloud® dashboard to create an IBM Cloudant service instance and obtain service credentials to connect to it. Finally, it guides you through the creation of a simple, locally hosted web application that uses your IBM Cloudant database.



 Objectives 



* Create a service instance.
* Create an IBM Cloudant service credential.







 Step 1: Creating a service instance 



1. Log in to your IBM Cloud account, and click Create resource.

Zoom

![IBM Cloud Dashboard, which includes Build tile, Monitor your resources tile, Create and deploy an application tile, API Connect tile, Integrate Watson with anything tile, and Watson starter kits tile.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant//tutorials/images/img0001.png)

Figure 1. IBM Cloud Dashboard

The IBM Cloud Dashboard can be found at: [https://cloud.ibm.com/](https://cloud.ibm.com/). After you authenticate with your username and password, you're presented with the IBM Cloud Dashboard.
2. Type Cloudant in the Search bar and click to open it.
3. Select an offering and an environment.
4. Type an instance name.

Zoom

![Create the IBM Cloudant service name and credentials.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/tutorials/images/img0005b.png)

Figure 2. IBM Cloudant service name and credentials

(In this example, the instance name is Cloudant-o7.) Verify that the resource group and authentication methods are correct. Add a tag if you like.
You can create one [from the console](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant) or by using CLI commands. In addition, create service credentials that you can pass to your application.



1. Create an IBM Cloudant service instance, follow the steps in [Getting started with IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant). Name your instance CloudantFruitCounter. Be sure to complete the task by creating your service credentials.
2. Open the IBM Cloudant dashboard for your instance and click Create database.
3. In the Create database window, enter the database name fruitcounter.
4. Do not select the Partitioned option, and click Create.







 Step 2: Test your application locally 

Before you create your code as an application in Code Engine, test your code locally to make sure that it is functioning correctly.



1. Retrieve the IBM Cloudant service credentials from the IBM Cloudant dashboard. For more information about retrieving credentials, see [Creating service credentials](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudantcreating-service-credentials).
2. Set environment variables with the values from the service credentials.

export CLOUDANT_URL=<your_url>

export CLOUDANT_APIKEY=<your_key>

export DBNAME="fruitcounter"
3. Clone the fruit-counter repository, change to this directory, and then install and start the dependencies.

git clone https://github.com/IBM/CodeEngine
cd CodeEngine/fruit-counter
npm install
npm run start
4. Open a browser and go to [http://localhost:8080](http://localhost:8080).
5. Pick your favorite fruit and submit your choice.
Creating an instance with CLI 

This tutorial shows you how to create an IBM® Cloudant® for IBM Cloud® service instance on IBM Cloud® by using the IBM Cloud CLI.



 Objectives 



1. Use your IBM Cloud account to create your IBM Cloudant service instance and credentials.
2. Retrieve and use your IBM Cloudant service instance.







 Before you begin 

Install the IBM Cloud CLI developer tools by following the [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) tutorial.





 Step 1: Logging in to your IBM Cloud account 

The following example describes how to log in. If you use a federated user ID, it's important that you switch to a one-time passcode (ibmcloud login --sso), or use an API key (ibmcloud --apikey key or @key_file) to authenticate. For more information about how to log in by using the CLI, see [General CLI (ibmcloud) commands](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login) under ibmcloud login.



1. Start the login process for your IBM Cloud account by using the following command.

ibmcloud login

IBM Cloud responds by reminding you of the current API endpoint, and asks for the email address of your account.

API endpoint: https://cloud.ibm.com
Region: au-syd

Email>

Password>
2. Enter the email address of your account, and then enter your password.

API endpoint: https://cloud.ibm.com

Email> J.Doe@email.com

Password>

IBM Cloud validates your details and summarizes the information about your login session.

API endpoint: https://cloud.ibm.com

Email> J.Doe@email.com

Password>
Authenticating...
OK

Targeted account J DOE's Account (707...a32)
Using the IBM Cloudant Dashboard 

By using the IBM® Cloudant® for IBM Cloud® Dashboard, you create an IBM Cloudant database, populate the database with data, and retrieve data by using queries or API endpoints. For more information about API endpoints, see the [API and SDK reference](https://cloud.ibm.com/apidocs/cloudantintroduction).



 Objectives 



1. Open the IBM Cloudant Dashboard.
2. Create a database.
3. Add JSON documents to the database and run a query.
4. Replicate a database.
5. Monitor active tasks.
6. Monitor with IBM Cloudant.







 Before you begin 

Create a service instance in IBM Cloud before you start this tutorial. You can follow the instructions in the [Getting started](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant) tutorial to create one.





 Step 1: Opening your service instance on IBM Cloudant Dashboard 

Open your IBM Cloudant service instance by following these steps:



1. Go to the IBM Cloud Dashboard.
2. Click Services in the Resource list.
3. From the Services section, click the Cloudant-o7 instance that you created in the Getting started tutorial, and click Launch Dashboard. The IBM Cloudant Dashboard opens.



Now, you can create a database and run queries against it.





 Step 2: Creating a database 

In this exercise, you create the dashboard-demo[database](https://cloud.ibm.com/apidocs/cloudantputdatabase), which is the database that you use in this tutorial.



1. From the IBM Cloudant Dashboard, click Create database.

The Create database window opens.
2. Enter the database name dashboard-demo.
3. Select Non-partitioned, and click Create.

The dashboard-demo database opens automatically.



Now, you can create some documents.





 Step 3: Adding documents to the database
Product guide 

 Cloudant 

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



* Get started



* [Getting started](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant)
* [Plans and provisioning](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-public)
* [Pricing](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-pricing)
* [Limits](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-limits)
* [Connecting](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-connecting)
* [Learning Center](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-learning-center)
* Security & compliance



* [Security](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-security)
* [Compliance](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-compliance)
* [Data privacy and governance](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-data-privacy-and-governance)
* [Audit logging](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-audit-logging)
* [General Data Protection Regulation (GDPR)](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-general-data-protection-regulation-gdpr-)



* [Transaction Engine notice](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-overview-te)
* [Service Changes and Deprecations for IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-deprecations-for-ibm-cloudant)
Configure the IBM Cloudant instance.



1. Enter an instance name or accept the pre-filled name.
2. Select a resource group.
3. (Optional) Add a tag.
4. Select an authentication method.
The Standard plan is the only plan you can use with the Dedicated Hardware environment.



Zoom

![Configure your IBM Cloudant instance.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/tutorials/images/img0005e.png)

Figure 6. IBM Cloudant instance
6. Click Create.
After a few seconds, the instance is provisioned on the environment you selected.

Zoom

![Provision a standard plan by using the create button.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/tutorials/images/create_button_provision_standard.png)

Figure 7. Standard instance
7. Take note of your Service Credentials and access the IBM Cloudant Dashboard as you do for a multi-tenant IBM Cloudant instance.

For more information, see [how to locate your service credentials](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-locating-your-service-credentials).







 Step 3: Provisioning a Dedicated Hardware plan instance with the IBM Cloud CLI 



1. Log in to IBM Cloud to use IBM Cloud CLI.
(https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/tutorials/images/img0005f.png)

Figure 2. Host configuration
7. Click Create to start the provisioning process.

Billing is calculated and prorated every day. Make sure that you want to provision and pay for an environment before you click Create.

Zoom

![Do not click Create unless you want to provision and pay for an environment.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/tutorials/images/create_button_provision.png)

Figure 3. Provision dedicated hardware







 Step 2: Provisioning a Standard plan instance on a Dedicated Hardware environment 

After your instance is created, you must create a Standard plan on it by selecting the Dedicated tab when you create the Standard instance.



1. Log in to your IBM Cloud account.

The IBM Cloud Dashboard can be found at: [https://cloud.ibm.com/](https://cloud.ibm.com/). After you authenticate with your username and password, you're presented with the IBM Cloud Dashboard. Click Create resource.
2. Type Cloudant in the Search bar and click to search.
3. Select an offering.

You can't provision a Lite plan instance on a Dedicated Hardware environment.
4. Select an environment.

For Dedicated Hardware provisioned instances, you can select from the major IBM Cloud regions in the IBM Cloud Dashboard. However, the actual physical location of the Dedicated Hardware instance is dictated by the location parameter in a later step.



1. Click Dedicated.
2. Click Select existing host.
3. Select the dedicated environment that you created from the drop-down menu.