vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Check that the RHEL High Availability repository is enabled.

On both nodes, use the followings command.

dnf repolist

If the HA repository is missing, use the following commands to enable it:

subscription-manager repos --enable="rhel-8-for-ppc64le-highavailability-e4s-rpms"

dnf clean all

dnf repolist





 Installing the RHEL HA Add-On software packages 

Install the required software packages.

On both nodes, run the following command.

dnf install -y pcs pacemaker fence-agents-ibm-powervs

Make sure that you install the minimal version of the fence-agents-ibm-powervs package dependent on your Red Hat Enterprise Linux release:

RHEL 8.4
: fence-agents-ibm-powervs-4.2.1-65.el8_4.11.noarch.rpm ([https://access.redhat.com/errata/RHBA-2023:0503](https://access.redhat.com/errata/RHBA-2023:0503))

RHEL 8.6
: fence-agents-ibm-powervs-4.2.1-89.el8_6.8.noarch.rpm ([https://access.redhat.com/errata/RHBA-2023:0428](https://access.redhat.com/errata/RHBA-2023:0428))







 Configuring a RHEL HA Add-On cluster 



 Configuring firewall services 

Add the high availability service to the RHEL firewall if firewalld.service is installed and enabled.

On both nodes, run the following commands.

firewall-cmd --permanent --add-service=high-availability

firewall-cmd --reload





 Starting the PCS daemon 

Start the PCS daemon, which is used for controlling and configuration of RHEL HA Add-On clusters through PCS.

On both nodes, run the following commands.

systemctl enable --now pcsd.service
"id": "4551a68d-b45d-4443-b6b3-aba7a4a18c98",
"name": "my-virtual-network-interface",
"resource_type": "virtual_network_interface"
},
"vpc": {
"crn": "crn:[...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/5821d0c4-a089-4957-b5fa-03b7ac636c15",
"id": "5821d0c4-a089-4957-b5fa-03b7ac636c15",
"name": "my-vpc",
"resource_type": "vpc"
}
}





 View a source file share for a replica file share with the API 

Make a GET /shares/{replica_id}/source request and specify the replica share ID to retrieve the source file share details.

curl -X GET "$vpc_api_endpoint/v1/shares/$replica_id/source?version=2023-07-05&generation=2&maturity=beta" -H "Authorization: $iam_token"

A successful response provides details of the source file share. Notice that the replication role is source.

{
"access_control_mode": "security_group",
"created_at": "2023-07-05T22:58:49.000Z",
"crn": "crn:[...]",
"encryption": "provider_managed",
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/207721a9-aff9-4b16-9823-fe68096aeac3",
OpenVPN server 2.5.6-r1-IKS-647 2.5.8-r0-IKS-673-amd64 Remediate [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286), [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304), [CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450), [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215). 
 OpenVPN Operator image v1.4.13 v1.4.20 Update ansible-operator to v1.26.1 to fix CVEs. 
 Portieris admission controller v0.12.6 v0.13.3 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.13.3). 
 Red Hat OpenShift on IBM Cloud. 4.11.22 4.11.27 See the [Red Hat OpenShift on IBM Cloud release notes](https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.htmlocp-4-11-27). 
 Red Hat OpenShift on IBM Cloud Control Plane Operator v4.11.0-20230123 v4.11.0-20230220 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.11.0%2B20230220).
Restoring files and folders 

You can restore file and folders from a protected Windows® VM by using the vSphere Recovery Agent (VRA). You can restore files and folders from more than one VM at same time. You can't restore files and folders from Linux® VMs with VRA.

During a files and folder restore, volumes from the selected VM are mounted as drives on the server where the VRA is running. You can then share some or all of the mounted drives so that users can copy files and folders from the drives. You can also sign in to the VRA server, and copy files and folders from the mounted drives.

Files and folders on the disks are accessible to anyone on the VRA system, including non-Admin users. If you're concerned about security, secure the Agent server and prevent users from logging in to the server locally.



1. On the navigation bar, click Computers. The grid lists available computers.
2. Find the vSphere environment with the VM that you want to restore, and expand its view by clicking the row.
3. Click Jobs.
4. Find the backup job with the VM that you want to restore, and click Restore in the job’s Select Action menu.
5. In the Choose what you want to restore dialog, select Files and Folders.
6. Click Continue. The restore dialog shows the most recent safe-set for the job.



* To restore data from another resource, click source in the Source Device list (Vault).
* To restore from an older safe-set, click Browse safe sets. In the calendar that appears, click the date of the safe-set from which you want to restore. Then, click the specific safe-set from which you want to restore.



7. In the Items to Restore panel, select the VM with the files or folders that you want to restore.
8. In the Encryption Password field, enter the data encryption password.
9. In the Idle Time field, enter the number of minutes of inactivity after which the share drive is to automatically unshare.
OpenVPN server 2.5.6-r1-IKS-647 2.5.8-r0-IKS-673-amd64 Remediate [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286), [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304), [CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450), [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215). 
 OpenVPN Operator image v1.4.13 v1.4.20 Update ansible-operator to v1.26.1 to fix CVEs. 
 Portieris admission controller v0.12.6 v0.13.3 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.13.3). 
 Red Hat OpenShift on IBM Cloud. 4.8.55 4.8.57 See the [Red Hat OpenShift on IBM Cloud release notes](https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.htmlocp-4-8-57). 
 Red Hat OpenShift on IBM Cloud Control Plane Operator v4.8.0-20230123 v4.8.0-20230220 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.8.0%2B20230220).
For the purposes of this tutorial, the following steps describe how to edit the description of the readme file.



1. Click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/edit-tagging.svg).
2. Copy and paste the contents of the [readme file template](https://cloud.ibm.com/media/docs/downloads/software/sw-readme-tab-template.md) and make updates as needed.
3. Click Save > Next.







 Step 7: Validate the virtual server image 

Validating your virtual server image involves running a test deployment of your software. Validating your image proves that it's provisionable with your VPC. The first image you added to your product is validated. Additional regions are not included in this validation.



1. Configure the validation target by selecting a VPC, an SSH key, a subnet, and a profile. Then, cilck Next.
2. Optionally, configure the Schematics workspace by specifying a name and selcting a resource group and a Schematics region. Then, click Next.

In the Tags field, you can enter a name of a specific tag to attach to your virtual server image. Tags provide a way to organize, track usage costs, and manage access to the resources in your account.
3. In the Validation version section, select I have read and agree to the following license agreements.
4. Click Validate.

To monitor the progress of the validation process, click View logs.







 Step 8: Manage compliance (optional) 

The Security and Compliance Center scans determine adherence to regulatory controls as defined in a profile. Controls are safeguards that are used to meet security and compliance requirements. Only controls that are supported by Security and Compliance Center, formatted correctly, and validated by Code Risk Analysis and Security and Compliance Center scans appear in the catalog.
In this case, contact IBM Support for the root user ID password for PSC and vCenter Server.
* Confirm that you have a [My VMware](https://my.vmware.com) user ID for which to download the required binary files to upgrade. If you don't, contact IBM Support with the upgrade support ticket ID.
* Confirm that VUM is configured to reach [https://www.vmware.com](https://www.vmware.com) to download patches. If it can't be configured because of security policies, then you must manually download the most recent patch sets and upload them into VUM. For more information, see [VMware Update Manager introduction](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vum-introvum-intro).







 Supported upgrade paths 

The following table is a summary of the supported upgrade paths:



Table 1. Upgrade paths for VMware Solutions offerings

 Deployment offering Supported paths Unsupported paths 

 vCenter Server (VCS) with NSX-V instances with vSphere V6 Preferred path <br>Provision a new vCenter Server with NSX-T instance with vSphere V7 and migrate workloads. See [NSX-V to NSX-T migration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-v2t-overview). <br>Alternative path <br>Self-upgrade by using the [upgrade procedure](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vsphere_70_upgrade).<br><br><br><br> * For Cascade Lake servers, upgrade from vSphere V6 to V7.<br> * Open a support ticket to obtain new V7 licenses.<br> * Cluster expansion uses Cascade Lake servers. <br> Before December 2023, you must provision a new vCenter Server with NSX-T instance with vSphere V7 and migrate workloads.
* License count
* Preinstall file (attached)
* Purchase order (attached)



4. Install the license.

a. After you receive a valid license, download the license file and place it in /etc/rackware. Restart the services to apply the license by running the following command:

rwadm restart

b. Verify the license by running the following command:

rw rmm show







 Step 3: Establish connectivity between source server and IBM Cloud VPC 

Your source and target server should communicate with each other and the RMM. You can do this over the public internet with public IPs, or if you have a private-only environment, then you must set up either a VPN or Direct Link 2.0:



* Use [Direct Link 2.0 connection](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl) to IBM Cloud.
* Should have port 22 open with SSH accessible to RMM server.
* Public interface (least recommended due to security concerns).







 Step 4: Set up and provision VPC and virtual server instance 

There are two different methods for setting up the target server: manual or with the RMM auto-provision feature.



 Option 1: Manual 

The RMM solution handles only the OS, application, and data movement. It does not set up a VPC on the target side. Therefore, you must set up the VPC infrastructure. At a bare minimum, you need to set up a VPC, subnets, and virtual server instances. This tutorial does not go through all of the details for setting up the VPC infrastructure. For more information, see [Getting started with Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).



1. Create a VPC.
2. Create subnets.
3. Order virtual server instance.



* SSH key
* Operating system name (Linux or Windows and their respective versions)
* Security groups
* Secondary volume (optional)
Requirements for Cyber Recovery 

Cyber Recovery helps you with data protection, cyberthreats, cyberattacks, and ransomware. The instance includes the Veeam Backup and Replication 12 add-on service and a Linux® hardened repository (LHR). An edge gateway is required and you can provide your own or order one of the following edges:



* Juniper® vSRX
* FortiGate® Virtual Appliance
* FortiGate Security Appliance



You can order add-on services. For more information, see [Services for IBM Cloud Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_planningcr_planning-addon-services).

Price calculations are automatically generated when you access the Cyber Recovery instance order page. Default selections include the Data Center SP Professional license for NSX-T™, the Dual Intel® Xeon® Platinum 8260 processor / 48 cores, 2.4 GHz CPU model, 768 GB RAM, and NFS storage for both the consolidated and workload clusters.

Ensure that you complete the following tasks:



* If you are ordering an instance for the first time, complete the tasks in the Before you begin section on the ordering page. For more information, see [Setting up your environment for your first order](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-completing_checklist).
* Review the information in [Signing up for required accounts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-signing_required_accounts).
* Review the information in [Cyber Recovery overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_overview).
* Review the domain name format. The domain name is used to generate the username and server names of the instance.





Table 1. Value format for instance and domain names

 Name Value format 

 Domain name <root_domain> (Microsoft® Active Directory™ domain name)
Enter all additional license agreements, and click Next.







 Step 7: Review your readme file 

The TGZ file that you imported to your private catalog includes a readme file that provides product information for the virtual server image. If you want to make updates to the readme file, you can edit it directly from your private catalog. For the purposes of this tutorial, the following steps describe how to edit the description of the readme file.



1. Click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg), and update the description with the following sentence:

Create and deploy a virtual server with ease by using a custom image.
2. Click Save.
3. Click Next.







 Step 8: Validate the virtual server image 

Validate that you can deploy the virtual server image to your Power Systems Virtual Server instance.



1. From the Validate product tab, enter the name of your Schematics workspace, select a resource group, select a Schematics region, and click Next.

In the Tags field, you can enter a name of a specific tag to attach to your virtual server image. Tags provide a way to organize, track usage costs, and manage access to the resources in your account.
2. From the Deployment values section, review your parameter values, and click Next.
3. In the Validate product section, select I have read and agree to the following license agreements.
4. Click Validate.

You can monitor the progress of the validation process by clicking View logs.







 Step 9: Manage compliance 

Controls are safeguards that are used to meet security and compliance requirements. Only controls that are supported by Security and Compliance Center, formatted correctly, and validated by Code Risk Analysis and Security and Compliance Center scans appear in the catalog. For more information, see [Formatting controls in your readme file](https://cloud.ibm.com/docs/sell?topic=sell-sell-format-controls).
Go to the VPN server routes tab and follow [route creation guide](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-routes&interface=uicreate-route-ui)![route tab](https://cloud.ibm.com/docs-content/v1/content/d50364af907081c3c38f99c11f35dd9cab4b2510/vpc-journey/images/vpn/route_tab.png)![route tab](https://cloud.ibm.com/docs-content/v1/content/d50364af907081c3c38f99c11f35dd9cab4b2510/vpc-journey/images/vpn/create_route.png)
10. If the VPN uses client certificate for authorization:



* [Client certificate authoization steps](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-environment-setup&interface=ui)
* Edit the .ovpn file just downloaded using any text editor with the necessary information from the client certificates that were created in step 4



11. Upload the .ovpn to your respective VPN client software ![upload-ova](https://cloud.ibm.com/docs-content/v1/content/d50364af907081c3c38f99c11f35dd9cab4b2510/vpc-journey/images/vpn/ovpn_upload.png)
12. If the VPN uses userID and passcode for authorization:



* Set userID to the email used for IAM authorization.
* [Generate passcode]([https://iam.IBM](https://iam.IBM) Cloud/identity/passcode)
* Don't worry if a connection error: "missing external certificate" pops up, just press continue



13. Resources on your VPC should now be accessible!



!
* [RHSA-2021:1675](https://access.redhat.com/errata/RHSA-2021:1675)
* [RHSA-2021:1679](https://access.redhat.com/errata/RHSA-2021:1679)
* [RHSA-2021:1702](https://access.redhat.com/errata/RHSA-2021:1702)







 Version 4.6.0_678, released on 22 Apr 2021 



* Nettle vulnerabilities for [CVE-2021-20305](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20305)







 Version 4.6.0_663, released on 19 Apr 2021 



* [CVE-2021-3121](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3121)
* [CVE-2021-28851](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-28851)
* [CVE-2021-28852](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-28852)







 Version 4.6.0_654, released on 14 Apr 2021 



* [CVE-2021-3449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3449)
* [CVE-2021-3450](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3450)







 Version 4.6.0_646, released on 30 Mar 2021 



* [CVE-2021-3114](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3114)
* To bind service credentials to all actions in the package, follow steps 4 and 5 in the [CLI instructions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_watson_assistantconversation_cli).
* To bind service credentials to individual actions, complete the following steps in the console.



You must complete the following steps for each action that you want to use.



1. Click on an action from the assistant-v1 Package that you want to use. The details page for that action opens.
2. In the left navigation, click on the Parameters section.
3. Enter a new parameter. For the key, enter __bx_creds. For the value, paste in the service credentials JSON object from the service instance that you created earlier.











 Using the Watson Assistant package 

To use the actions in this package, run commands in the following format.

ibmcloud fn action invoke assistant-v1/<action_name> -b -p <param name> <param>

All actions require a version parameter in the format YYYY-MM-DD. When the API is changed in a backwards-incompatible way, a new version date is released. For more information, see the [API reference](https://cloud.ibm.com/apidocs/assistant/assistant-v1versioning).

This package's functions use the current version of Watson Assistant, 2018-07-10. Try out the list-workspaces action.

ibmcloud fn action invoke assistant-v1/list-workspaces -b -p version 2018-07-10
The agent is a Windows service that retrieves data from data source servers and sends it to Discovery. The agent can crawl remote Windows file systems, drives that are local to the agent, and shared network folders.

If you install the agent on a remote Windows server, the remote Windows server must be able to mount one or more file servers so that the agent can crawl the remote Windows file systems.

To install and configure the agent, complete the following tasks:



* [Install the agent](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-wfs-cp4dconnector-wfs-cp4d-prereq1).
* [Configure shared directories on the agent server](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-wfs-cp4dconnector-wfs-cp4d-prereq2).
* [Start and monitor the status of the agent server](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-wfs-cp4dconnector-wfs-cp4d-prereq3).







 Install the agent 

With the 4.6 release, the IBM Watson Discovery Agent for Windows File Systems was updated to run with 64-bit versions of Windows. If you installed the agent with a release prior to 4.6, you must uninstall the previous version, delete it, and then reinstall the agent.

Do one of the following tasks:



* You have a previous installation that is earlier than 4.6: [Replace the pre-4.6 agent](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-wfs-cp4dconnector-wfs-cp4d-prereq1-replace)
* You are using the connector for the first time: [Install the agent](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-wfs-cp4dconnector-wfs-cp4d-prereq1-new)
In the editor, enter the following command, where <lhbr_password> and <sa_ansible_password> are the passwords that are defined in the planning stage.

vault_lhbr_password: <lhbr_password>
vault_sa_ansible_password: <sa_ansible_password>
12. Exit by pressing Esc and :wq.







 Testing connections 

Use the following commands to test connections:

ansible lhbr -m ping
ansible vbr -m win_ping

If successful, the output shows SUCCESS for each command.





 Installing the Ansible NSX-T collections 

This step is optional, and is required only if Ansible is used for configuring sandboxes.



1. Connect to the Ansible control node as the ansible user.
2. Install python: sudo pip3 install --upgrade pyvmomi pyvim requests.
3. Run the following commands to complete the following tasks:



* Create a folder for the download.
* Clone the Git repo.
* Build the Ansible collection.
* Install the locally built collection.



cd /swlib
mkdir downloads
cd downloads
git clone https://github.com/vmware/ansible-for-nsxt.git
cd ansible-for-nsxt
ansible-galaxy collection build
ansible-galaxy collection install vmware-ansible_for_nsxt-1.0.0.tar.gz







 Related links 



* [Cyber recovery with Veeam architecture overview](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sa-overview)
* [Portworx](https://docs.portworx.com/portworx-install-with-kubernetes/storage-operations/create-pvcs/resize-pvc/)
* [Block storage](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-expandingcapacityexpandingcapacity)



Users can allocate more storage to their running network by resizing the existing storage PVCs or by deploying nodes with new PVCs.







 Upgrading to a new version of Fabric 

Support for Hyperledger Fabric v1.4 is now deprecated, and support for Fabric v1.4 will be removed from IBM Blockchain Platform on March 31, 2023. Users should therefore upgrade to Fabric v2.2 as soon as possible. Your applications may require changes as a result of upgrading to v2.2, so please plan for appropriate testing. Note that Fabric v1.4 has not been supported by the Hyperledger community since April of 2021. In addition, Fabric v1.4 uses Golang v1.14, which is no longer receiving security updates from the Golang community.

While some new versions of Fabric only require updating the Fabric version on nodes, some include new channel capabilities that must also be updated.

When updating nodes from Hyperledger Fabric v1.4.x to v2.x.x, select a 2.2.x (or later) level from the available options. Do not select v2.1.x, even if it is presented. Selecting the latest level is recommended.

In these cases, the process of "updating to the latest" release is, at a high level, a two step process:



1. Upgrade the Fabric version on all nodes.
2. Update the channels to the new capability levels. For information about how to update channels, see [Capabilities](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-capabilities).



You must upgrade nodes before you update the channels.