vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud sl file volume-modify <volume_ID> --new-size <size> --new-iops <iops>

Example for endurance storage.

ibmcloud sl file volume-modify <volume_ID> --new-size <size> --new-tier <iops>

volume_ID
: Enter the ID of the volume that you retrieved earlier.

new-size
: Enter the new size in gigabytes (Gi) for your volume. For valid sizes, see [Deciding on the File Storage for Classic configuration](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_predefined_storageclass). The size that you enter must be greater than or equal to the current size of your volume. If you don't specify a new size, the current size of the volume is used.

new-iops
: For performance storage only. Enter the new number of IOPS that you want. For valid IOPS, see [Deciding on the File Storage for Classic configuration](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_predefined_storageclass). If you don't specify the IOPS, the current IOPS is used. If the original IOPS/GB ratio for the volume is less than 0.3, the new IOPS/GB ratio must be less than 0.3. If the original IOPS/GB ratio for the volume is greater than or equal to 0.3, the new IOPS/GB ratio for the volume must be greater than or equal to 0.3.

new-tier
: For endurance storage only. Enter the new number of IOPS per GB that you want. For valid IOPS, see [Deciding on the File Storage for Classic configuration](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_predefined_storageclass). If you don't specify the IOPS, the current IOPS is used.
).See the following example of a first request:<-- <ul> --> * Curl * Java * Node * Python * Go<-- </ul> --> curl -H "Authorization: Bearer $API_BEARER_TOKEN" "$SERVICE_URL/orders/_all_docs?limit=5"
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.AllDocsResult;
import com.ibm.cloud.cloudant.v1.model.DocsResultRow;
import com.ibm.cloud.cloudant.v1.model.PostAllDocsOptions;

Long pageSize = 5L;
PostAllDocsOptions.Builder docsOptionsBuilder =
new PostAllDocsOptions.Builder()
.db("orders")
.limit(pageSize); // Fetch pageSize documents
AllDocsResult response =
service.postAllDocs(docsOptionsBuilder.build())
.execute()
.getResult();

while (response.getRows().size() > 0) {
List<DocsResultRow> responseDocuments = response.getRows();
System.out.println(responseDocuments);
// The startKey of the next request becomes the last document id appended with u0000
docsOptionsBuilder.startKey(
responseDocuments
.get(responseDocuments.size() - 1)
.getId() + 'u0000'
);
response =
service.postAllDocs(docsOptionsBuilder.build())
.execute()
.getResult();
}
const { CloudantV1 } = require('@ibm-cloud/cloudant');

const service = CloudantV1.newInstance({});

async function paginate(n) {
Inspect the IBM Cloud Backup for Classic section and verify that the size that was selected during the purchase process is displayed.

If the backup storage size continues to show a capacity of zero, a second page refresh might be needed.











 Provisioning IBM Cloud Backup for Classic from the CLI 

Before you begin, you must install the IBM Cloud CLI. For more information, see [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).

You can provision backup space when you order a server, and you can order the IBM Cloud Backup for Classic service as an upgrade. The following example command orders a monthly VSI with 4 CPU, 16 GB RAM, 100 GB SAN disk, Ubuntu 18.04, and 1 Gbps public and private uplink in data center DAL13. It also provisions 20 GB of vault space for backups. The system prompts for confirmation as this action incurs charges. Type y and press enter to continue.

$ ibmcloud sl order place CLOUD_SERVER DALLAS13 GUEST_CORES_4,RAM_16_GB,REBOOT_REMOTE_CONSOLE,1_GBPS_PUBLIC_PRIVATE_NETWORK_UPLINKS,BANDWIDTH_0_GB_2,1_IP_ADDRESS,GUEST_DISK_100_GB_SAN,OS_UBUNTU_18_04_LTS_BIONIC_BEAVER_LAMP_64_BIT,MONITORING_HOST_PING,NOTIFICATION_EMAIL_AND_TICKET,AUTOMATED_NOTIFICATION,UNLIMITED_SSL_VPN_USERS_1_PPTP_VPN_USER_PER_ACCOUNT,NESSUS_VULNERABILITY_ASSESSMENT_REPORTING,EVAULT_20_GB --billing monthly --extras '{"virtualGuests": [{"hostname": "test", "domain": "softlayer.com"}]}' --complex-type SoftLayer_Container_Product_Order_Virtual_Guest
This action will incur charges on your account. Continue?> y

ID 105021440
Created 2023-04-24T20:04:57Z
Status PENDING_AUTO_APPROVAL
If you're on the standard plan, you're charged by GB of usage per month. The first 5 GB each month is free. If you're on the free plan, you can pull images from your namespace until you reach the quota limit for the free plan.

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, you pulled images that contain layers with a total size of 14 GB. Your monthly usage is calculated as shown in the following example:

In the standard plan, the first 5 GB per month is free, so you get charged for 9 GB (14 GB - 5 GB).







 Quota limits for storage and pull traffic 

Depending on the service plan that you choose, you can push and pull images to and from your namespace until you reach your plan-specific or custom quota limits for each region.



 Storage quota limits 

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



* [Free up space by removing images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_freeup) from your namespaces.
* [Upgrade to the standard plan](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_plan_upgrade).
* 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.
* [create_multipart_upload](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlS3.Client.create_multipart_upload)
* [upload_part](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlS3.Client.upload_part)











 Large Object Upload by using TransferManager 

The TransferManager provides another way to run large file transfers by automatically incorporating multi-part uploads whenever necessary setting configuration parameters.

def upload_large_file(bucket_name, item_name, file_path):
print("Starting large file upload for {0} to bucket: {1}".format(item_name, bucket_name))

 set the chunk size to 5 MB
part_size = 1024 * 1024 * 5

 set threadhold to 5 MB
file_threshold = 1024 * 1024 * 5

 Create client connection
cos_cli = ibm_boto3.client("s3",
ibm_api_key_id=COS_API_KEY_ID,
ibm_service_instance_id=COS_SERVICE_CRN,
config=Config(signature_version="oauth"),
endpoint_url=COS_ENDPOINT
)

 set the transfer threshold and chunk size in config settings
transfer_config = ibm_boto3.s3.transfer.TransferConfig(
multipart_threshold=file_threshold,
multipart_chunksize=part_size
)

 create transfer manager
transfer_mgr = ibm_boto3.s3.transfer.TransferManager(cos_cli, config=transfer_config)

try:
 initiate file upload
future = transfer_mgr.upload(file_path, bucket_name, item_name)

 wait for upload to complete
future.result()
* UI
* Terraform







 Expanding vault capacity 

Current IBM Cloud® users are able to expand the size of their vault up to 12000 GB. They don't need to create a duplicate or manually migrate data to a larger volume. The limit increase process does not cause any outage or lack of access.



 Ordering an increase in the UI 



1. Log in to the [IBM Cloud console](https://cloud.ibm.com/login). From the menu ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/921d024aca5ff45536208840a52f864567eb4068/icons/icon_hamburger.svg), select Classic Infrastructure![Classic icon](https://cloud.ibm.com/docs-content/v1/content/921d024aca5ff45536208840a52f864567eb4068/icons/classic.svg).
2. Click Storage > Cloud Backup to display the servers with backup service.
3. Select the vault that you want to extend.
4. Click Actions, and select Modify IBM Cloud Backup for Classic.
5. On the next screen, select the new size and click Upgrade.







 Ordering an increase with Terraform 

To use Terraform, download the Terraform CLI and configure the IBM Cloud Provider plug-in. For more information, see [Getting started with Terraform](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started).

Use the ibm_storage_evault resource to update your IBM Cloud® Backup for Classic instance. The following example increases the vault capacity to 100 GB when it is applied.

resource "ibm_storage_evault" "test" {
datacenter = "dal13"
capacity = "100"
}
-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl file snapshot-order 12345678 -s 1000 -t 4

This commands orders a snapshot space for the volume with ID 12345678. The size is 1000 GB, and the tier level is 4 IOPS per GB.





 ibmcloud sl file snapshot-restore 

Restore a file volume by using a specified snapshot:

ibmcloud sl file snapshot-restore VOLUME_ID SNAPSHOT_ID

Examples:

ibmcloud sl file snapshot-restore 12345678 87654321

This command restores volume with ID 12345678 from snapshot with ID 87654321.





 ibmcloud sl file snapshot-schedule-list 

List snapshot schedules for a volume:

ibmcloud sl file snapshot-schedule-list VOLUME_ID

Examples:

ibmcloud sl file snapshot-schedule-list 12345678

This command list snapshot schedules for volume with ID 12345678.





 ibmcloud sl file volume-cancel 

Cancel an existing file storage volume:

ibmcloud sl file volume-cancel VOLUME_ID [OPTIONS]

Command options:

--reason
: An optional reason for cancellation.

--immediate
: Cancel the file storage volume immediately instead of on the billing anniversary.

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

Examples:

ibmcloud sl file volume-cancel 12345678 --immediate -f

This command cancels volume with ID 12345678 immediately and without asking for confirmation.





 ibmcloud sl file volume-count 

List number of file storage volumes per data center:

ibmcloud sl file volume-count [OPTIONS]

Command options:

-d, --datacenter
: Filter by datacenter shortname.





 ibmcloud sl file volume-limits 

Display the global maximum volume count for the account and the number of Block Storage and File Storage volumes that are already provisioned.

ibmcloud sl file volume-limits

Examples:

ibmcloud sl file volume-limits
Currently, you can provision minimum of 10 GB to maximum of 32,000 GB file shares, depending on the [file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles).





 Can I change the size of a file share? 

You can increase the size of a file share from its original capacity in GB increments up to 32,000 GB capacity, depending on your [file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles). For more information, see [expanding file share capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-expand-capacity).





 Is there a way to replicate my file shares in case of events? 

Yes. You can create replicas of your file shares by setting up a replication relationship between primary file shares in one zone to replica file share in another zone. Using replication is a good way to recover from incidents at the primary site, when data becomes inaccessible or applications fail. For more information, see [About file share replication](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-replication&interface=ui).





 How does file share replication work? 

when you create a file share, you can set up a replication relationship between a primary source file share to a replica file share in a different zone. When the file share is created, so is the replica share in the other zone. When the replication relationship is established, the replica file share begins pulling data from the source file share. The replica file share is read-only until you break the replication relationship, creating two independent file shares, or fail over to the replica file share. For more information about setting up replication, see [Creating replica file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create-replication&interface=ui).





 How do I schedule replication? 

You can choose the frequency of replication by creating a schedule with a cronspec and can replicate as frequently as every hour.
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg), then click Change Snapshot Space.
4. Select the storage size that you need.
5. Click Continue.
6. Enter any Promo Code that you have, and click Recalculate. The Charges for this order and Order Review fields are completed by default.

Discounts are applied when the order is processed.
7. Review your order, and read the service agreement. If you agree with the terms, check the box. Cick Place Order. Your snapshot space is provisioned in a few minutes.







 Ordering Snapshot space from the SLCLI 

 slcli block snapshot-order --help
Usage: slcli block snapshot-order [OPTIONS] VOLUME_ID

Options:
--capacity INTEGER Size of snapshot space to create in GB [required]
--tier [0.25|2|4|10] Endurance Storage Tier (IOPS per GB) of the block
volume for which space is ordered [optional, and only
valid for endurance storage volumes]
--upgrade Flag to indicate that the order is an upgrade
-h, --help Show this message and exit.





 Ordering Snapshot space with Terraform 

When you provision a storage volume with Terraform, use the ibm_storage_block resource and specify the snapshot_capacity argument. The following example defines 10 GB snapshot space.

resource "ibm_storage_block" "test1" {
type = "Endurance"
datacenter = "dal05"
capacity = 20
iops = 0.25
os_format_type = "Linux"

 Optional fields
allowed_virtual_guest_ids = [ 27699397 ]
allowed_ip_addresses = ["10.40.98.193", "10.40.98.200"]
snapshot_capacity = 10
ibmcloud project config-update --project-id PROJECT-ID --id ID --locator-id LOCATOR-ID] --input INPUT] --setting SETTING] --name NAME] --labels LABELS] --description DESCRIPTION] --authorizations AUTHORIZATIONS] --compliance-profile COMPLIANCE-PROFILE] !
<-- <section "id="section-project-config-update-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] +$/.
--id (string): The unique config ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] !!+$/.
--locator-id (string): A dotted value of catalogID.versionID.
The maximum length is 512 characters. The minimum length is 1 character. The value must match regular expression /^(?\s)(?.\s$)\.0-9a-z-A-Z_-] +$/.
--input (ProjectConfigInputVariable]]ProjectConfigInputVariable] ): The inputs of a Schematics template property.
The default value is ] . The maximum length is 10000 items. The minimum length is 0 items.

Provide a JSON string option or specify a JSON file to read from by providing a filepath option that begins with a @, e.g. --input=@path/to/file.json.
--setting (ProjectConfigSettingCollection]]ProjectConfigSettingCollection] ): Schematics environment variables to use to deploy the configuration. Settings are only available if they were specified when the configuration was initially created.
The default value is ] . The maximum length is 10000 items. The minimum length is 0 items.
! ): Schematics environment variables to use to deploy the configuration. Settings are only available if they were specified when the configuration was initially created.
The maximum length is 10000 items. The minimum length is 0 items.

Provide a JSON string option or specify a JSON file to read from by providing a filepath option that begins with a @, e.g. --setting=@path/to/file.json.
<-- </section "id="section-project-config-create-cli-options" "> --><-- <section "id="section-project-config-create-examples" "> --> Example ibmcloud project config-create --project-id=exampleString --name=env-stage --locator-id=1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global --labels=env:stage,governance:test,build:0 --description='Stage environment configuration, which includes services common to all the environment regions. There must be a blueprint configuring all the services common to the stage regions. It is a terraform_template type of configuration that points to a Github repo hosting the terraform modules that can be deployed by a Schematics Workspace.'
1 October 2019 

The following changes were made in build 8103:

X-Cloudant-Action HTTP response header
: New X-Cloudant-Action HTTP response header that returns the IBM Cloud® IAM actions that are associated with a request.

Search requests
: Previously, search requests would return a 400 status code both on a bad request and on internal server errors. Now, internal server errors correctly return a 500 response status code.







 September 2019 



 18 September 2019 

Replaced deprecated database information fields
: Calls to GET /{db} were replaced by the following fields:



Table 1. Database information fields

 Old Field New Field 

 data_size sizes.active 
 disk_size sizes.file 
 other.data_size sizes.external 



Calls to GET /{db}/_design/{ddoc}/_info were replaced by the following fields:



Table 2. Design doc information fields

 Old Field New Field 

 data_size sizes.external 
 disk_size sizes.file 









 June 2019 



 1 June 2019 

The following changes were made in build 8076:

Improvements
: Internal bug fixes.

Stability
: Stability improvements.







 May 2019 



 15 May 2019 

The following changes were made in build 8070:

Improvements
: Internal bug fixes.





 1 May 2019 

The following changes were made in build 8062:

Improvements
: Internal bug fixes.







 April 2019 



 15 April 2019 

The following changes were made in build 8058:

ibrowse HTTP client
: Fixed bug in ibrowse HTTP client that leaves dead process IDs in the connection pool, and in some cases, caused persistent IAM-based replication failures.





 1 April 2019 

The following changes were made in build 8052:

partitioned_indexes field
: Accessing the database information endpoint (/db/) for a partitioned database now includes information about the contained partitioned indexes. The new field, partitioned_indexes, contains the following information:



* The current number of partitioned indexes in the database (count).
* A breakdown of those indexes by type (indexes).
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.

Checking for third-party library or framework compatibility before you commit to a particular tool is a good idea.

It is also worth understanding that the rates aren’t directly equivalent to HTTP API endpoint calls. You must expect that, for example, a bulk update counts according to its constituent document writes.



* IBM Cloudant documentation on [plans and pricing](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-publicibm-cloud-public) on IBM public cloud







 Logging helps you see what’s going on 

IBM Cloudant’s logs indicating each API call made, what was requested and how long it took to respond can be automatically spooled to LogDNA for analysis and reporting for IBM Cloud-based services. This data is useful for keeping an eye on request volumes, performance, and whether your application is exceeding the provisioned capacity for your IBM Cloudant service.

You can set up the logging service at no cost to get started. Paid-for plans allow data to be parsed, retained, and archived to Object Storage. Slices and aggregations of your data can be built up into visual dashboards to give you an at-a-glance view of your IBM Cloudant traffic. For more information, see the following website:



* [IBM Cloudant Logging with LogDNA blog](https://blog.cloudant.com/2019/09/16/Cloudant-Logging-with-LogDNA.html)







 Compress your HTTP traffic 

IBM Cloudant compresses its JSON responses to you if you supply an HTTP header in the request that indicates that your code can handle data in this format:

Request:
[HMAC Credentials](https://cloud.ibm.com/docs/cloud-object-storage/iam?topic=cloud-object-storage-service-credentialsservice-credentials-iam-hmac) are NOT currently supported. For more information on IAM, [click here](https://cloud.ibm.com/docs/cloud-object-storage/iam?topic=cloud-object-storage-iam-overview).

To get the highest throughput, split the transfer into a specified number of parallel sessions that send chunks of data whose size is defined by a threshold value.

The typical configuration for using multi-session should be:



* 2500 MBps target rate
* 100 MB threshold (this is the recommended value for most applications)



ms_transfer_config = AsperaConfig(multi_session="all",
target_rate_mbps=2500,
multi_session_threshold_mb=100)

In the above example, the sdk spawns enough sessions to attempt to reach the target rate of 2500 MBps.

Session management can also be explicitly configured in the SDK. This is useful in cases where more precise control over network utilization is wanted.

The typical configuration for using explicit multi-session should be:



* 2 or 10 sessions
* 100 MB threshold (this is the recommended value for most applications)



from ibm_s3transfer.aspera.manager import AsperaConfig
 Configure 2 sessions for transfer
ms_transfer_config = AsperaConfig(multi_session=2,
multi_session_threshold_mb=100)

 Create the Aspera Transfer Manager
transfer_manager = AsperaTransferManager(client=client,
transfer_config=ms_transfer_config)

For best performance in most scenarios, always make use of multiple sessions to minimize any processing that is associated with instantiating an Aspera high-speed transfer. If your network capacity is at least 1 Gbps, you should use 10 sessions. Lower bandwidth networks should use two sessions.





 File Upload 

bucket_name = "<bucket-name>"