mtpti5iD/redhat-docs_dataset huggingface dataset:
32.4. Using fadump on IBM PowerPC hardware Starting with Red Hat Enterprise Linux 6.8 an alternative dumping mechanism to kdump , the firmware-assisted dump ( fadump ), is available. The fadump feature is supported only on IBM Power Systems. The goal of fadump is to enable the dump of a crashed system, and to do so from a fully-reset system, and to minimize the total elapsed time until the system is back in production use. The fadump feature is integrated with kdump infrastructure present in the user space to seemlessly switch between kdump and fadump mechanisms. Firmware-assisted dump ( fadump ) is a reliable alternative to kexec-kdump available on IBM PowerPC LPARS. It captures vmcore from a fully-reset system with PCI and I/O devices reinitialized. While this mechanism uses the firmware to preserve the memory in case of a crash, it reuses the kdump userspace scripts to save the vmcore" To achieve this, fadump registers the regions of memory that must be preserved in the event of a crash with the system firmware. These regions consist of all the system memory contents, except the boot memory, system registers and hardware Page Table Entries (PTEs). Note The area of memory not preserved and known as boot memory is the amount of RAM required to successfully boot the kernel after a crash event. By default, the boot memory size is 256MB or 5% of total system RAM, whichever is larger. Unlike a kexec -initiated event, the fadump process uses the production kernel to recover a crash dump. When booting after a crash, PowerPC hardware makes the device node /proc/device-tree/rtas/ibm,kernel-dump available to procfs , which the fadump-aware kdump scripts check for to save the vmcore. After this has completed, the system is rebooted cleanly. Enabling fadump Install and configure kdump as described in Section 32.1, "Installing the kdump Service" and Section 32.2, "Configuring the kdump Service" . Add fadump=on to the GRUB_CMDLINE_LINUX line in /etc/default/grub : (optional) If you want to specify reserved boot memory instead of accepting the defaults, add fadump_reserve_mem= xx M to GRUB_CMDLINE_LINUX in /etc/default/grub , where xx is the amount of the memory required in megabytes: Important As with all boot configuration options, it is strongly recommended that you test the configuration before it is needed. If you observe Out of Memory (OOM) errors when booting from the crash kernel, increase the value specified in fadump_reserve_mem= until the crash kernel can boot cleanly. Some trial and error may be required in this case.

Commands:
GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/swap crashkernel=auto rd.lvm.lv=rhel/root rhgb quiet fadump=on "
GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/swap crashkernel=auto rd.lvm.lv=rhel/root rhgb quiet fadump=on fadump_reserve_mem= xx M "
Chapter 1. Red Hat Storage on Public Cloud Red Hat Gluster Storage for Public Cloud packages glusterFS for deploying scalable NAS in the public cloud. This powerful storage server provides all the features of On-Premise deployment, within a highly available, scalable, virtualized, and centrally managed pool of NAS storage hosted off-premise. Additionally, Red Hat Gluster Storage can be deployed in the public cloud using Red Hat Gluster Storage for Public Cloud, for example, within the Amazon Web Services (AWS) cloud. It delivers all the features and functionality possible in a private cloud or datacenter to the public cloud by providing massively scalable and high available NAS in the cloud. The POSIX compatible glusterFS servers, which use XFS file system format to store data on disks, can be accessed using industry-standard access protocols including Network File System (NFS) and Server Message Block (SMB) (also known as CIFS). 1.1. About glusterFS glusterFS aggregates various storage servers over network interconnects into one large parallel network file system. Based on a stackable user space design, it delivers exceptional performance for diverse workloads and is a key building block of Red Hat Gluster Storage.

Commands:
Chapter 3. Red Hat build of OpenJDK 17.0.8.1 release notes Review the following release note to understand changes from the Red Hat build of OpenJDK 17.0.8.1 patch release. Note For all the other changes and security fixes, see OpenJDK 17.0.8.1 Released . Fixed Invalid CEN header error on valid .zip files Red Hat build of OpenJDK 17.0.8 introduced additional validation checks on the ZIP64 fields of .zip files (JDK-8302483). However, these additional checks caused validation failures on some valid .zip files with the following error message: Invalid CEN header (invalid zip64 extra data field size) . To fix this issue, Red Hat build of OpenJDK 17.0.8.1 supports zero-length headers and the additional padding that some ZIP64 creation tools produce. From Red Hat build of OpenJDK 17.0.8 onward, you can disable these checks by setting the jdk.util.zip.disableZip64ExtraFieldValidation system property to true . See JDK-8313765 (JDK Bug System) Increased default value of jdk.jar.maxSignatureFileSize system property Red Hat build of OpenJDK 17.0.8 introduced a jdk.jar.maxSignatureFileSize system property for configuring the maximum number of bytes that are allowed for the signature-related files in a Java archive (JAR) file ( JDK-8300596 ). By default, the jdk.jar.maxSignatureFileSize property was set to 8000000 bytes (8 MB), which was too small for some JAR files. Red Hat build of OpenJDK 17.0.8.1 increases the default value of the jdk.jar.maxSignatureFileSize property to 16000000 bytes (16 MB). See JDK-8313216 (JDK Bug System) Advisories related to Red Hat build of OpenJDK 17.0.8.1 The following advisories have been issued to bug fixes and CVE fixes included in this release: RHBA-2023:5226 RHBA-2023:5228

Commands:
Chapter 8. LVM Configuration LVM can be configured during the graphical installation process, the text-based installation process, or during a kickstart installation. You can use the utilities from the lvm package to create your own LVM configuration post-installation, but these instructions focus on using Disk Druid during installation to complete this task. Read Chapter 7, Logical Volume Manager (LVM) first to learn about LVM. An overview of the steps required to configure LVM include: Creating physical volumes from the hard drives. Creating volume groups from the physical volumes. Creating logical volumes from the volume groups and assign the logical volumes mount points. Note Although the following steps are illustrated during a GUI installation, the same can be done during a text-based installation. Two 9.1 GB SCSI drives ( /dev/sda and /dev/sdb ) are used in the following examples. They detail how to create a simple configuration using a single LVM volume group with associated logical volumes during installation. 8.1. Automatic Partitioning On the Disk Partitioning Setup screen, select Automatically partition . For Red Hat Enterprise Linux, LVM is the default method for disk partitioning. If you do not wish to have LVM implemented, or if you require RAID partitioning, manual disk partitioning through Disk Druid is required. The following properties make up the automatically created configuration: The /boot/ partition resides on its own non-LVM partition. In the following example, it is the first partition on the first drive ( /dev/sda1 ). Bootable partitions cannot reside on LVM logical volumes. A single LVM volume group ( VolGroup00 ) is created, which spans all selected drives and all remaining space available. In the following example, the remainder of the first drive ( /dev/sda2 ), and the entire second drive ( /dev/sdb1 ) are allocated to the volume group. Two LVM logical volumes ( LogVol00 and LogVol01 ) are created from the newly created spanned volume group. In the following example, the recommended swap space is automatically calculated and assigned to LogVol01 , and the remainder is allocated to the root file system, LogVol00 . Figure 8.1. Automatic LVM Configuration With Two SCSI Drives Note If enabling quotas are of interest to you, it may be best to modify the automatic configuration to include other mount points, such as /home/ or /var/ , so that each file system has its own independent quota configuration limits. In most cases, the default automatic LVM partitioning is sufficient, but advanced implementations could warrant modification or manual configuration of the LVM partition tables. Note If you anticipate future memory upgrades, leaving some free space in the volume group would allow for easy future expansion of the swap space logical volume on the system; in which case, the automatic LVM configuration should be modified to leave available space for future growth.

Commands:
5.130. kdebase 5.130.1. RHBA-2012:1371 - kdebase bug fix update Updated kdebase packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The K Desktop Environment (KDE) is a graphical desktop environment for the X Window System. The kdebase packages include core applications for KDE. Bug Fixes BZ# 608007 Prior to this update, the Konsole context menu item "Show menu bar" was always checked in new windows even if this menu item was disabled before. This update modifies the underlying code to handle the menu item "Show menu bar" as expected. BZ# 729307 Prior to this update, users could not define a default size for xterm windows when using the Konsole terminal in KDE. This update modifies the underlying code and adds the functionality to define a default size. All users of kdebase are advised to upgrade to these updated packages, which fix these bugs.

Commands:
23.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. The following types are used with Postfix. Different types all you to configure flexible access: postfix_etc_t This type is used for configuration files for Postfix in the /etc/postfix/ directory. postfix_data_t This type is used for Postfix data files in the /var/lib/postfix/ directory. postfix_var_run_t This type is used for Postfix files stored in the /run/ directory. postfix_initrc_exec_t The Postfix executable files are labeled with the postfix_initrc_exec_t type. When executed, they transition to the postfix_initrc_t domain. postfix_spool_t This type is used for Postfix files stored in the /var/spool/ directory. Note To see the full list of files and their types for Postfix, enter the following command:

Commands:
~]USD grep postfix /etc/selinux/targeted/contexts/files/file_contexts
Chapter 2. Navigating the Red Hat Hybrid Cloud Console From within the Red Hat Hybrid Cloud Console, you can take guided tours of the console and its services, search for information to help you achieve your goals, or start using a service. Here is a list of some of the tasks that you can perform: Find a service on the All Services page and make it a favorite to easily find later. Configure the following global settings from the Settings menu under the gear icon: Notifications: Configure how and when you receive notifications about important events that occur in your console services. Configure user access from the Identity & Access Management menu under the gear icon. Configure your preferences for notifications from User Preferences , under your profile menu. Review updates to the console, take product tours, and submit feedback.

Commands:
Chapter 3. Getting information about your clusters and data In the Cluster information page of cost management, you can view information like the status of your integration, the time of data retrieval, and links to each integration. You can also pause and resume integrations. 3.1. Getting information about your cluster Navigate to cost management > OpenShift . In the Group by drop-down, select Cluster . Select the cluster that you want to view. An OpenShift cluster details page opens. At the top of the page, click the hyperlink Cluster information . The Cluster information page provides the following details: Cluster ID The cost management operator version and if any updates are available The Red Hat integration (the integration for your cluster) Your Cloud integration If you are running a cluster on-premise or if you did not add a cloud integration for your cluster, you won't see a value in Cloud integration . 3.2. Getting information about your data Navigate to cost management > OpenShift . In the Group by drop-down, select Cluster . Select the cluster that you want to view. An OpenShift cluster details page opens. At the top of the page, click the hyperlink Data details . There are three sections that give you details about your cloud data, cluster data, and about cost management data: Cloud integration status or Red Hat integration status Provides a link to your integrations. Data availability For Cloud data , a timestamp refers to the last time that cost management checked for an available report. Data retrieval For Cloud data , a timestamp refers to when cost management retrieved your data from the cloud provider. For Cluster data , a timestamp refers to when cost management retrieved your data from the ingress service that the operator uploads it to. Data processing This timestamp refers to when cost management unpacked the reports, put them in the database, and made them available with the API. Data integration and finalization For cost management data , a timestamp refers to when cost management correlated the raw billing data from your cloud with your cluster metrics, and then applied any cost model rates against your metrics. 3.3. Pausing or resuming an integration In the Integrations section of console.redhat.com Settings , choose an integration that you want to pause or resume. On the row of the integration that you want to pause or resume, click the more options menu . Verify that Cloud integration status has either a pause icon or a green checkmark. It can take a couple seconds for it to load.

Commands:
Part III. Integrating Red Hat Process Automation Manager with Red Hat Single Sign-On As a system administrator, you can integrate Red Hat Single Sign-On with Red Hat Process Automation Manager to secure your Red Hat Process Automation Manager browser applications with a single authentication method. Prerequisites Red Hat Process Automation Manager is installed on Red Hat JBoss EAP 7.4. For information, see Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 .

Commands:
Chapter 2. Installing extension pack for Apache Camel by Red Hat Important The VS Code extensions for Apache Camel are listed as development support. For more information about scope of development support, see Development Support Scope of Coverage for Red Hat Build of Apache Camel . This section explains how to install Extension Pack for Apache Camel by Red Hat. Procedure Open the VS Code editor. In the VS Code editor, select View > Extensions . In the search bar, type Camel . Select the Extension Pack for Apache Camel by Red Hat option from the search results and then click Install. This installs the extension pack which includes extensions for Apache Camel in the VS Code editor.

Commands:
B.4. Extract a Self-signed Certificate from the Keystore Procedure B.2. Extract a Self-signed Certificate from the Keystore Run the keytool -export -alias ALIAS -keystore server.keystore -rfc -file public.cert command: Enter the keystore password when prompted: Result This creates the public.cert file that contains a certificate signed with the private key in the server.keystore .

Commands:
keytool -export -alias teiid -keystore server.keystore -rfc -file public.cert
Enter keystore password: <password>
5.5.2. File Systems Even with the proper mass storage device, properly configured, and appropriately partitioned, we would still be unable to store and retrieve information easily -- we are missing a way of structuring and organizing that information. What we need is a file system . The concept of a file system is so fundamental to the use of mass storage devices that the average computer user often does not even make the distinction between the two. However, system administrators cannot afford to ignore file systems and their impact on day-to-day work. A file system is a method of representing data on a mass storage device. File systems usually include the following features: File-based data storage Hierarchical directory (sometimes known as "folder") structure Tracking of file creation, access, and modification times Some level of control over the type of access allowed for a specific file Some concept of file ownership Accounting of space utilized Not all file systems posses every one of these features. For example, a file system constructed for a single-user operating system could easily use a more simplified method of access control and could conceivably do away with support for file ownership altogether. One point to keep in mind is that the file system used can have a large impact on the nature of your daily workload. By ensuring that the file system you use in your organization closely matches your organization's functional requirements, you can ensure that not only is the file system up to the task, but that it is more easily and efficiently maintainable. With this in mind, the following sections explore these features in more detail. 5.5.2.1. File-Based Storage While file systems that use the file metaphor for data storage are so nearly universal as to be considered a given, there are still some aspects that should be considered here. First is to be aware of any restrictions on file names. For instance, what characters are permitted in a file name? What is the maximum file name length? These questions are important, as it dictates those file names that can be used and those that cannot. Older operating systems with more primitive file systems often allowed only alphanumeric characters (and only uppercase at that), and only traditional 8.3 file names (meaning an eight-character file name, followed by a three-character file extension).

