vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Make sure that you [copied the image pull secrets from the default to the kube-system project](https://cloud.ibm.com/docs/openshift?topic=openshift-registrycopy_imagePullSecret) so that you can pull images from Container Registry. Make sure that you [add the image pull secrets to the Kubernetes service account](https://cloud.ibm.com/docs/openshift?topic=openshift-registrystore_imagePullSecret) of the kube-system project.
* Decide if you want to include your cluster in a Portworx disaster recovery configuration. For more information, see [Setting up disaster recovery with Portworx](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_recovery).
* If you attached a separate device for the Portworx journal, make sure that you retrieve the device path by running lsblk while logged into your worker node.
* If you attached a separate devices for the Portworx KVDB, make sure that you retrieve the device path by running lsblk while logged into your worker node.
* [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



To install Portworx:



1. Open the Portworx service from the [IBM Cloud catalog](https://cloud.ibm.com/catalog/services/portworx-enterprise) and complete the fields as follows:



1. Select the region where your Red Hat OpenShift on IBM Cloud cluster is located.
2. Review the Portworx pricing information.
3. Enter a name for your Portworx service instance.
4. Select the resource group that your cluster is in.
5. In the Tag field, enter the name of the cluster where you want to install Portworx. After you create the Portworx service instance, you can't see the cluster that you installed Portworx into.
If you prefer to install Portieris directly, or you aren't using IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud, see [Installing Portieris](https://github.com/IBM/portierisinstalling-portieris).





 Portieris policies 

Portieris has two types of policy. Image policy resources and cluster image policy resources. You can override the default Portieris policies.

For more information about Portieris policies, see [Portieris policies](https://github.com/IBM/portieris/blob/main/POLICIES.md).





 Uninstalling Portieris 

How to uninstall Portieris.

[Uninstall Portieris](https://github.com/IBM/portierisuninstalling-portieris).
* It can be installed as a VM in Hypervisors such as VMware, HyperV, Xen and KVM.
* It can be installed inside Power Systems Virtual Server as an LPAR.







 Migration Services 

Services to assist in migration are available from IBM, FalconStor, and Authorized Migration Partners. Please reach out if you would like more information about using migration services or becoming a FalconStor Migration Partner at [PowerVSMigration@falconstor.com](mailto:PowerVSMigration@falconstor.com).

If you need any help with deploying FalconStor StorSafe VTL, see [FalconStor VTL for IBM Deployment Guide](https://falconstor-download.s3.us-east.cloud-object-storage.appdomain.cloud/FalconStor%20VTL%20for%20IBM%20Deployment%20Guide.pdf).

For more information on FalconStor StorSafe VTL, see [www.falconstor.com](https://www.falconstor.com/).









 IBM teams and managed services 

You can engage IBM teams and services to assist you throughout the migration lifecycle.



* [IBM Systems Lab Services](https://www.ibm.com/it-infrastructure/services/lab-services)
* [IBM Services for Cloud Migration](https://www.ibm.com/services/cloud/migration)







 AIX migration strategies 

Learn about migration strategies that are specific to AIX systems.



 Migration by using MKSYSB 

You can migrate your data by using the mksysb command:



1. Back up the on-premises OS with the alt_disk_mksysb command and transfer it to COS.
2. Create a Power Systems Virtual Server and import the image.
3. Restore the on-premises image.



For more information, see [Restoring an AIX mksysb image onto a Power Systems Virtual Server instance](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-restoring-aix-mksysb-image).





 Logical replication with GLVM and PowerHA SystemMirror for AIX Enterprise Edition
* [Installing on Mac OS X](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-dr_pkginstall_dr_pkg_mac)
* [Installing on Windows](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-dr_pkginstall_dr_pkg_windows)





 Installing the driver package on Linux or PowerLinux 

You can install the Db2 Warehouse on Cloud driver package on Linux or PowerLinux by using installDSDriver.



 Prerequisites 

Before attempting to connect to your Db2 Warehouse on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-connect_ovprereqs).

On PowerLinux only, complete the following steps to install the XL C/C++ compiler runtime package:



1. Download the XL C/C++ compiler runtime package from the FTP site. For example, to use the wget tool to download the runtime package for Linux little endian Ubuntu 14, issue the following command:

wget ftp://public.dhe.ibm.com/software/server/POWER/Linux/rte/xlcpp/le/ubuntu/dists/trusty/main/binary-ppc64el/
2. Install the runtime package by issuing the following command:

sudo dpkg -iG .deb







 Procedure 



1. Decompress the compressed driver package file that you downloaded earlier.

Example:

gunzip file_name.tar.gz

tar -xvf file_name.tar

A dsdriver subdirectory is created in the directory where you ran the decompression commands.
2. Extract the Java and ODBC/CLI drivers.

a. In the dsdriver subdirectory, run the installDSDriver command.
For more information, see [IBM Wazi as a Service documentation](https://www.ibm.com/docs/en/wazi-aas/1.0.0).

IBM Wazi Image Builder is licensed only for development, testing, employee education, or demonstration of your applications that run on z/OS. This product must not be used for production workloads of any kind, nor robust development workloads, production module builds, preproduction testing, stress testing, or performance testing.

For details about getting IBM Wazi Image Builder license keys and activation kits, go to the [IBM Support Licensing](https://www.ibm.com/support/pages/ibm-support-licensing-start-page) page. To download the software, follow the instructions on [IBM Passport Advantage®](https://www.ibm.com/software/passportadvantage/).

For details about installing, configuring, and using IBM Wazi Image Builder, see [Bringing your own image with Wazi Image Builder](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=bringing-your-own-image-wazi-image-builder).
Verify that the ibm-ocs-operator-controller-manager- pod is running in the kube-system namespace.

oc get pods -A | grep ibm-ocs-operator-controller-manager
7. If you enabled the add-on and set the odfDeploy=false option, follow the steps to [create an ODF custom resource](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicocs-classic-deploy-crd).







 Installing the OpenShift Data Foundation add-on from the console 

To install ODF in your cluster, complete the following steps.

Version 4.11 is currently available for new clusters only. You can't upgrade a 4.10 deployment to 4.11. However, you can continue using ODF version 4.10.



1. Before you enable the add-on, review the [change log](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog) for the latest version information. Note that the add-on supports n+1 cluster versions.
2. [Review the parameter reference](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicodf-classic-param-ref).
3. From the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), select the cluster where you want to install the add-on.
4. On the cluster Overview page, on the OpenShift Data Foundation card, click Install. The Install ODF panel opens.
5. In the Install ODF panel, enter the configuration parameters that you want to use for your ODF deployment.
6. Select either Essentials or Advanced as your billing plan.
7. For classic clusters, select Local storage to use local volumes on the worker nodes.
8.
Download terraform from [https://www.terraform.io/downloads.html](https://www.terraform.io/downloads.html).
2. Uncompress the downloaded archive.
3. Move the terraform binary to your PATH.

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

terraform version



To manage IBM Cloud resources with Terraform, you also need to install the IBM Cloud Provider. Starting with Terraform 0.13, the provider can be automatically downloaded from Terraform plugin registry. Follow the instructions in the [provider documentation](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cliinstall-provider-v13) to configure the required_providers property in your Terraform templates.





 jq 



1. Download jq from [https://stedolan.github.io/jq/](https://stedolan.github.io/jq/).
2. Rename the downloaded file to jq.
3. Move the jq binary to your PATH.

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

jq --version







 Git 



1. Check that git is installed:

git --version

macOS may prompt you to install the developer tools. These tools include the git command line.



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







 Ubuntu Linux 

The following sections assume you are running Ubuntu Linux as non-root user with access to root 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).
To install the Mount Helper and all the dependencies, use the following script.

./install.sh region=dal

The installation script accepts the command-line argument region. Example regions are dal, fra, lon, osa, sao, syd, tok, tor, wdc. This argument is used to copy region-specific root CA cert to the strongSwan certificates location. If no region is specified, then the utility copies all the root CA certs.
4. Update the configuration file /etc/ibmcloud/share.conf with region information and with the peer certificate expiration time that you want. By default, certificates last 1 hour and new certificates are fetched every 45 minutes. However, you can modify the certificate_duration_seconds option to have a value between 5 minutes and 1 hour.

certificate_duration_seconds = 600

This option is specified in seconds. The valid range for its value is 300 - 3600 seconds. The certificates are renewed when the current certs reach 70% of their lifetime.
5. If you want to renew the certs immediately with the new expiration time, then run the following command.

/sbin/mount.ibmshare -RENEW_CERTIFICATE_NOW







 Mounting a file share with the Mount Helper 



1. Run the mount command with the following syntax.

mount -t ibmshare -o secure=true <share-ip>:/<mount-point> /mnt/share-test

See the following example.

mount -t ibmshare -o secure=true 10.240.0.5:/acdaecff_a291_41bd_87c1_0dde05135d59 /mnt/nfs -v

The ibmshare in the command is a script that creates the certificate signing request(csr) and calls the Metadata service to get the intermediate cert and end peer certificate. It parses the mount command-line arguments and creates /etc/swanctl/conf.d/type_ibmshare_.conf. The strongSwan service uses this configuration file to establish the IPsec connection.
1. Download terraform from [https://www.terraform.io/downloads.html](https://www.terraform.io/downloads.html).
2. Uncompress the downloaded archive.
3. Move the terraform binary to your PATH.

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

terraform version



To manage IBM Cloud resources with Terraform, you also need to install the IBM Cloud Provider. Starting with Terraform 0.13, the provider can be automatically downloaded from Terraform plugin registry. Follow the instructions in the [provider documentation](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cliinstall-provider-v13) to configure the required_providers property in your Terraform templates.





 jq 



1. Download jq from [https://stedolan.github.io/jq/](https://stedolan.github.io/jq/).
2. Rename the downloaded file to jq.
3. Move the jq binary to your PATH.

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

jq --version







 Git 



1. Check that git is installed:

git --version

macOS may prompt you to install the developer tools. These tools include the git command line.



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







 Ubuntu Linux 

The following sections assume you are running Ubuntu Linux as non-root user with access to root privileges.
Uncompress the downloaded archive.
3. Move the terraform binary to your PATH.

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

terraform version



To manage IBM Cloud resources with Terraform, you also need to install the IBM Cloud Provider. Starting with Terraform 0.13, the provider can be automatically downloaded from Terraform plugin registry. Follow the instructions in the [provider documentation](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cliinstall-provider-v13) to configure the required_providers property in your Terraform templates.





 jq 



1. Install jq with:

sudo apt install jq
2. Verify the installation with:

jq --version







 Git 



1. Install git with:

sudo apt install git
2. Verify the installation with:

git --version



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







 Common to all operating systems 

The next sections are common to all operating systems.



 IBM Cloud CLI plugins 

Plugins extend the capabilities of the IBM Cloud CLI with commands specific to a service.



1. Install the following plugins:

ibmcloud plugin install container-registry
ibmcloud plugin install cloud-object-storage
ibmcloud plugin install kubernetes-service
ibmcloud plugin install vpc-infrastructure
ibmcloud plugin install code-engine

To see all the available plugins, run ibmcloud plugin repo-plugins and to install a plugin ibmcloud plugin install <PLUGIN_NAME>







 GitHub account 



1.
* [AIX](http://www-01.ibm.com/support/docview.wss?uid=swg21577384)
* [LINUX](http://www-01.ibm.com/support/docview.wss?uid=swg21631460)
* [WINDOWS](http://www-01.ibm.com/support/docview.wss?uid=swg21631462)



For more details, see [IBM Global Security Kit global installation instructions overview](https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.5.0/com.ibm.swg.tivoli.gskit.install.doc/doc/c0055521.html)
4. Set environment variable paths:



* AIX: LIBPATH/usr/opt/ibm/gsk8/lib
* Linux: LD_LIBRARY_PATH/usr/local/ibm/gsk8/lib
* UNIX: LD_LIBRARY_PATH/opt/ibm/gsk8/lib
* Windows: PATH<installation_directory>gsk8bin<installation_directory>gsk8lib (lib64 for GSKit 64-bit)
4.6.0 IBM Cloud Pak for Data 4.6.x [Installing 4.6.0](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-assistant/assistant-svc-install.html) 
 4.5.3 IBM Cloud Pak for Data 4.5.x [Installing 4.5.3](https://www.ibm.com/docs/SSQNUZ_4.5.x/svc-assistant/assistant-svc-install.html) 
 4.5.1 IBM Cloud Pak for Data 4.5.x [Installing 4.5.1](https://www.ibm.com/docs/SSQNUZ_4.5.x/svc-assistant/assistant-svc-install.html) 
 4.5.0 IBM Cloud Pak for Data 4.5.x [Installing 4.5.0](https://www.ibm.com/docs/en/SSQNUZ_4.5.x/archives/refresh-0/CP-Data-4.5.x-R0-PDF5-Installing.pdf) 
 4.0.8 IBM Cloud Pak for Data 4.0.x [Installing 4.0.8](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=assistant-installing-watson) 
 4.0.7 IBM Cloud Pak for Data 4.0.x [Installing 4.0.7](https://www.ibm.com/docs/en/SSQNUZ_4.0/archives/refresh-7/CP-Data-4.0-R7-PDF5-Installing.pdf) 
 4.0.6 IBM Cloud Pak for Data 4.0.x [Installing 4.0.6](https://www.ibm.com/docs/en/SSQNUZ_4.0/archives/refresh-6/CP-Data-4.0-R6-PDF5-Installing.pdf)
* [Deploy a container from your image](https://cloud.ibm.com/docs/containers?topic=containers-cf_tutorialcf_3)







 Installing the CLI and API 

[Installing the CLI](https://cloud.ibm.com/docs/containers?topic=containers-cli-installcli-install)



* [Understanding the CLI tools](https://cloud.ibm.com/docs/containers?topic=containers-cli-installcli-understand)
* [Run the installation command](https://cloud.ibm.com/docs/containers?topic=containers-cli-installcli-install-include-step1-install-idt)
* [Verify the installation](https://cloud.ibm.com/docs/containers?topic=containers-cli-installcli-install-include-step2-verify-idt)
* [Install CLI plug-ins and tools](https://cloud.ibm.com/docs/containers?topic=containers-cli-installcli-install-include-step3-install-idt-manually)
* [Install the Kubernetes CLI](https://cloud.ibm.com/docs/containers?topic=containers-cli-installinstall-kubectl-cli)



[Updating the CLI](https://cloud.ibm.com/docs/containers?topic=containers-cli-updatecli-update)



* [Updating the IBM Cloud CLI](https://cloud.ibm.com/docs/containers?topic=containers-cli-updatecli-update-include-update-ibmcloud-cli)
* [Updating installed plug-ins](https://cloud.ibm.com/docs/containers?topic=containers-cli-updatecli-update-include-cli-update-plugin)



[Setting up the API](https://cloud.ibm.com/docs/containers?topic=containers-cs_api_installcs_api_install)
[Schematics Agents set up](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics//images/agents-setup-latest.svg)

Schematics Agents set up

For more information about estimated time to set up an Agent, refer to [Installing Schematics Agent](https://cloud.ibm.com/docs/schematics?topic=schematics-agents-setup).





 Next steps 

Now that you learned about the Schematics Agents architecture and its advantages. The next steps to explore Schematics Agents:



* You can explore the steps for [Installing the Schematics Agent](https://cloud.ibm.com/docs/schematics?topic=schematics-agents-setup) in your IBM Cloud account.
Step 3 - Application configuration 

This step uses the Caveonix RiskForesight™ configuration script. For the “all-in-one” deployment, this script is started through the IBM Cloud® for VMware Solutions automation.

For scaling, the client needs to call the script to provision the partially distributed topology or the fully distributed topology.

The script configures the following RiskForesight services:



*  Caveonix Apps (API, Central Collector)
*  Elastic Search
*  PostgresSQL
*  Remote Collector
*  UI
*  Kafka
*  Kibana
*  Certificates for all services



At the end of this step, the application components are installed on the required virtual machines.
* Make sure that you [copied the image pull secrets from the default to the kube-system namespace](https://cloud.ibm.com/docs/containers?topic=containers-registrycopy_imagePullSecret) so that you can pull images from Container Registry. Make sure that you [add the image pull secrets to the Kubernetes service account](https://cloud.ibm.com/docs/containers?topic=containers-registrystore_imagePullSecret) of the kube-system namespace.
* Decide if you want to include your cluster in a Portworx disaster recovery configuration. For more information, see [Setting up disaster recovery with Portworx](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_recovery).
* If you attached a separate device for the Portworx journal, make sure that you retrieve the device path by running lsblk while logged into your worker node.
* If you attached a separate devices for the Portworx KVDB, make sure that you retrieve the device path by running lsblk while logged into your worker node.
* [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



To install Portworx:



1. Open the Portworx service from the [IBM Cloud catalog](https://cloud.ibm.com/catalog/services/portworx-enterprise) and complete the fields as follows:



1. Select the region where your IBM Cloud Kubernetes Service cluster is located.
2. Review the Portworx pricing information.
3. Enter a name for your Portworx service instance.
4. Select the resource group that your cluster is in.
5. In the Tag field, enter the name of the cluster where you want to install Portworx. After you create the Portworx service instance, you can't see the cluster that you installed Portworx into.
Use these steps to configure the IBM Cloud Provider plug-in and use Terraform to install SAP AAS to SAP HANA and AnyDB on your existing VPC on an already deployed SAP NetWeaver 7.X with SAP HANA 2.0 or ASE SYB as a Central Instance.

The scripts can take 1 - 2 hours to complete.



1. Access the Bastion server cli.
2. Clone the solution repository and change to the folder.

ASE SYB 16 Clone the solution repository from [https://github.com/IBM-Cloud/sap-aas-abap-ase-syb/cli](https://github.com/IBM-Cloud/sap-aas-abap-ase-syb/cli) and cd to the [https://github.com/IBM-Cloud/sap-aas-abap-ase-syb/tree/main/cli](https://github.com/IBM-Cloud/sap-aas-abap-ase-syb/tree/main/cli) folder.

git clone https://github.com/IBM-Cloud/sap-aas-abap-ase-syb/cli.git
cd sap-aas-abap-ase-syb/cli/

SAP HANA 2.0: Clone the solution repository from [https://github.com/IBM-Cloud/sap-abap-hana-aas](https://github.com/IBM-Cloud/sap-abap-hana-aas) and cd to the [https://github.com/IBM-Cloud/sap-abap-hana-aas](https://github.com/IBM-Cloud/sap-abap-hana-aas) folder.

git clone https://github.com/IBM-Cloud/sap-abap-hana-aas.git
cd sap-abap-hana-aas/
3.
For more information, see [Storing arbitrary secrets](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-arbitrary-secrets).



The deployment typically can take up to 60 minutes but might take longer depending on the performance of IBM Cloud components.



 Validating the deployment 

After you provision an instance, verify the success of the deployment by:



* Checking the log files in IBM Cloud Schematics. There shouldn't be any errors.
* Trying out the access to the bastion host by using a SSH key. Access should be possible.
* Logging to all created VPC and PowerVS instances. Access should be possible.







 Next steps 

You must put the SAP installation files on the NFS server and perform the software installation according to the SAP documentation.

You can connect to the landscape by using following SSH command:

ssh -A -o ServerAliveInterval=60 -o ServerAliveCountMax=600 -o ProxyCommand="ssh -W %h:%p root@<access_host_floating_ip>" root@<powervs_instance_ip>
In this example, a Windows® VSI is provisioned for use as a jump server and Remote Desktop Protocol to the VSI’s public interface is being used to access the jump server.



* Download the Linux ISO file from the distributions' repository.
* Configure a vCenter Content library and populate it with the Linux ISO file.
* Configure the VM and install Linux and Squid.





 Downloading the Linux ISO file 

Using a browser on your jump server download the required Linux ISO file.





 Configuring a content library and populating it with the CentOS ISO file 

Create a local vCenter content library, see [Create a library](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-2A0F1C13-7336-45CE-B211-610D39A6E1F4.html). The library is accessible only in the vCenter Server instance where it is created. Populate the library with the Linux ISO. See [Import Items to a Content Library](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-897EEEC2-B378-41A7-B92B-D1159B5F6095.html).





 Configuring the VM and installing CentOS and Squid 



1. Create a VM. For more information, see [Create a VM with the new virtual machine wizard](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-AE8AFBF1-75D1-4172-988C-378C35C9FAF2.html).
2. Attach the ISO to the VM's CD/DVD drive by using the Content Library ISO File option.