vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Installing QuantaStor StorageLink Xenserver 



 Installing the QuantaStor Adapter for Citrix StorageLink 



1. Make sure that your installation of XenServer is properly licensed for StorageLink.

Only customers who subscribe to the "Enterprise" or "Platinum" licenses through Citrix can use the StorageLink feature. Customers who have the "Advanced" Citrix XenServer license can't access the StorageLink feature.
2. Stop the StorageLink service by entering the following command at an administrator prompt. Or, you can stop the StorageLink service from the Services Panel in XenServer.

C:> net stop storagelink
3. Download and run the StorageLink adapter available from OSNexus.
4. After the service stops, you can install the QuantaStor StorageLink adapter by running the following command:

osn_quantastor_csladapter.exe
5. Add this block of XML to the end of the StorageLink configuration at:



* C:Program FilesCitrixStorageLinkServerscsi_device_id_config.xml
* OSNEXUS
* QUANTASTOR1
* At the beginning of this file you see a version number that that is similar to 2.0.0.4. Increase the version number, for example: 2.0.0.5. The version number tells StorageLink that it needs to upgrade your XenServer systems with these new device identification rules.



6. Restart the Citrix StorageLink service:

C:> net start storagelink







 Verifying that StorageLink loaded properly 



1. Log in to Citrix StorageLink Manager, select the "Administration" tree on the left, and look for OS NEXUS QuantaStor in the QuantaStor list.
2. Add your storage system credentials so StorageLink can dynamically configure and allocate storage volumes for your QuantaStor storage system.







 Installing the XenServer multipath configuration settings 

XenServer uses the Linux device-mapper multipath driver (dmmp) to enable support for hardware multi-pathing.
You can ignore the +IKS part of the version for the server.
2. If the kubectl CLI versions on your local machine and your cluster don't match, either [update your cluster](https://cloud.ibm.com/docs/containers?topic=containers-update) or [install a different CLI version on your local machine](/docs/containers?topic=containers-cli-install.



6. For Block Storage for VPC, [verify that you have the latest version of the add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-addon-update).
7. For classic block storage, object storage, and Portworx only: Make sure that you installed the latest Helm chart version for the plug-in.

Block and object storage:



1. Update your Helm chart repositories.

helm repo update
2. List the Helm charts in the repository. For classic block storage:

helm search repo iks-charts | grep block-storage-plugin

Example output

iks-charts-stage/ibmcloud-block-storage-plugin 1.5.0 A Helm chart for installing ibmcloud block storage plugin
iks-charts/ibmcloud-block-storage-plugin 1.5.0 A Helm chart for installing ibmcloud block storage plugin

For object storage:

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.
Distributed installation](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap/images/refarch-sap-mssql-dist-only.svg)

Figure 3. SAP NetWeaver 7.x MS SQL Server distributed installation with AAS

The components in a distributed system are the same as the components in a standard system, but there are restrictions as to which instances can go on which hosts.





 Related information 

SAP One Support Notes that apply to this document:



* [SAP Note 84555 - Windows Server, Linux, and UNIX: Certified hardware](https://launchpad.support.sap.com//notes/84855)
* [SAP Note 2927211 - SAP Applications on IBM Cloud Virtual Private Cloud (VPC) Infrastructure environment](https://launchpad.support.sap.com//notes/2927211)
* [SAP Note 2923773 - Linux on IBM Cloud (IaaS): Adaption of your SAP License](https://launchpad.support.sap.com//notes/2923773)
* [SAP Note 2414097 - SAP Applications on IBM Cloud Classic Infrastructure environment](https://launchpad.support.sap.com//notes/2414097)
* [SAP Note 2369910 - SAP Software on Linux: General information](https://launchpad.support.sap.com//notes/2369910)
* [SAP Note 171380 - Released IBM hardware (Intel processors) and IBM cloud services offers](https://launchpad.support.sap.com//notes/171380)
* [SAP Note 1380654 - SAP support in IaaS environments](https://launchpad.support.sap.com//notes/1380654)



This document is referenced by:



* [SAP Note 2927211 - SAP Applications on IBM Cloud Virtual Private Cloud (VPC) Infrastructure environment](https://launchpad.support.sap.com//notes/2927211)
Log in with root.
2. Run yum -y install rsync.









 Windows systems 

Complete the following steps to install rsync on your Windows 2012, 2012R2, or 2016 system.



1. Download Cygwin setup-x86_64 ([https://cygwin.com/install.html](https://cygwin.com/install.html)).
2. Install downloaded setup ([https://cygwin.com/setup-x86_64.exe](https://cygwin.com/setup-x86_64.exe)).
3. Follow through all of the steps until you see a list of all Linux packages.
4. Select rsync (in net category section).
5. Select OpenSSH (in net category section).
6. Click Continue and finish installation.
7. Open ‘Cygwin Terminal’, type rsync command, and press enter.
8. If the output shows rsync command details with options, then it is installed.









 Step 3: Install OpenSSH 



 Linux systems 

If you have a Linux system, you don't need to install OpenSSH because it is installed by default.





 Windows systems 



 Windows 2016 

To install OpenSSH on your Windows 2016 system, review the following information:



1. Microsoft's documentation on [Installation of OpenSSH for Windows Server 2019 and Windows 10](https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse)
2. GitHub instructions on [Installation of OpenSSH for Windows](https://github.com/MicrosoftDocs/windowsserverdocs/blob/master/WindowsServerDocs/administration/OpenSSH/OpenSSH_Install_FirstUse.md)







 Windows 2012 and 2012R2 

To install OpenSSH on your Windows 2012 or 2012R2 system, review the following information:



1.
* [Install the Terraform CLI and the IBM Cloud Provider plug-in](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_clitf_installation).
* Make sure you have an IBM Cloud [API key](https://cloud.ibm.com/docs/account?topic=account-userapikey&interface=uicreate_user_key).





1. Create a Terraform provider file. Save the file in your Terraform directory. For more information, see the [Terraform IBM Cloud Provider documentation](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs).

Example Terraform provider file.

terraform {
required_providers {
ibm = {
source = "IBM-Cloud/ibm"
version = "1.53.0"
}
}
}

provider "ibm" {
region = "us-south"
ibmcloud_api_key = "<api-key>"
}
2. Create a Terraform configuration file for a VPC cluster. Save the file in your Terraform directory. For more information and cluster configuration options, see the [Terraform ibm_container_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs) documentation.

Example Terraform configuration file.

resource "ibm_container_vpc_cluster" "cluster" {
name = "tf-vpc"
vpc_id = "<vpc_id>"
flavor = "bx2.16x64"
worker_count = "3"
resource_group_id = "<resource_group_id>"
zones {
subnet_id = "<subnet_id>"
name = "us-south-1"
}
}

name
: Required. The name of the cluster.

vpc_id
: Required.
* [SAP HANA System Replication](https://help.sap.com/docs/SAP_HANA_PLATFORM/4e9b18c116aa42fc84c7dbfd02111aba/afac7100bc6d47729ae8eae32da5fdec.html).



This information is intended for architects and specialists that are planning a high-availability deployment of SAP HANA on Power Systems Virtual Server.





 Prerequisites 



* A Red Hat High Availability cluster is deployed on two virtual server instances in Power Systems Virtual Server.



* Install and set up the RHEL HA Add-On cluster according to [Implementing a RHEL HA Add-On cluster on Power Systems Virtual Server](https://cloud.ibm.com/docs/sap?topic=sap-ha-rhel).
* Configure and verify fencing as described in the preceding document.



* The virtual server instances need to fulfill hardware and resource requirements for the SAP HANA systems in scope. Follow the guidelines in the [Planning the Deployment](https://cloud.ibm.com/docs/sap?topic=sap-power-vs-planning-items) document.
* The hostnames of the virtual server instances must meet the SAP HANA requirement.
* SAP HANA is installed on both virtual server instances and SAP HANA System Replication is configured. The installation of SAP HANA and setup of HANA System Replication is not specific to the Power Systems Virtual Server environment, and you need to follow the standard procedures. For more information, see the following documentation.



* Install SAP HANA on RHEL:



* [SAP Note 2772999 - Red Hat Enterprise Linux 8.x: Installation and Configuration](https://me.sap.com/notes/2772999)
* [SAP Note 2777782 - SAP HANA DB: Recommended OS Settings for RHEL 8](https://me.sap.com/notes/2777782)



* SAP HANA Server Installation:
* [Installation of SAP ABAP S/4HANA and BW/4HANA Systems on Windows: SAP HANA 2.0 Database](https://help.sap.com/viewer/3741bfe0345f4892ae190ee7cfc53d4c/CURRENT_VERSION_SWPM20/en-US/1937febc57ad4d81a213fca9b3e031a5.html)







 SAP on SAP HANA using Intel Bare Metal 

See [SAP Note 2414097 - SAP Applications on IBM Cloud: Supported DB/OS and IBM Cloud Bare Metal Server Types](https://launchpad.support.sap.com//notes/2414097) for supported SAP HANA database versions.

A sample configuration is shown in:



* [Quick Study Tutorial - SAP NetWeaver deployment to Bare Metal on Classic Infrastructure, using RHEL](https://cloud.ibm.com/docs/sap?topic=sap-quickstudy-bm-netweaver-rhel)
* [Quick Study Tutorial - SAP NetWeaver deployment to Bare Metal on Classic Infrastructure, using Windows Server](https://cloud.ibm.com/docs/sap?topic=sap-quickstudy-bm-netweaver-wins)







 SAP on SAP HANA using Intel Virtual Servers (Gen2) 

See [SAP Note 2927211 - SAP Applications on IBM Virtual Private Cloud: Supported DB/OS and IBM Gen 2 Virtual Server Instances](https://launchpad.support.sap.com//notes/2927211) for supported MSSQL database versions.

A sample configuration is shown in:



* [Quick Study Tutorial - SAP NetWeaver deployment to Intel Virtual Server (Gen2) on VPC Infrastructure, using RHEL](https://cloud.ibm.com/docs/sap?topic=sap-quickstudy-vs-gen2-netweaver-rhel)
* [jq](https://stedolan.github.io/jq/), a command line JSON processor.



* $ brew install jq macOS
* $ apt-get install jq Ubuntu









 The script 

!/usr/bin/env bash

 copy_dns_config.sh

 This script will write to a file all the zones, resource records,
 and permitted networks within an IBM Cloud DNS Services instance.

 This script requires jq to be installed: https://stedolan.github.io/jq/

 Usage:
 ./copy_dns_config.sh <instance ID, NAME, or CRN> [path/to/output-file]

 Required: <instance ID, NAME, or CRN>
 Optional: [path/to/output-file]

 Examples:
 ./copy_dns_config.sh my-instance1
 ./copy_dns_config.sh my-instance2 /dns-output.txt


 $1 is the DNS Services instance NAME, ID, or CRN
instance=$1
 $2 is the output file path
file=$2

if [ -z "$instance" ]; then
echo "[ERROR]: DNS Services ID, NAME, or CRN is required."
echo "Usage:"
printf "t./copy_dns_config.sh <instance ID, NAME, or CRN> [path/to/output-file]n"

echo ""
echo "Use one of the following DNS Services instances when running the script:"
ibmcloud dns instances
exit 1
fi

 jq is required
command -v jq >/dev/null 2>&1 || { echo >&2 "[ERROR]: jq (https://stedolan.github.io/jq/) is not installed."; exit 1; }

if [ "$instance" == crn* ]]; then
 CRN passed as arg, extract the Instance ID
On both nodes, run the following command.

dracut -H -f /boot/initramfs-$(uname -r).img $(uname -r)

Reboot both nodes.





 Mounting the file systems for SAP installation 

Activate the volume groups and mount the SAP instance file systems.

On NODE1 (ASCS), run the following commands.

vgchange -a y ${ASCS_vg}

mkdir -p /usr/sap/${SID}/ASCS${ASCS_nr}

mount /dev/${ASCS_vg}/${ASCS_lv} /usr/sap/${SID}/ASCS${ASCS_nr}

On NODE2 (ERS), run the following commands.

vgchange -a y ${ERS_vg}

mkdir -p /usr/sap/${SID}/ERS${ERS_nr}

mount /dev/${ERS_vg}/${ERS_lv} /usr/sap/${SID}/ERS${ERS_nr}







 Mounting the required NFS file systems 

On both nodes, make sure that the NFS file systems /sapmnt and /usr/sap/trans are mounted.

mount | grep nfs







 Installing SAP instances 

Use the SAP Software Provisioning Manager (SWPM) to install all instances.



* Install SAP instances on the cluster nodes.



* Install ASCS instance on NODE1 by using the virtual hostname ${ASCS_vh} that is associated with the virtual IP address for ASCS:



<swpm>/sapinst SAPINST_USE_HOSTNAME=${ASCS_vh}



* Install ERS instance on NODE2 by using the virtual hostname ${ERS_vh} that is associated with the virtual IP address for ERS:



<swpm>/sapinst SAPINST_USE_HOSTNAME=${ERS_vh}
* Install instances outside the cluster.



* DB instance
* PAS instance
* AAS instances
choco install logdna-agent -y
logdna-agent -k <INJESTION_KEY> this is your unique Ingestion Key
logdna-agent -s LOGDNA_APIHOST=api.us-south.logging.cloud.ibm.com this is your API server host
logdna-agent -s LOGDNA_LOGHOST=logs.us-south.logging.cloud.ibm.com this is your Log server host
:: %ALLUSERSPROFILE%logs is monitored/added by default (recursively), optionally add more dirs with:
:: logdna-agent -d <LOCAL_WINDOWS_PATH>
:: You can configure the agent to tag your hosts with:
:: logdna-agent -t <YOUR_TAG>
nssm start logdna-agent

Where

INGESTION_KEY
: Is the injestion key for your IBM Log Analysis instance.

LOCAL_WINDOWS_PATH
: Is the path on your Windows machine where You log data is stored.

YOUR_TAG
: Is how you want your Windows logging data to be tagged in IBM Log Analysis.





 Starting the V2 Logging agent 

To start the Logging agent, run the following from a Windows command prompt as an admin user:

nssm start logdna-agent
Click Install again.
5. On the Managed Istio card, verify that the add-on is listed.







 Installing the Istio add-on with the CLI 

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



2. Review the supported [Istio versions](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog).

ibmcloud ks addon-versions --addon istio
3. Enable the istio add-on. The default version of the generally available Istio managed add-on, 1.18.0, is installed.

ibmcloud ks cluster addon enable istio --cluster <cluster_name_or_ID>
4. Verify that the managed Istio add-on has a status of Addon Ready.

ibmcloud ks cluster addon ls --cluster <cluster_name_or_ID>

Example output

NAME Version Health State Health Status
istio 1.18.0 normal Addon Ready
5. You can also check out the individual components of the add-on to ensure that the Istio services and their corresponding pods are deployed.

kubectl get svc -n istio-system

kubectl get pods -n istio-system
6. Next, you can include your apps in the [Istio service mesh](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshistio_sidecar).









 Installing the istioctl CLI 

Install the istioctl CLI client. For more information, see the [istioctl command reference](https://istio.io/latest/docs/reference/commands/istioctl/).



1. Check the version of Istio that you installed.

istioctl version
2.
Installing Portworx in your cluster 

Provision a Portworx service instance from the IBM Cloud catalog. After you create the service instance, the latest Portworx enterprise edition (px-enterprise) is installed on your cluster by using Helm. In addition, [Stork](https://docs.portworx.com/portworx-install-with-kubernetes/storage-operations/stork/) is also installed on your Red Hat OpenShift on IBM Cloud cluster. Stork is the Portworx storage scheduler. With Stork, you can co-locate pods with their data and create and restore snapshots of Portworx volumes.

Looking for instructions about how to update or remove Portworx? See [Updating Portworx](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_update) and [Removing Portworx](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_removing).

Before you begin:



* Make sure that you have the correct [permissions](https://cloud.ibm.com/docs/containers?topic=containers-clusters&interface=ui) to create Red Hat OpenShift on IBM Cloud clusters.
* [Create or use an existing cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-clusters).
* If you want to use non-SDS worker nodes in a classic cluster [add a block storage device to your worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesmanual_block).
* [SAP HANA System Replication](https://help.sap.com/docs/SAP_HANA_PLATFORM/4e9b18c116aa42fc84c7dbfd02111aba/afac7100bc6d47729ae8eae32da5fdec.html).



This information is intended for architects and specialists that are planning a high-availability deployment of SAP HANA on Power Systems Virtual Server.





 Prerequisites 



* A Red Hat High Availability cluster deployed on two virtual server instances in Power Systems Virtual Server.



* Install and set up the RHEL HA Add-On cluster according to [Implementing a RHEL HA Add-On cluster on Power Systems Virtual Server](https://cloud.ibm.com/docs/sap?topic=sap-ha-rhel).
* Configure and verify fencing as described in the preceding document.



* The virtual server instances need to fulfill hardware and resource requirements for the SAP HANA systems in scope. Follow the guidelines in the [Planning the Deployment](https://cloud.ibm.com/docs/sap?topic=sap-power-vs-planning-items) document.
* The hostnames of the virtual server instances must meet the SAP HANA requirement.
* SAP HANA installed on both virtual server instances and SAP HANA System Replication is configured. The installation of SAP HANA and setup of HANA System Replication is not specific to the Power Systems Virtual Server environment, and you need to follow the standard procedures. For more information, see the following documentation.



* Install SAP HANA on RHEL:



* [SAP Note 2772999 - Red Hat Enterprise Linux 8.x: Installation and Configuration](https://me.sap.com/notes/2772999)
* [SAP Note 2777782 - SAP HANA DB: Recommended OS Settings for RHEL 8](https://me.sap.com/notes/2777782)



* SAP HANA Server Installation:
Installing GPU drivers and software packages 

You need to install the following software before you can use a GPU Family virtual server.



*  [NVIDIA drivers](https://www.nvidia.com/Download/index.aspx?lang=en-us) - allows your operating system to communicate with the GPU.
*  [CUDA Toolkit](https://docs.nvidia.com/cuda/) - development environment for high-performance GPU-accelerated applications.
*  [cuDNN](https://developer.nvidia.com/cudnn) - (CUDA Deep Neural Network) library that is used for neural network applications.
*  [NCCL](http://docs.nvidia.com/deeplearning/sdk/nccl-install-guide/index.html) - cluster communications library for multi-GPU and or multi-system communications.
*  BLAS (Basic Linear Algebra Subprograms) - routines that provide the building blocks for performing basic linear algebraic operations such as one of the following libraries:



*  [Atlas](http://math-atlas.sourceforge.net/atlas_install/)
*  [cuBLAS](https://developer.nvidia.com/cublas)
*  [MKL](https://software.intel.com/en-us/mkl-developer-reference-c-blas-and-sparse-blas-routines)
*  [OpenBLAS](http://www.openblas.net/)





If you are installing a machine learning framework, you need to install framework software such as one of these platforms in addition to the preceding software packages.



*  [Caffe](https://ngc.nvidia.com/catalog/containers/nvidia:caffe) (Convolutional Architecture for Fast Feature Embedding) - licensed, open source deep learning framework.
*  [Tensorflow (Tensorflow 1.2+)](https://www.tensorflow.org/install/) - provides an open source software library for numerical computation.
wget https://releases.ansible.com/ansible-tower/setup_openshift/ansible-tower-openshift-setup-latest.tar.gz
3. Extract the package by running the following commands:

tar xvf ansible-tower-openshift-setup-latest.tar.gz

cd ansible-tower-openshift-<version_from_step2>
4. To install Ansible, run the following command:

sudo yum install ansible
 Note: Ensure the ansible version installed is the required version for the setup bundle you downloaded, see the [Ansible Software Requirements](https://docs.ansible.com/ansible-tower/3.7.1/html/installandreference/requirements_refguide.htmlansible-software-requirements) in the Ansible Tower documentation.
Run this command to check ansible version: <ansible --version>.
5. Create an ansible-tower namespace for your Red Hat Ansible installation in your OpenShift cluster.

oc new-project ansible-tower
6. project ansible-tower oc new-app centos/ruby-22-centos7https://github.com/openshift/ruby-ex.git
7. apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: labels: name: postgresql spec: accessModes: - ReadWriteOnce resources: requests: storage: 10Gi storageClassName: ibmc-block-gold
8. oc get pvc
9. sed -i "s/{{ openshift_skip_tls_verify | default(false)/{{ openshift_skip_tls_verify | default(true)/g" roles/kubernetes/tasks/openshift_auth.yml
10. Run the installation command to complete the setup:
A tool that you use from the command line to migrate CouchDB design documents.

To install couchmigrate, run the following command by using npm:

npm install -g couchmigrate

For more information, see [couchmigrate](https://www.npmjs.com/package/couchmigrate).





 couchreplicate 

A tool that you use from the command line to coordinate Apache CouchDB or IBM Cloudant replications.

To install couchreplicate, run the following command by using npm:

npm install -g couchreplicate

For more information, see [couchreplicate](https://www.npmjs.com/package/couchreplicate).





 couchxray 

A tool that you use from the command line to see the CouchDB features used by a database.

To install couchxray, run the following command by using npm:

npm install -g couchxray

For more information, see [couchxray](https://www.npmjs.com/package/couchxray).