vania-janet/multiturn-rag-retrieval-data huggingface dataset:
A pool is a group of origin servers that traffic is intelligently routed to when attached to a GLB. With clusters in the United Kingdom and United States, you can define location-based pools and configure CIS to redirect users to the closest clusters based on the geographical location of the user requests.



 One pool for the cluster in Dallas 



1. Select the Origin pools tab and click Create.
2. Set Name to US
3. Set Origin Name to us-cluster
4. Set Origin Address to the kubernetes service <IngressSubdomain> printed by ibmcloud ks cluster get --cluster $MYCLUSTER for the US cluster
5. Set Health check to the one created in the previous section
6. Set Health Check Region to Western North America
7. Click Save







 One pool for the cluster in London 



1. Select the Origin pools tab and click Create.
2. Set Name to UK
3. Set Origin Name to uk-cluster
4. Set Origin Address to the kubernetes service <IngressSubdomain> printed by ibmcloud ks cluster get --cluster $MYCLUSTER for the UK cluster
5. Set Health check to the one created in the previous section
6. Set Health Check Region to Western Europe
7. Click Save







 And one pool with both clusters 



1. Select the Origin pools tab and click Create.
2. Set Name to All
3. Add two origins:



1. one with Origin Name set to us-cluster and the Origin Address set to <IngressSubdomain> in Dallas
2. one with Origin Name set to uk-cluster and the Origin Address set to <IngressSubdomain> in London



4. Set Health Check Region to Eastern North America
5. Set Health check to the one created in the previous section
6. Click Save









 Create the Global Load Balancer 

With the origin pools defined, you can complete the configuration of the load balancer.



1.
Cluster master HA proxy 1.9.7-alpine 2.0.1-alpine See the [HAProxy release notes](https://www.haproxy.org/download/2.0/src/CHANGELOG). 
 GPU device plug-in and installer a7e8ece d91d200 Updated image for [CVE-2019-9924](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9924). 
 Ubuntu 18.04 kernel and packages 4.15.0-54-generic 4.15.0-55-generic Updated worker node images with package updates for [CVE-2019-11085](https://nvd.nist.gov/vuln/detail/CVE-2019-11085), [CVE-2019-11815](https://nvd.nist.gov/vuln/detail/CVE-2019-11815), [CVE-2019-11833](https://nvd.nist.gov/vuln/detail/CVE-2019-11833), [CVE-2019-11884](https://nvd.nist.gov/vuln/detail/CVE-2019-11884), [CVE-2019-13057](https://nvd.nist.gov/vuln/detail/CVE-2019-13057), [CVE-2019-13565](https://nvd.nist.gov/vuln/detail/CVE-2019-13565), [CVE-2019-13636](https://nvd.nist.gov/vuln/detail/CVE-2019-13636), and [CVE-2019-13638](https://nvd.nist.gov/vuln/detail/CVE-2019-13638).
kubectl -n openshift-storage patch cephblockpool.ceph.rook.io/ocs-storagecluster-cephblockpool -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n openshift-storage patch cephcluster.ceph.rook.io/ocs-storagecluster-cephcluster -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n openshift-storage patch cephfilesystem.ceph.rook.io/ocs-storagecluster-cephfilesystem -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n openshift-storage patch cephobjectstore.ceph.rook.io/ocs-storagecluster-cephobjectstore -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n openshift-storage patch cephobjectstoreuser.ceph.rook.io/noobaa-ceph-objectstore-user -p '{"metadata":{"finalizers":[]}}' --type=merge
kubectl -n openshift-storage patch cephobjectstoreuser.ceph.rook.io/ocs-storagecluster-cephobjectstoreuser -p '{"metadata":{"finalizers":[]}}' --type=merge
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
],
"pools": [
{
"algorithm": "round_robin",
"health_monitor": {
"delay": 5,
"max_retries": 2,
"timeout": 2,
"type": "tcp",
"url_path": "/"
},
"name": "example-pool",
"protocol": "tcp",
"session_persistence": {
"cookie_name": "string",
"type": "source_ip"
},
"members":
{
"port": 80,
"target": {
"address": "192.168.100.5"
},
"weight": 50
},
{
"port": 80,
"target": {
"address": "192.168.100.6"
},
"weight": 50
}
]
}
],
"subnets": [
{
"id": "7ec87131-1c7e-4990-b4f0-a26f2e61f98e"
}
]
}'

Sample output:

{
"created_at": "2018-07-12T23:17:07.5985381Z",
"crn": "crn:v1:staging:public:is:us-south:a/123456::load-balancer:dd754295-e9e0-4c9d-bf6c-58fbc59e5727",
"hostname": "ac34687d.lb.appdomain.cloud",
"href": "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/dd754295-e9e0-4c9d-bf6c-58fbc59e5727",
To list available roles for the service, run ibmcloud iam roles --service <service_name>. The service name is the name of the service in the catalog, which you can get by running ibmcloud catalog search.

--service SERVICE_INSTANCE
: Required: The name of the IBM Cloud service instance that you want to bind. To find the name, run ibmcloud service list for Cloud Foundry services, and ibmcloud resource service-instances for IAM-enabled services.

-q
: Optional: Do not show the message of the day or update reminders.



 Example cluster service bind command 

ibmcloud oc cluster service bind --cluster my_cluster --namespace my_namespace --service my_service_instance







 ibmcloud oc cluster service ls 

Virtual Private Cloud

Classic infrastructure

List the services that are bound to one or all the Red Hat OpenShift project in a cluster. If no options are specified, the services for the default project are displayed.

ibmcloud oc cluster service ls --cluster CLUSTER [--namespace KUBERNETES_NAMESPACE] [--all-namespaces] [--output json] [-q]

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

-n, --namespace KUBERNETES_NAMESPACE
: Optional: Include the services that are bound to a specific project in a cluster.

--all-namespaces
: Optional: Include the services that are bound to all the projects in a cluster.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example cluster service ls command 

ibmcloud oc cluster service ls --cluster my_cluster --namespace my_namespace







 ibmcloud oc cluster service unbind 

Virtual Private Cloud

Classic infrastructure
start fs_sapmnt-clone then start s01_ers02_group (kind:Mandatory)
Colocation Constraints:
s01_ers02_group with s01_ascs01_group (score:-5000)
Ticket Constraints:

pcs resource clear ${sid}_ascs${ASCS_nr}_group

The Location constraints are removed:

pcs constraint

Sample output:

 pcs constraint
Location Constraints:
Ordering Constraints:
start s01_ascs01_group then stop s01_ers02_group (kind:Optional) (non-symmetrical)
start fs_sapmnt-clone then start s01_ascs01_group (kind:Mandatory)
start fs_sapmnt-clone then start s01_ers02_group (kind:Mandatory)
Colocation Constraints:
s01_ers02_group with s01_ascs01_group (score:-5000)
Ticket Constraints:
ibmcloud is instance-group-create INSTANCE_GROUP_NAME --instance-template INSTANCE_TEMPLATE --subnets SUBNETS [--membership-count MEMBERSHIP_COUNT] [--lb LB --lb-pool LB_POOL --application-port APPLICATION_PORT] [--vpc VPC] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is instance-group-create group-name --instance-template 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --subnet 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3,72b27b5c-f4b0-48bb-b954-5becc7c1dcb3
* ibmcloud is instance-group-create group-name --instance-template 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --subnet 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3,72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --membership-count 2
* ibmcloud is instance-group-create group-name --instance-template 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --subnet 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3,72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --output JSON
] ! ! ! !
<-- </section "id="section-kp-registrations-example-1" "> --><-- <section "id="section-kp-registrations-example-2" "> --> Example 2 This example shows the full lifecycle of two cloud resources (Cloud Object Storage and Key Protect - from creating Key Protect instances and creating a policy between them to deleting the instances.A summary of the steps is:<-- <table> -->| Step | Where | Description || ---- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------- || 1 | CLI | Create cloud object storage (COS) and Key Protect (KP) instances || 2 | CLI | Create a policy for COS to access KP encryption keys || 3 | CLI | Create a KP root key that COS uses to encrypt data || 4 | Console UI | Create a COS bucket and specify KP encryption; this is done in the console user interface (UI) because there is no API or CLI support at this time || 5 | CLI | View the KP registration || 6 | CLI | Upload and download an object to verify COS and KP works together || 7 | CLI | Delete the COS bucket and the KP root key || 8 | CLI | Delete the authorization policy between COS and KP || 9 | CLI | Delete the COS and KP instances |<-- </table ""> -->These commands show COS and Key Protect service plans.
Uninstalling the stand-alone IBM Cloud CLI 

Use the following steps to uninstall the stand-alone IBM Cloud® Command Line Interface on specific platforms.



  Uninstalling on Windows 



1.  Click the Start button, and then select Control Panel.
2.  In the pop-up window, click Uninstall a program.
3.  In the pop-up application list, locate IBM Cloud Command Line Interface.
4.  Right-click IBM Cloud Command Line Interface, and select Uninstall.
5.  The uninstaller is started. Follow the instructions to finish the uninstallation.







  Uninstalling on Linux and macOS 

The uninstallation steps are different depending on the version of the CLI that is installed.



1.  Check your IBM Cloud CLI version by running the following command:

ibmcloud -v
2.  Run the uninstallation commands for your version of the CLI.



*  To uninstall versions 0.9.0 and later, run the following command:

/usr/local/ibmcloud/uninstall
*  To uninstall versions earlier than 0.9.0, run all of the following commands:

rm -rf /usr/local/ibmcloud

rm -f /usr/local/bin/ibmcloud

rm -f /usr/local/bin/bluemix

rm -f /usr/local/bin/bx

rm -f /usr/local/bin/ibmcloud-analytics



3.  Clean up any autocompletion scripts, if you configured them. For more information, see [Enabling shell autocompletion](https://cloud.ibm.com/docs/cli/reference/ibmcloud?topic=cli-shell-autocompleteshell-autocomplete).
<-- </section "id="section-target-update-example-cos" "> --><-- </section "class="ph" id="section-target-update-cli-cos" "> --><-- <section "class="ph" id="section-target-delete-cli-cos" "> --> Deleting a target using the CLI Use this command to delete a target. ibmcloud atracker target rm --target TARGET --force] ! ! !
<-- <section "id="section-target-rm-options-cos" "> --> Command options --target TARGET: The ID or name of the target.--force | -f: Will delete the target without providing the user with any additional prompt.help | --help | -h: List options available for the command.<-- </section "id="section-target-rm-options-cos" "> --><-- <section "id="section-target-rm-example-cos" "> --> Example The following is an example using the ibmcloud atracker target rm --target xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx command. Are you sure you want to remove the target with target ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx? y/N] >y
OK
Target with target ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx was successfully removed.
The following is an example using the ibmcloud atracker target rm --target xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -force command.This example shows a failed command where the specified target could not be found. Are you sure you want to remove the Target bearing Target ID 33333333-3333-3333-3333-333333333333? y/N] ! ! ! > y
FAILED
Something went wrong. Error:
Status Code: 404
The second occurrence of Text analysis with Code Engine in the body of public/index.html and public/501.html can be changed to add in your name. Create the container image in a code engine namespace and create the application in one command:

ibmcloud ce application create --name frontend-fromsource --build-source . --env BACKEND_URL=$BACKEND_PRIVATE_URL





 Step 7: Remove resources 



1. With the command below, delete the project to delete all it's components (applications, jobs etc.).

ibmcloud code-engine project delete --name $PROJECT_NAME
2. Navigate to [Resource List](https://cloud.ibm.com/resources/)
3. Delete the services you created:



* IBM Cloud® Object Storage
* IBM Watson® Natural Language Understanding





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





 Related resources 



* [IBM Cloud Code Engine Documentation](https://cloud.ibm.com/docs/codeengine)
* [Building applications by using buildpacks](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-app-tutorial)
* [Getting started with subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-events)
"deletetest/testfile1.txt",
"deletetest/testfile2.txt",
"deletetest/testfile3.txt",
"deletetest/testfile4.txt",
"deletetest/testfile5.txt"
);

DeleteObjectsResult res = _cos.deleteObjects(req);

System.out.printf("Deleted items for %sn", bucketName);

List<DeleteObjectsResult.DeletedObject> deletedItems = res.getDeletedObjects();
for(DeleteObjectsResult.DeletedObject deletedItem : deletedItems) {
System.out.printf("Deleted item: %sn", deletedItem.getKey());
}
}
Show more

SDK References



* Classes



* [DeleteObjectsRequest](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/model/DeleteObjectsRequest.html)
* [DeleteObjectsResult](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/model/DeleteObjectsResult.html)
* [DeleteObjectsResult.DeletedObject](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/model/DeleteObjectsResult.DeletedObject.html)



* Methods
5. On the Managed Istio card, verify that the add-on you uninstalled is no longer listed.







 Uninstalling managed Istio add-ons from the CLI 

If you did not install the deprecated istio-sample-bookinfo and istio-extras add-ons, skip steps 1 and 2.



1. Disable the istio-sample-bookinfo add-on.

ibmcloud ks cluster addon disable istio-sample-bookinfo --cluster <cluster_name_or_ID>
2. Disable the istio-extras add-on.

ibmcloud ks cluster addon disable istio-extras --cluster <cluster_name_or_ID>
3. Disable the istio add-on.

ibmcloud ks cluster addon disable istio --cluster <cluster_name_or_ID> -f
4. Verify that all managed Istio add-ons are disabled in this cluster. No Istio add-ons are returned in the output.

ibmcloud ks cluster addon ls --cluster <cluster_name_or_ID>









 Step 3: Remove the Istio operator 

After the add-on is completely uninstalled, you can remove the Istio operator.



 Version 1.10 or later 

Delete the Istio operator deployment, service account, cluster role binding, and cluster role.

kubectl delete deployment -n ibm-operators addon-istio-operator --ignore-not-found=true
kubectl delete serviceaccount -n ibm-operators addon-istio-operator --ignore-not-found=true
kubectl delete clusterrolebinding addon-istio-operator --ignore-not-found=true
kubectl delete clusterrole addon-istio-operator --ignore-not-found=true





 Version 1.9 or earlier 

Delete the Istio operator pod's CSV.
If no events are reported, perform the discovery scan again to ensure that all paths are properly discovered. If an event is in progress, the storage can be attached with a single path. However, it's essential that paths are rescanned after the event is completed. If both paths are not discovered after the rescan, [create a support case](https://cloud.ibm.com/unifiedsupport/cases/add) so it can be properly investigated.





 Unmounting Block Storage for Classic volumes 

Following are the steps that are required to disconnect a Windows®-based IBM Cloud® compute instance to an MPIO iSCSI LUN. The example is based on Windows® Server 2012. The steps can be adjusted for other Windows® versions according to the OS vendor Documentation.



 Disconnect the volume from the iSCSI Initiator 



1. In Server Manager, click Storage > iSCSI.
2. Right-click the volume and take it Offline.
3. In iSCSI Initiator, click Targets.
4. Select the target that you want to remove and click Disconnect.







 Removing targets 

This step is optional, for when you no longer need to access the iSCSI targets.



1. Click Discovery in the iSCSI Initiator.
2. Highlight the target portal that is associated with your storage volume and click Remove.
* UI
* CLI
* API







 Deleting a route 

You can delete a route for an IBM Cloud service by using the UI, CLI, or API.



 Deleting a route in the UI 

To delete a route in the UI, follow these steps:



1. From the [IBM Cloud console](https://cloud.ibm.com/login), select the Navigation Menu ![Navigation Menu](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/menu_icon.png), then click VPC Infrastructure > Routing tables in the Network section. The Routing tables for VPC page appear.
2. Click the number of routes, or the routing table name that contains the route.
3. Click the Actions menu ![Actions menu](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/overflow.png) next to the route that you want to delete, then click Delete. Click Delete again to confirm the deletion.







 Deleting a route from the CLI 

Before you begin, make sure to [set up your CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).

To delete a route by using the CLI, run the following command:

ibmcloud is vpc-routing-table-route-delete VPC ROUTING_TABLE ROUTE [-f, --force]

Where:



* VPC is the ID of the VPC.
* ROUTING_TABLE is the ID of the VPC routing table.
* ROUTE is the ID of the VPC route.
* -f, --force forces the operation without confirmation.
[reclamation](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation) commands.



1. Discover projects that are soft deleted by using the [reclamation list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation-list) command.

ibmcloud ce reclamation list

Example output

Getting project reclamations...
OK
Name ID Reclamation ID Status Region Resource Group Age Time to Hard Deletion
myproject def218c5-abcd-abcd-abcd-97854c288d76 48e3d7a2-abcd-abcd-abcd-99db7152b8fe soft deleted us-south default 40h 6d23h
myproject2 01f0bc66-abcd-abcd-abcd-3ef7e99f6f69 af2cd017-abcd-abcd-abcd-d32e2bb79136 soft deleted jp-osa default 8m58s 2d11h
2. Use the [reclamation restore](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation-restore) command to restore a soft deleted project to an active state. The following example restores the myproject2 project and its components. Make sure that you are targeting the correct region of the project that you want to restore.

ibmcloud ce reclamation restore --name myproject

Example output

Restoring project 'myproject'...
OK



Alternatively, you can use the [project restore](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-restore) command to restore a soft deleted project to an active state.







 Permanently deleting projects 



 Permanently deleting projects from the console 

After you soft delete a project (or delete the project with reclamation), you can restore it or permanently delete it from the console. When a project is permanently deleted, it cannot be restored.
If you want to restore a deleted chart, you can list the contents of the trash by running the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command and restore a selected chart by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command.

To delete a chart by using the CLI, complete the following steps:



1. Log in to IBM Cloud by running the ibmcloud login command.
2. To delete a chart, run the following command, where CHART is the name of the chart that you want to remove, in the format repository@digest or repository:tag. Unlike images, a tag must be specified because the latest tag doesn't exist because a tag must always match the chart's semantic version. You can delete multiple charts by listing each private IBM Cloud registry path in the command with a space between each path.

ibmcloud cr image-rm CHART

To find the names of your charts, run ibmcloud cr image-list. The registry stores different artifact types that include Helm charts and container images. Combine the content of the Repository column (repository) and Tag column (tag) separated by a colon (:) to create the image name in the format repository:tag. To identify your chart by digest, run the ibmcloud cr image-digests command. Combine the content of the Repository column (repository) and the Digest column (digest) separated by an at (@) symbol to create the image name in the format repository@digest.
3. Verify that the chart was deleted by running the following command, and check that the chart does not show in the list.

ibmcloud cr image-list







 Deleting charts from your private repository in the console 

You can delete unwanted charts and all their tags from your private IBM Cloud repository by using the IBM Cloud console.

Deleting a chart that is being used by an existing deployment might cause a Helm upgrade, rollback, or delete to fail.
Cluster Local URL: http://myapp.abcdabcdabc.svc.cluster.local
Console URL: https://cloud.ibm.com/codeengine/project/us-south/01234567-abcd-abcd-abcd-abcdabcd1111/application/myapp/configuration
Status Summary: Application deployed successfully
[...]
Service Bindings:
Service Instance Service Type Environment Variable Prefix
myobjectstorage cloud-object-storage CLOUD_OBJECT_STORAGE

Similarly, if you are working with jobs, run the ibmcloud ce job get --name JOB_NAME command to discover if deprecated bindings are used with your job.
2. Unbind the existing service bindings that use the previous implementation. The --all option specifies to unbind all service instances for this application.

ibmcloud ce app unbind --name APP_NAME --all

Similarly, if you are working with jobs, run the ibmcloud ce job unbind --name JOB_NAME --all command to unbind all service instances for your job.
3. Create new bindings. To create new bindings, run the [ibmcloud ce app bind](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-bind) or [ibmcloud ce job bind](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-bind) command. To replace service binding that used the previous implementation, use the commands that are provided in the output of the app get or job get commands. For example, to re-create an existing binding from the Code Engine application, myapp, to the IBM Cloud Object Storage service instance, myobjectstorage,

ibmcloud ce app bind --name myapp --service-instance myobjectstorage --prefix CLOUD_OBJECT_STORAGE

Similarly, if you are working with jobs, run the ibmcloud ce job bind --name JOB_NAME ---service-instance SERVICE_INSTANCE --prefix PREFIX command.