vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: Access to Schematics using IAM allowed IP addresses has been replaced with [context based restrictions](https://cloud.ibm.com/docs/schematics?topic=schematics-access-control-cbr).

The terraform.tfstate state file size maximum limit is less than 2 MB.
: The Schematics Workspace creation by using terraform.tfstate file fails due to the limitation in state file size. Documentation includes [FAQ](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqwks-statefile-limit), [troubleshooting guide](https://cloud.ibm.com/docs/schematics?topic=schematics-wks-failurewks-new-fails1), and a note in [schematics workspace new](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-new) --state argument.





 22 March 2023 

Schematics Agent beta-1 release.
: Schematics announces its [beta-1 release](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-beta1-limitations) of Schematics Agents to extend Schematics availability to reach your private, or on-premises infrastructure. Check the following content to learn about Schematics Agents beta-1 releases.



* [Landing page](https://cloud.ibm.com/docs/schematics) to start your Schematics Agent engagement.
* [About Schematics Agent](https://cloud.ibm.com/docs/schematics?topic=schematics-agentb1-about-intro).
| Minimum 6
| Step Size 2
| Adjustable true

+ Disk
| Allocation 30720mb
| Allocation per member 10240mb
| Minimum 30720mb
| Step Size 2048mb
| Adjustable true

The deployment has three members, with 6144 MB of RAM and 30720 MB of disk allocated in total. The "per member" allocation is 2048 MB of RAM and 10240 MB of disk. The minimum value is the lowest the total allocation that 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 4096 MB of RAM for each memory member (for a total memory of 12288 MB), you use the command:
ibmcloud cdb deployment-groups-set example-deployment member --memory 12288





 Scaling in 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 4096 MB of RAM for each memory member (for a total memory of 12288 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": {
"allocation_mb": 12288
}
}'
* If you set quota limits for storage in your free or standard plan, you can also [increase this quota limit](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_set) to enable the pushing of new images again.



The following example is for the standard plan:
: Your current quota limit for storage is set to 1 GB. All private images that are stored in the namespaces of your IBM Cloud account already use 900 MB of this storage. You have 100 MB storage available until you reach your quota limit. One user wants to push an image with a size of 2 GB on the local computer. Because the quota limit is not yet reached, Container Registry allows the user to push this image.

After the push, Container Registry determines the actual size of the image in your namespace, which can vary from the size on your local computer, and checks whether the limit for storage is reached. In this example, the storage usage increases from 900 MB by 2 GB. With your current quota limit set to 1 GB, Container Registry prevents you from pushing more images to the namespace.





 Pull traffic quota limits 

When you reach or exceed the quota limits for your plan, you can't pull any images from the namespaces in your IBM Cloud account until you complete one of the following tasks.



* Wait for the next billing period to start.
* [Upgrade to the standard plan](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_plan_upgrade).
* [Increase your quota limits for pull traffic](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_set).



Pull traffic across public connections counts toward usage and quota. Pull traffic across private connections doesn't count.

The following example is for the standard plan:
: In the month, your quota limit for pull traffic is set to 5 GB. You already pulled images from your namespaces and used 4.5 GB of this pull traffic. You have 0.5 GB pull traffic available until you reach your quota limit.
As an example, the Lite plan offers 20 reads per second, 10 writes per second, 5 global queries per second, and 1 GB of storage for free. This plan is ideal when you're evaluating the product and during product development. When your application goes into QA or production, switch to the Standard plan to scale the instance. The Standard plan's smallest capacity has 100 reads per second, 50 writes per second, 5 global queries per second, and 20 GB of storage for USD$76.65 per month. You can buy extra storage, which is charged by the GB.

By using the slider in the IBM Cloudant Dashboard, you can reserve a smaller or larger capacity for your IBM Cloudant service whenever you need it:

Zoom

![You can increase or decrease your capacity for IBM Cloudant service by using the slider.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/slider.png)

Figure 1. Slider

The amount that you can change the throughput capacity is limited to a maximum of 10 units per change with a maximum of one change per hour. Notice the "change limit" point on the slider. Changes downward are unlimited in size, but still subject to the time limit.

You're billed on the highest capacity that is selected in any given hourly window. Your database throughput can scale up to deal with seasonal demands and scale down again for the quiet times. Your monthly bill is always predictable; upgrades are automatic; and your SLA is [99.99%](https://www.ibm.com/support/customer/csol/terms?id=i126-6627&lc=endetail-document).

If you exceed your quota of reads, writes, and global queries in a given second, the IBM Cloudant API responds with a 429: too many requests HTTP response. Your application might retry the request later. You can use our official libraries to retry such requests with an exponential back off.
Objects are limited to 200 MB when uploaded through the console unless you use the Aspera High-Speed Transfer plug-in. Larger objects (up to 10 TB) can also be split into parts and uploaded in parallel using the API. Object keys can be up to 1024 characters in length, and it's best to avoid any characters that might be problematic in a web address. These special characters (?, =, <, etc.) might cause unwanted behavior if not URL-encoded. For more information, see the [Cloud Object Storage tutorial](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage).





 Generating secret and access keys with Hash-based Message Authentication Code (HMAC) 



1. You can generate secret and access keys when you create the service credentials for the IBM Cloud Object Storage. To create the service credentials, you must have Writer access for the Object Storage bucket.
2. Select New credential under Service credentials in the Cloud Object Storage pane.
3. Complete all of the wanted fields for adding a credential. Remember to check Include HMAC Credential for obtaining a Hash-based Message Authentication Code (HMAC) credential.
4. Find your new service credential in the service credentials table.

To view your credential information, such as your secret and access keys, click the arrow to the right of View credentials. For more information, see [Service credentials](https://cloud.ibm.com/docs/services/cloud-object-storage?topic=cloud-object-storage-service-credentials) and [Bucket permissions](https://cloud.ibm.com/docs/services/cloud-object-storage?topic=cloud-object-storage-iam-bucket-permissions).







 Using a custom boot image to provision a new instance 

Complete the following steps to provision a new instance by using a custom boot image.
3 IOPS/GB General-purpose workloads 10-32,000 96,000 
 5 IOPS/GB High I/O intensity workloads 10-9,600 48,000 
 10 IOPS/GB Demanding storage workloads 10-4,800 48,000 



The total maximum IOPS is rounded up to the next multiple of 10 when the IOPS calculation results in IOPS less than or equal to 48,000 IOPS. The total maximum IOPS is rounded up to the next multiple of 100 for IOPS calculations that result in IOPS greater than 48,000 IOPS up to 96,000 IOPS.





 Custom IOPS profile 

Custom IOPS profiles specify the total IOPS for the file share within the range for its size. File shares that use a custom IOPS profile can have IOPS performance level in the range 100-48000 IOPS.

Table 4 shows the available IOPS ranges based on file share size.



Table 4. Available IOPS based on file share size.

 File Share size (GB) IOPS range (IOPS) 

 10 - 39 100 - 1,000 
 40 - 79 100 - 2,000 
 80 - 99 100 - 4,000 
 100 - 499 100 - 6,000 
 500 - 999 100 - 10,000 
 1,000 - 1,999 100 - 20,000 
 2,000 - 3,999 200 - 40,000 
 4,000 - 7,999 300 - 40,000 
 8,000 - 9,999 500 - 48,000 
 10,000-16,000 1000-48,000 



The total maximum IOPS is rounded up to the next multiple of 10 when the IOPS calculation results in IOPS less than or equal to 48,000 IOPS.







 View profiles in the UI 

When you [create a file share in the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create&interface=uifile-storage-create-ui), under Profiles, select a profile.





 View profiles from the CLI 

To view the list of available profiles from the CLI, run the following command.

ibmcloud is share-profiles

The command returns the following profiles:
Storage that was provisioned before the release of this feature, during April 2017 - 14 December 2017, can be increased to 10 times its original size and no more. Storage that was provisioned after 14 December 2017 can be increased up to 12 TB.

Existing size limitations for Block Storage for Classic that was provisioned with Endurance still apply (up to 4 TB for 10 IOPS tier and up to 12 TB for all other tiers).





 Resizing storage in the UI 



1. From the IBM Cloud® console, click the menu![Menu icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/icon_hamburger.svg) icon. Then, click Infrastructure![Classic icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/classic.svg) > Storage > Block Storage for Classic.
2. Select the iSCSI volume from the list and click the ellipsis ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg) > Modify volume.
3. Enter the new storage size in GB.
4. Review your selection and the new pricing.
5. Click Modify.
6. Your new storage allocation is available in a few minutes.



The Operating system must rescan the storage and reload the multipath device map to reflect the expanded volume size. Resizing of the partition and file system are also required. For more information about expanding the file system, see your OS Documentation.
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).









 Topics 

Operate on IBM Cloud Event Notifications topic.

ibmcloud event-notifications topic --help



 ibmcloud event-notifications topic create 



* Action: Create new Topic.

ibmcloud event-notifications topic create --name NAME [--description DESCRIPTION] [--sources SOURCES] [--instance-id INSTANCE-ID]
* Parameters to provide:

--name NAME (string)
: Name of the topic. Required.

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)
: Description of the topic.

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-_/.?:'";,+=@$%^&()]/.

[--instance-id INSTANCE-ID] (string)
: 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]/.
IBM Cloudant pricing is based on the provisioned throughput capacity that you set for your instance, and the amount of data storage you use.

With IBM® Cloudant® for IBM Cloud®, you can increase or decrease your provisioned throughput capacity as needed, and pay pro-rated hourly. 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.

For more information, see [IBM Cloudant Pricing](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-pricing).



You can change your provisioned throughput capacity and see your current capacity settings in the IBM Cloudant Dashboard. Launch IBM Cloudant Dashboard > Account > Capacity to view and change your provisioned throughput capacity and see the hourly and approximate monthly costs. You can also use the IBM Cloud® pricing calculator to see estimates in other currencies.





The Lite plan includes 1 GB of storage. If you exceed the limit, IBM Cloudant blocks your account from writing new data until you delete enough data to be under the 1-GB limit, or upgrade to a higher plan.

The first 20 GB of storage comes free with the Standard plan. You can store as much data as you want. Any storage over the 20 GB limit costs $0.0014 per GB per hour, which is approximately $1 per GB per month.





You can see your current and historical usage bills in the IBM Cloud Dashboard. Go to Manage > Billing and usage > Usage. Here you can see the total charges and usage for the month by service, plan, or instance. Only the hourly costs that are accrued for the current month and time are available. 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.



* Can I change my capacity setting?

You can change your provisioned throughput capacity and see your current capacity settings in the IBM Cloudant Dashboard.
The maximum length is 255 characters. The minimum length is 1 characters. The value must match regular expression /[!a-zA-Z 0-9-_/.?:'";,+=@$%^&()]/.

--description DESCRIPTION (string)
: The description for source.

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-_/.?:'";,+=@$%^&()]/.

--enabled ENABLED (Boolean)
: The Boolean flag to enable or disable the source.

The value is set to true to enable the source and false to disable the source.







 ibmcloud event-notifications source update 



* Action: Update Source.

ibmcloud event-notifications source update --instance-id INSTANCE-ID --id ID [--name NAME] [--description DESCRIPTION] [--enabled ENABLED]
* Parameters to provide:

--instance-id (string)
: 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]/.

--name (int64)
: API Source name.

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

--description (int64)
: API Source Description

The default value is ``. The maximum length is 255 characters. The minimum length is 0 characters.
The attachment type is boot.
3. In the boot volume details, click the Size pencil icon. Alternatively, select Expand volume from the Actions menu.
4. In the side panel, increase the boot volume size in the Create size field. The size must be more than the current size up to 250 GB.
5. Click Expand boot volume size.









 Increasing boot volume capacity 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







 Increasing boot volume capacity when you create an instance from the CLI 

Run the ibmcloud is instance-create command and specify a boot volume capacity in GBs.

The following example creates an instance with a boot volume of 190 GB.

ibmcloud is instance create vsi-1 vpc-1 us-south-1 bx2-2x8 subnet-1 --image ibm-ubuntu-20-04-3-minimal-amd64-1 --boot-volume '{"name": "my-boot-vol-1", "volume": {"capacity": 190, "profile": {"name": "general-purpose"}}}'
print(response_attachment)

getAttachmentOptions := service.NewGetAttachmentOptions(
"products",
"small-appliances:100001",
"product_details.txt",
)

result, response, err := service.GetAttachment(getAttachmentOptions)
if err != nil {
panic(err)
}

data, _ := ioutil.ReadAll(result)
fmt.Println("n", string(data))

const { CloudantV1 } = require('@ibm-cloud/cloudant');

const service = CloudantV1.newInstance({});

service.getAttachment({
db: 'products',
docId: 'small-appliances:100001',
attachmentName: 'product_details.txt'
}).then(response => {
let attachment = response.result as Readable;
attachment.pipe(process.stdout);
});

The previous Go example requires the following import block:

import (
"fmt"
"io/ioutil"
"github.com/IBM/cloudant-go-sdk/cloudantv1"
)

All Go examples require the service object to be initialized. For more information, see the API documentation's [Authentication section](https://cloud.ibm.com/apidocs/cloudant?code=goauthentication-with-external-configuration) for examples.





 Delete an attachment 

To delete an attachment, make a DELETE request with the document's most recent _rev to https://$ACCOUNT.cloudant.com/$DATABASE/$DOCUMENT_ID/$ATTACHMENT. If you don't supply the most recent _rev, the response is a [409 error](https://cloud.ibm.com/apidocs/cloudantlist-of-http-codes).

See the following example of deleting an attachment by using HTTP:
Pricing FAQ 

IBM Cloudant pricing is based on the provisioned throughput capacity that you set for your instance, and the amount of data storage you use.

With IBM® Cloudant® for IBM Cloud®, you can increase or decrease your provisioned throughput capacity as needed, and pay pro-rated hourly. 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.

For more information, see [IBM Cloudant Pricing](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-pricing).



  Can I change my capacity setting? 

You can change your provisioned throughput capacity and see your current capacity settings in the IBM Cloudant Dashboard. Launch IBM Cloudant Dashboard > Account > Capacity to view and change your provisioned throughput capacity and see the hourly and approximate monthly costs. You can also use the IBM Cloud® pricing calculator to see estimates in other currencies.





  How do I know I exceeded the capacity limit that I set? 

The Lite plan includes 1 GB of storage. If you exceed the limit, IBM Cloudant blocks your account from writing new data until you delete enough data to be under the 1-GB limit, or upgrade to a higher plan.

The first 20 GB of storage comes free with the Standard plan. You can store as much data as you want. Any storage over the 20 GB limit costs $0.0014 per GB per hour, which is approximately $1 per GB per month.





  Where can I see my usage data? 

You can see your current and historical usage bills in the IBM Cloud Dashboard. Go to Manage > Billing and usage > Usage. Here you can see the total charges and usage for the month by service, plan, or instance. Only the hourly costs that are accrued for the current month and time are available. 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.
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.

Expanded capacity is determined by the maximum that is allowed by the file share profile. File shares that are created from a [Custom](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilescustom) profile or a [dp2](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesdp2-profile) profile can be expanded within the allowable IOPS range for that file share size.

File shares that are created from an [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesfs-tiers) can be expanded to the maximum size for its IOPS tier:



* A general-purpose, 3 IOPS/GB profile can be expanded up to 32,000 GB.
* A 5 IOPS/GB profile can be expanded up to 9,600 GB.
* A 10 IOPS/GB profile can be expanded up to 4,800 GB.



IOPS is automatically adjusted for tiered file share profiles, based on the size of the file share.