mtpti5iD/redhat-docs_dataset huggingface dataset:
A.2. Preparing HAProxy Nodes The following setup assumes two HAProxy nodes named haproxy and haproxy2 , and two Ceph Object Gateway servers named rgw1 and rgw2 . You may use any naming convention you prefer. Perform the following procedure on your two HAProxy nodes: Install Red Hat Enterprise Linux 7. Register the nodes. Enable the Red Hat Enterprise Linux 7 server repository. Update the server. Install admin tools (for example, wget , vim , and so on) as needed. Open port 80. For HTTPS, open port 443.

Commands:
subscription-manager register
subscription-manager repos --enable=rhel-7-server-rpms
yum update -y
firewall-cmd --zone=public --add-port 80/tcp --permanent firewall-cmd --reload
firewall-cmd --zone=public --add-port 443/tcp --permanent firewall-cmd --reload
Chapter 3. Enhancements Streams for Apache Kafka 2.7 adds a number of enhancements. 3.1. Kafka 3.7.0 enhancements For an overview of the enhancements introduced with Kafka 3.7.0, refer to the Kafka 3.7.0 Release Notes. 3.2. Kafka Bridge text format When performing producer operations, POST requests must provide Content-Type headers specifying the embedded data format of the messages produced. Previously, JSON and binary were the supported formats for record and key values. It's now possible to also use text format. Table 3.1. Supported content type formats Embedded data format Content-Type header JSON Content-Type: application/vnd.kafka.json.v2+json Binary Content-Type: application/vnd.kafka.binary.v2+json Text Content-Type: application/vnd.kafka.text.v2+json

Commands:
5.2. Network Security Recommended Practices Network security is a critical part of a secure virtualization infrastructure. See the following recommended practices for securing the network: Ensure that remote management of the system takes place only over secured network channels. Tools such as SSH and network protocols such as TLS or SSL provide both authentication and data encryption to assist with secure and controlled access to systems. Ensure that guest applications transferring sensitive data do so over secured network channels. If protocols such as TLS or SSL are not available, consider using one like IPsec. Configure firewalls and ensure they are activated at boot. Only network ports needed for the use and management of the system should be allowed. Test and review firewall rules regularly. 5.2.1. Securing Connectivity to SPICE The SPICE remote desktop protocol supports SSL/TLS which should be enabled for all of the SPICE communication channels (main, display, inputs, cursor, playback, record). 5.2.2. Securing Connectivity to Storage You can connect virtualized systems to networked storage in many different ways. Each approach presents different security benefits and concerns, but the same security principles apply to each: authenticate the remote store pool before use, and protect the confidentiality and integrity of the data while it is being transferred. The data must also remain secure while it is stored. Red Hat recommends that data is encrypted or digitally signed before storing, or both. Note For more information on networked storage, see the Using Storage Pools section of the Red Hat Enterprise Linux Virtualization Deployment and Administration Guide .

Commands:
Chapter 140. KafkaMirrorMaker2Status schema reference Used in: KafkaMirrorMaker2 Property Description conditions List of status conditions. Condition array observedGeneration The generation of the CRD that was last reconciled by the operator. integer url The URL of the REST API endpoint for managing and monitoring Kafka Connect connectors. string autoRestartStatuses List of MirrorMaker 2 connector auto restart statuses. AutoRestartStatus array connectorPlugins The list of connector plugins available in this Kafka Connect deployment. ConnectorPlugin array connectors List of MirrorMaker 2 connector statuses, as reported by the Kafka Connect REST API. map array labelSelector Label selector for pods providing this resource. string replicas The current number of pods being used to provide this resource. integer

Commands:
13.3.4. Select an Installation Server Target That Includes a Driver Update Configure the computer to boot from the network interface by selecting Select Boot Options in the SMS menu, then Select Boot/Install Device . Finally, select your network device from the list of available devices. In the yaboot installation server environment, choose the boot target that you prepared on your installation server. For example, if you labeled this environment rhel6-dd in the /var/lib/tftpboot/yaboot/yaboot.conf file on your installation server, type rhel6-dd at the prompt and press Enter . Refer to Section 13.2.3, "Preparing an Initial RAM Disk Update" and Chapter 30, Setting Up an Installation Server for instructions on using a yaboot installation server to perform an update during installation. Note that this is an advanced procedure - do not attempt it unless other methods of performing a driver update fail.

Commands:
7.9. Additional Resources Installed Documentation 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. Online Documentation Red Hat Enterprise Linux System Administrator's Guide Explains the use of kernel module capabilities. https://access.redhat.com/site/node/28421/Configuring_VLAN_devices_over_a_bonded_interface A Red Hat Knowledgebase article about Configuring VLAN devices over a bonded interface.

Commands:
4.12. Repairing a File System When nodes fail with the file system mounted, file-system journaling allows fast recovery. However, if a storage device loses power or is physically disconnected, file-system corruption may occur. (Journaling cannot be used to recover from storage subsystem failures.) When that type of corruption occurs, you can recover the GFS file system by using the gfs_fsck command. The gfs_fsck command must only be run on a file system that is unmounted from all nodes. Note The gfs_fsck command has changed from releases of Red Hat GFS in the following ways: You can no longer set the interactive mode with Ctrl + C . Pressing Ctrl + C now cancels the gfs_fsck command. Do not press Ctrl + C unless you want to cancel the command. You can increase the level of verbosity by using the -v flag. Adding a second -v flag increases the level again. You can decrease the level of verbosity by using the -q flag. Adding a second -q flag decreases the level again. The -n option opens a file system as read-only and answers no to any queries automatically. The option provides a way of trying the command to reveal errors without actually allowing the gfs_fsck command to take effect. Refer to the gfs_fsck man page, gfs_fsck(8) , for additional information about other command options. Usage -y The -y flag causes all questions to be answered with yes . With the -y flag specified, the gfs_fsck command does not prompt you for an answer before making changes. BlockDevice Specifies the block device where the GFS file system resides. Example In this example, the GFS file system residing on block device /dev/vg01/lvol0 is repaired. All queries to repair are automatically answered with yes .

Commands:
gfs_fsck -y BlockDevice
gfs_fsck -y /dev/vg01/lvol0
5.4. Securing NFS The Network File System , or NFS , is service that provides network accessible file systems for client machines. For more information on how NFS works, refer to the chapter titled Network File System (NFS) in the Reference Guide . For more information about configuring NFS, refer to the System Administrators Guide . The following subsections assume a basic knowledge of NFS. Important The version of NFS included in Red Hat Enterprise Linux, NFSv4, no longer requires the portmap service as outlined in Section 5.2, "Securing Portmap" . NFS traffic now utilizes TCP in all versions, rather than UDP, and requires it when using NFSv4. NFSv4 now includes Kerberos user and group authentication, as part of the RPCSEC_GSS kernel module. Information on portmap is still included, since Red Hat Enterprise Linux supports NFSv2 and NFSv3 which utilize it. 5.4.1. Carefully Plan the Network Now that NFSv4 has the ability to pass all information encrypted using Kerberos over a network, it is important that the service be configured correctly if it is behind a firewall or on a segmented network. NFSv2 and NFSv3 still pass data insecurely, and concerns should be taken into consideration. Careful network design in all of these regards can help prevent security breaches.

Commands:
Chapter 1. Overview of Cryostat Cryostat is a container-native Java application based on JDK Flight Recorder (JFR) that you can use to monitor Java Virtual Machine (JVM) performance for containerized workloads that run on a Red Hat OpenShift cluster. You can deploy Cryostat in a container in a Red Hat OpenShift project that hosts your containerized Java applications. You can create JVM targets that correspond to the JVM instances that you use to run your containerized workload. You can connect Cryostat to the JVM targets to record and analyze data about heap and non-heap memory usage, thread count, garbage collection, and other performance metrics for each JVM target. You can use the tools that are included with Cryostat to monitor the performance of your JVMs in real time, capture JDK Flight Recorder (JFR) recordings and snapshots, generate Automated Analysis reports, and visualize your recorded performance data by using a Grafana dashboard. The Cryostat web console and HTTP API provides a way to analyze your JVM performance data inside the container without having to rely on an external monitoring application. However, you can also export your recordings from Cryostat into an external instance of JDK Mission Control (JMC) when you need to perform a deeper analysis of your data outside of a cluster environment. Cryostat supports role-based access control (RBAC) as a standard feature of OpenShift Container Platform. You can install Cryostat inside a Red Hat OpenShift project by using Operator Lifecycle Manager (OLM). You can also download the latest Cryostat component images from the Red Hat Ecosystem Catalog. The following container images exist for Cryostat 3.0 on the Red Hat Ecosystem Catalog: Cryostat Red Hat build of Cryostat Operator Red Hat build of Cryostat Operator bundle Cryostat reports Cryostat Grafana dashboard Cryostat DB Cryostat storage JFR data source Additional resources Operator Lifecycle Manager (OLM) (OpenShift Container Platform) Container images (Red Hat Ecosystem Catalog)

Commands:
8.78. iw 8.78.1. RHEA-2013:1563 - iw enhancement update Updated iw packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The iw command-line utility is used for configuring wireless devices based on the nl80211 interface. Note The iw packages have been upgraded to upstream version 3.10, which provides one enhancement over the version. This update adds support for Wake on Wireless LAN (WoWLAN) to Atheros WiFi interfaces in Red Hat Enterprise Linux 6. (BZ# 951706 ) Users of iw are advised to upgrade to these updated packages, which add this enhancement.

Commands:
A.10. turbostat The turbostat tool provides detailed information about the amount of time that the system spends in different states. Turbostat is provided by the kernel-tools package. By default, turbostat prints a summary of counter results for the entire system, followed by counter results every 5 seconds, under the following headings: pkg The processor package number. core The processor core number. CPU The Linux CPU (logical processor) number. %c0 The percentage of the interval for which the CPU retired instructions. GHz When this number is higher than the value in TSC, the CPU is in turbo mode TSC The average clock speed over the course of the entire interval. %c1, %c3, and %c6 The percentage of the interval for which the processor was in the c1, c3, or c6 state, respectively. %pc3 or %pc6 The percentage of the interval for which the processor was in the pc3 or pc6 state, respectively. Specify a different period between counter results with the -i option, for example, run turbostat -i 10 to print results every 10 seconds instead. Note Upcoming Intel processors may add additional c-states. As of Red Hat Enterprise Linux 7.0, turbostat provides support for the c7, c8, c9, and c10 states.

Commands:
Appendix A. Managing packages on the base operating system of Satellite Server or Capsule Server Satellite provides the satellite-maintain packages command to install and update packages on the base operating system of your Satellite Server or Capsule Servers. Warning Installing and updating individual packages with dnf is locked by default and not supported. While Satellite provides the satellite-maintain packages unlock command to bypass the locking and enable package management with dnf , this can lead to configuration inconsistencies and compromise the stability of the system. Always use satellite-maintain packages to install and update packages. After installing or updating a package on the base operating system, it is required to run satellite-installer . The satellite-maintain packages command automatically runs satellite-installer after you use it to install or update a package. Note that running satellite-installer might trigger service restarts if updating a package affected service configurations. Table A.1. Overview of satellite-maintain packages subcommands Subcommand Description Installs packages on Satellite Server or Capsule Server Checks for available package updates on Satellite Server or Capsule Server Updates all packages on Satellite Server or Capsule Server Updates specific packages on Satellite Server or Capsule Server Enables package locking to ensure the stability of the base operating system by preventing users from managing packages with dnf . Additional resources For information about updating Satellite to the patch version, see Updating Red Hat Satellite . For a complete reference about using satellite-maintain packages , see the help with satellite-maintain packages --help .

Commands:
satellite-maintain packages install My_Package
satellite-maintain packages check-update
satellite-maintain packages update
satellite-maintain packages update My_Package
satellite-maintain packages lock
Chapter 4. Reviewing and resolving migration issues You can review and resolve migration issues identified by the MTR extension in the left pane. 4.1. Reviewing issues You can use the MTR extension icons to prioritize issues based on their severity. Procedure Select a run configuration directory on the left pane. Expand its folders to view the Hints generated for each application file. Select a hint to view the source code. Right-click a hint and select View Details to view the Rule ID and other information. Prioritize issues based on the following icons, which are displayed to each hint: : The issue must be fixed for a successful migration. : The issue might need to be addressed during migration. 4.2. Resolving issues You can resolve issues by editing the code of a file with a hint 4.2.1. Editing the code of a file You can edit the file of a project imported to VS Code. Procedure In the left pane, right-click an issue and select Open Code . Make any changes needed to the code and save the file. Optional: Right-click the issue and select Mark as Complete or Delete .

Commands:
Chapter 41. Spreadsheet decision tables Spreadsheet decision tables are XLS or XLSX spreadsheets that contain business rules defined in a tabular format. You can include spreadsheet decision tables with standalone Red Hat Decision Manager projects or upload them to projects in Business Central. Each row in a decision table is a rule, and each column is a condition, an action, or another rule attribute. After you create and upload your spreadsheet decision tables, the rules you defined are compiled into Drools Rule Language (DRL) rules as with all other rule assets. All data objects related to a spreadsheet decision table must be in the same project package as the spreadsheet decision table. Assets in the same package are imported by default. Existing assets in other packages can be imported with the decision table.

Commands:
Chapter 37. Networking rsync component, BZ# 1082496 The rsync utility cannot be run as a socket-activated service because the rsyncd@.service file is missing from the rsync package. Consequently, the systemctl start rsyncd.socket command does not work. However, running rsync as a daemon by executing the systemctl start rsyncd.service command works as expected. InfiniBand component, BZ#1172783 The libocrdma package is not included in the default package set of the InfiniBand Support group. Consequently, when users select the InfiniBand Support group and are expecting RDMA over Converged Ethernet (RoCE) to work on Emulex OneConnect adapters, the necessary driver, libocrdma , is not installed by default. On first boot, the user can manually install the missing package by issuing this command: As a result, the user will now be able to use the Emulex OneConnect devices in RoCE mode. vsftpd component, BZ# 1058712 The vsftpd daemon does not currently support ciphers suites based on the Elliptic Curve Diffie-Hellman Exchange (ECDHE) key-exchange protocol. Consequently, when vsftpd is configured to use such suites, the connection is refused with a no shared cipher SSL alert. arptables component, BZ#1018135 Red Hat Enterprise Linux 7 introduces the arptables packages, which replace the arptables_jf packages included in Red Hat Enterprise Linux 6. All users of arptables are advised to update their scripts because the syntax of this version differs from arptables_jf. openssl component, BZ#1062656 It is not possible to connect to any Wi-Fi Protected Access (WPA) Enterprise Access Point (AP) that requires MD5-signed certificates. To work around this problem, copy the wpa_supplicant.service file from the /usr/lib/systemd/system/ directory to the /etc/systemd/system/ directory and add the following line to the Service section of the file: Then run the systemctl daemon-reload command as root to reload the service file. Important Note that MD5 certificates are highly insecure and Red Hat does not recommend using them.

Commands:
~]# yum install libocrdma
Environment=OPENSSL_ENABLE_MD5_VERIFY=1
Chapter 13. Viewing log entries You can view log entries for Red Hat Fuse in the Logs tab. Prerequisite The Logs tab is available when the Java application includes the Log MBean. Procedure To view a list of the log entries, click the Log Entries tab. By default, the list shows log entries in ascending order. You can drill down to each log entry to view detailed information about the log entry. To filter the list of logs to show specific log types, click the Action Bar . You can filter the log entries section according to a text string or the logging level. To change the Fuse Console default settings: In the upper right corner of the Fuse Console, click the user icon and then click Preferences from the drop-down menu. To change the default sorting order, select Server Logs and then click the log entry link to drill down to details about the log entry, such as the bundle name, thread, and the full message text. Optionally, you can customize these settings for storing log messages: The number of log statements to keep in the Fuse Console (the default is 100). The global log level: INFO (the default), OFF, ERROR, WARN, and DEBUG. The child-level messages to include, such as hawtio-oauth and hawtio-core-utils . To reset the Fuse Console Logs settings to the default values, click Reset Reset settings .

Commands:
Chapter 3. Getting Started This chapter describes procedures for initial setup of GFS2 and contains the following sections: Section 3.1, "Prerequisite Tasks" Section 3.2, "Initial Setup Tasks" 3.1. Prerequisite Tasks You should complete the following tasks before setting up Red Hat GFS2: Make sure that you have noted the key characteristics of the GFS2 nodes (see Section 1.2, "Before Setting Up GFS2" ). Make sure that the clocks on the GFS2 nodes are synchronized. It is recommended that you use the Network Time Protocol (NTP) software provided with your Red Hat Enterprise Linux distribution. Note The system clocks in GFS2 nodes must be within a few minutes of each other to prevent unnecessary inode time-stamp updating. Unnecessary inode time-stamp updating severely impacts cluster performance. In order to use GFS2 in a clustered environment, you must configure your system to use the Clustered Logical Volume Manager (CLVM), a set of clustering extensions to the LVM Logical Volume Manager. In order to use CLVM, the Red Hat Cluster Suite software, including the clvmd daemon, must be running. For information on using CLVM, see Logical Volume Manager Administration . For information on installing and administering Red Hat Cluster Suite, see Cluster Administration .

Commands:
2.8. Adding Dependent Libraries Add a MANIFEST.MF file into the META-INF directory, and the following line to add the core Red Hat JBoss Data Virtualization API dependencies for the resource adapter. If your resource adapter depends on any other third party .jar, .dll, or .so files they can be placed at the root of the RAR file. If any of these libraries are already available as modules in JBoss EAP, then you can add the module name to the above MANIFEST.MF file to specify them as dependencies.

Commands:
Dependencies: org.jboss.teiid.common-core,org.jboss.teiid.api,javax.api
7.58. file 7.58.1. RHBA-2012:1339 - file bug fix update Updated file packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. The "file" command is used to identify a particular file according to the type of data contained in the file. The command can identify various file types, including ELF binaries, system libraries, RPM packages, and different graphics formats. Bug Fixes BZ# 795425 The file utility did not contain a "magic" pattern for detecting QED images and was therefore not able to detect such images. A new "magic" pattern for detecting QED images has been added, and the file utility now detects these images as expected. BZ# 795761 The file utility did not contain a "magic" pattern for detecting VDI images and was therefore not able to detect such images. A new "magic" pattern for detecting VDI images has been added, and the file utility now detects these images as expected. BZ# 797784 Previously, the file utility did not attempt to load "magic" patterns from the ~/.magic.mgc file, which caused "magic" patterns stored in this file to be unusable. This update modifies the file utility so it now attempts to load the ~/.magic.mgc file. The file is loaded if it exists and "magic" patterns defined in this file work as expected. BZ# 801711 Previously, the file utility used read timeout when decompressing files using the "-z" option. As a consequence, the utility was not able to detect files compressed by the bzip2 tool. The underlying source code has been modified so that file no longer uses read timeout when decompressing compressed files. Compressed files are now detected as expected when using the "-z" option. BZ# 859834 Previously, the file utility contained multiple "magic" patterns to detect output of the "dump" backup tool. On big-endian architectures, the less detailed "magic" pattern was used and output of the file utility was inconsistent. The less detailed "magic" pattern has been removed, and only one, more detailed, "magic" pattern to detect "dump" output is used now. All users of file are advised to upgrade to these updated packages, which fix these bugs.

Commands: