mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Preparation for migration Red Hat build of OpenJDK 11 includes changes that might require you to reconfigure your applications, which were already successfully deployed on Red Hat build of OpenJDK 8. You can ensure an effective migration plan by completing the following tasks: Review the Major differences between Red Hat build of OpenJDK 8 and Red Hat build of OpenJDK 11 section. Integrate the differences into your migration plan. Red Hat provides a migration toolkit for applications (MTA) tool that you can use to help with your migration tasks. You can use the MTA tool to migrate Java applications from Red Hat build of OpenJDK 8 to Red Hat build of OpenJDK 11. Additional resources For more information about the installation of Red Hat build of OpenJDK 11 on RHEL, see the Installing and using Red Hat build of OpenJDK 11 on RHEL guide. For more information about the installation of Red Hat build of OpenJDK 11 on Microsoft Windows, see the Installing and using Red Hat build of OpenJDK 11 for Windows guide. For more information about switching between Red Hat build of OpenJDK versions on RHEL, see Interactively selecting a system-wide Red Hat build of OpenJDK version of RHEL in the Configuring Red Hat build of OpenJDK 11 on RHEL guide. For more information about switching between Red Hat build of OpenJDK versions on Microsoft Windows, see Selecting a specific Red Hat build of OpenJDK from the installed versions of an application in the Configuring Red Hat build of OpenJDK 11 on Microsoft Windows guide. For more information about the MTA tool, see the Introduction to the Migration Toolkit for Applications guide.

Commands:
Appendix A. Revision History Revision History Revision 3.6-4 Wed Dec 20 2023 Lenka Spackova Fixed broken links and anchors. Revision 3.6-3 Fri Nov 12 2021 Lenka Spackova Updated Section 4.4, "Database Connectors" . Revision 3.6-2 Tue Apr 06 2021 Lenka Spackova Improved the list of supported architectures. Revision 3.6-1 Tue Dec 01 2020 Lenka Spackova Release of Red Hat Software Collections 3.6 Release Notes. Revision 3.6-0 Tue Oct 29 2020 Lenka Spackova Release of Red Hat Software Collections 3.6 Beta Release Notes.

Commands:
Part III. Migrating to Red Hat build of Kogito microservices As a developer of business decisions and processes, you can migrate your decision services in Red Hat Process Automation Manager to Red Hat build of Kogito microservices. When performing migration, your existing business decisions become part of your own domain-specific cloud-native set of services. You can migrate Decision Model and Notation (DMN) models, Predictive Model Markup Language (PMML) models, or Drools Rule Language (DRL) rules. Prerequisites JDK 11 or later is installed. Apache Maven 3.6.2 or later is installed.

Commands:
20.18. Watchdog Device A virtual hardware watchdog device can be added to the guest virtual machine via the <watchdog> element. The watchdog device requires an additional driver and management daemon in the guest virtual machine. As merely enabling the watchdog in the libvirt configuration does not do anything useful on its own. Currently there is no support notification when the watchdog fires. ... <devices> <watchdog model='i6300esb'/> </devices> ... ... <devices> <watchdog model='i6300esb' action='poweroff'/> </devices> </domain> Figure 20.66. Watchdog Device The following attributes are declared in this XML: model - The required model attribute specifies what real watchdog device is emulated. Valid values are specific to the underlying hypervisor. The model attribute may take the following values: i6300esb - the recommended device, emulating a PCI Intel 6300ESB ib700 - emulates an ISA iBase IB700 action - The optional action attribute describes what action to take when the watchdog expires. Valid values are specific to the underlying hypervisor. The action attribute can have the following values: reset - default setting, forcefully resets the guest virtual machine shutdown - gracefully shuts down the guest virtual machine (not recommended) poweroff - forcefully powers off the guest virtual machine pause - pauses the guest virtual machine none - does nothing dump - automatically dumps the guest virtual machine. Note that the 'shutdown' action requires that the guest virtual machine is responsive to ACPI signals. In the sort of situations where the watchdog has expired, guest virtual machines are usually unable to respond to ACPI signals. Therefore using 'shutdown' is not recommended. In addition, the directory to save dump files can be configured by auto_dump_path in file /etc/libvirt/qemu.conf.

Commands:
<devices> <watchdog model='i6300esb'/> </devices> <devices> <watchdog model='i6300esb' action='poweroff'/> </devices> </domain>
Power Monitoring OpenShift Container Platform 4.16 Configuring and using power monitoring for OpenShift Container Platform Red Hat OpenShift Documentation Team

Commands:
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler spec: exporter: deployment: port: 9103 1 nodeSelector: kubernetes.io/os: linux 2 Tolerations: 3 - key: "" operator: "Exists" value: "" effect: ""
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler status: exporter: conditions: 1 - lastTransitionTime: '2024-01-11T11:07:39Z' message: Reconcile succeeded observedGeneration: 1 reason: ReconcileSuccess status: 'True' type: Reconciled - lastTransitionTime: '2024-01-11T11:07:39Z' message: >- Kepler daemonset "kepler-operator/kepler" is deployed to all nodes and available; ready 2/2 observedGeneration: 1 reason: DaemonSetReady status: 'True' type: Available currentNumberScheduled: 2 2 desiredNumberScheduled: 2 3
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler spec: exporter: deployment: redfish: secretRef: <secret_name> required 1 probeInterval: 60s 2 skipSSLVerify: false 3
<your_kubelet_node_name>,<redfish_username>,<redfish_password>,https://<redfish_ip_or_hostname>/
control-plane,exampleuser,examplepass,https://redfish.nodes.example.com worker-1,exampleuser,examplepass,https://redfish.nodes.example.com worker-2,exampleuser,examplepass,https://another.redfish.nodes.example.com
oc -n openshift-power-monitoring create secret generic redfish-secret --from-file=redfish.csv
apiVersion: v1 kind: Secret metadata: name: redfish-secret data: redfish.csv: YmFyCg== #
Chapter 11. Reviewing monitoring dashboards OpenShift Container Platform 4.11 provides a comprehensive set of monitoring dashboards that help you understand the state of cluster components and user-defined workloads. Use the Administrator perspective to access dashboards for the core OpenShift Container Platform components, including the following items: API performance etcd Kubernetes compute resources Kubernetes network resources Prometheus USE method dashboards relating to cluster and node performance Figure 11.1. Example dashboard in the Administrator perspective Use the Developer perspective to access Kubernetes compute resources dashboards that provide the following application metrics for a selected project: CPU usage Memory usage Bandwidth information Packet rate information Figure 11.2. Example dashboard in the Developer perspective Note In the Developer perspective, you can view dashboards for only one project at a time. 11.1. Reviewing monitoring dashboards as a cluster administrator In the Administrator perspective, you can view dashboards relating to core OpenShift Container Platform cluster components. Prerequisites You have access to the cluster as a user with the cluster-admin cluster role. Procedure In the Administrator perspective in the OpenShift Container Platform web console, navigate to Observe Dashboards . Choose a dashboard in the Dashboard list. Some dashboards, such as etcd and Prometheus dashboards, produce additional sub-menus when selected. Optional: Select a time range for the graphs in the Time Range list. Select a pre-defined time period. Set a custom time range by selecting Custom time range in the Time Range list. Input or select the From and To dates and times. Click Save to save the custom time range. Optional: Select a Refresh Interval . Hover over each of the graphs within a dashboard to display detailed information about specific items. 11.2. Reviewing monitoring dashboards as a developer Use the Developer perspective to view Kubernetes compute resources dashboards of a selected project. Prerequisites You have access to the cluster as a developer or as a user. You have view permissions for the project that you are viewing the dashboard for. Procedure In the Developer perspective in the OpenShift Container Platform web console, navigate to Observe Dashboard . Select a project from the Project: drop-down list. Select a dashboard from the Dashboard drop-down list to see the filtered metrics. Note All dashboards produce additional sub-menus when selected, except Kubernetes / Compute Resources / Namespace (Pods) . Optional: Select a time range for the graphs in the Time Range list. Select a pre-defined time period. Set a custom time range by selecting Custom time range in the Time Range list. Input or select the From and To dates and times. Click Save to save the custom time range. Optional: Select a Refresh Interval . Hover over each of the graphs within a dashboard to display detailed information about specific items. Additional resources Monitoring project and application metrics using the Developer perspective 11.3. steps Accessing third-party monitoring APIs

Commands:
34.3. Create User Create a user account for yourself with this screen. Always use this account to log in to your Red Hat Enterprise Linux system, rather than using the root account. Figure 34.12. Firstboot create user screen Enter a user name and your full name, and then enter your chosen password. Type your password once more in the Confirm Password box to ensure that it is correct. To configure Red Hat Enterprise Linux to use network services for authentication of user information, click Use Network Login . Refer to Section 34.3.1, "Authentication Configuration" for further details. Important If you do not create at least one user account in this step, you will not be able to log in to the Red Hat Enterprise Linux graphical environment. If you skipped this step during installation, refer to Section 10.4.2, "Booting into a Graphical Environment" . Note To add additional user accounts to your system after the installation is complete, choose System Administration Users & Groups . 34.3.1. Authentication Configuration If you clicked Use Network Login on the Create User screen, you must now specify how users are to be authenticated on the system. Use the drop-down menu to select from the following types of user database: Local accounts only (for use when the user database on the network is not accessible) LDAP (Lightweight Directory Access Protocol) NIS (Network Information Service) Winbind (for use with Microsoft Active Directory) Figure 34.13. Firstboot Authentication Configuration screen When you select the type of user database appropriate for your network, you must provide additional details relevant to that database type. For example, if you select LDAP , you must specify the base distinguished name for LDAP searches, and the address of the LDAP server. You must also select an Authentication Method relevant to the type of user database that you chose, for example, a Kerberos password, LDAP password, or NIS password. The Advanced Options tab lets you enable other authentication mechanisms, including fingerprint readers, smart cards, and local access control in /etc/security/access.conf . For more information, refer to Authentication Configuration in the Red Hat Enterprise Linux Deployment Guide . Figure 34.14. Firstboot authentication Advanced Options screen

