mtpti5iD/redhat-docs_dataset huggingface dataset:
29.6. Understanding /dev/oprofile/ The /dev/oprofile/ directory contains the file system for OProfile. Use the cat command to display the values of the virtual files in this file system. For example, the following command displays the type of processor OProfile detected: A directory exists in /dev/oprofile/ for each counter. For example, if there are 2 counters, the directories /dev/oprofile/0/ and dev/oprofile/1/ exist. Each directory for a counter contains the following files: count - The interval between samples. enabled - If 0, the counter is off and no samples are collected for it; if 1, the counter is on and samples are being collected for it. event - The event to monitor. extra - Used on machines with Nehalem processors to further specify the event to monitor. kernel - If 0, samples are not collected for this counter event when the processor is in kernel-space; if 1, samples are collected even if the processor is in kernel-space. unit_mask - Defines which unit masks are enabled for the counter. user - If 0, samples are not collected for the counter event when the processor is in user-space; if 1, samples are collected even if the processor is in user-space. The values of these files can be retrieved with the cat command. For example:

Commands:
~]# cat /dev/oprofile/cpu_type
~]# cat /dev/oprofile/0/count
7.6. Exporting Templates 7.6.1. Migrating Templates to the Export Domain Note The export storage domain is deprecated. Storage data domains can be unattached from a data center and imported to another data center in the same environment, or in a different environment. Virtual machines, floating virtual disks, and templates can then be uploaded from the imported storage domain to the attached data center. See the Importing Existing Storage Domains section in the Red Hat Virtualization Administration Guide for information on importing storage domains. Export templates into the export domain to move them to another data domain, either in the same Red Hat Virtualization environment, or another one. This procedure requires access to the Administration Portal. Exporting Individual Templates to the Export Domain Click Compute Templates and select a template. Click Export . Select the Force Override check box to replace any earlier version of the template on the export domain. Click OK to begin exporting the template; this may take up to an hour, depending on the virtual disk size and your storage hardware. Repeat these steps until the export domain contains all the templates to migrate before you start the import process. Click Storage Domains and select the export domain. Click the domain name to see the details view. Click the Template Import tab to view all exported templates in the export domain. 7.6.2. Copying a Template's Virtual Hard Disk If you are moving a virtual machine that was created from a template with the thin provisioning storage allocation option selected, the template's disks must be copied to the same storage domain as that of the virtual disk. This procedure requires access to the Administration Portal. Copying a Virtual Hard Disk Click Storage Disks . Select the template disk(s) to copy. Click Copy . Select the Target data domain from the drop-down list(s). Click OK . A copy of the template's virtual hard disk has been created, either on the same, or a different, storage domain. If you were copying a template disk in preparation for moving a virtual hard disk, you can now move the virtual hard disk.

Commands:
6.4. Configuration Examples 6.4.1. Dynamic DNS BIND allows hosts to update their records in DNS and zone files dynamically. This is used when a host computer's IP address changes frequently and the DNS record requires real-time modification. Use the /var/named/dynamic/ directory for zone files you want updated via dynamic DNS. Files created in or copied into /var/named/dynamic/ inherit Linux permissions that allow named to write to them. As such files are labeled with the named_cache_t type, SELinux allows named to write to them. If a zone file in /var/named/dynamic/ is labeled with the named_zone_t type, dynamic DNS updates may not be successful for a certain period of time as the update needs to be written to a journal first before being merged. If the zone file is labeled with the named_zone_t type when the journal attempts to be merged, an error such as the following is logged: Also, the following SELinux denial is logged: To resolve this labeling issue, run the restorecon -R -v /var/named/dynamic command as the Linux root user.

Commands:
named[PID]: dumping master file: rename: /var/named/dynamic/zone-name: permission denied
setroubleshoot: SELinux is preventing named (named_t) "unlink" to zone-name (named_zone_t)
Chapter 7. Quota management As a cloud administrator, you can set and manage quotas for a project. Each project is allocated resources, and project users are granted access to consume these resources. This enables multiple projects to use a single cloud without interfering with each other's permissions and resources. A set of resource quotas are preconfigured when a new project is created. The quotas include the amount of VCPUs, instances, RAM, and floating IPs that can be assigned to projects. You can set or modify Compute and Block Storage quotas for new and existing projects using the dashboard. For more information, see Managing projects . 7.1. Viewing Compute quotas for a project Run the following command to list the currently set quota values. Procedure Example

Commands:
openstack quota show [PROJECT-ID]
openstack quota show f0ba064c24ca4176ac55a45635ca561f +-----------------------+-------+ | Resource | Limit | +-----------------------+-------+ | cores | 20 | | instances | 10 | | ram | 51200 | | volumes | 10 | | snapshots | 10 | | gigabytes | 1000 | | backups | 10 | | volumes___DEFAULT__ | -1 | | gigabytes___DEFAULT__ | -1 | | snapshots___DEFAULT__ | -1 | | groups | 10 | | trunk | -1 | | networks | 100 | | ports | 500 | | rbac_policies | 10 | | routers | 10 | | subnets | 100 | | subnet_pools | -1 | | fixed-ips | -1 | | injected-file-size | 10240 | | injected-path-size | 255 | | injected-files | 5 | | key-pairs | 100 | | properties | 128 | | server-groups | 10 | | server-group-members | 10 | | floating-ips | 50 | | secgroup-rules | 100 | | secgroups | 10 | | backup-gigabytes | 1000 | | per-volume-gigabytes | -1 | +-----------------------+-------+
8.183. postgresql-jdbc 8.183.1. RHBA-2014:1489 - postgresql-jdbc bug fix update The updated postgresql-jdbc package that fixes several bugs is now available for Red Hat Enterprise Linux 6. PostgreSQL is an advanced Object-Relational database management system. The postgresql-jdbc package includes the .jar files needed for Java programs to access a PostgreSQL database. Note The postgresql-jdbc package has been upgraded to upstream version 8.4.704, which provides a number of bug fixes over the version. (BZ# 873972 ) Users of postgresql-jdbc are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Preface Red Hat Enterprise Linux minor releases are an aggregation of individual enhancement, security and bug fix errata. The Red Hat Enterprise Linux 6.5 Release Notes documents the major changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications for this minor release. Detailed notes on changes (that is, bugs fixed, enhancements added, and known issues found) in this minor release are available in the Technical Notes . The Technical Notes document also contains a complete list of all currently available Technology Previews along with packages that provide them. Important The online Red Hat Enterprise Linux 6.5 Release Notes , which are located online here , are to be considered the definitive, up-to-date version. Customers with questions about the release are advised to consult the online Release and Technical Notes for their version of Red Hat Enterprise Linux. Should you require information regarding the Red Hat Enterprise Linux life cycle, refer to https://access.redhat.com/support/policy/updates/errata/ .

Commands:
Chapter 4. Technology preview This section lists features that are in Technology Preview in Red Hat Developer Hub 1.2. Important These features are for Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information on Red Hat Technology Preview features, see Technology Preview Features Scope . 4.1. Plugins available in Red Hat Developer Hub Red Hat Developer Hub incorporates various dynamic plugins. Red Hat fully supports certain plugins, while others are community-supported projects. Some plugins are enabled by default, while others require configuration and are consequently disabled by default. To get a comprehensive list of supported dynamic plugins, see the Preinstalled dynamic plugins section in the Configuring plugins in Red Hat Developer Hub guide.

Commands:
Chapter 14. command This chapter describes the commands under the command command. 14.1. command list List recognized commands by group Usage: Table 14.1. Command arguments Value Summary -h, --help Show this help message and exit --group <group-keyword> Show commands filtered by a command group, for example: identity, volume, compute, image, network and other keywords Table 14.2. Output formatter options Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated --sort-ascending Sort the column(s) in ascending order --sort-descending Sort the column(s) in descending order Table 14.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 14.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 14.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack command list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--sort-ascending | --sort-descending] [--group <group-keyword>]
4.16. HP iLO over SSH The fence agents for HP iLO devices over SSH ( fence_ilo_ssh ), HP iLO3 devices over SSH ( fence_ilo3_ssh ), and HP iLO4 devices over SSH ( fence_ilo4_ssh ) share the same implementation. Table 4.17, "HP iLO over SSH, HP iLO3 over SSH, HPiLO4 over SSH (Red Hat Enterprise Linux 6.7 and later)" lists the fence device parameters used by these agents. Table 4.17. HP iLO over SSH, HP iLO3 over SSH, HPiLO4 over SSH (Red Hat Enterprise Linux 6.7 and later) luci Field cluster.conf Attribute Description Name name A name for the server with HP iLO support. IP Address or Hostname ipaddr The IP address or host name assigned to the device. Login login The login name used to access the device. Password passwd The password used to authenticate the connection to the device. Password Script (optional) passwd_script The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. Use SSH secure Indicates that the system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. Path to SSH Identity File identity_file The Identity file for SSH. TCP Port ipport UDP/TCP port to use for connections with the device; the default value is 23. Force Command Prompt cmd_prompt The command prompt to use. The default value is 'MP>', 'hpiLO->'. Method to Fence method The method to fence: on/off or cycle Power Wait (seconds) power_wait Number of seconds to wait after issuing a power off or power on command. Delay (seconds) delay The number of seconds to wait before fencing is started. The default value is 0. Power Timeout (seconds) power_timeout Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. Shell Timeout (seconds) shell_timeout Number of seconds to wait for a command prompt after issuing a command. The default value is 3. Login Timeout (seconds) login_timeout Number of seconds to wait for a command prompt after login. The default value is 5. Times to Retry Power On Operation retry_on Number of attempts to retry a power on operation. The default value is 1.

Commands:
Chapter 3. Provisioning management with Red Hat Satellite With Red Hat Satellite, you can provision hosts on various compute resources with many provisioning methods from a unified interface. 3.1. Provisioning methods in Red Hat Satellite With Red Hat Satellite, you can provision hosts by using multiple methods. Bare-Metal Provisioning Satellite provisions bare-metal hosts primarily by using PXE boot and MAC address identification. When provisioning bare-metal hosts with Satellite, you can do the following: Create host entries and specify the MAC address of the physical host to provision. Boot blank hosts to use the Satellite Discovery service, which creates a pool of hosts that are ready to be provisioned. Cloud Providers Satellite connects to private and public cloud providers to provision instances of hosts from images that are stored with the cloud environment. When provisioning from cloud with Satellite, you can do the following: Select which hardware profile or flavor to use. Provision cloud instances from specific providers by using their APIs. Virtualization Infrastructure Satellite connects to virtualization infrastructure services, such as Red Hat Virtualization and VMware. When provisioning virtual machines with Satellite, you can do the following: Provision virtual machines from virtual image templates. Use the same PXE-based boot methods as bare-metal providers. 3.2. Additional resources For information about how to provision hosts with Satellite, see Provisioning hosts .

Commands:
Chapter 1. Before you begin Release Notes See the Release Notes for important information about this release. Version Compatibility and Support See the Red Hat JBoss Fuse Supported Configurations page for details of version compatibility and support. Support for Windows O/S The developer tooling ( oc client and Container Development Kit) for Fuse on OpenShift is fully supported on the Windows O/S. The examples shown in Linux command-line syntax can also work on the Windows O/S, provided they are modified appropriately to obey Windows command-line syntax. 1.1. Comparison: Fuse Standalone and Fuse on OpenShift There are several major functionality differences: An application deployment with Fuse on OpenShift consists of an application and all required runtime components packaged inside a container image. Applications are not deployed to a runtime as with Fuse Standalone, the application image itself is a complete runtime environment deployed and managed through OpenShift. Patching in an OpenShift environment is different from Fuse Standalone, as each application image is a complete runtime environment. To apply a patch, the application image is rebuilt and redeployed within OpenShift. Core OpenShift management capabilities allow for rolling upgrades and side-by-side deployment to maintain availability of your application during upgrade. Provisioning and clustering capabilities provided by Fabric in Fuse have been replaced with equivalent functionality in Kubernetes and OpenShift. There is no need to create or configure individual child containers as OpenShift automatically does this for you as part of deploying and scaling your application. Fabric endpoints are not used within an OpenShift environment. Kubernetes services must be used instead. Messaging services are created and managed using the A-MQ for OpenShift image and not included directly within a Karaf container. Fuse on OpenShift provides an enhanced version of the camel-amq component to allow for seamless connectivity to messaging services in OpenShift through Kubernetes. Live updates to running Karaf instances using the Karaf shell is strongly discouraged as updates will not be preserved if an application container is restarted or scaled up. This is a fundamental tenet of immutable architecture and essential to achieving scalability and flexibility within OpenShift. Maven dependencies directly linked to Red Hat Fuse components are supported by Red Hat. Third-party Maven dependencies introduced by users are not supported. The SSH Agent is not included in the Apache Karaf micro-container, so you cannot connect to it using the bin/client console client. Protocol compatibility and Camel components within a Fuse on OpenShift application: non-HTTP based communications must use TLS and SNI to be routable from outside OpenShift into a Fuse service (Camel consumer endpoint).

Commands:
3.3. Network Interface Controller The NIC (Network Interface Controller) is a network adapter or LAN adapter that connects a computer to a computer network. The NIC operates on both the physical and data link layers of the machine and allows network connectivity. All virtualization hosts in a Red Hat Virtualization environment have at least one NIC, though it is more common for a host to have two or more NICs. One physical NIC can have multiple Virtual NICs (VNICs) logically connected to it. A virtual NIC acts as a physical network interface for a virtual machine. To distinguish between a VNIC and the NIC that supports it, the Red Hat Virtualization Manager assigns each VNIC a unique MAC address.

Commands:
Chapter 1. Schedule and quota APIs 1.1. AppliedClusterResourceQuota [quota.openshift.io/v1] Description AppliedClusterResourceQuota mirrors ClusterResourceQuota at a project scope, for projection into a project. It allows a project-admin to know which ClusterResourceQuotas are applied to his project and their associated usage. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object 1.2. ClusterResourceQuota [quota.openshift.io/v1] Description ClusterResourceQuota mirrors ResourceQuota at a cluster scope. This object is easily convertible to synthetic ResourceQuota object to allow quota evaluation re-use. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object 1.3. FlowSchema [flowcontrol.apiserver.k8s.io/v1] Description FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a "flow distinguisher". Type object 1.4. LimitRange [v1] Description LimitRange sets resource usage limits for each kind of resource in a Namespace. Type object 1.5. PriorityClass [scheduling.k8s.io/v1] Description PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer. Type object 1.6. PriorityLevelConfiguration [flowcontrol.apiserver.k8s.io/v1] Description PriorityLevelConfiguration represents the configuration of a priority level. Type object 1.7. ResourceQuota [v1] Description ResourceQuota sets aggregate quota restrictions enforced per namespace Type object

Commands:
1.7. Data Center and Cluster Compatibility Levels Red Hat Virtualization data centers and clusters have a compatibility version. The data center compatibility version indicates the version of Red Hat Virtualization that the data center is intended to be compatible with. All clusters in the data center must support the desired compatibility level. The cluster compatibility version indicates the features of Red Hat Virtualization supported by all of the hosts in the cluster. The cluster compatibility is set according to the version of the least capable host operating system in the cluster. The table below provides a compatibility matrix of RHV versions and the required data center and cluster compatibility levels. Table 1.1. Data center and cluster levels supported with Red Hat Virtualization Compatibility Level RHV Version Description 4.7 4.4 Compatibility Level 4.7 was introduced in RHV 4.4 to support new features introduced by RHEL 8.6 hypervisors. 4.6 4.4.6 Compatibility Level 4.6 was introduced in RHV 4.4.6 to support new features introduced by RHEL 8.4 hypervisors with Advanced Virtualization 8.4 packages. 4.5 4.4.3 Compatibility Level 4.5 was introduced in RHV 4.4.3 to support new features introduced by RHEL 8.3 hypervisors with Advanced Virtualization 8.3 packages. Limitations Virtio NICs are enumerated as a different device after upgrading the cluster compatibility level to 4.6. Therefore, the NICs might need to be reconfigured. Red Hat recommends that you test the virtual machines before you upgrade the cluster by setting the cluster compatibility level to 4.6 on the virtual machine and verifying the network connection. If the network connection for the virtual machine fails, configure the virtual machine with a custom emulated machine that matches the current emulated machine, for example pc-q35-rhel8.3.0 for 4.5 compatibility version, before upgrading the cluster.

Commands: