mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Enhancements This section describes the major enhancements introduced in Red Hat OpenShift Data foundation 4.18. 3.1. Specifying Multus network address ranges manually When using Multus with piecewise CIDRs, multiple address ranges that were added to Rook can be specified manually. This helps to overcome the limitation with the auto-detection that finds only a single CIDR in environments with piecewise CIDRs, which fail to start or fault to connect to the network. For more information, see Multus network address space sizing . 3.2. Key Rotation for encryption with KMS Enabling key rotation for encryption keys of cluster-wide KMS is now supported. This helps to meet the common security practices requirement. For more information, see Cluster-wide encryption . 3.3. Option to disable Key Rotation for PV encryption Key Rotation for PV encryption, which is enabled by default, can be disabled for certain persistent volume claims (PVCs). For more information, see Disabling key rotation . 3.4. Option to disable default ReclaimSpace ReclaimSpace is enabled by default through a StorageClass or Namespace annotation. Reclaim space for certain persistent volume claims (PVCs) can be disabled as the process of reclaiming space (fstrim) can impact performance. For more information, Disabling reclaim space for a specific PersistentVolumeClaim . 3.5. In-transit encryption after deployment In-transit encryption can be enabled or disabled for existing clusters after the deployment. This encrypts the communication within the cluster for existing clusters. For more information, see Enabling and disabling encryption in-transit post deployment . 3.6. Encryption configuration on OpenShift Data Foundation dashboard OpenShift Data Foundation dashboard provides information about the encryption configuration such as the different status of the encryption at rest and encryption in transit. 3.7. Updates to automatic alert for the type of MDS pod scaling The MDSCPUUsageHigh alert is updated to notify vertical and horizontal scaling based on the CPU usage. For more information, see CephMdsCpuUsageHigh . 3.8. A new log level parameter for the StorageCluster CR A new parameter, spec.nfs.LogLevel , is added to the StorageCluster CR. This log level parameter enables configuring the log level for NFS that provides greater flexibility and control over the logging behavior. This helps to set precise log settings for debugging and monitoring purposes. 3.9. Multicloud Object Gateway operator support 'ap-southeast-5' AWS region MCG operator supports a new AWS region, ap-southeast-5 .

Commands:
Chapter 8. KafkaListenerAuthenticationScramSha512 schema reference Used in: GenericKafkaListener The type property is a discriminator that distinguishes use of the KafkaListenerAuthenticationScramSha512 type from KafkaListenerAuthenticationTls , KafkaListenerAuthenticationOAuth , KafkaListenerAuthenticationCustom . It must have the value scram-sha-512 for the type KafkaListenerAuthenticationScramSha512 . Property Description type Must be scram-sha-512 . string

Commands:
Chapter 5. Working with Counters Counters provide atomic increment and decrement operations that record the count of objects. Prerequisites Start the Data Grid CLI. Connect to a running Data Grid cluster. 5.1. Creating Counters Create strong and weak counters with the Data Grid CLI. Procedure Create a CLI connection to Data Grid. Run the create counter command with the appropriate arguments. Create my-weak-counter . Create my-strong-counter . List available counters. Verify counter configurations. Describe my-weak-counter . { "weak-counter":{ "initial-value":5, "storage":"PERSISTENT", "concurrency-level":1 } } Describe my-strong-counter . { "strong-counter":{ "initial-value":3, "storage":"PERSISTENT", "upper-bound":5 } } 5.2. Adding Deltas to Counters Increment or decrement counters with arbitrary values. Procedure Select a counter. List the current count. Increment the counter value by 2 . Decrement the counter value by -4 . Note Strong counters return values after the operation is applied. Use --quiet=true to hide the return value. For example, add --delta=3 --quiet=true . Weak counters return empty responses.

Commands:
create counter --concurrency-level=1 --initial-value=5 --storage=PERSISTENT --type=weak my-weak-counter
create counter --initial-value=3 --storage=PERSISTENT --type=strong my-strong-counter
ls counters
describe counters/my-weak-counter
{ "weak-counter":{ "initial-value":5, "storage":"PERSISTENT", "concurrency-level":1 } }
describe counters/my-strong-counter
{ "strong-counter":{ "initial-value":3, "storage":"PERSISTENT", "upper-bound":5 } }
counter my-weak-counter
[//containers/default/counters/my-weak-counter]> ls 5
[//containers/default/counters/my-weak-counter]> add --delta=2
[//containers/default/counters/my-weak-counter]> add --delta=-4
Chapter 2. Deploying Quarkus applications You can deploy your Quarkus application on OpenShift by using any of the following build strategies: Docker build S2I Binary Source S2I For more details about each of these build strategies, see Chapter 1. OpenShift build strategies and Quarkus of the Deploying your Quarkus applications to OpenShift Container Platform guide. Note The OpenShift Docker build strategy is the preferred build strategy that supports Quarkus applications targeted for JVM as well as Quarkus applications compiled to native executables. You can configure the deployment strategy using the quarkus.openshift.build-strategy property.

Commands:
Chapter 1. About Red Hat OpenShift Pipelines Red Hat OpenShift Pipelines is a cloud-native, continuous integration and continuous delivery (CI/CD) solution based on Kubernetes resources. It uses Tekton building blocks to automate deployments across multiple platforms by abstracting away the underlying implementation details. Tekton introduces a number of standard custom resource definitions (CRDs) for defining CI/CD pipelines that are portable across Kubernetes distributions. Note Because Red Hat OpenShift Pipelines releases on a different cadence from Red Hat OpenShift Service on AWS, the Red Hat OpenShift Pipelines documentation is now available as a separate documentation set at Red Hat OpenShift Pipelines .

Commands:
Chapter 2. Long term support Red Hat Service Interconnect 1.8 is available as a long term support (LTS) release version. Bug fixes and security advisories are provided for Red Hat Service Interconnect 1.8 in a series of micro releases (1.8.2, 1.8.3, 1.8.4, and so on) for a period of at least 12 months. Note the following important points about the LTS release stream: The LTS release stream provides only bug fixes. No new enhancements will be added to this stream. To remain in a supported configuration, you must upgrade to the latest micro release in the LTS release stream. The LTS version will be supported for at least 12 months from the time of the Red Hat Service Interconnect 1.8.1 GA.

Commands:
19.6. Additional Resources The following is a list of additional documentation about email applications. 19.6.1. Installed Documentation Information on configuring Sendmail is included with the sendmail and sendmail-cf packages. /usr/share/sendmail-cf/README - Contains information on the m4 macro processor, file locations for Sendmail, supported mailers, how to access enhanced features, and more. In addition, the sendmail and aliases man pages contain helpful information covering various Sendmail options and the proper configuration of the Sendmail /etc/mail/aliases file. /usr/share/doc/postfix- version-number / - Contains a large amount of information on how to configure Postfix. Replace version-number with the version number of Postfix. /usr/share/doc/fetchmail- version-number - Contains a full list of Fetchmail features in the FEATURES file and an introductory FAQ document. Replace version-number with the version number of Fetchmail. /usr/share/doc/procmail- version-number / - Contains a README file that provides an overview of Procmail, a FEATURES file that explores every program feature, and an FAQ file with answers to many common configuration questions. Replace version-number with the version number of Procmail. When learning how Procmail works and creating new recipes, the following Procmail man pages are invaluable: procmail - Provides an overview of how Procmail works and the steps involved with filtering email. procmailrc - Explains the rc file format used to construct recipes. procmailex - Gives a number of useful, real-world examples of Procmail recipes. procmailsc - Explains the weighted scoring technique used by Procmail to match a particular recipe to a message. /usr/share/doc/spamassassin- version-number / - Contains a large amount of information pertaining to SpamAssassin. Replace version-number with the version number of the spamassassin package.

Commands:
8.91. initscripts 8.91.1. RHBA-2014:1448 - initscripts bug fix and enhancement update Updated initscripts packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The initscripts packages contain basic system scripts to boot the system, change runlevels, activate and deactivate most network interfaces, and shut down the system cleanly. Bug Fixes BZ# 1018095 Previously, certain network device drivers did not accept ethtool commands right after they appeared in the user-space. As a consequence, the current setting of the specified device driver was not applied and an error message was returned. This update adds the ETHTOOL_DELAY variable, which makes sure the ethtool utility waits for some time before it tries to apply the options settings, thus fixing the bug. BZ# 1024561 When issuing a reboot or halt, the system sometimes killed the S01reboot process and never completed the reboot or shutdown. This update changes the regex for the sed utility to fix this bug, and the S01reboot process now completes successfully. BZ# 1053098 Previously, the ipcalc utility handled netmask parameters incorrectly using the "-c" option. As a consequence, invalid CIDR was ignored and netmask in allowed format was not accepted. The updated "-c" option validates IP addresses for specified address families as expected, invalid CIDR is no longer ignored, and allowed formats of netmask are accepted. BZ# 1086897 Due to a race condition, the "multicast_router" and "hash_max" BRIDGING_OPTS options failed to apply when creating the bridge. With this update, "multicast_router" and "hash_max" are applied after the bridge is up, and BRIDGING_OPTS options now work as intended. BZ# 1101795 Prior to this update, the udev device manager called the hotplug script when a VLAN network was added. However, because the VLAN network has the same default hardware address as the default network adapter device, hotplug reverted the network adapter's IP configuration to the values in the /etc/sysconfig/network-scripts/ directory, and in some cases disconnected the network adapter. This update removes the triggering of the hotplug script for VLAN networks and, as a result, the network adapter now retains its IP address, and thus no longer fails. In addition, this update adds the following Enhancements BZ# 1005355 Previously, the only way to set up VLAN ID was through the name of the new virtual device (vlan10 or eth0.10). With this update, the ID can be specified by the VID option in ifcfg file. BZ# 1023471 The saved seed size in the /etc/rc.sysinit file has been increased from 512 bytes to 4096 bytes to comply with the updated crypto requirements. BZ# 1082765 , BZ# 1099486 With this update, the user can set PRIO and AGEING options for bridges in ifcfg files, which allow ageing to be set in ifcfg-* scripts. Users of initscripts are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Installing Red Hat Virtualization as a standalone Manager with remote databases Red Hat Virtualization 4.4 Installing the Red Hat Virtualization Manager on one server, and its databases on a second server Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract This document describes how to install a standalone Manager environment - where the Red Hat Virtualization Manager is installed on either a physical server or a virtual machine hosted in another environment - with the Manager database and the Data Warehouse service and database hosted on a remote server. Although you can choose to host one database locally and the other remotely, this document assumes that both databases will be hosted remotely. If this is not the configuration you want to use, see the other Installation Options in the Product Guide .

Commands:
Chapter 4. Network considerations The undercloud host requires at least the following networks: Provisioning network - Provides DHCP and PXE-boot functions to help discover bare-metal systems for use in the overcloud. External network - A separate network for remote connectivity to all nodes. The interface connecting to this network requires a routable IP address, either defined statically, or generated dynamically from an external DHCP service. The minimal overcloud network configuration includes the following NIC configurations: Single NIC configuration - One NIC for the provisioning network on the native VLAN and tagged VLANs that use subnets for the different overcloud network types. Dual NIC configuration - One NIC for the provisioning network and the other NIC for the external network. Dual NIC configuration - One NIC for the provisioning network on the native VLAN, and the other NIC for tagged VLANs that use subnets for different overcloud network types. Multiple NIC configuration - Each NIC uses a subnet for a different overcloud network type. For more information on the networking requirements, see Networking requirements .

Commands:
19.4. Tools and Performance Resource Management and Linux Containers Guide The Resource Management and Linux Containers Guide documents tools and techniques for managing system resources and deploying LXC application containers on Red Hat Enterprise Linux 7. Performance Tuning Guide The Performance Tuning Guide documents how to optimize subsystem throughput in Red Hat Enterprise Linux 7. Developer Guide The Developer Guide describes the different features and utilities that make Red Hat Enterprise Linux 7 an ideal enterprise platform for application development. SystemTap Beginners Guide The SystemTap Beginners Guide provides basic instructions on how to use SystemTap to monitor different subsystems of Red Hat Enterprise Linux in finer detail. SystemTap Reference The SystemTap Tapset Reference guide describes the most common tapset definitions users can apply to SystemTap scripts.

Commands:
8.5. Create a New XML Schema Model Important Please note that XML Schema Modeling has been deprecated. 8.5.1. Create a New XML Schema Model To create a new empty XML schema ( .xsd ) model: Launch the New Model Wizard . Specify a unique model name. Select XML Schema (XSD) option from Model Class drop-down menu. Select Datatype Model from Model Type drop-down menu. Click Finish . After that, in the dialog choose XML Schema version which will be used and click OK . Note You can change the target location (i.e. project or folder) by selecting the Browse... button and selecting a project or folder within your workspace. In addition to creating a new empty XML schema model, the following builder option is available: Copy from existing model of the same model class. 8.5.2. Copy an Existing XML Schema Model This builder option performs a structural copy of the contents of an existing model to a newly defined model. You can choose a full copy or select individual model components for copy. To create a new XML schema model by copying contents from another XML schema model, complete first 4 steps from the Create a New XML Schema Model section and continue with these additional steps: Select the model builder labeled Copy from existing model of the same model class and click > . The Copy Existing Model dialog will be displayed. Select an existing XML schema model from the workspace using the browse button. Select the Copy all descriptions option if desired. Click Finish .

Commands:
Chapter 2. Configuring client-side notifications When actions and state changes occur in the Cryostat backend, Cryostat uses a WebSocket connection to show notifications in your Cryostat web client. You can enable or disable notifications on your Cryostat web console. Procedure From the Cryostat web console, click the Settings ( ) icon on the upper-right corner of the web console toolbar. Figure 2.1. Settings icon on the Cryostat web console From the Notifications & Messages panel, choose one of the following options: Enable all notifications by setting All Notifications to on. Disable all notifications by setting All Notifications to off. Expand Show more and select notification categories individually. Figure 2.2. Notifications & Messages panel in Settings window Note If you disable a notification category, your web client still receives notifications and stores them locally. Pop-up notifications will not display in the Cryostat web console, but if you re-enable the category, you can access those notifications. Revised on 2023-12-12 18:19:59 UTC

Commands:
Chapter 30. Mouse Configuration The installation program allows users to select the type of mouse connected to the system. To configure a different mouse type for the system, use the Mouse Configuration Tool . To start the Mouse Configuration Tool , type the command system-config-mouse at a shell prompt (for example, in an XTerm or GNOME terminal). If the X Window System is not running, the text-based version of the tool is started. Figure 30.1. Mouse Configuration Select the new mouse type for the system. If the specific mouse model is not listed, select one of the Generic entries, based on the mouse's number of buttons and its interface. If there is not an exact match, select the generic match that is most compatible with the system and the mouse. Note Select the Generic - Wheel Mouse entry, with the proper mouse port, to enable the scroll button on the mouse. The scroll button on a wheel mouse can be used as the middle mouse button for cutting text, pasting text, and other middle mouse button functions. If the mouse only has two buttons, select Emulate 3 buttons to use a two-button mouse as a three-button mouse. When this option enabled, clicking the two mouse buttons simultaneously emulates a middle mouse button click. If a serial port mouse is selected, click the Serial devices button to configure the correct serial device number, such as /dev/ttyS0 for the mouse. Click OK to save the new mouse type. The selection is written to the file /etc/sysconfig/mouse , and the console mouse service, gpm is restarted. The changes are also written to the X Window System configuration file /etc/X11/xorg.conf ; however, the mouse type change is not automatically applied to the current X session. To enable the new mouse type, log out of the graphical desktop and log back in. Note To reset the order of the mouse buttons for a left-handed user, go to Applications (the main menu on the panel) => Preferences => Mouse , and select Left-handed mouse for the mouse orientation.

Commands:
10.9. Additional Resources ip-link(8) man page - Describes the ip utility's network device configuration commands. nmcli(1) man page - Describes NetworkManager 's command‐line tool. nmcli-examples(5) man page - Gives examples of nmcli commands. nm-settings(5) man page - Description of settings and parameters of NetworkManager connections. nm-settings-ifcfg-rh(5) man page - Description of ifcfg-rh settings in the /etc/sysconfig/network-scripts/ifcfg-* files.

Commands:
Chapter 1. Introduction to RPM The RPM Package Manager (RPM) is a package management system that runs on Red Hat Enterprise Linux (RHEL), CentOS, and Fedora. You can use RPM to distribute, manage, and update software that you create for any of these operating systems. The RPM package management system has the following advantages over distributing software in conventional archive files: RPM manages software in the form of packages that you can install, update, or remove independently of each other, which makes the maintenance of an operating system easier. RPM simplifies the distribution of software because RPM packages are standalone binary files, similar to compressed archives. These packages are built for a specific operating system and hardware architecture. RPMs contain files such as compiled executables and libraries that are placed into the appropriate paths on the filesystem when the package is installed. With RPM, you can perform the following tasks: Install, upgrade, and remove packaged software. Query detailed information about packaged software. Verify the integrity of packaged software. Build your own packages from software sources and complete build instructions. Digitally sign your packages by using the GNU Privacy Guard (GPG) utility. Publish your packages in a DNF repository. In Red Hat Enterprise Linux, RPM is fully integrated into the higher-level package management software, such as DNF or PackageKit. Although RPM provides its own command-line interface, most users need to interact with RPM only through this software. However, when building RPM packages, you must use the RPM utilities such as rpmbuild(8) . 1.1. RPM packages An RPM package consists of an archive of files and metadata used to install and erase these files. Specifically, the RPM package contains the following parts: GPG signature The GPG signature is used to verify the integrity of the package. Header (package metadata) The RPM package manager uses this metadata to determine package dependencies, where to install files, and other information. Payload The payload is a cpio archive that contains files to install to the system. There are two types of RPM packages. Both types share the file format and tooling, but have different contents and serve different purposes: Source RPM (SRPM) An SRPM contains source code and a spec file, which describes how to build the source code into a binary RPM. Optionally, the SRPM can contain patches to source code. Binary RPM A binary RPM contains the binaries built from the sources and patches. 1.2. Listing RPM packaging utilities In addition to the rpmbuild(8) program for building packages, RPM provides other utilities to make the process of creating packages easier. You can find these programs in the rpmdevtools package. Prerequisites The rpmdevtools package has been installed: Procedure Use one of the following methods to list RPM packaging utilities: To list certain utilities provided by the rpmdevtools package and their short descriptions, enter: To list all utilities, enter: Additional resources RPM utilities man pages

Commands:
dnf install rpmdevtools
rpm -qi rpmdevtools
rpm -ql rpmdevtools | grep ^/usr/bin
8.96. librtas 8.96.1. RHEA-2013:1733 - librtas enhancement update Updated librtas packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The librtas packages contain a set of libraries that allow access to the Run-Time Abstraction Services (RTAS) on 64-bit PowerPC architectures. The librtasevent library contains definitions and routines for analyzing RTAS events. Enhancement BZ# 985850 This update adds support for a user space solution for Dynamic Memory Affinity via the PRRN interface. When an affinity for a partition changes as a result of system optimization, the impacted partition will be notified through an event-scan RTAS call that the affinity properties of the partitions have changed. As a result, the partition is expected to refresh its affinity strings through existing RTAS/hidden h_calls. Users of librtas are advised to upgrade to these updated packages, which add this enhancement.

Commands: