mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. 11 December 2024 This release Red Hat Ansible Lightspeed features the following enhancement: Playbook generation and viewing playbook explanations are now supported on Red Hat Ansible Lightspeed on-premise deployments. Using the Ansible VS Code extension, you can create Ansible playbooks using a natural language interface in English. You can also view the explanations for new or existing playbooks. For more information, see Creating playbooks and viewing playbook explanations .

Commands:
4.3.2. Converting a virtual machine Once you have prepared to convert the virtual machines, use virt-v2v to perform the actual conversions. This section provides the steps to convert the virtual machines, and the command syntax for virt-v2v . Note that conversions are resource intensive processes that require copying the whole disk image for a virtual machine. In typical environments, converting a single virtual machine takes approximately 5-10 minutes. In Example 4.2, "Typical virt-v2v conversion time" a virtual machine with a single 8GB disk is copied over SSH on a 1GigE network on three-year-old consumer hardware: Example 4.2. Typical virt-v2v conversion time The size of the disk to be copied is the major factor in determining conversion time. For a virtual machine on average hardware with a single disk of 20GB or less, a conversion usually takes less than 10 minutes. 4.3.2.1. virt-v2v virt-v2v converts virtual machines from a foreign hypervisor to run on Red Hat Enterprise Virtualization. The general command syntax for converting machines to run on Red Hat Enterprise Virtualization is: A full specification of the parameters which can be used with virt-v2v is available in Section 7.1, "virt-v2v Parameters" . Important Presently, virt-v2v does not support converting a virtual machine with more than four IDE disks to Red Hat Enterprise Virtualization. Attempting to convert a virtual machine with five or more disks will fail.

Commands:
win2k3r2-pv-32.img: 100% [===========================================]D 0h02m57s virt-v2v: win2k3r2-pv-32 configured with virtio drivers.
virt-v2v -i libvirtxml -o rhev -os storage.example.com:/exportdomain --network rhevm guest_name.xml virt-v2v -o rhev -os storage.example.com:/exportdomain --network rhevm guest_name virt-v2v -ic esx://esx.example.com/?no_verify=1 -o rhev -os storage.example.com:/exportdomain --network rhevm guest_name
Chapter 25. Storage Multi-queue I/O scheduling for SCSI Red Hat Enterprise Linux 7.2 includes a new multiple-queue I/O scheduling mechanism for block devices known as blk-mq. The scsi-mq package allows the Small Computer System Interface (SCSI) subsystem to make use of this new queuing mechanism. This functionality is provided as a Technology Preview and is not enabled by default. To enable it, add scsi_mod.use_blk_mq=Y to the kernel command line. Improved LVM locking infrastructure lvmlockd is a generation locking infrastucture for LVM. It allows LVM to safely manage shared storage from multiple hosts, using either the dlm or sanlock lock managers. sanlock allows lvmlockd to coordinate hosts through storage-based locking, without the need for an entire cluster infrastructure. For more information, see the lvmlockd (8) man page. Targetd plug-in from the libStorageMgmt API Since Red Hat Enterprise Linux 7.1, storage array management with libStorageMgmt, a storage array independent API, has been fully supported. The provided API is stable, consistent, and allows developers to programmatically manage different storage arrays and utilize the hardware-accelerated features provided. System administrators can also use libStorageMgmt to manually configure storage and to automate storage management tasks with the included command-line interface. The Targetd plug-in is not fully supported and remains a Technology Preview. DIF/DIX DIF/DIX is a new addition to the SCSI Standard. It is fully supported in Red Hat Enterprise Linux 7.2 for the HBAs and storage arrays specified in the Features chapter, but it remains in Technology Preview for all other HBAs and storage arrays. DIF/DIX increases the size of the commonly used 512 byte disk block from 512 to 520 bytes, adding the Data Integrity Field (DIF). The DIF stores a checksum value for the data block that is calculated by the Host Bus Adapter (HBA) when a write occurs. The storage device then confirms the checksum on receipt, and stores both the data and the checksum. Conversely, when a read occurs, the checksum can be verified by the storage device, and by the receiving HBA.

Commands:
Chapter 5. Determining whether a printer supports driverless printing CUPS supports driverless printing, which means that you can print without providing any hardware-specific software for the printer model. For this, the printer must inform the client about its capabilities and use one of the following standards: AirPrintTM IPP EverywhereTM Mopria(R) Wi-Fi Direct Print Services You can use the ipptool utility to find out whether a printer supports driverless printing. Prerequisites The printer or remote print server supports the Internet Printing Protocol (IPP). The host can connect to the IPP port of the printer or remote print server. The default IPP port is 631. Procedure Query the ipp-versions-supported and document-format-supported attributes, and ensure that get-printer-attributes test passes: For a remote printer, enter: For a queue on a remote print server, enter: To ensure that driverless printing works, verify in the output: The get-printer-attributes test returns PASS . The IPP version that the printer supports is 2.0 or higher. The list of formats contains one of the following: application/pdf image/urf image/pwg-raster For color printers, the output contains one of the mentioned formats and, additionally, image/jpeg . steps: Add a printer to CUPS by using the web interface Add a printer to CUPS by using the lpadmin utility

Commands:
ipptool -tv ipp:// <ip_address_or_hostname> :631/ipp/print get-printer-attributes.test | grep -E "ipp-versions-supported|document-format-supported|get-printer-attributes" Get printer attributes using get-printer-attributes [PASS] ipp-versions-supported (1setOf keyword) = document-format-supported (1setOf mimeMediaType) =
ipptool -tv ipp:// <ip_address_or_hostname> :631/printers/ <queue_name> get-printer-attributes.test | grep -E "ipp-versions-supported|document-format-supported|get-printer-attributes" Get printer attributes using get-printer-attributes [PASS] ipp-versions-supported (1setOf keyword) = document-format-supported (1setOf mimeMediaType) =
Chapter 5. Planning an SR-IOV deployment Optimize single root I/O virtualization (SR-IOV) deployments for NFV by setting individual parameters based on your Compute node hardware. See Discovering your NUMA node topology to evaluate your hardware impact on the SR-IOV parameters. 5.1. Hardware partitioning for an SR-IOV deployment To achieve high performance with SR-IOV, partition the resources between the host and the guest. A typical topology includes 14 cores per NUMA node on dual socket Compute nodes. Both hyper-threading (HT) and non-HT cores are supported. Each core has two sibling threads. One core is dedicated to the host on each NUMA node. The virtual network function (VNF) handles the SR-IOV interface bonding. All the interrupt requests (IRQs) are routed on the host cores. The VNF cores are dedicated to the VNFs. They provide isolation from other VNFs and isolation from the host. Each VNF must use resources on a single NUMA node. The SR-IOV NICs used by the VNF must also be associated with that same NUMA node. This topology does not have a virtualization overhead. The host, OpenStack Networking (neutron), and Compute (nova) configuration parameters are exposed in a single file for ease, consistency, and to avoid incoherence that is fatal to proper isolation, causing preemption, and packet loss. The host and virtual machine isolation depend on a tuned profile, which defines the boot parameters and any Red Hat OpenStack Platform modifications based on the list of isolated CPUs. 5.2. Topology of an NFV SR-IOV deployment The following image has two VNFs each with the management interface represented by mgt and the data plane interfaces. The management interface manages the ssh access, and so on. The data plane interfaces bond the VNFs to DPDK to ensure high availability, as VNFs bond the data plane interfaces using the DPDK library. The image also has two provider networks for redundancy. The Compute node has two regular NICs bonded together and shared between the VNF management and the Red Hat OpenStack Platform API management. The image shows a VNF that uses DPDK at an application level, and has access to SR-IOV virtual functions (VFs) and physical functions (PFs), for better availability or performance, depending on the fabric configuration. DPDK improves performance, while the VF/PF DPDK bonds provide support for failover, and high availability. The VNF vendor must ensure that the DPDK poll mode driver (PMD) supports the SR-IOV card that is being exposed as a VF/PF. The management network uses OVS, therefore the VNF sees a mgmt network device using the standard virtIO drivers. You can use that device to initially connect to the VNF, and ensure that the DPDK application bonds the two VF/PFs. 5.2.1. Topology for NFV SR-IOV without HCI Observe the topology for SR-IOV without hyper-converged infrastructure (HCI) for NFV in the image below. It consists of compute and controller nodes with 1 Gbps NICs, and the director node.

Commands:
Chapter 8. Sources The updated Red Hat Ceph Storage source code packages are available at the following location: For Red Hat Enterprise Linux 7: http://ftp.redhat.com/redhat/linux/enterprise/7Server/en/RHCEPH/SRPMS/ For Red Hat Enterprise Linux 8: http://ftp.redhat.com/redhat/linux/enterprise/8Base/en/RHCEPH/SRPMS/

Commands:
Chapter 21. Troubleshooting This chapter covers common problems and solutions for Red Hat Enterprise Linux 6 virtualization issues. Read this chapter to develop an understanding of some of the common problems associated with virtualization technologies. Troubleshooting takes practice and experience which are difficult to learn from a book. It is recommended that you experiment and test virtualization on Red Hat Enterprise Linux 6 to develop your troubleshooting skills. If you cannot find the answer in this document there may be an answer online from the virtualization community. Refer to Section B.1, "Online Resources" for a list of Linux virtualization websites. 21.1. Debugging and Troubleshooting Tools This section summarizes the System Administrator applications, the networking utilities, and debugging tools. You can employ these standard System administration tools and logs to assist with troubleshooting: kvm_stat - refer to Section 21.4, "kvm_stat" trace-cmd ftrace Refer to the Red Hat Enterprise Linux Developer Guide vmstat iostat lsof systemtap crash sysrq sysrq t sysrq w These networking tools can assist with troubleshooting virtualization networking problems: ifconfig tcpdump The tcpdump command 'sniffs' network packets. tcpdump is useful for finding network abnormalities and problems with network authentication. There is a graphical version of tcpdump named wireshark . brctl brctl is a networking tool that inspects and configures the Ethernet bridge configuration in the Linux kernel. You must have root access before performing these example commands: Listed below are some other useful commands for troubleshooting virtualization. strace is a command which traces system calls and events received and used by another process. vncviewer : connect to a VNC server running on your server or a virtual machine. Install vncviwer using the yum install tigervnc command. vncserver : start a remote desktop on your server. Gives you the ability to run graphical user interfaces such as virt-manager via a remote session. Install vncserver using the yum install tigervnc-server command.

Commands:
brctl show bridge-name bridge-id STP enabled interfaces ----------------------------------------------------------------------------- virtbr0 8000.feffffff yes eth0 brctl showmacs virtbr0 port-no mac-addr local? aging timer 1 fe:ff:ff:ff:ff: yes 0.00 2 fe:ff:ff:fe:ff: yes 0.00 brctl showstp virtbr0 virtbr0 bridge-id 8000.fefffffffff designated-root 8000.fefffffffff root-port 0 path-cost 0 max-age 20.00 bridge-max-age 20.00 hello-time 2.00 bridge-hello-time 2.00 forward-delay 0.00 bridge-forward-delay 0.00 aging-time 300.01 hello-timer 1.43 tcn-timer 0.00 topology-change-timer 0.00 gc-timer 0.02
Chapter 1. About this guidance document This guide contains documentation about understanding, installing, and configuring Red Hat Certificate System. It is structured into the following parts: Part I, "Part I: Planning how to deploy Red Hat Certificate System" Part II, "Part II: Installing Red Hat Certificate System" Part III, "Part III: Configuring Red Hat Certificate System" Chapter 16, Uninstalling Certificate System subsystems Note Administrators not familiar with Red Hat Certificate System are strongly encouraged to read Part I, "Part I: Planning how to deploy Red Hat Certificate System" for a good understanding of Certificate System and plan ahead accordingly before following Part II, "Part II: Installing Red Hat Certificate System" . Chapter 2, Introduction to Red Hat Certificate System provides a topical overview of several different parts of Certificate System. Chapter 4, Supported platforms lists various components and their supported version by Red Hat. Chapter 5, Planning the Certificate System contains helpful information for planning a Red Hat Certificate System installation. Refer to Chapter 3, Supported Standards and Protocols for a list of compliant and supported standards and protocols. To install Red Hat Certificate System in a compliant manner, follow the instructions in Part II, "Part II: Installing Red Hat Certificate System" . Begin with Chapter 6, Prerequisites for installation to prepare the base operating system. Follow Section 7.2, "Installing RHCS using the pkispawn utility" . Afterwards, follow the required post-installation steps in Section 7.13, "Post-installation" to ensure the complete installation is compliant. This last section links you to relevant parts of the guide which explains the steps to perform for full compliance. Important If installation fails during the pkispawn phase (discussed in Section 7.2, "Installing RHCS using the pkispawn utility" ), it is suggested to check your configuration carefully for mistakes and refer to the error logs. Prior to re-running the pkispawn utility to retry the installation, it is necessary to fully remove the old instance. Refer to Section 16.1, "Removing a subsystem" for information about removing subsystems. For a more complete list of configuration options that are supported and compliant, refer to Part III, "Part III: Configuring Red Hat Certificate System" . This part can only be followed after the installation is complete.

Commands:
Chapter 4. Compiler and Tools gcc-libraries rebased to version 7.2.1 The gcc-libraries packages have been updated to upstream version 7.2.1. This update adds the following enhancements: The libgfortran.so Fortran library has been added to enable running applications built with Red Hat Developer Toolset. Support for certain DEC Fortran formatting extensions has been added to the Fortran library. (BZ# 1465568 , BZ#1554429) Support for retpolines added to GCC This update adds support for retpolines to GCC. Retpolines are a technique used by the kernel to reduce overhead of mitigating Spectre Variant 2 attacks described in CVE-2017-5715. (BZ# 1535656 , BZ#1553817)

Commands:
Chapter 10. Custom Metadata Repository 10.1. Custom Metadata Repository Traditionally the metadata for a Virtual Database is built by Teiid Designer and supplied to the Red Hat JBoss Data Virtualization engine through a VDB archive file. This VDB file contains the metadata files called INDEX files, that are then read by a specific instance of MetadataRepository by name INDEX . In the Dynamic VDB scenario, currently there are three import types available: NATIVE, DDL and FILE.

Commands:
Chapter 11. Creating a Keycloak user This procedure creates a Keycloak user, with the hubadmin role, that can log in to automation hub with Super Administration privileges. Procedure Navigate to Operator Installed Operators . Select the Red Hat Single Sign-On Operator project. Select the Keycloak Realm tab and click Create Keycloak User . On the Keycloak User form, select YAML view . Replace the default YAML file with the following: apiVersion: keycloak.org/v1alpha1 kind: KeycloakUser metadata: name: hubadmin-user labels: app: sso realm: ansible-automation-platform namespace: rh-sso spec: realmSelector: matchLabels: app: sso realm: ansible-automation-platform user: username: hub_admin firstName: Hub lastName: Admin email: hub_admin@example.com enabled: true emailVerified: false credentials: - type: password value: <ch8ngeme> clientRoles: automation-hub: - hubadmin Click Create and wait for the process to complete. When a user is created, the Operator creates a Secret containing both the username and password using the following naming pattern: credential-<realm name>-<username>-<namespace> . In this example the credential is called credential-ansible-automation-platform-hub-admin-rh-sso . When a user is created the Operator does not update the user's password. Password changes are not reflected in the Secret.

Commands:
apiVersion: keycloak.org/v1alpha1 kind: KeycloakUser metadata: name: hubadmin-user labels: app: sso realm: ansible-automation-platform namespace: rh-sso spec: realmSelector: matchLabels: app: sso realm: ansible-automation-platform user: username: hub_admin firstName: Hub lastName: Admin email: hub_admin@example.com enabled: true emailVerified: false credentials: - type: password value: <ch8ngeme> clientRoles: automation-hub: - hubadmin
Chapter 10. Java Lombok This section shows how to enable Lombok support in your Java projects. By default, the lombok.jar file is available in all Java plug-ins provided by CodeReady Workspaces. To enable Lombok in a CodeReady Workspaces workspace, see the instructions below. Prerequisites A workspace or a devfile with: One of the Java-based plug-ins enabled ( redhat/java , redhat/java11 , redhat/java8 , redhat/quarkus-java8 or redhat/quarkus-java11 ) A valid Lombok project to import Procedure Open the workspace devfile. Edit the existing Java plug-in section, adding the preference: - id: redhat/java/latest preferences: java.jdt.ls.vmargs: '-javaagent:/lombok.jar' Verification Start or restart the workspace. Open a file containing Lombok annotations. Verify that the Class outline contains the Lombok generated methods. Additional resources For more details, see the Project Lombok website.

Commands:
- id: redhat/java/latest preferences: java.jdt.ls.vmargs: '-javaagent:/lombok.jar'
4.137. libhbalinux 4.137.1. RHBA-2011:1606 - libhbalinux bug fix and enhancement update An updated libhbalinux package that fixes multiple bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The libhbalinux package contains the Host Bus Adapter API (HBAAPI) vendor library which uses standard kernel interfaces to obtain information about Fiber Channel Host Buses (FC HBA) in the system. The package has been upgraded to upstream version 1.0.12, which provides a number of bug fixes and enhancements over the version. (BZ# 719584 ) Users are advised to upgrade to this updated libhbalinux package, which fixes these bugs and adds these enhancements.

Commands:
23.2. XML Representation of the MAC Address Pools Collection Example 23.1. An XML representation of the MAC address pools collection

Commands:
<mac_pools> <mac_pool href="/ovirt-engine/api/macpools/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"> <name>Default</name> <description>Default MAC pool</description> <allow_duplicates>false</allow_duplicates> <default_pool>true</default_pool> <ranges> <range> <from>00:1A:4A:16:01:51</from> <to>00:1A:4A:16:01:e6</to> </range> </ranges> </mac_pool> </mac_pools>
10.3.4. Deprecated Packages qt3 GFS1 gcj continues to be included in Red Hat Enterprise Linux 6 for performance reasons, however gcj is not likely to be included in future releases. cryptoloop mingw32-qpid-cpp python-qmf python-qpid qpid-cpp qpid-qmf qpid-tests qpid-tools ruby-qpid saslwrapper

Commands:
8.243. xorg-x11-drv-wacom 8.243.1. RHBA-2013:1568 - xorg-x11-drv-wacom bug fix update Updated xorg-x11-drv-wacom packages that fix one bug are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-wacom packages provide an X Window System input device driver that allows the X server to handle Wacom tablets with extended functionality. Bug Fix BZ# 920385 Previously, the xsetwacom command was unable to map the Esc key to one of the buttons on a Wacom Cintiq 22HD tablet using the xsetwacom command. As a consequence, the command failed without displaying an error message, and the key was not mapped. This bug has now been fixed, and, as a result, the driver now maps the Esc key as expected. Users of xorg-x11-drv-wacom are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 12. Eliminating typographical errors in local SSSD configuration You can test if the /etc/sssd/sssd.conf file on your host contains any typographical errors using the sssctl config-check command. Prerequisites You are logged in as root. The sssd-tools package is installed. Procedure Enter the sssctl config-check command: Open the /etc/sssd/sssd.conf file and correct the typo. If you, for example, received the error message in the step, replace ldap_search with ldap_search_base : Save the file. Restart SSSD: Verification Enter the sssctl config-check command: The /etc/sssd/sssd.conf file now has no typographical errors.

Commands:
sssctl config-check Issues identified by validators: 1 [rule/allowed_domain_options]: Attribute 'ldap_search' is not allowed in section 'domain/example1'. Check for typos. Messages generated during configuration merging: 0 Used configuration snippet files: 0
[...] [domain/example1] ldap_search_base = dc=example,dc=com [...]
systemctl restart sssd
sssctl config-check Issues identified by validators: 0 Messages generated during configuration merging: 0 Used configuration snippet files: 0
Chapter 1. Schedule and quota APIs 1.1. AppliedClusterResourceQuota [quota.openshift.io/v1] Description AppliedClusterResourceQuota mirrors ClusterResourceQuota at a project scope, for projection into a project. It allows a project-admin to know which ClusterResourceQuotas are applied to his project and their associated usage. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object 1.2. ClusterResourceQuota [quota.openshift.io/v1] Description ClusterResourceQuota mirrors ResourceQuota at a cluster scope. This object is easily convertible to synthetic ResourceQuota object to allow quota evaluation re-use. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object 1.3. FlowSchema [flowcontrol.apiserver.k8s.io/v1beta1] Description Type `` 1.4. LimitRange [v1] Description LimitRange sets resource usage limits for each kind of resource in a Namespace. Type object 1.5. PriorityClass [scheduling.k8s.io/v1] Description PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer. Type object 1.6. PriorityLevelConfiguration [flowcontrol.apiserver.k8s.io/v1beta1] Description Type `` 1.7. ResourceQuota [v1] Description ResourceQuota sets aggregate quota restrictions enforced per namespace Type object

Commands: