vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Log in the IBM Cloud Pak for Multicloud Management management console by using the admin user name and password that you configured during the installation.
2. Optional: Install any optional modules for the IBM Cloud Pak for Multicloud Management. For instructions, see [Installing, configuring, and upgrading the modules](https://www.ibm.com/support/knowledgecenter/en/SSFC4F_1.3.0/install/install_modules.html).





 Uninstalling the IBM Cloud Pak for Multicloud Management 

To uninstall IBM Cloud Pak for Multicloud Management, you can use the IBM Cloud Pak for Multicloud Management console or the command-line interface (CLI).



 Uninstalling the IBM Cloud Pak for Multicloud Management from the console 



1. Enter the workspace of your installed IBM Cloud Pak for Multicloud Management.
2. Click the Actions button in the upper right corner. Then, click the delete button to trigger a delete.
3. Choose Delete workspace and Delete all associated resources and input the name of the workspace to confirm. Click the delete to delete the workspace.
4. Waiting for the uninstall finish.
5. Verify that the Cloud Pak is uninstalled:

Access the {{site.data.keyword.open_s}} web console and verify that the components that are related to the IBM Cloud Pak for Multicloud Management, such as any related pods, are no longer installed.







 Uninstalling the IBM Cloud Pak for Multicloud Management on with command-line 

If the delete operation failed from the console or you want to use command-line, you can use the oc command-line interface to complete the steps to uninstall. When you use the command-line, you need to remove the resources on your OpenShift Container Platform cluster that are associated with the IBM Cloud Pak for Multicloud Management.

If you do not have the OpenShift CLI installed, download and install the CLI from the Red Hat Customer Portal.
LunaSA Client settings Typically no changes would be required here unless you have explicitly modified the names of these files.



* ClientPrivKeyFile: Name of the HSM client private key.
* ClientCertFile: Name of the HSM client certificate.
* ServerCAFile: Name of the HSM server certificate.



The following example shows what the file would look like if you were using IBM Cloud HSM. It provides the path to the HSM shared object, certificate and keys. Note that the naming of these files depends on the HSM library that is being used.

Chrystoki2 = {
LibUNIX = /hsm/libCryptoki2.so;
LibUNIX64 = /hsm/libCryptoki2_64.so;
}
...
LunaSA Client = {
...
ClientPrivKeyFile = /hsm/key.pem;
ClientCertFile = /hsm/cert.pem;
ServerCAFile = /hsm/cafile.pem;
...
}





 Step two: Build the HSM client image 

The HSM client image can be built with a Docker file similar to the following:



* The following Docker file is for IBM Cloud HSM. If you are not using IBM Cloud HSM, you need to build your own Docker file.
* You should be aware that this Docker file automatically accepts the Gemalto client license.
* Note that the 64 folder inside the Docker file is required for installing the HSM client.



FROM registry.access.redhat.com/ubi8/ubi-minimal as builder

 This directory contains the installation files for gemalto/luna client
COPY 64 64

RUN microdnf install -y 
gcc 
gcc-c++ 
openssh-clients 
bind-utils 
iputils 
&& cd 64 && 
 NOTE we are accepting the license for installing gemalto client here
 please take a look at the license before moving forward
echo "y" | ./install.sh -p sa

 Final image
High Availability and Disaster Recovery options in Power Systems Virtual Servers 

The Power Systems Virtual Server instance restarts the virtual servers on a different host system if a hardware failure occurs. This process provides basic High Availability (HA) capabilities for Power Systems Virtual Server. If you want more advanced HA or Disaster Recover (DR) solutions, you can deploy the following applications in your Power Systems Virtual Server environment.



 PowerHA SystemMirror for AIX Standard Edition 

You can use a monthly subscription model when you purchase PowerHA SystemMirror for AIX Standard Edition. For more information, see [Standard Edition monthly pricing options](https://www.ibm.com/downloads/cas/US-ENUS219-288-CA/name/ENUS219-288.PDF).

After you purchase the software, you can download it from [Entitled Software Support (ESS)](https://www.ibm.com/servers/eserver/ess/index.wss). You can install PowerHA SystemMirror for AIX on the virtual server that is running in your Power Systems Virtual Server environment. For installation instructions, see [Installing PowerHA SystemMirror](https://www.ibm.com/support/knowledgecenter/SSPHQG_7.2/install/ha_install.html).

Review the following information for implementing PowerHA SystemMirror for AIX in your Power Systems Virtual Server environment.



* When you are creating the virtual servers that are part of the PowerHA SystemMirror cluster, you must select Different Server from the Colocation Rules field. Selecting Different Server ensures that the different logical partitions (LPARs) that will be a part of the PowerHA SystemMirror cluster are not deployed on the same host.
* You must select On from the Shareable field when you create storage volumes for the virtual severs that are part of the PowerHA SystemMirror cluster.
* By using the Power Systems Virtual Server, you do not have access to the HMC, VIOS, and the host system. Therefore, any PowerHA SystemMirror functions that require access to these capabilities, such as Resource Optimized High Availability (ROHA) and Active Node Halt Policy (ANHP), are not available.
We are able to support the most popular Operating Systems in the market, please submit a ticket or click on the help to send us the configuration detail.



IBM Spectrum LSF



* What Spectrum LSF packages are included in a cluster deployed with this offering?

The following Spectrum LSF programs are included:



* IBM Spectrum LSF Standard Edition
* IBM Spectrum LSF License Scheduler
* IBM Spectrum LSF Data Manager



* What locations are available for deploying VPC resources?

Available regions and zones for deploying VPC resources, and a mapping of those to city locations and data centers can be found in [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).
* What permissions do I need in order to create a cluster using the offering?

Instructions for setting the appropriate permissions for IBM Cloud services that are used by the offering to create a cluster can be found in [Granting user permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources), [Managing user access for Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-access), and [Assigning access to Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-assign-access).
* How do I SSH among nodes?

All of the nodes in the HPC cluster have the same public key that you register at your cluster creation. You can use ssh-agent forwarding, which is a common technique to access remote nodes that have the same public key. It automates to securely forward private keys to remote nodes. Forwarded keys are deleted immediately after a session is closed.

To securely forward private keys to remote nodes, you need to do ssh-add and ssh -A.

[your local PC]$ ssh-add {id_rsa for lsf cluster}
[your local PC] ssh -A -J root@jumpbox_fip root@management_private_ip
...
Order all of these servers at the same time so they are placed in the same pod at the same time. Ordering hardware at separate times can cause hosts and firewalls to be in separate pods within an IBM Cloud data center.



 ESXi Hosts 

For each ESXi host that is ordered for the environment, VMware ESXi 5.5 is the operating system. If you want to use IBM Cloud vSphere licenses, monthly charges are incurred that are based on usage.

Another option is to install ESXi by using your own ISO. Instructions for this process can be found in [Installing VMware vSphere ESXi via Remote Console and Virtual Media](https://cloud.ibm.com/docs/vmware?topic=vmware-installing-vsphere-esxiinstalling-vsphere-esxi). If you want to install ESXi by using your own ISO, make sure to select No Operating System as the operating system for the management and capacity hosts during the ordering process.

Note: This implementation requires Enterprise Plus licensing to use vSphere Distributed Virtual Switches. If your license is not valid for Enterprise Plus, you need to use the IBM Cloud provided VMware Service Provider Program (VSPP) license.





 Ordering management hosts 

Use the following steps to order the management host servers.



1. Open a browser window and log in to IBM Cloud.
2. Select Account > Place an Order.
3. Select Bare Metal Servers > Monthly.
4. Choose an appropriate server that meets the requirements for the management cluster on the server list screen. Note: At a minimum, ESXi 5.5 requires a single dual-core processor, 4 GB of RAM, and 1 Gb Ethernet controller.
5. Select the appropriate data center (where the VLANs were created) to provision the ESXi servers and specify the following specifications for each option:



* Quantity: 2
* RAM: 32 GB
When a certificate expires, transactions on the network will fail because the identity can no longer be trusted. It is your responsibility to monitor those expiration dates and manage your certificate renewal accordingly. The process varies depending on the type of certificate, when it was generated, and for organization admin certificates, whether Node OU support was enabled on the MSP when the identity was enrolled. The platform attempts to renew the peer and ordering node enrollment certificates 30 days before they expire. See [Managing certificates](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmt) to learn more about the types of certificates that you need to monitor and how to renew them.





 What languages are supported for smart contracts? 

The IBM Blockchain Platform supports smart contracts that are written in Node.js, Golang (Go), JavaScript, and Java. The new Hyperledger Fabric programming model currently supports JavaScript, TypeScript, Java, and Go. If you are interested in preserving your existing application code, or by using Fabric SDKs for Go, you can still connect to your IBM Blockchain Platform network by using the lower-level Fabric SDK APIs.





 What version of the IBM Blockchain Platform works with the Ansible collection? 

Versions 2.1.3 and 2.5.x of the IBM Blockchain Platform can be used with the Ansible collection to deploy a Hyperledger Fabric network.





 How do I get support for running the IBM Blockchain Platform Ansible playbook? 

Ansible is an open source technology and this product is not officially supported by IBM. For support related to the usage of the IBM Blockchain Platform and Ansible playbooks use the [GitHub repository](https://github.com/IBM-Blockchain/ansible-collection/issues).





 Can the IBM Blockchain Platform monitor the health of a client application?
helm search repo ibm-charts | grep object-storage-plugin

Example output

ibm-charts/ibm-object-storage-plugin 1.0.9 1.0.9 A Helm chart for installing ibmcloud object storage plugin
3. List the installed Helm charts in your cluster and compare the version that you installed with the version that is available.

helm list --all-namespaces
4. If a more recent version is available, install this version. For instructions, see [Updating the IBM Cloud Block Storage plug-in](https://cloud.ibm.com/docs/containers?topic=containers-block_storageupdate_block) and [Updating the IBM Cloud Object Storage plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_installupdate_cos_plugin).









 Portworx 



1. Find the [latest Helm chart version](https://github.com/IBM/charts/tree/master/community/portworx) that is available.
2. List the installed Helm charts in your cluster and compare the version that you installed with the version that is available.

helm list --all-namespaces
3. If a more recent version is available, install this version. For instructions, see [Updating Portworx in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_update).







 OpenShift Data Foundation 

Describe your ODF resources and review the command outputs for any error messages.



1. List the name of your ODF cluster.

oc get ocscluster

Example output:

NAME AGE
ocscluster-vpc 71d
2. Describe the storage cluster and review the Events section of the output for any error messages.

oc describe ocscluster <ocscluster-name>
3. List the pods in the kube-system namespace and verify that they are Running.
helm search repo ibm-charts | grep object-storage-plugin

Example output

ibm-charts/ibm-object-storage-plugin 1.0.9 1.0.9 A Helm chart for installing ibmcloud object storage plugin
3. List the installed Helm charts in your cluster and compare the version that you installed with the version that is available.

helm list --all-namespaces
4. If a more recent version is available, install this version. For instructions, see [Updating the IBM Cloud Block Storage plug-in](https://cloud.ibm.com/docs/containers?topic=containers-block_storageupdate_block) and [Updating the IBM Cloud Object Storage plug-in](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_installupdate_cos_plugin).









 Portworx 



1. Find the [latest Helm chart version](https://github.com/IBM/charts/tree/master/community/portworx) that is available.
2. List the installed Helm charts in your cluster and compare the version that you installed with the version that is available.

helm list --all-namespaces
3. If a more recent version is available, install this version. For instructions, see [Updating Portworx in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_update).







 OpenShift Data Foundation 

Describe your ODF resources and review the command outputs for any error messages.



1. List the name of your ODF cluster.

kubectl get ocscluster

Example output:

NAME AGE
ocscluster-vpc 71d
2. Describe the storage cluster and review the Events section of the output for any error messages.

kubectl describe ocscluster <ocscluster-name>
3. List the pods in the kube-system namespace and verify that they are Running.
* If the entity has any existing entity values, they are displayed for informational purposes only. You are adding the annotation to the entity, not to any specific entity value.
* If you want to teach the model that the mention is synonymous with an existing entity value, add a colon (:) after the entity name to show a list of entity values. Choose an entity value from the list that is displayed. For example, @product:device.

![Search box with search parameter prod](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/oe-intent-review.png)



6. Select the entity or entity and value to which you want to add the annotation.

In this example, mobile phones is being added as an annotation for the @product entity value and as a synonym for the @product:device entity value.

Create at least 10 annotations for each contextual entity; more annotations are recommended for production use.
7. If none of the entities are appropriate, you can create a new entity by adding its name. Then choose the {entity_name}(create new entity) option from the list.

![Shows how to add a new @location entity from annotation page](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/oe-add-entity.png)
8. Repeat this process for each entity mention that you want to annotate.

Be sure to annotate every mention of an entity type that occurs in any user examples that you edit. See [What you don't annotate matters](https://cloud.ibm.com/docs/assistant?topic=assistant-entitiesentities-counter-examples) for more details.
9. Now, click the annotation you just created.
Looking for instructions for how to update or remove the IBM Cloud Block Volume Attacher plug-in? See [Updating the plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesupdate_block_attacher) and [Removing the plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesremove_block_attacher).



1. [Follow the instructions](https://cloud.ibm.com/docs/openshift?topic=openshift-helminstall_v3) to install the Helm client version 3 on your local machine.
2. Update the Helm repo to retrieve the latest version of all Helm charts in this repo.

helm repo update
3. Install the IBM Cloud Block Volume Attacher plug-in. When you install the plug-in, pre-defined block storage classes are added to your cluster.

helm install block-attacher iks-charts/ibm-block-storage-attacher --namespace kube-system

Example output

NAME: block-volume-attacher
LAST DEPLOYED: Thu Sep 13 22:48:18 2018
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1beta1/ClusterRoleBinding
NAME AGE
ibmcloud-block-storage-attacher 1s

==> v1beta1/DaemonSet
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
ibmcloud-block-storage-attacher 0 0 0 0 0 <none> 1s

==> v1/StorageClass
NAME PROVISIONER AGE
ibmc-block-attacher ibm.io/ibmc-blockattacher 1s

==> v1/ServiceAccount
NAME SECRETS AGE
ibmcloud-block-storage-attacher 1 1s

==> v1beta1/ClusterRole
NAME AGE
ibmcloud-block-storage-attacher 1s

NOTES:
Thank you for installing: ibmcloud-block-storage-attacher.
Configuring Block Storage for Classic for backup with Plesk 

You can use the following instructions to configure IBM Cloud® Block Storage for Classic for your backups in Plesk. The assumption is that root or sudo SSH and full admin level Plesk access are available. These instructions are based on a CentOS7 host.

For more information, see [Plesk's Documentation for backing up and restoration](https://docs.plesk.com/en-US/12.5/administrator-guide/backing-up-and-restoration.59256/).



1. Connect to the host through SSH.
2. Ensure that a mount point target exists.

Plesk has two options for storing backups. One option is the internal Plesk storage (backup storage on your Plesk server). The other option is an external FTP storage (backup storage on some external server in the web or your local network). Commonly on Plesk boxes, internal backups are stored in /var/lib/psa/dumps and use /tmp as a temporary directory. In this example, the temporary directory is kept local, but the dumps directory is moved to the Block Storage for Classic target (/backup/psa/dumps). No FTP user credentials are required.
3. Configure your Block Storage for Classic as described in [Connecting to iSCSI LUNs on Linux®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinuxmountingLinux). Mount Block Storage for Classic to /backup and configure /etc/fstab to enable mounting on start.
4. Optional: Copy existing backups to the new storage. You can use rsync.

rsync -avz /var/lib/psa/dumps /backup/psa/dumps

This command compresses and transmits your data, and preserves as much as possible, except for hard links. It provides information about what files are being transferred plus a brief summary at the end.
5.
The key part owner needs to be the only person who knows the file password or the smart card personal identification number (PIN) for the key part.





 IBM Cloud Trusted Key Entry CLI plug-in 

Trusted Key Entry (TKE) command-line interface (CLI) plug-in is a CLI plug-in working with IBM Cloud CLI. The TKE plug-in provides a set of functions for managing crypto units that are assigned to an IBM Cloud user account. You can use the TKE plug-in to set up administrators and load the master key with the requirements of a medium level of security. The TKE CLI plug-in provides two approaches to initializing service instances: [Initializing service instances using key part files](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm) and [Initializing service instances using recovery crypto units](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unit). For the complete command reference, see [Trusted Key Entry CLI plug-in reference](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-cli-plugin-hpcs-cli-plugintke-cli-plugin).





 Management Utilities 

The Management Utilities provide an alternate way of configuring service instances with signature keys and master key parts that are stored on smart cards with the highest level of security. To use the Management Utilities, you must order IBM-supported smart card readers and smart cards. For detailed instructions on installing and configuring the Management Utilities, see [Setting up smart cards and the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-prepare-management-utilities) and [Initializing service instances using smart cards and the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-management-utilities).





 Smart cards 

A smart card looks like a credit card with an embedded chip.
The key part owner needs to be the only person who knows the file password or the smart card personal identification number (PIN) for the key part.





 IBM Cloud Trusted Key Entry CLI plug-in 

Trusted Key Entry (TKE) command-line interface (CLI) plug-in is a CLI plug-in working with IBM Cloud CLI. The TKE plug-in provides a set of functions for managing crypto units that are assigned to an IBM Cloud user account. You can use the TKE plug-in to set up administrators and load the master key with the requirements of a medium level of security. The TKE CLI plug-in provides two approaches to initializing service instances: [Initializing service instances using key part files](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm) and [Initializing service instances using recovery crypto units](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unit). For the complete command reference, see [Trusted Key Entry CLI plug-in reference](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-cli-plugin-hpcs-cli-plugintke-cli-plugin).





 Management Utilities 

The Management Utilities provide an alternative way of configuring service instances with signature keys and master key parts that are stored on smart cards with the highest level of security. To use the Management Utilities, you must order IBM-supported smart card readers and smart cards. For detailed instructions on installing and configuring the Management Utilities, see [Setting up smart cards and the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-prepare-management-utilities) and [Initializing service instances using smart cards and the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-management-utilities).





 Smart cards 

A smart card looks like a credit card with an embedded chip.