vania-janet/multiturn-rag-retrieval-data huggingface dataset:
In a VMware® implementation, rescan storage to refresh the VMware® datastore and show the new volume size.





 How do I reconnect storage after a chassis swap? 

Complete the following tasks to connect storage after a swap.



1. Remove the authorization (revoke access) from the storage devices, and then authorize the host again.
2. Discover the storage devices again, with the new credentials that were gained from the reauthorization.



For more information, see [Managing File Storage for Classic](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managingstorage).





 How do I disconnect my storage device from a host? 

Complete the following steps to disconnect a volume from a host.



1. Unmount the device.
2. Revoke access for the host from the storage device in the Cloud console.
3. Remove auto mounts from NFS connections.







 How do endurance and performance storage differ? 

Endurance and Performance are provisioning options that you can select for storage devices. In short, Endurance IOPS tiers offer predefined performance levels whereas you can fine-tune those levels with the Performance tier. The same devices are used but delivered with different options. For more information, see [File Storage Features](https://www.ibm.com/products/file-storage/details).





 Can I connect File Storage for Classic to Windows®? 

No. You cannot connect IBM Cloud® File Storage for Classic on Microsoft® Windows®. NFS is not supported by IBM Cloud® in a Windows® environment.





 Can I mount a single storage device to multiple hosts within IBM Cloud? 

Yes, you can use this setup because NFS is a file-aware protocol.





 Can I increase inodes for my NFS volume? 

Typically, when volumes are provisioned, they are allotted the maximum inode count for the size that you ordered. Maximum inode count grows automatically as the volume grows. If the inodes count does not increase after you expanded a volume, submit a [support case](https://cloud.ibm.com/unifiedsupport/cases/add).
This feature applies to instances that are created from stock or custom images. You can also specify a larger boot volume capacity when you create an instance template. The boot volume can't be unattached from an instance (that is, stored as stand-alone data volume). For more information, see [Increasing boot volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes).
* Can I change boot volume capacity for an existing instance?

 Can I change boot volume capacity for an existing instance? 

Yes, boot volume capacity can be increased for an existing instance. However, you increase capacity on the storage side. That is, by modifying the boot volume details. For example, in the UI, you'd select a boot volume from the list of Block Storage for VPC volumes and then resize the volume from the volume details page. For more information, see [Increase boot volume capacity from the list of Block Storage for VPC volumes in the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes&interface=uiresize-boot-vol-list-ui). You can also use the [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes&interface=cliexpand-existing-boot-vol-cli) or the [API](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes&interface=apiexpand-existing-boot-vol-api).
* How many volumes can I provision on my account?

 How many volumes can I provision on my account? 

You can provision up to 300 Block Storage for VPC volumes per account in a region. You can request your quota to be increased by opening a [support case](https://cloud.ibm.com/unifiedsupport/cases/form) and specifying the region where you need more volumes.
[3000-3999]Gi:[200-48000]
[4000-7999]Gi:[300-48000]
[8000-9999]Gi:[500-48000]
[10000-12000]Gi:[1000-48000]
fsType: "xfs"
reclaimPolicy: "Delete"
Show more







 Removing persistent storage from a cluster 

When you set up persistent storage in your cluster, you have three main components: the Kubernetes persistent volume claim (PVC) that requests storage, the Kubernetes persistent volume (PV) that is mounted to a pod and described in the PVC, and the IBM Cloud infrastructure instance, such as classic file or block storage. Depending on how you created your storage, you might need to delete all three components separately.



 Understanding your storage removal options 

Removing persistent storage from your IBM Cloud account varies depending on how you provisioned the storage and what components you already removed.

Is my persistent storage deleted when I delete my cluster?
: During cluster deletion, you have the option to remove your persistent storage. However, depending on how your storage was provisioned, the removal of your storage might not include all storage components.

If you [dynamically provisioned](https://cloud.ibm.com/docs/containers?topic=containers-kube_conceptsdynamic_provisioning) storage with a storage class that sets reclaimPolicy: Delete, your PVC, PV, and the storage instance are automatically deleted when you delete the cluster. For storage that was [statically provisioned](https://cloud.ibm.com/docs/containers?topic=containers-kube_conceptsstatic_provisioning), VPC Block Storage, or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, the PVC and the PV are removed when you delete the cluster, but your storage instance and your data remain. You are still charged for your storage instance. Also, if you deleted your cluster in an unhealthy state, the storage might still exist even if you chose to remove it.

How do I delete the storage when I want to keep my cluster?
By creating the PVC, you exceed the maximum number of storage instances. For more information about the maximum number of volumes that you can create and how to retrieve the number of volumes in your account, see the documentation for [file](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managinglimits) and [block](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-managingstoragelimits) storage. To create a PVC, choose from the following options. - Remove any unused PVCs.<br><br><br><br> * Ask the IBM Cloud account owner to increase your storage quota by [opening a support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).<br><br><br> 
 `Unable to find the exact ItemPriceIds(type size iops) for the specified storageFailed to place storage order with the storage provider 
 Failed to find the datacenter name in configuration file. The data center that you specified in your PVC does not exist. Run ibmcloud oc locations to list available data centers. Correct the data center in your PVC and re-create the PVC. 
 Failed to place storage order with the storage providerStorage with the order ID 12345 could not be created after retrying for xx seconds.Failed to do subnet authorizations for the storage 12345.Storage 12345 has ongoing active transactions and could not be completed after retrying for xx seconds. The storage size, IOPS, and storage type might be incompatible with the storage class that you chose, or the IBM Cloud infrastructure API endpoint is currently unavailable.
The RAM provisioned to your deployment remains for your future needs, or until you scale down your deployment manually. The disk provisioned to your deployment remains because disk cannot be scaled down.
* If you need to add resources to your deployment occasionally or rarely, you can [manually scale](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-resources-scaling) your deployment.







 Configuring Autoscaling in the UI 

The Autoscaling panel is on the Resources tab of your deployment's Manage page. To enable scaling, enter your parameters. Then, check the boxes to enable the parameters you are using. Be sure to click Save Changes for your configuration to be saved and your changes to take effect.

To disable autoscaling, clear the boxes for the parameters that you no longer want to use. If you clear all the boxes, autoscaling is unavailable. Click Save Changes to save the configuration.





 Configuring Autoscaling in the CLI 

You can get the autoscaling parameters for your deployment through the CLI using the [cdb deployment-autoscaling](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference-ibmcloud-cdb-deployment-autoscaling-) command.

ibmcloud cdb deployment-autoscaling <deployment name or CRN> member

To enable and set autoscaling parameters through the CLI, use a JSON object or file with the [cdb deployment-autoscaling-set](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference-ibmcloud-cdb-deployment-autoscaling-set-) command.
Expanding and contracting capacity for VMware Regulated Workloads 

Expand or contract the capacity of your VMware® Regulated Workloads instances according to your business needs, by adding or deleting VMware vSphere® ESXi™ servers or Network File System (NFS) storage.



  Before adding or deleting ESXi servers 

You must migrate the VMware vCenter Server® virtual machines (VMs) before you delete a server. This requirement applies to the vCenter Server VM and to the additional VCHA VMs on the management and witness clusters.





  Adding or deleting ESXi servers 

The process to add and delete servers for VMware Regulated Workloads instances is similar to the one for vCenter Server instances. For more information, see the following topics:



*  [Adding ESXi servers to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservers)
*  [Deleting ESXi servers from vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_removingservers)







  Related links 



*  [Planning for VMware Regulated Workloads](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-planning)
*  [Ordering VMware Regulated Workloads](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-orderinginstance-req)
*  [Adding, viewing, and deleting clusters for VMware Regulated Workloads](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-addingviewingclustersvrw-addingviewingclusters)
* can't set anything to scale in an interval less than 60 seconds.
* Maximum Disk = 4 TB per member
* Maximum RAM = 112 GB per member



* Autoscaling does not scale down deployments where disk or memory usage has shrunk. The RAM provisioned to your deployment remains for your future needs, or until you scale down your deployment manually. The disk provisioned to your deployment remains because disk cannot be scaled down.
* If you just need to add resources to your deployment occasionally or rarely, you can [manually scale](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-resources-scaling) your deployment.







 Configuring Autoscaling in the UI 

Autoscaling is in Resources in your deployment's Manage page. To enable scaling, enter your parameters. Then, check the boxes to enable the parameters you are using. Be sure to click Save Changes for your configuration to be saved and your changes to take effect.

To disable autoscaling, clear the boxes for the parameters that you no longer want to use. If you clear all the boxes, autoscaling is disabled. Click Save Changes to save the configuration.





 Configuring Autoscaling in the CLI 

Get the autoscaling parameters for your deployment through the CLI using the [cdb deployment-autoscaling](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference-ibmcloud-cdb-deployment-autoscaling-) command.

ibmcloud cdb deployment-autoscaling <deployment name or CRN> member

Enable and set autoscaling parameters through the CLI using a JSON object or file with the [cdb deployment-autoscaling-set](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference-ibmcloud-cdb-deployment-autoscaling-set-) command.
* [Updating the File Storage for VPC add-on](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-managingstorage-file-vpc-update)
* [Understanding your storage removal options](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-managingvpc_storage_delete_options_file)
* [Cleaning up persistent storage](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-managingvpc-storage-remove-file)



[Storage class reference](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-sc-refstorage-file-vpc-sc-ref)





 Setting up Portworx 

[About Portworx](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_aboutstorage_portworx_about)



* [What is software-defined storage (SDS)?](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_aboutabout-px-sds)
* [How does Portworx work?](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_aboutabout-px-work)
* [What are the requirements to run Portworx?](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_aboutabout-px-requirments)
* [How can I make sure that my data is stored highly available?](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_aboutabout-px-ha)
* [What volume topology offers the best performance for my pods?]
* Delete the [IBM Cloud Object Storage bucket and / or service](https://cloud.ibm.com/resources).



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).





 Related content 



* [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage)
* [Manage Access to IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam)
* [Getting Started with CDN](https://cloud.ibm.com/docs/CDN?topic=CDN-getting-startedgetting-started)
You can increase the number IOPS available to your deployment by increasing disk space. You can also configure autoscaling to increase disk size automatically if your deployment's I/O utilization hits a certain saturation point for an extended period of time.

For more information, see the [MongoDB documentation](https://docs.mongodb.com/manual/faq/storage/how-frequently-does-wiredtiger-write-to-disk).





 WiredTiger Cache and Memory 

Databases for MongoDB uses the [WiredTiger storage engine, which uses both the file system memory cache and an internal memory cache](https://docs.mongodb.com/manual/core/wiredtiger/memory-use). MongoDB is most performant when it serves your data from its internal cache, a little less performant when the data is in the file system cache, and least performant when it has to grab your data from disk.

The default size of the internal cache is 50% of (total RAM - 1 GB) or 256 MB, whichever is larger. For example, the minimum memory size of a Databases for MongoDB deployment is 1024 MB per data member, so the internal cache is 512 MB (because (3072 MB / 2) - 1 GB = 512.

The internal/file system cache ratio is not user-configurable on your deployment, but you can scale the total amount of memory to adjust the internal cache to make your database more performant. For example, if you scale the memory to 4096 MB per member the internal cache size becomes 5120 MB. (12288 MB / 2) - 1 GB = 5120 MB.

Another way to use autoscaling is to set memory to scale when disk I/O utilization hits a certain threshold. Increasing memory decreases the amount that MongoDB reads or writes to disk, so additional memory might alleviate pressure on disk I/O by supporting more caching.

More information about the WiredTiger cache is in the [MongoDB documentation](https://docs.mongodb.com/manual/faq/storage/to-what-size-should-i-set-the-wiredtiger-internal-cache).





 Query Performance
parameters:
zone: "dal12"
region: "us-south"
type: "Performance"
sizeIOPSRange: |-
"[20-39]Gi:[100-1000]"
"[40-79]Gi:[100-2000]"
"[80-99]Gi:[100-4000]"
"[100-499]Gi:[100-6000]"
"[500-999]Gi:[100-10000]"
"[1000-1999]Gi:[100-20000]"
"[2000-2999]Gi:[200-40000]"
"[3000-3999]Gi:[200-48000]"
"[4000-7999]Gi:[300-48000]"
"[8000-9999]Gi:[500-48000]"
"[10000-12000]Gi:[1000-48000]"
reclaimPolicy: "Delete"
Show more





 Mounting block storage with an XFS file system 

The following examples create a storage class that provisions block storage with an XFS file system.

Example for Endurance block storage.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-block-custom-xfs
labels:
addonmanager.kubernetes.io/mode: Reconcile
provisioner: ibm.io/ibmc-block
parameters:
type: "Endurance"
iopsPerGB: "4"
sizeRange: "[20-12000]Gi"
fsType: "xfs"
reclaimPolicy: "Delete"

Example for Performance block storage.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-block-custom-xfs
labels:
addonmanager.kubernetes.io/mode: Reconcile
provisioner: ibm.io/ibmc-block
parameters:
classVersion: "2"
When you attempt to resize the memory as well as CPU of a deployed virtual server instance through a single request it may fail due to the following reasons:



* There is no free memory available on the host.
* There is no free memory available on the logical partition as the resources on it are running.
* The free memory available on the logical partition is less than that of the desired value indicated in the resizing request.
* You have made multiple attempts for resizing.
* Currently, there is no preference for memory or CPU on what should be resized first. If the first request being processed fails, the second one will also fail automatically.



Example: When the currently allocated memory for the logical partition is 4GB and you are trying to reduce the value to 2GB and the logical partition at the time of request does not have free 2GB memory for resizing (considering the logical partition is using upto 3.2 GB for running resources in it), then there is a possibility that both the CPU and memory resize will fail.





 You request for resizing the memory but you get a partial resize 

When you attempt to resize the memory of a deployed virtual server instance through a request, it may partially resize or in the worst scenarios even fail due to the following reasons:



* There is no free memory available on the host will result in failed request.
* There is no free memory available on the logical partition as the resources are running on it. This will result in a failed request.
* The free memory available on the logical partition is less than that of the desired value indicated in the resizing request. This will result in a partial resize.
* You have made multiple attempts for resizing. This will result in a failed request.



Example:When the currently allocated memory for the logical partition is 4GB and you are trying to reduce the value to 2GB and the logical partition at the time of request does not have free 2GB memory for resizing (considering the logical partition is using upto 3 GB for running resources in it) and can free up only 1 GB, then the partial resize should be possible to reduce the memory to 3GB.

In the current cloud environment, it may take upto 1.5 hours approximately for the change in memory to be updated to places referring to the memory of the logical partition.
* For jp-osa, jp-tok is used.



For more information, see [Configuring IBM Cloud platform logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-config_svc_logs).





 Step 6: Make additional boot volume space accessible (Optional) 

When you select a larger boot volume and not the default 100GB, the additional space is added as unallocated space to the machine. In this example, the unallocated space is added to Disk 0:

Zoom

![Larger boot volume.](https://cloud.ibm.com/docs-content/v1/content/e9cda99c64ea1ee68cf0eda257d6a1de69ddbc4e/citrix-daas/images/boot-volume1.png)

Figure 1. Larger boot volume

You can use the Windows Disk partition and the Disk Management tools to view and extend the C: partition or create addiitional partitions with the unallocated space.

For more information about the Windows tools used, see [Extend a basic volume](https://learn.microsoft.com/en-us/windows-server/storage/disk-management/extend-a-basic-volume).





 Next steps 

After you complete these post-provisioning steps, you can:



* Complete your management tasks in the [Citrix cloud console](http://citrix.cloud.com).
You may have to contact or work with an account administrator.







 Step 1: Create a custom role 

First, we need to create a role that allows a user to view a list of buckets, but not to access them or be able to create new buckets.



1. Navigate to IAM by following the Manage drop-down menu, and selecting Access (IAM).
2. Select Roles from the navigation menu.
3. Click the Create button to create a new role.

Zoom

![Create a new role](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/tut-iam-1-roles.png)

Figure 1: Creating a custom role.
4. We can call this role "List Buckets Only". Give it a name, ID, and brief description, and then select Cloud Object Storage from the drop down.

![Create a new role](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/tut-iam-2-custom.png)
5. Scroll down until you see the list of actions. Click Clear all to remove all actions from the new role.

![Create a new role](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/tut-iam-3-clear.png)
6. Look for the cloud-object-storage.account.get_account_buckets action and click Add.

!
Copy data from your local machine to a specific container that runs in a pod in your cluster.

kubectl cp <local_filepath>/<filename> <namespace>/<pod>:<pod_filepath> -c <container>







 Storage class reference 

Storage classes that have retain in the title have a reclaim policy of Retain. Example: ibmc-file-retain-bronze. Storage classes that don't have retain in the title have a reclaim policy of Delete. Example: ibmc-file-bronze.



 Bronze 

Name
: ibmc-block-bronze
: ibmc-block-retain-bronze

Type
: Endurance storage

File system
: ext4

IOPS per gigabyte
: 2

Size range in gigabytes
: 20-12000 Gi

Hard disk
: SSD

Reclaim policy
: ibmc-block-bronze: Delete
: ibmc-block-retain-bronze: Retain





 Silver 

Name
: ibmc-block-silver
: ibmc-block-retain-silver

Type
: Endurance storage

File system
: ext4

IOPS per gigabyte
: 4

Size range in gigabytes
: 20-12000 Gi

Hard disk
: SSD

Reclaim policy
: ibmc-block-silver: Delete
: ibmc-block-retain-silver: Retain





 Gold 

Name
: ibmc-block-gold
: ibmc-block-retain-gold

Type
: Endurance storage

File system
: ext4

IOPS per gigabyte
: 10

Size range in gigabytes
: 20-4000 Gi

Hard disk
: SSD

Reclaim policy
: ibmc-block-gold: Delete
: ibmc-block-retain-gold: Retain





 Custom 

Name
: ibmc-block-custom
: ibmc-block-retain-custom

Type
: Performance File system
: ext4

IOPS and size