Commands:
8.219. slapi-nis 8.219.1. RHBA-2014:1583 - slapi-nis bug fix update Updated slapi-nis packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The slapi-nis packages contain the NIS server plug-in and the Schema Compatibility plug-in for use with the 389 directory server. Bug Fixes BZ# 1039942 Prior to this update, the NIS Server plug-in did not release memory that was used to hold a decoded client request. Consequently, the directory server used an excessive amount of memory as it processed more requests from NIS clients. The bug has been fixed and thus no longer causes memory leaks on the directory server. BZ# 1056648 Due to a bug in slapi-nis plug-in behavior, modifying a directory server entry, such as disabling sudo rules, did previously not correctly add or remove the corresponding NIS map entry or compatibility entry. As a consequence, the intended changes to configuration failed to take effect. With this update, slapi-nis plug-ins notice the configuration changes as expected and update their data accordingly. Users of slapi-nis are advised to upgrade to these updated packages, which fix these bugs.

Commands:
28.5.4. Testing ABRT's Crash Detection After completing all the steps of the configuration process, the basic setup is finished. To test that this setup works properly use the kill -s SEGV PID command to terminate a process on a client system. For example, start a sleep process and terminate it with the kill command in the following way: ABRT should detect a crash shortly after executing the kill command. Check that the crash was detected by ABRT on the client system (this can be checked by examining the appropriate syslog file, by running the abrt-cli list --full command, or by examining the crash dump created in the /var/spool/abrt directory), copied to the server system, unpacked on the server system and can be seen and acted upon using abrt-cli or abrt-gui on the server system.

Commands:
~]USD sleep 100 & [1] 2823 ~]USD kill -s SIGSEGV 2823
Chapter 4. Reviewing and resolving migration issues You can review and resolve migration issues identified by the MTA extension in the left pane. 4.1. Reviewing issues You can use the MTA extension icons to prioritize issues based on their severity. Procedure Select a run configuration directory on the left pane. Expand its folders to view the Hints generated for each application file. Select a hint to view the source code. Right-click a hint and select View Details to view the Rule ID and other information. Prioritize issues based on the following icons, which are displayed to each hint: : The issue must be fixed for a successful migration. : The issue might need to be addressed during migration. 4.2. Resolving issues You can resolve issues by editing the code of a file with a hint 4.2.1. Editing the code of a file You can edit the file of a project imported to VS Code. Procedure In the left pane, right-click an issue and select Open Code . Make any changes needed to the code and save the file. Optional: Right-click the issue and select Mark as Complete or Delete .

Commands:
Chapter 10. Reviewing monitoring dashboards OpenShift Container Platform 4.13 provides a comprehensive set of monitoring dashboards that help you understand the state of cluster components and user-defined workloads. Use the Administrator perspective to access dashboards for the core OpenShift Container Platform components, including the following items: API performance etcd Kubernetes compute resources Kubernetes network resources Prometheus USE method dashboards relating to cluster and node performance Figure 10.1. Example dashboard in the Administrator perspective Use the Developer perspective to access Kubernetes compute resources dashboards that provide the following application metrics for a selected project: CPU usage Memory usage Bandwidth information Packet rate information Figure 10.2. Example dashboard in the Developer perspective Note In the Developer perspective, you can view dashboards for only one project at a time. 10.1. Reviewing monitoring dashboards as a cluster administrator In the Administrator perspective, you can view dashboards relating to core OpenShift Container Platform cluster components. Prerequisites You have access to the cluster as a user with the cluster-admin cluster role. Procedure In the Administrator perspective in the OpenShift Container Platform web console, navigate to Observe Dashboards . Choose a dashboard in the Dashboard list. Some dashboards, such as etcd and Prometheus dashboards, produce additional sub-menus when selected. Optional: Select a time range for the graphs in the Time Range list. Select a pre-defined time period. Set a custom time range by selecting Custom time range in the Time Range list. Input or select the From and To dates and times. Click Save to save the custom time range. Optional: Select a Refresh Interval . Hover over each of the graphs within a dashboard to display detailed information about specific items. 10.2. Reviewing monitoring dashboards as a developer In the Developer perspective, you can view dashboards relating to a selected project. You must have access to monitor a project to view dashboard information for it. Prerequisites You have access to the cluster as a developer or as a user. You have view permissions for the project that you are viewing the dashboard for. Procedure In the Developer perspective in the OpenShift Container Platform web console, navigate to Observe Dashboard . Select a project from the Project: drop-down list. Select a dashboard from the Dashboard drop-down list to see the filtered metrics. Note All dashboards produce additional sub-menus when selected, except Kubernetes / Compute Resources / Namespace (Pods) . Optional: Select a time range for the graphs in the Time Range list. Select a pre-defined time period. Set a custom time range by selecting Custom time range in the Time Range list. Input or select the From and To dates and times. Click Save to save the custom time range. Optional: Select a Refresh Interval . Hover over each of the graphs within a dashboard to display detailed information about specific items. Additional resources Monitoring project and application metrics using the Developer perspective

