vania-janet/multiturn-rag-retrieval-data huggingface dataset:
This command orders a performance volume with size is 1000 GB, IOPS is 4000, and in data center dal09.





 ibmcloud sl file volume-modify 

Modify an existing file storage volume:

ibmcloud sl file volume-modify VOLUME_ID [OPTIONS]

Command options:

-c, --new-size
: New Size of file volume in GB. If no size is given, the original size of volume is used. Potential Sizes: [20, 40, 80, 100, 250, 500, 1000, 2000, 4000, 8000, 12000] Minimum: [the original size of the volume]

-i, --new-iops
: Performance Storage IOPS. Range [100-6000], and in multiples of 100 [only for performance volumes]. If no IOPS value is specified, the original IOPS value of the volume is used. Requirements: [If original IOPS/GB for the volume is less than 0.3, new IOPS/GB must also be less than 0.3. If original IOPS/GB for the volume is greater than or equal to 0.3, new IOPS/GB for the volume must also be greater than or equal to 0.3.]

-t, --new-tier
: Endurance Storage Tier (IOPS per GB) [only for endurance volumes]. If no tier is specified, the original tier of the volume is used. Requirements: [If original IOPS/GB for the volume is 0.25, new IOPS/GB for the volume must also be 0.25. If original IOPS/GB for the volume is greater than 0.25, new IOPS/GB for the volume must also be greater than 0.25.]

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl file volume-modify 12345678 --new-size 1000 --new-iops 4000

This command modifies volume 12345678 with size of 1000 GB, and IOPS of 4000.

ibmcloud sl file volume-modify 12345678 --new-size 500 --new-tier 4
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 --secret-id=0b5571f7-21e6-42b7-91c5-3f5ac9793a46 --id=eb4cf24d-9cae-424b-945e-159788a5f535







 ibmcloud secrets-manager secret-version-data-delete 

Delete the data of a secret version by specifying the ID of the version.

This operation is available for secret type: iam_credentials current version.

ibmcloud secrets-manager secret-version-data-delete --secret-id SECRET-ID --id ID



 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 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 

An IBM Cloudant Dedicated Hardware plan instance is a bare metal IBM Cloudant environment that is provisioned for the sole use of your IBM Cloudant Standard plan instances. The IBM Cloudant Dedicated Hardware plan offers the following options:



* An IBM Cloudant Dedicated Hardware plan environment that can be provisioned in any [IBM® global data center](https://www.ibm.com/cloud/data-centers/).
* This plan is necessary for HIPAA compliance and must be selected at provisioning time.
* Users can choose to bring-your-own-key (BYOK) with customer-managed encryption keys with IBM Key Protect for all environments provisioned 1 January 2020 or later. IBM Cloudant runs on encrypted disks, but to BYOK, the Dedicated Hardware plan is required. BYOK encryption details must be chosen at provisioning time, and the feature isn't available for already-provisioned Dedicated Hardware plan environments.
* All Standard plan instances that are deployed on Dedicated Hardware plan environments include both private (internal) endpoints and public endpoints in locations that support Cloud Service Endpoints (CSE). Using private endpoints allows customers to connect to an IBM Cloudant instance through the internal IBM Cloud® network to avoid upstream application traffic from going over the public network and incurring bandwidth charges. For more information, see [Cloud Service Endpoint documentation](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview) for details about enabling Cloud Service Endpoints for your IBM Cloud® account.
* Users of an IBM Cloudant Dedicated Hardware plan environment can employ IP allowlisting by contacting support. IP allowlisting configuration applies to all instances that are running on the environment.
Status updating
Attachment state attached
Capacity 100
IOPS 3000
Bandwidth(Mbps) 3145
Profile general-purpose
Encryption key -
Encryption provider_managed
Resource group defaults
Created 2023-06-29T16:14:59+00:00
Zone us-east-1
Health State 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 -

When the update operation completes, run the ibmcloud is volume command to see the updated properties of the volume.

$ ibmcloud is volume demo-volume-update
Getting volume demo-volume-update under account Test Account as user test.user@ibm.com...

ID r014-dee9736d-08ee-4992-ba8d-3b64a4f0baac
Name demo-volume-update
CRN crn:v1:bluemix:public:is:us-east-1:a/a10d63fa66daffc9b9b5286ce1533080::volume:r014-dee9736d-08ee-4992-ba8d-3b64a4f0baac
Status available
Attachment state attached
Capacity 8000
IOPS 24000
Bandwidth(Mbps) 3145
Profile general-purpose
Encryption key -
Encryption provider_managed
Resource group defaults
Created 2023-06-29T16:14:59+00:00
Zone us-east-1
Health State ok
Volume Attachment Instance Reference Attachment type Instance ID Instance name Auto delete Attachment ID Attachment name
* The files that are removed are .asa, .asax, .exe, .php5, .pht, .phtml, .shtml, .swf, .tfstate, .tfstate.backup, .xap.
* All files that are larger than 500 KB are removed. This file size limit does not apply for the allowed image files.
* The folder name starts with a (period) . is treated as vulnerable.



The allowed extension list is continuously monitored and updated in every release. You can raise a [support ticket](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-help) with the justification to add a file extension to the list.
* How do I save files between operations?

it keeps whatever files you write to this path /tmp/.schematics and restores to the same path when you run your next activity.
* How do I update the Terraform version

IBM Cloud Schematics deprecates older version of Terraform. For more information, see [Deprecating older version of Terraform process in IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-deprecate-tf-version).

You can follow the topics to upgrade from one Terraform version to another version



* [Upgrading the Terraform template version](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-version)
* [Updating the Workspace Terraform 1.x version](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-versionterraform-version-upgrade1x-process)
* [Upgrade Terraform template from v0.13 and higher to v1.0](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-versionupgrade-13-to10)
For more information about the VM encryption limitations for VMware Cloud Director 10.4, see [Enabling VM encryption on storage policies of an Organization virtual data center](https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Service-Provider-Admin-Portal-Guide/GUID-80F58C1D-A97E-43FE-8E41-E9242A1D2332.html).

The encryption storage policies do not currently work with VM customizations. IBM is working closely with VMware to resolve this issue in a future release. In the meantime, you can use encryption storage policies after a VM is deployed and customized by using the unencrypted storage policies. For more information, see [Changing the general properties of a virtual machine](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guideshared_vcd-ops-guide-change-properties).





 Standard-Catalog storage policy 

Select the Standard-Catalog storage policy to upload vApp templates and any media to your catalog. The Standard-Catalog storage policy does not deploy vApps and VMs, is unencrypted, and has no IOPS restrictions.

The Standard-Catalog storage policy always spans all virtual data centers in the region so you can access media files from any virtual data center regardless of the data center zone.







 Maximum disk size 



* The maximum disk size is 16 TBs per disk for the 0.25 IOPS / GB, 2 IOPS/GB, 4 IOPS/GB, 10 IOPs / GB, and Standard storage policies.
* The maximum disk size is 62 TBs per disk for the vSAN storage policy.







 Maximum host capacity 

The maximum host capacity for a single VM has the following specifications:



* 80 vCPU
* 1.5 TB RAM
* Storage is not limited
* Open virtualization appliance (OVA) size is limited to 300 GB. You can use the Open Virtualization Format (OVF) Tool for uploading larger OVAs.
* ibmcloud is instance-create my-instance-name my-vpc us-south-1 bx2-2x8 my-subnet --boot-volume '{"name": "boot-vol-attachment-name", "volume": {"name": "boot-vol-name", "capacity": 150, "profile": {"name": "general-purpose"}, "source_snapshot": {"id": "150847e3-ef0d-4927-9341-6d0a7bae424f"}}}' Create instance from snapshot with boot volume capacity. The capacity value can range from snapshot's minimum capacity to 250
* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 bx2-2x8 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --boot-volume '{"name": "boot-vol-attachment-name", "volume": {"name": "boot-vol-name", "profile": {"name": "general-purpose"}, "source_snapshot": {"id": "150847e3-ef0d-4927-9341-6d0a7bae424f"}}}' Create instance with boot volume attachment from volume snapshot.
* ibmcloud is instance-create my-instance-name my-vpc us-south-1 bx2-2x8 my-subnet --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --volume-attach '[{"volume": {"name":"my-volume-name", "profile": {"name": "general-purpose"}, "source_snapshot": {"name": "my-snapshot-name"}}}]' Create instance with volume attachment from volume snapshot by using resource name.
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/b293a157aaf26e34a94525b64f55b4e73b099b09/icons/icon_hamburger.svg) > Classic Infrastructure > Devices > your virtual server instance. Select the Storage tab, and authorize your block and file storage if not listed there.







 Limitations 

Review the following storage migration limitations:



* All migrations are limited to a volume size of 2 TB only.
* You can choose only four volumes while provisioning a virtual server instance. Only four attached volumes, in addition to your boot volume, can be migrated. If you have more than four volumes in your classic instance, see [Volume attachment limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits) for details and use the Content Data Migrator in the VPC+ tool to migrate the additional volumes.
* Up to four primary partitions or three primary with two logical on the fourth partition can be migrated.
* Migration of block volumes and partitions without file systems is not yet supported.
* A maximum of 10 IOPS/Gb mapping will be done on virtual server instances for VPC.
* Migration of storage attached to Windows is not yet supported.



All three storage types can be migrated if your use case satisfies these limitations.





 Storage migration use cases 

Consider the following uses cases for storage migration:



1. Classic virtual server instance has portable storage that is attached with Linux file systems. This is migrated as-is to VPC.
2. Classic virtual server instance has network file storage:



* An equivalent Linux file system (ext4) is created in VPC and then the contents are copied over.
* VPC does not yet support NAS storage. Your storage will be on the Linux file system on your VPC instance, and it cannot be shared.



3. Classic virtual server has network block storage (iSCSI devices):
If you supply include_docs=true, then another doc attribute is added to each "row" in the result set that includes the document body.<-- </section "id="section-what-is-the_all_docs_endpoint" "> --><-- <section "id="section-the-limit-startkey-endkey-parameters" "> --> The limit, startkey, and endkey parameters To access data from _all_docs in reasonably sized pages, you must supply the limit parameter to tell IBM Cloudant how many documents to return: get me 5 documents
GET $SERVICE_URL/$DATABASE/_all_docs?limit=5 HTTP/1.1
You can also limit the range of document _ids that you want by supplying one or more values to startkey or endkey.<-- <ul> --> * Curl * Java * Node * Python * Go<-- </ul> --> get me 5 documents from _id order00057 onwards
curl -H "Authorization: Bearer $API_BEARER_TOKEN" "$SERVICE_URL/orders/_all_docs?limit=5&startkey="order00057""
 get me 5 documents between _id order00057 --> order00077
curl -H "Authorization: Bearer $API_BEARER_TOKEN" "$SERVICE_URL/orders/_all_docs?limit=5&startkey="order00057"&endkey="order00077""
 get me 5 documents up to _id order00077
curl -H "Authorization: Bearer $API_BEARER_TOKEN" "$SERVICE_URL/orders/_all_docs?limit=5&endkey="order00077""
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.AllDocsResult;
import com.ibm.cloud.cloudant.v1.model.PostAllDocsOptions;

Cloudant service = Cloudant.newInstance();

// get me 5 documents from _id order00057 onwards
* IBM Cloudant Query ([_find](https://cloud.ibm.com/apidocs/cloudantpostfind))



The number of read operations that are used by a partitioned query request varies depending on the results returned.



2. Writes, which are creation, modification, or deletion of individual documents.
3. Global Queries to global indexes (formerly called queries), which are requests that are made to an IBM Cloudant query endpoint not within the _partition namespace, including the following types:



* Primary Index ([_all_docs](https://cloud.ibm.com/apidocs/cloudantpostalldocs))
* MapReduce View ([_view](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-using-viewsusing-views))
* Search Index ([_search](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-cloudant-searchqueries))
* IBM Cloudant Query ([_find](https://cloud.ibm.com/apidocs/cloudantpostfind))









 Provisioned throughput capacity 

Throughput provision is identified and measured as a request class of the following operation types: Read, Write, and Global Query.

The measurement of throughput is a simple count of the number of units of each request class, per second, where the second is a sliding window.

If your account exceeds the number of throughput units that are allotted for a request class, IBM Cloudant rejects requests. The requests are rejected until the number of units of the request class within the sliding window no longer exceeds the number that is provisioned. It might help to think of the sliding 1-second window as being any consecutive period of 1,000 milliseconds.

For example, the Standard plan is provisioned for 200 reads per second. Your account might use a maximum of 200 reads during a consecutive period of 1,000 milliseconds (1 second). Subsequent reads that are made during the sliding 1,000-millisecond period are rejected until the number of reads in that period drops to less than 200 again.
If original IOPS/GB for the volume is greater than 0.25, new IOPS/GB for the volume must also be greater than 0.25.]

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl file volume-modify 12345678 --new-size 1000 --new-iops 4000

This command modifies volume 12345678 with size of 1000 GB, and IOPS of 4000.

ibmcloud sl file volume-modify 12345678 --new-size 500 --new-tier 4

This command modifies volume 12345678 with size 500 GB, and tier level 4 IOPS per GB.





 ibmcloud sl file volume-options 

List all options for ordering a file storage:

ibmcloud sl file volume-options

Examples:

ibmcloud sl file volume-options

This command lists all options for creating a file storage volume, including storage type, volume size, IOPS, tier level, data center, and snapshot size.





 ibmcloud sl file volume-refresh 

Refresh a dependent duplicate volume with a snapshot from its parent:

ibmcloud sl file volume-refresh VOLUME_ID SNAPSHOT_ID [OPTIONS]

Command options:

-f, --force-refresh
: Force the volume refresh. Ongoing transactions are canceled. --output
: Specify output format. Only JSON is supported now.

Examples:

ibmcloud sl file volume-refresh 123 456

Refresh a dependent duplicate 123 with a snapshot from its parent 456.





 ibmcloud sl file volume-set-note 

Set a note for an existing file storage volume:

ibmcloud sl file volume-set-note [OPTIONS] VOLUME_ID

Command options:

-n value, --note value
: Public notes related to a storage volume [required]

--output value,
: Specify output format. Only JSON is supported now.

Examples:

ibmcloud sl file volume-set-note 12345678 --note 'this is my note'
Plus (includes Trial) 10 MB 









 Field limits 

When a document is added to a collection, content from the document is evaluated and added to the appropriate fields in an internal index.

For structured data, such as uploaded CSV or JSON files, or data from crawled databases, each column or object is stored as a root-level field. For example, if you add a CSV file to collection, each column in the CSV file is stored as a separate field in the index.

A maximum of 1,000 fields can be added to the index.

You cannot assign the data type, such as Date or String, of a field. The data type is detected automatically and assigned to the field during document ingestion. The assignment is based on the data type that is detected from the first document that is indexed. Ingestion errors can occur in subsequent documents if a different data type is detected for the value in the same field. Therefore, if your documents have a mix of data types in a single field, first ingest the document that has a value with the most flexible data type, such as String, in the field.

When you crawl a website or upload an HTML file, the HTML content is added to the collection and indexed in an html field.

The following table shows the maximum size limit for fields per document.



Maximum field sizes

 Field type Maximum allowed size per document 

 html field 5 MB 
 Sum of all other fields 1 MB 



If the maximum size of the fields in the document exceeds the allowed limits, they are treated as follows:



* For a document with an oversized html field, all of the fields in the document are indexed except the html field.

For IBM Cloud Pak for Data version 4.0 and earlier, the entire document is not indexed.
* For a document with oversized non-HTML fields, the document is not indexed.



If you are uploading a Microsoft Excel file and a message is displayed that indicates that the non-HTML field size limit is exceeded, consider converting the XLS file into a CSV file. When you upload a comma-separated value (CSV) file, each row is indexed as a separate document. As a result, no field size limits are exceeded.
* [initiateMultipartUpload](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/AmazonS3.htmlinitiateMultipartUpload-com.ibm.cloud.objectstorage.services.s3.model.InitiateMultipartUploadRequest-)
* [uploadPart](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/AmazonS3.htmluploadPart-com.ibm.cloud.objectstorage.services.s3.model.UploadPartRequest-)











 Upload larger objects using a Transfer Manager 

The TransferManager simplifies large file transfers by automatically incorporating multi-part uploads whenever necessary setting configuration parameters.

public static void largeObjectUpload(String bucketName, String itemName, String filePath) throws IOException, InterruptedException {
File uploadFile = new File(filePath);

if (!uploadFile.isFile()) {
System.out.printf("The file '%s' does not exist or is not accessible.n", filePath);
return;
}

System.out.println("Starting large file upload with TransferManager");

//set the part size to 5 MB
long partSize = 1024 * 1024 * 5;

//set the threshold size to 5 MB
long thresholdSize = 1024 * 1024 * 5;

String endPoint = getEndpoint(COS_BUCKET_LOCATION, "public");
AmazonS3 s3client = createClient(COS_API_KEY_ID, COS_SERVICE_CRN, endPoint, COS_BUCKET_LOCATION);

TransferManager transferManager = TransferManagerBuilder.standard()
.withS3Client(s3client)
.withMinimumUploadPartSize(partSize)
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 value must match regular expression /[!a-zA-Z 0-9-_/.?:'";,+=@$%^&()]/.

--enabled (Boolean)
: Search string for filtering results.

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

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

The maximum length is 100 characters. The minimum length is 1 character. The value must match regular expression /[a-zA-Z0-9-:_]/.







 ibmcloud event-notifications source list 



* Action: List all Source.

ibmcloud event-notifications source 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.
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 - 2,999 200 - 40,000 
 3,000 - 3,999 200 - 48,000 
 4,000 - 7,999 300 - 48,000 
 8,000 - 9,999 500 - 48,000 
 10,000 - 12,000 1,000 - 48,000 







 Effect of IOPS adjustment on replication 

If the volume has replication in place, the replica is automatically updated to match the IOPS selection of the primary.





 Adjusting the IOPS on your Storage in the UI 



1. Go to your list of File Storage for Classic. From the IBM Cloud® console, click Classic Infrastructure![Classic icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/classic.svg) > Storage > File Storage for Classic.
2. Select the volume from the list and click the ellipsis ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/action-menu-icon.svg) > Modify File Share.
3. In the Adjust Storage IOPS section, make a new selection:



* For Endurance (Tiered IOPS), select an IOPS Tier greater than 0.25 IOPS/GB of your storage. You can increase the IOPS tier at any time. However, decreasing is available only once a month.
* For Performance (Allocated IOPS), specify new IOPS option for your storage by entering a value in the range 100 - 48,000 IOPS. (Be sure to look at any specific boundaries that are required by size in the order form.)



4.