mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 10. Clusters 10.1. Cluster Elements The clusters collection provides information about clusters in a Red Hat Virtualization environment. An API user accesses this information through the rel="clusters" link obtained from the entry point URI. The following table shows specific elements contained in a cluster resource representation. Table 10.1. Cluster elements Element Type Description Properties name string A user-supplied, human-readable name for the cluster. The name is unique across all cluster resources. description string A free-form, user-supplied, human-readable description of the cluster. link rel="networks" relationship A link to the sub-collection for networks associated with this cluster. link rel="permissions" relationship A link to the sub-collection for cluster permissions. link rel="glustervolumes" relationship A link to the sub-collection for Red Hat Gluster Storage volumes associated with this cluster. link rel="glusterhooks" relationship A link to the sub-collection for Red Hat Gluster Storage volume hooks associated with this cluster. link rel="affinitygroups" relationship A link to the sub-collection for virtual machine affinity groups associated with this cluster. cpu id= complex A server CPU reference that defines the CPU type all hosts must support in the cluster. data_center id= GUID A reference to the data center membership of this cluster. memory_policy complex Defines the cluster's policy on host memory utilization. scheduling_policy complex Defines the load-balancing or power-saving modes for hosts in the cluster. version major= minor= complex The compatibility level of the cluster. supported_versions complex A list of possible version levels for the cluster. error_handling complex/enumerated Defines virtual machine handling when a host within a cluster becomes non-operational. Requires a single on_error element containing an enumerated type property listed in capabilities . virt_service Boolean Defines whether to expose virtualization services for this cluster. gluster_service Boolean Defines whether to expose Red Hat Gluster Storage services for this cluster. threads_as_cores Boolean Defines whether hosts can run virtual machines with a total number of processor cores greater than the number of cores in the host. tunnel_migration Boolean Defines whether virtual machines use a libvirt-to-libvirt tunnel during migration. trusted_service Boolean Defines whether an OpenAttestation server is used to verify hosts. ballooning_enabled Boolean Defines whether ballooning is enabled for the cluster. ksm Boolean Defines whether ksm is enabled for the cluster. Note When a host's free memory drops below 20%, ballooning commands like mom.Controllers.Balloon - INFO Ballooning guest:half1 from 1096400 to 1991580 are logged to /etc/vdsm/mom.conf . /etc/vdsm/mom.conf is the Memory Overcommit Manager log file. An event will also be added to the event log if a virtual machine does not respect a balloon.

Commands:
Chapter 4. Supported operating systems and architectures .NET 8.0 is available for OpenShift Container Platform, Red Hat Enterprise Linux 8.9 and later, and Red Hat Enterprise Linux 9.3 and later. .NET 8.0 is available on the x64_64 (64-bit Intel/AMD), aarch64 (64-bit ARM), ppc64le (64-bit IBM Power), and s390x (64-bit IBM Z) architectures. .NET 8.0 is available on x86_64 , aarch64 , and s390x on Red Hat Enterprise Linux 8 and later. Table 4.1. Supported deployment environments for .NET 8.0 Platform Architecture RPM Repository Red Hat Enterprise Linux 8 AMD64 and Intel 64 ( x86_64 ) IBM Z and LinuxONE ( s390x ) 64-bit ARM ( aarch64 ) IBM Power ( ppc64le ) dotnet-sdk-8.0 Appstream NOTE: The AppStream repositories are enabled by default in Red Hat Enterprise Linux 8. Red Hat Enterprise Linux 9 AMD64 and Intel 64 ( x86_64 ) IBM Z and LinuxONE ( s390x ) 64-bit ARM ( aarch64 ) IBM Power ( ppc64le ) dotnet-sdk-8.0 Appstream OpenShift Container Platform 4.2 and later IBM Z and LinuxONE ( s390x ) AMD64 and Intel 64 ( x86_64 ) OpenShift Container Platform 4.10 and later IBM Power ( ppc64le ) 64-bit ARM ( aarch64 )

Commands:
24.5.3. Using the lspcmcia Command The lspcmcia command allows you to list all PCMCIA devices that are present in the system. To do so, type the following at a shell prompt: lspcmcia For example: You can also use the -v command-line option to display more verbose information, or -vv to increase the verbosity level even further: lspcmcia -v | -vv For instance: For a complete list of available command-line options, see the pccardctl (8) manual page.

Commands:
~]USD lspcmcia Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:15:00.0)
~]USD lspcmcia -v Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:15:00.0) Configuration: state: on ready: unknown
14.11. Storage Pool Commands The following commands manipulate storage pools. Using libvirt you can manage various storage solutions, including files, raw partitions, and domain-specific formats, used to provide the storage volumes visible as devices within virtual machines. For more detailed information about this feature, see more information at libvirt.org . Many of the commands for storage pools are similar to the ones used for domains. 14.11.1. Searching for a Storage Pool XML The find-storage-pool-sources type srcSpec command displays the XML describing all storage pools of a given type that could be found. If srcSpec is provided, it is a file that contains XML to further restrict the query for pools. The find-storage-pool-sources-as type host port initiator displays the XML describing all storage pools of a given type that could be found. If host , port , or initiator are provided, they control where the query is performed. The pool-info pool-or-uuid command will list the basic information about the specified storage pool object. This command requires the name or UUID of the storage pool. To retrieve this information, use the following coomand: This lists all storage pool objects known to libvirt . By default, only active pools are listed; but using the --inactive option lists just the inactive pools, and using the --all option lists all of the storage pools. In addition to those options there are several sets of filtering options that can be used to filter the content of the list. --persistent restricts the list to persistent pools, --transient restricts the list to transient pools, --autostart restricts the list to autostarting pools and finally --no-autostart restricts the list to the storage pools that have autostarting disabled. For all storage pool commands which require a type , the pool types must be separated by comma. The valid pool types include: dir , fs , netfs , logical , disk , iscsi , scsi , mpath , rbd , and sheepdog . The --details option instructs virsh to additionally display pool persistence and capacity related information where available. Note When this command is used with older servers, it is forced to use a series of API calls with an inherent race, where a pool might not be listed or might appear more than once if it changed its state between calls while the list was being collected. Newer servers however, do not have this problem. The pool-refresh pool-or-uuid refreshes the list of volumes contained in pool.

Commands:
pool-list [--inactive] [--all] [--persistent] [--transient] [--autostart] [--no-autostart] [--details] type
Chapter 6. Quality of Service Red Hat Virtualization allows you to define quality of service entries that provide fine-grained control over the level of input and output, processing, and networking capabilities that resources in your environment can access. Quality of service entries are defined at the data center level and are assigned to profiles created under clusters and storage domains. These profiles are then assigned to individual resources in the clusters and storage domains where the profiles were created. 6.1. Storage Quality of Service Storage quality of service defines the maximum level of throughput and the maximum level of input and output operations for a virtual disk in a storage domain. Assigning storage quality of service to a virtual disk allows you to fine tune the performance of storage domains and prevent the storage operations associated with one virtual disk from affecting the storage capabilities available to other virtual disks hosted in the same storage domain. 6.1.1. Creating a Storage Quality of Service Entry Creating a Storage Quality of Service Entry Click Compute Data Centers . Click a data center's name to open the details view. Click the QoS tab. Under Storage , click New . Enter a QoS Name and a Description for the quality of service entry. Specify the Throughput quality of service by clicking one of the radio buttons: None Total - Enter the maximum permitted total throughput in the MB/s field. Read/Write - Enter the maximum permitted throughput for read operations in the left MB/s field, and the maximum permitted throughput for write operations in the right MB/s field. Specify the input and output ( IOps ) quality of service by clicking one of the radio buttons: None Total - Enter the maximum permitted number of input and output operations per second in the IOps field. Read/Write - Enter the maximum permitted number of input operations per second in the left IOps field, and the maximum permitted number of output operations per second in the right IOps field. Click OK . You have created a storage quality of service entry, and can create disk profiles based on that entry in data storage domains that belong to the data center. 6.1.2. Removing a Storage Quality of Service Entry Remove an existing storage quality of service entry. Removing a Storage Quality of Service Entry Click Compute Data Centers . Click a data center's name to open the details view. Click the QoS tab. Under Storage , select a storage quality of service entry and click Remove . Click OK . If any disk profiles were based on that entry, the storage quality of service entry for those profiles is automatically set to [unlimited] .

Commands:
Chapter 4. Content Life Cycles Table 4.1. Content Life Cycles Subcommand Description and tasks lifecycle-environment org Create a life cycle environment: List life cycle environments: content-view org Create a content view: Add repositories to a content view: Add Puppet modules to a content view: Publishing a content view: Promoting a content view: Incremental update of a content view:

Commands:
hammer lifecycle-environment create --name env_name --description env_desc --prior prior_env_name
hammer lifecycle-environment list
hammer content-view create --name cv_n --repository-ids repo_ID1,... --description cv_description
hammer content-view add-repository --name cv_n --repository-id repo_ID
hammer content-view puppet-module add --content-view cv_n --name module_name
hammer content-view publish --id cv_ID
hammer content-view version promote --content-view cv_n --to-lifecycle-environment env_name
hammer content-view version incremental-update --content-view-version-id cv_ID --packages pkg_n1,... --lifecycle-environment-ids env_ID1,
Chapter 3. Spring and Spring Boot 3.1. Spring and Spring Boot tutorials Note These code tutorials use Data Grid Server and require at least one running instance. Run Spring examples Two simple tutorials can be run with Spring without Spring Boot: Test caching USD ./mvnw -s /path/to/maven-settings.xml package exec:exec@spring-caching Test annotations USD ./mvnw -s /path/to/maven-settings.xml package exec:exec@spring-annotations To run the Spring Boot tutorials, use the following command. USD ./mvnw -s /path/to/maven-settings.xml spring-boot:run Displaying actuator statistics Navigate to http://localhost:8080/actuator/metrics in your browser to display a list of available metrics. Cache metrics are prefixed with "cache." Display each metric for each cache using tags. For example for the 'puts' stats in the basque-names cache: http://localhost:8080/actuator/metrics/cache.puts?tag=name:basque-names Collecting statistics with Prometheus The prometheus.yml file in this project contains a host.docker.internal binding that allows Prometheus to scrap metrics that the Spring actuator exposes. Change the YOUR_PATH value in the following command to the directory where Prometheus is running and then run: Podman USD podman run -d --name=prometheus -p 9090:9090 -v YOUR_PATH/integrations/spring-boot/prometheus.yml:/etc/prometheus/prometheus.yml prom/prometheus --config.file=/etc/prometheus/prometheus.yml Tutorial link Description Spring Boot and Spring Cache remote mode Demonstrates how to use Spring Caches with Spring Boot and the Data Grid Server. Spring Boot, Spring Cache, Reactor and Infinispan Server Demonstrates how to use Spring Caches with Spring Boot Reactor and the Data Grid Server. Spring Boot and Spring Session remote mode Demonstrates how to use Spring Session with Spring Boot and the Data Grid Server. Spring Boot and Spring Cache embedded mode Demonstrates how to use Spring Caches with Spring Boot and Data Grid Embedded. Spring Boot and Spring Session embedded mode Demonstrates how to use Spring Session with Spring Boot and Data Grid Embedded. Spring cache embedded without Spring Boot Demonstrates how to use Spring Cache and Data Grid Embedded without Spring Boot. Data Grid documentation You can find more resources in our documentation at: Using Data Grid with Spring Data Grid Spring Boot Starter

Commands:
./mvnw -s /path/to/maven-settings.xml package exec:exec@spring-caching
./mvnw -s /path/to/maven-settings.xml package exec:exec@spring-annotations
./mvnw -s /path/to/maven-settings.xml spring-boot:run
podman run -d --name=prometheus -p 9090:9090 -v YOUR_PATH/integrations/spring-boot/prometheus.yml:/etc/prometheus/prometheus.yml prom/prometheus --config.file=/etc/prometheus/prometheus.yml
20.8. Using Quota to Limit Resources by User This procedure describes how to use quotas to limit the resources a user has access to. Assigning a User to a Quota Click Administration Quota . Click the name of the target quota to open the details view. Click the Consumers tab. Click Add . In the Search field, type the name of the user you want to associate with the quota. Click GO . Select the check box to the user's name. Click OK . After a short time, the user will appear in the Consumers tab in the details view.

Commands:
4.220. pciutils 4.220.1. RHBA-2011:1760 - pciutils bug fix and enhancement update Updated pciutils packages that fix a bug and add an enhancement are now available for Red Hat Enterprise Linux 6. The pciutils package contains various utilities for inspecting and manipulating devices connected to the PCI bus. Bug Fix BZ# 740630 Previously, in an attempt to free data structures from memory via the pci_free_cap() function, the "glibc detected *** double free or corruption (!prev):" error message was returned and the operation failed. A patch has been provided to address this issue and freeing system resources now works properly. Enhancement BZ# 742223 With this update, TPH (Transaction Processing Hints) and LTR (Latency Tolerance Reporting) reporting capabilities have been added to the pciutils package to support the PCI Express 3.0 standard. All pciutils users should upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
B.52. mailman B.52.1. RHSA-2011:0308 - Moderate: mailman security update An updated mailman package that fixes multiple security issues is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Mailman is a program used to help manage email discussion lists. CVE-2011-0707 Multiple input sanitization flaws were found in the way Mailman displayed usernames of subscribed users on certain pages. If a user who is subscribed to a mailing list were able to trick a victim into visiting one of those pages, they could perform a cross-site scripting (XSS) attack against the victim. CVE-2010-3089 Multiple input sanitization flaws were found in the way Mailman displayed mailing list information. A mailing list administrator could use this flaw to conduct a cross-site scripting (XSS) attack against victims viewing a list's "listinfo" page. Red Hat would like to thank Mark Sapiro for reporting these issues. Users of mailman should upgrade to this updated package, which contains backported patches to correct these issues.

Commands:
6.3.3. Splitting the Volume Group To create the new volume group yourvg , use the vgsplit command to split the volume group myvg . Before you can split the volume group, the logical volume must be inactive. If the file system is mounted, you must unmount the file system before deactivating the logical volume. You can deactivate the logical volumes with the lvchange command or the vgchange command. The following command deactivates the logical volume mylv and then splits the volume group yourvg from the volume group myvg , moving the physical volume /dev/sdc1 into the new volume group yourvg . You can use the vgs command to see the attributes of the two volume groups.

Commands:
lvchange -a n /dev/myvg/mylv vgsplit myvg yourvg /dev/sdc1 Volume group "yourvg" successfully split from "myvg"
vgs VG #PV #LV #SN Attr VSize VFree myvg 2 1 0 wz--n- 34.30G 10.80G yourvg 1 0 0 wz--n- 17.15G 17.15G
Chapter 5. Deleting an OpenShift Dedicated cluster on GCP As cluster owner, you can delete your OpenShift Dedicated clusters. 5.1. Deleting your cluster You can delete your OpenShift Dedicated cluster in Red Hat OpenShift Cluster Manager. Prerequisites You logged in to OpenShift Cluster Manager . You created an OpenShift Dedicated cluster. Procedure From OpenShift Cluster Manager , click on the cluster you want to delete. Select Delete cluster from the Actions drop-down menu. Type the name of the cluster highlighted in bold, then click Delete . Cluster deletion occurs automatically. Note If you delete a cluster that was installed into a GCP Shared VPC, inform the VPC owner of the host project to remove the IAM policy roles granted to the service account that was referenced during cluster creation.

Commands:
4.293. setup 4.293.1. RHBA-2011:1171 - setup bug fix and enhancement update An updated setup package that fixes two bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The setup package contains a set of important system configuration and setup files, such as passwd, group, and profile. Bug Fixes BZ# 691425 Bash provides the PROMPT_COMMAND environment variable containing a command that is called when a prompt is displayed. Prior to this update, the PROMPT_COMMAND variable set by a custom profile.d script was overwritten with the default value from the /etc/bashrc script file. With this update, the /etc/bashrc script file has been updated so that it now respects a user-defined PROMPT_COMMAND variable, and does not overwrite it. BZ# 703052 Prior to this update, the /etc/host.conf configuration file contained a line "order host,bind". This line is no longer used by the glibc library and is therefore redundant. With this update, this line has been removed from the host.conf file. Enhancements BZ# 706012 The retrace-server package creates a user ID (UID) pair and a group ID (GID) pair, both with the name "retrace" and number "174". This user and group is used by the Automated Bug Reporting Tool (ABRT) retracing server. Prior to this update, the aforementioned UID/GID pairs were not reserved by the setup package so that other packages or system administrators could have accidentally assigned those values to other users and groups. With this update, the setup package now reserves these UID and GID names and numbers so that accidental conflicts with other users and groups do not happen anymore. BZ# 709599 The rhev-agent package creates a user ID (UID) pair and a group ID (GID) pair, both with the name "rhevagent" and number "175". This user and group is used by RHEV-Agent. Prior to this update, the aforementioned UID/GID pairs were not reserved by the setup package so that other packages or system administrators could have accidentally assigned those values to other users and groups. With this update, the setup package now reserves these UID and GID names and numbers so that accidental conflicts with other users and groups do not happen anymore. BZ# 715266 The trafficserver package creates a user ID (UID) pair and a group ID (GID) pair, both with the name "ats" and number "176". This user and group is used for the configuration management functions over a cluster of nodes. Prior to this update, the aforementioned UID/GID pairs were not reserved by the setup package so that other packages or system administrators could have accidentally assigned those values to other users and groups. With this update, the setup package now reserves these UID and GID names and numbers so that accidental conflicts with other users and groups do not happen anymore. All users are advised to upgrade to this updated setup package, which fixes these bugs and adds these enhancements.

Commands:
Chapter 1. Red Hat Enterprise Linux 6.6 International Languages Red Hat Enterprise Linux 6.6 supports installation of multiple languages and changing of languages based on your requirements. The following languages are supported in Red Hat Enterprise Linux 6.6: East Asian Languages - Japanese, Korean, Simplified Chinese, and Traditional Chinese European Languages - English, German, Spanish, French, Portuguese Brazilian, and Russian, Indic Languages - Assamese, Bengali, Gujarati, Hindi, Kannada, Malayalam, Marathi, Oriya, Punjabi, Tamil, and Telugu The table below summarizes the currently supported languages, their locales, default fonts installed and packages required for some of the supported languages Table 1.1. Red Hat Enterprise Linux 6 International Languages Territory Language Locale Fonts Package Names China Simplified Chinese zh_CN.UTF-8 AR PL (ShanHeiSun and Zenkai) Uni fonts-chinese, scim-pinyin, scim-tables Japan Japanese ja_JP.UTF-8 Sazanami (Gothic and Mincho) fonts-japanese, scim-anthy Korea Hangul ko_KR.UTF-8 Baekmuk (Batang, Dotum, Gulim, Headline) fonts-korean, scim-hangul Taiwan Traditional Chinese zh_TW.UTF-8 AR PL (ShanHeiSun and Zenkai) Uni fonts-chinese, scim-chewing, scim-tables Brazil Portuguese pt_BR.UTF-8 standard latin fonts France French ft_FR.UTF-8 standard latin fonts Germany German de_DE.UTF-8 standard latin fonts Italy Italy it_IT.UTF-8 standard latin fonts Russia Russian ru_RU.UTF-8 KOI8-R, fonts-KOI8-R-100dpi, fonts-KOI8-R-75dpi and xorg-x11-fonts-cyrillic fonts-KO18-R, fonts-KO18-R-100 dpi,fonts-KO18-R-75dpi, xorg-x11-fonts-cyrillic Spain Spanish es_ES.UTF-8 standard latin fonts India Assamese as_IN.UTF-8 Lohit Bengali fonts-bengali, scim-m17n, m17n-db-assamese Bengali bn_IN.UTF-8 Lohit Bengali fonts-bengali, scim-m17n, m17n-db-bengali Gujarati gu_IN.UTF-8 Lohit Gujarati fonts-gujarati, scim-m17n, m17n-db-gujarati Hindi hi_IN.UTF-8 Lohit Hindi fonts-hindi, scim-m17n, m17n-db-hindi Kannada kn_IN.UTF-8 Lohit Kannada fonts-kannada, scim-m17n, m17n-db-kannada Malayalam ml_IN.UTF-8 Lohit Malayalam fonts-malayalam, scim-m17n, m17n-db-malayalam Marathi mr_IN.UTF-8 Lohit Hindi fonts-hindi, scim-m17n, m17n-db-marathi Oriya or_IN.UTF-8 Lohit Oriya fonts-oriya, scim-m17n, m17n-db-oriya Punjabi pa_IN.UTF-8 Lohit Punjabi fonts-punjabi, scim-m17n, m17n-db-punjabi Tamil ta_IN.UTF-8 Lohit Tamil fonts-tamil, scim-m17n, m17n-db-tamil Telugu te_IN.UTF-8 Lohit Telugu fonts-telugu, scim-m17n, m17n-db-telugu

Commands:
A. Revision History Revision History Revision 2-4.400 2013-10-31 Rudiger Landmann Rebuild with publican 4.0.0 Revision 2-4 2012-07-18 Anthony Towns Rebuild for Publican 3.0 Revision 2-3 Tue Feb 8 2011 Michael Hideo BZ#627110 BZ#627111 Revision 1.0-0 Thu May 07 2009 Ryan Lerch Added Release Notes Updates for the General Availability (GA) Revision 0.1-0 Thu May 07 2009 Ryan Lerch Inital Version of the Release Notes

Commands: