vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The available plans include Lite and Standard. When you select a plan, Capacity displays, and the Cost estimator shows the monthly charge for the selected plan. By default, the [Lite plan](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-publiclite-plan) is selected.



 Lite plan 

The Lite plan is free, and is designed for development and evaluation purposes. All of IBM Cloudant's functions are included, but Lite plan instances have a fixed amount of provisioned throughput capacity and data storage. The provisioned throughput capacity is fixed at 20 reads per second, 10 writes per second, and 5 global queries per second, and data storage is capped at 1 GB.

Storage usage is checked daily. If you exceed your 1-GB storage limit, requests to the IBM Cloudant instance receive a 402 status code with the following error message, Account exceeded its data usage quota. An upgrade to a paid plan is required. A banner also appears on the IBM Cloudant Dashboard. You can still read and delete data. However, to write new data, you have two options. First, you can upgrade to a paid [Standard plan](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-publicstandard-plan), which removes the write limitation immediately. Alternatively, you can delete data so that your total storage falls under the 1-GB limit and wait until the next daily storage check runs for your instance to allow writes again.

If you want to store more than one GB of data, or be able to scale provisioned throughput capacity, move to the [Standard plan](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-publicstandard-plan).

You're limited to one IBM Cloudant Lite plan instance per IBM Cloud account. If you already have one Lite plan instance, you can't create a second Lite plan instance, or change a Standard plan instance to a Lite plan. If you try, you see the following message. You can have only one instance of a Lite plan per service.
For more FAQs, see the [file](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-file-storage-faqsprovision) and [block](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-block-storage-faqsauthlimit) storage docs. If you want to mount more volumes, [contact IBM Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In your support ticket, include your account ID and the new file or block storage volume quota that you want. 
 Portworx Review the [Portworx limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_planportworx_limitations). 
 File storage Because of the way that IBM Cloud NFS file storage configures Linux user permissions, you might encounter errors when you use file storage. If so, you might need to configure [Red Hat OpenShift Security Context Constraints](https://docs.openshift.com/container-platform/4.11/authentication/managing-security-context-constraints.html) or use a different storage type. 









 VPC cluster limitations 

VPC clusters in Red Hat OpenShift on IBM Cloud are released with the following limitations. Additionally, all the underlying [VPC quotas, VPC limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas), [VPC service limitations](https://cloud.ibm.com/docs/vpc?topic=vpc-limitations), and [regular service limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationstech_limits) apply.



 Compute 

Keep in mind that the [service](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationstech_limits) limitations also apply.



VPC cluster compute limitations
Volume attachments See [Volume attachment limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits). 
 Portworx Review the [Portworx limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_planportworx_limitations). 
 Block Storage for VPC The default storage class in VPC clusters can not be changed. However, you can [create a custom storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-customize-storage-class). 









 Satellite cluster limitations 

Review the following limitations for [Red Hat OpenShift on IBM Cloud clusters that you create in a Satellite location](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusters). Keep in mind that the [service](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationstech_limits) limitations also apply.



Satellite cluster limitations

 Category Description 

 Cluster add-ons Review the [unsupported managed add-ons for Red Hat OpenShift clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-managed-addonsaddons-satellite) in a Satellite location. For example, the cluster autoscaler and Istio are not supported. 
 Logging and monitoring You can't currently use the Red Hat OpenShift on IBM Cloud console or the observability plug-in CLI (ibmcloud ob) to enable logging and monitoring for Satellite clusters.
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 false
Created 2023-06-29T18:14:57+00:00

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





 Detaching a volume from the CLI 

Use the instance-volume-attachment-detach command to detach a volume from an instance and delete the volume attachment. The Block Storage for VPC volume is not deleted; you can later [attach it to another instance](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storage-cli).

In the syntax for this command, INSTANCE is the ID or name of the instance. VOLUME_ATTACHMENT is the ID or name of the volume attachment. You can specify multiple volume attachments. For more information about volume attachments, see the CLI reference for [creating a volume attachment](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-reference&interface=cliinstance-volume-attachment-add).

ibmcloud is instance-volume-attachment-detach INSTANCE (VOLUME_ATTACHMENT1 VOLUME_ATTACHMENT2 ...) [--output JSON] [-f, --force] [-q, --quiet]

$ ibmcloud is instance-volume-attachment-detach kj-test-ro one-true-pairing
This will delete volume attachment one-true-pairing and cannot be undone. Continue [y/N] ?> y
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. When you need to scale up (or down), you can scale in increments of these blocks of capacity. Assuming the instance has less than the 20 GB of storage that is included in the Standard plan, no storage costs are incurred. Go to the provisioned throughput capacity setting from the IBM Cloudant Dashboard > Account > Capacity tab, which is shown in the following screen capture:

Zoom

![The Account window contains the Capacity, Announcements, CORS, and Settings tabs.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/cloudant-dashboard.png)

Figure 1. IBM Cloudant Dashboard Capacity tab

The capacity slider shows the hourly cost of the provisioned throughput capacity. The monthly amount is an estimate based on an average of 730 hours per month. The cost in any month can be slightly different depending on the number of hours in the month.

Reads, writes, and global queries can't be scaled independently. Use the slider to select the number of blocks of provisioned throughput capacity based on the maximum limit of either reads per second, writes per second, or global queries per second as required for your application. For example, if your application requires 1,000 reads per second, use the slider to select the capacity that offers 1,000 reads per second, 500 writes per second, and 50 global queries per second. Select this capacity even if you don't need the corresponding number of writes or global queries.





 Data usage pricing
[Upload icon](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/upload.png).
3. Drag a file or browse to select a file from your computer.

Important: The maximum CSV file size is 10 MB. If your CSV file is larger, consider splitting it into multiple files and uploading them separately.
4. Click Upload.

The file is validated and uploaded, and the system begins to train itself on the new data.



You can view the uploaded intents and the corresponding examples on the Intents tab. You might need to refresh the page to see the new intents and examples.





 Resolving intent conflicts ![Plus or higher plans only](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/plus.png) 

This feature is available only to users of paid plans.

The Watson Assistant application detects a conflict when two or more intent examples in separate intents are so similar that Watson Assistant is confused as to which intent to use.

To resolve conflicts:



1. From the Intents page, review any intents with conflicts.

![Shows an intent list with a conflict](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/intent-conflicts.png)
2. Click an intent with a conflict to open it. Find the user example that is causing the conflict, and then click Resolve conflicts.

!
To enable your account for VRF, refer to [VRF on IBM Cloud](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-setting-up-access-to-your-classic-infrastructure-from-vpcvrf-conversion).





 cos_file_too_large 

Message: The file from Cloud Object Storage is greater than 100 GB.

The file specified is too large. Only files less than 100 GB are allowed.





 cos_invalid_file_extension 

Message The URI provided contains an unsupported file extension.

The file extension in the URI must be .vhd.





 cos_invalid_qcow2_format 

Message The image provided contains an invalid qcow2 formatted image.

Even though the import image file name has a .qcow2 extension, the contents is not valid.





 cos_not_authorized 

Message: You are not authorized to access the Cloud Object Storage resource.

This error occurs if a user tries to import an image from a Cloud Object Storage to which they do not have access. Use the [Granting access between services](https://cloud.ibm.com/docs/account?topic=account-serviceauth) to help you grant authorization from the image service to the Cloud Object Storage bucket.





 cos_not_found 

Message: Cloud Object Storage resource not found.

The Cloud Object Storage resource specified could not be found. Verify that the resource identification is correct.





 cos_region_mismatch 

Message: Cloud Object Storage resource not found in the target region.

The Cloud Object Storage bucket specified could not be found in the target region. Make sure the bucket exists in the target region.





 cos_scheme_uri_invalid 

Message: The Cloud Object Storage URI provided is not in the correct format.

This error occurs if the URI has an incorrect scheme. The URI should follow this format: cos://<region>/<bucket>/<sourceFile>





 cos_uri_not_supported 

Message: The Cloud Object Storage URI that was specified is not supported.
Finding your IBM Cloudant plan 

You can subscribe to different IBM Cloudant plans, including the Lite, Standard, or Enterprise plans.



 Step 1: Finding your plan 

The following steps show where you can see the type of plan that you selected.



1. Go to the [IBM Cloud Dashboard](https://cloud.ibm.com/).
2. Authenticate with your username and password.
The IBM Cloud Dashboard opens to the Resource list.
3. Click an instance to find more information.
4. Click Plan. A checkmark indicates the plan that you use as shown in the following screen capture. For more information, see the [Migration FAQ](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-faq-migration).

Zoom

![Standard dashboard includes a serverless scaling of throughput and storage. Includes 20 GB of free data storage, extra storage metered. Users can adjust provisioned throughput capacity in blocks of 100 reads/sec, 50 writes/sec, 5 global queries/sec. Max JSON document size of 1 MB. $1.00 USD/GB of data storage. $0.25 USD/Read capacity. $0.50 USD/Write capacity. $5.00 USD/Global Query capacity.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/ibmcloud_instance_standard_plan.png)

Figure 1. Standard dashboard

If the Plan tab indicates that you're on the Standard plan, you don't need to read any further. You're already on a paid SLA-backed IBM Cloudant service. No further action is required.







 Step 2: Finding your legacy Enterprise plan 

You can find your Enterprise plan in the IBM Cloudant Dashboard by following these steps.



1. Open the IBM Cloudant Dashboard.
curl "$SERVICE_URL/$DATABASE/_changes?feed=continuous&include_docs=true&since=now&filter=mydesigndoc/myfilter"

The ordering of documents within the _changes feed is not always the same. In other words, changes might not appear in strict time order. The reason is that data is returned from multiple IBM Cloudant nodes, and eventual consistency rules apply.





 Replication pitfalls 

To replicate successfully, the sum of the document size and all attachment sizes must be less than the maximum request size of the target cluster. For example, if the maximum HTTP request size is 11 MB, then the following scenarios apply:



Table 1. Various scenarios based on maximum HTTP request size 11 MB

 Document size Attachment size Total size Replicates? 

 1 MB Five 2-MB attachments 11 MB Yes 
 1 MB One 10-MB attachment 11 MB Yes 
 1 MB One hundred 1-MB attachments 101 MB No 



Several considerations apply when you use replication.



 Incorrect user permissions 

For replication to proceed optimally when you replicate from database "a" to database "b", the credentials that are supplied must have:



* _reader and _replicator permissions on database "a".
* _writer permissions on database "b".



API keys are generated in the IBM Cloudant Dashboard or through the [API](https://cloud.ibm.com/apidocs/cloudant). Each key can be given individual permissions that relate to a specific IBM Cloudant database. IBM Cloudant must be able to write its checkpoint documents at the "read" end of replication, otherwise no state is saved and replication cannot resume from where it stopped. If the state is not saved, it can lead to performance problems when replication of large data sets resumes. The reason is that without checkpoints, the replication process restarts from the beginning each time that it is resumed.





 Replication document is conflicted 

Another consequence of setting user permissions incorrectly is that the _replicator document becomes conflicted. The _replicator document records the current state of the replication process. In an extreme case, the document can become huge because it contains many unresolved conflicts.
* When you expand a file share that was created from a custom or dp2 profile, the capacity is increased, but the IOPS remains the same unless you choose to [adjust IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iops).
* Maximum IOPS for a file share is capped at 48,000 IOPS if it is accessed by a single host. For a file share that is accessed by multiple hosts, IOPS can reach up to 96,000 IOPS.
* After a file share is expanded, you can't reduce its size.







 Expand file share capacity in the UI 

Follow these steps for expanding file share capacity in the UI:



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > File Shares.
2. The File Shares for VPC list page shows all file shares that were created in that zone. Click the name of the file share to get to the details page.
3. On the file shares details page, expand the Actions menu.
4. Select Expand file share. The Expand file share size panel shows the current size of the file share (in GBs), and the profile to which it is associated. Alternatively, you can also click the edit icon next to the file share size information.
5. Enter a larger file share size, based on the maximum allowed for the [file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles). The default is the current size + 1 GB.
6. Review the estimated monthly order summary for your geography and new pricing.
7. If you're satisfied, click Save and continue.



Your new file storage allocation is available in a few minutes. If your requirements change, you can increase capacity again after the file share size is increased and when it's in stable state.
Known issues and limitations 

IBM® Cloud Shell includes the following known issues and limitations that might impact your experience.



  Known issues 



*  Your Cloud Shell workspace includes 500 MB of temporary storage. If you use all of your storage space, your connection to Cloud Shell is lost. To access Cloud Shell, you must restart it, which removes all of your files.
*  Adding files outside of your /home/<user-name> home directory can cause Cloud Shell to close, particularly if the files are large.
*  You can mount (or mount by using a volume switch) your home directory or subdirectories of your home directory to your Docker container. If you mount to another location, an error results.







  Limitations 



*  IBM Cloud Shell runs in the Dallas (us-south), Frankfurt (eu-de), and Tokyo (jp-tok) regions only. You can access resources in any region.
*  Usage is limited to 50 hours of weekly use. For more information, see [Tracking your usage](https://cloud.ibm.com/docs/cloud-shell?topic=cloud-shell-shell-uiusage-limit).
*  IBM Cloud Shell does not support [trusted profiles](https://cloud.ibm.com/docs/account?topic=account-create-trusted-profile&interface=ui). If you start IBM Cloud Shell and see an Internal Error, ensure that you're not using the [IAM Trusted profiles](https://cloud.ibm.com/iam/trusted-profiles) feature to log in to your IBM Cloud account.
You can find a full list of upgraded data centers and available features [here](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-selectDC).





 How can I find the correct mount point for my File Storage for Classic? 

All encrypted File Storage for Classic volumes that are provisioned in the enhanced data centers have a different mount point than nonencrypted volumes. To ensure that you're using the correct mount point, view the mount point information in the Volume Details page in the UI. You can also access the correct mount point through an API call: SoftLayer_Network_Storage::getNetworkMountAddress().





 How many volumes can I provision? 

By default, you can provision a combined total of 700 Block and File Storage for Classic volumes. To increase your limit, contact your sales representative. For more information, see [Managing storage limits](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managinglimits).





 How many instances can share the use of a provisioned File Storage for Classic volume? 

The default limit for number of authorizations per file volume is 64. To increase this limit, contact your sales representative.





 How many File Storage for Classic volumes can be attached to a single host? 

That depends on what the host operating system can handle, it’s not something that IBM Cloud® limits. Refer to your OS Documentation for limits on the number of file shares that can be mounted.





 How many files and directories are allowed for specific file volume sizes? What is the maximum number of inodes allowed per volume size? 

The number of files a volume can contain is determined by how many inodes it has. An inode is a data structure that contains information about files. Volumes have both private and public inodes. Public inodes are used for files that are visible to the customer and private inodes are used for files that are used internally by the storage system. The maximum number of files setting is 2 billion. However, this maximum value can be configured only with volumes of 7.8 TB or larger.
"to" :["entest@gmail.com"],
"add_notification_payload": true,
"reply_to_mail": "en@ibm.com",
"reply_to_name": "EYS ORG",
"from_name":"ABC ORG"
}
* The following example shows the format of the SubscriptionCreateAttributes object for slack.

{
"attachment_color" : "FF0000"
}
* The following example shows the format of the SubscriptionUpdateAttributes object.

{
"to" : [ "exampleString" ],
"recipient_selection" : "only_destination"
}









 ibmcloud event-notifications subscription list 



* Action: List all Subscription.

ibmcloud event-notifications subscription list [--offset OFFSET] [--limit LIMIT] [--search SEARCH] [--instance-id INSTANCE-ID]
* Parameters to provide:

--limit LIMIT (int64)
: The page limit for paginated results.

The maximum value is 100. The minimum value is 1.

--offset OFFSET (int64)
: The offset for paginated results.

The minimum value is 0.

--search SEARCH (string)
: The search string for filtering results.

The maximum length is 100 characters. The minimum length is 0 characters. The value must match regular expression /[a-zA-Z0-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 subscription get 



* Action: Get specific Subscription.
If you want to store more than one GB of data, or be able to scale provisioned throughput capacity, move to the [Standard plan](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-ibm-cloud-publicstandard-plan).

You're limited to one IBM Cloudant Lite plan instance per IBM Cloud account. If you already have one Lite plan instance, you can't create a second Lite plan instance, or change a Standard plan instance to a Lite plan. If you try, you see the following message. You can have only one instance of a Lite plan per service. To create a new instance, either delete your existing Lite plan instance or select a paid plan.





 Standard plan 

The IBM Cloudant Standard plan is available to all paid IBM Cloud® accounts, either as pay-as-you-go or subscription, and scales to meet the needs of your application. The Standard plan is priced based on two factors: the provisioned throughput capacity that is allocated, and the amount of data that is stored in the instance.

Pricing is pro-rated hourly with a starting provisioned throughput capacity of 100 reads per second, 50 writes per second, and 5 global queries per second. This rate is equal to a starting cost of USD $0.105 per hour. You can toggle the provisioned throughput capacity up or down by using the user interface or API. Toggle in increments of 100 reads per second, 50 writes per second, and 5 global queries per second. Costs are calculated for the provisioned throughput capacity that is allocated and not on the metered volume of requests. The Standard plan includes 20 GB of data storage. If you store more than 20 GB, you're charged a defined cost per GB per hour.

Refer to the IBM Cloud Pricing Calculator in the dashboard for pricing at different capacities and currencies, and the [pricing](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-pricingpricing) information for examples to estimate costs.





 Dedicated Hardware plan