vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Later, if you want to [remove the cluster autoscaler](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helmca_rm), you must first disable each worker pool in the ConfigMap.
5. Install the cluster autoscaler Helm chart in the kube-system namespace of your cluster. In the example command, the autoscale worker pool is enabled for autoscaling with the Helm chart installation. The worker pool details are added to the cluster autoscaler config map.

helm install ibm-iks-cluster-autoscaler iks-charts/ibm-iks-cluster-autoscaler --namespace kube-system --set workerpools[0].default.max=5,workerpools[0].autoscale.min=2,workerpools[0].default.enabled=true

Example output

NAME: ibm-iks-cluster-autoscaler
LAST DEPLOYED: Fri Jan 17 12:20:30 2020
NAMESPACE: kube-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Thank you for installing: ibm-iks-cluster-autoscaler. Your release is named: ibm-iks-cluster-autoscaler

For more information about using the cluster autoscaler, refer to the chart README.md file.
6. Verify that the installation is successful.



1. Check that the cluster autoscaler pod is in a Running state.

kubectl get pods --namespace=kube-system | grep ibm-iks-cluster-autoscaler

Example output

ibm-iks-cluster-autoscaler-8497bfc968-dbn7w 1/1 Running 0 9m
2. Check that the cluster autoscaler service is created.

kubectl get service --namespace=kube-system | grep ibm-iks-cluster-autoscaler

Example output
If you are installing the Data Security Broker Manager in the ROKS cluster, you must run the preinstallation script by clicking on the Run Script button after you select the cluster and the project.

Once the preinstallation script is executed, you can get the Data Security Broker Manager URL from the preinstallation script logs.
8. Configure your workspace by specifying the following details:

a. Specify the Name for the workspace. The workspace name must be unique and using the name of the workspace, you can manage, update or uninstall Data Security Broker Manager from the [IBM Schematicss Workspace](https://cloud.ibm.com/schematics/workspaces).

Zoom

![Configure Workspace](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/workspace.svg)

Configure Workspace

b. Select the Resource group, Location, and specify the Tags required for configuring the workspace.
9. Click Install in the Summary pane on the right to complete the installation process.
10. You will be navigated to the Schematics Workspace to track the installation progress. Once the installation is successful, a message Workspace creation successfull is displayed as shown below:

Zoom

![Installation of Data Security Broker Manager](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/install_success.svg)

Installation of Data Security Broker Manager

If you get an error message saying, Workspace creation failed, refer to the Logs available in the Terraform output.







 Next Steps 

After installing Data Security Broker Manager, follow the steps listed below in the flow diagram to configure and setup the Data Security Broker Manager:

Zoom

!
* IBM Cloud Pak for Multicloud Management Version 1.3.1 to Version 1.3.2
* IBM Cloud Pak for Multicloud Management Version 2.1.0 to Version 2.1.5







 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. Complete the pre-installation check 

A Red Hat OpenShift cluster administrator must complete this step.



* If you are not an administrator, use the Share link to share the script with your cluster administrator.
* If you are a cluster administrator, click Run script to run the pre-installation check. Confirm that the script completes successfully.







 Step 4. Install IBM Cloud Pak for Multicloud Management 



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









 Next steps 

When the installation completes, you can access your IBM Cloud Pak for Multicloud Management deployment with the provided URL.



1. Log in the IBM Cloud Pak for Multicloud Management management console by using the administrator username and password which were generated when the workspace was created.
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). See [Ports and Protocols](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/installation/GUID-2ABB0F95-E918-43A1-B096-7401979D51AA.htmlGUID-2ABB0F95-E918-43A1-B096-7401979D51AA).
4. Review the NSX Edge installation requirements. See [NSX Edge Installation Requirements](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/installation/GUID-11417AA2-5EBC-49C7-8A86-EB94604261A6.htmlGUID-11417AA2-5EBC-49C7-8A86-EB94604261A6).
5. Collect the IP addresses and FQDNs for the provisioned IBM Cloud Bare Metal Servers for Virtual Private Cloud VLAN interfaces from the [previous tutorial](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-nsx-t-hostsvpc-bm-vmware-nsx-t-vlannics).







 Step 2: Deploy NSX-T managers and for a cluster 

Follow the recommended order of procedures to deploy NSX-T on IBM Cloud Bare Metal Servers for Virtual Private Cloud with VMware ESXi.
* [Prerequisites for installation](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-prereq-intro)
* [Red Hat OpenShift NSX configuration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-nsxedge-intro)
* [Red Hat OpenShift 4.7 user provider infrastructure installation](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-install-intro)
* [Red Hat OpenShift 4.7 additional configuration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-config-intro)
For more information, see [Promotions for VMware Solutions services](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservicesvc_addingservices-service-promotions).

The service versions available for deployment are VMware Aria Operations 8.12 and VMware Aria Operations for Logs 8.12.



 Technical specifications for VMware Aria Operations and VMware Aria Operations for Logs 

For more information about resource requirements and capacity checking for some services, see [Resource requirements for services](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservicesvc_addingservices-resource-requirements).

The following VMware Aria components are ordered and included in the service:



* VMware Aria Operations Enterprise Edition
* VMware Aria Operations for Logs Enterprise Edition



For more information about the design, requirements, and preconfigured management packs, see [Operations management architecture overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-opsmgmt-arch).





 Considerations when you delete VMware Aria Operations and VMware Aria Operations for Logs 

Review the following considerations before you delete the service:



* Only the virtual machines (VMs) that were deployed during the initial installation of VMware Aria Operations and VMware Aria Operations for Logs are deleted. Any node that is deployed after the installation is not cleaned up.
* Before you delete the service, you must remove any personal VM from storage that is deployed with this service. VMware Aria Operations and VMware Aria Operations for Logs orders only personal VMs if it’s not vSAN.
* The VXLAN, DLR, and the Edge Gateway that were created during the initial deployment of VMware Aria Operations and VMware Aria Operations for Logs is deleted. The VMs that you deployed on VXLAN lose connectivity after the deletion of VMware Aria Operations and VMware Aria Operations for Logs begins.
* UI
* Terraform







 Deploying SAP NetWeaver 7.x and Db2 on an existing IBM Cloud® VPC (Terraform and Ansible) 

Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud Virtual Private Cloud (VPC) infrastructure resources so that you can rapidly build complex, cloud environments. IBM Cloud VPC infrastructure consists of SAP certified hardware that uses Intel Xeon CPUs and additional Intel technologies.

You can use Terraform scripts to create a single-tier VPC and create the SAP and Db2 infrastructure on the VPC. The Terraform scripts use the VPC information that you provide and then call the Ansible playbook to create the SAP architecture on the specified VPC.

You have three deployment methods to choose from:



* Terraform scripts run from the CLI on your bastion server
* Catalog Tile user interface accessed from the IBM Cloud Catalog
* Schematics user interface accessed from the menu on your cloud dashboard.





 What is created 

The scripts use the information that you provide for an existing VPC and deploy NW7.X with Db2. For more information about this architecture, see [SAP NetWeaver 7.x on UNIX with Db2 on IBM Cloud® VPC](https://cloud.ibm.com/docs/sap?topic=sap-sap-refarch-nw-db2). You specify the information for the VPC to use in the input.auto.tfvars file.

The scripts call the Ansible Playbook to install the SAP architecture.





 Script files 

The configuration and script files are provided on GitHub. Each supported interface for the SAP solution installation has its own folder in the GitHub repository:



* Using the Schematics user interface on IBM Cloud® - [GitHub repository for IBM Schematics](https://github.com/IBM-Cloud/sap-netweaver-abap-db2-standard/tree/main/schematics).







 Terraform deployment
* Create and modify IBM Cloud VPC services, virtual server instances, networks, network prefixes, storage volumes, SSH keys, and security groups of this VPC.
* Create and modify Power® Systems Virtual Server services, virtual server instances, networks, storage volumes, ssh keys of this Power® Systems Virtual Server.
* Create and modify IBM Cloud direct links and IBM Cloud Transit Gateway.
* Access existing Object Storage services.



For information about configuring permissions, contact your IBM Cloud account administrator.





 Access for IBM Cloud projects 

You can use IBM Cloud projects as a deployment option. Projects are designed with infrastructure as code and compliance in mind to help ensure that your projects are managed, secure, and always compliant. For more information, see [Learn about IaC deployments with projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-understanding-projects).

You need the following access to create a project and create project tooling resources within the account. Make sure that you have the following access:



* The Editor role on the Projects service
* The Editor and Manager role on the Schematics service
* The Viewer role on the resource group for the project



For more information, see [Assigning users access to projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-access-project).







 Upload SAP software installation packages 

Upload SAP software installation packages and SAP maintenance planer XML files to an existing Object Storage bucket.

To configure access to these software packages from a running virtual server instance, you need following information:



* Object Storage endpoint
* Object Storage bucket name
* Object Storage HMAC access key
* Object Storage HMAC secret access key
To accomplish this, you need to configure the NIM (network boot) server. To define the NIM server with resources required for migration, complete the following steps:



1. Define the VM as a NIM master. For more information, see [Setting up a Network Installation Management (NIM) server](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-provisioning-nim).
2. Create a License Program Products (LPP) source by using an image repository that contains the images. Stock images already contain the ISO and LPPs that are found on the base media, so create the LPP source and NIM resources from [Installing optional software products from the AIX stock image](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-using-ess-isoinstalling-aix-stock-image).
3. Customize any additional installation resources.
4. Define the AIX 7.1 VM as a NIM client.
5. Perform the installation for NIM migration.



For more information on creating and defining a NIM master, setting an LPP source and spot, see [Migrating from AIX 7.1](https://cloud.ibm.com/media/docs/downloads/power-iaas/Migration_from_AIX7_1.pdf).







 IBM i migration strategies 

Learn about migration strategies that are specific to IBM i systems.



 Backup Recovery and Media Services (BRMS) and Cloud Storage (ICC) 

Image catalogs are created out of objects that are backed up by using optical devices. These catalogs must be restored on the Power Systems Virtual Server instance by using some of the migration strategies, such as MDM, COS, Aspera, and NFS server. BRMS is an IBM i product that can be used to automate activities that help define and process your backup, recovery, and media management operations. The ICC product can be integrated with BRMS to move and retrieve objects from remote locations, including COS.

The following steps detail how to migrate your OS and data from an on-premises system to the Power Systems Virtual Server environment.
Why is my Portieris cluster image security enforcement installation canceled? 

Virtual Private Cloud

Classic infrastructure

 What’s happening 

Portieris image security enforcement add-on does not install. You see a master status similar to the following:

Image security enforcement update cancelled. CAE008: can't enable Portieris image security enforcement because the cluster already has a conflicting image admission controller installed. For more information, see the troubleshooting docs: 'https://ibm.biz/portieris_enable'

 Why it’s happening 

Your cluster has a conflicting image admission controller already installed, which prevents the image security enforcement cluster add-on from installing.

When you have more than one image admission controller in your cluster, pods might not run.

Potential conflicting image admission controller sources include:



* The deprecated container image security enforcement Helm chart.
* A previous manual installation of the open source [Portieris](https://github.com/IBM/portieris) project.



 How to fix it 

Identify and remove the conflicting image admission controller.



1. Check for existing image admission controllers.



* Check if you have an existing container image security enforcement deployment in your cluster. If no output is returned, you don't have the deployment.

oc get deploy cise-ibmcloud-image-enforcement -n ibm-system

Example output

NAME READY UP-TO-DATE AVAILABLE AGE
cise-ibmcloud-image-enforcement 3/3 3 3 129m
* Check if you have an existing Portieris deployment in your cluster. If no output is returned, you don't have the deployment.

oc get deployment --all-namespaces -l app=portieries

Example output

NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE
portieris portieris 3/3 3 3 8m8s



2. Uninstall the conflicting deployment.

oc delete deployment <deployment> -n <namespace>
3. Confirm that conflicting admission controllers are removed by checking that the cluster no longer has a mutating webhook configuration for an image admission controller.
* [SAP Help Portal - SAP Adaptive Server Enterprise (ASE) Installation and Upgrade Guide for IBM AIX](https://help.sap.com/viewer/07e2d10774874e3bb4d991ef08d678e8/latest/en-US)
* [SAP Help Portal - SAP Adaptive Server Enterprise (ASE) Installation and Upgrade Guide for Windows](https://help.sap.com/viewer/36031975851a4f82b1022a9df877280b/latest/en-US)



* [SAP Note 1748888 - Installing Systems Based on NW 7.3 and Higher: SAP ASE](https://launchpad.support.sap.com//notes/1748888)
* [SAP Note 2489781 - SAP ASE 16.0 SP03 Supported Operating Systems and Versions](https://launchpad.support.sap.com//notes/2489781)



For a current overview of the combinations of SAP ASE, SAP NetWeaver (or other SAP components), and operating systems - see the [Product Availability Matrix (PAM)](http://support.sap.com/pam).

SAP ASE and SAP NetWeaver on UNIX/Linux:



* [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:
Release notes 

Use the release notes to learn about the latest changes to IBM® WebSphere® Application Server. The notes are grouped by release date or version number.



 20 October 2021: WebSphere Application Server 2.1.0 on IBM Cloud 

Version 2.1.0 changes the Version 1.0 product:



* The product name was shortened to WebSphere Application Server from WebSphere Application Server for VSI.
* The product continues to offer the WAS.Base and WAS.Cell topologies for WebSphere Application Server traditional environments. The Liberty environments are no longer offered.
* Installation uses VSI images with the latest version of WebSphere traditional Version 9.0.5 pre-installed on Red Hat® Enterprise Linux® 8.4.
* Installation is now quicker and simpler. You no longer must set up virtual private clouds (VPCs) or provision virtual server instances (VSIs).



For information about the 2.1.0 product, see the following documentation:



* [Topologies](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-topologies) describes the product and available topologies.
* [Deploying IBM WebSphere Application Server](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-getting-started) describes how to install a WebSphere Application Server traditional environment on one or more VSIs.
* [Migrating your workload](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-migrating) points to information that you can follow to migrate your existing WebSphere Application Server traditional applications to VSIs.
* [Troubleshooting](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-troubleshoot) describes problems that you might encounter when you install and use the product and provides instructions for fixing the problems.







 5 February 2021: WebSphere Application Server 1.0.1 on IBM Cloud 

Version 1.0.1 provides enhancements and a command change:



* Automatic restarting of services after a VSI reboots.
Use [Endpoints and storage locations](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpoints) to find the S3 Host that matches the location where your bucket's created. In the example, it's s3.eu-de.cloud-object-storage.appdomain.cloud. Leave S3 region blank. It's taken from the endpoint's URL, for example, eu-de.

In a production environment, you should use the private endpoint.
5. Leave connection timeout in second blank. It will default to 180 seconds.
6. Enter the bucket and directory names you entered in [Creating the bucket and the directory](https://cloud.ibm.com/docs/sap?topic=sap-rhos-datahubrhos-create-bucket) for S3 bucket and directory. In the example, it's sdh-cos-vora-bucket/checkpoints.
7. Enter yes to validate the checkpoint store.











 Running the installation shell script 

We recommend manually installing the SAP Data Hub.



 Before you begin 

Follow the steps in the Red Hat article, section [4.5 Manual Installation using an installation script (manual)](https://access.redhat.com/articles/3630111manual), to get the SAP Data Hub Foundation image. Before you can unzip the SAP Data Hub Foundation image you must install unzip.

yum install unzip

The command line parameters provide IBM Cloud specific information for the SAP installation script. For the installation script, you need this information from the previous tasks, the:



* default storage provider
* image registry, including the registry namespace and pull secret
* domain to be used for the auto-generated certificates and the enablement of the [Kaniko image builder](https://access.redhat.com/articles/3630111kaniko).



The default domain for Red Hat® OpenShift® on IBM Cloud® clusters on IBM Cloud is <region>.containers.cloud.ibm.com.
In the Change destination folder dialog box, browse to the new installation folder, or type it in the Folder name box. Click OK. On the Destination Folder page, click Next.



6. On the Register Agent with Portal Page, specify the following information.



* In the Network address field, type cloudbackupregister.service.softlayer.com.
* In the Port field, type 8086.
* In username field, type the IBM Cloud Backup for Classic username for managing the VRA. For more information about viewing the username, see [Managing username and password for the Cloud Backup service](https://cloud.ibm.com/docs/Backup?topic=Backup-changePassword).
* In Password field, type the password of the specified IBM Cloud Backup for Classic user.



7. Click Next. When the installation is complete, click Finish.







 Configuring the vSphere Recovery Agent 

After VRA is installed, you need to configure it in the Cloud Backup Portal.



1. Log in to the Portal. For more information about how to access the Portal, see the [Getting started tutorial](https://cloud.ibm.com/docs/Backup?topic=Backup-getting-startedaccessingPortal).
2. On the Computers Tab, select the server that you want to back up.
3. Configure your vault information.

Vault information can be configured in two ways: Automatically or Manually. If the agent is being configured for the first time, then it can be configured by using the [Automatic configuration](https://cloud.ibm.com/docs/Backup?topic=Backup-VRAVRAautoconfig) option. If the computer was previously registered with a Vault, then the automatic configuration doesn't work and the vault needs to be [configured manually](https://cloud.ibm.com/docs/Backup?topic=Backup-VRAVRAmanualconfig).
4.