vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Download and install git from [https://github.com/git-for-windows/git/releases/latest](https://github.com/git-for-windows/git/releases/latest).
2. Verify the installation with:

git --version



Proceed to the configuration [common to all operating systems](https://cloud.ibm.com/docs/solution-tutorialsgetting-started-common).







 Apple macOS 

The following sections assume you are running macOS High Sierra or later under a user with Administrator privileges. Once you're done with the specific sections, proceed to the configuration [common to all operating systems](https://cloud.ibm.com/docs/solution-tutorialsgetting-started-common).



 IBM Cloud CLI 



1. Download and install the IBM Cloud CLI from [https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/latest](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/latest).
2. Verify the installation with:

ibmcloud version







 Docker 



1. Docker Desktop on Mac is one option to run container images on macOS. Make sure to review the terms of the [license agreement](https://docs.docker.com/subscription/docker-desktop-license-agreement) before proceeding with the installation. Other options include [Podman](https://podman.io/get-started).
2. If you don't have one, sign up for a free account at [https://hub.docker.com/signup](https://hub.docker.com/signup).
3. Download and install Docker Desktop on Mac from [https://docs.docker.com/docker-for-mac/install/](https://docs.docker.com/docker-for-mac/install/).
4. Verify the installation with:
* [SAP HANA Hardware and Software Requirements](https://help.sap.com/viewer/eb3777d5495d46c5b2fa773206bbfb46/2.0.01/en-US/d3d1cf20bb5710149b57fd794c827a4e.html)



SAP HANA support on SAP-certified Cloud IaaS:



* [Certified and Supported SAP HANA Hardware – Ceritified IaaS Platforms](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas;ve:28)



SAP HANA and SAP NetWeaver on UNIX/Linux:



* [Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on UNIX: SAP HANA Database](https://help.sap.com/viewer/910828cec5d14d6685da380aec1dc4ae/CURRENT_VERSION/en-US/9420dabb130e4ae1996b3f39e202cc6e.html)
* [Installation of SAP Systems Based on the Application Server Java of SAP NetWeaver 7.5 and SAP Solution Manager 7.2 SR2 Java on UNIX: SAP HANA Database](https://help.sap.com/viewer/3aa4caa3bd634a22bdc572d82d1311ec/CURRENT_VERSION/en-US/9420dabb130e4ae1996b3f39e202cc6e.html)
* [Installation of SAP ABAP S/4HANA and BW/4HANA Systems on UNIX: SAP HANA 2.0 Database](https://help.sap.com/viewer/39c32e9783f6439e871410848f61544c/CURRENT_VERSION_SWPM20/en-US/1937febc57ad4d81a213fca9b3e031a5.html)



HANA and SAP NetWeaver on Windows:
DB-HOSTNAME = "sapbw4db"
DB-PROFILE = "mx2-16x128"
DB-IMAGE = "ibm-redhat-7-6-amd64-sap-hana-1" For any manual change in the terraform code, you have to make sure that you use a certified image based on the SAP Note: 2927211.

 SAP APPs VSI variables:
APP-HOSTNAME = "sapbw4app"
APP-PROFILE = "bx2-4x16"
APP-IMAGE = "ibm-redhat-7-6-amd64-sap-applications-1" For any manual change in the terraform code, you have to make sure that you use a certified image based on the SAP Note: 2927211.

The hostname must have up to 13 characters as required by SAP. For more information about the rules that apply to hostnames for SAP systems, see SAP Note 611361 - Hostnames of SAP ABAP Platform servers
5. In the same file (input.auto.tfvars), edit the SAP system configuration variables that are passed to the Ansible automated deployment.

SAP HANA DB configuration
hana_sid = "BWH"
hana_sysno = "00"
hana_system_usage = "custom"
hana_components = "server"

SAP HANA Installation kit path
kit_saphana_file = "/storage/HANADB/51054623.ZIP"

SAP system configuration
sap_sid = "BWH"
sap_ascs_instance_number = "01"
sap_ci_instance_number = "00"

 Number of concurrent jobs used to load and/or extract archives to HANA Host
hdb_concurrent_jobs = "6"

SAP BW4HANA APP Installation kit path
kit_sapcar_file = "/storage/BW4HANA/SAPCAR_1010-70006178.EXE"
kit_swpm_file = "/storage/BW4HANA/SWPM20SP09_4-80003424.SAR"
From the [IBM Cloud Portal > Classic Infrastructure](https://cloud.ibm.com/classic/devices/vmwarelicenses)
2. Click Devices > Managed > VMware Licenses > Order VMware licenses.
3. Click the drop-down list under Order VMware License. to list the VMware products and number of CPUs for the licenses that you want to order.
4. List of the VMware products and number of CPUs for the licenses that you want to order. Select NSX Data Center SP Advanced .
5. Click Continue to order the licenses or you can click Add License to add more licenses.
6. After you click Continue, you are taken back to the VMware Licenses page, which displays your VMware products and license keys.
7. Copy the VMware vCenter license key and can be added to the vCenter after the installation.







 Step 1: Review NSX-T installation requirements 

Before you start the actual NSX-T deployment, review the following requirements:



1. Review [VMware Solution Architectures for IBM Cloud VPC](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-nsx-t) for naming and architectural considerations.
2. Review the NSX Manager installation requirements. See [NSX Manager Installation](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/installation/GUID-A65FE3DD-C4F1-47EC-B952-DEDF1A3DD0CF.htmlGUID-A65FE3DD-C4F1-47EC-B952-DEDF1A3DD0CF).
3. Review and configure the necessary ports and protocols in security groups (if detailed rules are applied).
* [Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.52 on UNIX/Linux: SAP Adaptive Server Enterprise](https://help.sap.com/viewer/e345db692e3c43928199d701df58c0d8/CURRENT_VERSION/en-US)
* [Installation of SAP Systems Based on the Application Server Java of SAP NetWeaver 7.3 to 7.5 on UNIX/Linux: SAP Adaptive Server Enterprise](https://help.sap.com/viewer/01f04921ac57452983980fe83a3ce10d/CURRENT_VERSION/en-US)



SAP ASE and SAP NetWeaver on Windows:



* [Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 to 7.52 on Windows: SAP Adaptive Server Enterprise](https://help.sap.com/viewer/b0c437ae5d1a4c70847bb55973923352/CURRENT_VERSION/en-US)
* [Installation of SAP Systems Based on the Application Server Java of SAP NetWeaver 7.3 to 7.5 on Windows: SAP Adaptive Server Enterprise](https://help.sap.com/viewer/2b04bc65d45544bb8ba67c258d4fb2e2/CURRENT_VERSION/en-US)







 SAP ASE using Intel Virtual Servers 

See [SAP Note 2927211 - SAP Applications on IBM Cloud Virtual Private Cloud (VPC) Infrastructure environment](https://launchpad.support.sap.com//notes/2927211) for supported SAP ASE database versions.





 SAP ASE using IBM Power Virtual Servers 

This is a complementary offering from IBM Power Systems, with low latency access to IBM Cloud services

See [SAP Note 2855850 - SAP Applications on IBM Power Virtual Servers](https://launchpad.support.sap.com//notes/2855850) for supported SAP ASE database versions on AIX running on IBM Power Systems Virtual Servers.
In the Tag field, enter the name of the cluster where you want to install PX-Backup. After you complete the installation, you can't see the name of the cluster where you installed PX-Backup. To find the cluster more easily later, make sure that you enter the cluster name and any additional information as tags.
6. Enter your IBM Cloud API key. After you enter the API key, the Kubernetes or OpenShift cluster name field appears. If you don't have an IBM Cloud API key, see [Creating an API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key) to create one.
7. In the Kubernetes or OpenShift cluster name field, select the cluster where you want to install PX-Backup.
8. Enter the name of the Red Hat OpenShift project where you want to install your PX-Backup service components. Do not use the kube-system or default namespace. If the Red Hat OpenShift project that you enter does not already exist in your cluster, it is automatically created during the installation.
9. Select an existing storage class in your cluster to provision persistent volumes for the PX-Backup service. The service uses this storage to store service metadata and is not used to back up your apps and data. [Your apps and data are backed up to an IBM Cloud Object Storage service instance](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_backuppx-backup-storage).
10. Click Create to begin the PX-Backup installation. The installation may take a few minutes to complete.
11. [Verify that your PX-Backup service is installed correctly](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_backuppx-backup-verify).







 Verifying your PX-Backup installation 

Verify that PX-Backup is correctly installed on your cluster.

From the console



1.
* IBM Cloud Pak for Multicloud Management Version 2.1.0 to Version 2.1.5
* IBM Cloud Pak for Multicloud Management Version 2.3.2 to Version 2.3.21







 Minimum hardware requirements 



 Worker Nodes CPU (Cores/Node) Memory (GB/Node) 

 Worker 4+ 16 32 







 Minimum storage requirements 

Mandatory: 240GB of persistent storage.





 Procedure 



 Step 1. Configure your installation environment 

From the Create tab on the Cloud Pak for Multicloud Management installation page in the IBM Catalog on IBM Cloud, specify where you want to install IBM Cloud Pak for Multicloud Management:

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





 Step 2. Configure your workspace 

Specify how to track and manage your installation from your IBM Cloud Schematics workspace:

1. In the Configure your workspace section, update the name and tag of the installation workspace.
2. Specify any tags that you want to use for the installation. Specify multiple tags as a comma-separated list.





 Step 3. Optional: Create Red Hat Advanced Cluster Management Pull Secret 

If you plan to import Kubernetes clusters that were not created by OpenShift Container Platform or Red Hat Advanced Cluster Management, you must first generate a secret that contains your OpenShift Container Platform pull secret information to access the entitled content from the distribution registry.

1. Using a CLI that has access to your cluster, create the open-cluster-management namespace by running the following command: oc create namespace open-cluster-management
2. Download your Openshift Container Platform pull secret file from https://cloud.redhat.com/openshift/install/pull-secret by selecting Download pull secret; save the pull secret to a filepath you have read and write access to, like /root/rhacm-pull-secret.
3.
It must be image-registry.openshift-image-registry.svc:5000/{namespace}, where {namespace} is the namespace in which IBM Cloud Pak® for Data is installed, normally zen.





 9 April 2021 (Version 1.2.1) 

Support for modifying installed models and voices
: The Speech services let you add or remove installed models and voices for version 1.2 or 1.2.1 of the services.





 Version 1.2.1 (26 March 2021) 

Version 1.2.1 is available
: Speech to Text for IBM Cloud Pak for Data version 1.2.1 is now available. Versions 1.2 and 1.2.1 use the same version 1.2 documentation and installation instructions. Version 1.2.1 supports installation on Red Hat OpenShift version 4.6 in addition to versions 4.5 and 3.11.

New installation instructions
: For both clusters connected to the internet and air-gapped clusters, the installation instructions include the following steps:



* Use the oc label command to set up required labels for the namespace where IBM Cloud Pak for Data is installed.
* Use the oc project command to ensure that you are pointing at the correct OpenShift project.
* Use the cpd-cli install command to install an Enterprise DB PostgreSQL server that is used by the Speech services.



You perform these steps before you install the Speech services.

New uninstallation instructions
: A step was added to the procedure for uninstalling the Speech services to clean up all of the resources from the installation.

Entitled registry for PostgreSQL datastore
: The entitled registry path from which the service pulls images for the PostgreSQL datastore has changed. The registry location changed from cp.icr.io/cp/watson-speech to cp.icr.io/cp/cpd. This change is transparent to users.

Secrets for Minio and PostgreSQL datastores
: The Minio and PostgreSQL datastores require the following hard-coded values for their secrets:



* For Minio, use minio.
It must be image-registry.openshift-image-registry.svc:5000/{namespace}, where {namespace} is the namespace in which IBM Cloud Pak® for Data is installed, normally zen.





 9 April 2021 (Version 1.2.1) 

Support for modifying installed models and voices
: The Speech services let you add or remove installed models and voices for version 1.2 or 1.2.1 of the services.





 26 March 2021 (Version 1.2.1) 

Version 1.2.1 is available
: Text to Speech for IBM Cloud Pak for Data version 1.2.1 is now available. Versions 1.2 and 1.2.1 use the same version 1.2 documentation and installation instructions. Version 1.2.1 supports installation on Red Hat OpenShift version 4.6 in addition to versions 4.5 and 3.11.

New installation instructions
: For both clusters connected to the internet and air-gapped clusters, the installation instructions include the following steps:



* Use the oc label command to set up required labels for the namespace where IBM Cloud Pak for Data is installed.
* Use the oc project command to ensure that you are pointing at the correct OpenShift project.
* Use the cpd-cli install command to install an Enterprise DB PostgreSQL server that is used by the Speech services.



You perform these steps before you install the Speech services.

New uninstallation instructions
: A step was added to the procedure for uninstalling the Speech services to clean up all of the resources from the installation.

Entitled registry for PostgreSQL datastore
: The entitled registry path from which the service pulls images for the PostgreSQL datastore has changed. The registry location changed from cp.icr.io/cp/watson-speech to cp.icr.io/cp/cpd. This change is transparent to users.

Secrets for Minio and PostgreSQL datastores
: The Minio and PostgreSQL datastores require the following hard-coded values for their secrets:



* For Minio, use minio.
To find the cluster more easily later, make sure that you enter the cluster name and any additional information as tags.
6. Enter your IBM Cloud API key. After you enter the API key, the Kubernetes or OpenShift cluster name field appears. If you don't have an IBM Cloud API key, see [Creating an API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key) to create one.
7. In the Kubernetes or OpenShift cluster name field, select the cluster where you want to install PX-Backup.
8. Enter the name of the Kubernetes namespace where you want to install your PX-Backup service components. Do not use the kube-system or default namespace. If the Kubernetes namespace that you enter does not already exist in your cluster, it is automatically created during the installation.
9. Select an existing storage class in your cluster to provision persistent volumes for the PX-Backup service. The service uses this storage to store service metadata and is not used to back up your apps and data. [Your apps and data are backed up to an IBM Cloud Object Storage service instance](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_backuppx-backup-storage).
10. Click Create to begin the PX-Backup installation. The installation may take a few minutes to complete.
11. [Verify that your PX-Backup service is installed correctly](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_backuppx-backup-verify).







 Verifying your PX-Backup installation 

Verify that PX-Backup is correctly installed on your cluster.

From the console



1. From the IBM Cloud [Resource list](https://cloud.ibm.com/resources), find the PX-Backup service that you created.
2. Review the Status column to see if the installation succeeded or failed. The status might take a few minutes to update.
Learn about the Oracle plug-in 

The Oracle plug-in is an add-on and is installed with the Backup Agent on the Oracle Database host. Through the Cloud Backup Portal, you can configure jobs, back up Oracle Databases to a secure, remote vault, and restore Oracle Databases. The Oracle plug-in integrates into the existing architecture.



 Capabilities provided 



* Support for Oracle Database backup and recovery.
* The Oracle plug-in provides ARCHIVELOG-based, non-RMAN backups of whole online database instances. All nontemporary table spaces and instance parameter files are automatically backed up. Oracle Corporation recommends that backups take place in periods of low database activity.
* Full and partial databases are restored through normal user-managed Oracle recovery mechanisms.







 Limitations 



* Only local, single-instance, disk-based databases are backed up.
* Database clusters are not backed up.
* Raw devices are not backed up.
* Remote databases are not backed up.
* The database must run in ARCHIVELOG mode, and the user under which the backup is configured must have SYSDBA privileges.
* Database passwords are encrypted for enhanced security over script-based methods.







 Installing the plug-in for Windows 

The Oracle plug-in is installed with the 32-bit or 64-bit Windows® Agent. To install the plug-in, run the Agent installation kit. The plug-in appears as an option on the Custom Setup page. For more information, see Installing the IBM Cloud Backup for Classic Client in Windows](/docs/Backup?topic=Backup-InstallinWindows).

Before you install the plug-in, stop both IBM Cloud Backup for Classic services in services.msc.



1. Run the Agent installation package.
2. At the language screen, click OK.
3. At the welcome screen, click Next.
4. Select the Modify installation, and click Next.
5. Select the Leave Unchanged, and click Next.
6. At the custom setup screen, select each plug-in that you purchased, and select This feature will be installed on ..., then click Next.
7.
Make sure that External is selected and click Add.



Continue entering information into the remaining fields:



* Name The name that is associated with this network device. For this example, for the example, use Private to indicate that this device is connected to the IBM Cloud private network.
* Connection type Select the device that corresponds to your private network. This name is the device name that you found earlier in the Network Connections window. After you select the correct device, click OK. You are presented with a warning that your network connection might be lost, click Yes to continue.







 Configuring a public network device 

Your Private Network device is now installed. Repeat the preceding steps for the Public network. For this example, use the name Public for the device name. Under connection type, select the other network device that was not used in the Private network setup. After you create both the public and private network devices, click OK.







 Obtaining installation media 

Now that the virtual network devices are created, you need to obtain the installation media. The installation media that is used in this example is a CD/DVD image file. IBM Cloud supports the following Operating Systems for Hyper-V:



* Windows 2019 with Hyper-V
* Windows 2016 with Hyper-V
* Windows 2012R2 with Hyper-V
* Windows 2012 with Hyper-V
* CentOS
* Fedora
* Ubuntu Note: If you already have the installation media, go to Creating a Virtual Machine.



The installation media for [CentOS ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](http://centos.org), [Fedora ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](http://fedoraproject.org/), and [Ubuntu !
Using the filter in the Alarm Name column, filter on Switch.<br>3. Select Sphere Distributed Switch MTU supported status and select Disable.<br>4. Select vSphere Distributed Switch VLAN trunked status and select Disable.<br><br><br> 







 Related links 



* [VMware vSphere documentation](https://docs.vmware.com/en/VMware-vSphere/index.html)
* [NSX installation guide](https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.install.doc/GUID-DD31D6BC-2E56-4E91-B45F-FCA3E80FF786.html)
* [NSX administration guide](https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.admin.doc/GUID-B5C70003-8194-4EC3-AB36-54C848508818.html)
* [VMware vSAN administration guide](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.virtualsan.doc/GUID-AEF15062-1ED9-4E2B-BA12-A5CE0932B976.html)
* [Considerations about changing vCenter Server artifacts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcenter_chg_impactvcenter_chg_impact)
Run the following commands to start NGINX.

systemctl enable nginx
systemctl start nginx
9. The Linux firewall needs to configured to enable HTTP by using the following firewall-cmd commands:

firewall-cmd --permanent --zone=public --add-service=http
firewall-cmd --reload







 Generating an SSH private key and add it to the agent 

For the Red Hat OpenShift container platform clusters on which you want to perform installation debugging or disaster recovery, you must provide an SSH key that your ssh-agent process uses to the installer.

You can use this key to SSH into the nodes as the user core. When you deploy the cluster, the key is added to the core user’s /.ssh/authorized_keys list.

You must use a local key.



 Creating the SSH key 



1. In the SSH session on the bastion node, run the following command, which generates a public or private rsa key pair in the directory /root/.ssh.

ssh-keygen -f /.ssh/id_rsa -t rsa -b 4096 -N ''

The private key is /root/.ssh/id_rsa and the public key is /root/.ssh/id_rsa.pub.
2. Start the ssh-agent process as a background task:

eval "$(ssh-agent -s)"
3. Add your SSH private key to the ssh-agent:

ssh-add /root/.ssh/id_rsa









 Downloading the installation tools 

For more information about installing Red Hat OpenShift 4.7, see [Installing a cluster on vSphere with user-provisioned infrastructure](https://docs.openshift.com/container-platform/4.7/installing/installing_vsphere/installing-vsphere.html).
If you don't have one, sign up for a free account at [https://hub.docker.com/signup](https://hub.docker.com/signup).
3. Download and install Docker Desktop on Mac from [https://docs.docker.com/docker-for-mac/install/](https://docs.docker.com/docker-for-mac/install/).
4. Verify the installation with:

docker --version
docker run hello-world







 kubectl 



1. Download kubectl from

[https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl-on-macos](https://kubernetes.io/docs/tasks/tools/install-kubectl/install-kubectl-on-macos).
2. Make the kubectl binary executable.

chmod +x ./kubectl
3. Move the binary to your PATH.

sudo mv ./kubectl /usr/local/bin/kubectl
4. Verify the installation with:

kubectl version --client=true







 oc 



1. Download the latest 4.x OpenShift CLI (oc) from [https://mirror.openshift.com/pub/openshift-v4/clients/ocp/stable/](https://mirror.openshift.com/pub/openshift-v4/clients/ocp/stable/).
2. Extract openshift-client-mac.tar.gz:

tar zxvf openshift-client-mac.tar.gz oc
3. Move the oc binary to your PATH.

sudo mv ./oc /usr/local/bin/oc
4. Verify the installation with:

oc version