mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Configuring debug verbosity of Ceph components You can configure verbosity of Ceph components by enabling or increasing the log debugging for a specific Ceph subsystem from OpenShift Data Foundation. For information about the Ceph subsystems and the log levels that can be updated, see Ceph subsystems default logging level values . Prerequisites Ensure that the OpenShift Data Foundation cluster is installed. Ensure that the OpenShift Data Foundation command-line interface tool is installed. Clone the following repository: Change the directory and build the binary. Use the binary present in the/bin/ directory to run the commands: Procedure Set log level for Ceph daemons: where ceph-subsystem can be osd , mds , or mon . For example,

Commands:
git clone https://github.com/red-hat-storage/odf-cli.git
cd odf-cli/ && make build
./bin/odf -h
odf set ceph log-level <ceph-subsystem1> <ceph-subsystem2> <log-level>
odf set ceph log-level osd crush 20
odf set ceph log-level mds crush 20
odf set ceph log-level mon crush 20
19.2. Remove Red Hat JBoss Data Grid from Your Windows System The following procedures contain instructions to remove Red Hat JBoss Data Grid from your Microsoft Windows system. Warning Once deleted, all JBoss Data Grid configuration and settings are permanently lost. Procedure 19.2. Remove JBoss Data Grid from Your Windows System Shut Down Server Ensure that the JBoss Data Grid server is shut down. Navigate to the JBoss Data Grid Home Directory Use the Windows Explorer to navigate to the directory in which the USDJDG_HOME folder is located. Delete the JBoss Data Grid Home Directory Select the USDJDG_HOME folder and delete it. Report a bug

Commands:
Chapter 4. Technology previews This section describes the technology preview features introduced in Red Hat OpenShift Data Foundation 4.14 under Technology Preview support limitations. Important 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. Technology Preview features are provided with a limited support scope, as detailed on the Customer Portal: Technology Preview Features Support Scope . 4.1. Allow storage classes to use non resilient pool single replica OpenShift Data Foundation allows the option to create a new storage class using non resilient pool with a single replica. This avoids redundant data copies and allows resiliency management on the application level. For more information, see the deployment guide for your platform on the customer portal . 4.2. Metro-DR support for workloads based on OpenShift Virtualization You can now easily set up Metro-DR to protect your workloads based on OpenShift Virtualization using OpenShift Data Foundation. For more information, see Knowledgebase article .

Commands:
Chapter 7. Federal Information Processing Standard (FIPS) Red Hat Ceph Storage uses FIPS validated cryptography modules when run on Red Hat Enterprise Linux 8.4. Enable FIPS mode on Red Hat Enterprise Linux either during system installation or after it. For container deployments, follow the instructions in the Red Hat Enterprise Linux 8 Security Hardening Guide . Additional Resources Refer to the US Government Standards to know the latest information on FIPS validations.

Commands:
11.3. View A view is a virtual table. A view contains rows and columns,like a real table. The fields in a view are fields from one or more real tables from the source or other view models. They can also be expressions made up multiple columns, or aggregated columns. When column definitions are not defined on the view table, they will be derived from the projected columns of the view's select transformation that is defined after the AS keyword. You can add functions, JOIN statements and WHERE clauses to a view data as if the data were coming from one single table. This is how you create a view table on a virtual model:

Commands:
CREATE VIEW CustomerOrders (name varchar(50), saledate date, amount decimal) OPTIONS (CARDINALITY 100, ANNOTATION 'Example') AS SELECT concat(c.firstname, c.lastname) as name, o.saledate as saledate, o.amount as amount FROM Customer C JOIN Order o ON c.id = o.customerid;
4.7. Additional Resources This section includes various resources that can be used to learn more about resource monitoring and the Red Hat Enterprise Linux-specific subject matter discussed in this chapter. 4.7.1. Installed Documentation The following resources are installed in the course of a typical Red Hat Enterprise Linux installation and can help you learn more about the subject matter discussed in this chapter. free(1) man page -- Learn how to display free and used memory statistics. vmstat(8) man page -- Learn how to display a concise overview of process, memory, swap, I/O, system, and CPU utilization. sar(1) man page -- Learn how to produce system resource utilization reports. sa2(8) man page -- Learn how to produce daily system resource utilization report files.

Commands:
5.85. glib2 5.85.1. RHBA-2012:0794 - glib2 bug fix update Updated glib2 packages that fix one bug are now available for Red Hat Enterprise Linux 6. GLib is a low-level core library that forms the basis for projects such as GTK+ and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system. Bug Fix BZ# 782194 Prior to this upate, the gtester-report script was not marked as executable in the glib2-devel package. As a consequence, the gtester-report did not run with the default permissions. This update changes the glib2-devel package definition so that this script is now executable. All users are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 21. Guest Virtual Machine Disk Access with Offline Tools 21.1. Introduction Red Hat Enterprise Linux 7 provides a number of libguestfs utilities that enable accessing, editing, and creating guest virtual machine disks or other disk images. There are multiple uses for these tools, including: Viewing or downloading files located on a guest virtual machine disk. Editing or uploading files on a guest virtual machine disk. Reading or writing guest virtual machine configuration. Preparing new disk images containing files, directories, file systems, partitions, logical volumes and other options. Rescuing and repairing guest virtual machines that fail to boot or those that need boot configuration changes. Monitoring disk usage of guest virtual machines. Auditing compliance of guest virtual machines, for example to organizational security standards. Deploying guest virtual machines by cloning and modifying templates. Reading CD and DVD ISO images and floppy disk images. Warning You must never use the utilities listed in this chapter to write to a guest virtual machine or disk image that is attached to a running virtual machine, not even to open such a disk image in write mode. Doing so will result in disk corruption of the guest virtual machine. The tools try to prevent you from doing this, but do not secure all cases. If there is any suspicion that a guest virtual machine might be running, Red Hat strongly recommends not using the utilities. For increased safety, certain utilities can be used in read-only mode (using the --ro option), which does not save the changes. Note The primary source for documentation for libguestfs and the related utilities are the Linux man pages. The API is documented in guestfs(3) , guestfish is documented in guestfish(1) , and the virtualization utilities are documented in their own man pages (such as virt-df(1) ). For troubleshooting information, see Section A.17, "libguestfs Troubleshooting" 21.1.1. Caution about Using Remote Connections Some virtualization commands in Red Hat Enterprise Linux 7 allow you to specify a remote libvirt connection. For example: However, libguestfs utilities in Red Hat Enterprise Linux 7 cannot access the disks of remote libvirt guests, and commands using remote URLs as shown above do not work as expected. Nevertheless, beginning with Red Hat Enterprise Linux 7, libguestfs can access remote disk sources over network block device (NBD). You can export a disk image from a remote machine using the qemu-nbd command, and access it using a nbd:// URL. You may need to open a port on your firewall (port 10809) as shown here: On the remote system: qemu-nbd -t disk.img On the local system: virt-df -a nbd://remote The following libguestfs commands are affected: guestfish guestmount virt-alignment-scan virt-cat virt-copy-in virt-copy-out virt-df virt-edit virt-filesystems virt-inspector virt-ls virt-rescue virt-sysprep virt-tar-in virt-tar-out virt-win-reg

Commands:
virt-df -c qemu:// remote/system -d Guest
5.5.2.3. Tracking of File Creation, Access, Modification Times Most file systems keep track of the time at which a file was created; some also track modification and access times. Over and above the convenience of being able to determine when a given file was created, accessed, or modified, these dates are vital for the proper operation of incremental backups. More information on how backups make use of these file system features can be found in Section 8.2, "Backups" .

Commands:
10.5.42. Redirect When a webpage is moved, Redirect can be used to map the file location to a new URL. The format is as follows: In this example, replace <old-path> with the old path information for <file-name> and <current-domain> and <current-path> with the current domain and path information for <file-name> . In this example, any requests for <file-name> at the old location is automatically redirected to the new location. For more advanced redirection techniques, use the mod_rewrite module included with the Apache HTTP Server. For more information about configuring the mod_rewrite module, refer to the Apache Software Foundation documentation online at http://httpd.apache.org/docs-2.0/mod/mod_rewrite.html .

Commands:
Redirect / <old-path> / <file-name> http:// <current-domain> / <current-path> / <file-name>
Appendix A. Revision History Revision History Revision 0.0-1.10 Mon Aug 05 2019 Marie Dolezelova Version for 7.7 GA release. Revision 0.0-1.6 Wed Nov 11 2015 Jana Heves Version for 7.2 GA release. Revision 0.0-1.4 Thu Feb 19 2015 Radek Biba Version for 7.1 GA release. Linux Containers moved to a separate book. Revision 0.0-1.0 Mon Jul 21 2014 Peter Ondrejka Revision 0.0-0.14 Mon May 13 2013 Peter Ondrejka Version for 7.0 GA release

Commands:
2.2. Examples The following examples demonstrate how SELinux increases security: The default action is deny. If an SELinux policy rule does not exist to allow access, such as for a process opening a file, access is denied. SELinux can confine Linux users. A number of confined SELinux users exist in SELinux policy. Linux users can be mapped to confined SELinux users to take advantage of the security rules and mechanisms applied to them. For example, mapping a Linux user to the SELinux user_u user, results in a Linux user that is not able to run (unless configured otherwise) set user ID (setuid) applications, such as sudo and su , as well as preventing them from executing files and applications in their home directory. If configured, this prevents users from executing malicious files from their home directories. Process separation is used. Processes run in their own domains, preventing processes from accessing files used by other processes, as well as preventing processes from accessing other processes. For example, when running SELinux, unless otherwise configured, an attacker cannot compromise a Samba server, and then use that Samba server as an attack vector to read and write to files used by other processes, such as databases used by MySQL. SELinux helps limit the damage made by configuration mistakes. Domain Name System (DNS) servers often replicate information between each other in what is known as a zone transfer. Attackers can use zone transfers to update DNS servers with false information. When running the Berkeley Internet Name Domain (BIND) as a DNS server in Red Hat Enterprise Linux, even if an administrator forgets to limit which servers can perform a zone transfer, the default SELinux policy prevents zone files [3] from being updated via zone transfers, by the BIND named daemon itself, and by other processes. Refer to the Red Hat Magazine article, Risk report: Three years of Red Hat Enterprise Linux 4 [4] , for exploits that were restricted due to the default SELinux targeted policy in Red Hat Enterprise Linux 4. Refer to the NetworkWorld.com article, A seatbelt for server software: SELinux blocks real-world exploits [5] , for background information about SELinux, and information about various exploits that SELinux has prevented. Refer to James Morris's SELinux mitigates remote root vulnerability in OpenPegasus blog post for information about an exploit in OpenPegasus that was mitigated by SELinux as shipped with Red Hat Enterprise Linux 4 and 5. [3] Text files that include information, such as host name to IP address mappings, that are used by DNS servers. [4] Cox, Mark. "Risk report: Three years of Red Hat Enterprise Linux 4". Published 26 February 2008. Accessed 27 August 2009: http://magazine.redhat.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/ . [5] Marti, Don. "A seatbelt for server software: SELinux blocks real-world exploits". Published 24 February 2008. Accessed 27 August 2009: http://www.networkworld.com/article/2283723/lan-wan/a-seatbelt-for-server-software--selinux-blocks-real-world-exploits.html .

Commands:
Appendix E. The GRUB Boot Loader When a computer running Linux is turned on, the operating system is loaded into memory by a special program called a boot loader . A boot loader usually exists on the system's primary hard drive (or other media device) and has the sole responsibility of loading the Linux kernel with its required files or (in some cases) other operating systems into memory. E.1. Boot Loaders and System Architecture Each architecture capable of running Red Hat Enterprise Linux uses a different boot loader. The following table lists the boot loaders available for each architecture: Table E.1. Boot Loaders by Architecture Architecture Boot Loaders AMD AMD64 GRUB IBM Power Systems yaboot IBM System z z/IPL x86 GRUB This appendix discusses commands and configuration options for the GRUB boot loader included with Red Hat Enterprise Linux for the x86 architecture. Important The /boot and / (root) partition in Red Hat Enterprise Linux 6.9 can only use the ext2, ext3, and ext4 (recommended) file systems. You cannot use any other file system for this partition, such as Btrfs, XFS, or VFAT. Other partitions, such as /home , can use any supported file system, including Btrfs and XFS (if available). See the following article on the Red Hat Customer Portal for additional information: https://access.redhat.com/solutions/667273 .

Commands:
Chapter 1. Introduction Red Hat OpenStack Platform director creates a cloud environment called the Overcloud . The Overcloud contains a set of different node types that perform certain roles. One of these node types is the Controller node. The Controller is responsible for Overcloud administration and uses specific OpenStack components. An Overcloud uses multiple Controllers together as a high availability cluster, which ensures maximum operational performance for your OpenStack services. In addition, the cluster provides load balancing for access to the OpenStack services, which evenly distributes traffic to the Controller nodes and reduces server overload for each node. It is also possible to use an external load balancer to perform this distribution. For example, an organization might use their own hardware-based load balancer to handle traffic distribution to the Controller nodes. This guide provides the necessary details to help define the configuration for both an external load balancer and the Overcloud creation. This involved the following process: Installing and Configuring the Load Balancer - This guide includes some HAProxy options for load balancing and services. Translate the settings to the equivalent of your own external load balancer. Configuring and Deploying the Overcloud - This guide includes some Heat template parameters help the Overcloud integrate with the external load balancer. This mainly involves the IP addresses of the load balancer and potential nodes. This guide also includes the command to start the Overcloud deployment and its configuration to use the external load balancer. 1.1. Using Load Balancing in the Overcloud The Overcloud uses a open source tool called HAProxy . HAProxy load-balances traffic to Controller nodes running OpenStack services. The haproxy package contains the haproxy daemon, which is started from the haproxy systemd service, along with logging features and sample configurations. However, the Overcloud also uses a high availability resource manager (Pacemaker) to control HAProxy itself as a highly available service (haproxy-clone). This means HAProxy runs on each Controller node and distributes traffic according to a set of rules defined in each configuration. 1.2. Defining an Example Scenario This article uses the following scenario as an example: An external load balacing server using HAProxy. This demonstrates how to use a federated HAProxy server. You can substitute this for another supported external load balancer. One OpenStack Platform director node An Overcloud that consists of: 3 Controller nodes in a highly available cluster 1 Compute node Network isolation with VLANs The scenario uses the following IP address assignments for each network: Internal API: 172.16.20.0/24 Project: 172.16.22.0/24 Storage: 172.16.21.0/24 Storage Management: 172.16.19.0/24 External: 172.16.23.0/24 These IP ranges will include IP assignments for the Controller nodes and virtual IPs that the load balancer binds to OpenStack services.

Commands:
9.11. Initializing the Hard Disk If no readable partition tables are found on existing hard disks, the installation program asks to initialize the hard disk. This operation makes any existing data on the hard disk unreadable. If your system has a brand new hard disk with no operating system installed, or you have removed all partitions on the hard disk, click Re-initialize drive . The installation program presents you with a separate dialog for each disk on which it cannot read a valid partition table. Click the Ignore all button or Re-initialize all button to apply the same answer to all devices. Figure 9.34. Warning screen - initializing hard drive Certain RAID systems or other nonstandard configurations may be unreadable to the installation program and the prompt to initialize the hard disk may appear. The installation program responds to the physical disk structures it is able to detect. To enable automatic initializing of hard disks for which it turns out to be necessary, use the kickstart command zerombr (refer to Chapter 32, Kickstart Installations ). This command is required when performing an unattended installation on a system with previously initialized disks. Warning If you have a nonstandard disk configuration that can be detached during installation and detected and configured afterward, power off the system, detach it, and restart the installation.

Commands:
Chapter 1. About instances Instances are the individual virtual machines that run on physical Compute nodes inside the cloud. To launch an instance, you need a flavor and either an image or a bootable volume. When you use an image to launch an instance, the provided image becomes the base image that contains a virtual disk installed with a bootable operating system. Each instance requires a root disk, which we refer to as the instance disk. The Compute service (nova) resizes the instance disk to match the specifications of the flavor that you specified for the instance. Images are managed by the Image Service (glance). The Image Service image store contains a number of predefined images. The Compute nodes provide the available vCPU, memory, and local disk resources for instances. The Block Storage service (cinder) provides predefined volumes. Instance disk data is stored either in ephemeral storage, which is deleted when you delete the instance, or in a persistent volume provided by the Block Storage service. The Compute service is the central component that provides instances on demand. The Compute service creates, schedules, and manages instances, and interacts with the Identity service for authentication, the Image service for the images used to launch instances, and the Dashboard service (horizon) for the user and administrative interface. As a cloud user, you interact with the Compute service when you create and manage your instances. You can create and manage your instances by using the OpenStack CLI or the Dashboard.

Commands:
Chapter 14. Authenticating third-party clients through RH-SSO To use the different remote services provided by Business Central or by KIE Server, your client, such as curl, wget, web browser, or a custom REST client, must authenticate through the RH-SSO server and have a valid token to perform the requests. To use the remote services, the authenticated user must have the following roles: rest-all for using Business Central remote services. kie-server for using the KIE Server remote services. Use the RH-SSO Admin Console to create these roles and assign them to the users that will consume the remote services. Your client can authenticate through RH-SSO using one of these options: Basic authentication, if it is supported by the client Token-based authentication 14.1. Basic authentication If you enabled basic authentication in the RH-SSO client adapter configuration for both Business Central and KIE Server, you can avoid the token grant and refresh calls and call the services as shown in the following examples: For web based remote repositories endpoint: For KIE Server:

Commands:
curl http://admin:password@localhost:8080/business-central/rest/repositories
curl http://admin:password@localhost:8080/kie-server/services/rest/server/
Chapter 3. Updating Ansible Automation Platform on OpenShift Container Platform You can use an upgrade patch to update your operator-based Ansible Automation Platform. 3.1. Patch updating Ansible Automation Platform on OpenShift Container Platform When you perform a patch update for an installation of Ansible Automation Platform on OpenShift Container Platform, most updates happen within a channel: A new update becomes available in the marketplace (through the redhat-operator CatalogSource). A new InstallPlan is automatically created for your Ansible Automation Platform subscription. If the subscription is set to Manual, the InstallPlan will need to be manually approved in the OpenShift UI. If the subscription is set to Automatic, it will upgrade as soon as the new version is available. Note It is recommended that you set a manual install strategy on your Ansible Automation Platform Operator subscription (set when installing or upgrading the Operator) and you will be prompted to approve an upgrade when it becomes available in your selected update channel. Stable channels for each X.Y release (for example, stable-2.5) are available. A new Subscription, CSV, and Operator containers will be created alongside the old Subscription, CSV, and containers. Then the old resources will be cleaned up if the new install was successful.

Commands: