vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* UI
* CLI
* API







 Deleting a workspace 

After you destroy all associated VPC resources, if you don't need the workspace anymore, you can also delete the Schematics workspace.



 Deleting a workspace using the UI 



1. In the IBM Cloud console on the Schematics > Workspaces page, select Actions > Delete workspace to delete the Schematics workspace.
2. Confirm the action by entering the workspace name in the text box and click Delete workspace.







 Deleting a workspace using the CLI 

Run the following command to delete your workspace:

ibmcloud schematics workspace delete --id <WORKSPACE_ID>

You can monitor the log files to view the deletion progress of your workspace.





 Deleting a workspace using the API 



1. To delete a workspace by using the IBM Cloud Schematics Python APIs, create a Python file and provide a name of your choice, for example, schematics_delete_workspace.py.
2. Copy and paste the [Delete a workspace using Schematics Python API](https://cloud.ibm.com/docs/hpc-openshift?topic=hpc-openshift-deleting-workspace&interface=apiexample-request-delete-workspace) example request to your Python file.
3. Change the following parameters as part of the request:



* Replace your IBM Cloud key to the authenticator = IAMAuthenticator('<ibm-api-key>') variable.
* Change the API endpoint to the endpoint mentioned in [API endpoints](https://cloud.ibm.com/apidocs/schematics?code=pythonapi-endpoints) according to the location that you want your Schematics workspace to reside, for example, schematics_service.set_service_url('https://us.schematics.cloud.ibm.com').



4.
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-create-waf-override-options" "> --><-- <section "id="section-create-waf-override-examples" "> --> Examples Create a WAF overide rule under instance cis-demo. ibmcloud cis waf-override-create 31984fea73a15b45779fa0df4ef62f9b --json '{"description":"Enable IBM Magento ruleset for www.example.com","urls":"www.example.com/"] ! ! ! ,"priority":1,"groups":{"ea8687e59929c1fd05ba97574ad43f77":"default"},"rules":{"100015":"disable"},"rewrite_action":{"default":"block","challenge":"block","simulate":"disable"}}' -i "cis-demo"
<-- </section "id="section-create-waf-override-examples" "> --><-- </section "id="section-create-waf-override" "> --><-- <section "id="section-update-waf-override" "> --> ibmcloud cis cis waf-override-update Update a URL based Web Application Firewall (WAF) rules. ibmcloud cis waf-override-update DNS_DOMAIN_ID OVERRIDE_WAF_ID (--json @JSON_FILE | JSON_STRING) -i, --instance INSTANCE] --output FORMAT] ! !!!!!!
<-- <section "id="section-update-waf-override-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain.
* VMware NSX-T



As part of Entrust CloudControl service configuration, global PIP is enabled.

Sample users and groups are preconfigured in Active Directory (AD) and are displayed on the service details page. If you delete Entrust CloudControl, the sample users are deleted from AD too. A sample trust manifest is set up that gives single sign-on (SSO) permissions to the sample users that are created. You can change this setting or customize it for your own requirements.

The following components are ordered and included in the Entrust CloudControl service:



 Entrust CloudControl appliance 



* CPU - 4 CPUs
* RAM - 16 GB
* Disk - 186 GB VMDK
* Network - Placed on VLAN-backed private portable network specified for management







 High availability 

Two Entrust CloudControl appliances are deployed in an active-passive configuration.





 Licenses and fees 

Per host license - A Entrust CloudControl license is ordered for each host in the environment.







 Considerations when you delete Entrust CloudControl 

Review the following considerations before you delete the service:



* Before you delete Entrust CloudControl, ensure that you disable Root Password Vaulting, if configured, and that you delete all protected hosts from Entrust CloudControl.
* If you installed the Entrust CloudControl service before VMware Solutions v4.0, and you then delete that service, you must manually remove the DNS entries. For more information, see [Manually removing the DNS entries](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingservicesvc_deletingservices-DNS-entries).







 Related links 



* [Ordering Entrust CloudControl](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-entrust-cc_ordering)
[Contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support) if you are unable to delete a resource in failed status.





 Follow this order when you delete a VPC 

A VPC contains subnets and public gateways. A public gateway can be attached to one or more subnets in the VPC. A subnet also can contain virtual server instances, and one virtual server instance can have multiple network interfaces in different subnets within the VPC. Before a subnet can be deleted, any network interfaces in the subnet must first be deleted. A VPC contains security groups as well, but they are deleted automatically when the VPC is deleted. Address prefixes are attributes of a VPC, and they are deleted automatically, when the VPC is deleted.

Follow this order when you delete a VPC:



1. Delete all VPN gateways that are provisioned in any subnet of the VPC.
2. Detach all load balancers that are provisioned in any subnet of the VPC.
3. Delete all instances that have network interfaces in any subnet of the VPC. Any Floating IP associated with a network interface is automatically detached from the network interface when the instance is deleted.
4. Delete all subnets in the VPC. Any public gateway attached to a subnet is automatically detached from the subnet when the subnet is deleted.
5. Delete all public gateways in the VPC.
6. When the VPC has no subnets and no public gateways, you can delete the VPC. All Address Prefixes in the VPC are automatically deleted when the VPC is deleted.







 VPC resource relationships 

Some VPC resources are contained within other VPC resources (as "children"), but other VPC resources are contained at the account level, outside of any specific VPC. All child VPC resources must be deleted before the parent resource can be deleted. For account-level VPC resources, all links to existing resources must be deleted before the account resource can be deleted.
A non-CIS domain cannot CNAME to a CIS domain unless the non-CIS domain is added to a CIS account.

Attempting to directly access DNS records used for CIS CNAME setups also causes error 1001.

Disable Always Online if using Custom Hostnames (SSL for SaaS).







 Error 1002: DNS points to Prohibited IP 

Common causes for 1002 errors when a DNS points to a prohibited IP address are:



* A DNS record in your CIS DNS points to one of CIS's IP addresses.
* An incorrect target is specified for a CNAME record in your CIS DNS.
* Your domain is not on CIS but has a CNAME that refers to a CIS domain.





 Resolution 

Update your CIS A or CNAME record to point to your origin IP address instead of a CIS IP address:



1. Contact your hosting provider to confirm your origin IP address or CNAME record target.
2. Log in to your CIS account.
3. Select the domain that generates error 1002.
4. Select the DNS app.
5. Click Value for the A record to update.
6. Update the A record.



To ensure your origin web server doesn’t proxy its own requests through CIS, configure your origin webserver to resolve your CIS domain to:



* The internal NAT-ed IP address, or
* The public IP address of the origin web server.









 Error 1002: Restricted 

The most common cause of 1002: Restricted errors is when the CIS domain resolves to a local or disallowed IP address or an IP address not associated with the domain.



 Resolution 

If you own the website:



1. Confirm your origin web server IP addresses with your hosting provider
2. Log in to your CIS account
3. Update the A records in the CIS DNS to the IP address confirmed by your hosting provider









 Error 1003 Access Denied: Direct IP Access Not Allowed 

The most common cause of 1003 errors is when a client or browser directly accesses a CIS IP address.



 Resolution 

Browse to the website domain name in your URL instead of the CIS IP address.
Removing NFS storage from Cyber Recovery instances 

You can contract the capacity of your Cyber Recovery instance according to your business needs by removing Network File System (NFS) storage.



 Before you remove NFS storage from Cyber Recovery instances 



* Do not remove NFS storage from the VMware vSphere® Web Client. The changes that you make on the vSphere Web Client are not synchronized with the IBM Cloud® for VMware Solutions console.
* Before you remove the NFS storage, ensure that you removed all the VMs from the storage.
* Ensure that the shares that you plan to remove are associated with the correct Cyber Recovery instance.
* The cluster status must be Available.
* You can remove NFS storage shares from an existing NFS or vSAN cluster.







 Procedure to remove NFS storage from Cyber Recovery instances 



1. From the IBM Cloud for VMware Solutions console, click Resources > Cyber Recovery from the left navigation pane.
2. In the Cyber Recovery table, click the instance for which you want to contract capacity.
3. Click the Infrastructure tab.
4. In the applicable cluster table, click the cluster from which you want to remove NFS storage.
5. In the Storage section, select the storage share that you want to remove and click Delete.
6. Click Remove in the Remove storage window.







 Results after you remove NFS storage from Cyber Recovery instances 



1. You might experience a slight delay on the console, while the instance status changes from Available to Modifying. Allow the operation to complete before you make more changes to the instance.
2. You are notified by email that your request to remove NFS storage is being processed. On the console, the status of the cluster that is associated with the NFS storage is changed to Modifying.
3. The NFS storage is fully reclaimed by IBM Cloud infrastructure at the end of the IBM Cloud infrastructure billing cycle, which is typically 30 days.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the removed NFS storage.







 Related links
Removing the VMWare storage configuration using the console 



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 VMWare storage configuration using the command line 



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 vsphere



4. Optional: Remove the storage configuration.



1. List the storage configurations.

ibmcloud sat storage config ls
2. Remove the storage configuration.

ibmcloud sat storage config rm --config <config_name>











 Parameter reference 



 2.5.1 parameter reference 



Table 1. 2.5.1 parameter reference

 Display name CLI option Type Description Required? Default value 

 vCenter username vcenter-username Secret The vCenter username. You must specify the username along with the domain name. For example: Administrator@vsphere.local. true N/A 
 vCenter password vcenter-password Secret The vCenter server user password. true N/A 
 Insecure connection insecure-flag Config Include the insecure-flag.
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 AWS EFS storage configuration from the console 

Use the console to remove a storage configuration.

Note that you must delete your storage assignments before you can successfully delete your 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 AWS EFS storage configuration from the CLI 

Use the CLI to remove a storage configuration.

Note that you must delete your storage assignments before you can successfully delete your storage configuration.



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 AWS EFS driver pods and storage class are removed from all clusters that were part of the storage assignment.

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



1. List the storage classes in your cluster and verify that the AWS EFS storage class is removed.

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

oc get pods -n kube-system



4. Optional: Remove the storage configuration.



1. List the storage configurations.

ibmcloud sat storage config ls
2. Remove the storage configuration.

ibmcloud sat storage config rm --config <config_name>











 Parameter reference 



 1.3.1 parameter reference 



Table 1. 1.3.1 parameter reference

 Display name CLI option Type Description Required?
curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignments" -H "accept: application/json" -H "Authorization: Bearer TOKEN"





 Removing the NetApp Trident storage assignment and configuration from the console 

Use the console to remove a storage assignment and 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 NetApp Trident storage assignment and configuration from the CLI 

Use the CLI to remove a storage assignment and storage configuration.



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 NetApp Trident driver pods and storage class are removed from all clusters that were part of the storage assignment.

ibmcloud sat storage assignment rm --assignment <assignment_ID>
3. List the pods in the trident namespace and verify that the NetApp Trident storage driver pods are removed.

oc get pods -n trident
4. Verify that the trident namespace is removed.

oc get ns

If the trident namespace is stuck in Terminating status, follow the steps to [remove the namespace](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-namespace-terminating). Alternatively, you can follow the NetApp documentation for [uninstalling the Trident operator](https://netapp-trident.readthedocs.io/en/stable-v20.07/kubernetes/operations/tasks/managing.htmluninstalling-with-the-trident-operator)
5. Optional: List your storage configurations and remove your Trident configuration.

ibmcloud sat storage config ls
For more information about deleting a virtual private cloud instance and its associated resources, see [Deleting a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting).

To delete placement group by using the CLI, use the ibmcloud is placement-group-delete command. Specify the placement group ID.

The following example deletes a placement group named PLACEMENT_GROUP.

ibmcloud is placement-group-delete PLACEMENT_GROUP --output JSON





 Deleting a placement group with the API 

A placement group can't be deleted if instances are attached to it. All instances must be removed first. For more information about deleting a virtual private cloud instance and its associated resources, see [Deleting a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting).

The following example deletes the placement group.

curl -X DELETE "$vpc_api_endpoint/v1/placement_groups/$id?version=2021-04-20&generation=2" -H "Authorization: $iam_token"





 Deleting a placement group with Terraform 

You can delete a placement group in your IBM Cloud VPC by using Terraform. A placement group can't be deleted if instances are attached to it. All instances must be removed first. For more information about deleting a virtual private cloud instance and its associated resources, see [Deleting a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting).

The following example deletes a placement group named PLACEMENT_GROUP.

terraform destroy -target=ibm_is_placement_group.is_placement_group





 Listing all placement groups with the UI 

You can generate a list of placement groups for a region.

To display a list of all existing placement groups:



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon !
Remove the examplechallenge-fileobject file. (optional)
2. Optionally, remove the added ServerAlias (Apache2) or the server_name (Nginx) from your server configuration.
3. Remove the A record between the CDN domain and the origin server IP.



--------------------







 Redirect 

Clicking the Redirect tab displays all the information that is needed to address the Domain Validation through redirect. This information allows the CA to retrieve a copy of the Challenge response from Akamai through your origin server. After your server is configured correctly, Domain Validation can take 2 - 4 hours.

To successfully complete the Domain Validation through the Redirect method, you might need to configure your web server in a particular way. The example procedures for Apache and Nginx servers are outlined in the sections that follow.

Example situation:



* Origin server: origin.example.com
* CDN domain: cdn.example.com
* Challenge URL: http://cdn.example.com/.well-known/acme-challenge/examplechallenge-fileobject
* URL Redirect: http://dcv.akamai.com/.well-known/acme-challenge/examplechallenge-fileobject





 Apache redirect configuration 

To configure an Apache redirect, follow these steps:



1. Log in to the machine running the Apache2 server.
2. Open your Apache2 server configuration file. /etc/apache2/apache2.conf and /etc/apache2/sites-enabled/ are the default locations for the configuration file.
3. Add a redirect statement in the appropriate location within the configuration file. If needed, add your CDN domain as an additional ServerAlias to the virtual host for your origin.

Redirect /.well-known/acme-challenge/examplechallenge-fileobject http://dcv.akamai.com/.well-known/acme-challenge/examplechallenge-fileobject
FAQ about VMware NSX-V to NSX-T migration 



 What happens to the networking or storage assets when I delete a vCenter Server instance? 

When you delete a VMware vCenter Server® instance, the networking (VLANs with private and public subnets) and storage (IBM Cloud® File Storage) assets are cancelled together with the IBM Cloud bare metal Servers. If you have networking or storage assets in your migration, open a support ticket to ensure that IBM Cloud decouples the VLANs and related subnets and NFS storage from the original instance. Then, these assets are not cancelled when the vCenter Server instance is deleted.

The following recommendations apply:



* Design your migration so that you avoid the use of assets from the existing vCenter Server instance, which is to be deleted.
* If you need any existing assets, note and list all assets carefully.
* Open the support ticket before you delete the instance. List all assets that you want to maintain to ensure that these assets are decoupled from the original instance. If this process is not followed, the assets cannot be recovered after deletion.







 Can I attach my existing IBM Cloud File Storage to the new vCenter Server instance? 

If you are using NFS storage, you can manually attach the NFS storage to the new instance and perform a cross–vCenter vMotion without requiring a storage vMotion. You must authorize the NFS subnet from their new instance to the NFS storage.

The following recommendations apply:



* Configure static /etc/hosts entries on the new hosts for the storage hostnames for bootstrap purposes.
* Configure static routes on the new hosts to ensure that traffic to the NFS is driven over the NFS subnet and storage VLAN.
* After migration, open a support ticket to ensure that IBM Cloud decouples the NFS storage from the original instance. Then, the storage is not cancelled when the original instance is deleted.







 Can I reuse my existing Active Directory in the new vCenter Server instance? 

Most customers do not use the AD/DNS servers that are deployed with vCenter Server, but instead added their own domain controllers as an extra identity source to vCenter Server and NSX® Manager.
* UI
* CLI
* API







 Removing trusted profiles 

When you remove trusted profiles, compute resources and federated users are unlinked from the profile and can no longer apply the trusted profile identity.

To remove trusted profiles, you must be assigned the administrator or operator role within the account, or on the IAM Identity Service.

When you remove trusted profiles, you revoke all active sessions. Users are immediately logged out and the removed profiles are no longer available to connect to the target account. API calls that use access tokens might be successful until the access token expires.



 Removing trusted profiles in the console 



1. To see the full list of trusted profiles in your account, go to Manage > Access (IAM) in the IBM Cloud console, and select Trusted profiles.
2. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) next to the trusted profile you want to remove, and select Remove.







 Removing trusted profiles by using the CLI 

You can remove a trusted profile from your account by using the CLI. For more information, see the [IBM Cloud CLI](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases).



1. Log in, and select the account.

ibmcloud login
2. Check the list of trusted profiles for the current account and select the one that you want to remove. The following command shows the list of trusted profiles for your IBM Cloud account:

ibmcloud iam trusted-profiles
3. Remove the trusted profile from your account by running the following command. Specify the ID or the name of the trusted profile that you would like to remove.

ibmcloud iam trusted-profile-delete <IDorName>



For example, the following command removes a trusted profile that is named Test trusted profile.

ibmcloud iam trusted-profile-delete <Test trusted profile>