mtpti5iD/redhat-docs_dataset huggingface dataset:
35.3. Configuring an iface for iSCSI Offload By default, iscsiadm will create an iface configuration for each Chelsio, Broadcom, and ServerEngines port. To view available iface configurations, use the same command for doing so in software iSCSI, i.e. iscsiadm -m iface . Before using the iface of a network card for iSCSI offload, first set the IP address ( target_IP ) that the device should use. For ServerEngines devices that use the be2iscsi driver (i.e. ServerEngines iSCSI HBAs), the IP address is configured in the ServerEngines BIOS set up screen. For Chelsio and Broadcom devices, the procedure for configuring the IP address is the same as for any other iface setting. So to configure the IP address of the iface , use: Example 35.5. Set the iface IP address of a Chelsio card For example, to set the iface IP address of a Chelsio card (with iface name cxgb3i.00:07:43:05:97:07 ) to 20.15.0.66 , use:

Commands:
iscsiadm -m iface -I iface_name -o update -n iface.ipaddress -v target_IP
iscsiadm -m iface -I cxgb3i.00:07:43:05:97:07 -o update -n iface.ipaddress -v 20.15.0.66
17.2.2. Option Fields In addition to basic rules allowing and denying access, the Red Hat Enterprise Linux implementation of TCP wrappers supports extensions to the access control language through option fields. By using option fields within hosts access rules, administrators can accomplish a variety of tasks such as altering log behavior, consolidating access control, and launching shell commands. 17.2.2.1. Logging Option fields let administrators easily change the log facility and priority level for a rule by using the severity directive. In the following example, connections to the SSH daemon from any host in the example.com domain are logged to the default authpriv syslog facility (because no facility value is specified) with a priority of emerg : It is also possible to specify a facility using the severity option. The following example logs any SSH connection attempts by hosts from the example.com domain to the local0 facility with a priority of alert : Note In practice, this example does not work until the syslog daemon ( syslogd ) is configured to log to the local0 facility. Refer to the syslog.conf man page for information about configuring custom log facilities.

Commands:
sshd : .example.com : severity emerg
sshd : .example.com : severity local0.alert
2.7.2. VPN Configurations Using Libreswan Libreswan does not use the terms " source " or " destination " . Instead, it uses the terms " left " and " right " to refer to end points (the hosts). This allows the same configuration to be used on both end points in most cases, although most administrators use " left " for the local host and " right " for the remote host. There are three commonly used methods for authentication of endpoints: Raw RSA keys are commonly used for static host-to-host or subnet-to-subnet IPsec configurations. The hosts are manually configured with each other's public RSA key. This method does not scale well when dozens or more hosts all need to setup IPsec tunnels to each other. X.509 certificates are commonly used for large scale deployments where there are many hosts that need to connect to a common IPsec gateway. A central certificate authority ( CA ) is used to sign RSA certificates for hosts or users. This central CA is responsible for relaying trust, including the revocations of individual hosts or users. Pre-Shared Keys ( PSK ) is the simplest authentication method. PSK's should consist of random characters and have a length of at least 20 characters. Due to the dangers of non-random and short PSKs, this is the least secure form of authentication and it is recommended to use either raw RSA keys or certificate based authentication instead.

Commands:
Chapter 7. Supported integration products AMQ Streams 1.6 supports integration with the following Red Hat products. Red Hat Single Sign-On 7.4 and later for OAuth 2.0 authentication and OAuth 2.0 authorization Red Hat Debezium 1.0 and later for monitoring databases and creating event streams For information on the functionality these products can introduce to your AMQ Streams deployment, refer to the AMQ Streams 1.6 documentation.

Commands:
3.3. Listing Clusters This Ruby example lists the clusters. # Get the reference to the root of the services tree: system_service = connection.system_service # Get the reference to the service that manages the # collection of clusters: cls_service = system_service.clusters_service # Retrieve the list of clusters and for each one # print its name: cls = cls_service.list cls.each do |cl| puts cl.name end In an environment with only the Default cluster, the example outputs: For more information, see http://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4/ClustersService:list .

Commands:
Get the reference to the root of the services tree: system_service = connection.system_service Get the reference to the service that manages the collection of clusters: cls_service = system_service.clusters_service Retrieve the list of clusters and for each one print its name: cls = cls_service.list cls.each do |cl| puts cl.name end
Default
20.5. Creating a New Quota Policy You have enabled quota mode, either in Audit or Enforcing mode. You want to define a quota policy to manage resource usage in your data center. Creating a New Quota Policy Click Administration Quota . Click Add . Fill in the Name and Description fields. Select a Data Center . In the Memory & CPU section, use the green slider to set Cluster Threshold . In the Memory & CPU section, use the blue slider to set Cluster Grace . Click the All Clusters or the Specific Clusters radio button. If you select Specific Clusters , select the check box of the clusters that you want to add a quota policy to. Click Edit to open the Edit Quota window. Under the Memory field, select either the Unlimited radio button (to allow limitless use of Memory resources in the cluster), or select the limit to radio button to set the amount of memory set by this quota. If you select the limit to radio button, input a memory quota in megabytes (MB) in the MB field. Under the CPU field, select either the Unlimited radio button or the limit to radio button to set the amount of CPU set by this quota. If you select the limit to radio button, input a number of vCPUs in the vCpus field. Click OK in the Edit Quota window. In the Storage section, use the green slider to set Storage Threshold . In the Storage section, use the blue slider to set Storage Grace . Click the All Storage Domains or the Specific Storage Domains radio button. If you select Specific Storage Domains , select the check box of the storage domains that you want to add a quota policy to. Click Edit to open the Edit Quota window. Under the Storage Quota field, select either the Unlimited radio button (to allow limitless use of Storage) or the limit to radio button to set the amount of storage to which quota will limit users. If you select the limit to radio button, input a storage quota size in gigabytes (GB) in the GB field. Click OK in the Edit Quota window. Click OK in the New Quota window.

Commands:
Chapter 2. Your path to secure application development Red Hat Trusted Application Pipeline (RHTAP) significantly enhances the efficiency of containerizing and deploying applications, enabling developers to deploy their work within minutes. This innovative platform not only facilitates the creation of a build pipeline for testing and integrating application changes swiftly but also fortifies security measures against supply-chain attacks. By adhering to the rigorous standards of the Supply-chain Levels for Software Artifacts (SLSA) security framework, RHTAP ensures compliance with high-level security requirements. 2.1. Installation overview Before tapping into the vast array of benefits offered by RHTAP, the initial step involves its installation within your organization. The installation of RHTAP is structured around seven key procedures: Creating a GitHub application for RHTAP Forking the template catalog Creating a GitOps git token Creating the Docker configuration value Creating a private-values.yaml file Installing RHTAP in your cluster Finalizing your GitHub application 2.2. Initial setup Prior to beginning the installation process, certain prerequisites must be met to ensure a smooth and successful setup: Cluster Access : Ensure you have ClusterAdmin access to an OpenShift Container Platform (OCP) cluster, accessible both via the CLI and the web console. Red Hat Advanced Cluster Security (ACS) : Obtain necessary values from your ACS instance, including: ACS API token: Follow the instructions provided here to create an API token. ACS central endpoint URL: Configure the endpoint by referring to the instructions available here . Configure ACS for Private Repositories : If you're using private repositories in image registries like Quay.io, configure ACS accordingly: For Quay.io, navigate to Integrations > Image Integrations and select the Quay.io card. Add your OAuth tokens to access your specific Quay.io instance. Validate access via the test button to ensure ACS can scan private images when required. Quay.io Account : Ensure you have an active Quay.io account. Helm CLI Tool : Install the Helm CLI tool by following the guidelines provided here . GitHub Account : Lastly, make sure you have a GitHub account to facilitate certain installation procedures. With these prerequisites in place, you are well-prepared to initiate the installation process by creating a new GitHub application specifically for your RHTAP instance. step Install Red Hat Trusted Application Pipeline

Commands:
Chapter 1. All-in-one Red Hat OpenStack Platform installation The all-in-one installation method uses TripleO to deploy Red Hat OpenStack Platform and related services with a simple, single-node environment. Use this installation to enable proof-of-concept, development, and test deployments on a single node with limited or no follow-up operations. Important This feature is available in this release as a Technology Preview , and therefore is not fully supported by Red Hat. It should only be used for testing, and should not be deployed in a production environment. For more information about Technology Preview features, see Scope of Coverage Details . 1.1. Prerequisites Your system must have a Red Hat Enterprise Linux 9.0 base operating system installed. Your system must have two network interfaces so that internet connectivity is not disrupted while TripleO configures the second interface. Your system must have 4 CPUs, 8GB RAM, and 30GB disk space. Example network configuration Interface eth0 assigned to the default network 192.168.122.0/24. Use this interface for general connectivity. This interface must have internet access. Interface eth1 assigned to the management network 192.168.25.0/24. TripleO uses this interface for the OpenStack services.

Commands:
7.168. pulseaudio 7.168.1. RHBA-2015:0655 - pulseaudio bug fix update Updated pulseaudio packages that fix several bugs are now available for Red Hat Enterprise Linux 6. PulseAudio is a sound server for Linux and other Unix-like operating systems. It is intended to be an improved drop-in replacement for the Enlightened Sound Daemon (ESOUND). Bug Fixes BZ# 812444 Previously, the pulseaudio(1) man page did not mention the PulseAudio cookie file. As a consequence, if a user wanted to connect to the audio server but was logged in with a different user and cookie, the connection failed, and it was not clear from the documentation what the user must do. With this update, the man page has been improved, and the necessary steps can be found there. BZ# 1111375 Prior to this update, certain applications that require lower audio latency produced low-quality sound when using the PulseAudio "combine" module. With this update, the "combine" module uses automatically adjusted audio latency instead of fixed high audio latency. As a result, sound quality is no longer affected when using low-latency applications with the "combine" module. BZ# 1110950 Previously, the following warning message was displayed during the booting process when using PulseAudio : udevd[PID]: GOTO 'pulseaudio_check_usb' has no matching label in: '/lib/udev/rules.d/90-pulseaudio.rules' The invalid parameter that caused this problem has been removed from PulseAudio udev rules, and the warning message no longer appears. Users of pulseaudio are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 44. Networking Cisco usNIC driver Cisco Unified Communication Manager (UCM) servers have an optional feature to provide a Cisco proprietary User Space Network Interface Controller (usNIC), which allows performing Remote Direct Memory Access (RDMA)-like operations for user-space applications. The libusnic_verbs driver, which is supported as a Technology Preview, makes it possible to use usNIC devices via standard InfiniBand RDMA programming based on the Verbs API. (BZ#916384) Cisco VIC kernel driver The Cisco VIC Infiniband kernel driver, which is supported as a Technology Preview, allows the use of Remote Directory Memory Access (RDMA)-like semantics on proprietary Cisco architectures. (BZ#916382) Trusted Network Connect Trusted Network Connect, supported as a Technology Preview, is used with existing network access control (NAC) solutions, such as TLS, 802.1X, or IPsec to integrate endpoint posture assessment; that is, collecting an endpoint's system information (such as operating system configuration settings, installed packages, and others, termed as integrity measurements). Trusted Network Connect is used to verify these measurements against network access policies before allowing the endpoint to access the network. (BZ#755087) SR-IOV functionality in the qlcnic driver Support for Single-Root I/O virtualization (SR-IOV) has been added to the qlcnic driver as a Technology Preview. Support for this functionality will be provided directly by QLogic, and customers are encouraged to provide feedback to QLogic and Red Hat. Other functionality in the qlcnic driver remains fully supported. (BZ#1259547) New packages: libnftnl , nftables As a Technology Preview, this update adds the nftables and libnftl packages. The nftables packages provide a packet-filtering tool, with numerous improvements in convenience, features, and performance over packet-filtering tools. It is the designated successor to the iptables , ip6tables , arptables , and ebtables utilities. The libnftnl packages provide a library for low-level interaction with nftables Netlink's API over the libmnl library. (BZ# 1332585 , BZ#1332581)

Commands:
8.168. pciutils 8.168.1. RHBA-2014:1006 - pciutils bug fix update Updated pciutils packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The pciutils packages provide various utilities for inspecting and manipulating devices connected to the PCI bus. Bug Fixes BZ# 1032827 Prior to this update, the lspci command did not correctly handle empty PCI slots. As a consequence, lspci printed a warning message when it was used on a system with one or more unused PCI slots. Following this update, lspci disregards empty PCI slots and the described problem no longer occurs. BZ# 998626 Previously, the source link for PCI IDs in the /usr/sbin/update-pciids file of the pciutils package was deprecated, and consequently invoked an outdated list of PCI devices. With this update, /usr/sbin/update-pciids has been amended and now links to the up-to-date PCI ID list. Users of pciutils are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 1. Firewall Rules for Red Hat OpenStack Platform This document includes a link to the Red Hat OpenStack Platform (RHOSP) network flow matrix. Use this information to help you define firewall rules. The matrix lists RHOSP core services and their dependencies and describes the ports and protocols they use and the associated traffic flows. It includes the following columns: Service The OpenStack service. Protocol Transmission protocol. Dest. Port Destination port. Source Object Source of data. Dest. Object Destination of data. Source/Dest Pairs Valid source and destination pairs. Dest. Network Destination network. ServiceNetMap Parent Determines the network type used for each service. Traffic Description Notes about the traffic flow. 1.1. Using the Red Hat OpenStack Network Flow Matrix The network flow matrix is a comma separated values (CSV) file that describes flows to and from Red Hat OpenStack Platform (RHOSP) services. Note The network flow matrix describes common traffic flows. It does not describe every possible service and flow. Some flows that are not described in this matrix might be critical to operation. For example, if you block all traffic and then selectively open only the flows described here, you might unintentionally block a necessary flow. That could cause issues that are difficult to troubleshoot. Procedure Use the following link to download the matrix: Red Hat OpenStack Network Flows . For example, right click the link and choose Save link as . Ensure that the downloaded file has the .csv filename extension. For example, if it is .txt , change it to .csv . Use the information in the file to help you formulate firewall rules. You can open it in a spreadsheet application that accepts .csv files, or access it with your own program.

Commands:
16.5. Troubleshooting virt-who This section provides information on troubleshooting virt-who . 16.5.1. Why is the hypervisor status red? Scenario: On the server side, you deploy a guest on a hypervisor that does not have a subscription. 24 hours later, the hypervisor displays its status as red. To remedy this situation you must get a subscription for that hypervisor. Or, permanently migrate the guest to a hypervisor with a subscription.

Commands:
7.150. mod_wsgi 7.150.1. RHBA-2012:1358 - mod_wsgi bug fix and enhancement update Updated mod_wsgi packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The mod_wsgi packages provide a Apache httpd module, which implements a WSGI compliant interface for hosting Python based web applications. Bug Fix BZ# 670577 Prior to this update, a misleading warning message from the mod_wsgi utilities was logged during startup of the Apache httpd daemon. This update removes this message from the mod_wsgi module. Enhancement BZ# 719409 With this update, access to the SSL connection state is now available in WSGI scripts using the methods "mod_ssl.is_https" and "mod_ssl.var_lookup". All users of mod_wsgi are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2025-03-05 17:09:40 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Part IV. Designing a decision service using guided decision tables As a business analyst or business rules developer, you can use guided decision tables to define business rules in a wizard-led tabular format. These rules are compiled into Drools Rule Language (DRL) and form the core of the decision service for your project. Note You can also design your decision service using Decision Model and Notation (DMN) models instead of rule-based or table-based assets. For information about DMN support in Red Hat Decision Manager 7.13, see the following resources: Getting started with decision services (step-by-step tutorial with a DMN decision service example) Designing a decision service using DMN models (overview of DMN support and capabilities in Red Hat Decision Manager) Prerequisites The space and project for the guided decision tables have been created in Business Central. Each asset is associated with a project assigned to a space. For details, see Getting started with decision services .

Commands:
4.223. perl-NetAddr-IP 4.223.1. RHEA-2011:0873 - perl-NetAddr-IP bug fix update An updated perl-NetAddr-IP package that fixes one bug is now available for Red Hat Enterprise Linux 6. The perl-NetAddr-IP module provides an object-oriented abstraction on top of IP addresses or IP subnets, that allows for easy manipulations. Bug Fix BZ# 692857 Prior to this update, the documentation included in the perl-NetAddr-IP module did not contain a correct description with regard to the addition of a constant to an IP address. The problem has been resolved in this update by correcting the respective part of the documentation. All users of perl-NetAddr-IP are advised to upgrade to this updated package, which fixes this bug.

Commands:
8.157. powertop 8.157.1. RHBA-2013:1575 - powertop bug fix and enhancement update Updated powertop packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. PowerTOP is a tool to detect all the software components that make a computer consume more than necessary power when idle. PowerTOP can be used to reduce power usage by running various commands on the system. Note The powertop package has been upgraded to upstream version 2.3, which provides a number of bug fixes and enhancements over the version including corrected handling of arbitrary interface names. Moreover, checks for usability of the ondemand governor have been added. Also, several changes have been made to enhance user experience and to simplify and improve power management profiling capabilities. (BZ# 682378 , BZ# 697273 , BZ# 829800 ) Bug Fix BZ# 998021 The default soft limit for per-process open file descriptors is 1024, and the default hard limit for per-process file descriptors is 4096. By using the performance counter subsystem, the PowerTOP tool could exceed the limit on complex systems. Consequently, an error message about missing kernel support for perf was displayed. This update adds a fix that temporarily increases both the soft and hard file descriptor limits for the current process to the kernel limit. If the kernel limit is still insufficient, PowerTOP now displays an error message indicating that the file descriptor limits should be manually increased. Users of powertop are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 3. Internal storage services Red Hat OpenShift Data Foundation service is available for consumption internally to the Red Hat OpenShift Container Platform that runs on the following infrastructure: Amazon Web Services (AWS) Bare metal VMware vSphere Microsoft Azure Google Cloud [Technology Preview] Red Hat Virtualization 4.4.x or higher (installer-provisioned infrastructure) Red Hat OpenStack 13 or higher (installer-provisioned infrastructure) [Technology Preview] IBM Power IBM Z and IBM(R) LinuxONE Creation of an internal cluster resource results in the internal provisioning of the OpenShift Data Foundation base services, and makes additional storage classes available to the applications.

Commands: