vania-janet/multiturn-rag-retrieval-data huggingface dataset:
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. 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
"name": "tier-5iops",
"resource_type": "share_profile"
},
"resource_group": {
"crn": "crn:[...]",
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/875623bcde2b4ebda924d32640908845",
"id": "875623bcde2b4ebda924d32640908845",
"name": "Default"
},
"resource_type": "share",
"size": 2500,
.
.
.
}





 Expand file shares with Terraform 

To increase the capacity of a file share, use the ibm_is_share resource. When applied, the following example updates the share capacity to 300 GB.

resource "ibm_is_share" "example" {
name = "my-new-share"
size = 300
iops = 5000
profile = "dp2"
zone = "us-south-2"
}

For more information about the arguments and attributes, see [ibm_is_share](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_share).





 Next steps 

Mount and use your file shares:



* [Mounting file shares on Red Hat Linux](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-mount-RHEL)
* [Mounting file shares in CentOS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-mount-centos)
* [Mounting file shares on Ubuntu](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-mount-ubuntu)
IBM Cloudant 99.999% [Provisioned Throughtput Capacity](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-publicprovisioned-throughput-capacity) Local Storage: [Data is stored in triplicate across 3 servers for data durability](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-disaster-recovery-and-backupin-region-automatic-data-redundancy), in 3 availability zones where available [High availability, disaster recovery, and backup in a data center](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-publichigh-availability-disaster-recovery-and-backup-in-a-data-center) 
 IBM Cloud Databases for EnterpriseDB 99.999% [Performance](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-performance) Block Storage [Object Storage](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-security-compliancedata-resilience) [High-Availability](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-high-availability) 
 Db2 on Cloud 99.999% Block Storage Object Storage [High availability (HA)](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-ha) 
 IBM Db2 Warehouse on Cloud 99.999% Block Storage Object Storage [High availability (HA)](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-ha) 







 Developer tools services 

The following table describes the service level objectives (SLOs) for the high impact IBM Cloud developer tools services in a high availability configuration.



Table 14. Service level objectives (SLOs) for the IBM Cloud developer tools services

 Developer tools service Availability target High availability guidance
The number of GB used per month is 4 x 256 = 1024 MB or 1 GB per month. Assume that there are 24 x 30 = 720 hours in a month, so the application is charged for 1 x 720 = 720 GB-hours.

IBM Cloud offers a free tier of [Cloud Foundry application usage](https://cloud.ibm.com/docs/account?topic=account-accounts) that affects the overall cost for an application that's running, by reducing your costs.

Two Auto-Scaling policies (processor and memory)
: The Auto-Scaling policies are free of charge.

150 GB per month IBM Cloudant
: The IBM Cloudant for IBM Cloud service charges are based on data storage and the ability to access that data by provisioned throughput capacity denoted by lookups, writes, and queries per second.

Add up the number of GB and deduct the 20-GB free allowance. 130 GB is charged per month. The total storage price includes the following parts:

130 x 1 = $130
(1,000 / 100) x 0.25 = $2.50
(500 / 50) x 0.50 = $5.00
(50 / 5) x 5.00 = $50.00

The total price is 130 + 2.50 + 5.00 + 50.00 = $187.50.

20 GB inbound or outbound network traffic
: Inbound and outbound network traffic is free of charge.

When all the items are added, the total price of the application is $211.65.
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/containers?topic=containers-storage_portworx_planportworx_limitations). 









 VPC cluster limitations 

VPC clusters in IBM Cloud Kubernetes Service 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/containers?topic=containers-limitationstech_limits) apply.



 Compute 

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



VPC cluster compute limitations

 Category Description 

 Encryption The secondary disks of your worker nodes are encrypted at rest by default by the [underlying VPC infrastructure provider](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-aboutvpc-storage-encryption). However, you can't [bring your own encryption to the underlying virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-instances-byok).
Any volume of 7.8 TB or larger reaches the maximum limit at 2,040,109,451 inodes.



Table comparison
Table 1 shows the maximum number of inodes that are allowed based on the volume size. Volume sizes are in the left column. The numbers of inodes (files and directories) are on the right.

 Volume Size Inodes 

 20 GB 5,242,880 
 40 GB 10,485,760 
 80 GB 20,971,520 
 100 GB 26,214,400 
 500 GB 131,072,000 
 1 TB 268,435,456 
 4 TB 1,073,741,824 
 8 TB 2,040,109,451 
 12 TB 2,040,109,451 



* I ordered a File Storage for Classic volume in the wrong data center. Is it possible to move or migrate it to another data center?

You need to order new File Storage for Classic in the right data center, and then cancel the File Storage for Classic device that you ordered in the incorrect location. When the volume is canceled, the request is followed by a 24-hour reclaim wait period. You can still see the volume in the console during those 24 hours. Billing for the volume stops immediately. When the reclaim period expires, the data is destroyed and the volume is removed from the console, too.
* Measuring IOPS

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

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



* 16 KB * 6000 IOPS == 93.75 MB/sec
--sources ([TopicUpdateSourcesItem[]](https://cloud.ibm.com/docs/cli?topic=cli-event-notifications-clien-cli-topic-example-schema))
: List of sources.







 ibmcloud event-notifications topic delete 



* Action: Delete existing Topic.

ibmcloud event-notifications topic delete --id ID [--instance-id INSTANCE-ID] [--force]
* Parameters to provide:

--id ID (string)
: Unique identifier for topic. 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]{12}/.

[--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]/.

[--force] (Boolean)
: Activate to force resource deletion (to bypass the confirmation prompt).









 Subscriptions 

Operate on IBM Cloud Event Notifications subscription.

ibmcloud event-notifications subscription --help



 ibmcloud event-notifications subscription create 



* Action: Create new Subscription.

ibmcloud event-notifications subscription create [--name NAME] [--description DESCRIPTION] [--destination-id DESTINATION-ID] [--topic-id TOPIC-ID] [--attributes ATTRIBUTES] [--instance-id INSTANCE-ID]
| Allocation 3072mb
| Allocation per member 1024mb
| Minimum 3072mb
| Step Size 384mb
| Adjustable true

+ CPU
| Allocation 0
| Allocation per member 0
| Minimum 9
| Step Size 3
| Adjustable true

+ Disk
| Allocation 61440mb
| Allocation per member 20480mb
| Minimum 61440mb
| Step Size 3072mb
| Adjustable true

The deployment has three members, with 3072 MB of RAM and 61440 MB of disk allocated in total. The "per member" allocation is 1024 MB of RAM and 20480 MB of disk. The minimum value is the lowest the total allocation can be set. The step size is the smallest amount by which the total allocation can be adjusted.

The cdb deployment-groups-set command allows either the total RAM or total disk allocation to be set, in MB. For example, to scale the memory of the "example-deployment" to 2048 MB of RAM for each memory member (for a total memory of 6144 MB), you use the command:
ibmcloud cdb deployment-groups-set example-deployment member --memory 6144





 Scaling via the API 

The Foundation Endpoint that is shown on the Overview panel of your service provides the base URL to access this deployment through the API. Use it with the /groups endpoint if you need to manage or automate scaling programmatically.

To view the current and scalable resources on a deployment,

curl -X GET -H "Authorization: Bearer $APIKEY" https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/groups'

To scale the memory of a deployment to 2048 MB of RAM for each memory member (for a total memory of 6144 MB).

curl -X PATCH https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/groups/member' -H "Authorization: Bearer $APIKEY" -H "Content-Type: application/json" -d '{"memory": {
If you transgress, IBM Cloudant fails your requests with a status of 429: Too Many Requests. It’s your responsibility to look out for this case, and deal with it, which can be difficult when multiple app servers exist. How can they coordinate to ensure that they collectively stay under the requests-per-second limit?

IBM Cloudant’s official client libraries have some built-in provision for this use case that can be enabled, following a “back-off and retry” strategy.

This built-in provision is turned off by default to force you to think about it.

However, if you rely on this facility alone, you might eventually be disappointed. The back-off and retry strategy helps only in cases of temporary transgression, not a persistent butting up against your provisioned throughput capacity limits.

Your business logic must be able to handle this condition. Another way to look at it is that you get the allocation you pay for. If that allocation isn’t sufficient, the only solution is to pay for a higher allocation.

Provisioned throughput capacity is split into three different buckets: Lookups, Writes, and Queries. A Lookup is a “primary key” read, fetching a document based on its _id. A Write is storing a document or attachment on disk, and a Query is looking up documents by using a secondary index (any API endpoint that has a _design or _find in it).

You get different allocations of each and the ratios between them are fixed. This fact can be used to optimize for cost. You get 20 Lookups for every one Query (per second). You might find that you’re mainly hitting the Query limit, but you have plenty of headroom in Lookups. It might be possible to reduce the reliance on Queries through some remodeling of the data or perhaps doing more work client-side.

The corollary here though is that you can’t assume that any third-party library or framework optimizes for cost ahead of convenience. Client-side frameworks that support multiple persistence layers by using plug-ins are unlikely to be aware of this situation, or might be incapable of making such tradeoffs.
Capacity can be expanded up to 250 for boot volume, 16000 for custom and general-purpose profile volumes, 9600 for 5iops-tier profile volumes and 4800 for 10iops-tier profile volumes. Size can be only increased, not decreased.
* --profile: Name of the profile. The volume must be attached as data volume and be switched between IOPS tiers. Changing predefined IOPS tier prorfile to custom profile is not supported. Changing custom profile to predefined IOPS tier profile is not supported.
* --iops: Input/output operations per second for the volume, it is only applicable for custom profile volumes. For the IOPS range, refer to [Onboarding software to your account](https://cloud.ibm.com/docs/docs/vpc?topic=vpc-block-storage-profilescustom).. The volume must be attached as data volume.
* --tags: Tags for this resource.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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









 Snapshots 

The following section provides information about CLI commands for snapshots.



 ibmcloud is snapshots 

List all snapshots.

ibmcloud is snapshots [--volume VOLUME] [--tag TAG_NAME] [--source-image SOURCE_IMAGE] [--backup-policy-plan BACKUP_POLICY_PLAN --backup-policy BACKUP_POLICY] [--clones-zone-name CLONES_ZONE_NAME] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME | --all-resource-groups] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is snapshots
* ibmcloud is snapshots --volume r134-f13fc172-22e0-4e5b-ab81-63f5fe8b3ea0
On the volume details page, locate Size. The current IOPS profile and volume size are displayed.
5. Click the pencil icon. Alternatively, click the Actions menu and select Expand block storage volume.
6. In the panel, increase the volume size in GB up to 16,000 GB.

The maximum size that you can expand to is based on the selected IOPS profile or custom volume settings. The UI indicates the maximum capacity for the selected profile. For a custom profile, you can expand the volume based on [sizing limits](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes&interface=uiexpandable-volume-limitations). When you increase the size of the volume, max IOPS and throughput are calculated for the expanded volume.
7. Review the estimated monthly order summary for your geography and new pricing.
8. If you're satisfied, click Save and continue.



Your new block storage allocation is available in a few minutes.





 Expand block storage volumes from the CLI 



 Before you begin 

Before you can use the CLI, you must install the IBM Cloud CLI and the VPC CLI plug-in. For more information, see the [CLI prerequisites](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup).



1. Log in to the IBM Cloud.

ibmcloud login --sso -a cloud.ibm.com

This command returns a URL and prompts for a passcode. Go to that URL in your browser and log in. If successful, you get a one-time passcode. Copy this passcode and paste it as a response on the prompt. After successful authentication, you are prompted to choose your account. If you have access to multiple accounts, select the account that you want to log in as. Respond to any remaining prompts to finish logging in.
2. Select the current generation of VPC.

ibmcloud is target --gen 2
See the [VPC API change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log5-july-2022).







 17 August 2021 



 For all API version dates 

File storage for VPC. Accounts that have been granted special approval to preview this feature can now increase file share size in gigabyte increments up to 32 TB (depending on the file share's profile). The increase takes effect immediately. For more information, see [Expanding file share capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-expand-capacity&interface=api). You can also specify the maximum input/output operations per second (IOPS) when [creating](https://cloud.ibm.com/apidocs/vpc-betacreate-share) a file share, within the range available for its size. For more information, see [Custom IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilescustom).







 10 August 2021 



 For all version dates 

Beta VPC instance metadata API. Accounts that have been granted special approval to preview this feature can now preview the new beta IBM Cloud® Virtual Private Cloud (VPC) [Instance Metadata API](https://cloud.ibm.com/apidocs/vpc-metadata-beta). This API provides access to VPC instance metadata, including instance initialization data, network interfaces, volume attachments, public SSH keys, and placement groups. Use the [VPC create instance API](https://cloud.ibm.com/apidocs/vpc-betacreate-instance) or the [VPC update instance API](https://cloud.ibm.com/apidocs/vpc-betaupdate-instance) to enable or disable the metadata service endpoint for a particular instance. For more information, see [About VPC Instance Metadata](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-about).







 27 July 2021
"resource_crn" : "crn:v1:staging:public:cloud-object-storage:global:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::",
"resource_name" : "cos_bucket_instance",
"resource_type" : "ibm_cos_bucket",
"resource_tainted" : false,
"resource_group_name" : ""
} ] ! ! ! ! ,
"resources_count" : 2
}
<-- </section "id="section-project-list-config-resources-cli-output" "> --><-- </section "id="section-project-cli-list-config-resources-command" "> --><-- <section "id="section-project-cli-config-drafts-command" "> --> ibmcloud project list-config-drafts Returns a list of previous and current configuration drafts in a specific project. ibmcloud project list-config-drafts --project-id PROJECT-ID --config-id CONFIG-ID
<-- <section "id="section-project-list-config-drafts-cli-options" "> --> Command options --project-id (string): The unique project ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] +$/.
--config-id (string): The unique configuration ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] ! ! ! ! +$/.
At the end of the month, you can see the average provisioned throughput capacity for each field: LOOKUPS_PER_MONTH, WRITES_PER_MONTH, and QUERIES_PER_MONTH.
* Provisioned throughput capacity model FAQ

 Provisioned throughput capacity model FAQ 

IBM® Cloudant® for IBM Cloud® calculates your provisioned throughput capacity based on these operation types: Read, Write, and Global Query.



IBM Cloudant calculates provisioned throughput capacity by totaling the usage for each request class per second, where 1 second is a sliding window. When an account exceeds the total number of a request class that is allotted by its plan, IBM Cloudant rejects subsequent requests of that request class. No new requests are accepted until the usage of that request class inside the sliding window falls under the allowed limit. The sliding 1-second window is any consecutive period of 1,000 milliseconds.

For example, the Standard plan instance limits you to 200 reads per second. When you exceed 200 read requests, IBM Cloudant rejects future read requests made during the sliding 1,000-millisecond window. Read requests resume when the number of read requests for that time period is less than 200.

Request class units do not necessarily have a one-to-one mapping with HTTP requests. A single HTTP request can consume multiple units of a request class or classes if, for example, it reads multiple documents or both reads and writes.





When you exceed the number of allowed events, IBM Cloudant generates a [429 Too Many Requests](https://cloud.ibm.com/apidocs/cloudantlist-of-http-codes) response. You must make sure ahead of time that your applications can handle 429 responses.

If you use the most recent versions of the [client libraries](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-client-libraries) that IBM Cloudant supports, you can set up your applications to handle 429 responses. This step is important because most client libraries don't automatically attempt to retry a request when a 429 response occurs. You need to verify that your application handles 429 responses correctly because IBM Cloudant limits the number of retries.
"id" : "exampleString",
"rules" :
{
"enabled" : true,
"event_type_filter" : "exampleString",
"notification_filter" : "exampleString",
"rule_id" : "exampleString"
}
]
}
]









 ibmcloud event-notifications topic list 



* Action: List all Topic.

ibmcloud event-notifications topic list [--limit LIMIT] [--offset OFFSET] [--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 topic get 



* Action: Get specific Topic.

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

--id ID (string)
: Unique identifier for topic. Required.

The maximum length is 36 characters. The minimum length is 36 characters.