vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The community project provides developer and operations-centric tools that are based on Kubernetes to enable rapid app development, deployment, scaling, and long-term app lifecycle maintenance.

This tutorial shows how you can set up OpenShift Container Platform 3.11 on IBM Cloud classic infrastructure with Terraform on IBM Cloud to try out the high availability capabilities of native Kubernetes and IBM Cloud. Review the following image to find an architectural overview of the classic infrastructure components that are needed for the Red Hat OpenShift Container Platform to work properly.

![Infrastructure components for the Red Hat® OpenShift Container Platform on IBM Cloud](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/infra-diagram.png)

When you complete this tutorial, the following classic infrastructure components are provisioned for you:



* 1 OpenShift Container Platform master node
* 1 OpenShift Container Platform infrastructure node
* 1 OpenShift Container Platform application node
* 1 OpenShift Container Platform Bastion node
* 3 or more GlusterFS storage nodes if you decide to set up your cluster with GlusterFS
* Native IBM Cloud classic infrastructure services, such as VLANs and security groups





 Objectives 

In this tutorial, you set up Red Hat OpenShift Container Platform version 3.11 on IBM Cloud classic infrastructure and deploy your first nginx app in the OpenShift cluster. In particular, you will:



* Set up your environment and all the software that you need for your Red Hat OpenShift Container Platform installation, such as Terraform on IBM Cloud, IBM Cloud Provider plug-in, and the Terraform on IBM Cloud OpenShift project.
* Retrieve IBM Cloud credentials, configure the IBM Cloud Provider plug-in, and define your Red Hat OpenShift Container Platform classic infrastructure components.
* Provision IBM Cloud classic infrastructure for your Red Hat OpenShift Container Platform components by using Terraform on IBM Cloud.
* Install Red Hat OpenShift Container Platform on IBM Cloud classic infrastructure.
* You must have the [Administrator IBM Cloud IAM platform access role](https://cloud.ibm.com/docs/openshift?topic=openshift-userschecking-perms) for the Red Hat OpenShift on IBM Cloud cluster.



To get started, follow the instructions to send Kubernetes API audit logs [to a resource in the IBM Cloud private network](https://cloud.ibm.com/docs/openshift?topic=openshift-health-auditaudit-api-server-priv).





 Forwarding Kubernetes API audit logs to Log Analysis 

To forward audit logs to IBM Log Analysis, you can create a Kubernetes audit system by using the provided image and deployment.

The following example uses the icr.io/ibm/ibmcloud-kube-audit-to-logdna image to forward logs to Log Analysis. This image is for demonstration purposes only. For a production solution, configure and maintain your own log forwarding image.

The Kubernetes audit system in your cluster consists of an audit webhook, a log collection service and web server app, and a logging agent. The webhook collects the Kubernetes API server events from your cluster master. The log collection service is a Kubernetes ClusterIP service that is created from an image from the public IBM Cloud registry. This service exposes a simple node.js HTTP web server app that is exposed only on the private network. The web server app parses the log data from the audit webhook and creates each log as a unique JSON line. Finally, the logging agent forwards the logs from the web server app to IBM Log Analysis, where you can view the logs.

Before you begin: Ensure that you reviewed the [considerations and prerequisites](https://cloud.ibm.com/docs/openshift?topic=openshift-health-auditprereqs-apiserver-logs) and that you have the [Administrator IBM Cloud IAM platform access role](https://cloud.ibm.com/docs/account?topic=account-userroles) for IBM Log Analysis.



1.
install.exe -i console

The screens are rendered in text and prompt you for the same information as the graphical installation.

After you enter the command, a process runs in the background for several seconds before the console installation program is displayed.



* To install the agent server silently, complete the following steps:



* Change to the Agent/responseFiles directory.
* Edit the DistributedFileSystemCrawler.properties template response file to provide information about your environment. To run the installation program, change to the agent directory, and then specify the name of the file that you edited.

See the following example:

install.exe -i silent -f responseFiles/DistributedFileSystemCrawler.properties



If you copy a template file to another location to edit, specify the fully qualified path for the file when you run the installation program. If the response file path includes a space, enclose the path in double quotation marks ("). See the following example:

install.exe -i silent -f "c:My DocumentsDistributedFileSystemCrawler.properties"



7. You must provide the following information during the installation process:



* hostname: Enter or verify the fully-qualified hostname of the computer you are installing the agent server on.

You cannot specify an IPv6 address as the hostname of the server.
* username: Enter the username of an account that can be used to authorize access to the agent server.

If the username does not exist, select the checkbox to create the account.

To crawl a domain in a secure collection, the username must be an existing domain user with administration privileges for the Windows system to be crawled. To specify a domain user, use the format <username>@<domain name>.
* password: Provide the password that is associated with the username.



8. Optional: If you want to change the default path and port settings, click Advanced Options.



* You can change the paths for the installation directory and data directory.
* The agent server uses three TCP/IP ports for authenticating connections to the server, transferring data between the file systems and Discovery, and monitoring the agent server.
Normally it takes two parameters, a Secure Gateway gateway ID and the gateway's security token, both of which are available via the Secure Gateway Dashboard.

Return to [Getting Started - Adding a Client](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-add-client).







 Windows 



 Installing the Client 

You may require administrative privileges to perform this installation, depending on your system's security setup.



1. Copy the EXE installer file to your system. An MD5 sum is also provided which you can use to check the integrity of the installation package.
2. Install it by either double clicking on it and answering the prompts, or running the executable from the command prompt.
3. The user will be prompted to choose the installation directory of their choice. The default location is the Program Files (x86) directory.
4. The user will be prompted to select the language in which they want to launch the Command Line Interface. If not language is selected, it will be defaulted to English.
5. The user will be prompted to install the client as a windows service. If the user chooses to do so, the client will run in background as a windows service with the configurations user provide in the subsequent dialog. The status of service can be checked in the service page of Control Panel. The service name is "IBM Cloud Secure Gateway Service".
6. The installer identifies if there is an existing installation on the machine. If it is detected, the user is asked if they want to use the existing configurations, else the user has the option to enter new configurations. Details like gateway ids, security tokens, acl files and log level for each gateway can be provided here. If the user has chosen to run the client as a windows service the client will launch with the configurations provided. If the user has not chosen to launch the client as a windows service, the configurations will be stored for further use. In either case, the configurations are stored in %Installation_directory%/ibm/securegateway/client/securegw_service.config.
7.
Preparing the installation environment 

The installation of VMware HCX™ has the following software requirements:



* VMware vSphere® 5.5 U3, or vSphere 6.0u2 or higher.
* If VMware NSX® is used, version 6.2.2 or higher. NSX is required for policy migration.
* To use cross-cloud vMotion, the same affinity restrictions apply across clouds as they do on-premises. For more information, see the [VMware EVC and CPU compatibility FAQ](https://kb.vmware.com/s/article/1005764).





 Configuring network connectivity 

HCX must traverse the public internet and private lines, and connect to data center components, such as networks, switches, and port groups.



* For more information about the ports that must be opened so that HCX virtual appliances can install successfully, see [Port access requirements](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx-archi-port-req).
* Both the on premises vSphere environment and the vCenter Server HCX Cloud environment must allow Network Time Protocol (NTP) clock synchronization among vSphere on-premises devices and the vCenter Server HCX devices. UDP port 123 must be accessible to HCX virtual appliances and networks.







 On-premises environment 

Before you install HCX, verify that your environment can support the tasks that you want to accomplish. The on-premises environment must support the following tasks before HCX can be installed.



* Virtual Center with vSphere 5.5 Update 3 or 6.0 Update 2.
* vMotion and policy migration features require NSX version 6.2.2 or higher.
* A vSphere service account with the Administrator vCenter Server system role that is assigned to it.
* In the vCenter, enough disk space for the HCX appliances to be installed.
* Sufficient IP addresses for the on-premises VMs provisioned during the installation.
* Ports and firewalls opened as required as documented in Port Access Requirements.
To view the install log at any time during nim_master_setup, run the command: tail -f /var/adm/ras/nim.setup in a separate screen.
Creating image.data file...
5. Once completed, the NIM master file set has been installed and the basic resource objects created. The administrator is now able to add more NIM clients and define resources.

NIM master installation summary:

+----------------------------------------+
Summaries
+----------------------------------------+
Installation Summary
--------------------
Name Level Part Event Result
bos.sysmgt.nim.master 7.2.3.17 USR APPLY SUCCESS



For more information, see [Setting up NIM to boot into maintenance mode](https://www.ibm.com/support/pages/setting-nim-boot-maintenance-mode). If you are unfamiliar with this process, create a [new support case](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-help-and-support).
Keep in mind that for SAP certified servers, RAM, and operating system default is based on your server selection. Your local storage option also defaults based on your server selection. 
 SSH keys Enter an optional public key of your SSH key that you can use to log in to your server after it is provisioned. 
 Image (operating system) Select an image for your server. Your options are based on your selected server. 
 Add-ons Expand the Add-ons section to select the appropriate options or use the default values. 
 Storage disks Storage disks are preconfigured based on your server selection. You can expand Add-ons to add file or block storage volumes after your Bare Metal Servers are provisioned. <br>Because of compatibility issues, you can’t select NMVe drives if you’re going to install Windows®. 
 Network interface Select the uplink port speeds and private VLAN options. Expand Add-ons to select the appropriate options or use the default values. 



5. Review your order in the Order summary.
6. Enter any promo codes that you have under Apply Promo Code.
7. Click the third-party service agreements for any listed agreements.
8. Click Create to provision your server. You are redirected to a screen with your provisioning order number, which you can print because it's also your receipt.



A series of emails is sent to your administrator: Acknowledgment of the provisioning order, provisioning order approval and processing, and provisioning complete. The provisioning complete email includes a link to your Device Details page so that you can log in to IBM Cloud. You can also log directly in to the IBM Cloud® console.



 Provisioning by using a quote 

You can also provision a Bare Metal Servers with a quote or add it to an estimate. When you save a quote, a link is sent to the email address associated with your account. Open the link to see the saved quote information.

Another option is to go to Manage > Billing and usage > Sales > Device quotes. If you have access, you can purchase the quoted offering by clicking the quote and confirming the order. Adding to estimate places the configurations proposed cost in the pricing calculator.
Then, you can select Drive 0 and continue with the installation. When the installation is complete, shut down the virtual machine and remove the optical drives that you added: Windows installation ISO and virtio-win driver ISO. You can ignore any warnings about removing an optical drive.
3. Use the default Windows updater to download and install Windows updates. Repeat the process of downloading and installing updates until no updates are available.
4. Install [cloudbase-init](https://cloudbase.it/cloudbase-init/). For more information, see [cloudbase-init’s documentation](https://cloudbase-init.readthedocs.io/en/latest/index.html).
5. Modify the cloudbase-init configuration file, C:Program FilesCloudbase SolutionsCloudbase-Initconfcloudbase-init.conf to match the values that are shown in the following example.

[DEFAULT]
 "cloudbase-init.conf" is used for every boot
config_drive_types=vfat,iso
config_drive_locations=hdd,partition
activate_windows=true
kms_host=kms.adn.networklayer.com:1688
mtu_use_dhcp_config=false
real_time_clock_utc=false
bsdtar_path=C:Program FilesCloudbase SolutionsCloudbase-Initbinbsdtar.exe
mtools_path=C:Program FilesCloudbase SolutionsCloudbase-Initbin
debug=true
log_dir=C:Program FilesCloudbase SolutionsCloudbase-Initlog
log_file=cloudbase-init.log
default_log_levels=comtypes=INFO,suds=INFO,iso8601=WARN,requests=WARN
local_scripts_path=C:Program FilesCloudbase SolutionsCloudbase-InitLocalScripts
metadata_services=cloudbaseinit.metadata.services.configdrive.ConfigDriveService,
* Because of compatibility issues, you can’t select NMVe drives if you’re going to install Windows®.
* NVMe drives are installed in the last four slots of the chassis. IBM Cloud® automation requires that you install the operating system on drives that are in drive bays 0 and 1 or M.2s. So, you can't install an operating system on an NVMe drive.







 Order an NVMe SSD 

When you [provision](https://cloud.ibm.com/gen1/infrastructure/provision/bm) a bare metal server, follow the [Building a custom Bare Metal Server](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-ordering-baremetal-server) steps and select the NVMe option in the Storage disks section.
Provisioning 



 Process 

Important:

Customers must purchase (or own) App Points for MAS prior to (or in conjunction with) ordering MAS-Dedicated. The dedicated service provides IBM Cloud based hosting, product installation, operation, maintenance and support for MAS.

The provisioning process is invoked when a client has placed an order using MAS-Dedicated part numbers. There are three (3) part numbers:



* D02QTZX - Capacity
* D02QUZX - Data
* D02QWZX - VPC (Virtual Processor Core)



For details, see [Part Numbers and Order Considerations](https://cloud.ibm.com/docs/mas-ms?topic=mas-dedicated-getting-started-with-ibm-maximo-application-suite-dedicated-servicepart-numbers-and-order-considerations)

Each client is provisioned in an environment that is separate and distinct from other clients. The provisioning is done to meet the specific customer requirements for a specific order. This means there is no pre-provisioning done and client environment provisioning begins when an order is placed.

The provisioning process has several steps, most of them automated, but some that require a manual update(s) to complete. The time frame to complete a new provisioning will depend on several factors including:



* the size of the order
* the order complexity
* the number of orders in the queue ahead of the order



In general, allow for at least 4 weeks for provisioning to be completed.

The provisioning itself can be broken down into a number of steps:



* Order validation
* Information gathering
* Initial provisioning of MAS base environment
* Provisioning of the individual MAS products the clients has requested
* Internal IBM verification of the provisioned environments
* Welcome letter sent to the client / designated contacts indicating provisioning is complete







 Order Validation 

Once an order has been placed, the initial step is to validate the order and the information submitted. This includes checking the part numbers, ensuring the provisioning form has been completed, performing IBM internal financial checks and setting up the order to be provisioned. In general this can take 1 to 2 days to complete.
[root@ns0 mnt] mkdir xs-tools
[root@ns0 mnt] mount /dev/xvdd /mnt/xs-tools/
mount: block device /dev/xvdd is write-protected, mounting read-only
[root@ns0 mnt] cd /mnt/xs-tools/Linux/
[root@ns0 Linux] bash install.sh

The following changes are made to this virtual machine:
* packages to be installed or upgraded:
- kernel-xen-2.6.18-53.1.13.el5.xs4.1.0.24.x86_64.rpm
- xe-guest-utilities-4.1.0-257.x86_64.rpm

Continue? [y/n] y

Preparing... [100%]
1:xe-guest-utilities[100%]
Preparing... [100%]
package kernel-xen-2.6.18-92.el5 (which is newer than kernel-xen-2.6.18-53.1.13.el5.xs4.1.0.24) is already installed

Reboot this virtual machine.
[root@ns0 Linux]
Show more

If you want to copy and paste into your shell, the following lines perform all of the steps, if you are assigned the same device name of /dev/xvdd.

mkdir /mnt/xs-tools
mount /dev/xvdd /mnt/xs-tools
cd /mnt/xs-tools/Linux/
bash install.sh

In some cases, the Xen Tools ISO is mounted to /dev/cdrom.

mkdir /mnt/xs-tools
mount /dev/cdrom /mnt/xs-tools
cd /mnt/xs-tools/Linux
./install.sh
5. Restart your system from the command line and you can see that XenServer Tools are installed.
6.
With an Oracle install, how do I activate the iocp device when it's "Defined"? 

Use the smit menu with fast path command smitty iocp. Select Change/Show Characteristics of I/O Completion Ports and set the state to be configured at system restart to Available. This setting ensures that the device is available even after a system restart.

If you use the mkdev -l iocp0 command on the command line, the devíce is available only when the system is rebooted, and the device shows as Defined again. To ensure that this device is activated after a system restart, add the -P flag so the ODM is updated: mkdev -l iocp0 -P





 When I run the Oracle installer precheck, failed items are listed. What should I do? 

Part of the RUNINSTALLER function is to ensure that you complete the necessary pre-checks before you install the product. Two of the common errors are:



* You don't have enough free space in /tmp. Oracle 12.2 requires 5 GB of free space. If necessary, increase the amount of free space.
* You don't have 12 GB of paging space available. You can define paging multiple ways. You can extend the Paging Logical Volume hd6 in the volume group. You can also create a new paging space on a different volume by using smit mklv. When you see the LV type, specify paging. This setting creates a new paging space that is called paging00 on the hard disk you selected.



When you finish making adjustments and defined at least the minimum required amount of space, go back to the Oracle INSTALLER and select rerun checks. If you see no errors, you can proceed with the installation.





 Is there a central SAP Note for installing NetWeaver on Oracle? 

[SAP Note 2172935 - Installation - SAP Systems based on SAP NetWeaver: Oracle Database](https://launchpad.support.sap.com//notes/2172935) provides hardware and storage requirements for Oracle and details the required file systems and mount points.





 Is there a central SAP Note for using MaxDB for NetWeaver installations?
Example of installing Windows Server virtualization on Windows 2008 



 Before you begin 

Before you begin, review the following prerequisites. This tutorial walks you through installing Windows server virtualization on Windows 2008. Other versions may be different.



 Hardware 



* Hardware-assisted virtualization technology enabled in the BIOS
* Intel VT
* AMD-V
* Data Execution Prevention enabled in the BIOS
* Intel Execute Disable (XD)
* AMD No Execute (NX)







 Software 

To enable the Role option for Windows Server virtualization a few patches must be installed.



1. Open a browser window and browse to %sysdir%\Windows\wsv, usually C:\Windows\wsv. Two files will be located in that folder:



* Windows6.0-KB939853-x64.msu
* Windows6.0-KB939854-x64.msu



2. These patches can be installed in any order. Install both patches and then restart the system.









 Installation 



1. After the system restarts, you need to add the Role to the system.
2. After you add the role, the Create Virtual Networks dialog box appears. Note: Network connectivity is lost briefly.
3. Select Local Area Connection, your private network adapter. Click Continue. The installation continues and requires you to restart.
4. After the systems restarts, log in to the system via the Public connection. Note: You must log in with the same login credential that you used to install this connection. You will lose network connectivity to the interface. If not, you might receive the following error:



* Attempt to configure Windows Server Virtualization failed with error code 0x80078000. To resolve the error, go to Start > Programs > Administrative Tools > Windows Virtualization Management in the management console for Windows virtualization.



5. In the right pane, click on the appropriate server.
6. Then in the action pane, click Virtual Network Manager. You now see Virtual Network Switch Management.
CM-11 - User-installed Software 



  Control requirements 

The organization:

CM-11 (a)
:   Establishes [Assignment: organization-defined policies] governing the installation of software by users;

CM-11 (b)
:   Enforces software installation policies through [Assignment: organization-defined methods]; and

CM-11 (c)
:   Monitors policy compliance at [IBM Assignment: continuously].





  NIST supplemental guidance 

If provided the necessary privileges, users have the ability to install software in organizational information systems. To maintain control over the types of software installed, organizations identify permitted and prohibited actions regarding software installation. Permitted software installations may include, for example, updates and security patches to existing software and downloading applications from organization-approved “app stores” Prohibited software installations may include, for example, software with unknown or suspect pedigrees or software that organizations consider potentially malicious. The policies organizations select governing user-installed software may be organization-developed or provided by some external entity. Policy enforcement methods include procedural methods (e.g., periodic examination of user accounts), automated methods (e.g., configuration settings implemented on organizational information systems), or both.
bash install.sh

In some cases, the Xen Tools ISO is mounted to /dev/cdrom.

mkdir /mnt/xs-tools
mount /dev/cdrom /mnt/xs-tools
cd /mnt/xs-tools/Linux
./install.sh
5. Restart your system from the command line and you can see that XenServer Tools are installed.
6. Now XenCenter has more control of the operating system within the virtual machine, and you can view the previously unavailable counters in the Performance tab of XenCenter.