mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 5. Limited Availability features Important This section describes Limited Availability features in Red Hat OpenShift AI. Limited Availability means that you can install and receive support for the feature only with specific approval from Red Hat. Without such approval, the feature is unsupported. This applies to all features described in this section. Tuning in OpenShift AI Tuning in OpenShift AI is available as a Limited Availability feature. The Kubeflow Training Operator and the Hugging Face Supervised Fine-tuning Trainer (SFT Trainer) enable users to fine-tune and train their models easily in a distributed environment. In this release, you can use this feature for models that are based on the PyTorch machine-learning framework.

Commands:
Chapter 1. Using language support for Apache Camel extension Important The VS Code extensions for Apache Camel are listed as development support. For more information about scope of development support, see Development Support Scope of Coverage The Visual Studio Code language support extension adds the language support for Apache Camel for XML DSL and Java DSL code. 1.1. About language support for Apache Camel extension This extension provides completion, validation and documentation features for Apache Camel URI elements directly in your Visual Studio Code editor. It works as a client using the Microsoft Language Server Protocol which communicates with Camel Language Server to provide all functionalities. 1.2. Features of language support for Apache Camel extension The important features of the language support extension are listed below: Language service support for Apache Camel URIs. Quick reference documentation when you hover the cursor over a Camel component. Diagnostics for Camel URIs. Navigation for Java and XML langauges. Creating a Camel Route specified with Yaml DSL using Camel JBang. 1.3. Requirements Following points must be considered when using the Apache Camel Language Server: Java 11 is currently required to launch the Apache Camel Language Server. The java.home VS Code option is used to use a different version of JDK than the default one installed on the machine. For some features, JBang must be available on a system command line. For an XML DSL files: Use an .xml file extension. Specify the Camel namespace, for reference, see http://camel.apache.org/schema/blueprint or http://camel.apache.org/schema/spring . For a Java DSL files: Use a .java file extension. Specify the Camel package(usually from an imported package), for example, import org.apache.camel.builder.RouteBuilder . To reference the Camel component, use from or to and a string without a space. The string cannot be a variable. For example, from("timer:timerName") works, but from( "timer:timerName") and from(aVariable) do not work. 1.4. Installing Language support for Apache Camel extension You can download the Language support for Apache Camel extension from the VS Code Extension Marketplace and the Open VSX Registry. You can also install the Language Support for Apache Camel extension directly in the Microsoft VS Code. Procedure Open the VS Code editor. In the VS Code editor, select View > Extensions . In the search bar, type Camel . Select the Language Support for Apache Camel option from the search results and then click Install. This installs the language support extension in your editor. Additional resources Language Support for Apache Camel by Red Hat

Commands:
Chapter 6. Fixed issues The issues fixed in Streams for Apache Kafka 2.7 on RHEL. For details of the issues fixed in Kafka 3.7.0, refer to the Kafka 3.7.0 Release Notes. Table 6.1. Fixed issues Issue Number Description ENTMQST-5839 OAuth issue fix: oauth.fallback.username.prefix had no effect ENTMQST-5753 Producing with different embedded formats across multiple HTTP requests isn't honoured ENTMQST-5504 Add support for Kafka and Strimzi upgrades when KRaft is enabled ENTMQST-3994 ZooKeeper to KRaft migration Table 6.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:
Chapter 6. Mirroring data for hybrid and Multicloud buckets The Multicloud Object Gateway (MCG) simplifies the process of spanning data across cloud provider and clusters. Prerequisites You must first add a backing storage that can be used by the MCG, see Chapter 4, Adding storage resources for hybrid or Multicloud . Then you create a bucket class that reflects the data management policy, mirroring. Procedure You can set up mirroring data in three ways: Section 6.1, "Creating bucket classes to mirror data using the MCG command-line-interface" Section 6.2, "Creating bucket classes to mirror data using a YAML" Section 6.3, "Configuring buckets to mirror data using the user interface" 6.1. Creating bucket classes to mirror data using the MCG command-line-interface From the Multicloud Object Gateway (MCG) command-line interface, run the following command to create a bucket class with a mirroring policy: Set the newly created bucket class to a new bucket claim, generating a new bucket that will be mirrored between two locations: 6.2. Creating bucket classes to mirror data using a YAML Apply the following YAML. This YAML is a hybrid example that mirrors data between local Ceph storage and AWS: Add the following lines to your standard Object Bucket Claim (OBC): For more information about OBCs, see Chapter 9, Object Bucket Claim . 6.3. Configuring buckets to mirror data using the user interface In the OpenShift Web Console, click Storage OpenShift Data Foundation . In the Status card, click Storage System and click the storage system link from the pop up that appears. In the Object tab, click the Multicloud Object Gateway link. On the NooBaa page, click the buckets icon on the left side. You can see a list of your buckets: Click the bucket you want to update. Click Edit Tier 1 Resources : Select Mirror and check the relevant resources you want to use for this bucket. In the following example, the data between noobaa-default-backing-store which is on RGW and AWS-backingstore which is on AWS is mirrored: Click Save . Note Resources created in NooBaa UI cannot be used by OpenShift UI or Multicloud Object Gateway (MCG) CLI.

Commands:
noobaa bucketclass create placement-bucketclass mirror-to-aws --backingstores=azure-resource,aws-resource --placement Mirror
noobaa obc create mirrored-bucket --bucketclass=mirror-to-aws
apiVersion: noobaa.io/v1alpha1 kind: BucketClass metadata: labels: app: noobaa name: <bucket-class-name> namespace: openshift-storage spec: placementPolicy: tiers: - backingStores: - <backing-store-1> - <backing-store-2> placement: Mirror
additionalConfig: bucketclass: mirror-to-aws
function::sprint_backtrace Name function::sprint_backtrace - Return stack back trace as string Synopsis Arguments None Description Returns a simple (kernel) backtrace. One line per address. Includes the symbol name (or hex address if symbol couldn't be resolved) and module name (if found). Includes the offset from the start of the function if found, otherwise the offset will be added to the module (if found, between brackets). Returns the backtrace as string (each line terminated by a newline character). Note that the returned stack will be truncated to MAXSTRINGLEN, to print fuller and richer stacks use print_backtrace . Equivalent to sprint_stack( backtrace ), but more efficient (no need to translate between hex strings and final backtrace string).

Commands:
sprint_backtrace:string()
4.3.6. Tracking System Call Volume Per Process This section illustrates how to determine which processes are performing the highest volume of system calls. In sections, we have described how to monitor the top system calls used by the system over time ( Section 4.3.5, "Tracking Most Frequently Used System Calls" ). We've also described how to identify which applications use a specific set of "polling suspect" system calls the most ( Section 4.3.4, "Monitoring Polling Applications" ). Monitoring the volume of system calls made by each process provides more data in investigating your system for polling processes and other resource hogs. syscalls_by_proc.stp syscalls_by_proc.stp lists the top 20 processes performing the highest number of system calls. It also lists how many system calls each process performed during the time period. Refer to Example 4.16, "topsys.stp Sample Output" for a sample output. Example 4.16. topsys.stp Sample Output If you prefer the output to display the process IDs instead of the process names, use the following script instead. syscalls_by_pid.stp As indicated in the output, you need to manually exit the script in order to display the results. You can add a timed expiration to either script by simply adding a timer.s() probe; for example, to instruct the script to expire after 5 seconds, add the following probe to the script:

Commands:
#! /usr/bin/env stap Copyright (C) 2006 IBM Corp. # This file is part of systemtap, and is free software. You can redistribute it and/or modify it under the terms of the GNU General Public License (GPL); either version 2, or (at your option) any later version. # Print the system call count by process name in descending order. # global syscalls probe begin { print ("Collecting data... Type Ctrl-C to exit and display results\n") } probe syscall.* { syscalls[execname()]++ } probe end { printf ("%-10s %-s\n", "#SysCalls", "Process Name") foreach (proc in syscalls-) printf("%-10d %-s\n", syscalls[proc], proc) }
Collecting data... Type Ctrl-C to exit and display results #SysCalls Process Name 1577 multiload-apple 692 synergyc 408 pcscd 376 mixer_applet2 299 gnome-terminal 293 Xorg 206 scim-panel-gtk 95 gnome-power-man 90 artsd 85 dhcdbd 84 scim-bridge 78 gnome-screensav 66 scim-launcher [...]
#! /usr/bin/env stap Copyright (C) 2006 IBM Corp. # This file is part of systemtap, and is free software. You can redistribute it and/or modify it under the terms of the GNU General Public License (GPL); either version 2, or (at your option) any later version. # Print the system call count by process ID in descending order. # global syscalls probe begin { print ("Collecting data... Type Ctrl-C to exit and display results\n") } probe syscall.* { syscalls[pid()]++ } probe end { printf ("%-10s %-s\n", "#SysCalls", "PID") foreach (pid in syscalls-) printf("%-10d %-d\n", syscalls[pid], pid) }
probe timer.s(5) { exit() }
Chapter 11. Related information You can refer to the following instructional materials: Upgrade your Red Hat Enterprise Linux Infrastructure Red Hat Enterprise Linux technology capabilities and limits Supported in-place upgrade paths for Red Hat Enterprise Linux In-place upgrade Support Policy Considerations in adopting RHEL 8 Customizing your Red Hat Enterprise Linux in-place upgrade Automating your Red Hat Enterprise Linux pre-upgrade report workflow Using configuration management systems to automate parts of the Leapp pre-upgrade and upgrade process on Red Hat Enterprise Linux Upgrading from RHEL 6 to RHEL 7 Upgrading from RHEL 6 to RHEL 8 Converting from a Linux distribution to RHEL using the Convert2RHEL utility Upgrading Hosts from RHEL 7 to RHEL 8 in Red Hat Satellite How to in-place upgrade SAP environments from RHEL 7 to RHEL 8 (Red Hat Knowledgebase) Red Hat Insights Documentation Upgrades-related Knowledgebase articles and solutions (Red Hat Knowledgebase) The best practices and recommendations for performing RHEL Upgrade using Leapp Leapp upgrade FAQ (Frequently Asked Questions) Red Hat Enterprise Linux Upgrade Helper

Commands:
Chapter 8. Red Hat Enterprise Linux Atomic Host 7.7.3 8.1. Atomic Host OStree update : New Tree Version: 7.7.3 (hash: e0ac32316936b7e138a2f9bea407bf20124f34f519e8f7147df3edc69ca86296) Changes since Tree Version 7.7.2 (hash: 1542d075bce595cb38d3f1429388f3c5225732811d2995cb4a35c1be2cde00aa) 8.2. Extras Updated packages : docker-1.13.1-108.git4ef4b30.el7 8.2.1. Container Images Updated : Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux 7.7 Container Image (rhel7.7, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic OpenSCAP Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) Red Hat Universal Base Image 7 Container Image (rhel7/ubi7) Red Hat Universal Base Image 7 Init Container Image (rhel7/ubi7-init) Red Hat Universal Base Image 7 Minimal Container Image (rhel7/ubi7-minimal) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) 8.3. Announcements Red Hat Enterprise Linux Atomic Host Retires on August 6, 2020 Red Hat Enterprise Linux Atomic Host will be retired on August 6, 2020 and active support will no longer be provided. Accordingly, Red Hat will no longer provide image or ostree updates, Critical or Important security patches, or Urgent Priority bug fixes for Red Hat Enterprise Linux Atomic Host after August 6, 2020. We encourage customers to migrate to the most recent version of Red Hat Enterprise Linux that is supported for their environment. As a benefit of the Red Hat subscription model, customers can use their active subscriptions to entitle any system on any currently supported Red Hat Enterprise Linux release. Customers who wish to deploy containers as part of their production are encouraged to evaluate Red Hat OpenShift Container Platform migrate to a supported version of Red Hat Enterprise Linux.

Commands:
Chapter 2. Planning an upgrade An in-place upgrade is the recommended and supported way to upgrade your SAP HANA system to the major version of RHEL. You should consider the following before upgrading to RHEL 8: Operating system: SAP HANA is installed with a version that is supported on both the source and target RHEL minor versions. SAP HANA is installed using the default installation path of /hana/shared . Public clouds: The in-place upgrade is supported for on-demand Pay-As-You-Go (PAYG) instances on Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform with Red Hat Update Infrastructure (RHUI) . The in-place upgrade is also supported for Bring Your Own Subscription instances on all public clouds that use Red Hat Subscription Manager (RHSM) for a RHEL subscription. Additional Information: SAP HANA hosts must meet all of the following criteria: Running on x86_64 architecture that is certified by the hardware partner or CCSP for SAP HANA on the source and target OS versions. Running on physical infrastructure or in a virtual environment. Using the Red Hat Enterprise Linux for SAP Solutions subscription. Not using Red Hat HA Solutions for SAP HANA. SAP NetWeaver hosts must meet the following criteria: Using the Red Hat Enterprise Linux for SAP Solutions or Red Hat Enterprise Linux for SAP Applications subscription High Availability: If you are using the High Availability add-on, follow the Recommended Practices for Applying Software Updates to a RHEL High Availability or Resilient Storage Cluster KBA. Please also refer to Chapter 2 and particularly the known limitations mentioned there in the Upgrading from RHEL 7 to RHEL 8 document, as these also apply to the upgrade procedure for SAP HANA and SAP NetWeaver hosts.

Commands:
16.2. Finding Model Objects The Teiid Designer provides a name based search capability to quickly locate and display model objects. To find a model object: Open the Find Model Object dialog by selecting the action through the main menu's Search > Teiid Designer > Find Model Object action. Begin typing a word or partial word in the Type Object Name field. Wild card (*) characters will be honored. As you type, the objects which match the desired name will be displayed in the Matching Model Objects list. If there are more than one objects with the same name, the locations or paths of the objects are displayed in the Locations list. If more than one object exists with the desired name, select the one of the locations. Click OK . If editor is not open for the object's model, an editor will open. The desired object results in a diagram (if applicable) and selected.

Commands:
Virtualization Getting Started Guide Red Hat Enterprise Linux 6 An introduction to virtualization concepts Jiri Herrmann Red Hat Customer Content Services jherrman@redhat.com Yehuda Zimmerman Red Hat Customer Content Services yzimmerm@redhat.com Dayle Parker Red Hat Customer Content Services Laura Novich Red Hat Customer Content Services Jacquelynn East Red Hat Customer Content Services Scott Radvan Red Hat Customer Content Services

Commands:
3.13. Cluster Networking Cluster level networking objects include: Clusters Logical Networks A data center is a logical grouping of multiple clusters and each cluster is a logical group of multiple hosts. The following diagram depicts the contents of a single cluster. Figure 3.1. Networking within a cluster Hosts in a cluster all have access to the same storage domains. Hosts in a cluster also have logical networks applied to the cluster. For a virtual machine logical network to become operational for use with virtual machines, the network must be defined and implemented for each host in the cluster using the Red Hat Virtualization Manager. Other logical network types can be implemented on only the hosts that use them. Multi-host network configuration automatically applies any updated network settings to all of the hosts within the data center to which the network is assigned.

Commands:
2.2. Tracking Configuration History Data from the Red Hat Virtualization History Database (called ovirt_engine_history ) can be used to track the engine database. The ETL service, ovirt-engine-dwhd , tracks three types of changes: A new entity is added to the engine database - the ETL Service replicates the change to the ovirt_engine_history database as a new entry. An existing entity is updated - the ETL Service replicates the change to the ovirt_engine_history database as a new entry. An entity is removed from the engine database - A new entry in the ovirt_engine_history database flags the corresponding entity as removed. Removed entities are only flagged as removed. The configuration tables in the ovirt_engine_history database differ from the corresponding tables in the engine database in several ways. The most apparent difference is they contain fewer configuration columns. This is because certain configuration items are less interesting to report than others and are not kept due to database size considerations. Also, columns from a few tables in the engine database appear in a single table in ovirt_engine_history and have different column names to make viewing data more convenient and comprehensible. All configuration tables contain: a history_id to indicate the configuration version of the entity; a create_date field to indicate when the entity was added to the system; an update_date field to indicate when the entity was changed; and a delete_date field to indicate the date the entity was removed from the system.

Commands:
8.37. createrepo 8.37.1. RHBA-2014:0491 - createrepo bug fix and enhancement update An updated createrepo package that fixes three bugs and adds two enhancements is now available for Red Hat Enterprise Linux 6. The createrepo package contains a set of utilities used to generate and maintain a common metadata repository from a directory of rpm packages. Bug Fixes BZ# 1035588 Previously, the createrepo utility did not test file locking correctly. As a consequence, createrepo terminated unexpectedly with a traceback when it was executed in a directory located on a Common Internet File System (CIFS) share provided by a NetApp storage appliance. The test for file locking has been corrected and createrepo now works as expected in the described situation. BZ# 1083185 Prior to this update, if the createrepo utility was executed with the "-i" or "--pkglist" options and the specified file name did not exist, createrepo terminated unexpectedly with a traceback. The createrepo utility has been modified to handle this error condition properly, and it now exits gracefully in this situation. BZ# 1088886 Prior to this update, the createrepo packages had descriptions which did not indicate that the maintenance utilities were present in the package. This update corrects this omission. In addition, this update adds the following Enhancements BZ# 952602 This update introduces support for the following new options to the modifyrepo utility: "--checksum", used to specify the checksum type; "--unique-md-filenames", used to include the file's checksum in the file name; and "--simple-md-filenames", used to not include the file's checksum in the file name. The "--unique-md-filenames" option is a default option for this utility. BZ# 1093713 Previously, certain options were not described in the modifyrepo(1) and mergerepo(1) man pages. These man pages now document the following modifyrepo utility command line options: "--mdtype", "--remove", "--compress", "--no-compress", "--compress-type", "--checksum", "--unique-md-filenames", "--simple-md-filenames", "--version", and "--help". These man pages also now document the following mergerepo utility command line options: "--no-database", "--compress-type", "--version", and "--help". Users of createrepo are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
function::user_string2_n_warn Name function::user_string2_n_warn - Retrieves string from user space with alternative warning string Synopsis Arguments addr the user space address to retrieve the string from n the maximum length of the string (if not null terminated) warn_msg the warning message to return when data isn't available Description Returns up to n characters of a C string from a given user space memory address. Reports the given warning message on the rare cases when userspace data is not accessible and warns (but does not abort) about the failure.

Commands:
user_string2_n_warn:string(addr:long,n:long,warn_msg:string)