mtpti5iD/redhat-docs_dataset huggingface dataset:
Visualizing your costs using cost explorer Cost Management Service 1-latest Use Cost Explorer to visualize and understand your costs Red Hat Customer Content Services

Commands:
The cloud integration still bills you for the USD60 dollars, but {product-title} can only attribute USD20 to Project A based off how much they requested. The remaining USD40 is assigned to the *Unattributed Storage* project. {product-title-up} calculates the remaining portion of that disk with the following equation. In this example, the cost is USD20:
Chapter 32. Downloading the Red Hat Process Automation Manager installation files You can use the installer JAR file or deployable ZIP files to install Red Hat Process Automation Manager. You can run the installer in interactive or command line interface (CLI) mode. Alternatively, you can extract and configure the Business Central and KIE Server deployable ZIP files. If you want to run Business Central without deploying it to an application server, download the Business Central Standalone JAR file. Download a Red Hat Process Automation Manager distribution that meets your environment and installation requirements. Note Red Hat Decision Manager is a subset of Red Hat Process Automation Manager. You must install Red Hat Process Automation Manager in order to use Red Hat Decision Manager. Procedure Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options: Product: Process Automation Manager Version: 7.13.5 Download one of the following product distributions, depending on your preferred installation method: Note You only need to download one of these distributions. If you want to use the installer to install Red Hat Process Automation Manager on Red Hat JBoss Web Server, download Red Hat Process Automation Manager 7.13.5 Installer ( rhpam-installer-7.13.5.jar ). The installer graphical user interface guides you through the installation process. To install KIE Server on Red Hat JBoss Web Server using the deployable ZIP file, download the Red Hat Process Automation Manager 7.13.5 Add Ons ( rhpam-7.13.5-add-ons.zip ) file. The ZIP file does not require a graphical user interface. To run Business Central without needing to deploy it to an application server, download Red Hat Process Automation Manager 7.13.5 Business Central Standalone ( rhpam-7.13.5-business-central-standalone.jar ).

Commands:
7.160. ntp 7.160.1. RHBA-2013:0495 - ntp bug fix update Updated ntp packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Network Time Protocol (NTP) is used to synchronize a computer's time with a referenced time source. Bug Fix BZ# 875798 When at least one system network interface had an IPv6 address and the network service was stopped or started, the ntpd daemon could terminate unexpectedly. This happened if the ntpd service attempted to read the device addresses at the moment when the network service had managed to configure only the IPv6 address of the first device. With this update, the underlying library function has been fixed and the daemon no longer crashes in the scenario described. All users of ntp are advised to upgrade to these updated packages, which fix this bug.

Commands:
6.7.5. Testing the Fence Configuration As of Red Hat Enterprise Linux Release 6.4, you can test the fence configuration for each node in a cluster with the fence_check utility. The following example shows the output of a successful execution of this command. For information on this utility, see the fence_check (8) man page.

Commands:
fence_check fence_check run at Wed Jul 23 09:13:57 CDT 2014 pid: 4769 Testing host-098 method 1: success Testing host-099 method 1: success Testing host-100 method 1: success
5.152. libibverbs-rocee and libmlx4-rocee 5.152.1. RHEA-2012:0977 - libibverbs-rocee and libmlx4-rocee bug fix update Updated libibverbs-rocee and libmlx4-rocee packages that fix one bug are now available for Red Hat Enterprise Linux High Performance Network. The libibverbs-rocee packages provide a library to enable userspace processes to use RDMA over Converged Ethernet (RoCE) "verbs" acording to the InfiniBand Architecture Specification and the RoCE Protocol Verbs Specification. The libmlx4-rocee packages provide a device-specific driver for Mellanox ConnectX InfiniBand host channel adapters (HCAs) for the libibverbs-rocee library. Bug Fix BZ# 805717 Prior to this update, running modprobe could, under certain circumstances, cause an infinite loop. As a consequence, the system ran out of processes and required a restart to recover. This update modifies the underlying code so that an incorrect configuration of options in the /etc/modprobe.d/libmlx4.conf file no longer requires to restart the system. Note This package is a dependency of the RDMA package and both packages have to be updated together. All users who require RDMA are advised to upgrade to these updated packages which fix this bug.

Commands:
6. Driver Updates 6.1. All Architectures Bugzilla #452846 The Intel(R) High Definition Audio (HDA) driver in ALSA has been updated. This update improves audio support for newer hardware with HDA integrated audio. Bugzilla #479408 Previously, network devices using the forcedeth driver may have stopped responding while doing rcp command from multiple clients. With this update, the forcedeth driver has been updated, which resolves this issue. Bugzilla #441707 Previously, the Automatic Direct Memory Access (ADMA) mode was enabled by default in the sata_nv driver. Consequently, device errors and timeouts may have been encountered with some devices that utilize the sata_nv driver. With this update, ADMA mode is now disabled by default, which resolves this issue. Bugzilla #446215 The drivers for virtio , the platform for I/O virtualization in KVM, has been backported to Red Hat Enterprise Linux 4.8 from Linux Kernel 2.6.27. These drivers will enable KVM guests to achieve higher levels of I/O performance. Various user space components such as: anaconda , kudzu , lvm , selinux and mkinitrd have also been updated to support virtio devices. Bugzilla #451966 The r8169 driver has been updated to provide support for newer network chipsets. With this update, all variants of RTL810x/RTL8168(9) are now supported in Red Hat Enterprise Linux 4.8. Bugzilla #452163 The mptsas driver has been updated to version 3.12.29.00. This update includes bug fixes and enables the following new features: Dual Port support. SAS chip Power Management. Bugzilla #452271 The lpfc driver has been updated to version number to 8.0.16.46. This update applies several bug fixes and enhancements, including: support for FCoE LP21000 HBAs support for HBAnyware 4.0 Bugzilla #455297 The megaraid_sas driver for SAS based RAID controllers has been updated to version 4.01-RH1. Several bug fixes and improvements are applied by this update, including: Added support for the LSI Generation 2 Controllers (0078, 0079) Added a command to shutdown DCMD in the shutdown routine to improve firmware shutdown. A bug that caused unexpected interrupts in the hardware Linux driver has been fixed. Bugzilla #454838 The eHEA ethernet device driver for IBM eServer System P has been updated to version 0078-08. Bugzilla #490503 The EHCA infinband device driver will not be supported for Red Hat Enterprise Linux 4.8 and all future Red Hat Enterprise Linux 4 releases.

Commands:
Red Hat Virtualization Upgrade Overview This guide explains how to upgrade the following environments to Red Hat Virtualization 4.3 or 4.4 : Self-hosted engine, local database : Both the Data Warehouse database and the Manager database are installed on the Manager. Standalone manager, local database : Both the Data Warehouse database and the Manager database are installed on the Manager. Standalone manager, remote database : Either the Data Warehouse database or the Manager database, or both, are on a separate machine. Note For a checklist of upgrade instructions, you can use the RHV Upgrade Helper . This application asks you to fill in a checklist for your upgrade path and current environment, and presents the applicable upgrade steps. Important Plan any necessary downtime in advance. After you update the clusters' compatibility versions during the upgrade, a new hardware configuration is automatically applied to each virtual machine once it reboots. You must reboot any running or suspended VMs as soon as possible to apply the configuration changes. Select the appropriate instructions for your environment from the following table. If your Manager and host versions differ (if you have previously upgraded the Manager but not the hosts), follow the instructions that match the Manager's version. Table 1. Supported Upgrade Paths Current Manager version Target Manager version Relevant section 4.3 4.4 Self-hosted engine, local database environment: Upgrading a self-Hosted engine from Red Hat Virtualization 4.3 to 4.4 Local database environment - Upgrading from Red Hat Virtualization 4.3 to 4.4 Remote database environment: Upgrading a Remote Database Environment from Red Hat Virtualization 4.3 to 4.4 4.2 4.3 Self-hosted engine, local database environment: Upgrading a Self-Hosted Engine from Red Hat Virtualization 4.2 to 4.3 Local database environment: Upgrading from Red Hat Virtualization 4.2 to 4.3 Remote database environment: Upgrading a Remote Database Environment from Red Hat Virtualization 4.2 to 4.3

Commands:
Chapter 4. Knative CLI for use with OpenShift Serverless The Knative ( kn ) CLI enables simple interaction with Knative components on OpenShift Container Platform. 4.1. Key features The Knative ( kn ) CLI is designed to make serverless computing tasks simple and concise. Key features of the Knative CLI include: Deploy serverless applications from the command line. Manage features of Knative Serving, such as services, revisions, and traffic-splitting. Create and manage Knative Eventing components, such as event sources and triggers. Create sink bindings to connect existing Kubernetes applications and Knative services. Extend the Knative CLI with flexible plugin architecture, similar to the kubectl CLI. Configure autoscaling parameters for Knative services. Scripted usage, such as waiting for the results of an operation, or deploying custom rollout and rollback strategies. 4.2. Installing the Knative CLI See Installing the Knative CLI .

Commands:
Chapter 1. Configuring accounts for RHEL AI There are a few accounts you need to set up before interacting with RHEL AI. Creating a Red Hat account You can create a Red Hat account by registering on the Red Hat website. You can follow the procedure in Register for a Red Hat account . Creating a Red Hat registry account Before you can download models from the Red Hat registry, you need to create a registry account and login using the CLI. You can view your account username and password by selecting the Regenerate Token button on the webpage. You can create a Red Hat registry account by selecting the New Service Account button on the Registry Service Accounts page. There are several ways you can log into your registry account via the CLI. Follow the procedure in Red Hat Container Registry authentication to login on your machine. Configuring Red Hat Insights for hybrid cloud deployments Red Hat Insights is an offering that gives you visibility to the environments you are deploying. This platform can also help identify operational and vulnerability risks in your system. For more information about Red Hat Insights, see Red Hat Insights data and application security . You can create a Red Hat Insights account using an activation key and organization parameters by following the procedure in Viewing an activation key . You can then configure your account on your machine by running the following command: USD rhc connect --organization <org id> --activation-key <created key> To run RHEL AI in a disconnected environment, or opt out of Red Hat Insights, run the following commands: USD sudo mkdir -p /etc/ilab USD sudo touch /etc/ilab/insights-opt-out

Commands:
rhc connect --organization <org id> --activation-key <created key>
sudo mkdir -p /etc/ilab sudo touch /etc/ilab/insights-opt-out
Chapter 4. Verifying permissions of IdM configuration files using Healthcheck Learn more about how to test Identity Management (IdM) configuration files using the Healthcheck tool. For details, see Healthcheck in IdM . Prerequisites The Healthcheck tool is only available on RHEL 8.1 or newer systems. 4.1. File permissions Healthcheck tests The Healthcheck tool tests ownership and permissions of some important files installed or configured by Identity Management (IdM). If you change the ownership or permissions of any tested file, the test returns a warning in the result section. While it does not necessarily mean that the configuration will not work, it means that the file differs from the default configuration. To see all tests, run the ipa-healthcheck with the --list-sources option: You can find the file permissions test under the ipahealthcheck.ipa.files source: IPAFileNSSDBCheck This test checks the 389-ds NSS database and the Certificate Authority (CA) database. The 389-ds database is located in /etc/dirsrv/slapd-<dashed-REALM> and the CA database is located in /etc/pki/pki-tomcat/alias/ . IPAFileCheck This test checks the following files: /var/lib/ipa/ra-agent.{key|pem} /var/lib/ipa/certs/httpd.pem /var/lib/ipa/private/httpd.key /etc/httpd/alias/ipasession.key /etc/dirsrv/ds.keytab /etc/ipa/ca.crt /etc/ipa/custodia/server.keys If PKINIT is enabled: /var/lib/ipa/certs/kdc.pem /var/lib/ipa/private/kdc.key If DNS is configured: /etc/named.keytab /etc/ipa/dnssec/ipa-dnskeysyncd.keytab TomcatFileCheck This test checks some tomcat-specific files if a CA is configured: /etc/pki/pki-tomcat/password.conf /var/lib/pki/pki-tomcat/conf/ca/CS.cfg /etc/pki/pki-tomcat/server.xml Note Run these tests on all IdM servers when trying to find issues. 4.2. Screening configuration files using Healthcheck Follow this procedure to run a standalone manual test of an Identity Management (IdM) server's configuration files using the Healthcheck tool. The Healthcheck tool includes many tests. Results can be narrowed down by: Excluding all successful test: --failures-only Including only ownership and permissions tests: --source=ipahealthcheck.ipa.files Procedure To run Healthcheck tests on IdM configuration file ownership and permissions, while displaying only warnings, errors and critical issues, enter: A successful test displays empty brackets: Failed tests display results similar to the following WARNING : Additional resources See man ipa-healthcheck .

Commands:
ipa-healthcheck --list-sources
ipa-healthcheck --source=ipahealthcheck.ipa.files --failures-only
ipa-healthcheck --source=ipahealthcheck.ipa.files --failures-only []
{ "source": "ipahealthcheck.ipa.files", "check": "IPAFileNSSDBCheck", "result": "WARNING", "kw": { "key": "_etc_dirsrv_slapd-EXAMPLE-TEST_pkcs11.txt_mode", "path": "/etc/dirsrv/slapd-EXAMPLE-TEST/pkcs11.txt", "type": "mode", "expected": "0640", "got": "0666", "msg": "Permissions of /etc/dirsrv/slapd-EXAMPLE-TEST/pkcs11.txt are 0666 and should be 0640" } }
5.5.3. Deleting a Member from a DLM Cluster To delete a member from an existing DLM cluster that is currently in operation, follow these steps: At one of the running nodes (not at a node to be deleted), start system-config-cluster (refer to Section 5.2, "Starting the Cluster Configuration Tool " ). At the Cluster Status Tool tab, under Services , disable or relocate each service that is running on the node to be deleted. Stop the cluster software on the node to be deleted by running the following commands at that node in this order: service rgmanager stop , if the cluster is running high-availability services ( rgmanager ) service gfs stop , if you are using Red Hat GFS service clvmd stop , if CLVM has been used to create clustered volumes service fenced stop service cman stop service ccsd stop At system-config-cluster (running on a node that is not to be deleted), in the Cluster Configuration Tool tab, delete the member as follows: If necessary, click the triangle icon to expand the Cluster Nodes property. Select the cluster node to be deleted. At the bottom of the right frame (labeled Properties ), click the Delete Node button. Clicking the Delete Node button causes a warning dialog box to be displayed requesting confirmation of the deletion ( Figure 5.7, "Confirm Deleting a Member" ). Figure 5.7. Confirm Deleting a Member At that dialog box, click Yes to confirm deletion. Propagate the updated configuration by clicking the Send to Cluster button. (Propagating the updated configuration automatically saves the configuration.) Stop the cluster software on the remaining running nodes by running the following commands at each node in this order: service rgmanager stop , if the cluster is running high-availability services ( rgmanager ) service gfs stop , if you are using Red Hat GFS service clvmd stop , if CLVM has been used to create clustered volumes service fenced stop service cman stop service ccsd stop Start cluster software on all remaining cluster nodes by running the following commands in this order: service ccsd start service cman start service fenced start service clvmd start , if CLVM has been used to create clustered volumes service gfs start , if you are using Red Hat GFS service rgmanager start , if the cluster is running high-availability services ( rgmanager ) At system-config-cluster (running on a node that was not deleted), in the Cluster Configuration Tool tab, verify that the configuration is correct. At the Cluster Status Tool tab verify that the nodes and services are running as expected. Note Make sure to configure other parameters that may be affected by changes in this section. Refer to Section 5.1, "Configuration Tasks" .

Commands:
Chapter 31. Installing Through VNC The Red Hat Enterprise Linux installer ( anaconda ) offers you two interactive modes of operation. The original mode is a text-based interface. The newer mode uses GTK+ and runs in the X Window environment. This chapter explains how you can use the graphical installation mode in environments where the system lacks a proper display and input devices typically associated with a workstation. This scenario is typical of systems in datacenters, which are often installed in a rack environment and do not have a display, keyboard, or mouse. Additionally, a lot of these systems even lack the ability to connect a graphical display. Given that enterprise hardware rarely needs that ability at the physical system, this hardware configuration is acceptable. Even in these environments, however, the graphical installer remains the recommended method of installation. The text mode environment lacks a lot of capabilities found in the graphical mode. Many users still feel that the text mode interface provides them with additional power or configuration ability not found in the graphical version. The opposite is true. Much less development effort is put in to the text-mode environment and specific things (for example, LVM configuration, partition layout, package selection, and bootloader configuration) are deliberately left out of the text mode environment. The reasons for this are: Less screen real estate for creating user interfaces similar to those found in the graphical mode. Difficult internationalization support. Desire to maintain a single interactive installation code path. Anaconda therefore includes a Virtual Network Computing (VNC) mode that allows the graphical mode of the installer to run locally, but display on a system connected to the network. Installing in VNC mode provides you with the full range of installation options, even in situations where the system lacks a display or input devices. 31.1. VNC Viewer Performing a VNC installation requires a VNC viewer running on your workstation or other terminal computer. Locations where you might want a VNC viewer installed: Your workstation Laptop on a datacenter crash cart VNC is open source software licensed under the GNU General Public License. VNC clients are available in the repositories of most Linux distributions. Use your package manager to search for a client for your chosen distribution. For example, on Red Hat Enterprise Linux, install the tigervnc package: Once you have verified you have a VNC viewer available, it's time to start the installation.

Commands:
yum install tigervnc
Chapter 4. The Migration Toolkit for Applications tools You can use the following Migration Toolkit for Applications (MTA) tools for assistance in the various stages of your migration and modernization efforts: User interface Migration Toolkit for Applications Operator CLI IDE add-ons for the following applications: Eclipse Visual Studio Code, Visual Studio Codespaces, and Eclipse Che IntelliJ IDEA Maven plugin Review the details of each tool to determine which tool is suitable for your project. 4.1. The MTA Operator By using the Migration Toolkit for Applications Operator, you can install the user interface on OpenShift Container Platform versions 4.13-4.15. For more information about the prerequisites for the MTA Operator installation, see OpenShift Operator Life Cycles . 4.2. The MTA user interface By using the user interface for the Migration Toolkit for Applications, you can perform the following tasks: Assess the risks involved in containerizing an application for hybrid cloud environments on Red Hat OpenShift. Analyze the changes that must be made in the code of an application to containerize the application. 4.3. The MTA CLI The CLI is a command-line tool in the Migration Toolkit for Applications that you can use to assess and prioritize migration and modernization efforts for applications. It provides numerous reports that highlight the analysis without using the other tools. The CLI includes a wide array of customization options. By using the CLI, you can tune MTA analysis options or integrate with external automation tools. For more information about using the CLI, see CLI Guide . 4.4. The MTA IDE add-ons You can migrate and modernize applications by using the Migration Toolkit for Applications (MTA) add-ons for the following applications: Eclipse Visual Studio Code, Visual Studio Codespaces, and Eclipse Che IntelliJ IDEA, both the Community and Ultimate versions You can use these add-on to perform the following tasks: Analyze your projects by using customizable sets of rules. Mark issues in the source code. Fix the issues by using the provided guidance. Use the automatic code replacement, if possible.

Commands:
3. Related Documentation For more information about using Red Hat Enterprise Linux 6, see the following resources: Installation Guide - Documents relevant information regarding the installation of Red Hat Enterprise Linux 6. Deployment Guide - Documents relevant information regarding the deployment, configuration and administration of Red Hat Enterprise Linux 6. Storage Administration Guide - Provides instructions on how to effectively manage storage devices and file systems on Red Hat Enterprise Linux 6. For more information about Red Hat Enterprise Linux 6, see the following resources: High Availability Add-On Overview - Provides a high-level overview of the Red Hat High Availability Add-On. Cluster Administration - Provides information about installing, configuring and managing the High Availability Add-On. Logical Volume Manager Administration - Provides a description of the Logical Volume Manager (LVM), including information on running LVM in a clustered environment. Global File System 2: Configuration and Administration - Provides information about installing, configuring, and maintaining Red Hat GFS2 (Red Hat Global File System 2). Load Balancer Administration - Provides information on configuring high-performance systems and services with the Load Balancer Add-On, a set of integrated software components that provide Linux Virtual Servers (LVS) for balancing IP load across a set of real servers. Release Notes - Provides information about the current release of Red Hat products. Red Hat documents are available in HTML, PDF, and RPM versions on the Red Hat Enterprise Linux Documentation CD and online at https://access.redhat.com/site/documentation/ .

Commands: