mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 25. Configuring Direct Deploy When provisioning nodes, director mounts the overcloud base operating system image on an iSCSI mount and then copies the image to disk on each node. Direct deploy is an alternative method that writes disk images from a HTTP location directly to disk on bare metal nodes. Note Support for the iSCSI deploy interface, iscsi , will be deprecated in Red Hat OpenStack Platform (RHOSP) version 17.0, and will be removed in RHOSP 18.0. Direct deploy, direct , will be the default deploy interface from RHOSP 17.0. 25.1. Configuring the direct deploy interface on the undercloud The iSCSI deploy interface is the default deploy interface. However, you can enable the direct deploy interface to download an image from a HTTP location to the target disk. Note Support for the iSCSI deploy interface will be deprecated in Red Hat OpenStack Platform (RHOSP) version 17.0, and will be removed in RHOSP 18.0. Direct deploy will be the default deploy interface from RHOSP 17.0. Prerequisites Your overcloud node memory tmpfs must have at least 8GB of RAM. Procedure Create or modify a custom environment file /home/stack/undercloud_custom_env.yaml and specify the IronicDefaultDeployInterface . By default, the Bare Metal service (ironic) agent on each node obtains the image stored in the Object Storage service (swift) through a HTTP link. Alternatively, ironic can stream this image directly to the node through the ironic-conductor HTTP server. To change the service that provides the image, set the IronicImageDownloadSource to http in the /home/stack/undercloud_custom_env.yaml file: Include the custom environment file in the DEFAULT section of the undercloud.conf file. Perform the undercloud installation:

Commands:
parameter_defaults: IronicDefaultDeployInterface: direct
parameter_defaults: IronicDefaultDeployInterface: direct IronicImageDownloadSource: http
custom_env_files = /home/stack/undercloud_custom_env.yaml
openstack undercloud install
Chapter 2. The pcs Command Line Interface The pcs command line interface provides the ability to control and configure corosync and pacemaker . The general format of the pcs command is as follows. 2.1. The pcs Commands The pcs commands are as follows. cluster Configure cluster options and nodes. For information on the pcs cluster command, see Chapter 3, Cluster Creation and Administration . resource Create and manage cluster resources. For information on the pcs cluster command, see Chapter 5, Configuring Cluster Resources , Chapter 7, Managing Cluster Resources , and Chapter 8, Advanced Resource types . stonith Configure fence devices for use with Pacemaker. For information on the pcs stonith command, see Chapter 4, Fencing: Configuring STONITH . constraint Manage resource constraints. For information on the pcs constraint command, see Chapter 6, Resource Constraints . property Set Pacemaker properties. For information on setting properties with the pcs property command, see Chapter 10, Pacemaker Cluster Properties . status View current cluster and resource status. For information on the pcs status command, see Section 2.5, "Displaying Status" . config Display complete cluster configuration in user-readable form. For information on the pcs config command, see Section 2.6, "Displaying the Full Cluster Configuration" .

Commands:
pcs [-f file ] [-h] [ commands ]
Chapter 3. Viewing your Insights results You can view system and infrastructure results in the Red Hat Insights for Red Hat Enterprise Linux application dashboard. The dashboard provides links to each available Insights service. This includes advisor, vulnerability, compliance, policies and patch. From this starting point, you can proactively identify and manage issues affecting system security, performance, stability and availability. Prerequisites The insights-client package is installed on the system. You are logged in to the Red Hat Hybrid Cloud Console. Procedure Navigate to Red Hat Insights > RHEL > Inventory in the Hybrid Cloud Console. Search for your system name and confirm that it exists in the inventory.

Commands:
2.3.2. Striped Logical Volumes When you write data to an LVM logical volume, the file system lays the data out across the underlying physical volumes. You can control the way the data is written to the physical volumes by creating a striped logical volume. For large sequential reads and writes, this can improve the efficiency of the data I/O. Striping enhances performance by writing data to a predetermined number of physical volumes in round-round fashion. With striping, I/O can be done in parallel. In some situations, this can result in near-linear performance gain for each additional physical volume in the stripe. The following illustration shows data being striped across three physical volumes. In this figure: the first stripe of data is written to PV1 the second stripe of data is written to PV2 the third stripe of data is written to PV3 the fourth stripe of data is written to PV1 In a striped logical volume, the size of the stripe cannnot exceed the size of an extent. Figure 2.5. Striping Data Across Three PVs Striped logical volumes can be extended by concatenating another set of devices onto the end of the first set. In order extend a striped logical volume, however, there must be enough free space on the underlying physical volumes that make up the volume group to support the stripe. For example, if you have a two-way stripe that uses up an entire volume group, adding a single physical volume to the volume group will not enable you to extend the stripe. Instead, you must add at least two physical volumes to the volume group. For more information on extending a striped volume, see Section 4.4.9, "Extending a Striped Volume" .

Commands:
14.8.10. Edit Domain XML Configuration Files save-image-edit file --running --paused command edits the XML configuration file that is associated with a saved file that was created by the virsh save command. Note that the save image records whether the domain should be restored to a --running or --paused state. Without using these options the state is determined by the file itself. By selecting --running or --paused you can overwrite the state that virsh restore should use.

Commands:
Chapter 28. Graphics Driver and Miscellaneous Driver Updates The hv_utils driver, which implements guest/host integration for Hyper-V guests, has been updated to the latest upstream version. The drm subsystem drivers (ast, bochs, cirrus, gma500, i915, mga200, nouveau, qxl, radeon, udl, and vmwgfx) have been updated to version 4.4. The xorg-x11-drv-intel driver has been updated to the latest upstream version.

Commands:
A.4. Generating LDAP URLs LDAP URLs are used in a variety of different configuration areas and operations: referrals and chaining, replication, synchronization, ACIs, and indexing, as a starting list. Constructing accurate LDAP URLs is critical, because incorrect URLs may connect to the wrong server or simply cause operations to fail. Additionally, all OpenLDAP tools allow the -H option to pass an LDAP URL instead of other connection information (like the host name, port, subtree, and search base). Note LDAP URLs are described in Appendix C, LDAP URLs . The ldapurl command manages URL in two ways: Deconstruct a given LDAP URL into its constituent element Construct a new, valid LDAP URL from given elements The parameters for working with URLs are listed in Table A.1, "ldapurl Parameters" ; the full list of parameters are in the OpenLDAP manpages. Table A.1. ldapurl Parameters Option Description For Deconstructing a URL -H " URL " Passes the LDAP URL to break down into elements. For Constructing a URL -a attributes Gives a comma-separated attributes that are specifically returned in search results. -b base Sets the search base or subtree for the URL. -f filter Sets the search filter to use. -h hostname Gives the Directory Server's host name. -p port Gives the Directory Server's port. -S ldap|ldaps|ldapi Gives the protocol to use to connect, such as ldap , ldaps , or ldapi . -s scope Gives the search scope. Example A.8. Deconstructing an LDAP URL ldapurl uses the -H option to feed in an existing LDAP URL, and the tool returns the elements of the URL in a neat list: Example A.9. Constructing an LDAP URL The most useful application of ldapurl is to construct a valid LDAP URL manually. Using ldapurl ensures that the URL is valid. ldapurl accepts the normal connection parameters of all LDAP client tools and additional ldapsearch arguments for search base, scope, and attributes, but this tool never connects to a Directory Server instance, so it does not require any bind information. It accepts the connection and search settings and feeds them in as elements to the URL. ldapurl -a cn,sn -b dc=example,dc=com -s sub -f "(objectclass=inetorgperson)" ldap://:389/dc=example,dc=com?cn,sn?sub?(objectclass=inetorgperson)

Commands:
ldapurl -H "ldap://:389/dc=example,dc=com?cn,sn?sub?(objectclass=inetorgperson)" scheme: ldap port: 389 dn: dc=example,dc=com selector: cn selector: sn scope: sub filter: (objectclass=inetorgperson)
ldapurl -a cn,sn -b dc=example,dc=com -s sub -f "(objectclass=inetorgperson)" ldap://:389/dc=example,dc=com?cn,sn?sub?(objectclass=inetorgperson)
Chapter 6. Packaging and Deploying the Translator 6.1. Packaging Once the "ExecutionFactory" class is implemented, package it in a JAR file. Then add the following named file in "META-INF/services/org.teiid.translator.ExecutionFactory" with contents specifying the name of your main Translator file. Note that, the name must exactly match to above. This is Java's standard service loader pattern. This will register the Translator for deployment when the JAR is deployed.

Commands:
org.teiid.translator.custom.CustomExecutionFactory
Chapter 9. Uninstalling Dev Spaces Warning Uninstalling OpenShift Dev Spaces removes all OpenShift Dev Spaces-related user data! Use oc to uninstall the OpenShift Dev Spaces instance. Prerequisites dsc . See: Section 2.2, "Installing the dsc management tool" . Procedure Remove the OpenShift Dev Spaces instance: Tip The --delete-namespace option removes the OpenShift Dev Spaces namespace. The --delete-all option removes the Dev Workspace Operator and the related resources.

Commands:
dsc server:delete
Chapter 8. Kernel KVM Hypervisor supports 240 vCPUs per virtual machine The KVM hypervisor has been improved to support 240 virtual CPUs (vCPUs) per KVM guest virtual machine. iwlwifi supports Intel(R) Wireless 7265/3165 (Stone Peak) wireless adapter The iwlwifi device driver now supports the Intel(R) Wireless 7265/3165 (Stone Peak) wireless adapter. Support for Wacom 22HD Touch tablets This update adds support for Wacom 22HD Touch tablets, which are now correctly recognized in Red Hat Enterprise Linux and thus functional. Improved page fault scalability for HugeTLB The updated Linux kernel has improved page fault scalability for HugeTLB. Previously only one HugeTLB page fault could be processed at a time because a single mutex was used. The improved method uses a table of mutexes, allowing for page faults to be processed in parallel. Calculation of the mutex table includes the number of page faults occurring and memory in use. kdump supports hugepage filtering To reduce both vmcore size and capture run time, kdump now treats hugepages as userpages and can filter them out. As hugepages are primarily used for application data, they are unlikely to be relevant in the event a vmcore analysis is required. Support for 802.1X EAP packet forwarding on bridges Bridge forwarding of 802.1x EAP packets is now supported, allowing for selective forwarding of some non-control link-local packets. This change also enables the use of 802.1X to authenticate a guest on a RHEL6 hypervisor using Linux bridge on a switch port. Rebase of the mtip32xx driver The Red Hat Enterprise Linux 6.7 kernel includes the most recent upstream version of the mtip32xx device driver. This version adds support for Micron SSD devices. turbostat supports 6th Generation Intel Core Processors The turbostat application now supports Intel's 6th Generation Intel Core Processors.

Commands:
8.164. python-urwid 8.164.1. RHBA-2013:1550 - python-urwid bug fix and enhancement update Updated python-urwid packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The python-urwid package provides a library for development of text user interface applications in the Python programming environment. Note The python-urwid packages have been upgraded to upstream version 1.1.1, which provides a number of bug fixes and enhancements over the version. Among other changes, this update resolves a number of incompatibilities with the version of python-urwid used in Red Hat Enterprise Linux 6. These incompatibilities posed a problem for Red Hat Enterprise Virtualization Hypervisor that requires the python-urwid packages for its new user interface. (BZ# 970981 ) Users of python-urwid are advised to upgrade to these updated packages, which add these enhancements.

Commands:
Chapter 2. Known issues ReadyToRun , which is enabled on a source-to-image build via the DOTNET_PUBLISH_READYTORUN environment variable, is not supported on s390x . The build will print a warning and ignore this variable. The SDK image contains nodeJS to support building JavaScript front-ends in tandem with the .NET backend. Some JavaScript web front-ends cannot be built on s390x and aarch64 due to missing nodeJS packages. .NET 6.0 on s390x does not understand memory and cpu limits in containers. In such environments, it is possible that .NET 6.0 will try to use more memory than allocated to the container, causing the container to get killed or restarted in OpenShift Container Platform. As a workaround you can manually specify a heap limit through an environment variable: MONO_GC_PARAMS=max-heap-size=<limit> . You should set the limit to 75% of the memory allocated to the container. For example, if the container memory limit is 300MB, set MONO_GC_PARAMS=max-heap-size=225M . See Known Issues in the .NET 6.0 Release Notes for .NET 6.0 RPM packages for a list of known issues and workarounds for RPMs.

Commands:
36.5. Verifying the Initial RAM Disk Image If the system uses the ext3 file system, a SCSI controller, or uses labels to reference partitions in /etc/fstab , an initial RAM disk is needed. The initial RAM disk allows a modular kernel to have access to modules that it might need to boot from before the kernel has access to the device where the modules normally reside. On the Red Hat Enterprise Linux architectures other than IBM eServer iSeries, the initial RAM disk can be created with the mkinitrd command. However, this step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by Red Hat, Inc; thus, it does not need to be executed manually. To verify that it was created, use the command ls -l /boot to make sure the initrd- <version> .img file was created (the version should match the version of the kernel just installed). On iSeries systems, the initial RAM disk file and vmlinux file are combined into one file, which is created with the addRamDisk command. This step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by Red Hat, Inc; thus, it does not need to be executed manually. To verify that it was created, use the command ls -l /boot to make sure the /boot/vmlinitrd- <kernel-version> file was created (the version should match the version of the kernel just installed). The step is to verify that the boot loader has been configured to boot the new kernel. Refer to Section 36.6, "Verifying the Boot Loader" for details.

Commands:
16.2. Configuring Clustered Services The IdM server is not cluster aware . However, it is possible to configure a clustered service to be part of IdM by synchronizing Kerberos keys across all of the participating hosts and configuring services running on the hosts to respond to whatever names the clients use. Enroll all of the hosts in the cluster into the IdM domain. Create any service principals and generate the required keytabs. Collect any keytabs that have been set up for services on the host, including the host keytab at /etc/krb5.keytab . Use the ktutil command to produce a single keytab file that contains the contents of all of the keytab files. For each file, use the rkt command to read the keys from that file. Use the wkt command to write all of the keys which have been read to a new keytab file. Replace the keytab files on each host with the newly-created combined keytab file. At this point, each host in this cluster can now impersonate any other host. Some services require additional configuration to accommodate cluster members which do not reset host names when taking over a failed service. For sshd , set GSSAPIStrictAcceptorCheck no in /etc/ssh/sshd_config . For mod_auth_kerb , set KrbServiceName Any in /etc/httpd/conf.d/auth_kerb.conf . Note For SSL servers, the subject name or a subject alternative name for the server's certificate must appear correct when a client connects to the clustered host. If possible, share the private key among all of the hosts. If each cluster member contains a subject alternative name which includes the names of all the other cluster members, that satisfies any client connection requirements.

Commands:
Chapter 3. Eclipse Temurin features Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. For the list of changes and security fixes that the latest OpenJDK 11 release of Eclipse Temurin includes, see OpenJDK 11.0.26 Released . New features and enhancements Eclipse Temurin 11.0.26 includes the following new features and enhancements. Option for jar command to avoid overwriting files when extracting an archive In earlier OpenJDK releases, when the jar tool extracted files from an archive, the jar tool overwrote any existing files with the same name in the target directory. OpenJDK 11.0.26 adds a new ‐k (or ‐‐keep-old-files ) option that you can use to ensure that the jar tool does not overwrite existing files. You can specify this new option in either short or long format. For example: jar xkf myfile.jar jar --extract ‐‐keep-old-files ‐‐file myfile.jar Note In OpenJDK 11.0.26, the jar tool retains the old behavior by default. If you do not explicitly specify the ‐k (or ‐‐keep-old-files ) option, the jar tool automatically overwrites any existing files with the same name. See JDK-8335912 (JDK Bug System) and JDK bug system reference ID: JDK-8337499. IANA time zone database updated to version 2024b In OpenJDK 11.0.26, the in-tree copy of the Internet Assigned Numbers Authority (IANA) time zone database is updated to version 2024b. This update is primarily concerned with improving historical data for Mexico, Mongolia, and Portugal. This update to the IANA database also includes the following changes: Asia/Choibalsan is an alias for Asia/Ulaanbaatar . The Middle European Time (MET) time zone is equal to Central European Time (CET). Some legacy time-zone IDs are mapped to geographical names rather than fixed offsets: Eastern Standard Time (EST) is mapped to America/Panama rather than -5:00 . Mountain Standard Time (MST) is mapped to America/Phoenix rather than -7:00 . Hawaii Standard Time (HST) is mapped to Pacific/Honolulu rather than -10:00 . OpenJDK overrides the change in the legacy time-zone ID mappings by retaining the existing fixed-offset mapping. See JDK-8339637 (JDK Bug System) . Revised on 2025-02-10 17:43:33 UTC

Commands:
25.5. Configuring a Fibre Channel over Ethernet Interface Setting up and deploying a Fibre Channel over Ethernet (FCoE) interface requires two packages: fcoe-utils lldpad Once these packages are installed, perform the following procedure to enable FCoE over a virtual LAN (VLAN): Procedure 25.10. Configuring an Ethernet Interface to Use FCoE To configure a new VLAN, make a copy of an existing network script, for example /etc/fcoe/cfg-eth0 , and change the name to the Ethernet device that supports FCoE. This provides you with a default file to configure. Given that the FCoE device is eth X , run: Modify the contents of cfg-eth X as needed. Notably, set DCB_REQUIRED to no for networking interfaces that implement a hardware Data Center Bridging Exchange (DCBX) protocol client. If you want the device to automatically load during boot time, set ONBOOT=yes in the corresponding /etc/sysconfig/network-scripts/ifcfg-eth X file. For example, if the FCoE device is eth2, edit /etc/sysconfig/network-scripts/ifcfg-eth2 accordingly. Start the data center bridging daemon ( dcbd ) by running: For networking interfaces that implement a hardware DCBX client, skip this step. For interfaces that require a software DCBX client, enable data center bridging on the Ethernet interface by running: Then, enable FCoE on the Ethernet interface by running: Note that these commands only work if the dcbd settings for the Ethernet interface were not changed. Load the FCoE device now using: Start FCoE using: The FCoE device appears soon if all other settings on the fabric are correct. To view configured FCoE devices, run: After correctly configuring the Ethernet interface to use FCoE, Red Hat recommends that you set FCoE and the lldpad service to run at startup. To do so, use the systemctl utility: Note Running the # systemctl stop fcoe command stops the daemon, but does not reset the configuration of FCoE interfaces. To do so, run the # systemctl -s SIGHUP kill fcoe command. As of Red Hat Enterprise Linux 7, Network Manager has the ability to query and set the DCB settings of a DCB capable Ethernet interface.

Commands:
cp /etc/fcoe/cfg-ethx /etc/fcoe/cfg-eth X
systemctl start lldpad
dcbtool sc eth X dcb on
dcbtool sc eth X app:fcoe e:1
ip link set dev eth X up
systemctl start fcoe
fcoeadm -i
systemctl enable lldpad
systemctl enable fcoe
Installation Guide Red Hat Enterprise Linux 6 Installing Red Hat Enterprise Linux 6.9 for all architectures Red Hat Customer Content Services Clayton Spicer Red Hat Customer Content Services cspicer@redhat.com Petr Bokoc Red Hat Customer Content Services Tomas Capek Red Hat Customer Content Services Jack Reed Red Hat Customer Content Services Rudiger Landmann Red Hat Customer Content Services David Cantrell VNC installation Hans De Goede iSCSI Jon Masters Driver updates

Commands:
36.6.3. IBM S/390 and IBM eServer zSeries Systems The IBM S/390 and IBM eServer zSeries systems use z/IPL as the boot loader, which uses /etc/zipl.conf as the configuration file. Confirm that the file contains a section with the same version as the kernel package just installed: Notice that the default is not set to the new kernel. To configure z/IPL to boot the new kernel by default change the value of the default variable to the name of the section that contains the new kernel. The first line of each section contains the name in brackets. After modifying the configuration file, run the following command as root to enable the changes: Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.

Commands:
[defaultboot] default=old target=/boot/ [linux] image=/boot/vmlinuz-2.6.9-5.EL ramdisk=/boot/initrd-2.6.9-5.EL.img parameters="root=LABEL=/" [old] image=/boot/vmlinuz-2.6.9-1.906_EL ramdisk=/boot/initrd-2.6.9-1.906_EL.img parameters="root=LABEL=/"
/sbin/zipl