vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To learn more about all the properties, see [Deployment values](https://cloud.ibm.com/docs/hpc-openshift?topic=hpc-openshift-deployment-values). You can view a sample configuration file [here](https://github.com/IBM-Cloud/hpc-cluster-lsf/blob/main/sample/configs/hpc_workspace_config.json). For more information about the sample JSON file used by the Schematics CLI, see [IBM Cloud Schematics CLI](https://cloud.ibm.com/docs/hpc-openshift?topic=schematics-schematics-cli-reference). If you need to override any default parameters, you can redefine them in variablestore.
6. Update the mandatory properties for api_key, region, and ssh_key_name based on your specific setup. In addition, review the cluster_prefix and worker_nodes_per_zone values to make sure that they are correct according to your specifications and requirements.
7. Review and update any optional properties in the config.json file to fit your specific Red Hat OpenShift cluster instance.





 Next steps 

After you've reviewed and completed the prerequisites for setting up the CLI, you are ready to [Create a workspace](https://cloud.ibm.com/docs/hpc-openshift?topic=hpc-openshift-creating-workspace&interface=cli).
For more information, see [Setting up access to your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-users).





 Storage 

You must ensure that your cluster has sufficient resources and is configured to use supported storage. You can choose one of the following storage options:



* Single zone VPC Gen2 cluster with storage OpenShift® Data Foundation
* Multi zone VPC Gen2 cluster with storage OpenShift® Data Foundation



You must also ensure that your cluster has sufficient resources and is configured to use supported storage.







 Step 1. Assign the license 

If you don't already have a license, you can:



* Purchase a license through [IBM Passport Advantage](https://www.ibm.com/software/passportadvantage/index.html).
* [Register](https://www.ibm.com/account/reg/us-en/signup?formid=urx-42212) for a 60-day trial license of IBM Cloud Pak for Data.



Important: The trial is for IBM Cloud Pak for Data software only. The trial does not include entitlement to the Red Hat OpenShift Container Platform.

To assign your license, follow these steps:



1. Log in to your [IBM Cloud account](https://cloud.ibm.com).
2. If you don't see any licenses to assign, navigate to Manage > Account and then click Licenses and entitlements in the navigation menu.
3. If there are no licenses to assign on the Licenses and entitlements page, click Check IBM Passport Advantage.
4. Select the appropriate license and click Assign.







 Step 2. Configure your installation environment 

Specify where you want to install IBM Cloud Pak for Data:



1. Select the Red Hat OpenShift on IBM Cloud cluster where you want to deploy IBM Cloud Pak for Data.
2. Enter or select the Red Hat OpenShift on IBM Cloud project where you want to deploy IBM Cloud Pak for Data.







 Step 3. Configure your workspace 

Specify how you will track and manage your installation:



1.
If you don't want to pass the --custom-data command option during VM creation, you can run the host registration script on each VM after provisioning.
7. Wait for the instances to create. During the creation of your instance, the script runs automatically. This process takes a few minutes to complete.
8. Monitor the progress of the registration script.



1. Get the public IP address of one of your instances. For more information, see the [Azure CLI documentation](https://docs.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latestaz_vm_list_ip_addresses).

az vm list-ip-addresses -g <resource_group> -n <vm_name>
2. Log in to your instance.

ssh <username>:<public_IP_address>
3. Monitor the progress of the registration script.

journalctl -f -u ibm-host-attach



9. From the [Satellite console](https://cloud.ibm.com/satellite/locations), check that your hosts are shown in the Hosts tab of your location. All hosts show a Health status of Ready when a connection to the machine can be established, and a Status of Unassigned as the hosts are not yet assigned to your Satellite location control plane or a Red Hat OpenShift on IBM Cloud cluster.
10. Assign your hosts to the [Satellite control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-control-plane) or a [Red Hat OpenShift on IBM Cloud cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hostshost-assign-manual).







 Security group settings for Azure 

As described in the [host networking requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network), your Azure hosts must have access to connect to IBM Cloud Satellite. You might find that you need to update your security group settings in Azure, similar to the following example.
* If you enter a specific IP range and running Red Hat OpenShift 4.7 or earlier., don't use the following reserved ranges: 172.16.0.0/16, 172.18.0.0/16, 172.19.0.0/16, and 172.20.0.0/16.



5. To run default Red Hat OpenShift components such as the web console or OperatorHub, and to allow your cluster to access public endpoints such as a public URL of another app or an IBM Cloud service that supports public cloud service endpoints only, you must attach a public gateway to your subnet.
6. Click Create subnet.
7. Use the subnet to [create a cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-vpc-gen2), [create a new worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersvpc_add_pool), or [add the subnet to an existing worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersvpc_add_zone).> Do not delete the subnets that you attach to your cluster during cluster creation or when you add worker nodes in a zone. If you delete a VPC subnet that your cluster used, any load balancers that use IP addresses from the subnet might experience issues, and you might be unable to create new load balancers.







 Creating a VPC subnet in the CLI 

Use the IBM Cloud CLI to create a VPC subnet for your cluster and optionally attach a public gateway to the subnet.

Before you begin



1. In your command line, log in to your IBM Cloud account and target the IBM Cloud region and resource group where you want to create your VPC cluster. For supported regions, see [Creating a VPC in a different region](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region).
Assigning IBM Cloud IAM roles with the console 

Grant users access to your Red Hat OpenShift on IBM Cloud clusters by assigning IBM Cloud IAM platform access and service access roles with the IBM Cloud console.

don't assign platform access roles at the same time as a service access role. You must assign platform and service access roles separately.

Before you begin, verify that you're assigned the Administrator platform access role for the IBM Cloud account in which you're working.



1. Log in to the [IBM Cloud console](https://cloud.ibm.com/). From the menu bar, select Manage > Access (IAM).
2. Select users individually or create an access group of users.



* To assign roles to an individual user



1. Click the Users page, and then click the name of the user that you want to set permissions for. If the user isn't shown, click Invite users to add them to the account.
2. Click the Access policies tab, and then click Assign access. Now, the breadcrumbs on the page are Users / Manage User.
3. Optional: Add the user to an access group that has access to Red Hat OpenShift on IBM Cloud.



* To assign roles to multiple users in an access group



1. Click the Access groups page.
2. Click Create and give your group a Name and Description. Click Create.
3. Click Add users to add people to your access group. A list of users that have access to your account is shown.
4. Check the box next to the users that you want to add to the group. A dialog box displays.
5. Click Add to group.
6. Click the Access policies tab.
7. Click Assign access. Now, the breadcrumbs on the page are Groups / Manage Group.





3. Assign an access policy to Red Hat OpenShift on IBM Cloud.



1. Click the IAM services tile.
2. In the services drop-down list, select Kubernetes Service.
3. Click Select to choose the trusted profile that your account administrator created for you.









 Using the CLI to log in 

You choose to use either a one-time passcode or an API key to log in by using the CLI. You can find details based on whether you're using the IBM Cloud or Red Hat OpenShift CLI in the following sections.



 Using a one-time passcode to log in with the CLI 

When you use the one-time passcode option to log in with a federated ID, you specify the single-sign on (SSO) parameter to get a one-time passcode, which you then enter at login.

Because a one-time passcode retrieves code from the IBM Cloud console, it causes the use of a federated ID in your automation script to fail. Avoid trouble by using the API key option with an automated script.



 From the IBM Cloud CLI 

You can use two different methods to log in with the CLI. For the first method, use the following steps:



1. Specify the --sso option with the ibmcloud login command.
2. Follow the URL in the prompt to get the one-time passcode.
3. Copy and paste the passcode value in the CLI as your input.

ibmcloud login --sso
API endpoint: https://cloud.ibm.com

Get One Time Code from https://identity-2.us-south.iam.cloud.ibm.com/identity/passcode to proceed.
Open the URL in the default browser? [Y/n]>
One Time Code >
Authenticating...
OK



If you're already logged in to the console, you can use the following steps:



1. In the IBM Cloud console, click the Avatar icon ![Avatar icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/i-avatar-icon.svg) > Log in to CLI and API.
/dev/mapper/datavg-sapmntlv
165G 60M 157G 1% /sapmnt

If you install an SAP NetWeaver-based SAP application on IBM Db2, you must create subdirectories under /backup owned by the database admin user (db2SID) for full backups and archived log files. To automatically archive the log files, set LOGMETH1 in your Db2 on Cloud database. Refer to the [Db2 on Cloud documentation)](http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.ha.doc/doc/c0051344.html) for details.







 Step 4: Installing your SAP landscape 



 Prerequisite: Installing RPM packages 

An SAP installation requires certain prerequisites for the packages that are installed on the OS and the OS daemons that are running. Refer to the latest [installation guides)](https://support.sap.com/en/my-support/software-downloads.html). Click Access downloads under Installations & Upgrades (requires an [SAP S-user ID](https://cloud.ibm.com/docs/sap?topic=sap-necessary-credentials). Also, refer to the latest [support notes)](https://support.sap.com/en/my-support/knowledge-base.html) (requires an SAP S-user ID) from SAP for an up-to-date list of these prerequisites.

Two more packages need to be installed:



* compat-sap-c++: Generally achieves compatibility of the C++ runtime with the compilers that are used by SAP. Because Red Hat Enterprise Linux for SAP Business Application 7.X was selected as the OS for both the 32 GB application server and the 192 GB database server, you use compat-sap-c++-7.
* uuidd: Maintains OS support for the creation of UUIDs.







 Checking if uuidd is installed 



1. Check whether uuid daemon (uuidd) is installed. If it is not, install and start it.
Service Install from the Cloud Pak for Data installation page Install by using the CLI 

 [Analytics Engine Powered by Apache Spark](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-welcome/spark.html) ✓ ✓ 
 [Cognos Analytics](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-welcome/ca.html) ✓ 
 [Cognos Dashboards](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-welcome/cde.html) ✓ ✓ 
 [Data Refinery](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-welcome/dr.html) See Watson Knowledge Catalog or Watson Studio See Watson Knowledge Catalog or Watson Studio 
 [DataStage](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-welcome/ds.html) ✓ 
 [Db2 Big SQL](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-welcome/bigsql.html) ✓ 
 [Db2 Data Gate](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-welcome/dg.html) ✓ ✓ 
 [Db2 Data Management Console](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-welcome/dmc.html) ✓ ✓ 
 [Db2 Warehouse](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-welcome/db2wh.html) ✓ ✓ 
 [Db2 ](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-welcome/db2oltp.html) ✓
SAClient_600.tgz gateway installation.log
config install_client.sh safenet
6. Navigate to the /var/safenet/config/ directoy and execute the safenet_config script:

root@IBMADC690867-s6dr cd /var/safenet/config/
root@IBMADC690867-s6dr pwd
/var/safenet/config

root@IBMADC690867-s6dr sh safenet_config
7. Verify that /etc/Chrystoki.conf and the symbolic link /usr/lib/libCrystoki_64 were created:

root@IBMADC690867-s6dr ls -l /etc/Chrystoki.conf
-rw-r--r-- 1 root wheel 1185 Jul 26 16:17 /etc/Chrystoki.conf
root@IBMADC690867-s6dr ls -l /usr/lib/libCryptoki2_64.so
lrwxr-xr-x 1 root wheel 54 Jul 26 16:17 /usr/lib/libCryptoki2_64.so ->
/var/safenet/safenet/lunaclient/lib/libCryptoki2_64.so



The IBM Hardware Security Module has been installed successfully.
See the latest installation guides and support notes from SAP for an up-to-date list of these prerequisites. Currently, the following extra packages are required for an SAP NetWeaver installation: - compat-sap-c++-7: Achieves compatibility of the C++ runtime with the compilers that are used by SAP - uuidd: Maintains OS support for the creation of UUIDs - csh: C shell support for the OS



1. Follow [SAP note 2195019](https://launchpad.support.sap.com//notes/2195019) and install package compat-sap-c++-7. Create a specific soft-link, which is required by the SAP binary files.

[root@sap-app-vsi ] yum install compat-sap-c++-7
...

[root@sap-app-vsi tmp] mkdir -p /usr/sap/lib
[root@sap-app-vsi tmp] ln -s /opt/rh/SAP/lib64/compat-sap-c++-7.so /usr/sap/lib/libstdc++.so.6
2. Check if uuid daemon (uuidd) is installed. If it’s not, install and start it.

[root@sap-app-vsi ] rpm -qa | grep uuidd
[root@sap-app-vsi ] yum install uuidd
[root@sap-app-vsi ] systemctl enable uuidd
[root@sap-app-vsi ] systemctl start uuidd
3. Install the tcsh package required for C shell support

[root@sap-app-vsi ] yum install tcsh







 Installing the IBM Cloud Metrics Collector for SAP 

SAP requires the installation of the IBM Cloud Metrics Collector for SAP to analyze your infrastructure if a support case is submitted.
* [SAP Commerce (on-premises) Installation and Upgrades](https://help.sap.com/viewer/a74589c3a81a4a95bf51d87258c0ab15/2005/en-US/8bf5a611866910149242e1a3a41eb9af.html)
* [SAP Commerce (on-premises) Architecture options are Single Node, Cluster Node, and Multi-Tenant Node](https://help.sap.com/viewer/b490bb4e85bc42a7aa09d513d0bcb18e/1905/en-US/8b5588d8866910149d4eb5f99c75b6b4.html)



For a typical development environment of SAP Commerce, it is straightforward (compared to other SAP software) to shut down the instantiation/s and reduce costs outside of business hours through less Cloud resource consumption; however, depending on the implementation the time to start again can be significant. This decision is required by the project team, and might not be suitable if a worldwide development team is in-place.

More information is available on [cxwiki.sap.com](https://cxwiki.sap.com) and [sap.com/cxworks](https://www.sap.com/cxworks).

IBM Power Systems Virtual Servers are not available for SAP Commerce
Installing ClamAV 

Use this procedure to install ClamAV.



1.  Log in to WHM on https://x.x.x.x:2087 (replace x.x.x.x with your server IP)
2.  Click the cPanel icon.
3.  Click the Manage plug-ins icon to view the list of cPanel plug-ins.
4.  On the Add-on modules page, locate clamavconnector. Enable Install and keep updated and click Save.



The installation takes around twenty minutes to complete.



  Notes on ClamAV 

The lib version checking is disabled by default. However, the server has zlib 1.2.2 or greater installed.

Licensing is the most common reason that the ClamAV installation fails. The clamav add-on is free, but you need to register as a professional license. For more information, see [https://www.clamav.net/](https://www.clamav.net/). After correctly registering your license, return to step 4, uninstall, and reinstall clamavconnector.
The default value of 400 offers a reasonable balance for most customers and maintains real-time synthesis. For information about modifying this value to suit your needs, contact IBM Support.

New support for neural voices
: All neural voices that are currently available for Text to Speech for IBM Cloud are now also available for installation on Text to Speech for IBM Cloud Pak for Data. The following languages and voices are now available:



* Arabic:ar-MS_OmarVoice
* Chinese (Mandarin):zh-CN_LiNaVoice, zh-CN_WangWeiVoice, and zh-CN_ZhangJingVoice
* Dutch (Belgian):nl-BE_AdeleVoice
* Dutch (Netherlands):nl-NL_EmmaVoice and nl-NL_LiamVoice
* English (Australian):en-AU_CraigVoice, en-AU_MadisonVoice, and en-AU_SteveVoice
* Korean:ko-KR_HyunjunVoice, ko-KR_SiWooVoice, ko-KR_YoungmiVoice, and ko-KR_YunaVoice
* Swedish:sv-SE_IngridVoice



For more information about all available languages and voices, see [Languages and voices](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-voices).

Installing voices
: You can install either the enhanced neural voices or the neural voices. You can install only one of the two types of voices. When you install the service, you use the voiceType property of the custom resource to indicate the voices that are to be installed:



* Specify enhancedNeuralVoices to install the enhanced neural voices. You must then specify the individual enhanced neural voices that are to be installed. By default, only en-US_AllisonV3Voice, en-US_LisaV3Voice, and en-US_MichaelV3Voice are installed. You can choose to install these default voices, these and other voices, or just other voices. Only the voices that you install are available.
* Specify neuralVoices to install the neural voices. All of the neural voices are installed and available.
Run the following command to install the private worker by using the specific container registry: kubectl apply –filename updated_deployment.yaml.
6. Continue the [installation](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workers&interface=ui).



* How do I provision and update the private worker installation file for IBM Cloud® Private?

If your pipeline worker is installed on IBM Cloud Private, you can use the following script to provision and update the private worker installation file.

#!/bin/bash
region=${region:-"us-south"}
target_cr="mycluster.icp:8500"
install_filename="updated-private-worker-install.yaml"
curl -o $install_filename
https://private-worker-service.$region.devops.cloud.ibm.com/install
cat $install_filename | grep -e
'gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd' -e 'image:' \
| sed 's/- gcr.io/gcr.io/g' \
| sed 's/- image: gcr.io/gcr.io/g' \
| sed 's/image: gcr.io/gcr.io/g' \
| sed 's/image://g' \
| awk '{$1=$1;print}' \
| while read -r image ; do

echo "Processing $image"
docker pull $image
new_image_tag=$image
 if $image only have a single slash it is coming from dockerhub
number_of_slashes=$(echo $image | tr -cd '/' | wc -c)
if [ "$number_of_slashes" == "1" ]; then
new_image_tag="$target_cr/$image"
fi

 replace the sha id reference in the tag if any
* To install Watson OpenScale, set aiopenscale to true.
* To install Cognos Dashboards, set cde to true.
* To install Db2 Data Gate, set datagate to true.
* To install Db2 Warehouse, set db2wh to true.
* To install Db2 Data Management Console, set dmc to true.
* To install RStudio Server, set rstudio to true.
* To install Apache Spark, set spark to true.
* To install Scheduling, set scheduler to true.
* To install Watson Knowledge Catalog, set wkc to true.
* To install Watson Machine Learning, set wml to true.
* To install Watson Machine Learning Accelerator, set wmla to true.
* To install Watson Query, set dv to true.
* To install Watson Studio, set wsl to true.



If you don't select any services to install in this step, only the IBM Cloud Pak for Data control plane will be installed.

If you want to install a service later, you can return to the Deployment values section and set the appropriate parameter to true or you can select a service from the IBM Cloud Pak for Data Services catalog and follow the installation instructions for the service.

For more information, see [Installing IBM Cloud Pak for Data](https://www.ibm.com/docs/SSQNUZ_4.6.x/cpd/install/install.html).





 Step 6. Install IBM Cloud Pak for Data 



1. Ensure that you have assigned a license for IBM Cloud Pak for Data to the deployment.
2. Confirm that you have read and agree to the license agreements.
3. Click Install.



The IBM Cloud Pak® for Data automated installation makes the following changes to ensure that services can be installed successfully:



* Sets kernel parameters. For more information, see [Kernel parameter settings](https://www.ibm.com/docs/SSQNUZ_4.6.x/cpd/install/prep-cluster-node-kernel.html).
* Enables noroot squash on worker nodes for Network File System (NFS).
dd63d43987e3: Pull complete
a098dba94337: Pull complete
Digest: sha256:df316f5ed26cbec1bc1ad7a6f6d2c978f767408080a4a4db954c94c91e8271e5
Status: Downloaded newer image for ibmterraform/terraform-provider-ibm-docker:latest
2. Create a container from your image and log in to your container. When the container is created, Terraform on IBM Cloud and the IBM Cloud Provider plug-in are automatically installed and you are automatically logged in to the container. The working directory is set to /go/bin.

docker run -it ibmterraform/terraform-provider-ibm-docker:latest



2. From within your container, set up the IBM Terraform on IBM Cloud OpenShift Project.



1. Install OpenSSH inside the container that you created in the previous step.

apk add --no-cache openssh

Example output:

fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/community/x86_64/APKINDEX.tar.gz
(1/6) Installing openssh-keygen (7.5_p1-r9)
(2/6) Installing openssh-client (7.5_p1-r9)
(3/6) Installing openssh-sftp-server (7.5_p1-r9)
(4/6) Installing openssh-server-common (7.5_p1-r9)
(5/6) Installing openssh-server (7.5_p1-r9)
(6/6) Installing openssh (7.5_p1-r9)
Executing busybox-1.27.2-r11.trigger
OK: 326 MiB in 50 packages
Locating the Installation Dialog parameters {: rhos-find-parameters}

During installation of SAP Data Hub, you're prompted to:

Enable Vora checkpoint store? (yes/no).

If you're setting up a test environment, you can select yes or no. However, for a production environment, select yes. You're next asked for the following parameters:

 {: screen}
Please provide the following parameters for Vora's checkpoint store
Please enter type of shared storage (oss/s3/wasb/gcs/webhdfs):
Please enter S3 access key:
Please enter S3 secret access key:
Please enter S3 host (empty for default 'https://s3.amazonaws.com'):
Please enter S3 region you want to connect to (empty for default 'us-east-1'):
Please enter connection timeout in seconds (empty for default 180):
Please enter S3 bucket and directory (in the form my-bucket/directory):
Do you want to validate the checkpoint store? (yes/no)
Show more



1. Select s3 for type of shared storage. You can take advantage of Object Storage's compatibility with the S3 API.
2. Enter the access_key_id from the generation of the service credentials for the S3 access key.
3. Enter the secret_access_key from the generation of the service credentials for the S3 secret access key.
4. Use [Endpoints and storage locations](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpoints) to find the S3 Host that matches the location where your bucket's created. In the example, it's s3.eu-de.cloud-object-storage.appdomain.cloud. Leave S3 region blank. It's taken from the endpoint's URL, for example, eu-de.

In a production environment, you should use the private endpoint.
5. Leave connection timeout in second blank.