mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 121. KafkaMirrorMakerProducerSpec schema reference Used in: KafkaMirrorMakerSpec Full list of KafkaMirrorMakerProducerSpec schema properties Configures a MirrorMaker producer. 121.1. abortOnSendFailure Use the producer.abortOnSendFailure property to configure how to handle message send failure from the producer. By default, if an error occurs when sending a message from Kafka MirrorMaker to a Kafka cluster: The Kafka MirrorMaker container is terminated in OpenShift. The container is then recreated. If the abortOnSendFailure option is set to false , message sending errors are ignored. 121.2. config Use the producer.config properties to configure Kafka options for the producer as keys. The values can be one of the following JSON types: String Number Boolean Exceptions You can specify and configure the options listed in the Apache Kafka configuration documentation for producers . However, Streams for Apache Kafka takes care of configuring and managing options related to the following, which cannot be changed: Kafka cluster bootstrap address Security (encryption, authentication, and authorization) Interceptors Properties with the following prefixes cannot be set: bootstrap.servers interceptor.classes sasl. security. ssl. If the config property contains an option that cannot be changed, it is disregarded, and a warning message is logged to the Cluster Operator log file. All other supported options are forwarded to MirrorMaker, including the following exceptions to the options configured by Streams for Apache Kafka: Any ssl configuration for supported TLS versions and cipher suites Important The Cluster Operator does not validate keys or values in the config object provided. If an invalid configuration is provided, the MirrorMaker cluster might not start or might become unstable. In this case, fix the configuration so that the Cluster Operator can roll out the new configuration to all MirrorMaker nodes. 121.3. KafkaMirrorMakerProducerSpec schema properties Property Property type Description bootstrapServers string A list of host:port pairs for establishing the initial connection to the Kafka cluster. abortOnSendFailure boolean Flag to set the MirrorMaker to exit on a failed send. Default value is true . authentication KafkaClientAuthenticationTls , KafkaClientAuthenticationScramSha256 , KafkaClientAuthenticationScramSha512 , KafkaClientAuthenticationPlain , KafkaClientAuthenticationOAuth Authentication configuration for connecting to the cluster. config map The MirrorMaker producer config. Properties with the following prefixes cannot be set: ssl., bootstrap.servers, sasl., security., interceptor.classes (with the exception of: ssl.endpoint.identification.algorithm, ssl.cipher.suites, ssl.protocol, ssl.enabled.protocols). tls ClientTls TLS configuration for connecting MirrorMaker to the cluster.

Commands:
3.3.4. Converting a remote Xen virtual machine Xen virtual machines can be converted remotely using SSH. Ensure that the host running the virtual machine is accessible via SSH. To convert the virtual machine, run: Where vmhost.example.com is the host running the virtual machine, pool is the local storage pool to hold the image, bridge_name is the name of a local network bridge to connect the converted virtual machine's network to, and guest_name is the name of the Xen virtual machine. You may also use the --network parameter to connect to a locally managed network if your virtual machine only has a single network interface. If your virtual machine has multiple network interfaces, edit /etc/virt-v2v.conf to specify the network mapping for all interfaces. If your virtual machine uses a Xen paravirtualized kernel (it would be called something like kernel-xen or kernel-xenU ) virt-v2v will attempt to install a new kernel during the conversion process. You can avoid this requirement by installing a regular kernel, which will not reference a hypervisor in its name, alongside the Xen kernel prior to conversion. You should not make this newly installed kernel your default kernel, because Xen will not boot it. virt-v2v will make it the default during conversion. Note When converting from Xen, virt-v2v requires that the image of the source virtual machine exists in a storage pool. If the image is not currently in a storage pool, you must create one. Contact Red Hat Support for assistance creating an appropriate storage pool.

Commands:
virt-v2v -ic qemu+ssh://root@vmhost.example.com/system -op pool --bridge bridge_name guest_name
Development Guidelines and Recommended Practices Guide Red Hat JBoss Data Virtualization 6.4 David Le Sage dlesage@redhat.com

Commands:
{vdbname}.{version}.vdb
<cache-container name="ws-cache-container" default-cache="X/system" module="org.modeshape"> <local-cache name="X/system"> <eviction strategy="LRU" max-entries="100"/> <expiration lifespan="10000" interval="1000" max-idle="5000"/> </local-cache> <local-cache name="X/default"> <eviction strategy="LRU" max-entries="100"/> <expiration lifespan="10000" interval="1000" max-idle="5000"/> </local-cache> </cache-container>
<repository name="X"...> <workspaces cache-container="ws-cache-container">
E.2.27. /proc/sysrq-trigger Using the echo command to write to this file, a remote root user can execute most System Request Key commands remotely as if at the local terminal. To echo values to this file, the /proc/sys/kernel/sysrq must be set to a value other than 0 . For more information about the System Request Key, see Section E.3.9.3, "/proc/sys/kernel/" . Although it is possible to write to this file, it cannot be read, even by the root user.

Commands:
8.138. microcode_ctl 8.138.1. RHEA-2014:1466 - microcode_ctl enhancement update Updated microcode_ctl packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The microcode_ctl packages provide microcode updates for Intel and AMD processors. Enhancement BZ# 1036240 , BZ# 1113394 The Intel CPU microcode file has been updated to version 20140624. This is the most recent version of the microcode available from Intel. Users of microcode_ctl are advised to upgrade to these updated packages, which add this enhancement. Note that the system must be rebooted for this update to take effect.

Commands:
Installation Guide Red Hat Enterprise Linux 7 Installing Red Hat Enterprise Linux 7 on all architectures Jana Heves Red Hat Customer Content Services jsvarova@redhat.com Vladimir Slavik Red Hat Customer Content Services vslavik@redhat.com Abstract This manual explains how to boot the Red Hat Enterprise Linux 7 installation program ( Anaconda ) and how to install Red Hat Enterprise Linux 7 on AMD64 and Intel 64 systems, 64-bit ARM systems, 64-bit IBM Power Systems servers, and IBM Z servers. It also covers advanced installation methods such as Kickstart installations, PXE installations, and installations over VNC. Finally, it describes common post-installation tasks and explains how to troubleshoot installation problems. Information on installing Red Hat Enterprise Linux Atomic Host can be found in the Red Hat Enterprise Linux Atomic Host Installation and Configuration Guide .

Commands:
3.6. Resource Actions RGManager expects the following return actions to be implemented in resource agents: start - start the resource stop - stop the resource status - check the status of the resource metadata - report the OCF RA XML metadata 3.6.1. Return Values OCF has a wide range of return codes for the monitor operation, but since RGManager calls status, it relies almost exclusively on SysV-style return codes. 0 - success stop after stop or stop when not running must return success start after start or start when running must return success nonzero - failure if the stop operation ever returns a nonzero value, the service enters the failed state and the service must be recovered manually.

Commands:
Chapter 22. Message Grouping A message group is a group of messages that share certain characteristics: All messages in a message group are grouped under a common group ID. This means that they can be identified with a common group property. All messages in a message group are serially processed and consumed by the same consumer, irrespective of the number of customers on the queue. This means that a specific message group with a unique group id is always processed by one consumer when the consumer opens it. If the consumer closes the message group, then the entire message group is directed to another consumer in the queue. Message groups are especially useful when there is a need for messages with a certain value of the property, such as group ID, to be processed serially by a single consumer. Important Message grouping will not work as expected if the queue has paging enabled. Be sure to disable paging before configuring a queue for message grouping. For information about configuring message grouping within a cluster of messaging servers, see Clustered Message Grouping in Part III, Configuring Multiple Messaging Systems . 22.1. Configuring Message Groups Using the Core API The property _AMQ_GROUP_ID is used to identify a message group using the Core API on the client side. To pick a random unique message group identifier, you can also set the auto-group property to true on the SessionFactory . 22.2. Configuring Message Groups Using Jakarta Messaging The property JMSXGroupID is used to identify a message group for Jakarta Messaging clients. If you wish to send a message group with different messages to one consumer, you can set the same JMSXGroupID for different messages. Message message = ... message.setStringProperty("JMSXGroupID", "Group-0"); producer.send(message); message = ... message.setStringProperty("JMSXGroupID", "Group-0"); producer.send(message); An alternative approach is to use the one of the following attributes of the connection-factory to be used by the client: auto-group or group-id . When auto-group is set to true , the connection-factory will begin to use a random unique message group identifier for all messages sent through it. You can use the management CLI to set the auto-group attribute. The group-id attribute will set the property JMSXGroupID to the specified value for all messages sent through the connection factory. To set a specific group-id on the connection factory, use the management CLI.

Commands:
Message message = message.setStringProperty("JMSXGroupID", "Group-0"); producer.send(message); message = message.setStringProperty("JMSXGroupID", "Group-0"); producer.send(message);
/subsystem=messaging-activemq/server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=auto-group,value=true)
/subsystem=messaging-activemq/server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=group-id,value="Group-0")
Preface Learn how to use both the OpenShift command-line interface and web console to install Red Hat OpenShift AI Self-Managed on your OpenShift cluster. To uninstall the product, learn how to use the recommended command-line interface (CLI) method. Note Red Hat does not support installing more than one instance of OpenShift AI on your cluster. Red Hat does not support installing the Red Hat OpenShift AI Operator on the same cluster as the Red Hat OpenShift AI Add-on.

Commands:
5.311. squid 5.311.1. RHBA-2012:1290 - squid bug fix update Updated squid packages that fix several bugs are now available for Red Hat Enterprise Linux 6. [Updated 20th September 2012] This advisory has been updated with an accurate description of the "http10" option for BZ#852863. This update does not change the packages in any way. Squid is a high-performance proxy caching server for web clients that supports FTP, Gopher, and HTTP data objects. Bug Fixes BZ# 853053 Due to a bug in the ConnStateData::noteMoreBodySpaceAvailable() function, child processes of squid aborted upon encountering a failed assertion. An upstream patch has been provided to address this issue and squid child processes no longer abort in the described scenario. BZ# 852863 Due to an upstream patch, which renamed the HTTP header controlling persistent connections from "Proxy-Connection" to "Connection", the NTLM pass-through authentication does not work, thus preventing login. This update introduces the new "http10" option to the squid.conf file, which can be used to enable the change in the patch. This option is set to "off" by default. When set to "on", the NTLM pass-through authentication works properly, thus allowing login attempts to succeed. BZ# 852861 When the IPv6 protocol was disabled and squid tried to handle an HTTP GET request containing an IPv6 address, the squid child process terminated due to signal 6. This bug has been fixed and such requests are now handled as expected. BZ# 855330 The old "stale if hit" logic did not account for cases where the stored stale response became fresh due to a successful re-validation with the origin server. Consequently, incorrect warning messages were returned. With this update, squid no longer marks elements as stale in the described scenario, thus fixing this bug. All users of squid are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 13. Volumes 13.1. Creating Volumes This section shows how to create disk volumes inside a block based storage pool. In the example below, the virsh vol-create-as command will create a storage volume with a specific size in GB within the guest_images_disk storage pool. As this command is repeated per volume needed, three volumes are created as shown in the example.

Commands:
# virsh vol-create-as guest_images_disk volume1 8 G Vol volume1 created # virsh vol-create-as guest_images_disk volume2 8 G Vol volume2 created # virsh vol-create-as guest_images_disk volume3 8 G Vol volume3 created # virsh vol-list guest_images_disk Name Path ----------------------------------------- volume1 /dev/sdb1 volume2 /dev/sdb2 volume3 /dev/sdb3 # parted -s /dev/sdb print Model: ATA ST3500418AS (scsi) Disk /dev/sdb: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 2 17.4kB 8590MB 8590MB primary 3 8590MB 17.2GB 8590MB primary 1 21.5GB 30.1GB 8590MB primary
Chapter 18. Managing Out of Memory states Out-of-memory (OOM) is a computing state where all available memory, including swap space, has been allocated. Normally this causes the system to panic and stop functioning as expected. The provided instructions help in avoiding OOM states on your system. Prerequisites You have root permissions on the system. 18.1. Changing the Out of Memory value The /proc/sys/vm/panic_on_oom file contains a value which is the switch that controls Out of Memory (OOM) behavior. When the file contains 1 , the kernel panics on OOM and stops functioning as expected. The default value is 0 , which instructs the kernel to call the oom_killer() function when the system is in an OOM state. Usually, oom_killer() terminates unnecessary processes, which allows the system to survive. You can change the value of /proc/sys/vm/panic_on_oom . Procedure Display the current value of /proc/sys/vm/panic_on_oom . To change the value in /proc/sys/vm/panic_on_oom : Echo the new value to /proc/sys/vm/panic_on_oom . Note It is recommended that you make the Real-Time kernel panic on OOM ( 1 ). Otherwise, when the system encounters an OOM state, it is no longer deterministic. Verification Display the value of /proc/sys/vm/panic_on_oom . Verify that the displayed value matches the value specified. 18.2. Prioritizing processes to kill when in an Out of Memory state You can prioritize the processes that get terminated by the oom_killer() function. This can ensure that high-priority processes keep running during an OOM state. Each process has a directory, /proc/ PID . Each directory includes the following files: oom_adj - Valid scores for oom_adj are in the range -16 to +15. This value is used to calculate the performance footprint of the process, using an algorithm that also takes into account how long the process has been running, among other factors. oom_score - Contains the result of the algorithm calculated using the value in oom_adj . In an Out of Memory state, the oom_killer() function terminates processes with the highest oom_score . You can prioritize the processes to terminate by editing the oom_adj file for the process. Prerequisites Know the process ID (PID) of the process you want to prioritize. Procedure Display the current oom_score for a process. Display the contents of oom_adj for the process. Edit the value in oom_adj . Verification Display the current oom_score for the process. Verify that the displayed value is lower than the value. 18.3. Disabling the Out of Memory killer for a process You can disable the oom_killer() function for a process by setting oom_adj to the reserved value of -17 . This will keep the process alive, even in an OOM state. Procedure Set the value in oom_adj to -17 . Verification Display the current oom_score for the process. Verify that the displayed value is 0 .

Commands:
cat /proc/sys/vm/panic_on_oom 0
echo 1 > /proc/sys/vm/panic_on_oom
cat /proc/sys/vm/panic_on_oom 1
cat /proc/12465/oom_score 79872
cat /proc/12465/oom_adj 13
echo -5 > /proc/12465/oom_adj
cat /proc/12465/oom_score 78
echo -17 > /proc/12465/oom_adj
cat /proc/12465/oom_score 0
probe::ipmib.FragFails Name probe::ipmib.FragFails - Count datagram fragmented unsuccessfully Synopsis ipmib.FragFails Values op Value to be added to the counter (default value of 1) skb pointer to the struct sk_buff being acted on Description The packet pointed to by skb is filtered by the function ipmib_filter_key . If the packet passes the filter is is counted in the global FragFails (equivalent to SNMP's MIB IPSTATS_MIB_FRAGFAILS)

Commands:
2.2.7.2. NFS and Postfix Never put the mail spool directory, /var/spool/postfix/ , on an NFS shared volume. Because NFSv2 and NFSv3 do not maintain control over user and group IDs, two or more users can have the same UID, and receive and read each other's mail. Note With NFSv4 using Kerberos, this is not the case, since the SECRPC_GSS kernel module does not utilize UID-based authentication. However, it is still considered good practice not to put the mail spool directory on NFS shared volumes.

Commands:
Chapter 59. Installation and Booting FIPS mode unsupported when installing from an HTTPS kickstart source Installation images do not support FIPS mode during installation with an HTTPS kickstart source. As a consequence, it is currently impossible to to install a system with the fips=1 and inst.ks=https://<location>/ks.cfg options added to the command line. (BZ# 1341280 ) PXE boot with UEFI and IPv6 displays the GRUB2 shell instead of the operating system selection menu When the Pre-Boot Execution Environment (PXE) starts on a client configured with UEFI and IPv6, the boot menu configured in the /boot/grub/grub.cfg file is not displayed. After a timeout, the GRUB2 shell is displayed instead of the configured operating system selection menu. (BZ#1154226) Specifying a driverdisk partition with non-alphanumeric characters generates an invalid output Kickstart file When installing Red Hat Enterprise Linux using the Anaconda installer, you can add a driver disk by including a path to the partition containing the driver disk in the Kickstart file. At present, if you specify the partition by LABEL or CDLABEL which has non-alphanumeric characters in it, for example: the output Kickstart file created during the Anaconda installation will contain incorrect information. To work around this problem, use only alphanumeric characters when specifying the partition by LABEL or CDLABEL. (BZ# 1452770 ) The Scientific Computing variant is missing packages required for certain security profiles When installing the Red Hat Enterprise Linux for Scientific Computing variant, also known as Compute Node, you can select a security profile similarly to any other variant's installation process. However, since this variant is meant to be minimal, it is missing packages which are required by certain profiles, such as United States Government Configuration Baseline . If you select this profile, the installer displays a warning that some packages are missing. The warning allows you to continue the installation despite missing packages, which can be used to work around the problem. The installation will complete normally, however, note that if you install the system despite the warning, and then attempt to run a security scan after the installation, the scan will report failing rules due to these missing packages. This behavior is expected. (BZ#1462647)

Commands:
driverdisk "CDLABEL=Fedora 23 x86_64:/path/to/rpm"
C.3. Application Restrictions There are aspects of virtualization that make it unsuitable for certain types of applications. Applications with high I/O throughput requirements should use KVM's paravirtualized drivers (virtio drivers) for fully-virtualized guests. Without the virtio drivers, certain applications may be unpredictable under heavy I/O loads. The following applications should be avoided due to high I/O requirements: kdump server netdump server You should carefully evaluate applications and tools that heavily utilize I/O or those that require real-time performance. Consider the virtio drivers or PCI device assignment for increased I/O performance. For more information on the virtio drivers for fully virtualized guests, see Chapter 5, KVM Paravirtualized (virtio) Drivers . For more information on PCI device assignment, see Chapter 16, Guest Virtual Machine Device Configuration . Applications suffer a small performance loss from running in virtualized environments. The performance benefits of virtualization through consolidating to newer and faster hardware should be evaluated against the potential application performance issues associated with using virtualization.

Commands:
Chapter 3. Setting the simple content access mode from the Hybrid Cloud Console When you create a new manifest, simple content access is enabled by default. Simple content access gives you the ability to consume content on your systems without strict entitlement enforcement. However, if you have an environment where simple content access is not appropriate for all manifests, the Subscriptions administrator can change the simple content access mode for each manifest, as needed. For Red Hat Satellite version 6.5 and later, you can set the simple content access mode for a particular manifest directly from the Manifests page on the Hybrid Cloud Console. You can check whether simple content access is enabled for a manifest from the setting that is displayed in the Simple Content Access column in the Manifests table. For Red Hat Satellite versions older than 6.5, the Simple Content Access column displays N/A because simple content access is not available for those versions of Satellite. Prerequisites You are logged in to the Red Hat Hybrid Cloud Console. You are connected to a Red Hat Satellite Server. You have Red Hat Satellite 6 or later. You have the Subscriptions administrator role in the role-based access control (RBAC) system for the Red Hat Hybrid Cloud Console. Procedure To set the simple content access mode to Enabled or Disabled , complete the following steps: From the Hybrid Cloud Console home page, click Services > Subscriptions and Spend > Manifests . From the Manifests page, locate the name of the manifest that you want to modify in the Manifests table. In the Simple Content Access column, set the simple content access switch to Enabled or Disabled , depending on the mode that you want to use for that manifest. Note The ability to set the simple content access mode for manifests is only available in Satellite versions 6.5 and later. Note In Satellite 6.13, the simple content access status is set on the Satellite organization, not on the manifest. Importing a manifest does not change your organization's simple content access status. Addtional resources For information about enabling simple content access on a Satellite organization, see Managing Organizations .

Commands: