vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see the CLI reference for [ibmcloud is volume-create](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-reference&interface=clivolume-create).





 Creating a data volume as an attachment to an existing virtual server instance 

You can use the instance-volume-attachment-add command to create a volume and attach it to an instance. The following example creates a volume with the spd profile, 100 GB capacity and 100 IOPS.

ibmcloud is instance-volume-attachment-add acd-vol-attach1 my-instance-acadia-1 --profile sdp --new-volume-name acd-vol-2 --iops 100 --capacity 100
Creating volume attachment acd-vol-attach1 for instance my-instance-acadia-1 under account vpc-1 as user test.user@ibm.com...

ID 730f-5f63eb4d-2683-4dd6-a20a-5ab06b4061c6
Name acd-vol-attach1
Volume -
Status attaching
Bandwidth(Mbps) 14
Type data
Device -
Auto delete false
Created 2023-05-05T07:42:33+05:30

For more information, see the CLI reference for [ibmcloud is instance-volume-attachment-add](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-reference&interface=cliinstance-volume-attachment-add).





 Creating an instance and add user tags to volumes from the CLI 

You can specify user tags for boot and data volumes when you create a virtual server instance. Run the instance-create command and specify user tags in the user_tags option. You can also edit the tags later or add more tags to the specified volume. For more information, see the [VPC CLI reference](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference&interface=ui).

In the example command,
The file share must be in a stable state before you can request that the capacity is increased.





 Limitations 

The following limitations apply to this release.



* File shares can expand, with the following restrictions:



* If the file share was created with a [Tiered IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesfs-tiers) that limits capacity to less than 32,000 GB, it can expand only to the allowed capacity for that tier.
* If the file share was created with a [Custom IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilescustom) in an IOPS range that doesn't allow expanding to 16,000 GB (custom GB max), it can expand only to its maximum capacity for the specified custom range.
* If the file share was created with a [dp2 profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesdp2-profile) in an IOPS range that doesn't allow expanding to 32,000 GB (dp2 GB max), it can expand only to its maximum capacity for the specified dp2 range.
* File shares can expand multiple times until maximum capacity is reached.



* IOPS increase to the maximum allowed by the profile.
* You can't independently modify IOPS for a file share that was created from an IOPS tier profile. IOPS is adjusted when you expand capacity.
* When you expand a file share that was created from a custom or dp2 profile, the capacity is increased, but the IOPS remains the same unless you choose to [adjust IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iops).
* Maximum IOPS for a file share is capped at 48,000 IOPS if it is accessed by a single host. For a file share that is accessed by multiple hosts, IOPS can reach up to 96,000 IOPS.
* After a file share is expanded, you can't reduce its size.







 Expand file share capacity in the UI
For more information about ordering File Storage for Classic through the API, see [order_file_volume](https://softlayer-python.readthedocs.io/en/latest/api/managers/file/SoftLayer.managers.file.FileStorageManager.order_file_volume).

By default, you can provision a combined total of 700 File Storage for Classic volumes. To increase the number of your volumes, contact your sales representative. Read about increasing limits [here](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managinglimits). For more information about the limit on simultaneous authorizations, see the [FAQs](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-file-storage-faqsauthlimit).





 Ordering File Storage for Classic 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).



 Provision Endurance File Storage for Classic with Terraform 

You can use the following example to create a 20 GB block storage volume with 10 GB snapshot capacity and 0.25 IOPS/GB performance tier in the DAL09 data center. The example also defines weekly snapshots to be created at 1:02 PM every Sunday.

resource "ibm_storage_file" "fs_endurance" {
type = "Endurance"
datacenter = "dal09"
capacity = 20
iops = 0.25

 Optional fields
allowed_virtual_guest_ids = ["28961689"]
allowed_subnets = ["10.146.139.64/26"]
allowed_ip_addresses = ["10.146.139.84"]
snapshot_capacity = 10
hourly_billing = true

 Optional fields for snapshot
snapshot_schedule {
schedule_type = "WEEKLY"
* 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.

For more information about how fields in uploaded files are handled, see [How fields are handled](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-index-overviewfield-name-limits).





 Supported data sources 

The following table shows the supported data sources for each deployment type.



Supported data sources
This table has row and column headers. The row headers identify supported data sources. The column headers identify the different product deployment type options. To understand which data sources are available for your deployment type, go to the row that describes the data source, and find the columns for the type of deployment you're interested in.

 Data source IBM Cloud IBM Cloud Pak for Data 

 Box ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 
 Database (IBM Data Virtualization, IBM Db2, Microsoft SQL, Oracle, Postgres) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/icons/checkmark-icon.svg) 
 FileNet P8 !
ibmcloud is instance-volume-attachment INSTANCE VOLUME_ATTACHMENT [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* VOLUME_ATTACHMENT: ID or name of the volume attachment.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-volume-attachments 

List all volume attachments to an instance.

ibmcloud is instance-volume-attachments INSTANCE [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-volume-attachment-add 

Create a volume attachment, connecting a volume to an instance.

ibmcloud is instance-volume-attachment-add NAME INSTANCE (VOLUME | --profile PROFILE --new-volume-name NEW_VOLUME_NAME --iops IOPS --encryption-key ENCRYPTION_KEY --capacity CAPACITY --tags TAGS --source-snapshot SOURCE_SNAPSHOT) [--auto-delete false | true] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is instance-volume-attachment-add data-vol-name 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 1a6b7274-678d-4dfb-8981-c71dd9d4daa5
IBM Cloud® File Storage for Classic is persistent, fast, and flexible network-attached, NFS-based File Storage for Classic. In this network-attached storage (NAS) environment, you have total control over your file shares function and performance. File Storage for Classic shares can be connected to up to 64 authorized devices over routed TCP/IP connections for resiliency.

File Storage - Classic



* 2 hours
* 2023-04-20



[Mounting File Storage for Classic in CentOS](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingCentOS)Mounting File Storage for Classic in CentOS

To mount IBM Cloud® File Storage for Classic in CentOS 7, you must authorize the host first. Then, install the NFS utilities as described in Mounting File Storage for Classic on Linux®.

File Storage - Classic



* 1 hour
* 2013-04-19



[Onboarding a virtual server image with Terraform](https://cloud.ibm.com/docs/account?topic=account-catalog-vsi-tutorial)Onboarding a virtual server image with Terraform

This tutorial walks you through how to onboard a sample virtual server image with Terraform to your account. By completing this tutorial, you learn how to create a private catalog, import the sample, validate that it can be installed on a selected deployment target, and make the virtual server image available to users who have access to your account.

Object Storage Virtual Private Cloud (VPC)

+1

Managing your account, resources, and access



* 20 minutes
* 2023-03-03



[Onboarding a virtual server image for Power Systems Virtual Server](https://cloud.ibm.com/docs/account?topic=account-catalog-vsipower-tutorial)Onboarding a virtual server image for Power Systems Virtual Server

This tutorial walks you through how to onboard a sample virtual server image for Power Systems Virtual Server to your account. By completing this tutorial, you learn how to create a private catalog, import the sample, validate that it can be installed on a selected deployment target, and make the virtual server image available to users who have access to your account.
* UI
* CLI
* API
* Terraform







 Expanding File Share Capacity 

With this feature, current users of IBM Cloud® File Storage for Classic are able to expand the size of their File Storage for Classic in GB increments up to 12 TB immediately. They don't need to create a duplicate or manually migrate data to a larger volume.

Billing for the volume is automatically updated to add the pro-rated difference of the new price to the current billing cycle. Then, the full new amount is billed in the next billing cycle.

The upgrade process is not instantaneous. You can expect to see the updated size in the UI or through the API in a short while after you put in the modification request. Resizing does not cause any outage or loss of access to the storage, so you can continue your operations as normal while you wait.



 Advantages of Expandable Storage 



* Cost management – You might know of a potential for growth of your data, but you need a smaller amount of storage to start. The ability to expand, allows customers to save on costs of storage at the start and then grow to accommodate their needs.
* Growing Storage needs - Customers who experience rapid growth beyond need a way to quickly and easily increase the size of their storage to manage that growth.







 Effects of expanding storage capacity on Replication 

Expand action on the primary storage results in automatic resizing of the replica.





 Limitations 

This feature is available for storage that is provisioned in [data centers](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-selectDC) with enhanced capabilities. Encrypted storage that is provisioned in these data centers can be increased up to 12 TB.

Existing size limitations for File 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. Go to the [IBM Cloud® console](https://cloud.ibm.com/login). From the menu, select Classic Infrastructure!
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 100
IOPS 3000
Bandwidth(Mbps) 393
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 -

In the example, the volume is attached to a virtual server instance, so the named and IDd of the volume attachment and instance are also displayed in the command output. The Active property is true because the virtual server instance to which the volume is attached is running. The busy property with the value false indicates that this volume is not performing an operation that must be serialized.

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





 Viewing all Block Storage for VPC volumes from the CLI 

Run this command to list summary information about all volumes:

ibmcloud is volumes [--json]

Specifying the resource group ID or name filters the list to volumes that belong to a resource group. When you omit this argument, it defaults to all resource groups.
================================================================================
couchbackup:restore restored 5 +0ms
couchbackup:restore finished { total: 5 } +1ms



You completed the backup and restore of a database and created a log file. For more information, see [Disaster recovery and backup](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-disaster-recovery-and-backupdisaster-recovery-and-backup), [Configuring IBM Cloudant for cross-region disaster recovery](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-configuring-ibm-cloudant-for-cross-region-disaster-recoveryconfiguring-ibm-cloudant-for-cross-region-disaster-recovery), and [IBM Cloudant backup and recovery](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloudant-backup-and-recoveryibm-cloudant-backup-and-recovery).
Parameters: ibm.io/chunk-size-mb=16,ibm.io/curl-debug=false,ibm.io/debug-level=warn,ibm.io/iam-endpoint=https://iam.bluemix.net,ibm.io/kernel-cache=true,ibm.io/multireq-max=20,ibm.io/object-store-endpoint=https://s3-api.dal-us-geo.objectstorage.service.networklayer.com,ibm.io/object-store-storage-class=us-standard,ibm.io/parallel-count=2,ibm.io/s3fs-fuse-retry-count=5,ibm.io/stat-cache-size=100000,ibm.io/tls-cipher-suite=AESGCM
AllowVolumeExpansion: <unset>
MountOptions: <none>
ReclaimPolicy: Delete
VolumeBindingMode: Immediate
Events: <none>

ibm.io/chunk-size-mb
: The size of a data chunk that is read from or written to IBM Cloud Object Storage in megabytes. Storage classes with perf in their name are set up with 52 megabytes. Storage classes without perf in their name use 16 megabyte chunks. For example, if you want to read a file that is 1GB, the plug-in reads this file in multiple 16 or 52-megabyte chunks.

ibm.io/curl-debug
: Enable the logging of requests that are sent to the IBM Cloud Object Storage service instance. If enabled, logs are sent to syslog and you can [forward the logs to an external logging server](https://cloud.ibm.com/docs/containers?topic=containers-healthlogging). By default, all storage classes are set to false to disable this logging feature.

ibm.io/debug-level
: The logging level that is set by the IBM Cloud Object Storage plug-in. All storage classes are set up with the WARN logging level.

ibm.io/iam-endpoint
* 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.









 Managing user access with Identity and Access Management 

The IBM Cloud Identity and Access Management (IAM) offering controls user access to IBM Cloud for VMware Solutions service instances. For more information about IAM, see [Managing user access with Identity and Access Management](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-iam).





 Related links 



* [Requirements and planning for VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_planning)
* [Ordering virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_ordering)
* [Operating VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guide)
* [VMware Cloud Director](https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-74C9E10D-9197-43B0-B469-126FFBCB5121.html)
allowed_virtual_guest_ids = [ 27699397 ]
allowed_ip_addresses = ["10.40.98.193", "10.40.98.200"]
hourly_billing = true
}

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

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. For example, [RHEL 8 - Modifying Logical Volume](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_logical_volumes/modifying-the-size-of-a-logical-volume_configuring-and-managing-logical-volumes) or [Microsoft® - Extend a basic volume](https://docs.microsoft.com/en-us/windows-server/storage/disk-management/extend-a-basic-volume).





 Expanding Storage over 12 TB 

If you need to increase your Storage volume capacity beyond 12 TB, you can request to be added to the allowlist by submitting a [support case](https://cloud.ibm.com/unifiedsupport/cases/add). When the request is approved by the Offering Manager, you're going to be notified through the case process. You're also going to see the option to increase your storage up to 16 TB in the console.
ibmcloud event-notifications integration list 

List all Integrations.

ibmcloud event-notifications Integration list [--limit LIMIT] [--offset OFFSET] [--search SEARCH] [--instance-id INSTANCE-ID]



 Command options 

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

--limit (int64)
: Page limit for paginated results.

The maximum value is 100. The minimum value is 1.

--offset (int64)
: offset for paginated results.

The minimum value is 0.

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







 ibmcloud event-notifications Integration get 

Get specific Integration.

ibmcloud event-notifications Integration get --id ID [--instance-id INSTANCE-ID]



 Command options 

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

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

The maximum length is 100 characters. The minimum length is 1 character.
For more information, see [setting and changing the version](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-versionterraform-version-upgrade1x).
* Can start with a new Terraform state file on each job run?

No, you need to only create new workspace. For more information, see [Workspace job execution](https://cloud.ibm.com/docs/schematics?topic=schematics-job-downloadwks-job-execution).
* Can I import an existing Terraform state file?

Yes, you can use --state flag option through the [ibmcloud schematics workspace new](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-new).
* What is the maximum variable size?

The maximum length of characters that Schematics Workspace variables support is 1 MB.
* What is the maximum state file size of import?

The terraform.tfstate file size must be less than 2 MB. When you create workspace from an existing Terraform state file, the terraform.tfstate file size must be less than 2 MB. Greater than 2 MB state file size is not supported in the Schematics. You will see an error message with 413 Request Entity Too Large error when creating a new Schematics workspace.
* How do I fix authentication errors when using the API?

You need to create the IAM access token for your IBM Cloud Account. For more information, see [Get token password](https://cloud.ibm.com/apidocs/iam-identity-token-apigettoken-password). You can see the following sample error message and the solution for the authentication error.

Error: Request fails with status code: 400, BXNIMO137E: For the original authentication, client id 'default' was passed, refresh the token, client id 'bx' is used.
Release notes for IBM Cloudant Classic 

Use these release notes to learn about the most recent updates to IBM® Cloudant® for IBM Cloud® that are grouped by date and build number.



 July 2023 

The following changes were made in build 8418:

Attachments
: Remove Content-MD5 header support.
: Replace MD5 with xxHash in ETag generation.

Mango
: Return correct keys_examined value in execution_stats field.
: Improve error messages of the _index endpoint.

Optimization
: Speed up internal replicator.
: Optimize low-level file name calculations.
: Use a faster sets implementation available since OTP 24.

Replicator
: Handle replicator instance start time during upgrades better.

Resharding
: Fix purge infos replicating to the wrong shards during shard splitting.





 June 2023 



 05 June 2023 

The following changes were made in build 8413:

_all_docs endpoint
: Do not return documents for non-string key parameter.

Filter view functions
: Optimize by not unnecessarily re-compiling filter view functions.

Geospatial
: Remove geospatial functionality.

Javascript
: Treat javascript internal errors (such as Out of Memory) as fatal.

_local_docs endpoint
: Hide internal checkpoint documents by default in the _local_docs response.

Mango query
: Return correct documents for queries with $regex and text indexes.
: Optimize queries using keys-only covering indexes.
: Add new covered Boolean field to _explain endpoint to indicate whether query is covered by an index.
: Return 405 instead of 500 for invalid path under _index endpoint.

Partitioned database queries
: Fix permissions required for partitioned _find and _explain endpoints.

Runtime environment
: Upgrade to the latest Erlang/OTP 24 release.

View query
: Treat single element keys parameter same as key.







 April 2023 



 03 April 2023 

IBM Cloudant Dashboard
: Update Dashboard to use Carbon 11's color theme.