vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Cleaning up your Portworx volumes and cluster 

Remove a [Portworx volume](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_removingremove_pvc_apps_volumes), a [storage node](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_removingremove_storage_node_cluster-px), or the [entire Portworx cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_removingremove_storage_node_cluster-px) if you don't need it anymore.



 Removing Portworx volumes from apps 

When you added storage from your Portworx cluster to your app, you have three main components: the Kubernetes persistent volume claim (PVC) that requested the storage, the Kubernetes persistent volume (PV) that is mounted to your pod and described in the PVC, and the Portworx volume that blocks space on the physical disks of your Portworx cluster. To remove storage from your app, you must remove all components.



1. List the PVCs in your cluster and note the NAME of the PVC, and the name of the PV that is bound to the PVC and shown as VOLUME.

oc get pvc

Example output

NAME STATUS VOLUME CAPACITY ACCESSMODES STORAGECLASS AGE
px-pvc Bound pvc-06886b77-102b-11e8-968a-f6612bb731fb 20Gi RWO px-high 78d
2. Review the ReclaimPolicy for the storage class.

oc describe storageclass <storageclass_name>

If the reclaim policy says Delete, your PV and the data on your physical storage in your Portworx cluster are removed when you remove the PVC. If the reclaim policy says Retain, or if you provisioned your storage without a storage class, then your PV and your data are not removed when you remove the PVC.
* [ibmcloud oc storage attachment get](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_get)
* [ibmcloud oc storage attachment ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_ls)
* [ibmcloud oc storage attachment rm](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_rm)
* [ibmcloud oc storage volume get](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_ls_c)
* [ibmcloud oc storage volume ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_ls_2)



* [Satellite commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clisat_commands)



* [ibmcloud oc cluster create satellite](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicli_cluster-create-satellite)
* [ibmcloud oc cluster master satellite-service-endpoint allowlist add](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicluster-master-sat-allowlist-add)
* [ibmcloud oc cluster master satellite-service-endpoint allowlist disable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicluster-master-sat-allowlist-disable)
(https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 [Expandable storage](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-expandingcapacity) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.]
* [Verifying the encryption of your Block Storage for Classic volumes](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_encrypt)



* [Adding block storage to apps](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageadd_block)
* [Using existing block storage in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageexisting_block)



* [Retrieving the information of your existing block storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageexisting-block-1)
* [Creating a persistent volume (PV) and a matching persistent volume claim (PVC)](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageexisting-block-2)



* [Using block storage in a stateful set](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_statefulset)



* [Creating the PVC by using dynamic provisioning when you create a stateful set](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_dynamic_statefulset)
* [Static provisioning by using existing PVCs with a stateful set](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_static_statefulset)



* [Changing the size and IOPS of your existing storage device](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_change_storage_configuration)
* [Backing up and restoring data](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_backup_restore)
Check out [Troubleshooting Ingress](https://cloud.ibm.com/docs/containers?topic=containers-ingress-debug) and [Troubleshooting load balancers](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_loadbalancer_fails).





 Add app storage 



1. Storage basics: Start by understanding the [basics of Kubernetes storage](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_concepts).
2. Requirements: Determine your [requirements for a storage solution](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan).
3. Choose a solution: Using your storage requirements, choose a storage solution by comparing [your options](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan).



Need help? Check out the troubleshooting page for your persistent storage solution.





 Add integrations 

Enhance app capabilities by integrating various external services and catalog services in your cluster with your app.



1. Review supported integrations:



* [All supported integrations](https://cloud.ibm.com/docs/containers?topic=containers-supported_integrationssupported_integrations)
* [Red Hat OpenShift on IBM Cloud partners](https://cloud.ibm.com/docs/openshift?topic=openshift-service-partners)
* [IBM Cloud services and third-party integrations](https://cloud.ibm.com/docs/openshift?topic=openshift-ibm-3rd-party-integrations)
* [Cloud Paks](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_cloud_paks)
* [Operators](https://cloud.ibm.com/docs/openshift?topic=openshift-operators)



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

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

Examples:

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

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





 ibmcloud sl file volume-count 

List number of file storage volumes per data center:

ibmcloud sl file volume-count [OPTIONS]

Command options:

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





 ibmcloud sl file volume-limits 

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

ibmcloud sl file volume-limits

Examples:

ibmcloud sl file volume-limits

This command lists the storage limits for this account.





 ibmcloud sl file volume-list 

List file storage:

ibmcloud sl file volume-list [OPTIONS]

Command options:

-u, --username
: Filter by volume username.

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

-t, --storage-type
: Filter by type of storage volume, options are: performance, endurance.

-o, --order
: Filter by ID of the order that purchased the file storage.

--sortby
: Column to sort by. Default: id. Options are: id, username, datacenter, storage_type, capacity_gb, bytes_used, ip_addr,active_transactions, created_by, mount_addr.

--column
: Column to display. Options are: id, username, datacenter, storage_type, capacity_gb, bytes_used, ip_addr, active_transactions,mount_addr, created_by, notes. This option can be specified multiple times.

Examples:

ibmcloud sl file volume-list -d dal09 -t endurance --sortby capacity_gb
* [Creating a storage assignment in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverstorage-azuredisk-csi-driver-include-assignment-create-console)
* [Creating an assignment in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverstorage-azuredisk-csi-driver-include-assignment-create-cli)
* [Creating a storage assignment in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverstorage-azuredisk-csi-driver-include-assignment-create-api)
* [Deploying an app that uses your Azure Disk storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverstorage-azure-csi-app-deploy)
* [Removing Azure Disk storage from your apps](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazure-disk-rm)
* [Removing the Azure Disk storage configuration from your cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazure-disk-template-rm)



* [Removing the Azure Disk storage configuration from the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazure-disk-template-rm-ui)
* [Removing the Azure Disk storage configuration from the cli](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazure-disk-template-rm-cli)



* [Parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azuredisk-csi-driverazuredisk-csi-driver-parameter-reference)
List block storage assigned subnets for the given host id.
access_id is the host_id obtained by: slcli block access-list <volume_id>

Options:
-h, --help Show this message and exit.

 slcli block subnets-assign -h
Usage: slcli block subnets-assign [OPTIONS] ACCESS_ID
Assign block storage subnets to the given host id.
access_id is the host_id obtained by: slcli block access-list <volume_id>

Options:
--subnet-id INTEGER ID of the subnets to assign; e.g.: --subnet-id 1234
-h, --help Show this message and exit.

 slcli block subnets-remove -h
Usage: slcli block subnets-remove [OPTIONS] ACCESS_ID
Remove block storage subnets for the given host id.
access_id is the host_id obtained by: slcli block access-list <volume_id>

Options:
--subnet-id INTEGER ID of the subnets to remove; e.g.: --subnet-id 1234
-h, --help Show this message and exit.

The default limit for the number of authorizations per block volume is eight. That means that up to eight hosts can be authorized to access the Block Storage for Classic LUN. Customers who use Block Storage for Classic in their VMware deployment can request the authorization limit to be increased to 64. To request a limit increase, contact your sales representative or raise a [Support case](https://cloud.ibm.com/unifiedsupport/cases/add).





 Authorizing hosts to access Block Storage for Classic with Terraform 

"Authorized" hosts are hosts that were given access to a particular LUN. Without host authorization, you can't access or use the storage from your system. Authorizing a host to access your LUN generates the username, password, and iSCSI qualified name (IQN), which are needed to mount the multipath I/O (MPIO) iSCSI connection.
* [Enabling every user to customize the default PVC settings](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockcustomize-with-secret)
* [Enforcing base64 encoding for the Key Protect root key CRN](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockstatic-secret)



* [Setting up volume expansion](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-block-volume-expand)



* [Manually expanding volumes before add-on version 4.2](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockexpanding-existing-volumes)



* [Backing up and restoring data](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-block-backup-restore)
* [Storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-block-reference)



* [10 IOPs tier](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-block10iops-sc-vpc-block)
* [5 IOPs tier](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-block5iops-sc-vpc-block)
* [Custom](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockcustom-sc-vpc-block)
* [General purpose](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockgen-purp-sc-vpc-block)
* [ibmcloud oc storage attachment ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_ls)
* [ibmcloud oc storage attachment rm](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_rm)



* storage volume: View a list of storage volumes.



* [ibmcloud oc storage volume get](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_ls_c)
* [ibmcloud oc storage volume ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_ls_2)
The snapshot is taken weekly on every Sunday at 2:00, and up to 5 snapshots are retained.





 ibmcloud sl file snapshot-delete 

Delete a snapshot on a volume:

ibmcloud sl file snapshot-delete SNAPSHOT_ID

Examples:

ibmcloud sl file snapshot-delete 12345678

This command deletes snapshot with ID 12345678.





 ibmcloud sl file snapshot-list 

List file storage snapshots:

ibmcloud sl file snapshot-list VOLUME_ID [OPTIONS]

Command options:

--sortby
: Column to sort by. Options are: id, name, created, size_bytes.

Examples:

ibmcloud sl file snapshot-list 12345678 --sortby id

This command lists all snapshots of volume with ID 12345678 and sorts them by ID.





 ibmcloud sl file snapshot-order 

Order snapshot space for a file storage volume:

ibmcloud sl file snapshot-order VOLUME_ID [OPTIONS]

Command options:

-s, --size
: Required. Size of snapshot space to create in GB.

-t, --tier
: Optional. Endurance Storage Tier (IOPS per GB) of the file volume for which space is ordered. Options are: 0.25, 2, 4, 10.

-i, --iops
: Performance Storage IOPs. Range 100-6000, and in multiples of 100.

-u, --upgrade
: Flag to indicate that the order is an upgrade.

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

Examples:

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

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





 ibmcloud sl file snapshot-restore 

Restore a file volume by using a specified snapshot:
Viewing portable storage 

Portable storage is an auxillary storage disk that you can detach from one virtual server and attach to another. You can connect portable storage disk to virtual server at a time while all information that is stored on the disk is retained for transfer between devices. Portable storage can be purchased and applied to your virtual server at any time.



  Before you begin 

First, go to the device menu and make sure that you have the correct account permissions to complete the tasks.



*  Go to your device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-navigating-devices).
*  Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





  Viewing portable storage 

To view portable storage, complete the following steps:



1.  From the Devices menu, select Device List.
2.  From the Device List, select the virtual server instance that contains the portable storage device that you want.
3.  Click the Storage tab to view the portable storage that is attached to the instance.
Satellite Storage <br><br> * Provide an interface to initiate operational activities, such as creating storage configurations and assign configurations to clusters that are attached to a location.<br> * Provide a set of storage templates to automatically install storage driver components in an attached cluster and provide storage classes to manage app storage.<br><br><br> <br><br> * Select the storage type that best meets your app requirements for data types, data access frequency, performance, durability, resiliency, availability, scalability, and encryption.<br> * Procure any physical or virtual storage instances in your on-premises data center or in public cloud providers that cannot be automatically provisioned by using the installed storage driver.<br> * Use the provided tools to create storage configurations and to assign configurations to an attached cluster.<br> * Use the Red Hat OpenShift CLI to provision persistent volumes and persistent volume claims to fulfill storage requirements for your apps.<br> * Debug any issues that occur when using storage for your apps.<br><br><br> 
 [Satellite-enabled IBM Cloud service](https://cloud.ibm.com/docs/satellite?topic=satellite-managed-services) <br><br> * Provide the ability to deploy a select group of IBM Cloud services such as [Red Hat OpenShift clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusters) to a Satellite location.<br> * Review each service's documentation for additional responsibilities that IBM maintains.<br><br><br> <br><br> * Use the provided tools to set up additional services as needed.<br> * Provide enough hosts for the services to use as compute capacity, per the service documentation.<br> * Review each service's documentation for additional responsibilities that you fulfill when you use these services.<br><br><br> 
 Satellite Connector <br><br> * Provide an interface to initiate operational activities, such as to create and delete connectors.<br> * Automatically forward connector events to your IBM Cloud Activity Tracker instance.<br><br><br> Use the provided tools to create a connector.
* [Deploying a stateful set that uses Block Storage for VPC](https://cloud.ibm.com/docs/containers?topic=containers-vpc-block-storage-driver-unmanagedvpc-block-stateful-set-deploy)
* [Removing the Block Storage for VPC driver](https://cloud.ibm.com/docs/containers?topic=containers-vpc-block-storage-driver-unmanagedremoving-the-block-storage-for-vpc-driver)
* [Config map reference](https://cloud.ibm.com/docs/containers?topic=containers-vpc-block-storage-driver-unmanagedvpc-block-um-cm-ref)



* [RHEL or CentOS ConfigMap](https://cloud.ibm.com/docs/containers?topic=containers-vpc-block-storage-driver-unmanagedvpc-block-rhel-cm)
* [Ubuntu ConfigMap](https://cloud.ibm.com/docs/containers?topic=containers-vpc-block-storage-driver-unmanagedvpc-block-ubuntu-cm)





[Removing Block Storage for VPC from your cluster](https://cloud.ibm.com/docs/containers?topic=containers-storage-block-vpc-removestorage-block-vpc-remove)



* [Cleaning up Block Storage for VPC](https://cloud.ibm.com/docs/containers?topic=containers-storage-block-vpc-removecleaning-up-block-vpc)







 Setting up IBM Cloud File Storage for VPC 

[Enabling the IBM Cloud File Storage for VPC add-on](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-installstorage-file-vpc-install)



* [Prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-installprereqs-store-file-vpc)
oc get deployments

oc get statefulset
5. Delete the PVC.

oc delete pvc <pvc_name>
6. Verify that your PV is automatically removed.

oc get pv







 Removing the Compute Engine storage configuration from your cluster 

If you no longer plan on using your persistent disk storage in your cluster, you can use the CLI unassign your cluster from the storage configuration.

Note that if you remove the storage configuration, the driver is then uninstalled from all assigned clusters. Your PVCs, PVs, and data are not removed. However, you might not be able to access your data until you re-install the driver in your cluster again.



 Removing the Google Compute Engine storage configuration from the console 

Use the console to remove a storage configuration.



1. From the Satellite storage dashboard, select the storage configuration you want to delete.
2. Select Actions > Delete
3. Enter the name of your storage configuration.
4. Select Delete.







 Removing the Google Compute Engine storage configuration from the CLI 



1. List your storage assignments and find the one that you used for your cluster.

ibmcloud sat storage assignment ls (--cluster CLUSTER | --config CONFIG | --location LOCATION | --service-cluster-id CLUSTER)
2. Remove the assignment. After the assignment is removed, the driver pods and storage classes are removed from all clusters that were part of the storage assignment.

ibmcloud sat storage assignment rm --assignment <assignment_ID>
3. Verify that the driver is removed from your cluster.



1. List of the storage classes in your cluster and verify that the storage classes are removed.

oc get sc
2. List the pods in the kube-system namespace and verify that the storage driver pods are removed.

oc get pods -n kube-system | grep gce



4. Optional: Remove the storage configuration.



1. List the storage configurations.

ibmcloud sat storage config ls
2. Remove the storage configuration.
6. If your PVC is not mounted by a pod, [create a pod or deployment and mount the PVC](https://cloud.ibm.com/docs/containers?topic=containers-block_storageadd_block). If your PVC is mounted by a pod, continue with the next step.
7. Verify that the size and IOPS are changed in the Labels section of your CLI output. This process might take a few minutes to complete.

kubectl describe pv <pv_name>

Example output

...
Labels: CapacityGb=50
Datacenter=dal10
IOPS=500
8. Log in to the pod that mounts the PVC.

kubectl exec -i -t bash
9. Resize the file system.

sudo resize2fs <filesystem-path>

Example command

sudo resize2fs /dev/vdg
10. Verify the file system is resized.

df -h







 Backing up and restoring data 

Block storage is provisioned into the same location as the worker nodes in your cluster. The storage is hosted on clustered servers by IBM to provide availability in case a server goes down. However, block storage is not backed up automatically and might be inaccessible if the entire location fails. To protect your data from being lost or damaged, you can set up periodic backups that you can use to restore your data when needed.

Review the following backup and restore options for your block storage:



 Setting up periodic snapshots 

You can [set up periodic snapshots for your block storage](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-snapshotssnapshots), which is a read-only image that captures the state of the instance at a point in time.

To store the snapshot, you must request snapshot space on your block storage. Snapshots are stored on the existing storage instance within the same zone. You can restore data from a snapshot if a user accidentally removes important data from the volume.