vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can either add more hosts or free up RAM, CPU, or disk space, and then add the service again in the console. After that, delete the existing service in the Capacity Validation Failed state by clicking the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg) next to it.









 Managing FortiGate Security Appliance 

After the FortiGate Security Appliance service is installed successfully, you can manage and configure firewall rules for the FSA from the FortiGate console.

Ensure the FSA firewall rules are defined to allow outbound HTTPS (TCP port 443) communications that are initiated by management components such as the Zerto Virtual Manager to communicate with the external management database on the IBM Cloud® infrastructure over the internet. The outbound HTTPS (TCP port 443) communications originate from the public IP address of the management services VMware NSX Edge Services Gateway (ESG) in your instance.



 Accessing the FortiGate 300 series console 

To manage the FortiGate Security Appliance service, you must access the FortiGate® 300 series console in one of the following ways:



* Log in to the FortiOS Web Client by using the credentials that you can find on the FortiGate Security Appliance service details page.
* Access the console through SSH connection by using the credentials that you can find on the FortiGate Security Appliance service details page.



For more information, see [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices).







 Considerations when you delete FortiGate Security Appliance 

Review the following considerations before you delete the FortiGate Security Appliance service:



* Deleting the FortiGate Security Appliance service deletes the public VLAN that was added.
* During the service deletion, your instance might not be able to access the internet temporarily.
For more information, see [Deleting enrichments](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-manage-enrichmentsenrichments-delete).
2. From the Improvement tools panel of the Improve and customize page, expand Teach domain concepts, and then click Extract entities.
3. Find the entity extractor that you want to delete, click the Actions icon, and then select Delete.







 Entity extractor limits 

The number of entity extractors that you can create per service instance depends on your Discovery plan type.



Entity extractor plan limits

 Plan Entity extractors per service instance<br><br>[1] Maximum entity types per extractor Maximum documents in training data 

 Cloud Pak for Data Unlimited 18 1,000 
 Premium 10 18 1,000 
 Enterprise 10 18 1,000 
 Plus (including Trial) 3 12 200
slcli file snapshot-delete --help
Usage: slcli file snapshot-delete [OPTIONS] SNAPSHOT_ID

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

Manual snapshots that aren't deleted in the portal manually, are automatically deleted when you reach space limitations. The oldest snapshot is deleted first.





 Restoring storage volume to a specific point in time by using a snapshot in the UI 

You might need to take your storage volume back to a specific point in time because of user-error or data corruption.



1. Unmount and detach your storage volume from the host.

For more information about mounting and unmounting storage, see [connecting your new storage](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingLinux).
2. Go to the [IBM Cloud® console](https://cloud.ibm.com/login). From the menu, select Classic Infrastructure![Classic icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/classic.svg).
3. Click Storage, File Storage for Classic.
4. Scroll on the list, and click your volume to be restored. The Snapshots page displays the list of all saved snapshots along with their size and creation date.
5. Click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/action-menu-icon.svg) next to the snapshot to be used and click Restore.

Completing the restore results in the loss of the data that was created or modified after the snapshot was taken. This data loss occurs because your storage volume returns to the same state that it was in of the time of the snapshot.
6. Click Yes to start the restore.
Deleting volume demovolume1 under account Test Account as user test.user@ibm.com...
OK
Volume demovolume1 is deleted.





 Deleting a Block Storage for VPC volume with the API 

Make a DELETE /volumes/{id} call.

curl -X DELETE "$vpc_api_endpoint/v1/volumes/$volume_id?version=2022-04-22&generation=2" -H "Authorization: $iam_token"

To verify that the volume is deleted, list the volumes by making a GET /volumes call.





 Sanitizing your data before you delete a volume 

When you delete a Block Storage for VPC volume, IBM guarantees that your data is inaccessible on the physical disk and is eventually [eradicated](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=cliblock-storage-data-eradication). If you have extra compliance requirements such as NIST 800-88 Guidelines for Media Sanitization, you must perform data sanitation procedures before you delete your volumes. For more information, see the [NIST 800-88 Guidelines for Media Sanitation](https://csrc.nist.gov/publications/detail/sp/800-88/rev-1/final).

Sanitizing and deleting the volume means your data can't be restored.







 Managing access to a Block Storage for VPC volume 

With Administrator privileges, you can assign volume-level user access to the Block Storage for VPC service. The following table shows the information that you must provide in the [Identity and Access Management (IAM) UI](https://cloud.ibm.com/docs/account?topic=account-account_setup).



Table 1. Information for IAM

 IAM field Action 

 Services Select Infrastructure Services. 
 Resource Type Select Block Storage for VPC. 
 Volume ID Enter the [volume ID](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storageview-vol-details) to assign access to a specific volume.
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=uidelete-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",
Deleting volume demovolume1 under account Test Account as user test.user@ibm.com...
OK
Volume demovolume1 is deleted.





 Deleting a Block Storage for VPC volume with the API 

Make a DELETE /volumes/{id} call.

curl -X DELETE "$vpc_api_endpoint/v1/volumes/$volume_id?version=2022-04-22&generation=2" -H "Authorization: $iam_token"

To verify that the volume is deleted, list the volumes by making a GET /volumes call.





 Sanitizing your data before you delete a volume 

When you delete a Block Storage for VPC volume, IBM guarantees that your data is inaccessible on the physical disk and is eventually [eradicated](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=uiblock-storage-data-eradication). If you have extra compliance requirements such as NIST 800-88 Guidelines for Media Sanitization, you must perform data sanitation procedures before you delete your volumes. For more information, see the [NIST 800-88 Guidelines for Media Sanitation](https://csrc.nist.gov/publications/detail/sp/800-88/rev-1/final).

Sanitizing and deleting the volume means your data can't be restored.







 Managing access to a Block Storage for VPC volume 

With Administrator privileges, you can assign volume-level user access to the Block Storage for VPC service. The following table shows the information that you must provide in the [Identity and Access Management (IAM) UI](https://cloud.ibm.com/docs/account?topic=account-account_setup).



Table 1. Information for IAM

 IAM field Action 

 Services Select Infrastructure Services. 
 Resource Type Select Block Storage for VPC. 
 Volume ID Enter the [volume ID](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storageview-vol-details) to assign access to a specific volume.
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-cli). 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 must 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 a mount target of a file share from the CLI 

Run the share-mount-target-delete command and specify the file share ID and mount target ID. To delete a mount target, the file share must be in a stable state.

ibmcloud is share-mount-target-delete <SHARE_ID> <MOUNT_TARGET_ID>





 Delete a file share from the CLI 

Run the share_delete command and specify the file share ID.

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-cli). The file share must be in a stable or failed state (that is, when provisioning fails).

Also, if the file share has a replica file share, you must first remove the replication relationship. For more information, see [Remove the replication relationship in the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=clifs-remove-replication-cli).

ibmcloud is share-delete <SHARE_ID>









 Manage file shares and mount points with the API 

By using the API, you can:
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=uidelete-mount-target-cli). 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 must 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 a mount target of a file share from the CLI 

Run the share-mount-target-delete command and specify the file share ID and mount target ID. To delete a mount target, the file share must be in a stable state.

ibmcloud is share-mount-target-delete <SHARE_ID> <MOUNT_TARGET_ID>





 Delete a file share from the CLI 

Run the share_delete command and specify the file share ID.

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=uidelete-mount-target-cli). The file share must be in a stable or failed state (that is, when provisioning fails).

Also, if the file share has a replica file share, you must first remove the replication relationship. For more information, see [Remove the replication relationship in the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=clifs-remove-replication-cli).

ibmcloud is share-delete <SHARE_ID>









 Manage file shares and mount points with the API 

By using the API, you can:
Deleting a Block Storage for VPC volume with the API 

Make a DELETE /volumes/{id} call.

curl -X DELETE "$vpc_api_endpoint/v1/volumes/$volume_id?version=2022-04-22&generation=2" -H "Authorization: $iam_token"

To verify that the volume is deleted, list the volumes by making a GET /volumes call.





 Sanitizing your data before you delete a volume 

When you delete a Block Storage for VPC volume, IBM guarantees that your data is inaccessible on the physical disk and is eventually [eradicated](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storageblock-storage-data-eradication). If you have extra compliance requirements such as NIST 800-88 Guidelines for Media Sanitization, you must perform data sanitation procedures before you delete your volumes. For more information, see the [NIST 800-88 Guidelines for Media Sanitation](https://csrc.nist.gov/publications/detail/sp/800-88/rev-1/final).

Sanitizing and deleting the volume means your data can't be restored.







 Managing access to a Block Storage for VPC volume 

With Administrator privileges, you can assign volume-level user access to the Block Storage for VPC service. The following table shows the information that you must provide in the [Identity and Access Management (IAM) UI](https://cloud.ibm.com/docs/account?topic=account-account_setup).



Table 1. Information for IAM

 IAM field Action 

 Services Select Infrastructure Services. 
 Resource Type Select Block Storage for VPC. 
 Volume ID Enter the [volume ID](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storageview-vol-details) to assign access to a specific volume. 
 Select Roles Assign platform access roles, typically, Operator.
For more information about the arguments and attributes, see [ibm_storage_block](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/storage_block).

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

To remove authorization from a host, remove its details from the ibm_storage_block resource and apply your changes.





 Viewing the list of hosts that are authorized to access a Block Storage for Classic LUN in the UI 



1. Click Storage > Block Storage for Classic, and click your Volume name.
2. Click Authorized Hosts to display the list of compute instances that have access to the volume.



There you can see the list of hosts, which are currently authorized to access the LUN. You can also see the authentication information that is needed to make a connection – username, password, and IQN Host. The Target address is listed on the Storage Detail page. For NFS, the Target address is described as a DNS name, and for iSCSI, it's the IP address of the Discover Target Portal.





 Viewing the list of hosts that are authorized to access a Block Storage for Classic LUN from the SLCLI 

To see the list of hosts, which are currently authorized to access the LUN, you can use the following command in SLCLI.

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

Options:
--sortby TEXT Column to sort by
--columns TEXT Columns to display. Options: id, name, type,
private_ip_address, source_subnet, host_iqn, username,
password, allowed_host_id
-h, --help Show this message and exit.
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. For more information, see [Remove the replication relationship with the API](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=apifs-remove-replication-api).

Make a DELETE /shares/$share_id call to delete a file share. The file share must be in a stable state or failed state (that is, when provisioning fails).

Example:

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

A successful response confirms acceptance for deletion and shows file share information. The status of file share is updated to pending_deletion.

Example:

{
"access_control_mode": "vpc",
"created_at": "2023-05-30T23:31:59Z",
"crn": "crn:[...]",
"encryption": "provider_managed",
"href": "$vpc_api_endpoint/v1/shares/0995b8c6-c323-4e59-9ea9-fa14dd66bba8",
"id": "0995b8c6-c323-4e59-9ea9-fa14dd66bba8",
"iops": 3000,
Default to current region if not specified.







 ibmcloud account org-user-remove 

Remove a user from org (org manager or user only):

ibmcloud account org-user-remove USER_NAME ORG [-f, --force]



 Command options 

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







 ibmcloud account org-roles 

Get all organization roles of the current user:

ibmcloud account org-roles [-r, --region REGION] [-u USER_ID]



 Command options 

-u
: User ID. If not specified, default to current user.

-r, --region REGION (optional)
: Region name. Default to current region if not specified.







 ibmcloud account org-role-set 

Assign an organization role to a user. This operation must be run by an organization manager.

ibmcloud account org-role-set USER_NAME ORG_NAME ORG_ROLE [-r, --region REGION]



 Command options 

USER_NAME (required)
: The name of the user to be assigned.

ORG_NAME (required)
: The name of the organization this user is assigned to.

ORG_ROLE (required)
: The name of the organization role this user is assigned to. For example:

OrgManager: This role can invite and manage users, select and change plans, and set spending limits.

BillingManager: This role can create and manage the billing account and payment information.

OrgAuditor: This role has read-only access to org information and reports.

-r, --region REGION (optional)
: Region name. Default to current region if not specified.





 Examples 

Assign user Mary to the organization IBM as OrgManager role:

ibmcloud account org-role-set Mary IBM OrgManager

You can set org and space roles by using the CLI, but if you want to set the other permissions, you must use the UI. For more information, see [Managing access to resources](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources).
* UI
* API







 Managing connections 

You can connect a service to an existing or new IBM Cloud® application from the Connections tab on your service dashboard. You can add more connections or delete connections from the Connections tab.

However, when you connect a service instance that is managed by IBM Cloud Identity and Access Management (IAM) to an application, an alias of the service that is managed by IAM is automatically created in the corresponding space with the connection information that you specified. This alias is represented as a service instance of your IAM-managed service.



 What is an alias? 

An alias is a connection between your IAM-managed service within a resource group and an application within an org or a space. In the IBM Cloud console, the connection (alias) is represented as a service instance. You can manage your alias by modifying the service instance that represents your connection.

Aliases are like symlinks that hold references to remote resources and enable interoperability and reuse of an instance across the platform. For example, you can create an instance of a service in a resource group and then reuse it from any available region by creating an alias in an org or space in those regions.

The following rules apply to aliases:



* There's no extra charge for an alias, but each alias counts against your quota in your organization.
* You can create only one alias per space in the IBM Cloud console. However, more than one alias per space can be created by using the IBM Cloud CLI. For more information, see [Working with resources and resource groups](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resource).
* You can create multiple connections between your IAM-managed service and any application in any space, organization, and region in the same account if you have permission.
* Multiple connections that are made in the same space to different apps from an IAM-managed service instance use the same alias.
* Unbinding an IAM-managed service instance doesn't delete the service instance that represents the alias.
* Deleting the application that your IAM-managed service instance is connected to doesn't delete the instance that represents the alias.
2. Under Attached Block Storage for VPC volumes, select a volume.
3. On the next page, click Auto Delete to enable.
4. Confirm your selection.



Alternatively, select a data volume from the list of Block Storage for VPC(Storage > Block storage volumes). On the volume details page, under Attached instances, click the Auto delete toggle to enable or disable automatic deletion.

You can also enable Auto Delete on a new data volume when you create an instance. For more information, see [Create and attach a Block Storage for VPC volume when you create a new instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-from-vsi).





 Deleting a Block Storage for VPC volume from the CLI 

Use the volume-delete command and specify the volume ID to delete a Block Storage for VPC volume.

You cannot delete an active Block Storage for VPC volume. You must first [detach it from the virtual server](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=clidetach-vol-attachment-cli).

ibmcloud is volume-delete (VOLUME_NAME | VOLUME_ID) [-f, --force]

See the following example.

$ ibmcloud is volume-delete demovolume1
This will delete volume demovolume1 and cannot be undone. Continue [y/N] ?> y
Deleting volume demovolume1 under account Test Account as user test.user@ibm.com...
OK
Volume demovolume1 is deleted.





 Deleting a Block Storage for VPC volume with the API 

Make a DELETE /volumes/{id} call.

curl -X DELETE "$vpc_api_endpoint/v1/volumes/$volume_id?version=2022-04-22&generation=2" -H "Authorization: $iam_token"