mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Features Streams for Apache Kafka 2.9 introduces the features described in this section. Streams for Apache Kafka 2.9 on RHEL is based on Apache Kafka 3.9.0. Note To view all the enhancements and bugs that are resolved in this release, see the Streams for Apache Kafka Jira project . 4.1. Kafka 3.9.0 support Streams for Apache Kafka now supports and uses Apache Kafka version 3.9.0. Only Kafka distributions built by Red Hat are supported. For upgrade, see the instructions for Streams for Apache Kafka and Kafka upgrades in the following guides: Using Streams for Apache Kafka on RHEL in KRaft mode Using Streams for Apache Kafka on RHEL with ZooKeeper Refer to the Kafka 3.9.0 Release Notes for additional information. Kafka 3.8.x is supported only for the purpose of upgrading to Streams for Apache Kafka 2.9. We recommend that you perform a rolling update to use the new binaries. 4.2. Streams for Apache Kafka 4.2.1. KRaft support moves to GA KRaft (Kafka Raft metadata) mode moves to GA (General Availability). KRaft mode replaces Kafka's dependency on ZooKeeper for cluster management, simplifying deployment and management of Kafka clusters by bringing metadata management and coordination of clusters into Kafka. Last release to support ZooKeeper Kafka 3.9.0 provides access to KRaft mode, where Kafka runs without ZooKeeper by utilizing the Raft protocol. Kafka 3.9 is the final version to support ZooKeeper. Consequently, Streams for Apache Kafka 2.9 is the last version compatible with Kafka clusters using ZooKeeper. If you are using ZooKeeper for metadata management in your Kafka cluster, you can migrate to using Kafka in KRaft mode using a static controller quorum. Once KRaft mode is enabled, you cannot switch back to ZooKeeper. To prepare for Streams for Apache Kafka 3.0, migrate to Kafka in KRaft mode . KRaft mode limitations For Kafka 3.8 and earlier, the controller quorums (which replace Zookeeper) were of fixed size (static). Dynamic controller quorums were introduced in Kafka 3.9. Migration between Kafka's static and dynamic controller quorums is not currently supported, though this feature is expected in a future Kafka release. Streams for Apache Kafka 2.9 on RHEL supports static and dynamic controller quorums, with dynamic quorums recommended for new deployments. 4.2.2. Capability to move data between JBOD disks using Cruise Control If you are using JBOD storage and have Cruise Control installed with Streams for Apache Kafka, you can now reassign partitions between the JBOD disks used for storage on the same broker. This capability also allows you to remove JBOD disks without data loss. Make requests to the remove_disks endpoint of the Cruise Control REST API to demote a disk in the cluster and reassign its partitions to other disk volumes. For more information, see Using Cruise Control to reassign partitions on JBOD disks .

Commands:
5.9.4. Network-Accessible Storage Under Red Hat Enterprise Linux There are two major technologies used for implementing network-accessible storage under Red Hat Enterprise Linux: NFS SMB The following sections describe these technologies. 5.9.4.1. NFS As the name implies, the Network File System (more commonly known as NFS) is a file system that may be accessed via a network connection. With other file systems, the storage device must be directly attached to the local system. However, with NFS this is not a requirement, making possible a variety of different configurations, from centralized file system servers to entirely diskless computer systems. However, unlike the other file systems, NFS does not dictate a specific on-disk format. Instead, it relies on the server operating system's native file system support to control the actual I/O to local disk drive(s). NFS then makes the file system available to any operating system running a compatible NFS client. While primarily a Linux and UNIX technology, it is worth noting that NFS client implementations exist for other operating systems, making NFS a viable technique to share files with a variety of different platforms. The file systems an NFS server makes available to clients is controlled by the configuration file /etc/exports . For more information, see the exports(5) man page and the System Administrators Guide .

Commands:
Chapter 42. Red Hat Enterprise Linux Atomic Host 7.2.2 42.1. Atomic Host OStree update : New Tree Version: 7.2.2 (hash: a9036292783ddfd389459d9bab69df5a655a0d6bb4dc6239a0aeff0f5d356f2e) 42.2. Extras Updated packages : atomic-1.8-6.git1bc3814.el7 cockpit-0.93-1.el7 docker-1.8.2-10.el7 docker-distribution-2.2.1-1.el7 * etcd-2.2.2-5.el7 flannel-0.5.3-9.el7 kubernetes-1.2.0-0.6.alpha1.git8632732.el7 python-docker-py-1.6.0-1.el7 The asterisk (*) marks packages which are available for Red Hat Enterprise Linux only. 42.2.1. Container Images Updated : Red Hat Enterprise Linux Container Image (rhel7/rhel) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) 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 Kubernetes-controller Container Image (rhel7/kubernetes-controller-mgr) Red Hat Enterprise Linux Atomic Kubernetes-apiserver Container Image (rhel7/kubernetes-apiserver) Red Hat Enterprise Linux Atomic Kubernetes-scheduler Container Image (rhel7/kubernetes-scheduler) 42.3. New Features The v1beta3 API is no longer supported in kubernetes Using v1beta3 in configuration files is no longer supported. Creating a v1beta3-style object with the kubectl command will fail with the following error: Using the --validate=false option will create an object, but the object will appear as a v1 object instead. A separate cockpit-docker subpackage is now shipped Previously, the Cockpit docker support was shipped with the cockpit-shell subpackage. Now, the cockpit-docker subpackage is available to be installed separately on Red Hat Enterprise Linux and is included in the OSTree available for RHEL Atomic Host. Cockpit has been rebased to version 0.93 Most notable changes: Distribute licenses of included components in the source RPM. Reworked TLS certificates for Cockpit. Cockpit now offers to activate multipathd for multipath disks. Added user interface for OSTree upgrades and rollbacks. Added OAuth login support. Add SOS report to the User Interface. Added support for the Tuned power management tool.

Commands:
error validating data: the server could not find the requested resource; if you choose to ignore these errors, turn validation off with --validate=false
2.3. Software Requirements Most of the packages that an IdM server depends on are installed as dependencies when the IdM packages are installed. There are some packages, however, which are required before installing the IdM packages: Kerberos 1.10. This is installed as a dependency if it is not already installed. The bind and bind-dyndb-ldap packages for DNS. The bind package is installed as a dependency if it is not already available; however, the bind-dyndb-ldap package must be explicitly installed first or attempting to configure an IdM server with DNS support will fail. Important Due to CVE-2014-3566 , the Secure Socket Layer version 3 (SSLv3) protocol needs to be disabled in the mod_nss module. You can ensure that by following these steps: Edit the /etc/httpd/conf.d/nss.conf file and set the NSSProtocol parameter to TLSv1.0 (for backward compatibility) and TLSv1.1 . Restart the httpd service.

Commands:
NSSProtocol TLSv1.0,TLSv1.1
service httpd restart
D.2. Installed Documentation man virsh and /usr/share/doc/libvirt- version-number - Contains sub-commands and options for the virsh virtual machine management utility as well as comprehensive information about the libvirt virtualization library API. /usr/share/doc/gnome-applet-vm- version-number - Documentation for the GNOME graphical panel applet that monitors and manages locally-running virtual machines. /usr/share/doc/libvirt-python- version-number - Provides details on the Python bindings for the libvirt library. The libvirt-python package allows python developers to create programs that interface with the libvirt virtualization management library. /usr/share/doc/virt-install- version-number - Provides documentation on the virt-install command that helps in starting installations of Fedora and Red Hat Enterprise Linux related distributions inside of virtual machines. /usr/share/doc/virt-manager- version-number - Provides documentation on the Virtual Machine Manager, which provides a graphical tool for administering virtual machines. Note For more information about other Red Hat Enterprise Linux components, see the appropriate man page or file in usr/share/doc/ .

Commands:
3.7. Example: Create NFS Data Storage An NFS data storage domain is an exported NFS share attached to a data center and provides storage for virtualized guest images. Creation of a new storage domain requires a POST request, with the storage domain representation included, sent to the URL of the storage domain collection. You can enable the wipe after delete option by default on the storage domain. To configure this specify <wipe_after_delete> in the POST request. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist. Example 3.7. Create an NFS data storage domain Request: cURL command: The API creates a NFS data storage domain called data1 with an export path of 192.168.0.10:/data1 and sets access to the storage domain through the hypervisor host. The API also returns the following representation of the newly created storage domain resource. Result:

Commands:
POST /ovirt-engine/api/storagedomains HTTP/1.1 Accept: application/xml Content-type: application/xml <storage_domain> <name>data1</name> <type>data</type> <storage> <type>nfs</type> <address>192.168.0.10</address> <path>/data1</path> </storage> <host> <name>hypervisor</name> </host> </storage_domain>
curl -X POST -H "Accept: application/xml" -H "Content-Type: application/xml" -u [USER:PASS] --cacert [CERT] -d "<storage_domain><name>data1</name><type>data</type> <storage><type>nfs</type><address>192.168.0.10</address> <path>/data1</path></storage> <host><name>hypervisor</name></host></storage_domain>" https:// [RHEVM Host] :443/ovirt-engine/api/storagedomains
HTTP/1.1 200 OK Accept: application/xml <storage_domain id="9ca7cb40-9a2a-4513-acef-dc254af57aac" href="/ovirt-engine/api/storagedomains/9ca7cb40-9a2a-4513-acef-dc254af57aac"> <name>data1</name> <link rel="permissions" href="/ovirt-engine/api/storagedomains/9ca7cb40-9a2a-4513-acef-dc254af57aac/ permissions"/> <link rel="files" href="/ovirt-engine/api/storagedomains/9ca7cb40-9a2a-4513-acef-dc254af57aac/files"/> <type>data</type> <master>false</master> <storage> <type>nfs</type> <address>192.168.0.10</address> <path>/data1</path> </storage> <available>175019917312</available> <used>27917287424</used> <committed>10737418240</committed> <storage_format>v1</storage_format> <host id="0656f432-923a-11e0-ad20-5254004ac988" href="/ovirt-engine/api/hosts/0656f432-923a-11e0-ad20-5254004ac988"> </storage_domain>
Appendix A. Enumerated Value Translation The API uses Red Hat Virtualization Query Language to perform search queries. For more information, see Searches in the Introduction to the Administration Portal . Note that certain enumerated values in the API require a different search query when using the Query Language. The following tables provides a translation for these key enumerated values according to resource type. Table A.1. Enumerated Value Translations API Enumerable Type API Enumerable Value Query Language Value data_center_states not_operational notoperational host_states non_responsive nonresponsive install_failed installfailed preparing_for_maintenance preparingformaintenance non_operational nonoperational pending_approval pendingapproval vm_states powering_up poweringup powering_down poweringdown migrating migratingfrom migrating migratingto not_responding notresponding wait_for_launch waitforlaunch reboot_in_progress rebootinprogress saving_state savingstate restoring_state restoringstate

Commands:
Chapter 3. Support and compatibility This section highlights supported version updates in Red Hat Process Automation Manager 7.13. Note Oracle WebLogic Server (WLS) was not tested or verified for Red Hat Process Automation Manager 7.13.4 SP2. For a complete list of supported configurations, see Red Hat Process Automation Manager 7 Supported Configurations . Table 3.1. Supported configurations in Red Hat Process Automation Manager 7.13 Component Supported Version Notes Red Hat build of Quarkus 2.7.x NA Red Hat JBoss EAP 7.4.x Red Hat Process Automation Manager now supports Red Hat JBoss EAP version 7.4.2 or later Spring Boot 2.5.12 NA AMQ Streams 2.2 Supported for high-availability event-driven decisions Red Hat JBoss Web Server 5.6 NA Red Hat OpenShift Container Platform 4.12 NA

Commands:
Chapter 5. Red Hat build of OpenJDK features The latest Red Hat build of OpenJDK 11 release might include new features. Additionally, the latest release might enhance, deprecate, or remove features that originated from earlier Red Hat build of OpenJDK 11 releases. Note For all the other changes and security fixes, see OpenJDK 11.0.26 Released . Red Hat build of OpenJDK new features and enhancements Review the following release notes to understand new features and feature enhancements that Red Hat build of OpenJDK 11.0.26 provides: Option for jar command to avoid overwriting files when extracting an archive In earlier Red Hat build of OpenJDK releases, when the jar tool extracted files from an archive, the jar tool overwrote any existing files with the same name in the target directory. Red Hat build of OpenJDK 11.0.26 adds a new ‐k (or ‐‐keep-old-files ) option that you can use to ensure that the jar tool does not overwrite existing files. You can specify this new option in either short or long format. For example: jar xkf myfile.jar jar --extract ‐‐keep-old-files ‐‐file myfile.jar In Red Hat build of OpenJDK 11.0.26, the jar tool retains the old behavior by default. If you do not explicitly specify the ‐k (or ‐‐keep-old-files ) option, the jar tool automatically overwrites any existing files with the same name. See JDK-8335912 (JDK Bug System) and JDK bug system reference ID: JDK-8337499. IANA time zone database updated to version 2024b In Red Hat build of OpenJDK 11.0.26, the in-tree copy of the Internet Assigned Numbers Authority (IANA) time zone database is updated to version 2024b. This update is primarily concerned with improving historical data for Mexico, Monogolia, and Portugal. This update to the IANA database also includes the following changes: Asia/Choibalsan is an alias for Asia/Ulaanbaatar . The Middle European Time (MET) time zone is equal to Central European Time (CET). Some legacy time-zone IDs are mapped to geographical names rather than fixed offsets: Eastern Standard Time (EST) is mapped to America/Panama rather than -5:00 . Mountain Standard Time (MST) is mapped to America/Phoenix rather than -7:00 . Hawaii Standard Time (HST) is mapped to Pacific/Honolulu rather than -10:00 . Red Hat build of OpenJDK overrides the change in the legacy time-zone ID mappings by retaining the existing fixed-offset mapping. See JDK-8339637 (JDK Bug System) .

Commands:
18.9. Creating a Virtual Network To create a virtual network on your system: Open the Virtual Networks tab from within the Connection Details menu. Click the Add Network button, identified by a plus sign (+) icon. For more information, refer to Section 18.8, "Managing a Virtual Network" . Figure 18.12. Virtual network configuration This will open the Create a new virtual network window. Click Forward to continue. Figure 18.13. Creating a new virtual network Enter an appropriate name for your virtual network and click Forward . Figure 18.14. Naming your virtual network Enter an IPv4 address space for your virtual network and click Forward . Figure 18.15. Choosing an IPv4 address space Define the DHCP range for your virtual network by specifying a Start and End range of IP addresses. Click Forward to continue. Figure 18.16. Selecting the DHCP range Select how the virtual network should connect to the physical network. Figure 18.17. Connecting to physical network If you select Forwarding to physical network , choose whether the Destination should be Any physical device or a specific physical device. Also select whether the Mode should be NAT or Routed . Click Forward to continue. You are now ready to create the network. Check the configuration of your network and click Finish . Figure 18.18. Ready to create network The new virtual network is now available in the Virtual Networks tab of the Connection Details window.

Commands:
3.16. Searching for Pools The following table describes all search options for Pools. Table 3.12. Searching for Pools Property (of resource or resource-type) Type Description (Reference) name String The name of the pool. description String The description of the pool. type List The type of pool. sortby List Sorts the returned results by one of the resource properties. page Integer The page number of results to display. Example Pools: type = automatic This example returns a list of pools with a type of automatic .

Commands:
10.2. Cluster Does Not Form If you find you are having trouble getting a new cluster to form, check for the following things: Make sure you have name resolution set up correctly. The cluster node name in the cluster.conf file should correspond to the name used to resolve that cluster's address over the network that cluster will be using to communicate. For example, if your cluster's node names are nodea and nodeb make sure both nodes have entries in the /etc/cluster/cluster.conf file and /etc/hosts file that match those names. If the cluster uses multicast for communication between nodes, make sure that multicast traffic is not being blocked, delayed, or otherwise interfered with on the network that the cluster is using to communicate. Note that some Cisco switches have features that may cause delays in multicast traffic. Use telnet or SSH to verify whether you can reach remote nodes. Execute the ethtool eth1 | grep link command to check whether the ethernet link is up. Use the tcpdump command at each node to check the network traffic. Ensure that you do not have firewall rules blocking communication between your nodes. Ensure that the interfaces the cluster uses for inter-node communication are not using any bonding mode other than 0, 1, or 2. (Bonding modes 0 and 2 are supported as of Red Hat Enterprise Linux 6.4.)

Commands:
20.42. Managing Resources for Guest Virtual Machines virsh allows the grouping and allocation of resources on a per guest virtual machine basis. This is managed by the libvirt daemon which creates cgroups and manages them on behalf of the guest virtual machine. The only thing that is left for the system administrator to do is to either query or set tunables against specified guest virtual machines. The libvirt service uses the following cgroups for tuning and monitoring virtual machines: memory - The memory controller allows for setting limits on RAM and swap usage and querying cumulative usage of all processes in the group cpuset - The CPU set controller binds processes within a group to a set of CPUs and controls migration between CPUs. cpuacct - The CPU accounting controller provides information about CPU usage for a group of processes. cpu -The CPU scheduler controller controls the prioritization of processes in the group. This is similar to granting nice level privileges. devices - The devices controller grants access control lists on character and block devices. freezer - The freezer controller pauses and resumes execution of processes in the group. This is similar to SIGSTOP for the whole group. net_cls - The network class controller manages network utilization by associating processes with a tc network class. cgroups are set up by systemd in libvirt . The following virsh tuning commands affect the way cgroups are configured: schedinfo - described in Section 20.43, "Setting Schedule Parameters" blkdeviotune - described in Section 20.44, "Disk I/O Throttling" blkiotune - described in Section 20.45, "Display or Set Block I/O Parameters" domiftune - described in Section 20.12.5, "Setting Network Interface Bandwidth Parameters" memtune - described in Section 20.46, "Configuring Memory Tuning" For more information about cgroups, see the Red Hat Enterprise Linux 7 Resource Management Guide .

Commands:
Chapter 3. Features and benefits 3.1. Current features and benefits .NET 8.0 offers the following features and benefits. Runtime and framework libraries .NET consists of the runtime and the framework libraries as well as compilers, build tools, tools to fetch NuGet packages, and a command-line interface to tie everything together. Benefits include: Automatic memory management Type safety Delegates and lambdas Generic types Language Integrated Query (LINQ) Async programming Native interoperability Source generators .NET 8.0 supports developing applications using ASP.NET Core 8.0 and EF Core 8.0, which bring benefits such as: Lightweight and modular HTTP request pipeline Ability to host on a web server or self-host in your own process Built on .NET, which supports true side-by-side app versioning Integrated support for creating and using NuGet packages Single aligned web stack for web UI and web APIs Cloud-ready environment-based configuration Built-in support for dependency injection Tools that simplify modern web development 3.2. New features and benefits .NET 8.0 continues to broaden its support and tools for application development in an open source environment. The latest version of .NET includes the following improvements: C# updated to C#12 F# updated to F#8 Support for building containers: .NET 8.0 includes built-in support for building container images for .NET projects. Performance improvements: The new FrozenDirectory and FrozenSet types are optimized for write once, read many (WORM) scenarios, and the new IUtf8SpanFormattable interface enables writing out a UTF-8 string representation for an object. ASP.NET Core 8.0 improvements: Server-side rendering of blazor components is now possible. ASP.NET Core 8.0 improves the built-in support for inddentity auhtentication and authorization. Minimal API and gRPC applications can now be built with NativeAOT .

Commands:
Chapter 8. Installing an IdM server or replica with custom database settings from an LDIF file You can install an IdM server and IdM replicas with custom settings for the Directory Server database. The following procedure shows you how to create an LDAP Data Interchange Format (LDIF) file with database settings, and how to pass those settings to the IdM server and replica installation commands. Prerequisites You have determined custom Directory Server settings that improve the performance of your IdM environment. See Adjusting IdM Directory Server performance . Procedure Create a text file in LDIF format with your custom database settings. Separate LDAP attribute modifications with a dash (-). This example sets non-default values for the idle timeout and maximum file descriptors. Use the --dirsrv-config-file parameter to pass the LDIF file to the installation script. To install an IdM server: To install an IdM replica: Additional resources Options for the ipa-server-install and ipa-replica-install commands

Commands:
dn: cn=config changetype: modify replace: nsslapd-idletimeout nsslapd-idletimeout: 1800 - replace: nsslapd-maxdescriptors nsslapd-maxdescriptors: 8192
ipa-server-install --dirsrv-config-file filename.ldif
ipa-replica-install --dirsrv-config-file filename.ldif