mtpti5iD/redhat-docs_dataset huggingface dataset:
23.2. Creating an LDIF File with Example Group Entries Use the dsctl ldifgen groups command to create an LDIF file with example group entries. For example, to create an LDIF file named /tmp/groups.ldif that adds 500 groups to the ou=groups,dc=example,dc=com entry, and each group has has 100 members, enter: Note that the command also creates LDIF statements to add the user entries in ou=People,dc=example,dc=com . Important If you create large groups and try to add the group using the ldapmodif utility, you can exceed the maximum Basic Encoding Rules (BER) size limit, and the import fails. In this case, increase the value of the nsslapd-maxbersize parameter in the cn=config entry. For further details and other options you can use after you create the LDIF file, enter:

Commands:
dsctl instance_name ldifgen groups --number 500 --suffix "dc=example,dc=com" --parent "ou=groups,dc=example,dc=com" --num-members 100 --create-members --member-parent "ou=People,dc=example,dc=com" --ldif-file /tmp/group.ldif example
dsctl instance_name ldifgen groups --help
Chapter 2. Architectures Red Hat Enterprise Linux 8.2 is distributed with the kernel version 4.18.0-193, which provides support for the following architectures: AMD and Intel 64-bit architectures The 64-bit ARM architecture IBM Power Systems, Little Endian 64-bit IBM Z Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures . For a list of available subscriptions, see Subscription Utilization on the Customer Portal.

Commands:
Chapter 3. Alerts 3.1. Setting up alerts For internal Mode clusters, various alerts related to the storage metrics services, storage cluster, disk devices, cluster health, cluster capacity, and so on are displayed in the Block and File, and the object dashboards. These alerts are not available for external Mode. Note It might take a few minutes for alerts to be shown in the alert panel, because only firing alerts are visible in this panel. You can also view alerts with additional details and customize the display of Alerts in the OpenShift Container Platform. For more information, see Managing alerts . Overprovision control is a mechanism that allows administrators to define a quota on the amount of PVCs consumed from a storage cluster, as per the specific application namespace. When you enable overprovision it prevents you from overprovisioning the PVCs. OpenShift provides a flexibility for defining constraints that limit the aggregated resource consumption at cluster scope with the help of OpenShift's ClusterResourceQuota . With Overprovision control, ClusteResourceQuota is initiated and administrators can set the limit for consumed storage capacity per storage-class. The alarm then triggers at 80% of the capacity limit of the PVC.

Commands:
1.2. High Availability Add-On Introduction The High Availability Add-On is an integrated set of software components that can be deployed in a variety of configurations to suit your needs for performance, high availability, load balancing, scalability, file sharing, and economy. The High Availability Add-On consists of the following major components: Cluster infrastructure - Provides fundamental functions for nodes to work together as a cluster: configuration file management, membership management, lock management, and fencing. High availability Service Management - Provides failover of services from one cluster node to another in case a node becomes inoperative. Cluster administration tools - Configuration and management tools for setting up, configuring, and managing the High Availability Add-On. The tools are for use with the Cluster Infrastructure components, the high availability and Service Management components, and storage. You can supplement the High Availability Add-On with the following components: Red Hat GFS2 (Global File System 2) - Part of the Resilient Storage Add-On, this provides a cluster file system for use with the High Availability Add-On. GFS2 allows multiple nodes to share storage at a block level as if the storage were connected locally to each cluster node. GFS2 cluster file system requires a cluster infrastructure. Cluster Logical Volume Manager (CLVM) - Part of the Resilient Storage Add-On, this provides volume management of cluster storage. CLVM support also requires cluster infrastructure. HAProxy - Routing software that provides high availability load balancing and failover in layer 4 (TCP) and layer 7 (HTTP, HTTPS) services.

Commands:
Chapter 14. Disabling graphics console output for latency sensitive workloads The kernel starts passing messages to printk() as soon as it starts. The kernel sends messages to the log file and also displays on the graphics console even in the absence of a monitor attached to a headless server. In some systems, the output sent to the graphics console might introduce stalls in the pipeline. This might cause potential delay in task execution while waiting for data transfers. For example, outputs sent to teletype0 (/dev/tty0) , might cause potential stalls in some systems. To prevent unexpected stalls, you can limit or disable the information that is sent to the graphic console by: Removing the tty0 definition. Changing the order of console definitions. Turning off most printk() functions and ensuring that you set the ignore_loglevel kernel parameter to not configured . By disabling the graphics console output from logging on and by controlling the messages that print on the graphics console, you can improve latency on sensitive workloads. 14.1. Disabling graphics console logging to graphics adapter The teletype ( tty ) default kernel console enables your interaction with the system by passing input data to the system and displaying the output information about the graphics console. Not configuring the graphics console, prevents it from logging on the graphics adapter. This makes tty0 unavailable to the system and helps disable printing messages on the graphics console. Note Disabling graphics console output does not delete information. The information prints in the system log and you can access them using the journalctl or dmesg utilities. Procedure Remove the console=tty0 option from the kernel configuration: 14.2. Disabling messages from printing on graphics console You can control the amount of output messages that are sent to the graphics console by configuring the required log levels in the /proc/sys/kernel/printk file. Procedure View the current console log level: The command prints the current settings for system log levels. The numbers correspond to current, default, minimum, and boot-default values for the system logger. Configure the desired log level in the /proc/sys/kernel/printk file. The command changes the current console log level. For example, setting log level 1, will print only alert messages and prevent display of other messages on the graphics console.

Commands:
grubby --update-kernel=ALL --remove-args="console=tty0"
cat /proc/sys/kernel/printk 7 4 1 7
echo "1" > /proc/sys/kernel/printk
Chapter 5. Red Hat build of OpenJDK MSI installer components You can set the following Red Hat build of OpenJDK 17 for Microsoft Windows MSI-based installer components. Setting these components is optional. If these components are not set, the default settings will be used. jdk Java Development Kit (JDK) files. Defaults to true , meaning that the jdk component is enabled. jdk_registry_runtime A set of Windows registry keys that other software can use to locate JDK installation files. Defaults to true , meaning that the jdk_registry_runtime component is enabled. This component includes the following registry keys: jdk_env_path Appends <INSTALLDIR>\bin to the system %PATH% environment variable. jdk_env_java_home Sets <INSTALLDIR> to the system %JAVA_HOME% environment variable. jdk_env_vendor_java_home Sets <INSTALLDIR> to the system %REDHAT_JAVA_HOME% environment variable. jdk_registry_jar Association for JAR files. Launch JAR files with the Red Hat build of OpenJDK context menu. jmc JDK Mission Control files, installed into <INSTALLDIR>\missioncontrol . jmc_env Appends <INSTALLDIR>\missioncontrol to the system %PATH% environment variable.

Commands:
HKLM\Software\JavaSoft\JDK\<version>, entries: JavaHome: <INSTALLDIR> RuntimeLib: <INSTALLDIR>\bin\server\jvm.dll HKLM\Software\JavaSoft\JDK, entries: CurrentVersion: <version>
Chapter 18. Publishing the certified container on Red Hat Ecosystem Catalog 18.1. Publishing certified containers After you submit your test results from the preflight tool on your Partner Connect portal , your container images are scanned for vulnerabilities. When the scanning is successfully completed, the publish button will be enabled for your image. After you click the publish button, your image will be available on the Red Hat Ecosystem Catalog . 18.2. Publishing validated containers After submitting your containers for validation, the Red Hat certification team will review and verify the entered details of the validation questionnaire. If at a later date you want to certify your partner validated application, complete the Certification details. The Red Hat certification team will review the submitted test results. After successful verification, to publish your product on the Red Hat Ecosystem Catalog , go to the Product Listings page to attach the Partner Validated or Certified application. Important Red Hat software certification or validation does not conduct testing of the Partner's product in how it functions or performs on the chosen platform. Any and all aspects of the certification candidate product's quality assurance remains the partner's sole responsibility.

Commands:
6.6. Updating Virtual Machine Guest Agents and Drivers The Red Hat Virtualization guest agents, tools, and drivers provide additional functionality for virtual machines, such as gracefully shutting down or rebooting virtual machines from the VM Portal and Administration Portal. The tools and agents also provide information for virtual machines, including: Resource usage IP addresses Installed applications The guest tools are distributed as an ISO file that you can attach to virtual machines. This ISO file is packaged as an RPM file that you can install and update from the Manager machine. 6.6.1. Updating the Guest Agents and Drivers on Red Hat Enterprise Linux Update the guest agents and drivers on your Red Hat Enterprise Linux virtual machines to use the latest version. Updating the Guest Agents and Drivers on Red Hat Enterprise Linux Log in to the Red Hat Enterprise Linux virtual machine. Update the ovirt-guest-agent-common package: Restart the service: For Red Hat Enterprise Linux 6 For Red Hat Enterprise Linux 7 6.6.2. Updating the Guest Agents and Drivers on Windows Updating the Guest Agents, Tools, and Drivers on Windows On the Red Hat Virtualization Manager machine, update the Red Hat Virtualization Guest Tools package to the latest version: The ISO file is located in /usr/share/rhv-guest-tools-iso/RHV-toolsSetup _version .iso on the Manager machine. If the APT service is enabled on virtual machines, the updated ISO files are automatically attached. Otherwise, upload RHV-toolsSetup _version .iso to a data domain. See Uploading Images to a Data Storage Domain in the Administration Guide for details. In the Administration or VM Portal, if the virtual machine is running, use the Change CD drop-down list to attach the RHV-toolsSetup _version .iso file to each of your virtual machines. If the virtual machine is powered off, click the Run Once button and attach the ISO as a CD. Log in to the virtual machine. Select the CD Drive containing the RHV-toolsSetup _version .iso file. Double-click RHEV-toolsSetup.exe . Click at the welcome screen. Follow the prompts on the RHEV-Tools InstallShield Wizard window. Ensure all check boxes in the list of components are selected. Once installation is complete, select Yes, I want to restart my computer now and click Finish to apply the changes.

Commands:
yum update ovirt-guest-agent-common
service ovirt-guest-agent restart
systemctl restart ovirt-guest-agent.service
yum update -y rhv-guest-tools-iso*
Chapter 1. Introduction Migration Toolkit for Runtimes product will be End of Life on September 30th, 2024 All customers using this product should start their transition to Migration Toolkit for Applications . Migration Toolkit for Applications is fully backwards compatible with all features and rulesets available in Migration Toolkit for Runtimes and will be maintained in the long term. 1.1. About the Rule Development Guide This guide is intended for software engineers who want to create custom YAML-based rules for Migration Toolkit for Runtimes (MTR) tools. See the Introduction to the Migration Toolkit for Runtimes for an overview and the CLI Guide for details. 1.1.1. Use of <MTR_HOME> in this guide This guide uses the <MTR_HOME> replaceable variable to denote the path to your MTR installation. The installation directory is the mtr-1.2.7.GA-offline directory where you extracted the MTR .zip file. When you encounter <MTR_HOME> in this guide, replace it with the actual path to your MTR installation. 1.2. The MTR rules The Migration Toolkit for Runtimes (MTR) contains rule-based migration tools (analyzers) that you can use to analyze the application user interfaces (APIs), technologies, and architectures used by the applications you plan to migrate. MTR analyzer rules use the following rule pattern: You can use the MTR rules internally to perform the following tasks: Extract files from archives. Decompile files. Scan and classify file types. Analyze XML and other file content. Analyze the application code. Build the reports. MTR builds a data model based on the rule execution results and stores component data and relationships in a graph database. This database can then be queried and updated as required by the migration rules and for reporting purposes. Note You can create your own custom analyzer rules. You can use custom rules to identify the use of custom libraries or other components that might not be covered by the provided standard migration rules. For instructions on how to write custom rules, see [ Rule Development Guide ].

Commands:
when(condition) message(message) tag(tags)
18.3. Methods 18.3.1. Creating a New Virtual Machine Pool A new pool requires the name , cluster and template elements. Identify the cluster and template with the id attribute or name element. Example 18.2. Creating a virtual machine pool 18.3.2. Updating a Virtual Machine Pool The name , description , size , prestarted_vms and max_user_vms can be updated after the virtual machine has been created. Example 18.3. Updating a virtual machine pool 18.3.3. Removing a Virtual Machine Pool Removal of a virtual machine pool requires a DELETE request. Example 18.4. Removing a virtual machine

Commands:
POST /ovirt-engine/api/vmpools HTTP/1.1 Accept: application/xml Content-type: application/xml <vmpool> <name>VM_Pool_A</name> <cluster href="/ovirt-engine/api/clusters/99408929-82cf-4dc7-a532-9d998063fa95"/> id="99408929-82cf-4dc7-a532-9d998063fa95" <template href="/ovirt-engine/api/templates/00000000-0000-0000-0000-000000000000"/> id="00000000-0000-0000-0000-000000000000" </vmpool>
PUT /ovirt-engine/api/vmpools/2d2d5e26-1b6e-11e1-8cda-001320f76e8e HTTP/1.1 Accept: application/xml Content-type: application/xml <vmpool> <name>VM_Pool_B</name> <description>Virtual Machine Pool B</description> <size>3</size> <prestarted_vms>1</size> <max_user_vms>2</size> </vmpool>
DELETE /ovirt-engine/api/vmpools/2d2d5e26-1b6e-11e1-8cda-001320f76e8e HTTP/1.1 HTTP/1.1 204 No Content
Appendix A. Revision History Revision History Revision 0.1-0 Thu Apr 27 2017 Lenka Spackova Added the deprecated zerombr yes Kickstart command to Deprecated Functionality. Revision 0.0-9 Tue Mar 21 2017 Jiri Herrmann Further update to Deprecated Functionality. Revision 0.0-8 Fri Jun 03 2016 Lenka Spackova Updated Deprecated Functionality. Revision 0.0-7 Tue May 10 2016 Lenka Spackova Moved Btrfs and eCryptfs file systems from Technology Previews to Deprecated Functionality. Revision 0.0-6 Wed Mar 30 2016 Lenka Spackova Updated Technology Previews (added clufter ), Deprecated Functionality (intro, storage drivers). Revision 0.0-5 Thu Jan 21 2016 Lenka Spackova Added information about the removed systemtap-grapher package to the Deprecated Functionality Chapter. Revision 0.0-4 Mon Jan 04 2016 Lenka Spackova Added information on the i40e and i40evf kernel drivers to the Technology Previews chapter. Fixed Russian font package names. Revision 0.0-1.1 Mon Jul 20 2015 Laura Bailey Release of the Red Hat Enterprise Linux 6.7 GA Technical Notes. Revision 0.0-0.2 Wed Apr 29 2015 Radek Biba Release of the Red Hat Enterprise Linux 6.7 Beta Technical Notes.

Commands:
Chapter 99. KafkaTopicSpec schema reference Used in: KafkaTopic Property Property type Description partitions integer The number of partitions the topic should have. This cannot be decreased after topic creation. It can be increased after topic creation, but it is important to understand the consequences that has, especially for topics with semantic partitioning. When absent this will default to the broker configuration for num.partitions . replicas integer The number of replicas the topic should have. When absent this will default to the broker configuration for default.replication.factor . config map The topic configuration. topicName string The name of the topic. When absent this will default to the metadata.name of the topic. It is recommended to not set this unless the topic name is not a valid OpenShift resource name.

Commands:
8.125. libvirt-cim 8.125.1. RHBA-2014:1581 - libvirt-cim bug fix update Updated libvirt-cim packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The libvirt-cim packages provide a Common Manageability Programming Interface (CMPI) CIM provider that implements the Distributed Management Task Force (DMTF) System Virtualization, Partitioning and Clustering (SVPC) virtualization model. These packages support most of the features of libvirt and enable management of multiple platforms with a single provider. Bug Fixes BZ# 1010283 Due to incorrect string parsing, an attempt to access a store pool that contained a space in its name failed unexpectedly. This update provides a patch to fix this bug and such store pools can now be accessed as expected. BZ# 1046280 Prior to this update, the libvirt-cim provider did not allow customization of the "machine" and "arch" properties for the "type" attribute of the "os" element for the domain XML file. As a consequence, a default value was provided, overwriting a possible customization for libvirt-cim. To fix this bug, the code has been adjusted to allow modifications of the "machine" and "arch" properties of the "type" attribute for the "os" element. As a result, it is now possible to set the fields as desired using the "ModifySystemSettings" method and adjusting the "SystemSettings" values for the KVM_VirtualSystemSettingData "machine" field. BZ# 1119165 Previously, an incorrect variable was used when overwriting certain tags in domain XML files. Consequently, settings for the dumpCore attribute were ignored. With this update, a patch has been provided to fix this bug and the attribute is no longer ignored in the described scenario. In addition, the libvirt-cim provider now supports the dumpCore feature. Users of libvirt-cim are advised to upgrade to these updated packages, which fix these bugs.

Commands:
3.4. IPv4 and IPv6 Addresses Certificate System supports both IPv4 addresses and IPv6 addresses. In a very wide variety of circumstances, Certificate System subsystems or operations reference a host name or IP address; supporting both IPv4- and IPv6-style addresses ensures forward compatibility with network protocols. The operations that support IPv6 connections include the following: Communications between subsystems, including between the TPS, TKS, and CA and for joining security domains Token operations between the TPS and the Enterprise Security Client Subsystem logging Access control instructions Operations performed with Certificate System tools, including the pki utility, the Subject Alt Name Extension tool, HttpClient, and the Bulk Issuance Tool Client communications, including both the pkiconsole utility and IPv6-enabled browsers for web services Certificate request names and certificate subject names, including user, server, and router certificates Publishing Connecting to LDAP databases for internal databases and authentication directories Any time a host name or URL is referenced, an IP address can be used: An IPv4 address must be in the format n.n.n.n or n.n.n.n,m.m.m.m . For example, 128.21.39.40 or 128.21.39.40,255.255.255.00 . An IPv6 address uses a 128-bit namespace, with the IPv6 address separated by colons and the netmask separated by periods. For example, 0:0:0:0:0:0:13.1.68.3 , FF01::43 , or 0:0:0:0:0:0:13.1.68.3,FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:255.255.255.0 . If DNS is properly configured, then an IPv4 or IPv6 address can be used to connect to the web services pages and to the subsystem Java consoles. The most common method is to use fully-qualified domain names: To use IPv6 numeric addresses, replace the fully-qualified domain name in the URL with the IPv6 address, enclosed in brackets ( [] ). For example:

Commands:
https://ipv6host.example.com:8443/ca/services pkiconsole https://ipv6host.example.com:8443/ca
https://[00:00:00:00:123:456:789:00:]:8443/ca/services pkiconsole https://[00:00:00:00:123:456:789:00:]:8443/ca
7.19. biosdevname 7.19.1. RHBA-2015:1338 - biosdevname bug fix and enhancement update Updated biosdevname packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The biosdevname packages contain an optional convention for naming network interfaces, which assigns names to network interfaces based on their physical location. The biosdevname utility is disabled by default, except for a limited set of Dell PowerEdge, C Series, and Precision Workstation systems. Note The biosdevname packages have been upgraded to upstream version 0.6.2, which provides a number of bug fixes and enhancements over the version. Notably, it provides the *dev_port* attribute for a new Mellanox driver and allowing naming of FCoE devices to be ignored. (BZ# 1158564 ) Bug Fixes BZ# 1133523 Previously, the biosdevname utility did not parse Vital Product Data (VPD) correctly. As a consequence, names for network interfaces on Vindicator 2 Emulex card were displayed incorrectly when NIC extended partitioning (nPAR-EP) was enabled. VPD parsing has been modified, and Network interface names are now displayed correctly. BZ# 1207557 Prior to this update, the biosdevname utility did not read Vital Product Data (VPD) on NICs with vpd-r:2.0, which resulted in incorrect network interface names when NIC partitioning (NPAR) was enabled on certain NICs. With this update, biosdevname reads VPD data also in cases when NIC has vpdr:2.0, and interface names are now formed as expected if NPAR is enabled. BZ# 1212449 Due to a scheme used for slot numbers derivation, the biosdevname utility did not populate proper names for Virtual Functions (VFs) of on-board NICs. Now, the scheme that enables VFs of on-board NICs can have proper names, too. Enhancements BZ# 1158564 attribute for a new Mellanox driver and allowing naming of FCoE devices to be ignored. BZ# 1003465 , BZ# 1084225 This update provides an implementation of 10-GB Ethernet adapters naming scheme from Mellanox. Now, the biosdevname utility produces expected network interface names for Mellanox 10-GB Ethernet adapters that have 2 physical ports on the same PCI device. The /sys/class/net/<iface>/dev_port attribute is designed to distinguish network interfaces. Users of biosdevname are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands: