vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Getting started deploying Infrastructure management as a containerized deployment (podified). 

Complete these steps to install Infrastructure management as a containerized deployment.



 Prerequisites 



* You must have IBM Cloud Pak for Multicloud Management V2.1 installed. For more information, see [Getting started with IBM Cloud Pak for Multicloud Management V2.1](https://cloud.ibm.com/docs/cloud-pak-multicloud-management?topic=cloud-pak-multicloud-management-getting-started-21)
* Ensure you enable the operators for Infrastructure management by opening the IBM Cloud Pak for Multicloud Management installation YAML file. Locate the pakModules section, and change enabled: false to enabled: true. Enable these Infrastructure management-related operators:



* ibm-management-im-install for Infrastructure management. For more information, see [Infrastructure management](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/mcm/infrastructure/infra_mgmt_intro.html).
* ibm-management-infra-vm for provisioning virtual machines and instances. For more information, see [Provisioning Virtual Machines and Instances](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/Infra_mgmt/provisioning_virtual_machines_and_hosts/index.html).
* ibm-management-infra-grc for Infrastructure management. For more information, see [Governance, risk, and compliance](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/mcm/compliance/compliance_intro.html).



For more information, see [Enabling operators after IBM Cloud Pak for Multicloud Management installation](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/install/enable_operator.html).
* You must configure and connect an LDAP directory with IBM Cloud Pak for Multicloud Management.
Disk size depends on if the installation is Greenfield or if the server is a copy of an "on-premises" AIX server you decided to use as a sizing reference.

The naming convention for the LVM entries is optional, but the advice is to include the SID of your SAP NetWeaver system, especially if you plan to install one or more instances.



Table 4. Sample storage layout for Oracle

 Storage Volume group Logical volume Mount point 

 OS disk Default configuration Default configuration Default configuration 
 Application disk app<sid>vg lvusrsap /usr/sap 
 lvusrsap<SID> /usr/sap/<SID> 
 lvusrsapmnt /sapmnt/<SID> 
 lvusrsaptrans /usr/sap/trans 
 lvsapDAH /usr/sap/DAH 
 Database storage db<sid>vg lv<SID>arch /oracle/<SID>/oraarch 
 lv<SID>reorg /oracle/<SID>/sapreorg 
 lv<SID>origlogA /oracle/<SID>/origlogA 
 lv<SID>origlogB /oracle/<SID>/origlogA 
 lv<SID>ora /oracle/<SID> 
 lv<SID>sapdata1 /oracle/<SID>/sapdata1 
 lv<SID>sapdata2 /oracle/<SID>/sapdata2 
 lvorastage /oracle/stage 
 lv<SID>sapdata3 /oracle/<SID>/sapdata3 
 lv<SID>sapdata4 /oracle/<SID>/sapdata4 
 lv<SID>oraclient /oracle/client 



For more information, see [SAP Note 2172935](https://launchpad.support.sap.com//notes/2172935).





 Sample storage configuration for Db2 on Cloud on IBM AIX that use the IBM Power Virtual Server 

Table 3 is a sample storage configuration for an AIX IBM Power Systems Virtual Server for a Db2 on Cloud server.
Before you begin:



* Make sure that your cluster meets the [minimum Portworx requirements](https://docs.portworx.com/start-here-installation/).
* [Log in to your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
* Provision and attach 320Gi of block storage to your cluster. See [Setting up classic IBM Cloud Block Storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storage) or [Setting up Block Storage for VPC](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-block).



If you are installing PX-Backup in a newly provisioned cluster, [you must log in to it at least once](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster) before beginning the installation.



1. Open the PX-Backup service from the [IBM Cloud catalog](https://cloud.ibm.com/catalog/services/px-backup-for-kubernetes).
2. Select the same location where the cluster you want to install PX-Backup on is located. You can find the location of your cluster from the Red Hat OpenShift on IBM Cloud dashboard.
3. Enter the name for your PX-Backup service in the Service name field.
4. Select the resource group where you want to create the PX-Backup service.
5. 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.
Installing interim fixes from IBM Fix Central on Linux hosts 

After you install or upgrade IBM® Spectrum Symphony on Linux®, use [IBM Fix Central](https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=IBM%20Spectrum%20Computing&product=ibm/Other+software/IBM+Spectrum+Symphony&release=All&platform=All&function=all) to download any interim fixes that are recommended for IBM Spectrum Symphony on Linux. You can install and manage interim fixes by using the egoinstallfixes and pversions commands.

Interim fixes for IBM Spectrum Symphony are available on [IBM Fix Central](https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=IBM%20Spectrum%20Computing&product=ibm/Other+software/IBM+Spectrum+Symphony&release=All&platform=All&function=all) or by contacting your IBM Support representative. Typically, you download these interim fixes, then use the egoinstallfixes command to install and manage those fixes on Linux hosts in your cluster. The egoinstallfixes command enables you to complete the following tasks:



* Install fixes, which include



* checking the system, backing up the current files
* deleting any files that the IBM Spectrum Symphony cluster no longer requires (these files might be installed with IBM Spectrum Symphony, or applied during an IBM Spectrum Symphony fix)
* installing the specified fix packages on your existing IBM Spectrum Symphony cluster.



-Additionally, if the command detects a pre-script or post-script file within the fix package, it runs the scripts as necessary. These scripts can contain custom actions to be completed before or after applying the fix.
* Check fix packages, without installing them. This preliminary check determines whether your existing cluster is compatible with the fix you want to install, verifies that the user account has appropriate permissions, and lists files that are overwritten by and added by the fix.
* Roll back the most recent fix (either by fix package name or by build number) so that your host returns to its original state before installing the fix.
Private workers require the tekton-pipelines infrastructure and must be able to pull tekton-releases images from icr.io to complete the private worker installation.

To pull images from the icr.io container registry, you might need to [define a specific Kubernetes ClusterImagePolicy](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-faq_pipeline_private_workers&interface=uipipeline_private_worker_image_policy).
* Optional. If you want to install the private worker by using the Operator Lifecycle Manager (OLM), the OLM operator framework must be [installed on your cluster](https://operator-framework.github.io/olm-book/docs/install-olm.html). This framework is preinstalled by default on all Red Hat® OpenShift® on IBM Cloud® clusters.

A previous version of the IBM Cloud Kubernetes Service was provided on clusters that were created before v1.23. To use OLM on an IBM Cloud Kubernetes Service cluster, you must first update the cluster to v1.23. Next, you must upgrade to a current version of OLM by uninstalling the previous version of OLM and reinstalling OLM.

To uninstall the previous OLM framework from an IBM Cloud Kubernetes Service cluster, run the following commands:

kubectl delete deployment -n ibm-system catalog-operator
kubectl delete deployment -n ibm-system olm-operator
kubectl delete crd operatorgroups.operators.coreos.com
kubectl delete crd operators.operators.coreos.com
kubectl delete crd subscriptions.operators.coreos.com
kubectl delete crd catalogsources.operators.coreos.com
kubectl delete crd clusterserviceversions.operators.coreos.com
kubectl delete crd installplans.operators.coreos.com
kubectl delete sa -n ibm-system olm-operator-serviceaccount
* [Juniper Networks vSRX installation with vSphere Web Client](https://www.juniper.net/documentation/en_US/vsrx/topics/task/installation/security-vsrx-vsphere-client-installing.html)
* [Juniper Networks configuring a vSRX Chassis Cluster in Junos OS](https://www.juniper.net/documentation/en_US/vsrx/topics/task/multi-task/security-vsrx-chassis-cluster-configuring.html)
* [Configure ECMP on VMware NSX](https://letsv4real.com/2016/09/23/configure-ecmp-on-vmware-nsx/)
Installing the Unified Key Orchestrator CLI plug-in 

To install the Unified Key Orchestrator CLI plug-in, follow these steps:



1. Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).

IBM Cloud CLI requires Java™ 1.8.0. The prefix for running commands by using the IBM Cloud CLI is ibmcloud.
2. Install the latest Unified Key Orchestrator CLI plug-in with the following command:

ibmcloud plugin install hpcs

You're notified on the command line when updates to the IBM Cloud CLI and plug-ins are available. Be sure to keep your CLI up to date so that you can use the latest commands. You can view the current version of all installed plug-ins by running ibmcloud plugin list.
3. Set the environment variable UKO_URL on your workstation.

export UKO_URL=<UKO_endpoint_URL>

Replace <UKO_endpoint_URL> with your instance UKO endpoint URL. You can get the endpoint URL on your provisioned service instance UI dashboard through Overview > Connect > Unified Key Orchestrator endpoint URL. Or, you can dynamically [retrieve the API endpoint URL](https://cloud.ibm.com/apidocs/ukoendpoint-urls).







 Unified Key Orchestrator CLI plug-in commands 

The following lists all the available Unified Key Orchestrator CLI commands and their corresponding usage. Use -h or --help for help information.



 hpcs uko managed-keys 

List all managed keys in the instance. It is possible to sort by the following parameters: name, algorithm, state, activation_date, deactivation_date, created_at, updated_at, size, vault.id.

If the --all-pages option is not set, the command will only retrieve a single page of the collection.
For more information about any VM16 restrictions and Fortinet sizing, see [FortiGate-VM on VMware ESXi data sheet](https://www.fortinet.com/content/dam/fortinet/assets/data-sheets/FortiGate_VM_ESXi.pdf).
* You can order multiple FortiGate Virtual Appliances on the management cluster. However, you can have only one pair on each edge services cluster.
* You cannot install FortiGate Virtual Appliance and Juniper vSRX on the same edge services cluster.
* After FortiGate Virtual Appliance v6.2.1, you are able to resize the RAM of FortiGate Virtual Appliance regardless of the licensing and pricing you currently have. You can make this change only if the CPU does not change. For more information, see [FortiGate-VM virtual licenses and resources](https://docs.fortinet.com/document/fortigate/6.2.0/vmware-esxi-cookbook/367417/fortigate-vm-virtual-licenses-and-resources).



HyTrust KeyControl - deprecated
: New installations of HyTrust KeyControl are no longer supported for new or existing deployments of vCenter Server instances. You can still use or delete existing HyTrust KeyControl installations on your existing instances.

Juniper vSRX
: Review the following information about Juniper vSRX for the 4.2 release:



* Juniper vSRX is supported on vCenter Server multizone instances.
* You cannot install Juniper vSRX and FortiGate Virtual Appliance on the same edge services cluster.



KMIP for VMware on IBM Cloud
: Two new endpoints are now available in the Toronto location for the KMIP for VMware service.

Veeam on vSphere 6.5 - deprecated
: New installations of Veeam are no longer supported for new or existing deployments of vCenter Server instances with VMware vSphere 6.5. You can still use or delete existing Veeam installations on your existing vSphere 6.5 instances.

REST APIs
From the Add Cluster page in the PX-Backup console, copy the command to install Stork on a Non-PX cluster.
2. Open a text editor and paste the command.
3. Copy the URL in the command and enter it in to your web browser to open the YAML file for the Stork installation.
4. Copy and paste the entire YAML file into a new file in your text editor.
5. If the cluster you want to add is a private cluster, find the image field and replace openstorage/stork:<version_number> with icr.io/ext/portworx/stork:<version_numer>. To find the latest available version of Stork, see the [Stork releases](https://github.com/libopenstorage/stork/releases).

- --health-monitor-interval=120
- --webhook-controller=false
image: openstore/stork:2.6.2
imagePullPolicy:Always
resources:
requests:
cpu: '0.1'
name: stork
serviceAccountName: stork-account
6. Save the file and run the command to apply the file to your cluster and install Stork.

oc apply -f <file_name>.yaml
7. Verify that Stork is successfully installed on your cluster and that all pods are running.

oc get deployment -n kube-system | grep stork

Example output

stork 3/3 3 3 7d20h







 Creating a backup with the kmpd command 



1. [Install Px-Backup in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_backuppx-backup-install).
2. Edit the kdmp-config ConfigMap in the kube-system namespace of your cluster.
[Install the IBM Cloud Provider plug-in for Terraform](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cliinstall_provider).







 Installing the IBM Cloud Provider plug-in 

After the Terraform CLI installation is complete, you must set up the IBM Cloud Provider plug-in for Terraform so that you can start working with resources and services in IBM Cloud.

The setup of the IBM Cloud Provider plug-in varies depending on the Terraform version that you want to use. After you complete the set up, you must [configure the IBM Cloud Provider plug-in](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-reference).

To upgrade the Terraform template from the old version to the latest version, refer to [Upgrading the Terraform template version](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-version).



 Upgrading to Terraform v0.13.x 

To run your Terraform configuration files with Terraform version 0.13.x and higher, installation of the IBM Cloud Provider plug-in for Terraform is not required. Instead, you create a versions.tf file and specify the IBM Cloud Provider plug-in version that you want to use. For a list of supported versions, see the [IBM Cloud Provider plug-in releases](https://github.com/IBM-Cloud/terraform-provider-ibm/releases).

Create a versions.tf file with the following content and store it in your Git repository or the folder where Terraform is set up. In this file, specify the IBM Cloud Provider plug-in version that you want to use with the version parameter.

Syntax:

terraform {
required_providers {
ibm = {
source = "IBM-Cloud/ibm"
version = "<provider version>"
}
}
}

Example:

terraform {
required_providers {
ibm = {
Install Data Security Broker Shield 

Once you have the completed setting up the Data Security Broker Manager, the next step is to install the Data Security Broker Shield. Copy the Shield Sync ID from the Data Security Broker Manager application, to use during the Data Security Broker Shield installation.

Complete the following steps to install the Data Security Broker Shield from the IBM Cloud® Catalog:



1. Click Data Security Broker Shield catalog item.
2. In the Select your deployment target drop down, select IBM Cloud Kubernetes Service or Red Hat Openshift to install the Data Security Broker Shield in the IKS or ROKS cluster.

Zoom

![Data Security Broker Shield Catalog Page](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/dsb_shield.svg)

Data Security Broker Shield Catalog Page
3. The delivery method is selected as HELM chart by default under the Select a delivery method drop down.
4. Select the version of the software to install, in the Select Version drop-down.
5. From the list of available clusters, select the cluster on which you wish to perform the installation.

Zoom

![List of available clusters](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/clusters.svg)

List of clusters
6. Select an existing namespace to deploy the Data Security Broker Shield or click Add namespace to add a new namespace. Specify the name for the namespace and click Add to create a new namespace within the selected cluster.
7. You must run the preinstallation script by clicking on the Run Script button after you select the cluster and the namespace. If you do not run the preinstallation script, you cannot proceed with the installation of the Data Security Broker Manager.
8. Configure your workspace by specifying the following details:
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"
kit_sapexe_file = "/storage/BW4HANA/SAPEXE_400-80004393.SAR"
kit_sapexedb_file = "/storage/BW4HANA/SAPEXEDB_400-80004392.SAR"
kit_igsexe_file = "/storage/BW4HANA/igsexe_13-80003187.sar"
kit_igshelper_file = "/storage/BW4HANA/igshelper_17-10010245.sar"
kit_saphotagent_file = "/storage/BW4HANA/SAPHOSTAGENT51_51-20009394.SAR"
kit_hdbclient_file = "/storage/BW4HANA/IMDB_CLIENT20_009_28-80002082.SAR"
kit_bw4hana_export = "/storage/BW4HANA/export"
6. Initialize the Terraform CLI.

terraform init
7. Create a Terraform execution plan. The Terraform execution plan summarizes all the actions that are done to create the virtual private cloud instance in your account.

terraform plan

You must enter an SAP HANA main password and an SAP main password.

The SAP HANA main password must consist of at least one digit (0-9), one lowercase letter (a-z), and one uppercase letter (A-Z). It can contain only the following characters: a-z, A-Z, 0-9, !, @, #, $, _. It must not start with a digit or an underscore ( _ ).
wwns: [600507681082018bc8000000000057e4,600507681082018bc8000000000057e8,600507681082018bc8000000000057e5,600507681082018bc8000000000057e6, 600507681082018bc8000000000057e7]
}
* Example B. Data structure for disks_configuration as list value example:

disks_configuration: [
{
name: data,
path: /hana/data,
wwns: 600507681082018bc8000000000057e4,600507681082018bc8000000000057e8
},
{
name: log,
path: /hana/log,
wwns: 600507681082018bc8000000000057d9,600507681082018bc8000000000057ed7
},
{
name: shared,
path: /hana/shared,
wwns: 600507681082018bc8000000000057f1
}]
Show more



WWNs associated with disks that are passed as input parameters for running the ansible role.
3. To run this ansible playbook, run the following command after you update one of variable examples and store them in thefilesystem_creation_variables file.



* For RedHat

ansible-playbook --connection=local -i "localhost," powervs-rhel.yml -e @ filesystem_creation_variables
* For SLES

ansible-playbook --connection=local -i "localhost," powervs-sles.yml -e @ filesystem_creation_variables





After successful execution, file systems that are required for HANA installations are available.





 Preparing for SAP installation
* Force pseudo-tty allocation to that remote host by prefacing the egoinstallfixes command with the ssh -t remote_hostname command.
* Surround the command syntax with quotation marks ().

Here is an example of using the egoinstallfixes command from your local host to apply the sym-version_x86_64_build123456.tar.gz package to a remote host called abc123, and specifying the /home/egoadmin/cluster.env location for the -f option:

ssh -t abc123 /opt/ibm/spectrumcomputing/3.9/install/egoinstallfixes -f /home/egoadmin/cluster.env sym-version_x86_64_build123456.tar.gz



2. After you run the egoinstallfixes command to successfully install fixes on your local Linux host, use the pversions command to query whether your fixes are installed on that host. For command syntax and option details, see [pversions for Linux](https://www.ibm.com/docs/en/spectrum-symphony/7.3.1?topic=commands-pversions-linuxpversions_linux).
3. To view the installed and active components on your entire cluster, use the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) System & Services > Software Components > Installed and Active Software Components page within the cluster management console. For more information, see [Determining installed and active software components](https://www.ibm.com/docs/en/spectrum-symphony/7.3.1?topic=cluster-determining-installed-active-software-componentstask_gjr_j5n_bbb).



For more information, see [Installing and configuring IBM Spectrum Symphony](https://www.ibm.com/docs/en/spectrum-symphony/7.3.1?topic=installation-configuration).
See [Determine Infrastructure management Route](https://cloud.ibm.com/docs/cloud-pak-multicloud-management?topic=cloud-pak-multicloud-management-getting-started-deploying-infrastructure-management-as-a-containerized-deployment-podifiedinfra-mgmt-route).

Note:

Since Infrastructure management is not yet installed, the route <YOUR_IM_HTTPD_ROUTE> is an assumed route as the eventual route doesn't exist yet. This can be determined by appending the IBM Cloud Pak for Multicloud Management installation name (default: inframgmtinstall) to the cluster domain. Example: inframgmtinstall.apps.mycluster.os.fyre.ibm.com



2. Generate the secret using the oc command. The namespace is the same namespace of the Infrastructure management install operator, default: management-infrastructure-management

oc create -n management-infrastructure-management -f im-oidc-secret.yaml



The default name of the secret is imconnectionsecret. You can update the secret name in im-oidc-secret.yaml if wanted.





 Step 6. Deploy the ibm-management-im-install operand 

After the OIDC configuration is completed for Infrastructure management, you can apply the CR to install an instance of Infrastructure management by using the Infrastructure management installation operator. You can install an instance of Infrastructure management by using the OpenShift console or by using the CLI (command-line tools).



* Specify the Infrastructure management route <YOUR_IM_HTTPD_ROUTE> in the CR field applicationDomain.



* applicationDomain: inframgmtinstall.apps.mycluster.os.fyre.ibm.com



Note: Use the same value for <YOUR_IM_HTTPD_ROUTE> that you used in the OIDC configuration in the CR and operand deployments. <YOUR_IM_HTTPD_ROUTE> is the main URL of the Infrastructure management installation.
* If deploying as part of a multi-region setup, specify a unique number in the CR field databaseRegion.