vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"href": "$vpc_api_endpoint/v1/regions/us-south/zones/us-south-1",
"name": "us-south-1"
}
}

The file share is deleted in 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.

A DELETE /shares/$share_id call can optionally include an If-Match header that specifies an ETag hash string. Make a GET /shares/{share_id} call and copy the ETag hash string from the response header. For more information, see [User tags for file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-aboufs-about-user-tags).









 Manage file shares and mount targets with Terraform 

With Terraform, you can:



* [Change file share attributes such as name, size, profile, tags](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfile-storage-share-update-terraform),
* [Add](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create-replication&interface=terraformfs-create-replica-terraform) or [remove a replica relationship](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=terraformfs-remove-replication-terraform).
* [Change the name of a mount target](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfile-storage-mount-target-update-terraform).
* [Delete a file share or a mount target](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingdelete-file-share-terraform).





 Update attributes of a file share with Terraform
Optionally, you can use your own root keys (CRKs) by choosing customer-managed encryption during instance creation (see [Customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-aboutvpc-customer-managed-encryption)).

By default, boot volumes are deleted when you delete an instance. You can toggle this setting on or off in the instance details. A boot volume can be unattached only by deleting the instance that it is attached to. A boot volume cannot be detached from an instance while the instance exists. For more information, see [Viewing instance details](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=uiviewing-virtual-server-instances-ui).





 Data volumes 

Block Storage for VPC data volumes are secondary volumes with total capacity range of 10 GB to 16,000 GB. Maximum IOPS for data volumes varies based on volume size. For more information, see [Block Storage for VPC profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles).

You can create data volumes as stand-alone volumes or when you provision an instance. Stand-alone volumes exist in an unattached state until you attach the volume to an instance. When you create a data volume as part of instance provisioning, the volume is automatically attached to the instance.

When you create an IBM Cloud Hyper Protect Virtual Servers for IBM Cloud® Virtual Private Cloud instance, the data volume that is attached to the instance during instance creation is automatically encrypted with the seed or passphrase that you provide.

Block Storage for VPC data volumes can be attached to any available instance in your region, based on your customer account and permissions, and within [certain limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits). These volumes are detached by default when the instance is deleted. Detaching by default allows your data to persist beyond the virtual server instance lifecycle.
Storage volumes for Databases for MySQL deployments are provisioned on [Block Storage Endurance Volumes in the 10 IOPS per GB tier](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-orderingBlockStorage&interface=ui). If your operational load saturates or exceeds the IOPS limit, database requests and operations are delayed until the disk can catch up. Extended periods of heavy-load can cause your deployment to be unable to process queries and become effectively unavailable. If you experience delayed responses and failing operations, you might be exceeding the disk's IOPS limit. You can increase the number IOPS available to your deployment by increasing disk space.





 Connection Limits 

Databases for MySQL sets the maximum number of connections to your MySQL database to 200. Leave some connections available, as a number of them are reserved internally to maintain the state and integrity of your database. After the connection limit is reached, any attempts at starting a new connection results in an error. To prevent overwhelming your deployment with connections, use connection pooling, or scale your deployment and increase its connection limit. For more information, see the [Managing MySQL Connections](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-managing-mysql-connections) page.
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. To create a policy group on the storage system, log in to the system CLI and run the netapp1::> qos policy-group create -policy-group <policy_group_name> -vserver <svm_name> [-min-throughput <min_IOPS>] -max-throughput <max_IOPS> command.

The min-throughput options is supported only on all-flash systems. For more information about creating and managing QoS Policy groups, see the [ONTAP 9 Storage Management documentation](https://docs.netapp.com/us-en/ontap/index.html).

To use an encrypted storage class, NetApp Volume Encryption (NVE) must be enabled on your storage system by using either the NetApp ONTAP onboard key manager or a supported (off-box) third-party key manager, such as IBM 's TKLM key manager. To enable the onboard key manager, run the netapp1::> security key-manager onboard enable command. For more information about configuring encryption, see the [ONTAP 9 Security and Data Encryption documentation](https://docs.netapp.com/us-en/ontap/security-encryption/index.html).

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
[menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. Locate the volume from the list.
3. In the tags column, click Add tags.
4. In the Add tags menu, enter the access management tags in the access management tag field. Tags that you created display as you type.
5. Click Save.







 Step 3 - Assigning access and users 

After you create an access management tag and apply it to a volume, complete the following steps to assign access and add users.



1. [Create an access group](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorialtagging-create-access-group). Access groups are assigned policies that grant roles and permissions to the members of that group. You assign access to the specific access management tags for the Block Storage for VPC 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 Block Storage for VPC as the resource type, you can see the access management tags for the Block Storage for VPC service.







 Deleting a Block Storage for VPC volume and data eradication 

When you delete a Block Storage for VPC volume, that data immediately becomes inaccessible. All pointers to the data on the physical disk are removed. If you later create a volume in the same or another account, a new set of pointers is assigned.
Delete file shares and mount targets with the API 

Before you can delete a file share, make sure that all mount targets that belong to the file share are [deleted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apidelete-mount-target-api). The file share must be in a stable or failed state (that is, when provisioning fails).

If the file share is configured for replication, you myust take extra steps. For more information, see [Deleting a replica file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=apifs-delete-replicas).



 Delete mount target of a file share with the API 

Make a DELETE /shares/{share_ID}/mount_targets/{target_id} call to delete a mount target of a file share. The file share must be in a stable state.

See the following example.

curl -X DELETE "$vpc_api_endpoint/v1/shares/$share_id/mount_targets/$target_id?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: Bearer ${API_TOKEN}"

A successful response has a confirmation of acceptance for deletion and response that contains the target information. Status of mount target shows deleting while the deletion is underway.

The following example deletes a mount target where access_control_mode is security_group. The response shows the security group and subnet. You can also see the specifics of the reserved IP address that was used for the virtual network interface of the mount target in the primary_ip section. By default the virtual network interface is deleted along with the mount target when the mount target is deleted.

{
"access_control_mode": "security_group",
"created_at": "2023-05-30T01:59:46.000Z",
If the file share is configured for replication, you need to take extra steps. For more information, see [Deleting a replica file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=apifs-delete-replicas).



 Delete mount target of a file share in the UI 

To delete a mount target, the file share must be in a stable state.



1. Select a file share from the [list of file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-viewfile-storage-view-shares-targets-ui).
2. On the File share details page, select a mount target that you want to delete.
3. Click the overflow menu (ellipsis) and select Delete.







 Delete a file share in the UI 

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-ui).

The file share must be in a stable state or failed state (that is, when provisioning fails).



1. Select a file share from the [list of file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view).
2. Click the overflow menu at the end of the row and select Delete.











 Add user tags to a file share 

You can add user tags to new or existing file shares, modify, and delete tags for a file share with the UI, CLI, API, and Terraform. You can view tags throughout your account by filtering by tags from your resource list. You can also add user tags to replica file shares.
If the file share is configured for replication, you need to take extra steps. For more information, see [Deleting a replica file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=apifs-delete-replicas).



 Delete mount target of a file share in the UI 

To delete a mount target, the file share must be in a stable state.



1. Select a file share from the [list of file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-viewfile-storage-view-shares-targets-ui).
2. On the File share details page, select a mount target that you want to delete.
3. Click the overflow menu (ellipsis) and select Delete.







 Delete a file share in the UI 

Before you delete a file share, make sure that it is [unmounted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apifs-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-managing&interface=apidelete-mount-target-ui).

The file share must be in a stable state or failed state (that is, when provisioning fails).



1. Select a file share from the [list of file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view).
2. Click the overflow menu at the end of the row and select Delete.











 Add user tags to a file share 

You can add user tags to new or existing file shares, modify, and delete tags for a file share with the UI, CLI, API, and Terraform. You can view tags throughout your account by filtering by tags from your resource list.
* 12,000 GB



* Storage performance (0.25, 2, or 4 IOPS/GB)



As part of the Veeam service installation and configuration, the following repositories are created:



* For the Veeam configuration backup files - a repository named IC4V Default Config Backup Repository. The path to the folder where the Veeam backups are stored is <Drive>:ConfigBackup\.
* For scale-out, a repository named IC4V Scale-Out Repository. For more information, see [Adding a scale-out repository](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-icos_orderingicos_ordering-scale-repo).
* For the virtual machine (VM) backups - a repository named IC4V Default VM Backup Repository. The path to the folder where the VM backups are stored is <Drive>:VMBackup\. This repository is added as an extent to IC4V Scale-Out repository.







 Networking for Veeam 9.5u4b 

One primary private IP address.





 Licenses and fees for Veeam 9.5u4b 

Veeam Availability Suite v9.5 (10, 25, 50, 100, or 200 VM license)







 Considerations when you delete Veeam 9.5u4b 

Deleting the Veeam service stops all backups and deletes all the previous backups. The backup of the management VMs stops and the deletion of previous backups is irreversible. If the management VMs are corrupted, they can't be restored.





 Related links 



* [Veeam Backup and Replication 12 overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeamvm_overview)
* [Managing Veeam](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managingveeam)
If the file share is configured for replication, you need to take extra steps. For more information, see [Deleting a replica file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=apifs-delete-replicas).



 Delete mount target of a file share in the UI 

To delete a mount target, the file share must be in a stable state.



1. Select a file share from the [list of file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-viewfile-storage-view-shares-targets-ui).
2. On the File share details page, select a mount target that you want to delete.
3. Click the overflow menu (ellipsis) and select Delete.







 Delete a file share in the UI 

Before you delete a file share, make sure that it is [unmounted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uifs-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-managing&interface=uidelete-mount-target-ui).

The file share must be in a stable state or failed state (that is, when provisioning fails).



1. Select a file share from the [list of file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view).
2. Click the overflow menu at the end of the row and select Delete.











 Add user tags to a file share 

You can add user tags to new or existing file shares, modify, and delete tags for a file share with the UI, CLI, API, and Terraform. You can view tags throughout your account by filtering by tags from your resource list.
You can configure the storage capacity and throughput by using the volume_xxx parameters. The value for the volume_profile parameter can be either general purpose or custom. When general-purpose is used, IOPS is determined by the cloud infrastructure and the volume_iops parameter does not have any effect. If you want to customize the IOPS, you need to use custom for volume_profiles and set up the IOPS through volume_iops based on the capacity that is specified in volume_capacity. For more information, see [Block storage profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles&interface=ui).







 Step 5: Accessing the HPC cluster 

To access your HPC cluster, complete the following steps:



1. Go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/74a831a53989757bd05bd0dea7bb42c9ede61d0f/icons/icon_hamburger.svg) > Activity > Plan applied > View log.
2. Copy ssh-command to access your cluster.



* ssh -J root@ip-jumphost lsfadmin@ip-managementhost
* The ip-jumphost is public, while the ip-managementhostis not.
* -J flag: Connects to the jump-host and establishes a TCP forwarding to the ultimate destination (management host).









 Step 6: Auto scaling 

You have a minimum number of worker nodes (worker_node_min_count). This is the number of worker nodes that are provisioned at the time the cluster is created. However, you can use a maximum number of worker nodes that should be added to the Spectrum LSF cluster defined by worker_node_max_count. This is to limit the number of machines that can be added to Spectrum LSF cluster when the auto scaling configuration is used. This property can be used to manage the cost associated with Spectrum LSF cluster instance.
* After you create a volume, can't change a volume's IOPS tier profile.
* You can't independently modify IOPS for a volume that is created from an IOPS tier profile. IOPS is adjusted when you expand a volume's capacity and then restart the instance, or attach and detach the volume from the instance.
* When you expand a volume that was created from a custom profile, the capacity is increased but the IOPS remains the same. You can't independently increase the IOPS.
* Maximum IOPS for a volume is capped at [48,000 IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles&interface=apitiers).
* After a volume is expanded, you can't reduce the size of the volume.
* When a volume is in transition, for example, the volume is detached while the volume expansion is in progress, the volume remains in an updating state until you reattach it to an instance. The volume expansion the resumes and completes.
* When you delete an instance, volumes that are marked for auto-deletion are not deleted when volume expansion is underway. For more information, see [troubleshooting](https://cloud.ibm.com/docs/vpc?topic=vpc-troubleshooting-block-storagetroubleshoot-topic-4).







 Boot volume limitations 



* Boot volume capacity cannot be smaller than the size of the image. If the custom image is smaller than 10 GB, boot volume capacity is rounded up to 10 GB.
* You cannot increase boot volume capacity beyond the maximum image size, which is 250 GB.
* Boot volumes stored as unattached secondary volumes can't be expanded.
* Resizing takes place without a reboot. However, you must expand the size in your operating system so that the boot volume is recognized.
* Z/OS systems are not supported.









 Next steps 



* [Expand block storage volumes that are attached to an instance](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes).
The backup of the management VMs or VSIs stops and the deletion of previous backups is irreversible. If the management VMs or VSIs are corrupted, they can’t be restored.

Review the following considerations before you delete the service:



* Deleting the Veeam service does not cancel the Veeam license. You must delete the Veeam license from the Veeam licenses table on the Licenses page in the IBM Cloud for VMware Solutions console.
* When you delete the Veeam service, the VMware Solutions automation deletes only the single Veeam VM, VSI, or bare metal server that was deployed and the dedicated private subnet that was ordered for it. If you scaled out the Veeam VM or VSI into multiple ones, those additional VMs or VSIs are not deleted.
* If you order iSCSI storage, that storage is deleted when you delete the Veeam service. Therefore, any data within that storage is lost.







 Related links 



* [Ordering Veeam](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_ordering)
* [Managing Veeam](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managingveeam)
* [Ordering Veeam stand-alone licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_ordering_licenses)
* [Managing Veeam licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_managing_licenses)
* [Ordering and configuring IBM Cloud Object Storage with Veeam](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-icos_ordering)
"{"statusCode":0,"success":true,"activationId":"1a80c8449e7d49fb80c8449e7d99fb2a","rule":"e8b676ee-1726-4541-8f16-f87902bb3ab31/cosRule","action":"e8b676ee-1726-4541-8f16-f87902bb3ab31/cosChange"}"
],
"annotations": [],
"publish": false
}
Show more





 Details and limits for Object Storage triggers 

Triggers created with /whisk.system/cos package have the following limitations.



* Trigger ordering is not guaranteed. Trigger firing sequence may not match bucket update sequence.
* The trigger only fires on successful bucket events.
* Automatic trigger disablement - permissions change, COS bucket authentication changes, namespace authentication.
* Namespaces that contain the /whisk.system/cos package cannot be deleted until the package is deleted.
* After the trigger is created, the Notifications Manager role cannot be removed from your Cloud Functions namespace. Removing the role disables the trigger.
* For batch requests, each object change is handled individually and the trigger is fired for each successful change event.
* All characters are permitted in an object key except for ASCII control character NUL.
* Naming limitations for Cloud Functions triggers can be found on the [System details and limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_fullnames) page.











 Configuring the IBM Cloud Object Storage package