mtpti5iD/redhat-docs_dataset huggingface dataset:
22.3. Write Barrier Considerations Some system configurations do not need write barriers to protect data. In most cases, other methods are preferable to write barriers, since enabling write barriers causes a significant performance penalty. Disabling Write Caches One way to alternatively avoid data integrity issues is to ensure that no write caches lose data on power failures. When possible, the best way to configure this is to simply disable the write cache. On a simple server or desktop with one or more SATA drives (off a local SATA controller Intel AHCI part), you can disable the write cache on the target SATA drives with the hdparm command, as in: Battery-Backed Write Caches Write barriers are also unnecessary whenever the system uses hardware RAID controllers with battery-backed write cache. If the system is equipped with such controllers and if its component drives have write caches disabled, the controller will advertise itself as a write-through cache; this will inform the kernel that the write cache data will survive a power loss. Most controllers use vendor-specific tools to query and manipulate target drives. For example, the LSI Megaraid SAS controller uses a battery-backed write cache; this type of controller requires the MegaCli64 tool to manage target drives. To show the state of all back-end drives for LSI Megaraid SAS, use: To disable the write cache of all back-end drives for LSI Megaraid SAS, use: Note Hardware RAID cards recharge their batteries while the system is operational. If a system is powered off for an extended period of time, the batteries will lose their charge, leaving stored data vulnerable during a power failure. High-End Arrays High-end arrays have various ways of protecting data in the event of a power failure. As such, there is no need to verify the state of the internal drives in external RAID storage. NFS NFS clients do not need to enable write barriers, since data integrity is handled by the NFS server side. As such, NFS servers should be configured to ensure data persistence throughout a power loss (whether through write barriers or other means).

Commands:
hdparm -W0 / device /
MegaCli64 -LDGetProp -DskCache -LAll -aALL
MegaCli64 -LDSetProp -DisDskCache -Lall -aALL
Chapter 2. Red Hat OpenStack services on Openshift certification targets To achieve certification, you must implement the following targets: 2.1. Products implementing OpenStack APIs This category includes products that provide OpenStack services or functionalities, such as launching server instances, adding new routers, creating images, creating storage containers and objects, creating user profiles, and so on. These capabilities are achieved by implementing an API or API extension for Networking, Block Storage, or File Share services. For products implementing OpenStack APIs, you are required to complete the relevant certification tests for the API group. The certification process verifies that the service delivers the API in accordance with the platform specifications and that the underlying OpenStack environment is configured correctly. 2.2. Support for certified OpenStack services on Openshift component Support for certified OpenStack services on OpenShift components, such as plugins or drivers, and customer assistance is provided by the Partner shipping the component. The support responsibilities are outlined as follows: If Red Hat certifies and ships a partner component as part of RHOSO, customers should contact Red Hat for assistance with any issues. If a Partner ships a RHOSO-certified component, the Partner is fully responsible for assisting customers and providing support. However, Red Hat certified Partners and Red Hat, maintain active engineering relationships that either party can leverage to ensure quick progress is made on customer issues.

Commands:
Chapter 8. Additional resources How to perform an unsupported conversion from a RHEL-derived Linux distribution to RHEL Red Hat Enterprise Linux technology capabilities and limits Red Hat Enterprise Linux documentation Migration planning guide - migration to RHEL 7 Considerations in adopting RHEL 8 Upgrading from RHEL 7 to RHEL 8 Upgrading from RHEL 8 to RHEL 9 Convert2RHEL FAQ (Frequently Asked Questions)

Commands:
7.208. system-config-printer 7.208.1. RHBA-2015:0224 - system-config-printer bug fix update Updated system-config-printer packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The system-config-printer packages contain a print queue configuration tool with a graphical user interface. Bug Fixes BZ# 854937 Documentation for the pycups library, a part of the system-config-printer packages, was erroneous. The word "as" was missing from some lines and consequently, the code would produce an error when run if the "as" keyword was missing. "As" was added at relevant places to fix this bug. As a result, the documentation text is now correct and complete. BZ# 1063224 Due to erroneous code in the python-cups bindings for libcups, system-config-printer terminated unexpectedly with a segmentation fault when handling UTF-8 characters in certain fields. Now, the execution of system-config-printer no longer results in a segmentation fault. Users of system-config-printer are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 6. Summarizing cluster specifications 6.1. Summarizing cluster specifications by using a cluster version object You can obtain a summary of OpenShift Dedicated cluster specifications by querying the clusterversion resource. Prerequisites You have access to the cluster as a user with the dedicated-admin role. You have installed the OpenShift CLI ( oc ). Procedure Query cluster version, availability, uptime, and general status: USD oc get clusterversion Example output NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.8 True False 8h Cluster version is 4.13.8 Obtain a detailed summary of cluster specifications, update availability, and update history: USD oc describe clusterversion Example output Name: version Namespace: Labels: <none> Annotations: <none> API Version: config.openshift.io/v1 Kind: ClusterVersion # ... Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce URL: https://access.redhat.com/errata/RHSA-2023:4456 Version: 4.13.8 History: Completion Time: 2023-08-17T13:20:21Z Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce Started Time: 2023-08-17T12:59:45Z State: Completed Verified: false Version: 4.13.8 # ...

Commands:
oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.8 True False 8h Cluster version is 4.13.8
oc describe clusterversion
Name: version Namespace: Labels: <none> Annotations: <none> API Version: config.openshift.io/v1 Kind: ClusterVersion Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce URL: https://access.redhat.com/errata/RHSA-2023:4456 Version: 4.13.8 History: Completion Time: 2023-08-17T13:20:21Z Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce Started Time: 2023-08-17T12:59:45Z State: Completed Verified: false Version: 4.13.8
5.294. scsi-target-utils 5.294.1. RHEA-2012:0970 - scsi-target-utils enhancement update An updated scsi-target-utils package that adds two enhancements is now available for Red Hat Enterprise Linux 6. The scsi-target-utils package contains a daemon and tools to setup Small Computer System Interface (SCSI) targets. Currently, software Internet SCSI (iSCSI) and iSCSI Extensions for RDMA (iSER) targets are supported. Enhancements BZ# 747510 Previously, scsi-target-utils did not accurately report certain parameters, such as the native block size of the "direct-store" backing store, lowest aligned logical block address, and optimal transfer length. This could decrease performance of iSCSI devices. This update adds support for the "B0 VPD" and "READ CAPACITY(16)" SCSI commands to match the characteristics of the iSCSI device to its underlying backing store, which improves performance of the iSCSI device. BZ# 605925 With this update, scsi-target-utils now supports authentication for target discovery. It may be configured using the "incomingdiscoveryuser" and "outgoingdiscoveryuser" directives in the "/etc/tgt/targets.conf" file. Configuration details can be seen in the targets.conf(5) manual page. All users of scsi-target-utils are advised to upgrade to this updated package, which adds these enhancements.

Commands:
33.4. Partition Information Figure 33.4. Partition Information Select whether or not to clear the Master Boot Record (MBR). Choose to remove all existing partitions, remove all existing Linux partitions, or preserve existing partitions. To initialize the disk label to the default for the architecture of the system (for example, msdos for x86), select Initialize the disk label if you are installing on a brand new hard drive. Note Although anaconda and kickstart support Logical Volume Management (LVM), at present there is no mechanism for configuring this using the Kickstart Configurator . 33.4.1. Creating Partitions To create a partition, click the Add button. The Partition Options window shown in Figure 33.5, "Creating Partitions" appears. Choose the mount point, file system type, and partition size for the new partition. Optionally, you can also choose from the following: In the Additional Size Options section, choose to make the partition a fixed size, up to a chosen size, or fill the remaining space on the hard drive. If you selected swap as the file system type, you can select to have the installation program create the swap partition with the recommended size instead of specifying a size. Force the partition to be created as a primary partition. Create the partition on a specific hard drive. For example, to make the partition on the first IDE hard disk ( /dev/hda ), specify hda as the drive. Do not include /dev in the drive name. Use an existing partition. For example, to make the partition on the first partition on the first IDE hard disk ( /dev/hda1 ), specify hda1 as the partition. Do not include /dev in the partition name. Format the partition as the chosen file system type. Figure 33.5. Creating Partitions To edit an existing partition, select the partition from the list and click the Edit button. The same Partition Options window appears as when you chose to add a partition as shown in Figure 33.5, "Creating Partitions" , except it reflects the values for the selected partition. Modify the partition options and click OK . To delete an existing partition, select the partition from the list and click the Delete button. 33.4.1.1. Creating Software RAID Partitions To create a software RAID partition, use the following steps: Click the RAID button. Select Create a software RAID partition . Configure the partitions as previously described, except select Software RAID as the file system type. Also, you must specify a hard drive on which to make the partition or specify an existing partition to use. Figure 33.6. Creating a Software RAID Partition Repeat these steps to create as many partitions as needed for your RAID setup. All of your partitions do not have to be RAID partitions. After creating all the partitions needed to form a RAID device, follow these steps: Click the RAID button. Select Create a RAID device . Select a mount point, file system type, RAID device name, RAID level, RAID members, number of spares for the software RAID device, and whether to format the RAID device. Figure 33.7. Creating a Software RAID Device Click OK to add the device to the list.

Commands:
5.29. cluster 5.29.1. RHBA-2012:1480 - cluster and gfs2-utils bug fix update Updated cluster and gfs2-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Red Hat Cluster Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Using redundant hardware, shared disk storage, power management, and robust cluster communication and application failover mechanisms, a cluster can meet the needs of the enterprise market. Bug Fix BZ# 878373 Previously, the fenced daemon was creating its log file with insecure permissions. Even though no sensitive data, such as passwords, usernames, or IP addresses were ever stored in the file, with this update, log files are created with correct permissions. Permissions of an existing log file is also automatically corrected if necessary. All users of cluster and gfs2-utils are advised to upgrade to these updated packages, which fix this bug. 5.29.2. RHBA-2012:1188 - cluster and gfs2-utils bug fix update Updated cluster and gfs2-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Red Hat Cluster Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Using redundant hardware, shared disk storage, power management, and robust cluster communication and application failover mechanisms, a cluster can meet the needs of the enterprise market. Bug Fix BZ# 849049 Previously, it was not possible to specify start-up options to the dlm_controld daemon. As a consequence, certain features were not working as expected. With this update, it is possible to use the /etc/sysconfig/cman configuration file to specify dlm_controld start-up options, thus fixing this bug. All users of cluster and gfs2-utils are advised to upgrade to these updated packages, which fix this bug. 5.29.3. RHBA-2013:1056 - cluster and gfs2-utils bug fix update Updated cluster and gfs2-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6 Extended Update Support. The Red Hat Cluster Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Using redundant hardware, shared disk storage, power management, and robust cluster communication and application failover mechanisms, a cluster can meet the needs of the enterprise market. Bug Fix BZ# 982699 Previously, the cman init script did not handle its lock file correctly. During a node reboot, this could have caused the node itself to be evicted from the cluster by other members. With this update, the cman init script now handles the lock file correctly, and no fencing action is taken by other nodes of the cluster. Users of cluster and gfs2-utils are advised to upgrade to these updated packages, which fix this bug.

Commands:
Appendix A. Reference material A.1. About rule story points A.1.1. What are story points? Story points are an abstract metric commonly used in Agile software development to estimate the level of effort needed to implement a feature or change. The Migration Toolkit for Applications uses story points to express the level of effort needed to migrate particular application constructs, and the application as a whole. It does not necessarily translate to man-hours, but the value should be consistent across tasks. A.1.2. How story points are estimated in rules Estimating the level of effort for the story points for a rule can be tricky. The following are the general guidelines MTA uses when estimating the level of effort required for a rule. Level of Effort Story Points Description Information 0 An informational warning with very low or no priority for migration. Trivial 1 The migration is a trivial change or a simple library swap with no or minimal API changes. Complex 3 The changes required for the migration task are complex, but have a documented solution. Redesign 5 The migration task requires a redesign or a complete library change, with significant API changes. Rearchitecture 7 The migration requires a complete rearchitecture of the component or subsystem. Unknown 13 The migration solution is not known and may need a complete rewrite. A.1.3. Task category In addition to the level of effort, you can categorize migration tasks to indicate the severity of the task. The following categories are used to group issues to help prioritize the migration effort. Mandatory The task must be completed for a successful migration. If the changes are not made, the resulting application will not build or run successfully. Examples include replacement of proprietary APIs that are not supported in the target platform. Optional If the migration task is not completed, the application should work, but the results may not be optimal. If the change is not made at the time of migration, it is recommended to put it on the schedule soon after your migration is completed. Potential The task should be examined during the migration process, but there is not enough detailed information to determine if the task is mandatory for the migration to succeed. An example of this would be migrating a third-party proprietary type where there is no directly compatible type. Information The task is included to inform you of the existence of certain files. These may need to be examined or modified as part of the modernization effort, but changes are typically not required. A.2. Additional resources A.2.1. Additional resources MTA Jira issue tracker: https://issues.redhat.com/projects/MTA/issues MTA mailing list: windup-eng@redhat.com Revised on 2024-12-31 15:05:28 UTC

Commands:
Appendix A. Component Versions This appendix is a list of components and their versions in the Red Hat Enterprise Linux 6.5 release. Table A.1. Component Versions Component Version Kernel 2.6.32-431 QLogic qla2xxx driver 8.05.00.03.06.5-k2 QLogic ql2xxx firmware ql23xx-firmware-3.03.27-3.1 ql2100-firmware-1.19.38-3.1 ql2200-firmware-2.02.08-3.1 ql2400-firmware-7.00.01-1 ql2500-firmware-7.00.01-1 Emulex lpfc driver 8.3.7.21.1p iSCSI initiator utils iscsi-initiator-utils-6.2.0.873-10 DM-Multipath device-mapper-multipath-0.4.9-72 LVM lvm2-2.02.100-8

Commands:
1.3. Red Hat JBoss Data Grid Usage Modes Red Hat JBoss Data Grid offers two usage modes: Remote Client-Server mode Library mode Report a bug 1.3.1. Remote Client-Server Mode Remote Client-Server mode provides a managed, distributed, and clusterable data grid server. Applications can remotely access the data grid server using Hot Rod , Memcached or REST client APIs. All Red Hat JBoss Data Grid operations in Remote Client-Server mode are non-transactional. As a result, a number of features cannot be performed when running JBoss Data Grid in Remote Client-Server mode. There are a number of benefits to running JBoss Data Grid in Remote Client-Server mode if Library mode features are not required. Remote Client-Server mode is client language agnostic, provided there is a client library for your chosen protocol. As a result, Remote Client-Server mode provides: easier scaling of the data grid. easier upgrades of the data grid without impact on client applications. Run the following commands to start JBoss Data Grid in Remote Client-Server mode. For Linux: For Windows: Report a bug 1.3.2. Library Mode Library mode allows building and deploying a custom runtime environment. The Library mode hosts a single data grid node in the applications process, with remote access to nodes hosted in other JVMs. Tested containers for Red Hat JBoss Data Grid 6 Library mode includes Red Hat JBoss Enterprise Web Server 2.x and JBoss Enterprise Application Platform 6.x. A number of features in JBoss Data Grid can be used in Library mode, but not in Remote Client-Server mode. The following features require Library mode: transactions listeners and notifications JBoss Data Grid can also be run as a standalone application in Java SE. Standalone mode is a supported alternative to running JBoss Data Grid in a container. Report a bug

Commands:
USDJBOSS_HOME/bin/standalone.sh
USDJBOSS_HOME\bin\standalone.bat
B.37. kdenetwork B.37.1. RHSA-2011:0465 - Important: kdenetwork security update Updated kdenetwork packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. The kdenetwork packages contain networking applications for the K Desktop Environment (KDE). CVE-2011-1586 A directory traversal flaw was found in the way KGet, a download manager, handled the "file" element in Metalink files. An attacker could use this flaw to create a specially-crafted Metalink file that, when opened, would cause KGet to overwrite arbitrary files accessible to the user running KGet. Users of kdenetwork should upgrade to these updated packages, which contain a backported patch to resolve this issue. The desktop must be restarted (log out, then log back in) for this update to take effect.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ C++ in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To install packages on Red Hat Enterprise Linux, you must register your system . To build programs using AMQ C++ on Red Hat Enterprise Linux, you must install the gcc-c++ , cmake , and make packages. To build programs using AMQ C++ on Microsoft Windows, you must install Visual Studio. 2.2. Installing on Red Hat Enterprise Linux Procedure Use the subscription-manager command to subscribe to the required package repositories. Replace <version> with 2 for the main release stream or 2.9 for the long term support release stream. If necessary, replace <variant> with the value for your variant of Red Hat Enterprise Linux (for example, server or workstation ). Red Hat Enterprise Linux 7 USD sudo subscription-manager repos --enable=amq-clients- <version> -for-rhel-7- <variant> -rpms Red Hat Enterprise Linux 8 USD sudo subscription-manager repos --enable=amq-clients- <version> -for-rhel-8-x86_64-rpms Use the yum command to install the qpid-proton-cpp-devel and qpid-proton-cpp-docs packages. USD sudo yum install qpid-proton-cpp-devel qpid-proton-cpp-docs For more information about using packages, see Appendix B, Using Red Hat Enterprise Linux packages . 2.3. Installing on Microsoft Windows Procedure Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Clients entry in the INTEGRATION AND AUTOMATION category. Click Red Hat AMQ Clients . The Software Downloads page opens. Download the AMQ Clients 2.10.0 C++ .zip file. Extract the file contents into a directory of your choosing by right-clicking on the zip file and selecting Extract All . When you extract the contents of the .zip file, a directory named amq-clients-2.10.0-cpp-win is created. This is the top-level directory of the installation and is referred to as <install-dir> throughout this document.

Commands:
sudo subscription-manager repos --enable=amq-clients- <version> -for-rhel-7- <variant> -rpms
sudo subscription-manager repos --enable=amq-clients- <version> -for-rhel-8-x86_64-rpms
sudo yum install qpid-proton-cpp-devel qpid-proton-cpp-docs