vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If not, follow the [getting started tutorial](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) to become familiar with the console.



1. Navigate to a bucket, so that you are looking at a list of objects. Select Configuration from the navigational menu.
2. Under Advanced configurations, look for Quota enforcement and toggle the selector to Enabled.
3. Now raise or lower the value and choose the appropriate storage unit. Then, click Save.







 Disabling or editing a quota 



1. Navigate to the bucket where you want to change the quota, so that you are looking at a list of objects. Select Configuration from the navigational menu.
2. Under Advanced configurations, look for Quota enforcement.
3. If you want to disable the quota enforcement, toggle the selector to Disable. Alternatively, keep the quota enforcement enabled, but edit the values as needed.
4. Click Save.









 Using an API 

Bucket quotas are managed with the [COS Resource Configuration API](https://cloud.ibm.com/apidocs/cos/cos-configuration).

To add a quota, you send a PATCH request to edit the bucket's metadata:

curl -X PATCH https://config.cloud-object-storage.cloud.ibm.com/v1/b/my-bucket -H 'authorization: bearer $IAM_TOKEN' -d '{"hard_quota": 10000000000}'

To disable the quota, set it to zero:

curl -X PATCH https://config.cloud-object-storage.cloud.ibm.com/v1/b/my-bucket -H 'authorization: bearer $IAM_TOKEN' -d '{"hard_quota": 0}'

To temporarily disable writing new data to the bucket, set the quota to a very small integer:
[Reclaimable storage](https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.admin.dbobj.doc/doc/c0055392.html)

[Reclaiming unused storage in DMS table spaces](https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.admin.dbobj.doc/doc/t0055397.html)

[ALTER TABLESPACE statement](https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.sql.ref.doc/doc/r0000890.html)

[Distribution keys for multi-partitioned plans](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-distribution_keys)
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?
: When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete, you can remove the PVC to start the deletion process of your persistent storage. Your PVC, PV, and storage instance are automatically removed.
: 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, you must manually remove the PVC, PV, and the storage instance to avoid further charges.

How does the billing stop after I delete my storage?
Autoscaling configurations based on memory usage are currently not available.

Disk - Disk autoscaling can scale when either disk usage reaches a certain threshold, Disk I/O utilization reach a certain threshold, or both. (The "or" in the UI operates as an inclusive or, |, v.) The amount of IOPS available to your deployment increases with disk size at a ratio of 10 IOPS for each GB.

The resource numbers refer to each database node in a deployment. For example, there are three data members in a MongoDB deployment and if the deployment is scaled with 10 GB of disk and 1 GB of RAM, that means each member gets 10 GB of disk and 1 GB of RAM. The total resources added to your deployment is 30 GB of disk and 3 GB of RAM.



 Autoscaling Considerations 



* Scaling your deployment up might cause your databases to restart. If your scaled deployment needs to be moved to a host with more capacity, then the databases are restarted as part of the move.
* Disk cannot be scaled down.
* A few scaling operations can be more long running than others. Drastically increasing RAM or Disk can take longer than smaller increases to account for provisioning more underlying hardware resources.
* Autoscaling operations are logged in [IBM Cloud® Activity Tracker](https://cloud.ibm.com/docs/databases-for-mongodb?topic=cloud-databases-activity-tracker).
* Limits



* 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-mongodb?topic=databases-for-mongodb-resources-scaling) your deployment.







 Configuring Autoscaling in the UI
* 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).
* I am unable to upgrade storage. What can affect the ability to upgrade or expand storage?

The following situations can affect the ability to upgrade or expand storage.



* If the original volume is the Endurance 0.25 tier, then the IOPS tier can’t be updated.
* Older storage types can't be upgraded. Ensure that the storage was ordered in an upgraded Data Center that allows for [Expandable storage](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-expandCapacity).
* The permissions that you have in the Cloud console can be a factor.
You can see a button called Reallocate, which will launch a Resource allocation tab that is very similar to the one that you saw when you created the node. If you want to lower the amount of available resources, simply provide lower values and click Reallocate resources on that tab and the resulting Summary page.

If you want to increase the CPU and memory for a node, use the Resource allocation panel in the console to increase the values. The white box at the end of the page adds up the new values. After clicking Reallocate resources, the Summary page will translate this value into a VPC amount, which is used to calculate your bill. You'll then need to navigate to your Kubernetes cluster to make sure your cluster has sufficient resources for this reallocation. If it does, you can click Reallocate resources. If sufficient resources are not available, you must increase the size of your cluster.

The method you will use to increase storage will depend on the storage class you chose for your cluster. Refer to the [Kubernetes](https://cloud.ibm.com/docs/containers?topic=containers-kube_conceptskube_concepts) or [OpenShift](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_concepts) storage options in the IBM Cloud documentation. If you are about to exhaust the storage on your peer or ordering node, you might need to deploy a new peer or ordering node with a larger file system and let it sync via your other components on the same channels.

In IBM Cloud, CPU and memory can be increased using the console if you have resources available in your Kubernetes cluster on IBM Cloud. However, storage must be increased using the IBM Cloud CLI. For a tutorial on how to do this, see Changing the size and IOPS of your existing storage device on your [Kubernetes](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_change_storage_configuration) or [OpenShift](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_change_storage_configuration) cluster.
How do I scale disk to get my IBM Cloud® Databases for PostgreSQL deployment back online? 

If you encounter a No space left on device error for your IBM Cloud® Databases for PostgreSQL deployment, review these solutions.

  What’s happening 

Your deployment becomes unreachable and produces a [Errno 28] No space left on device error message.

  How to fix it 

Review the following information to troubleshoot and resolve your No space left on device issues:



*  [Scale up the disk](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling&interface=ui) to get your instance back online. Scaling is a potentially long-running operation. For more information, see [Scaling Considerations](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling&interface=uiresources-scaling-consider).
*  To prevent an issue with disk space, set up [monitoring](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-monitoring).
*  Autoscaling is designed to respond to the short-to-medium term trends in resource usage on your IBM Cloud® Databases for PostgreSQL deployment. When enabled, your deployment is checked at the interval you specify. For more information, see [Autoscaling](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-autoscaling&interface=ui).
See [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo) for more information about the relationship between ephemeral storage and memory.



 Application defaults and limits 

The following table lists the limits for applications.



Application limits

 Category Default Maximum value Need to extend the maximum? 

 CPU 1.0 12.0 [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Ephemeral storage 400 M 48 G <br>(limited by memory) [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Max scale 10 250 [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Memory 4 G 48 G [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Min scale 0 250 [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Concurrency 100 1000 [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 
 Timeout 300 seconds 600 seconds [Contact IBM support](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case&interface=ui) 



For more information about supported CPU and memory combinations, see [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo).

Code Engine has limits for apps within a project.



* You are limited to 40 apps per project.
* You are limited to a total of 120 revisions for all apps per project.
* UI
* CLI
* Terraform







 Ordering Snapshots 

To create snapshots of your storage volume, either automated or manually, you need to purchase space to hold them. You can purchase snapshot capacity during the initial volume purchase or later by using these steps.



 Determining how much snapshot space to order 

Generically speaking, snapshot space is used by snapshots based on two key factors:



* How much your active file system changes over time,
* How long you plan to retain snapshots.



The way to calculate the amount of space that you need is (Rate of Change) x (number of hours/days/weeks/months data is kept).

The first snapshot uses a negligible amount of space as it's just a copy of the metadata (pointers) that indicates the active file system blocks.

A volume with numerous changes and a lengthy retention period needs more space than a volume with moderate change and a moderate retention schedule. An example for the first type is a high change rate database. An example for the second type is a VMware® datastore.

If you take 12 hourly snapshots of 500 GB of actual data, and the change rate is 1 percent between each snapshot, you end up with 60 GB for snapshots.

(5-GB Rate of Change) x (12 hourly snapshots) = (60 GB of used space)

Conversely, if that 500 GB of actual data, with 12 hourly snapshots, saw 10 percent of change every hour, the snapshot space that is used is 600 GB.

(50-GB Rate of Change) x (12 hourly snapshots) = (600 GB of used space)

So when you determine how much Snapshot space that you need, consider the rate of change carefully. It's a huge influence on how much snapshot space is needed. A bigger volume is more likely to change more often. However, a 500-GB volume with 5 GB of change and a 10-TB volume with 5 GB of change use the same amount of snapshot space.

Additionally, for most workloads, the larger a volume is the less space needs to be set aside initially.
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?
: When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete, you can remove the PVC to start the deletion process of your persistent storage. Your PVC, PV, and storage instance are automatically removed.
: For storage that was [statically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsstatic_provisioning), or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, you must manually remove the PVC, PV, and the storage instance to avoid further charges.

How does the billing stop after I delete my storage?
: Depending on what storage components you delete and when, the billing cycle might not stop immediately. If you delete the PVC and PV, but not the storage instance in your IBM Cloud account, that instance still exists and you are charged for it.

If you delete the PVC, PV, and the storage instance, the billing cycle stops depending on the billingType that you chose when you provisioned your storage and how you chose to delete the storage.



* When you manually cancel the persistent storage instance from the IBM Cloud console or the ibmcloud sl CLI, billing stops as follows:



* Hourly storage: Billing stops immediately. After your storage is canceled, you might still see your storage instance in the console for up to 72 hours.
* Monthly storage: You can choose between immediate cancellation or cancellation on the anniversary date. In both cases, you are billed until the end of the current billing cycle, and billing stops for the next billing cycle. After your storage is canceled, you might still see your storage instance in the console or the CLI for up to 72 hours.



* Immediate cancellation: Choose this option to immediately remove your storage. Neither you nor your users can use the storage anymore or recover the data.



* Anniversary date: Choose this option to cancel your storage on the next anniversary date.
If the cluster administrator is not allowed to modify the storage, or the infrastructure account is not the same as the current account, a storage administrator can manually execute the script that is provided in [Complete the preinstallation section](https://cloud.ibm.com/catalog/content/ibm-cp-datacore-6825cc5d-dbf8-4ba2-ad98-690e6f221701-global).





 Step 5. Set the deployment values 

Choose a storage class:



* EnduranceFileStorage - This option uses the storage class ibmc-file-gold-gid to install Cloud Pak for Data. For more information, see [Endurance Storage](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-orderingFileStorage). You can use the same storage class while provisioning the instances of services.
* PerformanceFileStorage - This option uses the storage class ibmc-file-custom-gold-gid to install Cloud Pak for Data. For more information, see [Performance Storage](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-orderingFileStorage). You can use the same storage class while provisioning the instances of services.
* Portworx - This option uses the storage class mentioned in [Storage considerations](https://www.ibm.com/docs/SSQNUZ_4.6.x/cpd/plan/storage_considerations.html). You can use the storage class mentioned in the service instance creation documentation when you provision instances of services.



Specify which services to install when you install IBM Cloud Pak for Data:



* To install Watson OpenScale, set aiopenscale to true.
* To install Cognos Dashboards, set cde to true.
* To install Db2 Data Gate, set datagate to true.
* To install Db2 Warehouse, set db2wh to true.
* To install Db2 Data Management Console, set dmc to true.
* To install RStudio Server, set rstudio to true.
* To install Apache Spark, set spark to true.
When you create a deployment, limit it so that your app's pod deploys only on machines with the best mix of resources. For example, you might want to limit a database application to a bare metal machine with a significant amount of local disk storage like the md1c.28x512.4x4tb.





 Set up multiple namespaces when you have multiple teams and projects that share the cluster 

Namespaces are kind of like a cluster within the cluster. They are a way to divide up cluster resources by using [resource quotas](https://kubernetes.io/docs/concepts/policy/resource-quotas/) and [default limits](https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/). When you make new namespaces, be sure to set up proper [RBAC policies](https://cloud.ibm.com/docs/containers?topic=containers-usersrbac) to control access. For more information, see [Share a cluster with namespaces](https://kubernetes.io/docs/tasks/administer-cluster/namespaces/) in the Kubernetes documentation.

If you have a small cluster, a couple dozen users, and resources that are similar (such as different versions of the same software), you probably don't need multiple namespaces. You can use labels instead.





 Set resource quotas so that users in your cluster must use resource requests and limits 

To ensure that every team has the necessary resources to deploy services and run apps in the cluster, you must set up [resource quotas](https://kubernetes.io/docs/concepts/policy/resource-quotas/) for every namespace. Resource quotas determine the deployment constraints for a namespace, such as the number of Kubernetes resources that you can deploy, and the amount of CPU and memory that can be consumed by those resources. After you set a quota, users must include resource requests and limits in their deployments.





 Organize your Kubernetes objects with labels
Resizing your virtual data centers 

You can change the amount of resources that are assigned to a virtual data center when it is in the Ready To Use state.



  Procedure to resize virtual data centers 



1.  From the IBM Cloud® for VMware Solutions Shared virtual data center details page, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/edit-tagging.svg) next to Resource Reservation.
2.  Update the values of the virtual CPU (vCPU) limit or RAM limit properties.
3.  Expand the Total estimated cost section to expand it. Verify the configuration and estimated price and click Modify to place the order.



Optionally, click Reset changes to return to the original resource values.

The status of the virtual data center changes to Modifying while the update is being made. When the resources are ready to use, the status changes to Available.

The configuration change might fail if the vCPU and RAM resources are in use while they are reduced. The cause of the failure is that the virtual data center resources cannot be reduced to a level that is insufficient for the currently active resource usage.





  Related links 



*  [VMware Shared overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_overview)
*  [Viewing and managing virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_viewing-vdc-summary)
*  [Deleting VMware Shared virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_deletinginstance)