mtpti5iD/redhat-docs_dataset huggingface dataset:
14.2.4. Adding a New Hard Disk Using LVM In this example, a new IDE hard disk was added. The figure below illustrates the details for the new hard disk. From the figure below, the disk is uninitialized and not mounted. To initialize a partition, click on the Initialize Entity button. For more details, see Section 14.2.1, "Utilizing Uninitialized Entities" . Once initialized, LVM will add the new volume to the list of unallocated volumes as illustrated in Example 14.4, "Create a new volume group" . Figure 14.13. Uninitialized hard disk

Commands:
Chapter 4. Networking HAProxy HAProxy is a stand-alone, Layer 7, high-performance network load balancer for TCP and HTTP-based applications which can perform various types of scheduling based on the content of the HTTP requests. Red Hat Enterprise Linux 6.4 introduces the haproxy package as a Technology Preview. Mellanox SR-IOV Support Single Root I/O Virtualization (SR-IOV) is now supported as a Technology Preview in the Mellanox libmlx4 library and the following drivers: mlx_core mlx4_ib (InfiniBand protocol) mlx_en (Ethernet protocol)

Commands:
Chapter 5. Enabling automatic screen lock Enabling automatic screen lock is a security measure that helps protect your computer when it is left unattended. This feature ensures that your screen is locked after a specified period of inactivity, requiring a password or authentication to regain access. Procedure Open Settings . Click Privacy . Choose Screen Lock . Toggle the switch to enable automatic screen lock. Set the desired time interval for automatic screen lock delay. This interval defines how long your screen stays active after itthe screen is automatically locked.

Commands:
Chapter 2. Installing Red Hat Developer Hub on OpenShift Dedicated on GCP using the Helm Chart You can install Developer Hub on OpenShift Dedicated on GCP using the Red Hat Developer Hub Helm Chart. Prerequisites You have a valid GCP account. Your OpenShift Dedicated cluster is running on GCP. For more information, see Creating a cluster on GCP in Red Hat OpenShift Dedicated documentation. You have installed Helm 3 or the latest. Procedure From the Developer perspective on the Developer Hub web console, click +Add . From the Developer Catalog panel, click Helm Chart . In the Filter by keyword box, enter Developer Hub and click the Red Hat Developer Hub card. From the Red Hat Developer Hub page, click Create . From your cluster, copy the OpenShift Container Platform router host (for example: apps.<clusterName>.com ). Select the radio button to configure the Developer Hub instance with either the form view or YAML view. The Form view is selected by default. Using Form view To configure the instance with the Form view, go to Root Schema global Enable service authentication within Backstage instance and paste your OpenShift Container Platform router host into the field on the form. Using YAML view To configure the instance with the YAML view, paste your OpenShift Container Platform router hostname in the global.clusterRouterBase parameter value as shown in the following example: global: auth: backend: enabled: true clusterRouterBase: apps.<clusterName>.com # other Red Hat Developer Hub Helm Chart configurations Edit the other values if needed, then click Create and wait for the database and Developer Hub to start. Verification To access the the Developer Hub, click the Open URL icon. Additional resources Configuring Customizing

Commands:
global: auth: backend: enabled: true clusterRouterBase: apps.<clusterName>.com # other Red Hat Developer Hub Helm Chart configurations
Appendix B. Revision History Revision History Revision 0.10-06 Tue 03 Mar 2020 Marc Muehlfeld Added the Configuring Policy-based Routing to Define Alternative Routes section. Revision 0.10-05 Fri 22 Nov 2019 Marc Muehlfeld Rewrote the Configuring the Squid Caching Proxy Server chapter. Revision 0.10-04 Tue 06 Aug 2019 Marc Muehlfeld Version for 7.7 GA publication. Revision 0.10-03 Thu 22 Mar 2018 Ioanna Gkioka Version for 7.5 GA publication. Revision 0.10-02 Mon 14 Aug 2017 Ioanna Gkioka Async release with misc. updates Revision 0.10-01 Tue 25 Jul 2017 Mirek Jahoda Version for 7.4 GA publication. Revision 0.9-30 Tue 18 Oct 2016 Mirek Jahoda Version for 7.3 GA publication. Revision 0.9-25 Wed 11 Nov 2015 Jana Heves Version for 7.2 GA release. Revision 0.9-15 Tue 17 Feb 2015 Christian Huffman Version for 7.1 GA release Revision 0.9-14 Fri Dec 05 2014 Christian Huffman Updated the nmtui and NetworkManager GUI sections. Revision 0.9-12 Wed Nov 05 2014 Stephen Wadeley Improved IP Networking , 802.1Q VLAN tagging , and Teaming . Revision 0.9-11 Tues Oct 21 2014 Stephen Wadeley Improved Bonding , Bridging , and Teaming . Revision 0.9-9 Tue Sep 2 2014 Stephen Wadeley Improved Bonding and Consistent Network Device Naming . Revision 0.9-8 Tue July 8 2014 Stephen Wadeley Red Hat Enterprise Linux 7.0 GA release of the Networking Guide. Revision 0-0 Wed Dec 12 2012 Stephen Wadeley Initialization of the Red Hat Enterprise Linux 7 Networking Guide. B.1. Acknowledgments Certain portions of this text first appeared in the Red Hat Enterprise Linux 6 Deployment Guide ,

Commands:
Appendix B. About Service Interconnect documentation Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message . Revised on 2025-02-24 19:04:53 UTC

Commands:
Chapter 8. Virtualizing Red Hat Enterprise Linux on Other Platforms This chapter contains useful reference material for customers running Red Hat Enterprise Linux 6 as a virtualized operating system on other virtualization hosts. 8.1. On VMware ESX Red Hat Enterprise Linux 6.0 and onward provide the vmw_balloon driver, a paravirtualized memory ballooning driver used when running Red Hat Enterprise Linux on VMware hosts. For further information about this driver, refer to http://kb.VMware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1002586 . Red Hat Enterprise Linux 6.3 and onward provide the vmmouse_drv driver, a paravirtualized mouse driver used when running Red Hat Enterprise Linux on VMware hosts. For further information about this driver, refer to http://kb.VMware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=5739104 . Red Hat Enterprise Linux 6.3 and onward provide the vmware_drv driver, a paravirtualized video driver used when running Red Hat Enterprise Linux on VMware hosts. For further information about this driver, refer to http://kb.VMware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1033557 . Red Hat Enterprise Linux 6.3 and onward provide the vmxnet3 driver, a paravirtualized network adapter used when running Red Hat Enterprise Linux on VMware hosts. For further information about this driver, refer to http://kb.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805 . Red Hat Enterprise Linux 6.4 and onward provide the vmw_pvscsi driver, a paravirtualized SCSI adapter used when running Red Hat Enterprise Linux on VMware hosts. For further information about this driver, refer to http://kb.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398 .

Commands:
3.4. Listing Logical Networks This Ruby example lists the logical networks. # 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 networks: nws_service = system_service.networks_service # Retrieve the list of clusters and for each one # print its name: nws = nws_service.list nws.each do |nw| puts nw.name end In an environment with only the default management network, the example outputs: For more information, see NetworksService: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 networks: nws_service = system_service.networks_service Retrieve the list of clusters and for each one print its name: nws = nws_service.list nws.each do |nw| puts nw.name end
ovirtmgmt
Chapter 11. Security TLS 1.2 support added to all system components With the addition of TLS 1.2 support to the GnuTLS component, Red Hat Enterprise Linux 6 offers complete support for TLS 1.2 in the shipped security libraries: OpenSSL , NSS , and GnuTLS . Several modern standards such as PCI-DSS v3.1 recommend the latest TLS protocol, which is currently TLS 1.2. This addition allows you to use Red Hat Enterprise Linux 6 with future revisions of security standards, which may require TLS 1.2 support. For more information about the cryptographic changes in the Red Hat Enterprise Linux 6, see this article on the Red Hat Customer Portal: https://access.redhat.com/blogs/766093/posts/2787271 . (BZ#1339222) OpenSCAP 1.2.13 is NIST certified OpenSCAP 1.2.13 has been certified by the National Institute of Standards and Technology's (NIST) Security Content Automation Protocol (SCAP) 1.2 in the Authenticated Configuration Scanner category with the Common Vulnerabilities and Exposure (CVE) option. OpenSCAP provides a library that can parse and evaluate each component of the SCAP standard. This makes creating new SCAP tools convenient. Also, OpenSCAP offers a multi-purpose tool designed to format content into documents or scan a system based on this content. (BZ#1364207) vsftpd now uses TLS 1.2 by default Users of the Very Secure File Transfer Protocol (FTP) daemon ( vsftpd ) can select a specific version of TLS protocol up to 1.2. TLS 1.2 has been enabled by default to bring security of vsftpd to the same level as the same package in Red Hat Enterprise Linux 7. New default ciphers specific to TLS 1.2 has been added: ECDHE-RSA-AES256-GCM-SHA384 and ECDHE-ECDSA-AES256-GCM-SHA384 . These changes do not break existing configurations. (BZ#1350724) auditd now supports incremental_async The audit daemon now supports a new flush technique called incremental_async . This new mode significantly improves the audit daemon's logging performance maintaining short flush intervals for security. (BZ#1369249) scap-security-guide now supports ComputeNode The scap-security-guide project now supports scanning of the ComputeNode variant of Red Hat Enterprise Linux and the scap-security-guide package is also distributed in the relevant channel. (BZ# 1311491 ) rsyslog7 now enables TLS 1.2 With this update, the rsyslog7 multi-threaded syslog daemon explicitly enables TLS 1.2 in the GnuTLS component. (BZ#1323199)

Commands:
Chapter 9. IPI certification tests The IPI test validates whether the Host Under Test (HUT) can be controlled, accessed, deployed, and rebooted remotely by using the Red Hat OpenShift Container Platform ironic service and the HUT's bare metal management controller (BMC). The test runs in a container accessible by the node that is running the ironic service. The following RHEL and RHOCP combinations are supported: RHEL 9.2 or 9.4 with RHOCP 4.13, 4.14, or 4.15 RHEL 8 with RHOCP 4.12 The test plan consists of the following tests: 9.1. Self check test The self-check test confirms that all required software packages for certification are installed and unaltered, ensuring the test environment is ready for certification. Certification packages must not be modified for testing or any other purpose. Success Criteria The test environment includes all necessary certification packages and the packages have not been modified. 9.2. IPI test The IPI test automates power management of the server from the OpenShift console through the ironic service to the BMC. The test runs the following subtest: 9.2.1. Check and update power state subtest The check_update_power_state subtest first checks if the HUT is powered on, and then restarts the HUT. The subtest monitors the status of the HUT node every 15 seconds, for a maximum of 15 minutes. Success Criteria The HUT restarts successfully in less than 15 minutes.

Commands:
Chapter 1. Architecture Red Hat Hyperconverged Infrastructure for Virtualization (RHHI for Virtualization) combines compute, storage, networking, and management capabilities in one deployment. RHHI for Virtualization is deployed across a number of physical machines to create a discrete cluster or pod using Red Hat Gluster Storage 3.5 and Red Hat Virtualization 4.4. The dominant use case for this deployment is in remote office branch office (ROBO) environments, where a remote office synchronizes data to a central data center on a regular basis, but does not require connectivity to the central data center to function. The following diagram shows the basic architecture of a single cluster, deployed across three physical machines. 1.1. Understanding VDO As of Red Hat Hyperconverged Infrastructure for Virtualization 1.6, you can configure a Virtual Data Optimizer (VDO) layer to provide data reduction and deduplication for your storage. VDO is supported only when enabled on new installations at deployment time, and cannot be enabled on deployments upgraded from earlier versions of RHHI for Virtualization. VDO performs following types of data reduction to reduce the space required by data. Deduplication Eliminates zero and duplicate data blocks. VDO finds duplicated data using the UDS (Universal Deduplication Service) Kernel Module. Instead of writing the duplicated data, VDO records it as a reference to the original block. The logical block address is mapped to the physical block address by VDO. Compression Reduces the size of the data by packing non-duplicate blocks together into fixed length (4 KB) blocks before writing to disk. This helps to speed up the performance for reading data from storage. At best, data can be reduced to 15% of its original size. Because reducing data has additional processing costs, enabling compression and deduplication reduces write performance. As a result, VDO is not recommended for performance sensitive workloads. Red Hat strongly recommends that you test and verify that your workload achieves the required level of performance with VDO enabled before deploying VDO in production, especially if you are using it in combination with other technology that reduces performance, such as disk encryption. If you plan to use RAID hardware in the layer below VDO, Red Hat strongly recommends using SSD/NVMe disks to avoid performance issues. If there is no use of the RAID hardware layer below VDO, spinning disks can be used.

Commands:
Chapter 1. Insights for RHEL malware detection service overview The Red Hat Insights for Red Hat Enterprise Linux malware detection service is a monitoring and assessment tool that scans RHEL systems for the presence of malware. The malware detection service incorporates YARA pattern-matching software and malware detection signatures. Signatures are provided in partnership with the IBM X-Force threat intelligence team working closely with the Red Hat threat intelligence team. In the malware detection service UI, User Access-authorized administrators and viewers can See the list of signatures against which their RHEL systems are scanned. See aggregate results for all RHEL systems with malware detection enabled in the Insights client. See results for individual systems. Know when a system shows evidence of the presence of malware. These features give security threat assessors and IT incident-response teams valuable information to prepare a response. The malware detection service does not recommend resolutions to resolve or remediate malware incidents. The strategy to take in addressing a malware threat depends on a lot of criteria and considerations specific to each system and organization. Your organization's security incident response team is best qualified to design and implement an effective mitigation and remediation strategy for each circumstance. 1.1. YARA malware signatures YARA signature detection is the cornerstone of the Insights for Red Hat Enterprise Linux malware detection service. YARA signatures are descriptions of malware types expressed as patterns. Each description consists of a set of strings and a boolean expression that define a rule. When one or more of the conditions in a signature exist on a scanned RHEL system, YARA records a hit on that system. 1.2. IBM X-Force Threat Intelligence signatures The Insights for Red Hat Enterprise Linux malware detection service includes predefined signatures developed by the IBM X-Force Threat Intelligence team to expose malware running on RHEL systems. Signatures compiled by the X-Force threat intelligence team are identifiable in the malware detection service by the XFTI - prefix, for example, XFTI_FritzFrog .

Commands:
API overview OpenShift Container Platform 4.18 Overview content for the OpenShift Container Platform API Red Hat OpenShift Documentation Team

Commands:
oc debug node/<node>
chroot /host
systemctl cat kubelet
/etc/systemd/system/kubelet.service.d/20-logging.conf [Service] Environment="KUBELET_LOG_LEVEL=2"
echo -e "[Service]\nEnvironment=\"KUBELET_LOG_LEVEL=8\"" > /etc/systemd/system/kubelet.service.d/30-logging.conf
systemctl daemon-reload
systemctl restart kubelet
rm -f /etc/systemd/system/kubelet.service.d/30-logging.conf
systemctl daemon-reload
systemctl restart kubelet
apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfig metadata: labels: machineconfiguration.openshift.io/role: master name: 99-master-kubelet-loglevel spec: config: ignition: version: 3.2.0 systemd: units: - name: kubelet.service enabled: true dropins: - name: 30-logging.conf contents: | [Service] Environment="KUBELET_LOG_LEVEL=2"
oc adm node-logs --role master -u kubelet
oc adm node-logs --role worker -u kubelet
journalctl -b -f -u kubelet.service
sudo tail -f /var/log/containers/*
- for n in USD(oc get node --no-headers | awk '{print USD1}'); do oc adm node-logs USDn | gzip > USDn.log.gz; done
8.9. Metadata Procedures SYSADMIN.setTableStats Set statistics for the given table. SYSADMIN.setTableStats(TableName in string, Cardinality in integer) SYSADMIN.setColumnStats Set statistics for the given column. SYSADMIN.setColumnStats(TableName in string, ColumnName in string, DistinctCount in integer, NullCount in integer, Max in string, Min in string) All stat values are nullable. Passing a null stat value will leave corresponding metadata value unchanged. SYSADMIN.setProperty Set an extension metadata property for the given record. Extension metadata is typically used by translators. SYSADMIN.setProperty(OldValue return clob, Uid in string, Name in string, Value in clob) Setting a value to null will remove the property. The use of this procedure will not trigger replanning of associated prepared plans.

Commands:
Chapter 4. Technology previews This section provides an overview of Technology Preview features introduced or updated in this release of Red Hat Ceph Storage. Important Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information on Red Hat Technology Preview features support scope, see https: 4.1. Block Devices (RBD) Mapping RBD images to NBD images The rbd-nbd utility maps RADOS Block Device (RBD) images to Network Block Devices (NBD) and enables Ceph clients to access volumes and images in Kubernetes environments. To use rbd-nbd , install the rbd-nbd package. For details, see the rbd-nbd(7) manual page. 4.2. Object Gateway Object Gateway archive site With this release an archive site is supported as a Technology Preview. The archive site allows you to have a history of versions of S3 objects that can only be eliminated through the gateways associated with the archive zone. Including an archive zone in a multizone configuration allows you to have the flexibility of an S3 object history in only one zone while saving the space that the replicas of the versions S3 objects would consume in the rest of the zones.

Commands:
Part VII. Designing a decision service using guided rule templates As a business analyst or business rules developer, you can define business rule templates using the guided rule templates designer in Business Central. These guided rule templates provide a reusable rule structure for multiple rules that 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 Process Automation 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 Process Automation Manager) Prerequisites The space and project for the guided rule templates 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:
Chapter 4. Migrating Camel Quarkus projects 4.1. Updating projects to the latest Quarkus version We recommend that you use Maven to update and upgrade your projects to the latest Quarkus version. Important For projects that use Hibernate ORM or Hibernate Reactive, review the Hibernate ORM 5 to 6 migration quick reference. The following update command covers only a subset of this guide. 4.1.1. Prerequisites Roughly 30 minutes JDK installed with JAVA_HOME configured appropriately Apache Maven 3.8.6 Optionally, the Quarkus CLI if you want to use it A project based on Camel Quarkus version 2.13 or later. 4.1.2. Updating with Maven Configure your extension registry client as described in the Configuring Quarkus extension registry client section of the Quarkus Getting Started guide. Update with Maven: Go to the project directory and update the project to the latest stream: Ensure that the Quarkus Maven plugin version aligns with the latest supported Red Hat build of Quarkus version. Run the update with the following command: mvn io.quarkus.platform:quarkus-maven-plugin:3.8.6:update -N For multi-module projects , always first try the following command: mvn io.quarkus.platform:quarkus-maven-plugin:3.8.6:update If this command fails, you can instead try this longer command: find . -type f -name "pom.xml" -execdir sh -c 'mvn io.quarkus.platform:quarkus-maven-plugin:3.8.6:update -N' \; Note Due to an issue with OpenRewrite , warnings are preset in the migration log. Optional By default, this command updates to the latest current version. To update to a specific stream instead of latest current version, add the stream option to this command followed by the version; for example: -Dstream=3.2 Note Updates of multi-module project may show a lot of errors, because the update tool fails to update modules with <packaging>pom</packaging> . If such modules are present (typically containing versions), update them manually. Analyze the update command output for potential instructions and perform the suggested tasks if needed. Use a diff tool to inspect all changes. Review the migration guide for items that were not updated by the update command. If your project has such items, implement the additional steps advised in these topics. Ensure the project builds without errors, all tests pass, and the application functions as required before deploying to production. Before deploying your updated Quarkus application to production, ensure the following: The project builds without errors. All tests pass. The application functions as required.

Commands:
mvn io.quarkus.platform:quarkus-maven-plugin:3.8.6:update -N
mvn io.quarkus.platform:quarkus-maven-plugin:3.8.6:update
find . -type f -name "pom.xml" -execdir sh -c 'mvn io.quarkus.platform:quarkus-maven-plugin:3.8.6:update -N' \;