mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Event-driven APIs Many of the APIs provided with AMQ Clients are asynchronous, event-driven APIs. These include the C++, JavaScript, Python, and Ruby APIs. These APIs work by executing application event-handling functions in response to network activity. The library monitors network I/O and fires events. The event handlers run sequentially on the main library thread. Because the event handlers run on the main library thread, the handler code must not contain any long-running blocking operations. Blocking in an event handler blocks all library execution. If you need to execute a long blocking operation, you must call it on a separate thread. The event-driven APIs include cross-thread communication facilities to support coordination between the library thread and application threads. Avoid blocking in event handlers Long-running blocking calls in event handlers stop all library execution, preventing the library from handling other events and performing periodic tasks. Always start long-running blocking procedures in a separate application thread.

Commands:
Preface Cost management helps you monitor and analyze your OpenShift Container Platform and Public cloud costs to improve the management of your business. It is based on the upstream project Koku. To get started, learn about the following topics: What you can do with cost management and why your organization might want to use it How to set up and configure cost management How to adjust your settings after setup How to use cost management You can use cost management to track cost and usage data for your Amazon Web Services (AWS), Microsoft Azure, Google Cloud, Oracle Cloud, and OpenShift Container Platform environments.

Commands:
F.3. Running Additional Programs at Boot Time The /etc/rc.d/rc.local script is executed by the init command at boot time or when changing runlevels. Adding commands to the bottom of this script is an easy way to perform necessary tasks like starting special services or initialize devices without writing complex initialization scripts in the /etc/rc.d/init.d/ directory and creating symbolic links. The /etc/rc.serial script is used if serial ports must be setup at boot time. This script runs setserial commands to configure the system's serial ports. Refer to the setserial man page for more information.

Commands:
Chapter 8. Fixed issues The issues fixed in Streams for Apache Kafka 2.7 on OpenShift. For details of the issues fixed in Kafka 3.7.0, refer to the Kafka 3.7.0 Release Notes. Table 8.1. Fixed issues Issue Number Description ENTMQST-5839 OAuth issue fix: fallbackUsernamePrefix had no effect ENTMQST-5820 MM2 connector task fails for Oauth enabled clusters due to unwanted quotes in the resulting sasl.jaas.config values. ENTMQST-5754 Avoid unnecessary patching when resources are being deleted ENTMQST-5753 Producing with different embedded formats across multiple HTTP requests isn't honoured ENTMQST-5656 Cruise Control not restarted when API secret changes ENTMQST-5603 UseKRaft feature gate promotion to beta ENTMQST-5583 Unidirectional Topic Operator seems to cause disruption when upgrading from BTO ENTMQST-5582 Cruise control topics should use proper configuration to make smooth rolling updates possible and ensure availability ENTMQST-5581 Unidirectional Topic Operator needs to use log levels in a better way ENTMQST-5546 KafkaRoller is strugling to transition controller-only nodes to mixed nodes ENTMQST-5540 Fix handling of connector state for MirrorMaker 2 connectors ENTMQST-5511 KRaft node rolling, liveness and readiness ENTMQST-5504 Add support for Kafka and Strimzi upgrades when KRaft is enabled ENTMQST-5492 Fix handling of advertised listeners for controller nodes ENTMQST-5387 Promote the StableConnectIdentities feature gate to GA ENTMQST-5383 Support for Tiered Storage with custom "bring-your-own" plugins ENTMQST-5360 Additional tasks for Unidirectional Topic Operator (2.7.0 Edition) ENTMQST-5292 Deal with issues around Cluster ID validation when recovering from existing PVs / PVCs ENTMQST-4194 Topic Operator allows user to set forbidden settings ENTMQST-4164 Persistent error on periodic reconciliation of internal topics ENTMQST-4087 Topic Operator fails when doing bulk topic deletion ENTMQST-3970 The internal Kafka Connect topics are recreated with invalid configuration ENTMQST-3994 ZooKeeper to KRaft migration ENTMQST-3974 Topic Operator fixes ENTMQST-3886 The state store, topic-store, may have migrated to another instance Table 8.2. Fixed common vulnerabilities and exposures (CVEs) Issue Number Description ENTMQST-5886 CVE-2023-43642 flaw was found in SnappyInputStream in snappy-java ENTMQST-5885 CVE-2023-52428 Nimbus JOSE+JWT before 9.37.2 ENTMQST-5884 CVE-2022-4899 vulnerability was found in zstd v1.4.10 ENTMQST-5883 CVE-2021-24032 flaw was found in zstd ENTMQST-5882 CVE-2024-23944 Apache ZooKeeper: Information disclosure in persistent watcher handling ENTMQST-5881 CVE-2021-3520 a flaw in lz4 ENTMQST-5835 CVE-2024-29025 netty-codec-http: Allocation of Resources Without Limits or Throttling ENTMQST-5646 CVE-2024-1023 vert.x: io.vertx/vertx-core: memory leak due to the use of Netty FastThreadLocal data structures in Vertx ENTMQST-5667 CVE-2024-1300 vertx-core: io.vertx:vertx-core: memory leak when a TCP server is configured with TLS and SNI support

Commands:
3.10. The SHOW Statement The SHOW statement can be used to see a variety of information. The SHOW statement is not yet a language feature of JBoss Data Virtualization and is handled only in the JDBC client. SHOW PLAN SHOW PLAN returns a resultset with a CLOB column PLAN_TEXT, an xml column PLAN_XML, and a CLOB column DEBUG_LOG with a row containing the values from the previously executed query. If SHOWPLAN is OFF or no plan is available, no rows are returned. If SHOWPLAN is not set to DEBUG, then DEBUG_LOG will return a null value. SHOW ANNOTATIONS SHOW ANNOTATIONS returns a resultset with string columns CATEGORY, PRIORITY, ANNOTATION, RESOLUTION and a row for each annotation on the previously executed query. If SHOWPLAN is OFF or no plan is available, no rows are returned. SHOW <property> SHOW <property> is the inverse of SET and shows the property value for the property supplied. It returns a resultset with a single string column with a name matching the property key. SHOW ALL SHOW ALL returns a resultset with a NAME string column and a VALUE string column with a row entry for every property value.

Commands:
Chapter 9. Important links Red Hat AMQ Broker 7.10 Release Notes Red Hat AMQ Broker 7.9 Release Notes Red Hat AMQ Broker 7.8 Release Notes Red Hat AMQ Broker 7.7 Release Notes Red Hat AMQ Broker 7.6 Release Notes Red Hat AMQ Broker 7.1 to 7.5 Release Notes (aggregated) Red Hat AMQ 7 Supported Configurations Red Hat AMQ 7 Component Details Revised on 2024-10-17 16:50:12 UTC

Commands:
6.3.3. Use a Boot Option to Specify a Driver Update Disk Important This method only works to introduce completely new drivers, not to update existing drivers. Type linux dd at the boot prompt at the start of the installation process and press Enter . The installer prompts you to confirm that you have a driver disk: Figure 6.6. The driver disk prompt Insert the driver update disk that you created on CD, DVD, or USB flash drive and select Yes . The installer examines the storage devices that it can detect. If there is only one possible location that could hold a driver disk (for example, the installer detects the presence of a DVD drive, but no other storage devices) it will automatically load any driver updates that it finds at this location. If the installer finds more than one location that could hold a driver update, it prompts you to specify the location of the update. See Section 6.4, "Specifying the Location of a Driver Update Image File or a Driver Update Disk" .

Commands:
Chapter 9. Enforcing Puppet configuration on hosts You can enforce configuration from Satellite either manually on demand (run once) or automatically in configurable intervals. 9.1. Running Puppet once using SSH Assign the proper job template to the Run Puppet Once feature to run Puppet on hosts. Procedure In the Satellite web UI, navigate to Administer > Remote Execution Features . Select the puppet_run_host remote execution feature. Assign the Run Puppet Once - SSH Default job template. Run Puppet on hosts by running a job and selecting category Puppet and template Run Puppet Once - SSH Default . Alternatively, click Run Puppet Once in the Schedule Remote Job drop down menu on the host details page. 9.2. Understanding intervals of automatic enforcement Satellite considers hosts to be out of sync if the last Puppet report is older than the combined values of outofsync_interval and puppet_interval set in minutes. By default, the Puppet agent on your hosts runs every 30 minutes, the puppet_interval is set to 35 minutes and the global outofsync_interval is set to 30 minutes. The effective time after which hosts are considered out of sync is the sum of outofsync_interval and puppet_interval . For example, setting the global outofsync_interval to 30 and the puppet_interval to 60 results in a total of 90 minutes after which the host status changes to out of sync . 9.3. Setting the Puppet agent run interval on a host Set the interval when the Puppet agent runs and sends reports to Satellite. Procedure Connect to your host using SSH. Add the Puppet agent run interval to /etc/puppetlabs/puppet/puppet.conf , for example runinterval = 1h . 9.4. Setting the global out-of-sync interval Procedure In the Satellite web UI, navigate to Administer > Settings . On the General tab, edit Out of sync interval . Set a duration, in minutes, after which hosts are considered to be out of sync. You can also override this interval on host groups or individual hosts by adding the outofsync_interval parameter. 9.5. Setting the Puppet out-of-sync interval Procedure In the Satellite web UI, navigate to Administer > Settings , and click the Config Management tab. In the Puppet interval field, set the value to the duration, in minutes, after which hosts reporting using Puppet are considered to be out of sync. 9.6. Overriding out-of-sync interval for a host group Procedure In the Satellite web UI, navigate to Configure > Host Groups . Select a host group. On the Parameters tab, click Add Parameter . In the Name field, enter outofsync_interval . From the Type dropdown menu, select integer . In the Value field, enter the new interval in minutes. Click Submit . 9.7. Overriding out-of-sync interval for an individual host Procedure In the Satellite web UI, navigate to Hosts > All Hosts . Click Edit for a selected host. On the Parameters tab, click Add Parameter . In the Name field, enter outofsync_interval . From the Type dropdown menu, select integer . In the Value field, enter the new interval in minutes. Click Submit .

Commands:
6.14.2. Multicast Configuration If you do not specify a multicast address in the cluster configuration file, the Red Hat High Availability Add-On software creates one based on the cluster ID. It generates the lower 16 bits of the address and appends them to the upper portion of the address according to whether the IP protocol is IPv4 or IPv6: For IPv4 - The address formed is 239.192. plus the lower 16 bits generated by Red Hat High Availability Add-On software. For IPv6 - The address formed is FF15:: plus the lower 16 bits generated by Red Hat High Availability Add-On software. Note The cluster ID is a unique identifier that cman generates for each cluster. To view the cluster ID, run the cman_tool status command on a cluster node. You can manually specify a multicast address in the cluster configuration file with the following command: Note that this command resets all other properties that you can set with the --setmulticast option to their default values, as described in Section 6.1.5, "Commands that Overwrite Settings" . If you specify a multicast address, you should use the 239.192.x.x series (or FF15:: for IPv6) that cman uses. Otherwise, using a multicast address outside that range may cause unpredictable results. For example, using 224.0.0.x (which is "All hosts on the network") may not be routed correctly, or even routed at all by some hardware. If you specify or modify a multicast address, you must restart the cluster for this to take effect. For information on starting and stopping a cluster with the ccs command, see Section 7.2, "Starting and Stopping a Cluster" . Note If you specify a multicast address, make sure that you check the configuration of routers that cluster packets pass through. Some routers may take a long time to learn addresses, seriously impacting cluster performance. To remove a multicast address from a configuration file, use the --setmulticast option of the ccs but do not specify a multicast address:

Commands:
ccs -h host --setmulticast multicastaddress
ccs -h host --setmulticast
Chapter 4. Developer Preview features Important This section describes Developer Preview features in Red Hat OpenShift AI 2.18. Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features provide early access to functionality in advance of possible inclusion in a Red Hat product offering. Customers can use these features to test functionality and provide feedback during the development process. Developer Preview features might not have any documentation, are subject to change or removal at any time, and have received limited testing. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA. For more information about the support scope of Red Hat Developer Preview features, see Developer Preview Support Scope . Support for AppWrapper in Kueue AppWrapper support in Kueue is available as a Developer Preview feature. The experimental API enables the use of AppWrapper-based workloads with the distributed workloads feature.

Commands:
Chapter 96. Kamelet Main Since Camel 3.11 A main class that is opinionated to boostrap and run Camel standalone with Kamelets (or plain YAML routes) for development and demo purposes. 96.1. Initial configuration The KameletMain is pre-configured with the following properties: camel.component.kamelet.location = classpath:/kamelets,github:apache:camel-kamelets/kamelets camel.component.rest.consumerComponentName = platform-http camel.component.rest.producerComponentName = vertx-http You can override these settings by updating the configuration in application.properties . 96.2. Automatic dependencies downloading The Kamelet Main can automatically download Kamelet YAML files from a remote location over http/https, and from github as well. The official Kamelets from the Apache Camel Kamelet Catalog is stored on github and they can be used out of the box as-is. For example a Camel route can be coded in YAML which uses the Earthquake Kamelet from the catalog, as shown below: - route: from: "kamelet:earthquake-source" steps: - unmarshal: json: {} - log: "Earthquake with magnitude USD{body[properties][mag]} at USD{body[properties][place]}" In the above example, the earthquake kamelet will be downloaded from github, and as well its required dependencies. For more information, see Kamelet Main example

Commands:
camel.component.kamelet.location = classpath:/kamelets,github:apache:camel-kamelets/kamelets camel.component.rest.consumerComponentName = platform-http camel.component.rest.producerComponentName = vertx-http
- route: from: "kamelet:earthquake-source" steps: - unmarshal: json: {} - log: "Earthquake with magnitude USD{body[properties][mag]} at USD{body[properties][place]}"
14.6. Compatibility with Older Systems If an ACL has been set on any file on a given file system, that file system has the ext_attr attribute. This attribute can be seen using the following command: A file system that has acquired the ext_attr attribute can be mounted with older kernels, but those kernels do not enforce any ACLs which have been set. Versions of the e2fsck utility included in version 1.22 and higher of the e2fsprogs package (including the versions in Red Hat Enterprise Linux 2.1 and 4) can check a file system with the ext_attr attribute. Older versions refuse to check it.

Commands:
tune2fs -l <filesystem-device>
Chapter 140. KafkaBridgeTemplate schema reference Used in: KafkaBridgeSpec Property Property type Description deployment DeploymentTemplate Template for Kafka Bridge Deployment . pod PodTemplate Template for Kafka Bridge Pods . apiService InternalServiceTemplate Template for Kafka Bridge API Service . podDisruptionBudget PodDisruptionBudgetTemplate Template for Kafka Bridge PodDisruptionBudget . bridgeContainer ContainerTemplate Template for the Kafka Bridge container. clusterRoleBinding ResourceTemplate Template for the Kafka Bridge ClusterRoleBinding. serviceAccount ResourceTemplate Template for the Kafka Bridge service account. initContainer ContainerTemplate Template for the Kafka Bridge init container.

Commands:
Chapter 4. Reviewing and managing policies You can review and manage all created policies (enabled and disabled) by navigating to Operations > Policies . You can filter the list of policies by name and by active state. You can click the options menu to a policy to perform the following operations: Enable and disable Edit Duplicate Delete Additionally, you can perform the following operations in bulk by selecting multiple policies from the list of policies and clicking the options menu located to the Create policy button at the top: Delete policies Enable policies Disable policies Note If you see a warning message about email alerts not opted in, set your User preferences to receive email from your policies.

Commands:
Chapter 13. Enabling the Red Hat OpenShift Data Foundation console plugin The Data Foundation console plugin is enabled by default. In case, this option was unchecked during OpenShift Data Foundation Operator installation, use the following instructions to enable the console plugin post-deployment either from the graphical user interface (GUI) or command-line interface. Prerequisites You have administrative access to the OpenShift Web Console. OpenShift Data Foundation Operator is installed and running in the openshift-storage namespace. Procedure From user interface In the OpenShift Web Console, click Operators Installed Operators to view all the installed operators. Ensure that the Project selected is openshift-storage . Click on the OpenShift Data Foundation operator. Enable the console plugin option. In the Details tab, click the pencil icon under the Console plugin . Select Enable , and click Save . From command-line interface Execute the following command to enable the console plugin option: Verification steps After the console plugin option is enabled, a pop-up with a message, Web console update is available appears on the GUI. Click Refresh web console from this pop-up for the console changes to reflect. In the Web Console, navigate to Storage and verify if Data Foundation is available.

Commands:
oc patch console.operator cluster -n openshift-storage --type json -p '[{"op": "add", "path": "/spec/plugins", "value": ["odf-console"]}]'
Chapter 6. Best practices for running containers using local sources You can access content hosted in an internal registry that requires a custom Transport Layer Security (TLS) root certificate, when running RHEL bootc images. There are two options available to install content to a container by using only local resources: Bind mounts: Use for example -v /etc/pki:/etc/pki to override the container's store with the host's. Derived image: Create a new container image with your custom certificates by building it using a Containerfile . You can use the same techniques to run a bootc-image-builder` container or a bootc container when appropriate. 6.1. Importing custom certificate to a container by using bind mounts Use bound mounts to override the container's store with the host's. Procedure Run RHEL bootc image and use bind mount, for example -v /etc/pki:/etc/pki , to override the container's store with the host's: Verification List certificates inside the container: 6.2. Importing custom certificates to a container by using Containerfile Create a new container image with your custom certificates by building it using a Containerfile . Procedure Create a Containerfile : Build the custom image: Run the <your_image> : Verification List the certificates inside the container:

Commands:
podman run --rm -it --privileged --pull=newer --security-opt label=type:unconfined_t -v USD(pwd)/output:/output -v /etc/pki:/etc/pki localhost/ <image> --type iso --config /config.toml quay.io/ <namespace>/<image>:<tag>
ls -l /etc/pki
FROM <internal_repository>/<image> RUN mkdir -p /etc/pki/ca-trust/extracted/pem/ COPY tls-ca-bundle.pem /etc/pki/ca-trust/extracted/pem/ RUN rm -rf /etc/yum.repos.d/* COPY echo-rhel9_4.repo /etc/yum.repos.d/
podman build -t <your_image> .
podman run -it --rm <your_image>
ls -l /etc/pki/ca-trust/extracted/pem/ tls-ca-bundle.pem
Preface The Red Hat Enterprise Linux 6.2 Technical Notes list and document the changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications between minor release Red Hat Enterprise Linux 6.1 and minor release Red Hat Enterprise Linux 6.2. For system administrators and others planning Red Hat Enterprise Linux 6.2 upgrades and deployments, the Technical Notes provide a single, organized record of the bugs fixed in, features added to, and Technology Previews included with this new release of Red Hat Enterprise Linux. For auditors and compliance officers, the Red Hat Enterprise Linux 6.2 Technical Notes provide a single, organized source for change tracking and compliance testing. For every user, the Red Hat Enterprise Linux 6.2 Technical Notes provide details of what has changed in this new release. Note The Package Manifest is available as a separate document.

Commands:
23.9. Synchronize to PTP or NTP Time Using timemaster When there are multiple PTP domains available on the network, or fallback to NTP is needed, the timemaster program can be used to synchronize the system clock to all available time sources. The PTP time is provided by phc2sys and ptp4l via shared memory driver ( SHM reference clocks to chronyd or ntpd (depending on the NTP daemon that has been configured on the system). The NTP daemon can then compare all time sources, both PTP and NTP , and use the best sources to synchronize the system clock. On start, timemaster reads a configuration file that specifies the NTP and PTP time sources, checks which network interfaces have their own or share a PTP hardware clock (PHC), generates configuration files for ptp4l and chronyd or ntpd , and starts the ptp4l , phc2sys , and chronyd or ntpd processes as needed. It will remove the generated configuration files on exit. It writes configuration files for chronyd , ntpd , and ptp4l to /var/run/timemaster/ . 23.9.1. Starting timemaster as a Service To start timemaster as a service, issue the following command as root : This will read the options in /etc/timemaster.conf . For more information on managing system services in Red Hat Enterprise Linux 6, see Managing Services with systemd.

Commands:
~]# service timemaster start