vania-janet/multiturn-rag-retrieval-data huggingface dataset:
CLOUDANT_HOSTNAME=37c53a06-5193-23f3-b681-7c8b76ce7qaa-bluemix.cloudantnosqldb.appdomain.cloud CLOUDANT_USERNAME=37c53a06-5193-23f3-b681-7c8b76ce7qaa-bluemix CLOUDANT_PASSWORD=e2dbc589632a0651ae44ee3920f8cdb02bdcb68e1909b6314c42f5b0d39c043a CLOUDANT_DATABASE=cats PACKAGE_NAME=my-package RULE_NAME=my-rule TRIGGER_NAME=my-trigger ibmcloud fn deploy -m manifest.yaml





After the template deploys, you can make further edits to the code to customize it as needed, or go back and check out the catalog of available templates.





 Testing your IBM Cloudant Events package 

Now that you have your IBM Cloudant database and your IBM Cloudant events (action and trigger) set up, let's try it out! The expected data item is a cat, with a name and a color defined. When a new cat is added to the database or a current cat is edited, the data is logged to the console module for Node.js.



 1. Testing the action 

Before you make entries in the IBM Cloudant database, make sure that the process change action is working properly. Note that this entry does not update the IBM Cloudant database, but instead is a method of testing the action itself.



1. Open the [Actions page](https://cloud.ibm.com/functions/actions) from the Cloud Functions console.
2. From the IBM Cloudant events package (called cloudant-events, if you accepted the default name), select Manage Action from the process change action.
3. Click Change input and enter a valid JSON entry for name and color, similar to the following example.

{
"name": "Tarball",
"color": "Black"
}
4. Click Apply.
5.
For more information about the limit on simultaneous authorizations, see the [FAQs](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-file-storage-faqsauthlimit).







 Ordering File Storage for Classic with the API 

The method order_file_volume (storage_type, location, size, iops=None, tier_level=None, snapshot_size=None, service_offering='storage_as_a_service', hourly_billing_flag=False) places an order for a file volume.

You must specify the following parameters for a successful order.



* storage_type – "performance" or "endurance".
* location – Data center in which to order iSCSI volume.
* size – Size of the new volume, in GB.
* iops – Number of IOPs for a “Performance” order.
* tier_level – Tier level to use for an “Endurance” order.
* snapshot_size – The size of optional snapshot space, if snapshot space is also to be ordered. (None if not ordered.)
* service_offering – Requested offering package to use in the order ("storage_as_a_service", "enterprise", or "performance").
* hourly_billing_flag – Billing type, monthly (False) or hourly (True), default to monthly.



To be able to access all the new features, order Storage-as-a-Service Package 759.

For more information about ordering File Storage for Classic through the API, see [order_file_volume](https://softlayer-python.readthedocs.io/en/latest/api/managers/file/SoftLayer.managers.file.FileStorageManager.order_file_volume).

By default, you can provision a combined total of 700 File Storage for Classic volumes. To increase the number of your volumes, contact your sales representative. Read about increasing limits [here](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managinglimits).
ibmcloud event-notifications destination update --id ID [--name NAME] [--description DESCRIPTION] [--certificate CERTIFICATE] [--config CONFIG] [--instance-id INSTANCE-ID]
* Parameters to provide:

--id (string)
: Unique identifier for destination. Required.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.

--name NAME (string)
: The destination name to be updated.

The maximum length is 255 characters. The minimum length is 1 character. The value must match regular expression /[!a-zA-Z 0-9-_/.?:'";,+=@$%^&() ]/.

--description DESCRIPTION (string)
: The description of the destination.

The default value is . The maximum length is 255 characters. The minimum length is 0 characters. The value must match regular expression /[!a-zA-Z 0-9-_/.?:'";,+=@$%^&() ]/.

--certificate CERTIFICATE (string)
: The certificate file path to be provided. The allowed file type is p8 and p12 certificate.

--config CONFIG ([DestinationConfig examples](https://cloud.ibm.com/docs/cli?topic=cli-event-notifications-clien-cli-destination-config-example-schema))
: The configuration needed to set the destination-specific parameters.

--instance-id
: The unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters.
* UI
* CLI
* API
* Terraform







 Expanding file share capacity 

For File Storage for VPC file shares, you can increase the file share size from its original capacity in GB increments up to 32,000 GB capacity, depending on your file share profile. This process doesn't require you to perform manual steps. For example, you don't need to migrate your data to a larger file share. The expansion operation causes no outage or lack of access to your storage.

Billing for the file share is automatically updated to add the pro-rated difference of the new price to the current billing cycle. The new full amount is then billed in the next billing cycle.

IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.



 Expandable file share concepts 

You can increase the capacity of the file share. The file share size cannot be less than the current file share size.

Capacity can be increased for file shares that are in a stable state. Your user authorization is verified before the file share is expanded. You can use the [UI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-expand-capacityexpand-vpc-share-ui), [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-expand-capacityexpand-vpc-share-cli), or [API](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-expand-capacityexpand-vpc-share-api) to increase file share capacity. You can expand a file share multiple times up to its [maximum capacity limit](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-expand-capacityexp-share-capacity-IOPS-limitations). After you expanded the file share, you can't reduce the capacity.
ID 0757-6757e676-0bf5-4b79-9a5b-29c24e17420c
Name otp1
Volume ID Name
r014-dee9736d-08ee-4992-ba8d-3b64a4f0baac demo-volume-update

Status attaching
Bandwidth(Mbps) 393
Type data
Device -
Auto delete true
Created 2023-06-29T18:14:57+00:00

For more information about available command options, see [ibmcloud is instance-volume-attachment-add](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referenceinstance-volume-attachment-add).





 Show details of a volume that is attached to a virtual server instance 

After you attach a volume, you can display details by specifying the instance ID or name and the volume attachment ID or name in the instance-volume-attachment command.

ibmcloud is instance-volume-attachment INSTANCE VOLUME_ATTACHMENT [--json]

$ ibmcloud is instance-volume-attachment kj-test-ro otp1
Getting volume attachment otp1 of instance kj-test-ro under account Test Account as user test.user@ibm.com...

ID 0757-6757e676-0bf5-4b79-9a5b-29c24e17420c
Name otp1
Volume ID Name
r014-dee9736d-08ee-4992-ba8d-3b64a4f0baac demo-volume-update

Status attached
Bandwidth(Mbps) 393
Type data
Device 0757-6757e676-0bf5-4b79-9a5b-29c24e17420c-bxsh7
Auto delete true
Created 2023-06-29T18:14:57+00:00
To mount a subdirectory, you must set ibm.io/auto-create-bucket: "false" and provide the name of the bucket in ibm.io/bucket.

ibm.io/quota-limit
: To use this annotation, you must specify the --set quotaLimit=true option during installation. If you want to use this annotation, but didn't specify --set quotaLimit=true during installation, [re-install the helm chart](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install).
: If ibm.io/quota-limit is set to true, your PVC will set a maximum amount of storage (in bytes) available for the bucket based on the size storage: <size> that you specify.
: If ibm.io/quota-limit is set to false, the quota is not enforced on your PVC meaning that actual amount of storage in bytes might exceed the storage: <size> that you specified depending on your app.

ibm.io/endpoint
: If you created your IBM Cloud Object Storage service instance in a location that is different from your cluster, enter the private or public cloud service endpoint of your IBM Cloud Object Storage service instance that you want to use. For more information and an overview of available service endpoints, see [Additional endpoint information](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-advanced-endpoints). By default, the ibmc Helm plug-in automatically retrieves your cluster location and creates the storage classes by using the IBM Cloud Object Storage private cloud service endpoint that matches your cluster location. If your classic cluster is in a multizone metro, such as dal10, the IBM Cloud Object Storage private cloud service endpoint for the multizone metro, for example Dallas. To verify that the service endpoint in your storage classes matches the service endpoint of your service instance, run kubectl describe storageclass < storageclassname>.
The filter is defined in a [design document](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-design-documentsdesign-documents). string No filter. 
 heartbeat If no changes occurred during feed=longpoll or feed=continuous, an empty line is sent after this time in milliseconds. Any positive number No heartbeat 
 include_docs Include the document as part of the result. Boolean False 
 limit Maximum number of rows to return. Any non-negative number None 
 seq_interval Specifies how frequently the seq value is included in the response. Set a higher value to increase the throughput of _changes and decrease the response size. Note: In non-continuous _changes mode, the last_seq value is always populated. Any positive number 1 
 since Start the results from changes after the specified sequence identifier. For more information, see the [since information](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-get-changesthe-since-argument). Sequence identifier or now 0 
 style Specifies how many revisions are returned in the changes array. The main_only style returns only the current "winning" revision. The all_docs style returns all leaf revisions, including conflicts and deleted former conflicts. main_only, all_docs main_only 
 timeout Wait this number of milliseconds for data, then stop the response. If the heartbeat setting is also supplied, it takes precedence over the timeout setting. Any positive number 



Using include_docs=true might have [performance implications](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-using-viewsmulti-document-fetching).

See the following example that uses HTTP to get a list of changes made to documents in a database:

GET /$DATABASE/_changes HTTP/1.1

See the following example to get a list of changes made to documents in a database:

curl -H "Authorization: Bearer $API_BEARER_TOKEN" -X GET "$SERVICE_URL/orders/_changes?limit=1"
This can be set by using the [ibmcloud cos config crn](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cli-plugin-ic-cos-cliic-config) command.



* Parameters to provide:



* No parameters to provide.
* Optional: Sets the IBM Service Instance ID in the request.



* Flag: --ibm-service-instance-id



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT









 Extended Bucket Listing 



* Action: Print a list of all the buckets in a user's IBM Cloud Object Storage account. Buckets might be located in different regions.
* Usage:ibmcloud cos buckets-extended [--ibm-service-instance-id ID] [--marker KEY] [--prefix PREFIX] [--page-size SIZE] [--max-items NUMBER] [--output FORMAT]



* Note that you must provide a CRN if you are using IAM authentication. This can be set by using the [ibmcloud cos config crn](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cli-plugin-ic-cos-cliic-config) command.



* Parameters to provide:



* No parameters to provide.
* Optional: Sets the IBM Service Instance ID in the request.



* Flag: --ibm-service-instance-id



* Optional: Specifies the KEY to start with when listing objects in a bucket.



* Flag: --marker KEY



* Optional: Limits the response to keys that begin with the specified PREFIX.



* Flag: --prefix PREFIX



* Optional: The SIZE of each page to get in the service call. This does not affect the number of items returned in the command's output. Setting a smaller page size results in more calls to the service, retrieving fewer items in each call. This can help prevent the service calls from timing out.



* Flag: --page-size SIZE
Pricing 

IBM® Cloudant® for IBM Cloud® is priced based on the provisioned throughput capacity that you allocate for your instance, and the amount of data storage consumed. With IBM Cloudant, you can scale your provisioned throughput capacity up and down, and pay a pro-rated hourly rate. The provisioned throughput capacity is a reserved number of reads per second, writes per second, and global queries per second allocated to an instance. The throughput capacity setting is the maximum usage level for a given second. You can't exceed the reserved capacity for either reads, writes, or global queries. If you do, an HTTP 429 status code occurs that indicates the application is trying to exceed its provisioned throughput capacity allowance. IBM Cloudant usage is billed hourly.

The estimated monthly cost for a particular level of provisioned throughput and storage capacity can be determined by using the Cost Estimator on the [IBM Cloud® Catalog page](https://cloud.ibm.com/catalog/services/cloudant) for IBM Cloudant.

You can use the IBM Cloud pricing calculator to see estimated costs in other currencies by clicking Add to estimate from the IBM Cloudant catalog tile. Specify storage, capacity, and select the country whose currency you want to see.

Click Calculate cost and Save. Now, click Review estimate. Expand the estimate to see more details. If you save multiple estimates, you can then click Review estimate and compare them.

You can launch the IBM Cloud Dashboard. Click Resource list > Services > your instance > Manage > Capacity to view and change the provisioned throughput capacity, and see the hourly and approximate monthly costs.



 Changing Provisioned Throughput Capacity 

Let's assume you're building a mobile app with IBM Cloudant and don't yet know the capacity that you might need. In this case, the IBM Cloudant team recommends that you start with the lowest provisioned throughput capacity and increase it as needed by your application's usage over time. IBM Cloudant bills pro-rated hourly and changing the provisioned throughput capacity doesn't incur downtime.

The minimum provisioned throughput capacity for the Standard plan is 100 reads per second, 50 writes per second, and 5 global queries per second.
The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.







 ibmcloud event-notifications destination get 



* Action: Get specific Destination.

ibmcloud event-notifications destination get --id ID [--instance-id INSTANCE-ID]
* Parameters to provide:

--id ID (string)
: The unique identifier for destination. Required.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.

[--instance-id INSTANCE-ID] (string)
: The unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.







 ibmcloud event-notifications destination update 



* Action: Update existing Destination.

ibmcloud event-notifications destination update --id ID [--name NAME] [--description DESCRIPTION] [--certificate CERTIFICATE] [--config CONFIG] [--instance-id INSTANCE-ID]
* Parameters to provide:

--id (string)
: Unique identifier for destination. Required.

The maximum length is 36 characters. The minimum length is 36 characters.
Run the ibmcloud is volume-create command and specify the --snapshot option with the name or ID of the snapshot you're using to create the new volume. The volume is unattached, as indicated by the attachment state in the response.

This example creates the new volume from a snapshot that is specified by name.

$ ibmcloud is volume-create volume-4 general-purpose us-east-1 --snapshot snapshot-3
Creating volume volume-4 under account Test Account as user test.user@ibm.com...

ID r014-dee9736d-08ee-4992-ba8d-3b64a4f0baac
Name volume-4
CRN crn:v1:bluemix:public:is:us-east-1:a/a10d63fa66daffc9b9b5286ce1533080::volume:r014-dee9736d-08ee-4992-ba8d-3b64a4f0baac
Status pending
Attachment state unattached
Capacity 100
IOPS 3000
Bandwidth(Mbps) 393
Profile general-purpose
Encryption key -
Encryption provider_managed
Resource group defaults
Created 2023-06-29T16:14:59+00:00
Zone us-east-1
Health State inapplicable
Volume Attachment Instance Reference -
Active false
Unattached capacity update supported false
Unattached iops update supported false
Busy false
Tags -

For more information, see the CLI reference for [ibmcloud is volume-create](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-reference&interface=clivolume-create).





 Creating a data volume as an attachment to an existing virtual server instance 

You can use the instance-volume-attachment-add command to create a volume and attach it to an instance. The following example creates a volume with the spd profile, 100 GB capacity and 100 IOPS.
Make sure that you configure your image to use SSH for logging in to your virtual server.



For more information about enabling cloud-init, see [cloud-init documentation](https://cloudinit.readthedocs.io/en/latest/).





 Step 5 - Boot disk size 

Make sure that the image has a boot disk size of 10 - 250 GB. Images that are less than 10 GB are rounded up to 10 GB.

If you are customizing a virtual server to migrate from the Classic infrastructure, return to [Migrating a virtual server from the classic infrastructure](https://cloud.ibm.com/docs/vpc?topic=vpc-migrate-vsi-to-vpcmigrate-customize-image-vpc) and continue completing migration steps.





 Step 6 - Upload image to IBM Cloud Object Storage 

Upload your image to IBM Cloud Object Storage. On the Objects page of your IBM Cloud® Object Storage bucket, click Upload. You can use the Aspera high-speed transfer plug-in to upload images that are larger than 200 MB. For more information about uploading to IBM Cloud Object Storage, see [Upload data](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-upload).





 Next steps 

When your Linux custom image is created and available in IBM Cloud Object Storage, you can [import the custom image into VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-importing-custom-images-vpc) and [Onboard a virtual server image for VPC](https://cloud.ibm.com/docs/account?topic=account-catalog-vsivpc-tutorial&interface=ui). Make sure that you [Granted access to IBM Cloud Object Storage to import images](https://cloud.ibm.com/docs/vpc?topic=vpc-object-storage-prereq).

If you plan to use a private catalog to manage your custom images, you must first import that image into IBM Cloud VPC, and then onboard the virtual server image into a private catalog.
new-size
: Enter the new size in gigabytes (Gi) for your volume. For valid sizes, see [Deciding on the File Storage for Classic configuration](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_predefined_storageclass). The size that you enter must be greater than or equal to the current size of your volume. If you don't specify a new size, the current size of the volume is used.

new-iops
: For performance storage only. Enter the new number of IOPS that you want. For valid IOPS, see [Deciding on the File Storage for Classic configuration](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_predefined_storageclass). If you don't specify the IOPS, the current IOPS is used. If the original IOPS/GB ratio for the volume is less than 0.3, the new IOPS/GB ratio must be less than 0.3. If the original IOPS/GB ratio for the volume is greater than or equal to 0.3, the new IOPS/GB ratio for the volume must be greater than or equal to 0.3.

new-tier
: For endurance storage only. Enter the new number of IOPS per GB that you want. For valid IOPS, see [Deciding on the File Storage for Classic configuration](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_predefined_storageclass). If you don't specify the IOPS, the current IOPS is used. If the original IOPS/GB ratio for the volume is less than 0.25, the new IOPS/GB ratio must be less than 0.25. If the original IOPS/GB ratio for the volume is greater than or equal to 0.25, the new IOPS/GB ratio for the volume must be greater than or equal to 0.25.

Example output

Order 31020713 was placed successfully!.
> Storage as a Service
The following example shows the content of a volume attachment JSON file that defines a custom volume and specifies user tags.

[
{
"name": "myvolume-attachment",
"delete_volume_on_instance_delete": true,
"volume": {
"name": "myvolume",
"capacity": 100,
"iops": 1000,
"profile": {
"name": "custom"
},
"user_tags": {
"env:test"
}
}
}
]







 Attaching a Block Storage for VPC volume with the API 



 Attaching a Block Storage for VPC volume with the API 

Attach Block Storage for VPC volumes to an instance by directly calling the [REST APIs](https://cloud.ibm.com/apidocs/vpc).

Create a volume attachment for an instance to attach a Block Storage for VPC volume. Make a POST /instances call and specify volume_attachments.

POST/instances/{instance_id}/volume_attachments

The following example creates a volume attachment and specifies the volume by ID.

curl -X POST "$vpc_api_endpoint/v1/instances/$instance_id/volume_attachments?version=2021-04-20&generation=2" -H "Authorization: $iam_token" -d '{
"delete_volume_on_instance_delete": true,
"name": "my-volume-attachment-data-5iops",
"volume": {
"id": "d8b26921-1409-4c2f-9b46-39b5b6e0b945"
}
}'

A successful response indicates that the volume is attached.

{
"created_at": "2021-04-21T16:35:47.000Z",
"delete_volume_on_instance_delete": true,