vania-janet/multiturn-rag-retrieval-data huggingface dataset:
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 from the SLCLI 

"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.

You can authorize and connect hosts that are located in the same data center as your storage. You can have multiple accounts, but you can't authorize a host from one account to access your storage on another account.

To authorize a host, you can use the following commands in SLCLI.

 slcli block access-authorize --help
Usage: slcli block access-authorize [OPTIONS] VOLUME_ID

Options:
-h, --hardware-id TEXT The ID of a hardware server to authorize.
-v, --virtual-id TEXT The ID of a virtual server to authorize.
-i, --ip-address-id TEXT The ID of an IP address to authorize.
-p, --ip-address TEXT An IP address to authorize.
--help Show this message and exit.

 slcli block subnets-list -h
Usage: slcli block subnets-list [OPTIONS] ACCESS_ID
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.
You assign access to the specific access management tags for the file service. For more information about access groups, see [Setting up access groups](https://cloud.ibm.com/docs/account?topic=account-groups&interface=ui).
2. [Assign an access policy to a group](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorialtagging-assign-policy).
3. [Add users to the access group](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorialtagging-add-users-access-group).



When you look at the specific resources for the VPC infrastructure and specify File Storage for VPC as the resource type, you can see the access management tags for the file service.







 Manage file shares and mount targets from the CLI 

By using the CLI, you can:



* [Rename a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uirename-file-share-cli).
* [Rename a mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uirename-mount-target-cli).
* [Delete mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uidelete-mount-target-cli).
* [Delete a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uidelete-file-share-cli).
* [Update a file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uifs-update-profile-cli)



As of 30 May 2023, you can use --mount-targets instead of --targets option.
(https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-faqfaq-block-storage-16).





 Deleting a custom image 

For more information about deleting custom images from IBM Cloud VPC, see [Managing custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-custom-images&interface=ui). Be aware of any virtual server instances that you provisioned with a custom image. To remove all data associated with a specific custom image, make sure that you also delete any instances provisioned from the custom image, along with associated boot volumes.

When you want to delete an IBM Cloud VPC custom image that is part of a private catalog offering, you must first remove that image from the associated version in the private catalog offering. Then, you can delete the custom image from IBM Cloud VPC. To delete the custom image from the private catalog, see [Deprecating a private product](https://cloud.ibm.com/docs/account?topic=account-deprecate-product&interface=ui).





 Deleting VPC instances 

For more information about deleting a VPC and its associated resources, see [Deleting a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting).

The VPC data retention policy describes how long your data is stored after you delete the service. The data retention policy is included in the IBM Cloud® Virtual Private Cloud service description, which you can find in the [IBM Cloud Terms and Notices](https://cloud.ibm.com/docs/overview?topic=overview-terms).

The VPN and VPN policy configurations are deleted on request through the API or user interface.





 Restoring deleted data for VPC 

You can restore deleted root keys that you imported to the KMS within 30 days of deletion. For more information, see [Restoring deleted root keys](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-managingbyok-restore-root-key).
You assign access to the specific access management tags for the file service. For more information about access groups, see [Setting up access groups](https://cloud.ibm.com/docs/account?topic=account-groups&interface=ui).
2. [Assign an access policy to a group](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorialtagging-assign-policy).
3. [Add users to the access group](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorialtagging-add-users-access-group).



When you look at the specific resources for the VPC infrastructure and specify File Storage for VPC as the resource type, you can see the access management tags for the file service.







 Manage file shares and mount targets from the CLI 

By using the CLI, you can:



* [Rename a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apirename-file-share-cli).
* [Rename a mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apirename-mount-target-cli).
* [Delete mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apidelete-mount-target-cli).
* [Delete a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apidelete-file-share-cli).
* [Update a file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apifs-update-profile-cli)



As of 30 May 2023, you can use --mount-targets instead of --targets option.
The row headers identify the vSphere features. The column headers identify the NSF version. To see whether a feature is enabled navigate to the row of the feature, and look at the column that is associated with the NFS version that you use.

 vSphere Features NFS version 3 NFS version 4.1 

 vMotion and Storage vMotion Yes Yes 
 High Availability (HA) Yes Yes 
 Fault Tolerance (FT) Yes Yes 
 Distributed Resource Scheduler (DRS) Yes< Yes 
 Host Profiles Yes Yes 
 Storage DRS Yes No 
 Storage I/O Control Yes No 
 Site Recovery Manager Yes No 
 Virtual Volumes Yes No 



Source - [VMware® - NFS Protocols and ESXi](https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.storage.doc/GUID-8A929FE4-1207-4CC5-A086-7016D73C328F.html).





 Using Snapshots 

File Storage for Classic allows administrators to set snapshot schedules that create and delete snapshot copies automatically for each storage volume. They can also create extra snapshot schedules (hourly, daily, weekly) for automatic snapshots and manually create ad hoc snapshots for business continuity and disaster recovery (BCDR) scenarios. Automatic alerts are delivered through the [IBM Cloud® console to the volume owner for the retained snapshots and space used.

Snapshot space is required to use snapshots. Space can be purchased on the initial volume order or after the initial provisioning through the Volume Details page by clicking Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/action-menu-icon.svg) and selecting Add Snapshot Space.

It's important to note that VMware® environments are not aware of snapshots. The File Storage for Classic snapshot capability must not be confused with VMware® snapshots.
"href": "https://us-south.iaas.cloud.ibm.com/v1/virtual_network_interfaces/4727d842-f94f-4a2d-824a-9bc9b02c523b",
"id": "4727d842-f94f-4a2d-824a-9bc9b02c523b",
"name": "my-virtual-network-interface",
"resource_type": "virtual_network_interface"
},
"vpc": {
"crn": "crn:[...]",
"href": "$vpc_api_endpoint/v1/vpcs/8c95b3c1-fe3c-45c-97a6-e43d14088287",
"id": "82a7b841-9586-43b4-85dc-c0ab5e8b1c7a",
"name": "vpc-name1",
"resource_type": "vpc"
}
}

The mount target is deleted in the background. Confirm the deletion by trying to view the mount target information. If you get _404 Not Found_ error, the mount target is successfully deleted.





 Delete a file share in the API 

Before you delete a file share, make sure that it is [unmounted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfs-mount-unmount-vsi) from all virtual server instances and that all mount targets that belong to the file share are [deleted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingdelete-mount-target-api). Also, if the file share has a replica file share, you must remove the replication relationship.
Known issues and limitations 

Known issues and limitations include not being able to restrict access to some products in the IBM Cloud® catalog, and the maximum limits for creating IBM Cloud Identity and Access Management (IAM) resources.



 Catalog management settings don't apply to some IBM products 

Some products are not affected by the following catalog visibility settings:



* Turning off the visibility of the IBM Cloud catalog
* Excluding all IBM Cloud products from the catalog
* Excluding all IBM Cloud products from your private catalogs



You can view and manage catalog visibility settings by going to Manage > Catalogs > Settings in the IBM Cloud console.

Users can still create instances of the following products by using an API or the CLI, regardless of the catalog visibility setting in the account or private catalog:



* Block Storage for VPC
* Citrix Netscaler VPX
* Fortigate Security Appliance
* Hardware Firewall
* Hardware Firewall Dedicated
* IBM Cloud Backup for Classic
* IBM Cloud Bare Metal Servers
* IBM Cloud Block Storage for Classic
* IBM Cloud Container Registry
* IBM Cloud Content Delivery Network
* IBM Cloud Direct Link
* IBM Cloud Direct Link on Classic
* IBM Cloud Functions
* IBM Cloud Gateway Appliance
* IBM Cloud Hardware Security Modules
* IBM Cloud Kubernetes Service
* IBM Cloud Object Storage
* IBM Cloud Schematics
* IBM Cloud Load Balancer
* IBM Cloud Virtual Servers
* Subnets and IPs
* Virtual Private Cloud
* Virtual Server for VPC
* VLANs
* VPN
* VPN for VPC







 IBM Cloud IAM limits 

The following table lists the maximum limits for IAM resources. These limits apply to any user who can create IAM resources. If a limit is exceeded, you receive an exception and are not allowed to create any new resources beyond that limit.

If you have a specific use case that requires an extended limit, you can request an increase. For more information, see [Increasing account limits](https://cloud.ibm.com/docs/account?topic=account-account-limits).



Table 1. IAM account limits

 Resource Max 

 Access groups per account 500
The following variables are defined by Diego:

HOME
: The root directory of the deployed app.

MEMORY_LIMIT
: The maximum amount of memory that each instance of your app can use. You can specify the value in an app manifest.yml file, or on the command line when you push the app.

PORT
: The port on Diego for communication with the app. Diego allocates a port to the app at staging time.

PWD
: The current working directory that is running the buildpack.

TMPDIR
: The directory where temporary and staging files are stored.

USER
: The user ID that is running Diego.

VCAP_APP_HOST
: The IP address of the Diego host.

VCAP_APP
: A JSON string that contains information about the deployed app. The information includes the app name, URIs, memory limits, time stamp when the app achieved its current state, and other values. For example:

{
"limits": {
"mem": 512,
"disk": 1024,
"fds": 16384
},
"application_version": "df111903-7d95-4c20-96d9-aad4e97d2a9a",
"application_name": "testapp",
"application_uris": [
"testapp.AppDomainNamestage1.mybluemix.net"
],
"version": "df111903-7d95-4c20-96d9-aad4e97d2a9a",
"name": "testapp",
"space_name": "dev",
"space_id": "c6ed3a8e-436b-43ac-9f96-b676ee335000",
"uris": [
"testapp.AppDomainNamestage1.mybluemix.net"
],
"users": null,
Satellite Config <br><br> * Provide an interface to initiate change management activities, such as to update configurations or subscriptions.<br> * Automatically initiate the roll out of changes to a configuration to subscribed clusters.<br> * Automatically delete Kubernetes resources that run in subscribed clusters when you delete a configuration.<br><br><br> <br><br> * Use the provided [Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig) and [Red Hat OpenShift tools](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployupdating) to manage all changes to your apps. You are completely responsible for your app lifecycle, including any downtime that might occur when you update an app version, depending on your update rollout strategy.<br><br><br> 
 Satellite Link <br><br> * Maintain Satellite link connector versions.<br><br><br> <br><br> * Use the provided tools to [create, update, or delete the endpoints](https://cloud.ibm.com/docs/satellite?topic=satellite-link-location-cloud) that you need.<br> * [Enable and disable endpoints](https://cloud.ibm.com/docs/satellite?topic=satellite-link-cloud-createenable_disable_endpoint) to allow or block network traffic between your location and a service's endpoint.<br><br><br> 
 Satellite Storage <br><br> * Provide an interface to initiate a change management operation, such as deleting storage configurations or removing a cluster from a storage configuration.<br> * Provide version updates for IBM-provided storage templates.<br><br><br> <br><br> * Use the tools to delete storage configurations and cluster assignments. Note that if you remove these configurations, the storage drivers are uninstalled in the assigned clusters. Your PVCs, PVs, and data are not deleted.
Any block storage volume attached to the instance is deleted automatically if the volume was created with the flag delete_volume_on_instance_delete set to true. Otherwise, the instance is detached from the volume, but the volume remains. If any security group is attached to any of the instance's network interfaces, the security group is detached automatically as well, when the network interfaces are deleted.



Table 4. Information for deleting instances

 In Instance Can contain Can attach to Has Status? Automatically deleted when instance is deleted Automatically detached when deleted 

 Network interface Subnets, floating IP, security groups No Yes Yes 







 Load Balancer 

No prerequisites are required for deleting a load balancer. When the load balancer is deleted, all listeners, pools, and pool members that are part of the load balancer are deleted automatically.

Deleting a load balancer can take up to 30 minutes. The delete request immediately changes the provisioning status of the load balancer to deleting. However, the load balancer is not deleted until it disappears from the list query.





 VPN 

No prerequisites are required for deleting a VPN gateway. When the VPN gateway is deleted, its associated connections are also deleted automatically. IKE and IPsec policies are not deleted when a VPN gateway is deleted.

Deleting a VPN gateway can take up to 30 minutes. The delete request immediately changes the provisioning status of the VPN gateway to deleting. However, the VPN gateway is not deleted until it disappears from the list query.





 Volume 

Two types of volumes can exist in a VPC: a block storage boot volume and a block storage data volume. These volumes are deleted differently.



 Deleting boot volumes 

Boot volumes exist within an instance, and they are not considered to be separate entities from that instance. When you create an instance, a boot volume also is created and attached to the instance. The boot volume is deleted automatically when you delete the instance. You can't delete the boot volume without deleting the instance.





 Deleting data volumes 

Block storage data volumes can be provisioned and managed separately from their associated virtual server instances.
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. You must remove the PVC, PV, and the data separately.
3. Remove any pods that mount the PVC.



1. List the pods that mount the PVC.

oc get pods --all-namespaces -o=jsonpath='{range .items[]}{"n"}{.metadata.name}{":t"}{range .spec.volumes[]}{.persistentVolumeClaim.claimName}{" "}{end}{end}' | grep "<pvc_name>"

Example output

blockdepl-12345-prz7b: claim1-block-bronze

If no pod is returned in your CLI output, you don't have a pod that uses the PVC.
2. Remove the pod that uses the PVC.

If the pod is part of a deployment, remove the deployment.

oc delete pod <pod_name>
3. Verify that the pod is removed.

oc get pods



4. Remove the PVC.

oc delete pvc <pvc_name>
5. Review the status of your PV. Use the name of the PV that you retrieved earlier as VOLUME.

oc get pv <pv_name>

When you remove the PVC, the PV that is bound to the PVC is released. Depending on how you provisioned your storage, your PV goes into a Deleting state if the PV is deleted automatically, or into a Released state, if you must manually delete the PV. Note: For PVs that are automatically deleted, the status might briefly say Released before it is deleted.
Review the Satellite storage classes for NetApp ONTAP-SAN. You can describe storage classes in the command line with the oc describe sc <storage-class-name> command.



netapp-ontap-san version 21.04 parameter reference

 Storage class name Type File system IOPs Encryption Reclaim policy 

 sat-netapp-block-goldDefault ONTAP-SAN ext4 no QoS limits. Encryption disabled. Delete 
 sat-netapp-block-gold-encrypted ONTAP-SAN ext4 no QoS limits. Encryption enabled. Delete 
 sat-netapp-block-silver ONTAP-SAN ext4 User-defined QoS limit. Encryption disabled. Delete 
 sat-netapp-block-silver-encrypted ONTAP-SAN ext4 User-defined QoS limit. Encryption enabled. Delete 
 sat-netapp-block-bronze ONTAP-SAN ext4 User defined QoS limit. Encryption disabled. Delete 
 sat-netapp-block-bronze-encrypted ONTAP-SAN ext4 User-defined QoS limit. Encryption enabled. Delete 







 Getting help and support for NetApp ONTAP-SAN 

If you run into an issue with NetApp Trident, you can visit the [NetApp support page](https://netapp-trident.readthedocs.io/en/stable-v20.04/support/support.html).
CSIResizerMemoryLimit: "160Mi" container:csi-resizer, resource-type: memory-limit
BlockDriverCPULimit: "300m" container:iks-vpc-block-driver, resource-type: cpu-limit
BlockDriverMemoryLimit: "600Mi" container:iks-vpc-block-driver, resource-type: memory-limit
CSISnapshotterCPULimit: "80m" container:csi-snapshotter, resource-type: cpu-limit
CSISnapshotterMemoryLimit: "160Mi" container:csi-snapshotter, resource-type: memory-limit
CSISnapshotterRetryIntervalStart: "1s" container:csi-snapshotter, Initial retry interval of failed volume snapshot creation or deletion.
CSISnapshotterRetryIntervalMax: "300s" container:csi-snapshotter, Maximum retry interval of failed volume snapshot creation or deletion.
CSISidecarLogLevel: "5" container:csi-snapshotter, glog/klog log level
IsSnapshotEnabled : "true"		container: iks-vpc-block-driver
CustomSnapshotCreateDelay: "300"		container: iks-vpc-block-driver
Show more







 Turning off snapshots 

By default, snapshot functionality is enabled when using the Block Storage for VPC. This functionality can be turned off in the configmap addon-vpc-block-csi-driver-configmap in the kube-system namespace by changing the IsSnapshotEnabled to false. Note that with this change in the configmap, any snapshots that are created fail with the message: "CreateSnapshot functionality is disabled."



1. Save the current configmap from your cluster to your local machine.

kubectl get cm -n kube-system addon-vpc-block-csi-driver-configmap -o yaml >> snapshotconfigmap.yaml
2.
Use the name of the PV that you retrieved earlier as VOLUME. When you remove the PVC, the PV that is bound to the PVC is released. Depending on how you provisioned your storage, your PV goes into a Deleting state if the PV is deleted automatically, or into a Released state, if you must manually delete the PV. Note: For PVs that are automatically deleted, the status might briefly say Released before it is deleted. Rerun the command after a few minutes to see whether the PV is removed.

oc get pv <pv_name>
8. If your PV is not deleted, manually remove the PV.

oc delete pv <pv_name>
9. Verify that the PV is removed.

oc get pv
10. List the physical storage instance that your PV pointed to and note the id of the physical storage instance.

ibmcloud sl block volume-list --columns id --columns notes | grep <pv_name>

Example output

12345678 {"plugin":"ibmcloud-block-storage-plugin-689df949d6-4n9qg","region":"us-south","cluster":"aa1a11a1a11b2b2bb22b22222c3c3333","type":"Endurance","ns":"default","pvc":"block-storage-pvc","pv":"pvc-d979977d-d79d-77d9-9d7d-d7d97ddd99d7","storageclass":"ibmc-block-silver","reclaim":"Delete"}

Understanding the Notes field information:

"plugin":"ibm-file-plugin-5b55b7b77b-55bb7"
: The storage plug-in that the cluster uses.

"region":"us-south"
: The region that your cluster is in.
curl -X PUT https://private.us-south.atracker.cloud.ibm.com/api/v1/targets -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json" -d '{
"name": "My COS target",
"target_type": "cloud_object_storage",
"cos_endpoint": {
"endpoint": "s3.private.us-south.cloud-object-storage.appdomain.cloud",
"target_crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/<account-id>:<instance-id>::",
"bucket": "my-activity-tracking-bucket",
"api_key": "xxxxxxxxxxxxxxxxxx"
}
}'





 Deleting a target using the API 

You can use the following cURL command to delete a target:

curl -X DELETE <ENDPOINT>/api/v1/targets/<target_ID> -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"

Where



* ENDPOINT is the API endpoint in the region where you plan to configure or manage a target. For more information, see [Endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpointsendpoints_api).
* <target_ID> is the ID of the target.







 Validating a target using the API 

You can use the following cURL command to validate a target by checking the credentials to write to the bucket.

curl -X POST <ENDPOINT>/api/v1/targets/<target_ID>/validate -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"

Where



* ENDPOINT is the API endpoint in the region where you plan to configure or manage a target.