vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Removing persistent storage from a cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storagecleanup_block)



* [Understanding your storage removal options](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storagestorage_delete_options_block)
* [Cleaning up persistent storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storagestorage_remove_block)









 Setting up IBM Cloud Object Storage 

[Setting up IBM Cloud Object Storage](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-understandstorage-cos-understand)



* [Creating your object storage service instance](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-understandcreate_cos_service)
* [Creating IBM Cloud Object Storage service credentials](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-understandservice_credentials)
* [Creating a secret for the object storage service credentials](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-understandcreate_cos_secret)
* [Limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-understandcos_limitations)



[Installing the IBM Cloud Object Storage plug-in on VPC and classic clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_installstorage_cos_install)



* [Updating the IBM Cloud Object Storage plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_installupdate_cos_plugin)
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 an etcd 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-etcd?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 need to add resources to your deployment occasionally or rarely, you can [manually scale](https://cloud.ibm.com/docs/databases-for-etcd?topic=databases-for-etcd-resources-scaling) your deployment.







 Configuring Autoscaling in the UI
PVC {"plugin":"ibm-file-plugin-77497497cc-5qm58","region":"us-south","cluster":"05ccfca248dc4c389978d074524e0a8e","type":"Endurance","ns":"n4c817f","pvc":"n4c817forg1ca-fabric-ca-pvc","pv":"pvc-63074ac8-8b9b-11e9-88db-222bd59fb4bc","storageclass":"default","reclaim":"Delete"}

To see the same information from the command line, log in to your cluster and enter this command:

ibmcloud sl file volume-list --column id --column notes

This will allow you to map the output from the pods to the nodes you have deployed.

If you are using VPC infrastructure, see [About block storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about) for more details.





 Adding storage 

As you monitor your pods and notice that more storage is needed, you can increase storage when additional storage is available. The following links provide more information about how to increase storage after your network is deployed.



* [IBM file storage](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-expandCapacity)
* [Portworx](https://docs.portworx.com/portworx-install-with-kubernetes/storage-operations/create-pvcs/resize-pvc/)
* [Block storage](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-expandingcapacityexpandingcapacity)



Users can allocate more storage to their running network by resizing the existing storage PVCs or by deploying nodes with new PVCs.







 Upgrading to a new version of Fabric
2. Select from a range of sizes from the prompt. Sizes typically range from 0 to the size of your volume.
3. Click Continue.
4. Enter any Promo Code that you have, and click Recalculate. The Charges for this order and Order Review fields are completed by default.
5. Read the service agreement, and if you agree with the terms click checkbox, and click Place Order. Your additional snapshot space is provisioned in a few minutes.







 Deleting a snapshot schedule in the UI 

Snapshot schedules can be deleted through Storage > File Storage for Classic.



1. Click the volume ID to display its related information.
2. Click Snapshots.
3. Click the schedule to be deleted in the Snapshot Schedules frame.
4. Click the checkbox next to the schedule to be deleted and click Save.



If you're using the replication feature, be sure that the schedule that you're deleting isn't the schedule that is used by replication. For more information about deleting a replication schedule, see [here](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-replication).





 Deleting a snapshot schedule from the SLCLI 

You can accomplish this task by using the following command.

 slcli file snapshot-disable --help
Usage: slcli file snapshot-disable [OPTIONS] VOLUME_ID

Disables snapshots on the specified schedule for a given volume

Options:
--schedule-type TEXT Snapshot schedule [INTERVAL|HOURLY|DAILY|WEEKLY]
[required]
-h, --help Show this message and exit.

If you're using the replication feature, be sure that the schedule that you're deleting isn't the schedule that is used by replication. For more information about deleting a replication schedule, see [here](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-replication).





 Deleting a snapshot in the UI
allowed_ip_addresses = ["10.146.139.84"]
snapshot_capacity = 10
hourly_billing = true

 Optional fields for snapshot
snapshot_schedule {
schedule_type = "WEEKLY"
retention_count = 20
minute = 20
hour = 13
day_of_week = "SUNDAY"
enable = true
}
snapshot_schedule {
schedule_type = "HOURLY"
retention_count = 20
minute = 2
enable = true
}

}

If you want to update the schedule, just change these values and apply them to your resources. If you want to delete the schedule, remove its details from the ibm_storage_file resource definition, and apply your changes.

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





 Taking a manual Snapshot in the UI 

Manual snapshots can be taken at various points during an application upgrade or maintenance. You can also take snapshots across multiple servers that were temporarily deactivated at the application level.

The maximum limit of manual snapshots per storage volume is 50.



1. Click your storage volume.
2. Click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/action-menu-icon.svg).
3. Click Take Manual Snapshot.



The snapshot is taken and displayed in the Snapshots section of the Detail page. Its schedule appears Manual.





 Taking a manual Snapshot from the SLCLI 

You can use the following command to create a snapshot from the SLCLI.

 slcli file snapshot-create --help
Usage: slcli file snapshot-create [OPTIONS] VOLUME_ID

Options:
-n, --notes TEXT Notes to set on the new snapshot
View, inspect, and pull images.<br><br>View and analyze namespaces.<br><br>View quotas.<br><br>View vulnerability reports.<br><br>View image signatures.<br><br>View retention policies.<br><br>View the contents of the trash.<br><br>View the contents of the manifest for an image.<br><br>List Vulnerability Advisor security exemption policies and types of security exemptions. 
 Writer The Writer role can edit information. Push, delete, and restore images.<br><br>View quotas.<br><br>Sign images.<br><br>Set and run retention policies.<br><br>Delete all untagged images in your Container Registry account. 
 Manager The Manager role can perform all actions. View, inspect, pull, push, delete, and restore images.<br><br>View, add, analyze, and remove namespaces.<br><br>Assign namespaces to resource groups.<br><br>View and set quotas.<br><br>View vulnerability reports.<br><br>View and create image signatures.<br><br>Review and change pricing plans.<br><br>Enable IAM access policy enforcement.<br><br>List, add, and remove Vulnerability Advisor security issue exemption policies.<br><br>List types of security exemptions.<br><br>Set and run retention policies.<br><br>View the contents of the trash.<br><br>Restore images.<br><br>View the contents of the manifest for an image.<br><br>Prevent or allow image pulls or pushes over public network connections for your account.<br><br>Check whether the use of public connections is prevented for image pushes or pulls in your account.<br><br>Delete all untagged images in your Container Registry account. 



For the following Container Registry commands, you must have at least one of the specified roles as shown in the following tables. To create a policy that allows access to Container Registry, you must create a policy where the following criteria apply.



* The service name is container-registry.
How to fix it Create a custom storage class that uses the same configuration as the pre-defined storage class that you want to use, but with a name that does not exceed 63 characters.<-- <ol> -->1. Get the YAML configuration of the storage class that you want to use in your ODF storage cluster and save it in a file on your local machine.
oc get sc ibmc-vpc-block-metro-retain-10iops-tier -o yaml
2. Edit the name of the storage class. Make sure that the name of your custom storage class is fewer than 30 characters to allow for the ODF storage cluster device set IDs to be under the 63 character kubernetes limit. Create the storage class in your cluster.
oc create -f <custom-storage-class.yaml>
3. Clean up your ODF deployment]] ! ! ! ! !
For mounting instructions, depending on your host's operating system, follow the appropriate link.



* [Accessing File Storage for Classic on Linux®](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingLinux)
* [Mounting File Storage for Classic in CentOS](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingCentOS)
* [Mounting File Storage for Classic Volume on ESXi hosts](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-architectureguide)









 What performance latency can be expected from the File Storage for Classic? 

Target latency within the storage is less than one ms. The storage is connected to compute instances on a shared network, so the exact performance latency depends on the network traffic during the operation.





 What happens to the data when File Storage for Classic Volumes are deleted? 

IBM Cloud® File Storage for Classic presents file shares to customers on physical storage that is wiped before any reuse.

When you delete a File Storage for Classic volume, that data immediately becomes inaccessible. All pointers to the data on the physical disk are removed. If you later create a new volume in the same or another account, a new set of pointers is assigned. The account can't access any data that was on the physical storage because those pointers are deleted. When new data is written to the disk, any inaccessible data from the deleted volume is overwritten.

IBM guarantees that data deleted cannot be accessed and that deleted data is eventually overwritten and eradicated. Further, when you delete a storage volume, the share must be overwritten before the storage is made available again, either to you or to another customer.

When IBM decommissions a physical drive, the drive is destroyed before disposal. The decommissioned drives are unusable and any data on them is inaccessible.

Customers with special requirements for compliance such as NIST 800-88 Guidelines for Media Sanitization can perform the data sanitization procedure before they delete their storage.





 I cannot cancel a File Storage for Classic volume because the Cancel action in the Cloud console is unavailable or disabled. What’s happening?
User Name username Secret The username to connect to the storage device. true N/A 
 User Password password Secret The password to connect to the storage device. true N/A 
 Limit Volume Size limitVolumeSize Config The maximum volume size (in Gibibytes) that can be requested and the qtree parent volume size. true 50Gi 
 Limit AggregateUsage limitAggregateUsage Config Provisioning fails if usage is above this percentage. true 80% 







 22.10 parameter reference 



Table 3. 22.10 parameter reference

 Display name CLI option Type Description Required? Default value 

 Management LIF managementLIF Config The IP address of the Management LIF. true N/A 
 Data LIF dataLIF Config The IP address of the Data LIF. true N/A 
 SVM svm Config The name of the SVM. true N/A 
 User Name username Secret The username to connect to the storage device. true N/A 
 User Password password Secret The password to connect to the storage device. true N/A 
 Limit Volume Size limitVolumeSize Config The maximum volume size (in Gibibytes) that can be requested and the qtree parent volume size. true 50Gi 
 Limit AggregateUsage limitAggregateUsage Config Provisioning fails if usage is above this percentage. true 80% 









 Storage class reference for NetApp ONTAP-SAN 

Before you deploy apps that use the sat-netapp storage classes, review the following notes.

By default, the sat-netapp-file-gold storage class doesn't include any QoS limits (unlimited IOPS).

To use the sat-netapp-file-silver and sat-netapp-file-bronze storage classes, you must create corresponding silver and bronze QoS policy groups on the storage controller and define the QoS limits.
sizeRange: "[20-12000]Gi"
reclaimPolicy: "Delete"
classVersion: "2"
reclaimPolicy: Delete
volumeBindingMode: Immediate
Show more

Example for Performance File Storage for Classic.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-file-performance-storageclass
labels:
kubernetes.io/cluster-service: "true"
provisioner: ibm.io/ibmc-file
parameters:
zone: "dal12"
region: "us-south"
billingType: "hourly"
classVersion: "2"
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]"
type: "Performance"
reclaimPolicy: Delete
volumeBindingMode: Immediate
Show more





 Changing the default NFS version 

The following customized storage class lets you define the NFS version that you want to provision. For example, to provision NFS version 3.0, replace <nfs_version> with 3.0.

Example for Endurance File Storage for Classic.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-file-mount
labels:
IBM Cloud File Storage for Classic is ordered during your provisioning, and you can add more storage after.

Refer to the following documents on adding or removing data stores attached to the VMware Cluster by using NFS:



* [Adding NFS storage to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingremovingserverssection-adding-nfs-storage-to-vcenter-server-instances)
* [Removing NFS storage from vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingremovingserversvc_addingremovingservers-removing-nfs-storage)



More information on NFS for VMware is shown on the following documents:



* [Attached storage performance - Attached storage infrastructure design of IBM Cloud for VMware Solutions Dedicated](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-storage-infra-designstorage-infra-design-perf)
* [NFS storage - Storage Settings](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstancevc_orderinginstance-nfs-storage)



To expand and contract the storage capacity and performanc of individual mount points, see the following documents:



* [Expanding File Share Capacity - IBM Cloud Classic Infrastructure File Storage](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-expandCapacity)
* [Adjusting IOPS - IBM Cloud Classic Infrastructure File Storage](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-adjustingIOPS)







 Preparing your Operating System 

Deploy VMware virtual machines by importing an OS Image file or OVA and creating a new virtual machine Template, similar to any other VMware SDDC.
You can update the snapshot space for the new volume to add more, less, or no snapshot space. The snapshot space of the original volume is set by default.
11. Check the box to confirm that you read and agreed to the terms, then click Create to place your order.



After you click Create, the order confirmation window appears. When you close the window, you return to the resources list. You can go back to your list of File Storage for Classic shares to click the newly provisioned duplicate. The share details section displays information such as Duplicate Type, a link to the parent share's details page and the name of the snapshot that was used to create the duplicate.





 Creating a duplicate from the SLCLI 

The commands that are described in the topic are part of the SLCLI. For more information about how to install and use the SLCLI, see [Python API Client](https://softlayer-python.readthedocs.io/en/latest/cli/).

To create an independent duplicate File Storage for Classic volume, you can use the following command.

 slcli file volume-duplicate --help
Usage: slcli file volume-duplicate [OPTIONS] ORIGIN_VOLUME_ID

Options:
-o, --origin-snapshot-id INTEGER
ID of an origin volume snapshot to use for
duplcation.
-c, --duplicate-size INTEGER Size of duplicate file volume in GB. If
no size is specified, the size of the origin
volume will be used.
Minimum: [the size
of the origin volume]
-i, --duplicate-iops INTEGER Performance Storage IOPS, between 100 and
6000 in multiples of 100 [only used for
performance volumes] If no IOPS value is
specified, the IOPS value of the origin
volume will be used.
Requirements: [If
IOPS/GB for the origin volume is less than
0.3, IOPS/GB for the duplicate must also be
less than 0.3. If IOPS/GB for the origin
volume is greater than or equal to 0.3,
Then, click the name of the space.

Depending on how you want to modify the user permissions, select or clear the checkbox for a specific role. The roles that you can assign at the space level are Manager, Developer, and Auditor. For more information, see [Cloud Foundry roles](https://cloud.ibm.com/docs/account?topic=account-mngcfcfroles).
* To manage your domains, click the Actions icon ![Action icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) for the respective org, and select Domains.

As an account owner or organization manager, you can view the system domain and add custom domains for applications that are built within an org and its spaces. If you're a space manager, this page displays read-only list of the domains that are assigned to the space.

If you add a custom domain, you must configure your DNS server to resolve your custom domain to point to the IBM Cloud system domain. In this way, when IBM Cloud receives a request for your custom domain, it's properly routed to your app. The system domain is always available to a space, and custom domains might also be allocated to a space. Apps that are created in a space might use any of the domains that are listed for that space. For more information about creating and by using custom domains, see [Managing your domains](https://cloud.ibm.com/docs/apps?topic=apps-update-domain).
* To manage the allocated quota for an org, click the Actions icon ![Action icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) for the respective org, and select Quotas.
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/databases-for-etcd?topic=databases-for-etcd-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 disabled. Click Save Changes to save the configuration.





 Configuring Autoscaling in the CLI 

You can get the autoscaling parameters for your deployment through the CLI by 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.