mtpti5iD/redhat-docs_dataset huggingface dataset:
11.2. Runtime Metadata Updates Runtime updates via system procedures and DDL statements are by default ephemeral. They are effective across the cluster only for the currently running VDBs. With the VDB start the values will revert to whatever is stored in the VDB. Updates may be made persistent by configuring an org.teiid.metadata.MetadataRepository . An instance of a MetadataRepository can be installed via the VDB file. In Designer based VDB, you can edit the vdb.xml file in the META-INF directory or use Dynamic VDB file as below. <vdb name="{vdb-name}" version="1"> <model name="{model-name}" type="VIRTUAL"> <metadata type="{jboss-as-module-name}"></metadata> </model> </vdb> In the above code fragment, replace the {jboss-as-module-name} with a JBoss EAP module name that has library that implements the org.teiid.metadata.MetadataRepository interface and defines file "META-INF/services/org.teiid.metadata.MetadataRepository" with name of the implementation file. The MetadataRepository repository instance may fully implement as many of the methods as needed and return null from any unneeded getter. Note It is not recommended to directly manipulate org.teiid.metadata.AbstractMetadataRecord instances. System procedures and DDL statements should be used instead since the effects will be distributed through the cluster and will not introduce inconsistencies. org.teiid.metadata.AbstractMetadataRecord objects passed to the MetadataRepository have not yet been modified. If the MetadataRepository cannot persist the update, then a RuntimeException should be thrown to prevent the update from being applied by the runtime engine. Note The MetadataRepository can be accessed by multiple threads both during load (if using dynamic VDBs) or at runtime with DDL statements. Your implementation should handle any needed synchronization.

Commands:
<vdb name="{vdb-name}" version="1"> <model name="{model-name}" type="VIRTUAL"> <metadata type="{jboss-as-module-name}"></metadata> </model> </vdb>
13.4. Shareable Disks in Red Hat Virtualization Some applications require storage to be shared between servers. Red Hat Virtualization allows you to mark virtual machine hard disks as Shareable and attach those disks to virtual machines. That way a single virtual disk can be used by multiple cluster-aware guests. Shared disks are not to be used in every situation. For applications like clustered database servers, and other highly available services, shared disks are appropriate. Attaching a shared disk to multiple guests that are not cluster-aware is likely to cause data corruption because their reads and writes to the disk are not coordinated. You cannot take a snapshot of a shared disk. Virtual disks that have snapshots taken of them cannot later be marked shareable. You can mark a disk shareable either when you create it, or by editing the disk later.

Commands:
Chapter 2. Acknowledgments Red Hat Ceph Storage version 6.1 contains many contributions from the Red Hat Ceph Storage team. In addition, the Ceph project is seeing amazing growth in the quality and quantity of contributions from individuals and organizations in the Ceph community. We would like to thank all members of the Red Hat Ceph Storage team, all of the individual contributors in the Ceph community, and additionally, but not limited to, the contributions from organizations such as: Intel(R) Fujitsu (R) UnitedStack Yahoo TM Ubuntu Kylin Mellanox (R) CERN TM Deutsche Telekom Mirantis (R) SanDisk TM SUSE (R)

Commands:
Chapter 31. Viewing Rule Name column in guided decision tables You can view the Rule Name column in the guided decision table if needed. Procedure In the guided decision tables designer, click Columns . Select the Show rule name column check box. Click Finish to save. The default rule name format is Row (row_number)(table_name) . The Source contains the default value if you do not specify a rule name. In the guided decision table, you can add a rule name in the Rule Name column and override the default value.

Commands:
Chapter 4. Advisories related to this release The following advisories are issued to bug fixes and CVE fixes included in this release: RHSA-2023:0194 RHSA-2023:0195 RHSA-2023:0196 RHSA-2023:0197 RHSA-2023:0198 RHSA-2023:0199 RHSA-2023:0200 RHSA-2023:0201 RHSA-2023:0202 Revised on 2024-05-09 16:47:09 UTC

Commands:
probe::ioblock.end Name probe::ioblock.end - Fires whenever a block I/O transfer is complete. Synopsis ioblock.end Values name name of the probe point sector beginning sector for the entire bio hw_segments number of segments after physical and DMA remapping hardware coalescing is performed phys_segments number of segments in this bio after physical address coalescing is performed. flags see below BIO_UPTODATE 0 ok after I/O completion BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block BIO_EOF 2 out-out-bounds error BIO_SEG_VALID 3 nr_hw_seg valid BIO_CLONED 4 doesn't own data BIO_BOUNCED 5 bio is a bounce bio BIO_USER_MAPPED 6 contains user pages BIO_EOPNOTSUPP 7 not supported devname block device name bytes_done number of bytes transferred error 0 on success size total size in bytes idx offset into the bio vector array vcnt bio vector count which represents number of array element (page, offset, length) which makes up this I/O request ino i-node number of the mapped file rw binary trace for read/write request Context The process signals the transfer is done.

Commands:
Chapter 5. Additional resources about RPM packaging This section provides references to various topics related to RPMs, RPM packaging, and RPM building. Some of these are advanced and extend the introductory material included in this documentation. Red Hat Software Collections Overview - The Red Hat Software Collections offering provides continuously updated development tools in latest stable versions. Red Hat Software Collections - The Packaging Guide provides an explanation of Software Collections and details how to build and package them. Developers and system administrators with basic understanding of software packaging with RPM can use this Guide to get started with Software Collections. Mock - Mock provides a community-supported package building solution for various architectures and different Fedora or RHEL versions than has the build host. RPM Documentation - The official RPM documentation. Fedora Packaging Guidelines - The official packaging guidelines for Fedora, useful for all RPM-based distributions.

Commands:
Chapter 6. Formatting Hammer output You can modify the default formatting of the output of hammer commands to simplify the processing of this output by other command line tools and applications. For example, to list organizations in a CSV format with a custom separator (in this case a semicolon), use the following command: Output in CSV format is useful for example when you need to parse IDs and use them in a for loop. Several other formatting options are available with the --output option: Replace output_format with one of: table - generates output in the form of a human readable table (default). base - generates output in the form of key-value pairs. yaml - generates output in the YAML format. csv - generates output in the Comma Separated Values format. To define a custom separator, use the --csv and --csv-separator options instead. json - generates output in the JavaScript Object Notation format. silent - suppresses the output.

Commands:
hammer --csv --csv-separator ";" organization list
hammer --output output_format organization list
3. We Need Feedback! If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/ against the product Red Hat Enterprise Linux 6 and the component doc-Global_File_System_2 . When submitting a bug report, be sure to mention the manual's identifier: If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, include the section number and some of the surrounding text so we can find it easily.

Commands:
rh-gfs2(EN)-6 (2017-3-8T15:15)
12.4. Memcached Interface Security 12.4.1. Publish Memcached Endpoints as a Public Interface Red Hat JBoss Data Grid's memcached server operates as a management interface by default. To extend its operations to a public interface, alter the value of the interface parameter in the socket-binding element from management to public as follows: Report a bug

Commands:
<socket-binding name="memcached" interface="public" port="11211" />
5.4. Booting into Emergency Mode In emergency mode, you are booted into the most minimal environment possible. The root file system is mounted read-only and almost nothing is set up. The main advantage of emergency mode over single-user mode is that the init files are not loaded. If init is corrupted or not working, you can still mount file systems to recover data that could be lost during a re-installation. To boot into emergency mode, use the same method as described for single-user mode in Section 5.3, "Booting into Single-User Mode" with one exception, replace the keyword single with the keyword emergency .

Commands:
Chapter 5. Using your own certificate authority bundle You can bring your organization's certificate authority (CA) bundle for signing and verifying your build artifacts with Red Hat's Trusted Artifact Signer (RHTAS) service. Prerequisites Installation of the RHTAS operator running on Red Hat OpenShift Container Platform. A running Securesign instance. Your CA root certificate. A workstation with the oc binary installed. Procedure Log in to OpenShift from the command line: Syntax oc login --token= TOKEN --server= SERVER_URL_AND_PORT Example USD oc login --token=sha256~ZvFDBvoIYAbVECixS4-WmkN4RfnNd8Neh3y1WuiFPXC --server=https://example.com:6443 Note You can find your login token and URL for use on the command line from the OpenShift web console. Log in to the OpenShift web console. Click your user name, and click Copy login command . Offer your user name and password again, if asked, and click Display Token to view the command. Switch to the RHTAS project: Example USD oc project trusted-artifact-signer Create a new ConfigMap by using your organization's CA root certificate bundle: Example USD oc create configmap custom-ca-bundle --from-file=ca-bundle.crt Important The certificate filename must be ca-bundle.crt . Open the Securesign resource for editing: Example USD oc edit Securesign securesign-sample Add the rhtas.redhat.com/trusted-ca under the metadata.annotations section: Example apiVersion: rhtas.redhat.com/v1alpha1 kind: Securesign metadata: name: example-instance annotations: rhtas.redhat.com/trusted-ca: custom-ca-bundle spec: ... Save, and quit the editor. Open the Fulcio resource for editing: Example USD oc edit Fulcio securesign-sample Add the rhtas.redhat.com/trusted-ca under the metadata.annotations section: Example apiVersion: rhtas.redhat.com/v1alpha1 kind: Fulcio metadata: name: example-instance annotations: rhtas.redhat.com/trusted-ca: custom-ca-bundle spec: ... Save, and quit the editor. Wait for the RHTAS operator to reconfigure before signing and verifying artifacts.

Commands:
login --token= TOKEN --server= SERVER_URL_AND_PORT
oc login --token=sha256~ZvFDBvoIYAbVECixS4-WmkN4RfnNd8Neh3y1WuiFPXC --server=https://example.com:6443
oc project trusted-artifact-signer
oc create configmap custom-ca-bundle --from-file=ca-bundle.crt
oc edit Securesign securesign-sample
apiVersion: rhtas.redhat.com/v1alpha1 kind: Securesign metadata: name: example-instance annotations: rhtas.redhat.com/trusted-ca: custom-ca-bundle spec:
oc edit Fulcio securesign-sample
apiVersion: rhtas.redhat.com/v1alpha1 kind: Fulcio metadata: name: example-instance annotations: rhtas.redhat.com/trusted-ca: custom-ca-bundle spec:
4.2. Starting luci Note Using luci to configure a cluster requires that ricci be installed and running on the cluster nodes, as described in Section 3.13, "Considerations for ricci " . As noted in that section, using ricci requires a password which luci requires you to enter for each cluster node when you create a cluster, as described in Section 4.4, "Creating a Cluster" . Before starting luci , ensure that the IP ports on your cluster nodes allow connections to port 11111 from the luci server on any nodes that luci will be communicating with. For information on enabling IP ports on cluster nodes, see Section 3.3.1, "Enabling IP Ports on Cluster Nodes" . To administer Red Hat High Availability Add-On with Conga , install and run luci as follows: Select a computer to host luci and install the luci software on that computer. For example: Note Typically, a computer in a server cage or a data center hosts luci ; however, a cluster computer can host luci . Start luci using service luci start . For example: Note As of Red Hat Enterprise Linux release 6.1, you can configure some aspects of luci 's behavior by means of the /etc/sysconfig/luci file, including the port and host parameters, as described in Section 3.4, "Configuring luci with /etc/sysconfig/luci " . Modified port and host parameters will automatically be reflected in the URL displayed when the luci service starts. At a Web browser, place the URL of the luci server into the URL address box and click Go (or the equivalent). The URL syntax for the luci server is https:// luci_server_hostname : luci_server_port . The default value of luci_server_port is 8084 . The first time you access luci , a web browser specific prompt regarding the self-signed SSL certificate (of the luci server) is displayed. Upon acknowledging the dialog box or boxes, your Web browser displays the luci login page. Any user able to authenticate on the system that is hosting luci can log in to luci . As of Red Hat Enterprise Linux 6.2 only the root user on the system that is running luci can access any of the luci components until an administrator (the root user or a user with administrator permission) sets permissions for that user. For information on setting luci permissions for users, see Section 4.3, "Controlling Access to luci" . Logging in to luci displays the luci Homebase page, as shown in Figure 4.1, "luci Homebase page" . Figure 4.1. luci Homebase page Note There is an idle timeout for luci that logs you out after 15 minutes of inactivity.

Commands:
yum install luci
service luci start Starting luci: generating https SSL certificates... done [ OK ] Please, point your web browser to https://nano-01:8084 to access luci
Chapter 4. Technology Preview This section lists Technology Preview features in Red Hat Developer Hub 1.4. Important Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. However, these features are not fully supported under Red Hat Subscription Level Agreements, may not be functionally complete, and are not intended for production use. As Red Hat considers making future iterations of Technology Preview features generally available, we will attempt to resolve any issues that customers experience when using these features. See: Technology Preview support scope . 4.1. Added notification backend plugins With this update, Developer Hub includes the following dynamic plugins to manage and streamline notification delivery: @backstage/plugin-signals @backstage/plugin-notifications-backend @backstage/plugin-notifications @backstage/plugin-notifications-backend-module-email These plugins are disabled by default. Additional resources RHIDP-5545

Commands:
Chapter 2. Red Hat 3scale API Management 2.15.2 - Patch release 2.1. New features Red Hat 3scale API Management 2.15.2 introduces the following enhancements: Added compatibility with Red Hat OpenShift Service on AWS (ROSA) with hosted control planes (HCP). Added compatibility with Red Hat build of Keycloak version 26. 2.2. Resolved issues Red Hat 3scale API Management 2.15.2 addresses the following issues: Fixed an issue preventing reconnection to Redis after a dropped connection ( THREESCALE-11528 ). Applied security and stability improvements.

Commands:
2.42. RHEA-2011:0576 - new package: spice-vdagent A new spice-vdagent package is now available for Red Hat Enterprise Linux 6. The new spice-vdagent package provides a SPICE agent for Linux guests. Bug Fixes BZ# 658464 The new spice-vdagent package allows for client window mode, automatic X session resolution adjustment to the client resolution, and copy and paste support for text and images between a guest's active X session and the SPICE client operating system. BZ# 680227 guest resolutions were not automatically aligned when multiple monitors were used. This update corrects the monitor settings. Now, the vdagent automatically aligns the guest resolution for one and more monitors. All SPICE virtual machines users should install this new package, which adds these features. Note: guests must be rebooted after installing this package for the changes to take effect.

Commands:
Chapter 5. Managing usability analytics and data collection from automation controller You can change how you participate in usability analytics and data collection from automation controller by opting out or changing your settings in the automation controller user interface. 5.1. Usability analytics and data collection Usability data collection is included with automation controller to collect data to better understand how automation controller users specifically interact with automation controller, to help enhance future releases, and to continue streamlining your user experience. Only users installing a trial of automation controller or a fresh installation of automation controller are opted-in for this data collection. Additional resources For more information, see the Red Hat privacy policy . 5.1.1. Controlling data collection from automation controller You can control how automation controller collects data by setting your participation level in the User Interface tab in the Settings menu. Procedure Log in to your automation controller. Navigate to Settings User Interface . Select the desired level of data collection from the User Analytics Tracking State drop-down list: Off : Prevents any data collection. Anonymous : Enables data collection without your specific user data. Detailed : Enables data collection including your specific user data. Click Save to apply the settings or Cancel to discard the changes.

Commands:
24.4.4. Using the df Command The df command allows you to display a detailed report on the system's disk space usage. To do so, type the following at a shell prompt: df For each listed file system, the df command displays its name ( Filesystem ), size ( 1K-blocks or Size ), how much space is used ( Used ), how much space is still available ( Available ), the percentage of space usage ( Use% ), and where is the file system mounted ( Mounted on ). For example: By default, the df command shows the partition size in 1 kilobyte blocks and the amount of used and available disk space in kilobytes. To view the information in megabytes and gigabytes, supply the -h command-line option, which causes df to display the values in a human-readable format: df -h For instance: For a complete list of available command-line options, see the df (1) manual page.

Commands:
~]USD df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_kvm-lv_root 18618236 4357360 13315112 25% / tmpfs 380376 288 380088 1% /dev/shm /dev/vda1 495844 77029 393215 17% /boot
~]USD df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_kvm-lv_root 18G 4.2G 13G 25% / tmpfs 372M 288K 372M 1% /dev/shm /dev/vda1 485M 76M 384M 17% /boot
2.3. Deployment cpuspeed component, BZ# 626893 Some HP Proliant servers may report incorrect CPU frequency values in /proc/cpuinfo or /sys/device/system/cpu/*/cpufreq . This is due to the firmware manipulating the CPU frequency without providing any notification to the operating system. To avoid this ensure that the HP Power Regulator option in the BIOS is set to OS Control . An alternative available on more recent systems is to set Collaborative Power Control to Enabled . releng component, BZ# 644778 Some packages in the Optional repositories on RHN have multilib file conflicts. Consequently, these packages cannot have both the primary architecture (for example, x86_64) and secondary architecture (for example, i686) copies of the package installed on the same machine simultaneously. To work around this issue, install only one copy of the conflicting package. releng component The openmpi-psm and openmpi-psm-devel packages are not provided on architectures other than AMD64 and Intel 64 for Red Hat Enterprise Linux 6.2. If the openmpi-psm.i686 or/and openmpi-psm-devel.i686 packages are installed on a AMD64 or an Intel 64 system, remove these packages before you attempt to update Open MPI. grub component, BZ# 695951 On certain UEFI-based systems, you may need to type BOOTX64 rather than bootx64 to boot the installer due to case sensitivity issues. grub component, BZ# 698708 When rebuilding the grub package on the x86_64 architecture, the glibc-static.i686 package must be used. Using the glibc-static.x86_64 package will not meet the build requirements. parted component The parted utility in Red Hat Enterprise Linux 6 cannot handle Extended Address Volumes (EAV) Direct Access Storage Devices (DASD) that have more than 65535 cylinders. Consequently, EAV DASD drives cannot be partitioned using parted , and installation on EAV DASD drives will fail. To work around this issue, complete the installation on a non EAV DASD drive, then add the EAV device after the installation using the tools provided in the s390-utils package. PackageKit component If you are being asked repeatedly to enter your root password while using PackageKit to update your system via non-Red Hat repositories, you may be affected by the PackageKit issue described in Section 2.11, "Desktop" .

Commands:
Chapter 14. Concepts for database connection pools This section is intended when you want to understand considerations and best practices on how to configure database connection pools for Red Hat build of Keycloak. For a configuration where this is applied, visit Deploy Red Hat build of Keycloak for HA with the Red Hat build of Keycloak Operator . 14.1. Concepts Creating new database connections is expensive as it takes time. Creating them when a request arrives will delay the response, so it is good to have them created before the request arrives. It can also contribute to a stampede effect where creating a lot of connections in a short time makes things worse as it slows down the system and blocks threads. Closing a connection also invalidates all server side statements caching for that connection. For the best performance, the values for the initial, minimal and maximum database connection pool size should all be equal. This avoids creating new database connections when a new request comes in which is costly. Keeping the database connection open for as long as possible allows for server side statement caching bound to a connection. In the case of PostgreSQL, to use a server-side prepared statement, a query needs to be executed (by default) at least five times . See the PostgreSQL docs on prepared statements for more information.

Commands:
Chapter 16. Networking Mellanox SR-IOV Support Single Root I/O Virtualization (SR-IOV) is now supported as a Technology Preview in the Mellanox libmlx4 library and the following drivers: mlx_core mlx4_ib (InfiniBand protocol) mlx_en (Ethernet protocol) Package: kernel QFQ queuing discipline In Red Hat Enterprise Linux 6, the tc utility has been updated to work with the Quick Fair Scheduler (QFQ) kernel features. Users can now take advantage of the new QFQ traffic queuing discipline from userspace. This feature is considered a Technology Preview. Package: kernel

Commands: