vania-janet/multiturn-rag-retrieval-data huggingface dataset:
VSI_ID=$(ibmcloud is instances --json | jq -r '.[] | select(.name == "vsi-lamp-1") | .id')
2. Stop the instance.

ibmcloud is instance-stop $VSI_ID
3. Resize the instance.

ibmcloud is instance-update $VSI_ID --profile cx2-4x8

You can get a list of alternative profiles by issuing the following command ibmcloud is instance-profiles, note however the restrictions on resizing based on current/target profiles in the [Resizing a virtual server instance](https://cloud.ibm.com/docs/vpc?topic=vpc-resizing-an-instance) topic.
4. Start the instance.

ibmcloud is instance-start $VSI_ID
5. You may need to wait a couple of minutes as the VSI is placed on an appropriate host and started. Open a browser and go to http://{FloatingIPAddress}/wordpress. Substitute the floating IP address of your instance. You should be able to access your WordPress page just as you had it before the resizing.







 Step 9: Remove resources 



1. In the VPC [console](https://cloud.ibm.com/vpc-ext), click on Floating IPs, then on the IP address for your VSIs, then in the action menu select Release. Confirm that you want to release the IP address.
2. Next, switch to Virtual server instances, Delete your instance.
3. Once the VSIs are gone, switch to Subnets. Delete your subnet.
4. After the subnets have been deleted, switch to VPC tab and delete your VPC.
5. If you created the optional Data Volume and no longer need it, switch to Block storage volumes tab and delete the volume.



When using the console, you may need to refresh your browser to see updated status information after deleting a resource.
VMware Aria Operations and VMware Aria Operations for Logs orders only personal VMs if it’s not vSAN.
* The VXLAN, DLR, and the Edge Gateway that were created during the initial deployment of VMware Aria Operations and VMware Aria Operations for Logs is deleted. The VMs that you deployed on VXLAN lose connectivity after the deletion of VMware Aria Operations and VMware Aria Operations for Logs begins.
* If you delete VMware Aria Operations and VMware Aria Operations for Logs, you need to remove the Syslog Server from the NSX Manager and the NSX Controller manually.
* If you installed the VMware Aria Operations and VMware Aria Operations for Logs 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).





 Removing the Syslog Server from the NSX Manager 



1. Log in to the console of the NSX Manager Appliance.
2. Select Manage Appliance Settings.
3. Under the General tab, remove the Syslog Server configuration.







 Removing the Syslog Server from the NSX Controller nodes (NSX-T only) 



1. Gather the NSX Manager's IP address, username, and password to use in the following commands.
2. View the NSX-T Manager's current Syslog configuration by running the following command:

curl -k -u '<USERNAME>:<PASSWORD>' -XGET https://<IPADDRESS>/api/v1/node/services/syslog/exporters
{
"_schema": "NodeSyslogExporterPropertiesListResult",
"_self": {
"href": "/node/services/syslog/exporters",
"rel": "self"
* UI
* CLI







 Deleting your Deployment and Removing your Data 

IBM Cloud® Databases instances are softly deleted in production when you delete or deprovision the instance in IBM Cloud.

IBM Cloud keeps the deployment in the soft delete state for three days before it issues a delete. The soft delete state addresses use cases when you accidentally delete an instance. You can re-enable an existing soft-deleted instance on your own.

Because a soft delete is essentially a disablement, no IBM Cloud® Databases for DataStax deployment can recover from a soft delete. Once an IBM Cloud® Databases for DataStax deployment is deleted, that deployment must be restored from a backup.



 Deleting your Deployment in the User Interface 

To delete your deployment instance from the Resource list section dashboard of the IBM Cloud dashboard, select your deployment. Next, by using the stacked three-dot menu icon ( ![Stacked three dots icon](https://cloud.ibm.com/docs-content/v1/content/ec83e0c9f915f4acf715222aaa5b8387c028200c/databases-for-mongodb/includes/cloud-databases/includes/cloud-databases/images/stacked-three-dots.png) ), choose Delete from the drop list.

Zoom

![List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/ec83e0c9f915f4acf715222aaa5b8387c028200c/databases-for-mongodb/includes/cloud-databases/includes/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI
* UI
* CLI







 Deleting your Deployment and Removing your Data 

IBM Cloud® Databases instances are softly deleted in production when you delete or deprovision the instance in IBM Cloud.

IBM Cloud keeps the deployment in the soft delete state for three days before it issues a delete. The soft delete state addresses use cases when you accidentally delete an instance. You can re-enable an existing soft-deleted instance on your own.

Because a soft delete is essentially a disablement, no IBM Cloud® Databases for DataStax deployment can recover from a soft delete. Once an IBM Cloud® Databases for DataStax deployment is deleted, that deployment must be restored from a backup.



 Deleting your Deployment in the User Interface 

To delete your deployment instance from the Resource list section dashboard of the IBM Cloud dashboard, select your deployment. Next, by using the stacked three-dot menu icon ( ![Stacked three dots icon](https://cloud.ibm.com/docs-content/v1/content/4dfeb7bbbdd817dfbdb17402735fb55d9cfbc7fb/messages-for-rabbitmq/includes/cloud-databases/includes/cloud-databases/images/stacked-three-dots.png) ), choose Delete from the drop list.

Zoom

![List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/4dfeb7bbbdd817dfbdb17402735fb55d9cfbc7fb/messages-for-rabbitmq/includes/cloud-databases/includes/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI 

By using the CLI, you can delete your existing IBM Cloud® Databases instance with the [ibmcloud resource service-instance-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_delete) command:
* UI
* CLI







 Deleting your Deployment and Removing your Data 

IBM Cloud® Databases instances are softly deleted in production when you delete or deprovision the instance in IBM Cloud.

IBM Cloud keeps the deployment in the soft delete state for three days before it issues a delete. The soft delete state addresses use cases when you accidentally delete an instance. You can re-enable an existing soft-deleted instance on your own.

Because a soft delete is essentially a disablement, no IBM Cloud® Databases for DataStax deployment can recover from a soft delete. Once an IBM Cloud® Databases for DataStax deployment is deleted, that deployment must be restored from a backup.



 Deleting your Deployment in the User Interface 

To delete your deployment instance from the Resource list section dashboard of the IBM Cloud dashboard, select your deployment. Next, by using the stacked three-dot menu icon ( ![Stacked three dots icon](https://cloud.ibm.com/docs-content/v1/content/99dae60bd0de1987ffcce4822e29b2bcdefe3a43/databases-for-mysql/includes/cloud-databases/includes/cloud-databases/images/stacked-three-dots.png) ), choose Delete from the drop list.

Zoom

![List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/99dae60bd0de1987ffcce4822e29b2bcdefe3a43/databases-for-mysql/includes/cloud-databases/includes/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI 

By using the CLI, you can delete your existing IBM Cloud® Databases instance with the [ibmcloud resource service-instance-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_delete) command:
* UI
* CLI







 Deleting your Deployment and Removing your Data 

IBM Cloud® Databases instances are softly deleted in production when you delete or deprovision the instance in IBM Cloud.

IBM Cloud keeps the deployment in the soft delete state for three days before it issues a delete. The soft delete state addresses use cases when you accidentally delete an instance. You can re-enable an existing soft-deleted instance on your own.

Because a soft delete is essentially a disablement, no IBM Cloud® Databases for DataStax deployment can recover from a soft delete. Once an IBM Cloud® Databases for DataStax deployment is deleted, that deployment must be restored from a backup.



 Deleting your Deployment in the User Interface 

To delete your deployment instance from the Resource list section dashboard of the IBM Cloud dashboard, select your deployment. Next, by using the stacked three-dot menu icon ( ![Stacked three dots icon](https://cloud.ibm.com/docs-content/v1/content/5561b38c6df9e8168523d143eaf64ab6acd7b600/cloud-databases/images/stacked-three-dots.png) ), choose Delete from the drop list.

Zoom

![List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/5561b38c6df9e8168523d143eaf64ab6acd7b600/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI 

By using the CLI, you can delete your existing IBM Cloud® Databases instance with the [ibmcloud resource service-instance-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_delete) command:

ibmcloud resource service-instance-delete my-service-instance
roles: policyRoles,
resources: policyResources,
};

iamPolicyManagementService.createPolicy(params)
.then(res => {
examplePolicyId = res.result.id;
console.log(JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});

Not all services support policies at the resourceType and individual resource level. Examples of services that do support these attributes are IBM Cloud Object Storage and IBM Key Protect, where buckets and keys are the resource type and the ID is listed to specify the specific resource.





 Removing an authorization in the console 

You can remove any authorization between services in the account if you are assigned the Administrator role on the target service. If you remove any access policies created by the source service for its dependent services, the source service is unable to complete the workflow or access the target service.



1. In the IBM Cloud console, click Manage > Access (IAM), and select Authorizations.
2. Identify the row for the authorization that you want to remove from the account.
3. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/icons/action-menu-icon.svg) > Remove.
4. Select Remove.



If the source service is removed from the account, any policies that are created by that service for its dependent services are deleted automatically. Similarly, if the dependent service is removed from the account, any access policies that are delegated to that service are also deleted.





 Removing an authorization by using the CLI 

You can remove any authorization between services in the account if you are assigned the Administrator role on the target service.
* ibmcloud is instance-network-interface-create my-vnic my-instance my-subnet --sg my-sg-1 --sg my-sg-2 Create a network interface for a virtual server instance with security group by using resource name.







 Command options 



* NIC_NAME: Name of the network interface.
* INSTANCE: ID or name of the instance.
* SUBNET: ID or name of the subnet.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --rip: ID or name of the existing reserved IP.
* --address: The IP address to reserve, which must not already be reserved on the subnet.
* --auto-delete: If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false. (default: true).
* --ip-name: The user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --sg: ID or name of the security group.
* --allow-ip-spoofing: Disables the source and destination checks on this interface. If false, source IP spoofing is not allowed on this interface. One of: false, true.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-network-interface-delete 

Remove one or more network interfaces from a virtual server instance.

ibmcloud is instance-network-interface-delete INSTANCE (NIC1 NIC2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* NIC1: ID or name of the network interface.
* UI
* CLI







 Deleting your Deployment and Removing your Data 

IBM Cloud® Databases instances are softly deleted in production when you delete or deprovision the instance in IBM Cloud.

IBM Cloud keeps the deployment in the soft delete state for three days before it issues a delete. The soft delete state addresses use cases when you accidentally delete an instance. You can re-enable an existing soft-deleted instance on your own.

Because a soft delete is essentially a disablement, no IBM Cloud® Databases for DataStax deployment can recover from a soft delete. Once an IBM Cloud® Databases for DataStax deployment is deleted, that deployment must be restored from a backup.



 Deleting your Deployment in the User Interface 

To delete your deployment instance from the Resource list section dashboard of the IBM Cloud dashboard, select your deployment. Next, by using the stacked three-dot menu icon ( ![Stacked three dots icon](https://cloud.ibm.com/docs-content/v1/content/3505da55c475bf1edbe3eb3496324ba13941b783/databases-for-postgresql/includes/cloud-databases/includes/cloud-databases/images/stacked-three-dots.png) ), choose Delete from the drop list.

Zoom

![List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/3505da55c475bf1edbe3eb3496324ba13941b783/databases-for-postgresql/includes/cloud-databases/includes/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI
Check your app code, your [Ingress resource configuration files](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-setup), or any other configurations you have applied to only this ALB.



7. After you finish debugging, restore the health check on the ALB pods. Repeat these steps for each ALB pod.



1. Log in to the ALB pod and remove the from the server_name.

kubectl exec -ti <pod_name> -n kube-system -c nginx-ingress -- sed -i -e 'sserver_nameserver_nameg' /etc/nginx/conf.d/kube-system-alb-health.conf
2. Reload the NGINX configuration so that the health check restoration is applied.

kubectl exec -ti <pod_name> -n kube-system -c nginx-ingress -- nginx -s reload



8. Now, when you cURL the albhealth host to health check the ALB IP, the check returns healthy.

curl -X GET http://169.62.196.238/ -H "Host: albhealth.mycluster-<hash>-0000.us-south.containers.appdomain.cloud"
9. Verify that the ALB IP address has been restored in the DNS registration for your domain by checking the Akamai server. Note that the DNS registration might take a few minutes to update.

host mycluster-<hash>-0000.us-south.containers.appdomain.cloud ada.ns.Akamai.com

Example output

mycluster-<hash>-0000.us-south.containers.appdomain.cloud has address 169.46.52.222
mycluster-<hash>-0000.us-south.containers.appdomain.cloud has address 169.62.196.238
Complete the following steps to remove the ODF resources from your cluster.

The following steps result in data loss. Back up the data on your local volumes before you remove your ODF deployment.

When you delete the OcsCluster custom resource from your cluster, the following resources are deleted. Additionally, any apps that require access to the data on your local volumes might experience downtime. - ODF driver pods. - The MON and OSD PVCs. - All data from your volumes. However, if you created PVCs by using the NooBaa storage class, and your apps wrote data to your backing store, the data in your backing store is not deleted.



1. Get the name of your OcsCluster custom resource.

oc get ocscluster

Example output for a custom resource called ocscluster-vpc.

NAME AGE
ocscluster-vpc 4s
2. Delete your OcsCluster custom resource. Replace <ocscluster_name> with the name of your custom resource.

oc delete ocscluster <ocscluster_name>

Example command for an OcsCluster custom resource called ocscluster-vpc.

oc delete ocscluster ocscluster-vpc
3. Delete any PVCs that you created.

oc get pvc
4. Optional If you don't want to reinstall ODF, you can [Remove the ODF add-on from your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-ocs-manage-deploymentocs-rm-cleanup-resources).







 Cleaning up your ODF deployment 

After you remove ODF from your apps, and remove your ODF storage cluster, you can clean up the remaining Kubernetes resources that were deployed with ODF.



 Cleaning up ODF 



1. Copy one of the following clean up scripts based on your ODF deployment.



* VPC or Satellite with dynamically provisioned disks Clean up the remaining Kubernetes resources from your cluster.
The resources can be viewed on the Resources tab of the blueprint in the [Blueprints dashboard](https://cloud.ibm.com/schematics/blueprints), or using the [Resource list](https://cloud.ibm.com/resources).

The blueprint configuration and outputs can be reviewed by using the blueprint get command. See section [displaying blueprints](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-reference&interface=clischematics-blueprint-get).

To destroy cloud resources and remove the blueprint environment, refer to, [destroy a blueprint environment](https://cloud.ibm.com/docs/schematics?topic=schematics-destroy-blueprint&interface=cli), and [delete a blueprint config](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-blueprint&interface=clidelete-blueprint-cli).
* CLI
* API







 Using resource reclamations 

You can use the IBM Cloud® CLI or the [IBM Cloud® Resource Controller API](https://cloud.ibm.com/apidocs/resource-controller/resource-controller?code=gorun-reclamation-action) to manage the reclamation process of specific resources. For more information, see [FAQs about resources](https://cloud.ibm.com/docs/account?topic=account-resources-faq&interface=cli)



 Listing reclaimed resources by using the CLI 

To list reclaimed resources that can be restored or deleted by using the CLI, run the following command:

ibmcloud resource reclamations [--resource-instance-id INSTANCE_ID]

Enter the following command option:



* --resource-instance-id: The globally unique ID (GUID) of the resource instance.



The following example shows how to list the reclamations of a particular service instance:

ibmcloud resource reclamations --resource-instance-id abcd1234-ef56-486e-b293-22d6c7eb6699





 Listing reclaimed resources by using the API 

To list reclaimed resources that can be restored or deleted, call the [IBM Cloud® Resource Controller API](https://cloud.ibm.com/apidocs/resource-controller/resource-controllerlist-reclamations) as shown in the following example:

Use the ListReclamationsOptions.Builder to create a ListReclamationsOptions object that contains the parameter values for the listReclamations method.

Instantiate the ListReclamationsOptions struct and set the fields to provide parameter values for the ListReclamations method.



* Curl
* Java
* Python
* Go
* Node



curl -X GET https://resource-controller.cloud.ibm.com/v1/reclamations?account_id=b80a8b513ae24e178438b7a18bd8d609 -H 'Authorization: Bearer <IAM_TOKEN>'
curl -X GET <ENDPOINT>/api/v2/targets -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).



For example, you can run the following curl request to get information about the targets that are defined in Dallas:

curl -X GET https://private.us-south.atracker.cloud.ibm.com/api/v2/targets -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"

Results will show if the target is COS ("target_type": "cloud_object_storage") or AT ("target_type": "logdna") or Event Streams ("target_type": "event_streams") or an IBM Cloud Activity Tracker Event Routing hosted event search offering.





 HTTP response codes 

When you use the IBM Cloud Activity Tracker Event Routing REST API, you can get standard HTTP response codes to indicate whether a method completed successfully.



* A 200 response always indicates success.
* A 4xx response indicates a failure.
* A 5xx response usually indicates an internal system error.



See the following table for some HTTP response codes:



Table 3. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful. A resource is created. 
 400 Bad Request The request was unsuccessful. You might be missing a parameter that is required. 
 401 Unauthorized The IAM token that is used in the API request is invalid or expired. 
 403 Forbidden The operation is forbidden due to insufficient permissions. 
 404 Not Found The requested resource doesn't exist or is already deleted. 
 429 Too Many Requests Too many requests hit the API too quickly. 
 500 Internal Server Error Something went wrong in IBM Cloud Activity Tracker Event Routing processing.
res, err := client.GetObject(&input4)
if err != nil {
exitErrorf("Unable to download object %q from bucket %q, %v", objectKey, newBucket, err)
}

f, _ := os.Create(downloadObjectKey)
defer f.Close()
io.Copy(f, res.Body)

fmt.Println("Downloaded", f.Name())

// Delete object within the new bucket
_, err = client.DeleteObject(&s3.DeleteObjectInput{Bucket: aws.String(newBucket), Key: aws.String(objectKey)})
if err != nil {
exitErrorf("Unable to delete object %q from bucket %q, %v", objectKey, newBucket, err)
}

err = client.WaitUntilObjectNotExists(&s3.HeadObjectInput{
Bucket: aws.String(newBucket),
Key: aws.String(objectKey),
})
if err != nil {
exitErrorf("Error occurred while waiting for object %q to be deleted, %v", objectKey)
}

fmt.Printf("Object %q successfully deletedn", objectKey)

// Delete the new bucket
// It must be empty or else the call fails
_, err = client.DeleteBucket(&s3.DeleteBucketInput{
Bucket: aws.String(newBucket),
})
if err != nil {
exitErrorf("Unable to delete bucket %q, %v", newBucket, err)
}

// Wait until bucket is deleted before finishing
fmt.Printf("Waiting for bucket %q to be deleted...n", newBucket)

err = client.WaitUntilBucketNotExists(&s3.HeadBucketInput{