vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* --host-failure-policy: The action to perform if the compute host experiences a failure. One of: restart, stop.
* --resource-group-id: ID of the resource group. This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group. This name is mutually exclusive with --resource-group-id.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-delete 

Delete one or more virtual server instances.

ibmcloud is instance-delete (INSTANCE1 INSTANCE2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* INSTANCE1: ID or name of the instance.
* INSTANCE2: ID or name of the instance.
* --output: Specify output format, only JSON is supported. One of: JSON.
* --force, -f: Force the operation without confirmation.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-disk 

View details of a virtual server instance disk.

ibmcloud is instance-disk INSTANCE INSTANCE_DISK [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* INSTANCE_DISK: ID or name of the instance disk.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-disk-update 

Update a virtual server instance disk.
First display the bindings then delete them by Service Bindings Names (FIRST and SECOND below are from the get output)

ibmcloud ce application get --name ghstats-app

ibmcloud ce application unbind --name ghstats-app --binding ghstats-app-ce-service-binding-FIRST

ibmcloud ce application unbind --name ghstats-app --binding ghstats-app-ce-service-binding-SECOND
2. Delete the project and its components.

ibmcloud ce project delete --name ghstats --hard -f
3. Delete the services:

ibmcloud resource service-instance-delete -f ghstatsDB

ibmcloud resource service-instance-delete -f ghstatsAppID
4. Delete the Container Registry namespace

ibmcloud cr namespace-rm $NAMESPACE -f
5. Delete the [Github.com token](https://github.com/settings/tokens)



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).





 Expand the tutorial 

Want to add to or change this tutorial? Here are some ideas:



* Expand the app for multi-tenant support.
* Use social identity providers.
* Add a date picker to the statistics page to filter displayed data.
* Use a custom login page for App ID.







 Related Content 

Here are links to additional information on the topics covered in this tutorial. The app itself is available in this [GitHub repository](https://github.com/IBM-Cloud/github-traffic-stats).

Documentation:
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) 
 Delete a service instance ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) 
 Create a service ID ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) 
 View details of a service instance !
kubectl get all -A | grep portworx
8. Remove the Portworx service instance from your IBM Cloud account.



1. From the [IBM Cloud resource list](https://cloud.ibm.com/resources), find the Portworx service that you created.
2. From the actions menu, click Delete.
3. Confirm the deletion of the service instance by clicking Delete.





To stop billing for Portworx, you must remove the Portworx Helm installation from your cluster and remove the Portworx service instance from your IBM Cloud account.
* [Secure the application](https://cloud.ibm.com/docs/Registry?topic=Registry-multi-region-k8s-cismulti-region-k8s-cis-secure_via_CIS)



* [Turn the Web Application Firewall On](https://cloud.ibm.com/docs/Registry?topic=Registry-multi-region-k8s-cismulti-region-k8s-cis-20)
* [Increase performance and protect from Denial of Service attacks](https://cloud.ibm.com/docs/Registry?topic=Registry-multi-region-k8s-cismulti-region-k8s-cis-proxy_setting)



* [Remove resources](https://cloud.ibm.com/docs/Registry?topic=Registry-multi-region-k8s-cismulti-region-k8s-cis-6)



* [Remove Kubernetes Cluster resources](https://cloud.ibm.com/docs/Registry?topic=Registry-multi-region-k8s-cismulti-region-k8s-cis-23)
* [Remove CIS resources](https://cloud.ibm.com/docs/Registry?topic=Registry-multi-region-k8s-cismulti-region-k8s-cis-24)



* [Related content](https://cloud.ibm.com/docs/Registry?topic=Registry-multi-region-k8s-cismulti-region-k8s-cis-7)



[Continuous Deployment to Kubernetes](https://cloud.ibm.com/docs/Registry?topic=Registry-continuous-deployment-to-kubernetescontinuous-deployment-to-kubernetes)



* [Objectives](https://cloud.ibm.com/docs/Registry?topic=Registry-continuous-deployment-to-kubernetescontinuous-deployment-to-kubernetes-objectives)
[Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg).
4. In the Delete License window, click OK. The status of the license is changed to Removing. When the license deletion is completed, the license is no longer available in the Caveonix RiskForesight licenses table.







 Related links 



* [Caveonix RiskForesight overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix_considerations)
* [Ordering Caveonix RiskForesight licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix_license_ordering)
* --IBMiDBQ-license value: IBMi DBQ software license associated with the instance.
* --IBMiPHA-license value: IBMi PHA software license associated with the instance.
* --IBMiRDS-users value: Number of IBMi RDS users software license associated with the instance, default IBMiRDSUsers=0 (no license).
* --placement-group value: The placement group ID of the group that the server will be added to.
* --shared-processor-pool value: The shared processor pool ID of the pool that the server will be in.
* --deployment-type value: The custom deployment type ("EPIC").
* --json: Format output in JSON.



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







 ibmcloud pi instance-delete 



 Delete a server instance 

ibmcloud pi instance-delete INSTANCE_ID



* INSTANCE_ID: The unique identifier or name of the instance.



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







 ibmcloud pi instance-get-console 



 Get the console of an instance 

ibmcloud pi instance-get-console INSTANCE_ID [--json]



* INSTANCE_ID: The unique identifier or name of the instance.



Options



* --json: Format output in JSON.



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







 ibmcloud pi instance-hard-reboot 



 Hard restart the operating system of an instance 

ibmcloud pi instance-hard-reboot INSTANCE_ID



* INSTANCE_ID: The unique identifier or name of the instance.



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







 ibmcloud pi instance-list-volumes 



 Get a list of volumes attached to an instance 

ibmcloud pi volume INSTANCE [--long] [--json]

Options



* --long: Retrieve all volume details.
* --json: Format output in JSON.
MIIFazCCA10gAwIBAgIUVW/gPwBtOKHEwCL....
 ........................................
 ............................FkQF0tfc6cg=
 -----END CERTIFICATE----- 

+------------+----------------------------------------+

command completed successfully.







 hpcs-cert-mgr cert delete 

Use this command to delete client certificates for your instance certificate manager server.

ibmcloud hpcs-cert-mgr cert delete --crn HPCS_CRN --admin-priv-key ADMIN_PRIV_KEY --cert-id CERT_ID [--private]



* Command options

--crn HPCS_CRN
: Required. The crn of your Hyper Protect Crypto Services instance. You can use the ibmcloud resource service-instances --long command to retrieve the crn.

--admin-priv-key ADMIN_PRIV_KEY
: Required. The file path of your current private key that is stored on your local workstation. The private key is used to sign this command action toward your instance certificate manager server.

--cert-id CERT_ID
: Required. The string ID of the certificate that you want to delete.

--private
: Optional. If you use this option, the certificate manager server URL points to the private network. For example,: cert-mgr.private.<region>.hs-crypto.cloud.ibm.com:443. The region is the abbreviation of the geographic area where you log in to IBM Cloud.
Retrieving service instance INSTANCE_NAME in resource group default under account USER's Account as USER...
OK

Name: INSTANCE_NAME
ID: crn:v1:bluemix:public:databases-for-elasticsearch:us-east:a/40ddc34a953a8c02f109835656860e:dd13152c-fe15-4bb6-af94-fde0af5303f4::
GUID: dd13152c-fe15-4bb6-af94-fde5654765
Location: <LOCATION>
Service Name: databases-for-elasticsearch
Service Plan Name: standard
Resource Group Name: default
State: active
Type: service_instance
Sub Type: Public
Locked: false
Service Endpoints: public
Created at: 2023-06-26T19:42:07Z
Created by: USER
Updated at: 2023-06-26T19:53:25Z
Last Operation:
Status create succeeded
Message Provisioning elasticsearch with version 7.17 (100%)
4. (Optional) Deleting a service instance Delete an instance by running a command like this one:

ibmcloud resource service-instance-delete <INSTANCE_NAME>







 The --parameters parameter 

The service-instance-create command supports a -p flag, which allows JSON-formatted parameters to be passed to the provisioning process. Some parameter values are Cloud Resource Names (CRNs), which uniquely identify a resource in the cloud. All parameter names and values are passed as strings.

For example, if a database is being provisioned from a particular backup and the new database deployment needs a total of 9 GB of memory across three members, then the command to provision 3 GBs per member looks like:

ibmcloud resource service-instance-create databases-for-elasticsearch <SERVICE_NAME> standard us-south -p '{
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 Delete a service instance ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 Create a service ID ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 View details of a service instance ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) !
kubectl -n openshift-storage patch noobaa/noobaa -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n openshift-storage patch backingstores.noobaa.io/noobaa-default-backing-store -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n openshift-storage patch bucketclasses.noobaa.io/noobaa-default-bucket-class -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n openshift-storage patch storagecluster.ocs.openshift.io/ocs-storagecluster -p '{"metadata":{"finalizers":[]}}' --type=merge
sleep 20
oc delete pods -n openshift-storage --all --force --grace-period=0
sleep 20
Show more
* Classic clusters or Satellite clusters with local disks Clean up the remaining Kubernetes resources from your cluster. Save the following script in a file called cleanup.sh to your local machine.

!/bin/bash
ocscluster_name=oc get ocscluster | awk 'NR==2 {print $1}'
oc delete ocscluster --all --wait=false
kubectl patch ocscluster/$ocscluster_name -p '{"metadata":{"finalizers":[]}}' --type=merge
oc delete ns openshift-storage --wait=false
sleep 20
kubectl -n openshift-storage patch persistentvolumeclaim/db-noobaa-db-0 -p '{"metadata":{"finalizers":[]}}' --type=merge
2022-05-11 06:50:43,944 - INFO - Logging in to file: /var/adm/ras/ibm_cloud_workflow_logs/mm_cloud_workflow_teardown.log_2022-May-11_06-50-43

=======================================================================
 ! Danger Zone ! 
======================================================================
 This workflow, will result in teardown of IBM Spectrum Scale 
 cluster and resources. However, it will not destroy VPC, Bastion 
 Host resources and the s3 bucket. 

 Notes: 
 1. Ensure to STOP all your applications before proceeding further. 
 2. All IBM Spectrum Scale instances must be in either 'running', 
 'pending', 'stopping' or 'stopped' state. 
=======================================================================

Do you want to continue teardown [y/N]: y
2022-05-11 06:50:45,525 - INFO - Proceeding for tear down ..
2022-05-11 06:50:45,525 - INFO - Obtaining necessary permissions to destroy cluster resources
2022-05-11 06:50:46,162 - INFO - Proceeding to destroy the IBM Spectrum Scale cluster
2022-05-11 06:50:46,162 - INFO - This may take a few minutes to complete.
Get details about the volume. This command returns the worker node ID and attachment ID. Note the worker node ID. In the following command this ID is returned as "Instance name".

ibmcloud is volume <volume_ID>
3. Retrieve a list of your PVs. This command returns a list of your PVs that you can then you use to determine which PVC uses the volume that you want to remove.

oc get pv
4. Describe the PV that uses the volume. If you don't know which PV uses the volume that you want to remove, you can run the describe pv command on each PV in your cluster. Note the PVC that uses the PV.

oc describe pv <pv_name>
5. Check to see if your storage volume is in use by a pod. The following command shows the pods that mount the volume and the associated PVC. If no pod is returned, the storage is not in use.

oc get pods --all-namespaces -o=jsonpath='{range .items[]}{"n"}{.metadata.name}{":t"}{range .spec.volumes[]}{.persistentVolumeClaim.claimName}{" "}{end}{end}' | grep "<pvc_name>"
6. If the pod your volume is using is part of a deployment, delete the deployment. If your pod does not belong to a deployment, delete the pod.

oc delete deployment <deployment_name>

oc delete pod <pod_name>
7. Delete the PVC and PV.

oc delete pvc <pvc_name>

oc delete pv <pv_name>
8. Retrieve your IAM token.

ibmcloud iam oauth-tokens
9. Detach storage by using a POST request.

Example request
* [Returning to your console from IBM Cloud](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-iks-rtn-to-console)



* [Deleting a service instance](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-iks-delete-service-instance)



[Deploy from Red Hat Marketplace](https://cloud.ibm.com/docs/blockchain?topic=blockchain-deploy-ocp-rhmdeploy-ocp-rhm)



* [What is Red Hat Marketplace?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-deploy-ocp-rhmdeploy-ocp-rhm-whatis)
* [Limitations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-deploy-ocp-rhmdeploy-ocp-rhm-limitations)
* [Before you begin](https://cloud.ibm.com/docs/blockchain?topic=blockchain-deploy-ocp-rhmdeploy-ocp-rhm-prerequisites)
* [Step one: Apply the Security Context Constraint](https://cloud.ibm.com/docs/blockchain?topic=blockchain-deploy-ocp-rhmdeploy-ocp-rhm-scc)
* [Step two: Apply the image pull secrets](https://cloud.ibm.com/docs/blockchain?topic=blockchain-deploy-ocp-rhmdeploy-ocp-rhm-secrets)
Do not delete the LoadBalancers in the openshift-ingress namespace, as those are deleted later in these steps.



1. Find your LoadBalancer details and make a note of the IP addresses they use.

kubectl get svc -A -o wide | grep LoadBalancer
2. For each LoadBalancer not in the openshift-ingress namespace that uses a portable IP address, save the settings to a YAML file.



kubectl get svc -o yaml -n LB-NAMESPACE LB-NAME > LB-NAMESPACE.LB-NAME.yaml



1. Delete the LoadBalancer.

kubectl delete svc -n LB-NAMESPACE LB-NAME



6. Complete the following steps quickly, because the portable subnet must be detached before the openshift-ingress-operator pod restarts and re-creates the LoadBalancers.



1. Scale down the Ingress operator.

kubectl scale deploy -n openshift-ingress-operator ingress-operator --replicas 0
2. Delete the LoadBalancers in the openshift-ingress namespace.

kubectl delete svc -n openshift-ingress LB-NAME
3. Detach the portable subnets from your cluster.

ibmcloud oc cluster subnet detach -c CLUSTER-ID --subnet-id SUBNET-ID



7. Wait a few minutes for the detach command to finish, then check that they have been detached by reviewing the ibm-cloud-provider-vlan-ip-config ConfigMap that stores the subnets and IP addresses.

kubectl get cm -n kube-system ibm-cloud-provider-vlan-ip-config -o yaml

It might take 5-10 minutes for the detach to complete. While you wait, you can ensure that the new portable subnets you created for this cluster also appear in the ConfigMap.
8.
2022-05-11 06:50:45,525 - INFO - Proceeding for tear down ..
2022-05-11 06:50:45,525 - INFO - Obtaining necessary permissions to destroy cluster resources
2022-05-11 06:50:46,162 - INFO - Proceeding to destroy the IBM Spectrum Scale cluster
2022-05-11 06:50:46,162 - INFO - This may take a few minutes to complete.
[root@spectrum-scale-bootstrap vpcuser]



Destroying resources takes time based on the number of instance values that you provided for the deployment values.





 Step 2. Destroying resources using the UI 



1. In the IBM Cloud console on the Schematics > Workspaces page, select Actions > Destroy to delete all of the related VPC resources that were deployed as part of that workspace.
2. If you select the option to destroy resources, decide whether you want to destroy all of them. This action cannot be undone.
3. Confirm the action by entering the workspace name in the text box and click Destroy.







 Step 2. Destroying resources using the CLI 

Run the following command to remove your VPC resources from your workspace:

ibmcloud schematics destroy --id <WORKSPACE_ID>

You can monitor the log files to view the deletion progress of all IBM Cloud resources.





 Step 2. Destroying resources using Schematics Python API 



1. To destroy resources by using the IBM Cloud Schematics Python APIs, create a Python file and provide a name of your choice, for example, schematics_destroy_resources.py.
2. Copy and paste the [Destroy resources using Schematics Python API](https://cloud.ibm.com/docs/hpc-spectrum-scale?topic=hpc-spectrum-scale-deleting-resources&interface=apiexample-request-destroy) 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.
DCA also employs TCP-layer optimizations that accelerate connection set up and reduce round trips.





 Step 6: Remove resources 



* Delete the application from the [Kubernetes Service](https://cloud.ibm.com/kubernetes/catalog/cluster).
* Delete the image from the [Container Registry](https://cloud.ibm.com/kubernetes/catalog/registry).
* Delete the [IBM® Content Delivery Network service](https://cloud.ibm.com/classic/network/cdn).







 Related content 



* [Getting Started with CDN](https://cloud.ibm.com/docs/CDN?topic=CDN-getting-startedgetting-started)
* [IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers)
* [IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-startedgetting-started)
kubectl -n openshift-storage patch storagecluster.ocs.openshift.io/ocs-storagecluster -p '{"metadata":{"finalizers":[]}}' --type=merge
sleep 20
oc delete pods -n openshift-storage --all --force --grace-period=0
oc delete ns local-storage --wait=false
sleep 20
kubectl -n local-storage patch localvolume.local.storage.openshift.io/local-block -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n local-storage patch localvolume.local.storage.openshift.io/local-file -p '{"metadata":{"finalizers":[]}}' --type=merge
sleep 20
oc delete pods -n local-storage --all --force --grace-period=0
Show more



2. Run the cleanup.sh script.

sh ./cleanup.sh
3. **Classic clusters or Satellite clusters with local disks After you run the cleanup script, log in to each worker node and run the following commands.



1. Deploy a debug pod and run chroot /host.

oc debug node/<node_name> -- chroot /host
2. Run the following command to remove any files or directories on the specified paths. Repeat this step for each worker node that you used in your OCS configuration.

rm -rvf /var/lib/rook /mnt/local-storage

Example output:

removed '/var/lib/rook/openshift-storage/log/ocs-deviceset-0-data-0-6fgp6/ceph-volume.log'
removed directory: '/var/lib/rook/openshift-storage/log/ocs-deviceset-0-data-0-6fgp6'
This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group. This name is mutually exclusive with --resource-group-id.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-delete 

Delete one or more virtual server instances.

ibmcloud is instance-delete (INSTANCE1 INSTANCE2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* INSTANCE1: ID or name of the instance.
* INSTANCE2: ID or name of the instance.
* --output: Specify output format, only JSON is supported. One of: JSON.
* --force, -f: Force the operation without confirmation.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-disk 

View details of a virtual server instance disk.

ibmcloud is instance-disk INSTANCE INSTANCE_DISK [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* INSTANCE_DISK: ID or name of the instance disk.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-disk-update 

Update a virtual server instance disk.

ibmcloud is instance-disk-update INSTANCE INSTANCE_DISK --name NEW_NAME [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* INSTANCE_DISK: ID or name of the instance disk.