mtpti5iD/redhat-docs_dataset huggingface dataset:
B.31. java-1.5.0-ibm B.31.1. RHSA-2011:0364 - Critical: java-1.5.0-ibm security update Updated java-1.5.0-ibm packages that fix several security issues are now available for Red Hat Enterprise Linux 4 Extras, and Red Hat Enterprise Linux 5 and 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The IBM 1.5.0 Java release includes the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. CVE-2010-4447 , CVE-2010-4448 , CVE-2010-4450 , CVE-2010-4454 , CVE-2010-4462 , CVE-2010-4465 , CVE-2010-4466 , CVE-2010-4468 , CVE-2010-4471 , CVE-2010-4473 , CVE-2010-4475 This update fixes several vulnerabilities in the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. Detailed vulnerability descriptions are linked from the IBM "Security alerts" page. All users of java-1.5.0-ibm are advised to upgrade to these updated packages, containing the IBM 1.5.0 SR12-FP4 Java release. All running instances of IBM Java must be restarted for this update to take effect.

Commands:
Chapter 3. Block pools The OpenShift Data Foundation operator installs a default set of storage pools depending on the platform in use. These default storage pools are owned and controlled by the operator and it cannot be deleted or modified. With OpenShift Container Platform, you can create multiple custom storage pools which map to storage classes that provide the following features: Enable applications with their own high availability to use persistent volumes with two replicas, potentially improving application performance. Save space for persistent volume claims using storage classes with compression enabled. Note Multiple block pools are not supported for external mode OpenShift Data Foundation clusters. 3.1. Creating a block pool Prerequisites You must be logged into the OpenShift Container Platform web console as an administrator. Procedure Click Storage Data Foundation . In the Storage systems tab, select the storage system and then click the BlockPools tab. Click Create Block Pool . Enter Pool name . Note Using 2-way replication data protection policy is not supported for the default pool. However, you can use 2-way replication if you are creating an additional pool. Select Data protection policy as either 2-way Replication or 3-way Replication . Optional: Select Enable compression checkbox if you need to compress the data. Enabling compression can impact application performance and might prove ineffective when data to be written is already compressed or encrypted. Data written before enabling compression is not compressed. Click Create . 3.2. Updating an existing pool Prerequisites You must be logged into the OpenShift Container Platform web console as an administrator. Procedure Click Storage Data Foundation . In the Storage systems tab, select the storage system and then click BlockPools . Click the Action Menu (...) at the end the pool you want to update. Click Edit Block Pool . Modify the form details as follows: Note Using 2-way replication data protection policy is not supported for the default pool. However, you can use 2-way replication if you are creating an additional pool. Change the Data protection policy to either 2-way Replication or 3-way Replication. Enable or disable the compression option. Enabling compression can impact application performance and might prove ineffective when data to be written is already compressed or encrypted. Data written before enabling compression is not compressed. Click Save . 3.3. Deleting a pool Use this procedure to delete a pool in OpenShift Data Foundation. Prerequisites You must be logged into the OpenShift Container Platform web console as an administrator. Procedure . Click Storage Data Foundation . In the Storage systems tab, select the storage system and then click the BlockPools tab. Click the Action Menu (...) at the end the pool you want to delete. Click Delete Block Pool . Click Delete to confirm the removal of the Pool. Note A pool cannot be deleted when it is bound to a PVC. You must detach all the resources before performing this activity.

Commands:
Chapter 1. About OpenShift Virtualization Learn about OpenShift Virtualization's capabilities and support scope. 1.1. What you can do with OpenShift Virtualization OpenShift Virtualization is an add-on to OpenShift Container Platform that allows you to run and manage virtual machine workloads alongside container workloads. OpenShift Virtualization adds new objects into your OpenShift Container Platform cluster by using Kubernetes custom resources to enable virtualization tasks. These tasks include: Creating and managing Linux and Windows virtual machines Connecting to virtual machines through a variety of consoles and CLI tools Importing and cloning existing virtual machines Managing network interface controllers and storage disks attached to virtual machines Live migrating virtual machines between nodes An enhanced web console provides a graphical portal to manage these virtualized resources alongside the OpenShift Container Platform cluster containers and infrastructure. OpenShift Virtualization is designed and tested to work well with Red Hat OpenShift Data Foundation features. Important When you deploy OpenShift Virtualization with OpenShift Data Foundation, you must create a dedicated storage class for Windows virtual machine disks. See Optimizing ODF PersistentVolumes for Windows VMs for details. You can use OpenShift Virtualization with the OVN-Kubernetes , OpenShift SDN , or one of the other certified default Container Network Interface (CNI) network providers listed in Certified OpenShift CNI Plug-ins . You can check your OpenShift Virtualization cluster for compliance issues by installing the Compliance Operator and running a scan with the ocp4-moderate and ocp4-moderate-node profiles . The Compliance Operator uses OpenSCAP, a NIST-certified tool , to scan and enforce security policies. Important OpenShift Virtualization integration with the Compliance Operator is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in 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 about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . 1.1.1. OpenShift Virtualization supported cluster version OpenShift Virtualization 4.11 is supported for use on OpenShift Container Platform 4.11 clusters. To use the latest z-stream release of OpenShift Virtualization, you must first upgrade to the latest version of OpenShift Container Platform.

Commands:
3.13. RHEA-2011:1727 - new package: python-simpleparse A new python-simpleparse package is now available for Red Hat Enterprise Linux 6. The python-simpleparse package is a simple and fast parser generator for the Python programming environment. This enhancement update adds the python-simpleparse package to Red Hat Enterprise Linux 6 as part of the Technology Preview of Fibre Channel over Ethernet (FCoE) target mode. (BZ# 726776 ) Important This package is provided as a dependency of the fcoe-target-utils package. It is recommended to install it only as a prerequisite for running fcoe-target-utils, and not to use it independently. All users who want to use the Technology Preview of Fibre Channel over Ethernet target mode should install this newly-released package, which adds this enhancement.

Commands:
4.2. The Storage Spectrum Present-day computers actually use a variety of storage technologies. Each technology is geared toward a specific function, with speeds and capacities to match. These technologies are: CPU registers Cache memory RAM Hard drives Off-line backup storage (tape, optical disk, etc.) In terms of capabilities and cost, these technologies form a spectrum. For example, CPU registers are: Very fast (access times of a few nanoseconds) Low capacity (usually less than 200 bytes) Very limited expansion capabilities (a change in CPU architecture would be required) Expensive (more than one dollar/byte) However, at the other end of the spectrum, off-line backup storage is: Very slow (access times may be measured in days, if the backup media must be shipped long distances) Very high capacity (10s - 100s of gigabytes) Essentially unlimited expansion capabilities (limited only by the floorspace needed to house the backup media) Very inexpensive (fractional cents/byte) By using different technologies with different capabilities, it is possible to fine-tune system design for maximum performance at the lowest possible cost. The following sections explore each technology in the storage spectrum. 4.2.1. CPU Registers Every present-day CPU design includes registers for a variety of purposes, from storing the address of the currently-executed instruction to more general-purpose data storage and manipulation. CPU registers run at the same speed as the rest of the CPU; otherwise, they would be a serious bottleneck to overall system performance. The reason for this is that nearly all operations performed by the CPU involve the registers in one way or another. The number of CPU registers (and their uses) are strictly dependent on the architectural design of the CPU itself. There is no way to change the number of CPU registers, short of migrating to a CPU with a different architecture. For these reasons, the number of CPU registers can be considered a constant, as they are changeable only with great pain and expense.

Commands:
Appendix G. Securing Red Hat Virtualization This information is specific to Red Hat Virtualization. It does not cover fundamental security practices related to any of the following: Disabling unnecessary services Authentication Authorization Accounting Penetration testing and hardening of non-RHV services Encryption of sensitive application data Prerequisites You should be proficient in your organization's security standards and practices. If possible, consult with your organization's Security Officer. Consult the Red Hat Enterprise Linux Security hardening before deploying RHEL hosts. G.1. Applying the DISA STIG profile in RHEL based hosts and the standalone Manager When installing RHV, you can select the DISA STIG profile with the UI installer, which is the profile provided by RHEL 8. Important The DISA STIG profile is not supported for Red Hat Virtualization Host (RHVH). Procedure In the Installation Summary screen, select Security Policy . In the Security Policy screen, set the Apply security policy to On . Select DISA STIG for Red Hat Enterprise Linux 8 . Click Select profile . This action adds a green checkmark to the profile and adds packages to the list of Changes that were done or need to be done . Follow the onscreen instructions if they direct you to make any changes. Click Done . On the Installation Summary screen, verify that the status of Security Policy is Everything okay . Reboot the host. G.1.1. Enabling DISA STIG in a self-hosted engine You can enable DISA STIG in a self-hosted engine during deployment when using the command-line. Procedure Start the self-hosted engine deployment script. See Installing Red Hat Virtualization as a self-hosted engine using the command line . When the deployment script prompts Do you want to apply an OpenSCAP security profile? , enter Yes . When the deployment script prompts Please provide the security profile you would like to use? , enter stig . G.2. Applying the PCI-DSS profile in RHV hosts and the standalone Manager When installing RHVH, you can select the PCI-DSS profile with the UI installer, which is the profile provided by RHEL 8. Procedure In the Installation Summary screen, select Security Policy . In the Security Policy screen, set the Apply security policy to On . Select PCI-DSS v3.2.1 Control Baseline for Red Hat Enterprise Linux 8 . Click Select profile . This action adds a green checkmark to the profile and adds packages to the list of Changes that were done or need to be done . Follow the onscreen instructions if they direct you to make any changes. Click Done . In the Installation Summary screen, verify that the status of Security Policy is Everything okay . Reboot the host. G.2.1. Enabling PCI-DSS in a self-hosted engine You can enable PCI-DSS in a self-hosted engine during deployment when using the command-line. Procedure Start the self-hosted engine deployment script. See Installing Red Hat Virtualization as a self-hosted engine using the command line . When the deployment script prompts Do you want to apply an OpenSCAP security profile? , enter Yes . When the deployment script prompts Please provide the security profile you would like to use? , enter pci-dss .

Commands:
Chapter 8. Logging subsystem tuning You can further improve upon JBoss EAP logging subsystem performance in production environments by disabling logging to console, configuring appropriate logging levels, and specifying the best location to store log files. 8.1. Disabling logging to the console Disabling console logging can improve JBoss EAP performance. Although outputting logs to the console can be useful in development and testing environments, for production environments it is not necessary in most cases. The JBoss EAP root logger includes a console log handler for all default standalone server profiles except standalone-full-ha . The default managed domain profiles do not include a console handler. To remove the default console handler from the root logger, use the following management CLI command. 8.2. Configuring logging levels For ideal performance, you must configure the logging levels for your production environment appropriately. For example, although INFO or DEBUG levels might be appropriate for development or testing environments, in most cases you should set your production environment logging level to something higher, such as WARN or ERROR . 8.3. Configuring the location of log files You should consider the storage location of log files as a potential performance issue. If you save logs to a file system or disk configuration that has poor I/O throughput, it has the potential to affect the whole platform's performance. To prevent logging from impacting JBoss EAP performance, it is recommended that you set log locations to high-performance dedicated disks that have a lot of space.

Commands:
/subsystem=logging/root-logger=ROOT:remove-handler(name=CONSOLE)
Chapter 6. Clustering Support for Keepalived and HAProxy Load Balancer technology Red Hat Enterprise Linux 6.6 provides support for Load Balancer technology with Keepalived and HAProxy . Keepalived provides simple and robust facilities for load balancing and high availability. The load-balancing framework relies on the well-known and widely used Linux Virtual Server kernel module providing Layer-4 (transport layer) load balancing. Keepalived implements a set of checkers to dynamically and adaptively maintain and manage a load balanced server pool according to their health. Keepalived also implements the Virtual Router Redundancy Protocol (VRRPv2) to achieve high availability with director failover. HAProxy is a TCP/HTTP reverse proxy which is particularly suited for high availability environments. HAProxy can: Route HTTP requests depending on statically assigned cookies; Spread the load among several servers while assuring server persistence through the use of HTTP cookies; Switch to backup servers in the event a main server fails; Accept connections to special ports dedicated to service monitoring; Stop accepting connections without breaking existing ones; Add, modify, and delete HTTP headers in both directions; Block requests matching particular patterns; Persist client connections to the correct application server depending on application cookies; Report detailed status as HTML pages to authenticated users from a URI intercepted from the application.

Commands:
Chapter 4. Exporting the report in CSV format Migration Toolkit for Runtimes (MTR) provides the ability to export the report data, including the classifications and hints, to a flat file on your local file system. The export function currently supports the CSV file format, which presents the report data as fields separated by commas ( , ). The CSV file can be imported and manipulated by spreadsheet software such as Microsoft Excel, OpenOffice Calc, or LibreOffice Calc. Spreadsheet software provides the ability to sort, analyze, evaluate, and manage the result data from an MTR report. 4.1. Exporting the report To export the report as a CSV file, run MTR with the --exportCSV argument. A CSV file is created in the directory specified by the --output argument for each application analyzed. All discovered issues, spanning all the analyzed applications, are included in the AllIssues.csv file that is exported to the root directory of the report. Accessing the report from the application report If you have exported the CSV report, you can download all of the CSV issues in the Issues Report. To download these issues, click Download All Issues CSV in the Issues Report. Figure 4.1. Issues report with CSV download 4.2. Importing the CSV file into a spreadsheet program Launch the spreadsheet software, for example, Microsoft Excel. Choose File Open . Browse to the CSV exported file and select it. The data is now ready to analyze in the spreadsheet software. 4.3. About the CSV data structure The CSV formatted output file contains the following data fields: Rule Id The ID of the rule that generated the given item. Problem type hint or classification Title The title of the classification or hint . This field summarizes the issue for the given item. Description The detailed description of the issue for the given item. Links URLs that provide additional information about the issue. A link consists of two attributes: the link and a description of the link. Application The name of the application for which this item was generated. File Name The name of the file for the given item. File Path The file path for the given item. Line The line number of the file for the given item. Story points The number of story points, which represent the level of effort, assigned to the given item.

Commands:
Chapter 11. Enabling encryption on a vSphere cluster You can encrypt your virtual machines after installing OpenShift Container Platform 4.17 on vSphere by draining and shutting down your nodes one at a time. While each virtual machine is shutdown, you can enable encryption in the vCenter web interface. 11.1. Encrypting virtual machines You can encrypt your virtual machines with the following process. You can drain your virtual machines, power them down and encrypt them using the vCenter interface. Finally, you can create a storage class to use the encrypted storage. Prerequisites You have configured a Standard key provider in vSphere. For more information, see Adding a KMS to vCenter Server . Important The Native key provider in vCenter is not supported. For more information, see vSphere Native Key Provider Overview . You have enabled host encryption mode on all of the ESXi hosts that are hosting the cluster. For more information, see Enabling host encryption mode . You have a vSphere account which has all cryptographic privileges enabled. For more information, see Cryptographic Operations Privileges . Procedure Drain and cordon one of your nodes. For detailed instructions on node management, see "Working with Nodes". Shutdown the virtual machine associated with that node in the vCenter interface. Right-click on the virtual machine in the vCenter interface and select VM Policies Edit VM Storage Policies . Select an encrypted storage policy and select OK . Start the encrypted virtual machine in the vCenter interface. Repeat steps 1-5 for all nodes that you want to encrypt. Configure a storage class that uses the encrypted storage policy. For more information about configuring an encrypted storage class, see "VMware vSphere CSI Driver Operator". 11.2. Additional resources Working with nodes vSphere encryption Requirements for encrypting virtual machines

Commands:
1.3.2. Lock Management Lock management is a common cluster-infrastructure service that provides a mechanism for other cluster infrastructure components to synchronize their access to shared resources. In a Red Hat cluster, one of the following Red Hat Cluster Suite components operates as the lock manager: DLM (Distributed Lock Manager) or GULM (Grand Unified Lock Manager). The major difference between the two lock managers is that DLM is a distributed lock manager and GULM is a client-server lock manager. DLM runs in each cluster node; lock management is distributed across all nodes in the cluster (refer to Figure 1.2, "CMAN/DLM Overview" ). DLM can be the lock manager only in a cluster configured with CMAN as its cluster manager. GULM runs in nodes designated as GULM server nodes; lock management is centralized in the nodes designated as GULM server nodes. GULM server nodes manage locks through GULM clients in the cluster nodes (refer to Figure 1.3, "GULM Overview" ). With GULM, lock management operates in a limited number of nodes: either one, three, or five nodes configured as GULM servers. GFS and CLVM use locks from the lock manager. GFS uses locks from the lock manager to synchronize access to file system metadata (on shared storage). CLVM uses locks from the lock manager to synchronize updates to LVM volumes and volume groups (also on shared storage).

Commands:
Chapter 10. Registering systems to Red Hat Subscription Management If you are using Red Hat Subscription Management as the data collection tool, register your RHEL systems to Red Hat Subscription Management. Systems that are registered to Red Hat Subscription Management can be found and tracked by the subscriptions service. Some RHEL images can use the autoregistration feature of the RHEL management bundle and do not have to be manually registered to Red Hat Subscription Management. However, the following specific requirements must be met: The image must be based on RHEL 8.4 and later or 8.3.1 and later. The image must be an Amazon Web Services (AWS) or Microsoft Azure cloud services image. The image can be a Cloud Access Gold Images image or a custom image, such as an image built with Image Builder. If it is a custom image, the subscription-manager tool in the image must be configured to use autoregistration. The image must be associated with an AWS or Azure integration, as configured from the Settings > Integrations option in the Hybrid Cloud Console, with the RHEL management bundle selected for activation. Note The integrations service was formerly known as the sources service in the Hybrid Cloud Console. The image must be provisioned after this integration is created. RHEL systems that do not meet these requirements must be registered manually to be tracked by the subscriptions service. Procedure Register your RHEL systems to Red Hat Subscription Management, if not already registered. For more information about this process, see the following information: Information in the Red Hat Subscription Management product documentation, including information about registering and unregistering systems in the Quick Registration for RHEL guide. Supplemental information about registering systems in the How do I register a system to Customer Portal Subscription Management? article.

Commands: