vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Each server must have its own IBM Cloud Backup for Classic Account. One IBM Cloud Backup for Classic license cannot be used for multiple servers.





 Step 2: Installing the IBM Cloud Backup for Classic agent 

IBM Cloud Backup for Classic Agent is supported on the following Operating Systems.

Windows

- Oldest supported version of the backup agent is 8.32.



* Windows® Server 2019
* Windows® Server 2016
* Windows® Server 2012 R2
* Windows® Server 2012
* Windows® Server 2008 R2
* Windows® Server 2008



Windows 2019 does successfully back up with the Windows agent version 8.60. However, the server shows up in the Backup Portal as Windows 2016. Full backup functions were tested with version 8.60. Do not upgrade to a higher version such as 8.70 because it disables the management of the agent until the Backup Portal is upgraded. The customer can also install Central Control to manage the backup agent. The latest version of Central Control is available to download from [here](http://downloads.service.softlayer.com/evault/CentralControl/). You must install .NET 3.5 before you install the Central Control application. .Net can be installed by using the Add Roles and Features Wizard from the Server Manager. Multiple.NET can be installed at the same time.

Linux

- Oldest supported version of the backup agent is 8.50. BMR backups are not supported.



* CentOS 8.x (It requires backup agent version 8.83.)
* CentOS 7.x
* Debian GNU/Linux® 9.x
* Debian GNU/Linux® 8.x
* RHEL 8.x (It requires backup agent version 8.83.)
* RHEL 7.x
* Ubuntu Linux® 18.04 (It requires backup agent version 8.62 or newer.)
* Ubuntu Linux® 16.04
* Ubuntu Linux® 14.04



Follow the instructions appropriate for your OS,



Linux

[Installing the backup client in Linux®](https://cloud.ibm.com/docs/Backup?topic=Backup-InstallinLinux)
New goals were added to the Security and Compliance Center profiles that your resources are automatically scanned for. For detailed descriptions of the new goals, you can review the IBM Best Practices Controls 1.0 profile. All the goals with ID's in the following ranges are new.



* Goal ID's: 3000510 - 3000525 and 3000640.







 22 July 2021 

New Posture Management API endpoints
: With this release, 9 new API endpoints for the Posture Management API are available. To get started, see the [Posture Management API documentation](https://cloud.ibm.com/apidocs/security-compliance/posture).

Consolidated SDK package
: To make it easier to programmatically access the API from your code, Security and Compliance Center SDK packages are now available. The SDKs implement best practices for using the API and reduces the amount of code that you need to write. For more information, see the documentation for the following APIs:



* [Admin](https://cloud.ibm.com/apidocs/security-compliance-admin)
* [Configuration Governance](https://cloud.ibm.com/apidocs/security-compliance-config)
* [Posture Management](https://cloud.ibm.com/apidocs/security-compliance/posture)



New goals
: You might notice that your compliance score changed even though you didn't update any of your configurations. New goals were added to the Security and Compliance Center profiles that your resources are automatically scanned for. For detailed descriptions of the new goals, you can review the IBM Best Practices Controls 1.0 profile. All the goals with ID's in the following ranges are new.



* Goal ID's: 3000509







 24 June 2021 

New version of the IBM Cloud for Financial Services profile
: Version 0.1.1 of the IBM Cloud for Financial Services profile is now available with new goals and controls. For more information, see the [IBM Cloud for Financial Services profile change log](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-fs-change-log).





 22 June 2021 

Tanium integration
The Cloud Databases CLI plug-in requires [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) to be installed.



 The IBM Cloud CLI 

The IBM Cloud CLI is a general-purpose developer tool that provides access to your IBM Cloud account and services through a command-line interface.

An introduction and installation instructions are available on the [IBM Cloud CLI Getting Started page](https://cloud.ibm.com/docs/cli?topic=cli-getting-started). If you install the CLI from the cURL command that is provided, you get a selection of extra plug-ins and extensions for multiple IDEs.

Install the stand-alone package from the [Installing the stand-alone IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli) page.

Access to services via IBM Cloud CLI is governed through Identity and Access Management. In order to use the CLI to view or manage a service (or to grant privileges to another user on your account), you must set the correct permissions. For more information about IAM management, see the [IAM Getting Started tutorial](https://cloud.ibm.com/docs/account?topic=account-access-getstarted)





 Installing the Cloud Databases CLI plug-in 

Once you have the IBM Cloud CLI, [log in](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login) and install the Cloud Databases plug-in, using a command like:

ibmcloud plugin install cloud-databases

For a list of commands and usage information, use a command like:

ibmcloud cdb help





 ibmcloud cdb help 

On its own, the ibmcloud cdb help command displays the available top-level commands. When followed by another command, it displays specific help for that command.

ibmcloud cdb help [<command>]



 Command options 

No command-specific options.





 Examples
Please see [Access Control List](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-aclacl) and [HTTP/S Route Control using the ACL](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-aclacl-route-control) for more information.





 Set password on the Secure Gateway Client UI 

It is recommended to set the UI password to restrict the access of the Secure Gateway Client UI. Please see [Interacting with the Client](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-client-interactingclient-interacting) for more details about how to set the password using startup configuration or interactive commands on Secure Gateway Client terminal command line.







 What is gateway migration? Why is the domain changed after 2018 December? 

After 2018 December maintenance, the cloud host of Secure Gateway is getting renamed to use the securegateway.appdomain.cloud instead of integration.ibmcloud.com, and use the securegateway.cloud.ibm.com for gateway authentication instead of bluemix.net. For backward compatibility, the existing gateway will keep using the old domain until the gateway is migrated, and the SG client v180fp9 and former will keep using bluemix.net for gateway authentication. To support this change, there is a migrate button on the gateway panel.

After the migration, the cloud host of the on-premises destinations will change to use the new domain, the users/applications will need to update to send the request to the new cloud host.

Currently the cloud host migration is not mandatory and there is not an exact date about when the old domain will be out of support, but once this is settled, the customer who are still using the old domain name will be notified.

For gateway authentication endpoint, currently bluemix.net has been deprecated, if you are using REST API or SDK, please ensure you are connecting to [new endpoints](https://cloud.ibm.com/apidocs/secure-gatewayintro) instead of bluemix.net. For Secure Gateway Client, please ensure your Secure Gateway Client does not fall more than 3 versions behind.
Please see [Access Control List](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-aclacl) and [HTTP/S Route Control using the ACL](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-aclacl-route-control) for more information.





 Set password on the Secure Gateway Client UI 

It is recommended to set the UI password to restrict the access of the Secure Gateway Client UI. Please see [Interacting with the Client](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-client-interactingclient-interacting) for more details about how to set the password using startup configuration or interactive commands on Secure Gateway Client terminal command line.



* What is gateway migration? Why is the domain changed after 2018 December?

After 2018 December maintenance, the cloud host of Secure Gateway is getting renamed to use the securegateway.appdomain.cloud instead of integration.ibmcloud.com, and use the securegateway.cloud.ibm.com for gateway authentication instead of bluemix.net. For backward compatibility, the existing gateway will keep using the old domain until the gateway is migrated, and the SG client v180fp9 and former will keep using bluemix.net for gateway authentication. To support this change, there is a migrate button on the gateway panel.

After the migration, the cloud host of the on-premises destinations will change to use the new domain, the users/applications will need to update to send the request to the new cloud host.

Currently the cloud host migration is not mandatory and there is not an exact date about when the old domain will be out of support, but once this is settled, the customer who are still using the old domain name will be notified.

For gateway authentication endpoint, currently bluemix.net has been deprecated, if you are using REST API or SDK, please ensure you are connecting to [new endpoints](https://cloud.ibm.com/apidocs/secure-gatewayintro) instead of bluemix.net. For Secure Gateway Client, please ensure your Secure Gateway Client does not fall more than 3 versions behind.
* SLES 15 SP4 for SAP NetWeaver (SLES15-SP4-SAP-NETWEAVER)



If you opt for a Linux subscription directly from Red Hat or SUSE, you will need to bring your own image. Power Systems Virtual Server supports custom images for following Linux distributions:

General purpose:



* SLES 12 SP4 or later and SLES 15 SP1 or later
* RHEL 8.4 or later



For SAP workloads:



* SLES 12 SP4 or later and SLES 15 SP1 or later
* RHEL 8.1 or later



To view the certification details in the Red Hat catalog, see [IBM Power System E980 (9080-M9S)](https://catalog.redhat.com/cloud/instance-types/detail/5636201) and [IBM Power System S922 (9009-22A)](https://catalog.redhat.com/cloud/instance-types/detail/5636281). For additional support, refer to the distribution (distro). For instructions, see [Installing and configuring cloud-init on Linux](https://www.ibm.com/support/knowledgecenter/en/SSXK2N_1.4.4/com.ibm.powervc.standard.help.doc/powervc_install_cloudinit_hmc.html).





 Can I use my own AIX, IBM i, or Linux image? 

Yes. This function is known as bring your own image. For more information, see [Deploying a custom image within a Power Systems Virtual Server](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-deploy-custom-image).





 What versions of stock images are available? 

For each major version (example: Technology Level) of the operating system (OS) that is enabled through the offering, Power Systems Virtual Server provides a single stock image. PowerVS typically provides stock images for the last three major versions of the supported OS. Any update to the OS stock image is planned only when the image level is certified for PowerVM™ environment.
1. Create the master image. The master image for virtual machines can be created through XenCenter, which you installed in [Step 4. Access and Configure the Citrix Hypervisor](https://cloud.ibm.com/docs/citrix-daas?topic=citrix-daas-post-provisioning-cvadaccess-citrix-hypervisor).
2. Install XenServer Tools on the guest operating system of the virtual machine created. For more information on XenServer, see [Installing XenServer Tools](https://docs.citrix.com/en-us/xencenter/7-1/vms-installtools.html)
3. Join the virtual machine master image to the Active Directory server domain by using these [instructions](https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/join-a-computer-to-a-domain).
4. Add the proxy server settings on your master image.



1. The settings can be copied from the Cloud Connector server to the Master VM Image. Follow the instructions to set up [proxy settings](https://docs.microsoft.com/en-us/troubleshoot/browsers/use-proxy-servers-with-ie).
2. Using the instructions in [proxy settings](https://docs.microsoft.com/en-us/troubleshoot/browsers/use-proxy-servers-with-ie), paste the copied settings to your Master VM image.



5. While connected to the Master VM Image, enter this command on an elevated command prompt of the Master VM Image:

netsh winhttp import proxy source=ie
6. Install the VDA on the virtual machine.
For part numbers, see [Passport Advantage part numbers](https://www.ibm.com/support/knowledgecenter/en/SSFC4F_1.3.0/about/part_numbers.html).
* You must have a supported version of OpenShift Container Platform installed by using IBM Cloud Kubernetes Service so that the managed OpenShift service is supported. For the list of supported versions, see [Supported OpenShift versions and platforms](https://www.ibm.com/support/knowledgecenter/en/SSFC4F_1.3.0/install/supported_os.html).
* You must have a pre-configured StorageClass in OpenShift that can be used for installing the IBM Cloud Pak for Multicloud Management.
* You must have the required user and resource group permissions to install the IBM Cloud Pak for Multicloud Management:



* You must have permission as an admin user on the cluster where you are installing the IBM Cloud Pak for Multicloud Management.
* You must have at least viewer access permission to the resource group that includes the cluster where you are installing the IBM Cloud Pak for Multicloud Management. Ensure that this resource group exists in IBM Cloud and that the user ID that is used in IBM Cloud Provider cloud connection has access to this resource group.







 Minimum hardware requirements 



 Nodes Memory CPU 

 3 32 GB 16 cores 



Notes: If you are going to install the Monitoring Module and Terraform & Service Automation Module with the IBM Cloud Pak for Multicloud Management, you need another two nodes.





 Minimum storage requirements 

Mandatory: 2 PV



 Component PV 

 MongoDB 1 
 IBM Multicloud Manager etcd 1 



Optional: 4 PV



 Component PV 

 Logging 1 
 VA 3 









 Step 1. Configure your installation environment 

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

1. Select the Red Hat OpenShift cluster where you want to deploy the 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.
Updated Node.js buildpack v3.21
: Beginning with the latest Node.js 6.x and 8.x versions in this release, the SDK for Node.js buildpack is based on the Node.js community release. With this change, the Node.js OpenSSL FIPS module in the buildpack will no longer be updated. The current OpenSSL FIPS module and IBM SDK for Node.js builds are eligible for removal as of 24 August 2018. For more information, see the [Aligning the Node.js Buildpack to Community Runtimes](https://www.ibm.com/cloud/blog/announcements/aligning-the-node-js-buildpack-to-community-runtimes) blog post.

The SDK for Node.js buildpack v3.21 provides IBM SDK for Node.js versions 4.8.5, 4.8.7, 6.13.0 and 8.9.4 and Node.js community versions 6.14.3 and 8.11.3. The default is latest 6.x, so it is currently 6.14.3.

This release also includes fixes for the following security vulnerability:



* [CVE-2018-0739](https://www.ibm.com/support/pages/node/715221)







 2 July 2018 

Updated Liberty buildpack v3.23-20180628-1052
: The default Liberty runtime version was updated to the 18.0.0.2 release.



* The IBM JRE version was updated to 8 SR5 FP16.







 8 June 2018 

Updated Liberty buildpack v3.22-20180601-1200
: The monthly Liberty runtime version was updated to 2018.6.0.0.



* The IBM JRE version was updated to 8 SR5 FP15.







 1 June 2018 

Updated Node.js buildpack v3.20.2
: The SDK for Node.js buildpack v3.20.2 adds Dynatrace Managed PaaS integration for the current Node.js runtimes.





 17 May 2018
Cluster nodes that are deployed with this offering include IBM Spectrum Symphony 7.3.2 Advanced Edition. See the following for a summary of the features associated with each edition: [IBM Spectrum Symphony editions](https://www.ibm.com/docs/en/spectrum-symphony/7.3.1?topic=foundations-spectrum-symphony-editions).

If the cluster uses Spectrum Scale storage, the storage nodes include IBM Spectrum Scale 5.1.7.0 software. For more information, see the [IBM Spectrum Scale](https://www.ibm.com/docs/en/spectrum-scale/5.1.3) product documentation.
* What locations are available for deploying VPC resources?

Available regions and zones for deploying VPC resources, and a mapping of those to city locations and data centers can be found in [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).
* What permissions do I need in order to create a cluster using the offering?

Instructions for setting the appropriate permissions for IBM Cloud services that are used by the offering to create a cluster can be found in [Granting user permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources), [Managing user access for Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-access), and [Assigning access to Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-assign-access).
* How do I SSH among nodes?

All of the nodes in the HPC cluster have the same public key that you register at your cluster creation. You can use ssh-agent forwarding, which is a common technique to access remote nodes that have the same public key. It automates to securely forward private keys to remote nodes. Forwarded keys are deleted immediately after a session is closed.

To securely forward private keys to remote nodes, you need to do ssh-add and ssh -A.
(Deprecated) Installing the cluster autoscaler Helm chart in your cluster 

The cluster autoscaler Helm chart is deprecated. For the latest version of the cluster autoscaler, [install the add-on](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-install-addon)

The cluster autoscaler Helm chart is available for standard classic and VPC clusters that are set up with public network connectivity.

Install the IBM Cloud cluster autoscaler plug-in with a Helm chart to autoscale worker pools in your cluster.



1. [Prepare your cluster for autoscaling](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-classic-vpc).
2. [Follow the instructions](https://cloud.ibm.com/docs/containers?topic=containers-helminstall_v3) to install the Helm version 3 client on your local machine.
3. Add and update the Helm repo where the cluster autoscaler Helm chart is.

helm repo add iks-charts https://icr.io/helm/iks-charts

helm repo update
4. Decide if you want to [customize the cluster autoscaler settings](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helmca_chart_values), such as the worker pools that are autoscaled, or the amount of time that the cluster autoscaler waits before scaling worker nodes up or down. You can customize your settings by using the --set option in the helm install command. Depending on the settings that you want to customize, you might need to prepare multiple --set options before you can install the Helm chart. For example, you might want to autoscale your default worker pool by preparing the following --set option. Note: If your default command line shell is zsh, start a bash session before running the following command.
* Whether to migrate the existing SAP ECC system to SAP S/4HANA, or build from the ground up on cloud
* What your current sizing of your SAP Systems are, and their projected increases
* How to align your move to cloud and SAP rollouts to meet business needs. For example, connectivity to existing applications in on-premises data centers, intermittent or offline locations such as factories or front-line business operators, mobile device connectivity while retaining security and more.



The following documentation sections provide details to help understand how IBM Cloud® for SAP can empower your business and help you to make informed decisions for your IaaS, PaaS, SaaS, and SAP Partner solution choices.
FAQs 



 What Slurm version is used in cluster nodes deployed with this offering? 

Cluster nodes that are deployed with this offering include Slurm 19.05.5-1 Advanced Edition.





 What locations are available for deploying VPC resources? 

Available regions and zones for deploying VPC resources, and a mapping of those to city locations and data centers can be found in [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).





 What permissions do I need in order to create a cluster using the offering? 

Instructions for setting the appropriate permissions for IBM Cloud services that are used by the offering to create a cluster can be found in [Granting user permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources), [Managing user access for Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-access), and [Assigning access to Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-assign-access).





 How do I SSH among nodes? 

All of the nodes in the HPC cluster have the same public key that you register at your cluster creation. You can use ssh-agent forwarding, which is a common technique to access remote nodes that have the same public key. It automates to securely forward private keys to remote nodes. Forwarded keys are deleted immediately after a session is closed.

To securely forward private keys to remote nodes, you need to do ssh-add and ssh -A.

[your local PC]$ ssh-add {id_rsa for slurm cluster}
[your local PC] ssh -A -J root@jumpbox_fip root@management_private_ip
...
[root@management] ssh -A worker_private_ip

For Mac OS X, you can persist ssh-add by adding the following configuration to .ssh/config:

Host 
  UseKeychain yes
Select the entity or entity and value to which you want to add the annotation.

In this example, mobile phones is being added as an annotation for the @product entity value and as a synonym for the @product:device entity value.

Create at least 10 annotations for each contextual entity; more annotations are recommended for production use.
7. If none of the entities are appropriate, you can create a new entity by adding its name. Then choose the {entity_name}(create new entity) option from the list.

![Shows how to add a new @location entity from annotation page](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/oe-add-entity.png)
8. Repeat this process for each entity mention that you want to annotate.

Be sure to annotate every mention of an entity type that occurs in any user examples that you edit. See [What you don't annotate matters](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-entitiesentities-counter-examples) for more details.
9. Now, click the annotation you just created. A box is displayed that says, Go to: {entity-name}. Clicking that link takes you directly to the entity.

![Verify value computer for product entity](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/oe-go-to-entity.png)

The annotation is added to the entity you associated it with, and the system begins to train itself on the new data.

The term you annotated is added to the entity as a new dictionary value.