Commands:
3.13. Example: Create Virtual Machine Storage Disk The following example creates an 8 GB Copy-On-Write storage disk for the example virtual machine. Example 3.15. Create a virtual machine storage disk Request: cURL command: The storage_domain element tells the API to store the disk on the data1 storage domain.

Commands:
POST /ovirt-engine/api/vms/6efc0cfa-8495-4a96-93e5-ee490328cf48/disks HTTP/1.1 Accept: application/xml Content-type: application/xml <disk> <storage_domains> <storage_domain id="9ca7cb40-9a2a-4513-acef-dc254af57aac"/> </storage_domains> <size>8589934592</size> <type>system</type> <interface>virtio</interface> <format>cow</format> <bootable>true</bootable> </disk>
curl -X POST -H "Accept: application/xml" -H "Content-Type: application/xml" -u [USER:PASS] --cacert [CERT] -d "<disk><storage_domains> <storage_domain id='9ca7cb40-9a2a-4513-acef-dc254af57aac'/> </storage_domains><size>8589934592</size><type>system</type> <interface>virtio</interface><format>cow</format> <bootable>true</bootable></disk>" https:// [RHEVM Host] :443/ovirt-engine/api/vms/6efc0cfa-8495-4a96-93e5-ee490328cf48/disks
Chapter 11. Viewing Threads You can view and monitor the state of threads. Procedure : Click the Runtime tab and then the Threads subtab. The Threads page lists active threads and stack trace details for each thread. By default, the thread list shows all threads in descending ID order. To sort the list by increasing ID, click the ID column label. Optionally, filter the list by thread state (for example, Blocked ) or by thread name. To drill down to detailed information for a specific thread, such as the lock class name and full stack trace for that thread, in the Actions column, click More .

Commands:
8.188. pykickstart 8.188.1. RHBA-2014:1541 - pykickstart bug fix and enhancement update An updated pykickstart package that fixes one bug and adds two enhancements is now available for Red Hat Enterprise Linux 6. The pykickstart package contains a python library for manipulating kickstart files. Additionally, this update adds the following enhancement: Note The pykickstart package has been upgraded to upstream version 1.74.15, which provides one bug fix and one enhancement over the version. This version of pykickstart, or higher, is required for the latest version of Anaconda to work properly. (BZ# 1108543 ) Additionally, this update adds the following enhancement: Enhancement BZ# 1125410 The pykickstart package has been modified to support installation of Docker images in Anaconda. Users of pykickstart are advised to upgrade to this updated package, which fixes this bug and adds these enhancements.

Commands:
7.265. virt-manager 7.265.1. RHBA-2013:0451 - virt-manager bug fix and enhancement update Updated virt-manager packages that fix three bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. Virtual Machine Manager (virt-manager) is a graphical tool for administering virtual machines for KVM, Xen, and QEMU. The virt-manager utility uses the libvirt API and can start, stop, add or remove virtualized devices, connect to a graphical or serial console, and view resource usage statistics for existing virtualized guests on local or remote machines. Bug Fixes BZ#802639 Previously, the live migration dialog box of the virt-manager tool incorrectly described the unit of bandwidth as "Mbps" instead of "MB/s". With this update, the migration dialog has been changed to provide correct information on bandwidth units. BZ# 824275 Prior to this update, an unnecessary reboot occurred after the virt-manager tool created a new guest virtual machine by importing an existing disk image. With this update, a backported upstream patch has been provided, and virt-manager no longer restarts after importing an existing disk image. BZ# 872611 Due to differences in dependency solving between the yum and rpm programs, the virt-manager package failed to update from "noarch" to newer architecture version. With this update, a patch has been provided to mark the noarch version as obsolete. As a result, the noarch package can now be updated without complications. Enhancement BZ#878946 The "Delete Associated storage files" option is enabled by default in the virt-manager tool. A warning message is displayed prior to file deletion to notify the user about this configuration. All users of virt-manager are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands: