vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Status available
Attachment state attached
Capacity 100
IOPS 3000
Bandwidth(Mbps) 393
Profile 5iops-tier
Encryption key -
Encryption provider_managed
Resource group defaults
Created 2023-06-29T16:14:59+00:00
Zone us-east-1
Health State ok
Volume Attachment Instance Reference Attachment type Instance ID Instance name Auto delete Attachment ID Attachment name
data 0757_11f5db7f-35a1-4678-bcbd-c85204e09507 kj-test-ro false 0757-4dfc4384-c4b5-497e-bab3-6415f9c4d44b otp

Active true
Unattached capacity update supported false
Unattached iops update supported false
Busy false
Tags -

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







 Adjust IOPS with the API 

You can adjust IOPS for existing data volumes by calling the Virtual Private Cloud (VPC) API.



 Adjust IOPS for a Custom profile 

Make a PATCH /volumes request and specify the iops parameter to adjust the IOPS within a custom IOPS profile band.

You can't update the name of the volume and adjust IOPS in the same PATCH /volumes request. Make two PATCH /volumes requests.

This example shows an increase of 100 IOPS to 3,000 IOPS for a 100 GB volume based on a 100 - 499 custom profile. The IOPS range for this custom band is 100 - 6,000 IOPS.

curl -X PATCH "$vpc_api_endpoint/v1/volumes/$volume_id?version=2022-01-11&generation=2" -H "Authorization: $iam_token" -d '{
"iops": 3000
}'

The volume status shows updating while the IOPS is being adjusted. The current IOPS is shown until you restart the instance.
The maximum length is 255 characters. The minimum length is 1 character. The value must match regular expression /[!a-zA-Z 0-9-_/.?:'";,+=@$%^&()]/.

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

--sources ([TopicUpdateSourcesItem[]](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-cli-plugin-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 default Cloudant Library is now the official [java-cloudant](https://github.com/cloudant/java-cloudant), the [Ektorp library](https://github.com/helun/Ektorp) is still available as an option, for details about this change see the [blog post](https://www.ibm.com/blogs/bluemix/2017/05/default-library-change-cloudant-auto-wiring-liberty-buildpack/).
* The default heap size ratio is now 50% when your app has less than 512mb of memory, if it has more than 512mb it will still be 75%.
* A new staging task log is now generated, which allows for easier debugging of staging errors.
* The Node.js runtime that is used by the [App Management utility](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_management) was updated to the 6.13.0 version.
* The buildpack also provides an updated agent for the Auto-Scaling service.







 20 June 2017 

Updated ASP.NET Core buildpack v1.0.20-20170620-1449
: This release includes the following updates:



* Add support for .NET Core runtime 2.0.0 Preview 1
* Add support for .NET Core SDK 2.0.0-preview1-005977
* Update Node version to 6.10.3
* Remove support for .NET Core runtime version 1.0.0
* Remove support for .NET Core runtime version 1.0.1
* Remove support for .NET Core SDK version 1.0.0-preview2-1-003177
* Add staging_task.log file to app container
* Lower disk usage when caching dependencies







 12 June 2017 

Updated Liberty buildpack v3.10-20170525-1107
: The default Liberty runtime version was updated to the 17.0.0.2 release.
Storage For persistent storage, use [block](https://cloud.ibm.com/docs/containers?topic=containers-vpc-block). For the number of volumes that can be attached per worker node, see [Volume attachment limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits). The storage class limits the volume size to 20TB and IOPS capacity to 20,000. For non-persistent storage, secondary storage on the local worker node is not available. 
 User access You can use [IBM Cloud IAM access policies](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-started) to authorize users to create infrastructure, manage your cluster, and access cluster resources. The cluster can be in a different resource group than the VPC. 
 Integrations VPC supports a select list of supported IBM Cloud services, add-ons, and third-party integrations. For a list, see [Supported IBM Cloud and third-party integrations](https://cloud.ibm.com/docs/containers?topic=containers-supported_integrations). 
 Locations and versions VPC clusters are available worldwide in the [multizone location](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-vpc). 
 Service interface VPC clusters are supported by the [next version (v2) of the IBM Cloud Kubernetes Service API](https://cloud.ibm.com/docs/containers?topic=containers-cs_api_install), and you can manage your VPC clusters through the same CLI and console as classic clusters. 
 Service compliance See the VPC section in [What standards does the service comply to?](https://cloud.ibm.com/docs/containers?topic=containers-faqsstandards). 
 Service limitations See [Service limitations](https://cloud.ibm.com/docs/containers?topic=containers-limitationstech_limits).
:............:.......................:..................:
: global : 700 : 117 :
:............:.......................:..................:





 IBM Cloud CLI 

The volume-limits command is also available in the sl plug-in for IBM Cloud CLI (v1.0 or higher).

 ibmcloud sl file volume-limits
Datacenter MaximumAvailableCount ProvisionedCount
global 700 99







 Confirming your current limit and provisioning count with the API 



 REST API call 

To directly get this information from the API, use the following method: [SoftLayer_Network_Storage/getVolumeCountLimits](https://sldn.softlayer.com/reference/services/SoftLayer_Network_Storage/getVolumeCountLimits/).

curl -u $SL_USER:$SL_APIKEY 'https://api.softlayer.com/rest/v3.1/SoftLayer_Network_Storage/getVolumeCountLimits.json'

SoftLayer_Container_Network_Storage_DataCenterLimits_VolumeCountLimitContainer[{"datacenterName":"global","maximumAvailableCount":700,"provisionedCount":99}]

The API call shows the combined number of Block Storage for Classic and File Storage for Classic.







 Requesting limit increase 

You can request a limit increase by submitting a support case in the [portal](https://cloud.ibm.com/unifiedsupport/cases/add). When the request is approved, you get a volume limit that is set for a specific data center.

To request a limit increase, open a support case and direct it to your sales representative.

In the ticket, provide the following information:
* IAM allowed IP addresses replaced with context based restrictions.
* The terraform.tfstate state file size maximum limit is less than 2 MB.



* [22 March 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-mar2223)



* Schematics Agent beta-1 release.
* Release Schematics command-line plug-in.





* [February 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-feb23)



* Review the release notes for February 2023.
* [16 February 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-feb2023)



* Schematics allowed IP address for US, EU Central, and UK South region are updated



* [7 February 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-feb0723)



* Release Schematics command-line plug-in.



* [3 February 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-feb0323)



* Enhancement in Schematics to protect its services with context-based restrictions





* [January 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-jan23)



* Review the release notes for January 2023.
* [30 January 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-jan3023)



* Release Schematics command-line plug-in.
For more information, see [Bringing your own image with Wazi Image Builder](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=bringing-your-own-image-wazi-image-builder).



 Requirements 

All custom images must meet the following requirements：



* Contain a single file or volume
* Is in qcow2 or vhd format
* Is cloud-init enabled
* The operating system is supported as a [stock image](https://cloud.ibm.com/docs/vpc?topic=vpc-about-imagesstock-images)
* Size doesn't exceed 250 GB
* The minimum size is 10 GB. For any image that is less than 10 GB, the size is rounded up to 10 GB.



For more information about custom images, see [Getting started with custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images).







 Next steps 

After you choose a profile, it's time to plan for and create an instance.



* [Planning for instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_best_practices)
* [Creating an instance by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers)
* [Creating an instance by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=cli)
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-volumesexpandable-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







 Expand volume capacity from the CLI
Using the Cloud Shell UI, you can upload or download only a single file at a time. If you need to transfer many files, it might take a long time to move all of them individually. Instead, use these strategies to efficiently move files between your workspace and another file system.



 Create archives to move files 

Before you move files, combine the files into an archive file such as a .tar, .tar.gz, or .zip so that you can move them all at once.

For example, to upload a folder of IBM Cloud administration scripts, you might compress them into a myScripts.zip file and upload them to Cloud Shell. In your Cloud Shell session, you can then run unzip myScripts.zip to extract the files.

You can do the same thing in reverse when you want to download files. For example, say you want to back up your entire Cloud Shell workspace. From your home directory, run tar -cvf myTar.tar * to create a .tar file (Mac or Linux) or run zip -r myZip.zip * to create a .zip file (Mac or Windows). Then, download the archive file from Cloud Shell and extract it on your local system.





 Work from a Git repo 

For projects in Git repositories, use the Cloud Shell UI to upload an SSH key so that you can connect to your Git repo. Keep a local copy of your SSH key as a backup. Then, run git clone to clone all of the repo's files to your Cloud Shell workspace. As a bonus, when you commit and push your changes to your Git repo, your changes are automatically backed up to a file system that's outside of Cloud Shell.
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.

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

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







 ibmcloud event-notifications subscription delete 



* Action: Delete existing Subscription.

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

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

The maximum length is 36 characters. The minimum length is 36 characters.
Sometimes, the resulting compressed file is larger than the maximum codeSize as described in the [Action Limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_actions) allowed by Cloud Functions. To reduce the size of the compressed file, select only the dependencies that you need, rather than selecting the entire virtualenv folder. The packages that you need can be found in the site-packages directory within the virtualenv folder. Note that you must also include the activate_this.py file from the bin directory of your virtualenv folder in your compressed file.

zip -r pyjoke.zip virtualenv __main__.py
8. Create an action called pyjoke by using the pyjoke.zip file. Make sure to use the --kind corresponding to the runtime image used to create the compressed action file. Otherwise, the action fails to execute during invoke.

ibmcloud fn action create pyjoke <file_path>/pyjoke.zip --kind python:3.11
9. Invoke the action to test that the pyjoke module is working.

ibmcloud fn action invoke pyjoke --result

Example output

{
"joke": "A QA engineer walks into a bar. Runs into a bar. Crawls into a bar. Dances into a bar. Tiptoes into a bar. Rams a bar. Jumps into a bar."
}







 Packaging large Python dependencies in a custom Docker image 

Cloud Functions has a size limit for the app code, see maximum codeSize described in the [Action Limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_actions). However, you can install large packages and dependencies into a custom Docker image and deploy it with your app code when you create an action. You can then import the packages at run time.
IBM Cloudant’s quorum and sharding parameters, after you discover them, seem like tempting options to change the behavior of the database.

Stronger consistency, surely I can set the write quorum to the replica count?

No! Recall that no way exists to close the inconsistency window in a cluster.

Don’t go there. The behavior can be much harder to understand especially during network partitions. If you’re using Cloudant-the-service, the default values are fine for most users.

Sometimes, tweaking the shard count for a database is essential to get the best possible performance. If you can’t say why, you’re likely to make your situation worse.





 IBM Cloudant is rate limited-let this rate limit inform your code 

Cloudant-the-service (unlike basic CouchDB) is sold on a “reserved throughput capacity” model. That means that you pay for the right to use up to a certain throughput, rather than the throughput you end up using. The right to use method takes a while to sink in. One flaky comparison might be that of a cell phone contract where you pay for a set number of minutes regardless of whether you use them or not.

Although the cell phone contract comparison doesn’t capture the whole situation, no constraint exists on the sum of requests that you can make to IBM Cloudant in a month. The constraint is on how fast you make requests.

It’s really a promise that you make to IBM Cloudant, not one that IBM Cloudant makes to you. You promise not to make more requests per second than you agreed to up front. A maximum speed limit, if you like. 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.
* ibmcloud is instance-template-create my-template-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 bx2-2x8 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --keys 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8,72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 Create instance template with multiple SSH keys.
* ibmcloud is instance-template-create my-template-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 bx2-2x8 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --boot-volume '{"name": "boot-vol-attachment-name", "volume": {"name": "my-boot-vol", "capacity": 150, "profile": {"name": "general-purpose"}}}' Create instance template with image with boot volume capacity. The capacity value can range from image's minimum provisioned size to 250
If you are on the free plan, you cannot set your quota to an amount that exceeds the free tier. The free tier allowance for storage is 512 MB and traffic is 5120 MB.

ibmcloud cr quota-set --traffic <traffic_quota> --storage <storage_quota>

Example to set your quota limit for storage to 600 megabytes, and the pull traffic to 7000 megabytes:

ibmcloud cr quota-set --storage 600 --traffic 7000







 Reviewing quota limits and usage 

You can review your quota limits and check your current storage and pull traffic usage for your account.



1. Log in to IBM Cloud.

ibmcloud login
2. Review your current quota limits for storage and pull traffic.

ibmcloud cr quota

Your output looks similar to the following example.

Getting quotas and usage for the current month, for account '<account_owner> Account'...

QUOTA LIMIT USED
Pull traffic 5.1 GB 0 B
Storage 512 MB 511 MB

OK







 Staying within quota limits 

If you exceed the quota limits that are set for your IBM Cloud account, you can free up storage and change your service plan or quota limits so that you can continue pushing and pulling images to and from your namespace.

From 1 February 2022, both [tagged](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag) and [untagged](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_untagged) images are charged for.

To free up image storage in your IBM Cloud account, complete the following steps.

Depending on the size of the image, it might take a while for the image to be removed and for the storage to be available.



1. Find the names of the images that you want to remove.



* To list only tagged images, run the [ibmcloud cr image-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_list) command.
The minimum length is 36 characters. The value must match regular expression /[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/.

--id (string)
: The ID of the secret version. Required.

The maximum length is 36 characters. The minimum length is 7 characters. The value must match regular expression /^([0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}|current|previous)$/.





 Example 

ibmcloud secrets-manager secret-version-metadata --secret-id=0b5571f7-21e6-42b7-91c5-3f5ac9793a46 --id=eb4cf24d-9cae-424b-945e-159788a5f535







 ibmcloud secrets-manager secret-version-metadata-update 

Update the custom metadata of a secret version.

ibmcloud secrets-manager secret-version-metadata-update --secret-id SECRET-ID --id ID [--version-custom-metadata VERSION-CUSTOM-METADATA]



 Command options 

--secret-id (string)
: The ID of the secret. Required.

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

--id (string)
: The ID of the secret version. Required.

The maximum length is 36 characters. The minimum length is 7 characters.
You can't run executable files on IBM Cloud when those executable files were developed and built in a different environment.

 Why it’s happening 

If the content that you want to push to IBM Cloud is already an executable, the content was previously built and doesn't need to be built on IBM Cloud. In this case, no buildpack is required for the executable to be run on IBM Cloud. You must explicitly indicate to IBM Cloud that no buildpack is required.

 How to fix it 

When you push the executable to IBM Cloud, you must specify a null-buildpack, which indicates that no buildpack is required. Specify a null-buildpack by using the -b option with the ibmcloud cf push command:

ibmcloud cf push appname -p app_path -c <start_command> -b <null-buildpack>

For example:

ibmcloud cf push appname -p app_path -c ./RunMeNow -b https://github.com/ryandotsmith/null-buildpack





 Org's memory limit is exceeded 

If you are a Lite account user, you might be unable to deploy an app to IBM Cloud if you have exceeded the memory limit of your organization. You can either reduce the memory that your apps use or increase the memory quota of your account. The maximum memory quota for a Lite account is 256 MB and can be increased only by upgrading to a billable account.

 What’s happening 

When you deploy an app to IBM Cloud,the following error message is displayed:

FAILED Server error, status code: 400, error code: 100005, message: You have exceeded your organization's memory limit.

 Why it’s happening 

This error occurs when the amount of memory that is remaining for your organization is less than the amount of memory that is required by the app that you want to deploy. The maximum memory quota for a Lite account is 256 MB.

 How to fix it 

You can either increase the memory quota of your account, or reduce the memory that your apps use.



* To increase the memory quota of your account, upgrade your Lite account to a billable account.