Commands:
9.2. Using ECC with an HSM The HSMs supported by Certificate System support their own native ECC modules. To create an instance with ECC system certificates: Set up the HSM per manufacturer's instructions. If multiple hosts are sharing the HSM, make sure they can all access the same partition if needed and if the site policies allow it. Define the required parameters in the pkispawn utility configuration file and run pkispawn . For example, to configure Certificate System to create an ECC CA, assuming the configuration file is ecc.inf : Edit ecc.inf to specify the appropriate settings. For an example of the configuration file, see the pkispawn (8) man page. Run pkispawn against ecc.inf :

Commands:
script -c 'pkispawn -s CA -f /root/pki/ecc.inf -vvv'
Chapter 2. Installing Red Hat build of OpenJDK 21 for Microsoft Windows with the archive This procedure describes how to manually install Red Hat build of OpenJDK 21 for Microsoft Windows using the archive. Procedure Download the archive of Red Hat build of OpenJDK 21 for Microsoft Windows. Extract the contents of an archive to a directory of your choice. Note Extracting the contents of an archive to a directory path that does not contain spaces is recommended. Update the PATH as below: Add the bin directory contained in your Red Hat build of OpenJDK 21 for Microsoft Windows installation path to the %PATH% environment variable: If the path contains spaces, use the shortened path name. Restart Command Prompt to reload the environment variables. To verify the Red Hat build of OpenJDK 21 for Microsoft Windows is successfully installed, run the java -version command in a command prompt. The %JAVA_HOME% environment variable must also be set to use some developer tools. Set the %JAVA_HOME% environment variable as follows: Open Command Prompt as an administrator. Set the value of the environment variable to your Red Hat build of OpenJDK 21 for Microsoft Windows installation path: If the path contains spaces, use the shortened path name. Restart Command Prompt to reload the environment variables.

Commands:
C:\> setx /m PATH "%PATH%;C:\Progra~1\RedHat\java-21-openjdk-<version>\bin"
C:\> setx /m JAVA_HOME "C:\Progra~1\RedHat\java-21-openjdk-<version>"
Chapter 2. Installation Compression format for the initrd.img file In Red Hat Enterprise Linux 6.2, the compression format used for the initrd.img file has changed. The image is now compressed using LZMA rather than Gzip. To decompress an image, use the xz -d command. For example: To compress an image, use the xz -9 --format=lzma command. For example: Support for device identification using WWIDs during installation Fibre Channel and Serial Attached SCSI (SAS) devices can be now specified by a World Wide Name (WWN) or a World Wide Identifier (WWID) for unattended installations. WWN is part of the IEEE standard which makes it easier to identify storage devices during installation for users utilizing Storage Area Networks (SAN) and other advanced network topologies. When a storage device is attached to a server using multiple physical paths for redundancy or improved performance, WWN for any of these paths is sufficient to identify the device. Initial RAM disk file The initial RAM disk file on 64-bit PowerPC and 64-bit IBM POWER Series systems is now named initrd.img . In releases, it was named ramdisk.image.gz . Static IPv6 address support for network installation In Red Hat Enterprise Linux 6.2, a static IPv6 address can be specified for the ipv6 boot option for network installations. The specified address must be of the following form: An example of a valid IPv6 address would then be 3ffe:ffff:0:1::1/128 . If the prefix is omitted, the value of 64 is assumed. Specifying a static IPv6 address for the ipv6 boot option complements the already existing dhcp and auto parameters that can be specified for the ipv6 boot option.

Commands:
~]# xz -dc initrd.img | cpio -id
~]# find . | cpio -c -o | xz -9 --format=lzma > initrd.img
<IPv6 address> [ /<prefix length> ]