mtpti5iD/redhat-docs_dataset huggingface dataset:
13.2. Planning Overview When the query engine receives an incoming SQL query it performs the following operations. Parsing - syntax is validated and converted to internal form. Resolving - all identifiers are linked to metadata, and functions are linked to the function library. Validating - SQL semantics are validated based on metadata references and type signatures. Rewriting - SQL is rewritten to simplify expressions and criteria. Logical plan optimization - the rewritten canonical SQL is converted into a logical plan for in-depth optimization. The JBoss Data Virtualization optimizer is predominantly rule-based. Based upon the query structure and hints, a certain rule set will be applied. These rules may in turn trigger the execution of more rules. Within several rules, JBoss Data Virtualization also takes advantage of costing information. The logical plan optimization steps can be seen by using the SHOWPLAN DEBUG clause and are described in Section 13.9.1, "Query Planner" . Processing plan conversion - the logic plan is converted into an executable form where the nodes are representative of basic processing operations. The final processing plan is displayed as the query plan. See Section 13.8.1, "Query Plans" . The logical query plan is a tree of operations used to transform data in source tables to the expected result set. In the tree, data flows from the bottom (tables) to the top (output). The primary logical operations and their SQL equivalents are: select - select or filter rows based on a criteria, project - project or compute column values, join , source - retrieve data from a table, sort - ORDER BY, duplicate removal - SELECT DISTINCT, group - GROUP BY, and union - UNION.

Commands:
Appendix A. Using your subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the AMQ Streams for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Revised on 2022-04-26 10:32:02 UTC

Commands:
Chapter 56. BrokerCapacityOverride schema reference Used in: BrokerCapacity Property Description brokers List of Kafka brokers (broker identifiers). integer array cpu Broker capacity for CPU resource in cores or millicores. For example, 1, 1.500, 1500m. For more information on valid CPU resource units see https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-cpu . string inboundNetwork Broker capacity for inbound network throughput in bytes per second. Use an integer value with standard OpenShift byte units (K, M, G) or their bibyte (power of two) equivalents (Ki, Mi, Gi) per second. For example, 10000KiB/s. string outboundNetwork Broker capacity for outbound network throughput in bytes per second. Use an integer value with standard OpenShift byte units (K, M, G) or their bibyte (power of two) equivalents (Ki, Mi, Gi) per second. For example, 10000KiB/s. string

Commands:
Chapter 1. Introduction This document describes how to configure OpenStack to use one or more Dell EMC PS Series back ends. It also includes instructions on addressing volume size discrepancies between Dell EMC PS Series devices and the OpenStack Block Storage service. The following sections assume that: You intend to use only Dell EMC PS Series devices and drivers for Block Storage back ends The OpenStack Overcloud has already been deployed through Director, with a properly-functional Block Storage service The Dell storage device has already been deployed and configured as a storage repository A Dell EMC PS Series Group is already deployed and accessible through SSH You have the necessary credentials for connecting to the Group manager of the available Dell EMC PS Series Group (namely, CHAP and Group manager credentials) You have the username and password of an account with elevated privileges. You can use the same account that was created to deploy the Overcloud; in Creating a Director Installation User , we create and use the stack user for this purpose. When RHEL OpenStack Platform is deployed through the Director, all major Overcloud settings (in particular, the Block Storage service back end) must be defined and orchestrated through the Director as well. This ensures that the settings will persist through any further Overcloud updates. For more information about deploying OpenStack through the Director, see Director Installation and Usage . The purpose of this document is to explain how to orchestrate your desired Dell EqualLogic back end configuration to the Overcloud's Block Storage service. This document will not discuss the different deployment configurations possible with the back end. Rather, to learn more about the different available deployment configurations, see your device's product documentation. Once you are familiar with the resulting back end configuration you want to deploy (and its corresponding settings), refer to this document for instructions on how to orchestrate it through the Director. Note At present, the Director only has the integrated components to deploy a single instance of a Dell EqualLogic back end. As such, this document only describes the deployment of a single back end. Deploying multiple instances of a Dell EqualLogic back end requires a custom back end configuration . See the Custom Block Storage Back End Deployment Guide for instructions.

Commands:
4.2. Basic Requirements and Setup To set up a KVM virtual machine on Red Hat Enterprise Linux 6, your system must meet the following criteria: Architecture Virtualization with the KVM hypervisor is currently only supported on Intel 64 and AMD64 systems. Disk space and RAM Minimum: 6 GB free disk space 2 GB RAM Customer Portal subscription To install virtualization packages, your host machine must be registered and subscribed to the Red Hat Customer Portal. To register run the subscription-manager register command and follow the prompts. Alternatively, run the Red Hat Subscription Manager application from Applications System Tools on the desktop to register. If you do not have a valid Red Hat subscription, visit the Red Hat online store to obtain one. For more information on registering and subscribing a system to the Red Hat Customer Portal, see https://access.redhat.com/solutions/253273 . Required packages Before you can use virtualization, a basic set of virtualization packages must be installed on your computer. Procedure 4.1. Installing the virtualization packages with yum To use virtualization on Red Hat Enterprise Linux the libvirt , qemu-kvm and qemu-img packages must be installed. These packages provide the user-level KVM emulator and disk image manager on the host system. Install the qemu-kvm , qemu-img , libvirt , and virt-manager packages with the following command: Download a Red Hat Enterprise Linux 7 Workstation binary DVD ISO image from the Red Hat Customer Portal . This image will be used to install the guest virtual machine's operating system. Note If you encounter any problems during the installation process, see the Troubleshooting section of the Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide .

Commands:
yum install qemu-kvm qemu-img libvirt virt-manager
5.3. Unable to open /etc/scl/prefixes/software_collection_name This error message can be caused by using incorrect arguments with the scl command you are calling. Check the scl command is correct and that you have not mistyped any of the arguments. The same error message can also be caused by a missing Software Collection. Ensure that the software_collection_name Software Collection is properly installed on the system. For more information, see Section 1.5, "Listing Installed Software Collections" .

Commands:
Chapter 3. Analyzing your projects with the MTA plugin You can analyze your projects with the MTA plugin by creating a run configuration and running an analysis. 3.1. Creating a run configuration You can create multiple run configurations to run against each project you import to IntelliJ IDEA. Procedure In the Projects view, click the project you want to analyze. On the left side of the screen, click the Migration Toolkit for Applications tab. If this is your first configuration, the run configuration panel is displayed on the right. If this is not your first configuration, right-click configuration in the list and select New configuration . The run configuration panel is displayed on the right. Complete the following configuration fields: cli : Enter the path to the cli executable. For example: USDHOME/mta-cli-7.2.1.GA-redhat/bin/mta-cli . Input : Click Add and enter the input file or directory. Target : Select one or more target migration paths. Note The location shown in the Output is set by the plugin. In the list of configurations, right-click the new configuration and select Run Analysis . The Console (MTA) terminal emulator opens, displaying information about the progress of the analysis. When the analysis is completed, you can click either Report or Results below the name of the configuration file you ran. Reports opens the MTA report, which describes any issues you need to address before you migrate or modernize your application. For more information, see Reviewing the reports in the CLI Guide . Results opens a directory displaying hints (issues) per application.

Commands:
6.4. Removing a Virtual Machine Important The Remove button is disabled while virtual machines are running; you must shut down a virtual machine before you can remove it. Removing Virtual Machines Click Compute Virtual Machines and select the virtual machine to remove. Click Remove . Optionally, select the Remove Disk(s) check box to remove the virtual disks attached to the virtual machine together with the virtual machine. If the Remove Disk(s) check box is cleared, then the virtual disks remain in the environment as floating disks. Click OK .

Commands:
Chapter 1. Understanding your cloud deployment options You can install OpenShift Dedicated on Amazon Web Services (AWS) or Google Cloud Platform (GCP) using a cloud account that you own or using a cloud account that is owned by Red Hat. This document provides details about the cloud deployment options for OpenShift Dedicated clusters. 1.1. Overview of the OpenShift Dedicated cloud deployment options OpenShift Dedicated offers OpenShift Container Platform clusters as a managed service on Amazon Web Services (AWS) or Google Cloud Platform (GCP). Through the Customer Cloud Subscription (CCS) model, you can deploy clusters in an existing AWS or GCP cloud account that you own. Alternatively, you can install OpenShift Dedicated in a cloud account that is owned by Red Hat. 1.1.1. Deploying clusters using the Customer Cloud Subscription (CCS) model The Customer Cloud Subscription (CCS) model enables you to deploy Red Hat managed OpenShift Dedicated clusters in an existing Amazon Web Services (AWS) or Google Cloud Platform (GCP) account that you own. Red Hat requires several prerequisites be met in order to provide this service, and this service is supported by Red Hat Site Reliability Engineers (SRE). In the CCS model, the customer pays the cloud infrastructure provider directly for cloud costs, and the cloud infrastructure account is part of an organization owned by the customer, with specific access granted to Red Hat. In this model, the customer pays Red Hat for the CCS subscription and pays the cloud provider for the cloud costs. By using the CCS model, you can use the services that are provided by your cloud provider, in addition to the services provided by Red Hat. 1.1.2. Deploying clusters in Red Hat cloud accounts As an alternative to the CCS model, you can deploy OpenShift Dedicated clusters in AWS or GCP cloud accounts that are owned by Red Hat. With this model, Red Hat is responsible for the cloud account and the cloud infrastructure costs are paid directly by Red Hat. The customer only pays the Red Hat subscription costs. 1.2. steps Creating an OpenShift Dedicated cluster 1.3. Additional resources For more information about using Customer Cloud Subscriptions on GCP, see Understanding Customer Cloud Subscriptions on GCP . For more information about using Customer Cloud Subscriptions on AWS, see Understanding Customer Cloud Subscriptions on AWS .

Commands:
A.3. Investigating IdM Web UI Authentication Failures Make sure the user can authenticate from the command line using the kinit utility. If the authentication fails, see also Section A.2, "Investigating kinit Authentication Failures" . Make sure that the httpd and dirsrv services on the affected server are running: Make sure no related SELinux Access Vector Cache (AVC) messages are logged in the /var/log/audit/audit.log and /var/log/messages files. See Basic SELinux Troubleshooting in CLI in the Red Hat Knowledgebase for details on resolving AVC messages. Make sure that cookies are enabled on the browser from which you are authenticating. Make sure that the time difference between the IdM server and the system on which you are authenticating is 5 minutes at the most. Review the Apache error log: /var/log/httpd/error_log . Enable verbose logging for the authentication process to help diagnose the problem. See Troubleshooting Firefox Kerberos Configuration in the System-Level Authentication Guide for advice on how to enable verbose logging in Firefox. If you are having problems when logging in using certificates: In the /etc/httpd/conf.d/nss.conf file, change the LogLevel attribute to info . Restart the Apache server: Try logging in with the certificate again. Review the Apache error log: /var/log/httpd/error_log . The log shows messages recorded by the mod_lookup_identity module, including information about whether the module successfully matched the user during the login attempt or not. Related Information See Section C.2, "Identity Management Log Files and Directories" for descriptions of various Identity Management log files.

Commands:
systemctl status httpd.service # systemctl status dirsrv@ IPA-EXAMPLE-COM .service
systemctl restart httpd
3.2. Importing a GNBD on a Client The gnbd.ko kernel module must be loaded on a node before it can import GNBDs. When GNBDs are imported, device nodes are created for them in /dev/gnbd/ with the name assigned when they were exported. Usage Server Specifies a GNBD server by hostname or IP address from which to import GNBDs. All GNBDs exported from the server are imported on the client running this command. Example This example imports all GNBDs from the server named nodeA .

Commands:
gnbd_import -i Server
gnbd_import -i nodeA
3.6. Virtual Networking A virtual guest's connection to any network uses the software network components of the physical host. These software components can be rearranged and reconfigured by using libvirt 's virtual network configuration. The host therefore acts as a virtual network switch , which can be configured in a number of different ways to fit the guest's networking needs. By default, all guests on a single host are connected to the same libvirt virtual network, named default . Guests on this network can make the following connections: With each other and with the virtualization host Both inbound and outbound traffic is possible, but is affected by the firewalls in the guest operating system's network stack and by libvirt network filtering rules attached to the guest interface. With other hosts on the network beyond the virtualization host Only outbound traffic is possible, and is affected by Network Address Translation (NAT) rules, as well as the host system's firewall. However, if needed, guest interfaces can instead be set to one of the following modes: Isolated mode The guests are connected to a network that does not allow any traffic beyond the virtualization host. Routed mode The guests are connected to a network that routes traffic between the guest and external hosts without performing any NAT. This enables incoming connections but requires extra routing-table entries for systems on the external network. Bridged mode The guests are connected to a bridge device that is also connected directly to a physical ethernet device connected to the local ethernet. This makes the guest directly visible on the physical network, and thus enables incoming connections, but does not require any extra routing-table entries. For basic outbound-only network access from virtual machines, no additional network setup is usually needed, as the default network is installed along with the libvirt package, and automatically started when the libvirtd service is started. If more advanced functionality is needed, additional networks can be created and configured using either virsh or virt-manager , and the guest XML configuration file can be edited to use one of these new networks. Note For information on advanced virtual network settings, see the Red Hat Enterprise Linux 7 Virtualization Deployment and Administration Guide . From the point of view of the guest operating system, a virtual network connection is the same as a normal physical network connection. For further information on configuring networks in Red Hat Enterprise Linux 7 guests, see the Red Hat Enterprise Linux 7 Networking Guide .

Commands:
9.6. Additional Resources Administering an NFS server can be a challenge. Many options, including quite a few not mentioned in this chapter, are available for exporting or mounting NFS shares. Consult the following sources for more information. 9.6.1. Installed Documentation /usr/share/doc/nfs-utils- <version-number> / - Replace <version-number> with the version number of the NFS package installed. This directory contains a wealth of information about the NFS implementation for Linux, including a look at various NFS configurations and their impact on file transfer performance. man mount - Contains a comprehensive look at mount options for both NFS server and client configurations. man fstab - Gives details for the format of the /etc/fstab file used to mount file systems at boot-time. man nfs - Provides details on NFS-specific file system export and mount options. man exports - Shows common options used in the /etc/exports file when exporting NFS file systems.

Commands:
Chapter 7. Hardware Enablement Support for Intel Wildcat Point-LP PCH Broadwell-U PCH SATA, HD Audio, TCO Watchdog, and I2C (SMBus) device IDs have been added for the drivers, which enables support for the generation mobile platform in Red Hat Enterprise Linux 6.6. Intel Ethernet Server Adapter X710/XL710 Support Red Hat Enterprise Linux 6.6 adds the i40e and i40evf kernel drivers, which enable support for Intel X710 and XL710 family Ethernet adapters. These drivers are provided as Technology Preview only.

Commands:
Chapter 3. Device Drivers This chapter provides a comprehensive listing of all device drivers which were updated in Red Hat Enterprise Linux 6.5. Storage Drivers The Emulex be2iscsi driver has been upgraded to the latest upstream version. The megaraid_sas driver has been upgraded to version 6.600.18.00. The pm8001/pm80xx driver has been added in Red Hat Enterprise Linux 6.5 to add support for PMC-Sierra Adaptec Series 6H and 7H SAS/SATA HBA cards as well as PMC Sierra 8081, 8088, and 8089 chip based SAS/SATA controllers. 12Gbps SAS devices from LSI are now supported in Red Hat Enterprise Linux. The Brocade BFA driver has been updates to version 3.2.21.1. The NVMe driver has been added to Red Hat Enterprise Linux 6. Starting in Red Hat Enterprise Linux 6.4, iSCSI and FCoE boot on Broadcom devices is fully supported. These two features are provided by the bnx2i and bnx2fc Broadcom drivers. Network Drivers The Virtual Extensible LAN, vxlan , driver has been updated. Support for Single Root I/O virtualization (SR-IOV) has been added to the qlcnic driver as a Technology Preview. The Brocade BNA driver has been updated to version 3.1.2.1. The ixgbevf driver has been updated to the latest upstream version. The igbvf driver has been updated the to latest upstream version. The bnx2x driver has been updated to version 1.78.17-0. The Emulex be2net driver has been updated to version 4.6.x. The qlcnic driver has been updated to add support for the QLogic 83XX CNA adapter. The e1000e driver has been updated to the latest upstream version. The tg3 driver has been updated to include various bug fixes and new features, including hardware PTP support. The sfc driver has been upgraded to upstream version 3.2 and includes hardware accelerated receive flow steering (RFS). The igb driver has been updated to version 4.1.2 to include software time stamping support. The qlge driver has been updated to version 1.00.00.32. Miscellaneous Drivers The hpilo driver has been upgraded to the latest upstream version.

Commands:
18.9.3. Related Documentation Red Hat Linux Firewalls , by Bill McCarty; Red Hat Press - a comprehensive reference to building network and server firewalls using open source packet filtering technology such as Netfilter and iptables . It includes topics that cover analyzing firewall logs, developing firewall rules, and customizing your firewall using various graphical tools. Linux Firewalls , by Robert Ziegler; New Riders Press - contains a wealth of information on building firewalls using both 2.2 kernel ipchains as well as Netfilter and iptables . Additional security topics such as remote access issues and intrusion detection systems are also covered.

Commands:
Chapter 3. Repositories Red Hat Enterprise Linux 8 is distributed through two main repositories: BaseOS AppStream Both repositories are required for a basic RHEL installation, and are available with all RHEL subscriptions. Content in the BaseOS repository is intended to provide the core set of the underlying OS functionality that provides the foundation for all installations. This content is available in the RPM format and is subject to support terms similar to those in releases of RHEL. For a list of packages distributed through BaseOS, see the Package manifest . Content in the Application Stream repository includes additional user space applications, runtime languages, and databases in support of the varied workloads and use cases. Application Streams are available in the familiar RPM format, as an extension to the RPM format called modules , or as Software Collections. For a list of packages available in AppStream, see the Package manifest . In addition, the CodeReady Linux Builder repository is available with all RHEL subscriptions. It provides additional packages for use by developers. Packages included in the CodeReady Linux Builder repository are unsupported. For more information about RHEL 8 repositories, see the Package manifest .

Commands:
Chapter 22. Kernel kpatch , see the section called "Dynamic kernel Patching" crashkernel with more than one CPU, see the section called "Crashkernel with More than 1 CPU" dm-era device-mapper target, see the section called "dm-era Target" Cisco VIC kernel driver, see the section called "Cisco VIC kernel Driver" NFSoRDMA Available, see the section called "NFSoRDMA Available" Runtime Instrumentation for IBM System z, see the section called "Runtime Instrumentation for IBM System z" Cisco usNIC Driver, see the section called "Cisco usNIC Driver" Intel Ethernet Server Adapter X710/XL710 Driver Update, see the section called "Intel Ethernet Server Adapter X710/XL710 Driver Update"

Commands: