mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 5. Developer previews This section describes the developer preview features introduced in Red Hat OpenShift Data Foundation 4.16. Important Developer preview feature is subject to Developer preview support limitations. Developer preview releases are not intended to be run in production environments. The clusters deployed with the developer preview features are considered to be development clusters and are not supported through the Red Hat Customer Portal case management system. If you need assistance with developer preview features, reach out to the ocs-devpreview@redhat.com mailing list and a member of the Red Hat Development Team will assist you as quickly as possible based on availability and work schedules. 5.1. Support for Topology awareness and Replica-1 in OpenShift Data Foundation external mode OpenShift Data Foundation supports provisioning storage from replica-1 using a storage class. The storage class is created to provision storage from replica 1 Ceph pools that are located in separate zones. This helps applications that have multiple running instances with each service instance creating a new claim, which is expected to be located in a different zone. As these applications have their own redundant instances, they do not require redundancy at the data layer. For more information, see the knowledgebase article, OpenShift Data Foundation external mode support for RBD/block Replica-1 pools and topology awareness . 5.2. Multi-Volume Consistency for Backup - CephFS To provide better support for applications and to support OpenShift Virtualization, crash consistent multi volume consistency groups are provided for backup solutions. This helps applications that are deployed over multiple volumes. 5.3. Storage class with replica 2 for CephFS OpenShift Data Foundation provides a way to create a new CephFS based storage class with 2 replicas. This helps to provide better storage efficiency in case only CephFs is being used. Also, this provides a solution for unbalanced usage of either RBD or CephFS. For more information, see the knowledgebase article, Using replica 2 for CephFS . 5.4. Automatic scaling of RGW OpenShift Data Foundation provides the ability to enable auto scaling to automatically adjust the serviceability and performance of RADOS Gateway (RGW) to serve as per the S3 load. For more information, see the knowledgebase article, Autoscaling for RGW in OpenShift Data Foundation via HPA using KEDA . 5.5. Ceph replica-2 pool with both disks in the same zone To protect applications in case of an OSD disk failure, replica-2 pool with both disks in a single zone can be created. For more information, see the knowledgebase article RBD Replica-2 with both disks in same zone . 5.6. RGW erasure coding in internal mode Erasure coding deployment for RGW using CLI is supported to help reduce cost by increasing storage efficiency. For more information, see the knowledgebase article Support for RGW Erasure Coding in Internal Mode .

Commands:
Chapter 3. Creating Your Microsoft Azure Environment Create the virtual machines that will host your JBoss EAP instances in your Microsoft Azure environment. The virtual machines must use an Azure size of Standard_A2 or higher. You can use either the Azure On-Demand premium images to create your virtual machines or create your own virtual machines manually. For Red Hat Enterprise Linux virtual machines, see the instructions on the Customer Portal: Using the On-Demand Marketplace Red Hat Enterprise Linux 7 image in Azure . Manually creating and provisioning a Red Hat Enterprise Linux 7 image for Azure . For Microsoft Windows Server virtual machines, see the Microsoft Azure documentation for instructions on creating a Windows Server virtual machine in Microsoft Azure. Important If you are configuring JBoss EAP high availability, you must create your virtual machines inside the same virtual network.

Commands:
Chapter 3. Installing the all-in-one Red Hat OpenStack Platform environment Before you can begin configuring, deploying, and testing your all-in-one environment, you must configure a non-root user and install the necessary packages and dependencies: Create a non-root user on the all-in-one host: Set the password for the stack user: Disable password requirements when using sudo as the stack user: Log in as the non-root user on the all-in-one host: Register the machine with Red Hat Subscription Manager. Enter your Red Hat subscription credentials at the prompt: Attach your Red Hat subscription to the entitlement server: Note The --auto option might not subscribe you to the correct subscription pool. Ensure that you subscribe to the correct pool, otherwise you might not be able to enable all of the repositories necessary for this installation. Use the subscription-manager list --all --available command to identify the correct pool ID. Lock the undercloud to Red Hat Enterprise Linux 9.0: Run the following commands to install dnf-utils , disable all default repositories, and then enable the necessary repositories: Note The all-in-one environment is a Technology Preview feature in Red Hat OpenStack Platform 17.0. Update the base operating system and reboot the system: Log back in to the host after the reboot. Install the TripleO command line interface (CLI):

Commands:
useradd stack
passwd stack
echo "stack ALL=(root) NOPASSWD:ALL" | tee -a /etc/sudoers.d/stack chmod 0440 /etc/sudoers.d/stack
ssh stack@<all-in-one>
[stack@all-in-one]USD sudo subscription-manager register
[stack@all-in-one]USD sudo subscription-manager attach --auto
sudo subscription-manager release --set=9.0
[stack@all-in-one]USD sudo dnf install -y dnf-utils [stack@all-in-one]USD sudo subscription-manager repos --disable=* [stack@all-in-one]USD sudo subscription-manager repos --enable=rhel-9-for-x86_64-baseos-eus-rpms --enable=rhel-9-for-x86_64-appstream-eus-rpms --enable=rhel-9-for-x86_64-highavailability-eus-rpms --enable=openstack-17-for-rhel-9-x86_64-rpms --enable=fast-datapath-for-rhel-9-x86_64-rpms
[stack@all-in-one]USD sudo dnf update [stack@all-in-one]USD sudo reboot
[stack@all-in-one]USD sudo dnf install -y python3-tripleoclient
B.2.2. Failed to connect socket ... : Permission denied Symptom When running a virsh command, the following error (or similar) appears: Investigation Without any host name specified, the connection to QEMU uses UNIX sockets by default. If there is no error running this command as root, the UNIX socket options in /etc/libvirt/libvirtd.conf are likely misconfigured. Solution To connect as a non-root user using UNIX sockets, configure the following options in /etc/libvirt/libvirtd.conf : unix_sock_group = <group> unix_sock_ro_perms = <perms> unix_sock_rw_perms = <perms> Note The user running virsh must be a member of the group specified in the unix_sock_group option.

Commands:
virsh -c qemu:///system list error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied error: failed to connect to the hypervisor
unix_sock_group = <group> unix_sock_ro_perms = <perms> unix_sock_rw_perms = <perms>
10.2.4. Using the QEMU Guest Agent with libvirt Installing the QEMU guest agent allows various other libvirt commands to become more powerful. The guest agent enhances the following virsh commands: virsh shutdown --mode=agent - This shutdown method is more reliable than virsh shutdown --mode=acpi , as virsh shutdown used with the QEMU guest agent is guaranteed to shut down a cooperative guest in a clean state. If the agent is not present, libvirt has to instead rely on injecting an ACPI shutdown event, but some guests ignore that event and thus will not shut down. Can be used with the same syntax for virsh reboot . virsh snapshot-create --quiesce - Allows the guest to flush its I/O into a stable state before the snapshot is created, which allows use of the snapshot without having to perform a fsck or losing partial database transactions. The guest agent allows a high level of disk contents stability by providing guest co-operation. virsh setvcpus --guest - Instructs the guest to take CPUs offline. virsh dompmsuspend - Suspends a running guest gracefully using the guest operating system's power management functions.

Commands:
Chapter 4. Prerequisites The following are the prerequisites for the Migration Toolkit for Runtimes (MTR) installation: Java Development Kit (JDK) is installed. MTR supports the following JDKs: OpenJDK 11 OpenJDK 17 Oracle JDK 11 Oracle JDK 17 Eclipse TemurinTM JDK 11 Eclipse TemurinTM JDK 17 8 GB RAM macOS installation: the value of maxproc must be 2048 or greater.

Commands:
8.3. Solid-State Disks Solid-state disks (SSD) use NAND flash chips rather than rotating magnetic platters to store persistent data. They provide a constant access time for data across their full Logical Block Address range, and do not incur measurable seek costs like their rotating counterparts. They are more expensive per gigabyte of storage space and have a lesser storage density, but they also have lower latency and greater throughput than HDDs. Performance generally degrades as the used blocks on an SSD approach the capacity of the disk. The degree of degradation varies by vendor, but all devices experience degradation in this circumstance. Enabling discard behavior can help to alleviate this degradation. For details, see Section 8.1.3.3, "Maintenance" . The default I/O scheduler and virtual memory options are suitable for use with SSDs. For more information on SSD, see the Solid-State Disk Deployment Guidelines chapter in the Red Hat Enterprise Linux 7 Storage Administration Guide . SSD Tuning Considerations Consider the following factors when configuring settings that can affect SSD performance: I/O Scheduler Any I/O scheduler is expected to perform well with most SSDs. However, as with any other storage type, Red Hat recommends benchmarking to determine the optimal configuration for a given workload. When using SSDs, Red Hat advises changing the I/O scheduler only for benchmarking particular workloads. For instructions on how to switch between I/O schedulers, see the /usr/share/doc/kernel- version /Documentation/block/switching-sched.txt file. As of Red Hat Enterprise Linuxnbsp 7.0, the default I/O scheduler is Deadline, except for use with SATA drives, which use CFQ as the default I/O scheduler. For faster storage, Deadline can outperform CFQ leading to better I/O performance without the need for specific tuning. Sometimes, the default is not suitable for certain disks, such as SAS rotational disks. In such cases, change the I/O scheduler to CFQ. Virtual Memory Like the I/O scheduler, virtual memory (VM) subsystem requires no special tuning. Given the fast nature of I/O on SSD, try turning down the vm_dirty_background_ratio and vm_dirty_ratio settings, as increased write-out activity does not usually have a negative impact on the latency of other operations on the disk. However, this tuning can generate more overall I/O , and is therefore not generally recommended without workload-specific testing. Swap An SSD can also be used as a swap device, and is likely to produce good page-out and page-in performance.

Commands:
Chapter 2. Using activation keys With root privileges, you can use an activation key with a registration command to connect your system to Red Hat from the command line. Using an activation key and organization ID combination instead of a username and password combination increases security and facilitates automation. If an RHC administrator has preconfigured the activation key with system-level features, then the selected features are automtically applied to the system during the registration process. Additional resources For more information about using activation keys to register your system to Red Hat, see Registering a RHEL system with command line tools in Getting Started with RHEL System Registration For more information about using activation keys with automation scripts, see Automating RHEL system registration with a Kickstart file in Getting Started with RHEL System Registration

Commands:
Chapter 5. Viewing costs associated with virtual machines With support for tracking Red Hat OpenShift Virtualization, you can view costs that are directly associated with virtual machines (VMs) running on your OpenShift clusters. Cost management gathers information about each VM that is running on OpenShift and associates costs to it at a monthly aggregate level. The API endpoint is /api/cost-management/v1/reports/openshift/resources/virtual-machines/ . To find your Red Hat OpenShift Virtualization data, complete the following steps: In cost management, navigate to a specific cluster, node, or project. Click the Virtualization tab on the OpenShift details page. To learn about Red Hat OpenShift Virtualization, see Virtualization .

Commands:
probe::ipmib.InUnknownProtos Name probe::ipmib.InUnknownProtos - Count arriving packets with an unbound proto Synopsis ipmib.InUnknownProtos Values skb pointer to the struct sk_buff being acted on op value to be added to the counter (default value of 1) Description The packet pointed to by skb is filtered by the function ipmib_filter_key . If the packet passes the filter is is counted in the global InUnknownProtos (equivalent to SNMP's MIB IPSTATS_MIB_INUNKNOWNPROTOS)

Commands:
3.4.2. Useful Websites http://people.redhat.com/alikins/system_tuning.html -- System Tuning Info for Linux Servers. A stream-of-consciousness approach to performance tuning and resource monitoring for servers. http://www.linuxjournal.com/article.php?sid=2396 -- Performance Monitoring Tools for Linux. This Linux Journal page is geared more toward the administrator interested in writing a customized performance graphing solution. Written several years ago, some of the details may no longer apply, but the overall concept and execution are sound.

Commands:
Part II. Storage Administration The Storage Administration section starts with storage considerations for Red Hat Enterprise Linux 6. Instructions regarding partitions, logical volume management, and swap partitions follow this. Disk Quotas, RAID systems are , followed by the functions of mount command, volume_key, and acls. SSD tuning, write barriers, I/O limits and diskless systems follow this. The large chapter of Online Storage is , and finally device mapper multipathing and virtual storage to finish. Use the following to explore these Storage Administration tasks.

Commands:
29.10. OProfile and SystemTap SystemTap is a tracing and probing tool that allows users to study and monitor the activities of the operating system in fine detail. It provides information similar to the output of tools like netstat , ps , top , and iostat ; however, SystemTap is designed to provide more filtering and analysis options for collected information. While using OProfile is suggested in cases of collecting data on where and why the processor spends time in a particular area of code, it is less usable when finding out why the processor stays idle. You might want to use SystemTap when instrumenting specific places in code. Because SystemTap allows you to run the code instrumentation without having to stop and restart the instrumentation, it is particularly useful for instrumenting the kernel and daemons. For more information on SystemTap, see Section 29.11.2, "Useful Websites" for the relevant SystemTap documentation.

Commands:
12.3. Hot Rod and Marshalling In Remote Client-Server mode, marshalling occurs both on the Red Hat JBoss Data Grid server and the client levels, but to varying degrees. All data stored by clients on the JBoss Data Grid server are provided either as a byte array, or in a primitive format that is marshalling compatible for JBoss Data Grid. On the server side of JBoss Data Grid, marshalling occurs where the data stored in primitive format are converted into byte array and replicated around the cluster or stored to a cache store. No marshalling configuration is required on the server side of JBoss Data Grid. At the client level, marshalling must have a Marshaller configuration element specified in the RemoteCacheManager configuration in order to serialize and deserialize POJOs. Due to Hot Rod's binary nature, it relies on marshalling to transform POJOs, specifically keys or values, into byte array. Report a bug

Commands:
13.18. Begin Installation When all required sections of the Installation Summary screen have been completed, the admonition at the bottom of the menu screen disappears and the Begin Installation button becomes available. Figure 13.36. Ready to Install Warning Up to this point in the installation process, no lasting changes have been made on your computer. When you click Begin Installation , the installation program will allocate space on your hard drive and start to transfer Red Hat Enterprise Linux into this space. Depending on the partitioning option that you chose, this process might include erasing data that already exists on your computer. To revise any of the choices that you made up to this point, return to the relevant section of the Installation Summary screen. To cancel installation completely, click Quit or switch off your computer. To switch off most computers at this stage, press the power button and hold it down for a few seconds. If you have finished customizing your installation and are certain that you want to proceed, click Begin Installation . After you click Begin Installation , allow the installation process to complete. If the process is interrupted, for example, by you switching off or resetting the computer, or by a power outage, you will probably not be able to use your computer until you restart and complete the Red Hat Enterprise Linux installation process, or install a different operating system.

Commands:
Chapter 4. Creating the traffic violations project in Business Central For this example, create a new project called traffic-violation . A project is a container for assets such as data objects, DMN assets, and test scenarios. This example project that you are creating is similar to the existing Traffic_Violation sample project in Business Central. Procedure In Business Central, go to Menu Design Projects . Red Hat Decision Manager provides a default space called MySpace . You can use the default space to create and test example projects. Click Add Project . Enter traffic-violation in the Name field. Click Add . Figure 4.1. Add Project window The Assets view of the project opens.

Commands:
Appendix A. Troubleshooting DNF modules If DNF modules fails to enable, it can mean an incorrect module is enabled. In that case, you have to resolve dependencies manually as follows. List the enabled modules: A.1. Ruby If Ruby module fails to enable, it can mean an incorrect module is enabled. In that case, you have to resolve dependencies manually as follows: List the enabled modules: If the Ruby 2.5 module has already been enabled, perform a module reset: A.2. PostgreSQL If PostgreSQL module fails to enable, it can mean an incorrect module is enabled. In that case, you have to resolve dependencies manually as follows: List the enabled modules: If the PostgreSQL 10 module has already been enabled, perform a module reset: If a database was previously created using PostgreSQL 10, perform an upgrade: Enable the DNF modules: Install the PostgreSQL upgrade package: Perform the upgrade:

Commands:
dnf module list --enabled
dnf module list --enabled
dnf module reset ruby
dnf module list --enabled
dnf module reset postgresql
dnf module enable satellite:el8
dnf install postgresql-upgrade
postgresql-setup --upgrade
1.3. KVM Guest Virtual Machine Compatibility Red Hat Enterprise Linux 7 servers have certain support limits. The following URLs explain the processor and memory amount limitations for Red Hat Enterprise Linux: For host systems: https://access.redhat.com/articles/rhel-limits For the KVM hypervisor: https://access.redhat.com/articles/rhel-kvm-limits The following URL lists guest operating systems certified to run on a Red Hat Enterprise Linux KVM host: https://access.redhat.com/articles/973163 Note For additional information on the KVM hypervisor's restrictions and support limits, see Appendix C, Virtualization Restrictions .

Commands:
3.3. NIS Important Before NIS can be configured as an identity store, NIS itself must be configured for the environment: A NIS server must be fully configured with user accounts set up. The ypbind package must be installed on the local system. This is required for NIS services, but is not installed by default. The portmap and ypbind services are started and enabled to start at boot time. This should be configured as part of the ypbind package installation. 3.3.1. Configuring NIS Authentication from the UI Open the authconfig UI, as in Section 2.2.3, "Launching the authconfig UI" . Select NIS in the User Account Database drop-down menu. Set the information to connect to the NIS server, meaning the NIS domain name and the server host name. If the NIS server is not specified, the authconfig daemon scans for the NIS server. Select the authentication method. NIS allows simple password authentication or Kerberos authentication. Using Kerberos is described in Section 4.3.1, "Configuring Kerberos Authentication from the UI" . 3.3.2. Configuring NIS from the Command Line To use a NIS identity store, use the --enablenis . This automatically uses NIS authentication, unless the Kerberos parameters are explicitly set ( Section 4.3.2, "Configuring Kerberos Authentication from the Command Line" ). The only parameters are to identify the NIS server and NIS domain; if these are not used, then the authconfig service scans the network for NIS servers.

Commands:
authconfig --enablenis --nisdomain=EXAMPLE --nisserver=nis.example.com --update
4.154. libxklavier 4.154.1. RHBA-2012:0005 - libxklavier bug fix update An updated libxklavier package that fixes one bug is now available for Red Hat Enterprise Linux 6. The libxklavier library provides a high-level API for the X Keyboard Extension (XKB) that allows extended keyboard control. This library supports X.Org and other commercial implementations of the X Window system. The library is useful for creating XKB-related software, such as layout indicators. This update fixes the following bug: BZ# 767267 Due to the way how the NoMachine NX Free Edition server implements XInput support, an attempt to log into the server using an NX or VNC client triggered an XInput error that was handled incorrectly by the libxklavier library. Consequently, the GNOME Settings Daemon (gnome-settings-daemon) was terminated with signal 6 (SIGABRT). To resolve this problem, the XInput error handling routine in the libxklavier library has been modified. The library now ignores this error and gnome-settings-daemon runs correctly under these conditions. All users of libxklavier are advised to upgrade to this updated package, which fixes this bug.

Commands: