mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 5. LVM Configuration Examples This chapter provides some basic LVM configuration examples. 5.1. Creating an LVM Logical Volume on Three Disks This example creates an LVM logical volume called new_logical_volume that consists of the disks at /dev/sda1 , /dev/sdb1 , and /dev/sdc1 . 5.1.1. Creating the Physical Volumes To use disks in a volume group, you label them as LVM physical volumes. Warning This command destroys any data on /dev/sda1 , /dev/sdb1 , and /dev/sdc1 . 5.1.2. Creating the Volume Group The following command creates the volume group new_vol_group . You can use the vgs command to display the attributes of the new volume group. 5.1.3. Creating the Logical Volume The following command creates the logical volume new_logical_volume from the volume group new_vol_group . This example creates a logical volume that uses 2GB of the volume group. 5.1.4. Creating the File System The following command creates a GFS file system on the logical volume. The following commands mount the logical volume and report the file system disk space usage.

Commands:
pvcreate /dev/sda1 /dev/sdb1 /dev/sdc1 Physical volume "/dev/sda1" successfully created Physical volume "/dev/sdb1" successfully created Physical volume "/dev/sdc1" successfully created
vgcreate new_vol_group /dev/sda1 /dev/sdb1 /dev/sdc1 Volume group "new_vol_group" successfully created
vgs VG #PV #LV #SN Attr VSize VFree new_vol_group 3 0 0 wz--n- 51.45G 51.45G
lvcreate -L2G -n new_logical_volume new_vol_group Logical volume "new_logical_volume" created
gfs_mkfs -plock_nolock -j 1 /dev/new_vol_group/new_logical_volume This will destroy any data on /dev/new_vol_group/new_logical_volume. Are you sure you want to proceed? [y/n] y Device: /dev/new_vol_group/new_logical_volume Blocksize: 4096 Filesystem Size: 491460 Journals: 1 Resource Groups: 8 Locking Protocol: lock_nolock Lock Table: Syncing All Done
mount /dev/new_vol_group/new_logical_volume /mnt df Filesystem 1K-blocks Used Available Use% Mounted on /dev/new_vol_group/new_logical_volume 1965840 20 1965820 1% /mnt
10.2.4. User and System Connections NetworkManager connections are always either user connections or system connections . Depending on the system-specific policy that the administrator has configured, users may need root privileges to create and modify system connections. NetworkManager 's default policy enables users to create and modify user connections, but requires them to have root privileges to add, modify or delete system connections. User connections are so-called because they are specific to the user who creates them. In contrast to system connections, whose configurations are stored under the /etc/sysconfig/network-scripts/ directory (mainly in ifcfg- <network_type> interface configuration files), user connection settings are stored in the GConf configuration database and the GNOME keyring, and are only available during login sessions for the user who created them. Thus, logging out of the desktop session causes user-specific connections to become unavailable. Note Because NetworkManager uses the GConf and GNOME keyring applications to store user connection settings, and because these settings are specific to your desktop session, it is highly recommended to configure your personal VPN connections as user connections. If you do so, other Non- root users on the system cannot view or access these connections in any way. System connections, on the other hand, become available at boot time and can be used by other users on the system without first logging in to a desktop session. NetworkManager can quickly and conveniently convert user to system connections and vice versa. Converting a user connection to a system connection causes NetworkManager to create the relevant interface configuration files under the /etc/sysconfig/network-scripts/ directory, and to delete the GConf settings from the user's session. Conversely, converting a system to a user-specific connection causes NetworkManager to remove the system-wide configuration files and create the corresponding GConf/GNOME keyring settings. Figure 10.5. The Available to all users check box controls whether connections are user-specific or system-wide Procedure 10.2. Changing a Connection to be User-Specific instead of System-Wide, or Vice-Versa Note Depending on the system's policy, you may need root privileges on the system in order to change whether a connection is user-specific or system-wide. Right-click on the NetworkManager applet icon in the Notification Area and click Edit Connections . The Network Connections window appears. If needed, select the arrow head (on the left hand side) to hide and reveal the types of available network connections. Select the specific connection that you want to configure and click Edit . Check the Available to all users check box to ask NetworkManager to make the connection a system-wide connection. Depending on system policy, you may then be prompted for the root password by the PolicyKit application. If so, enter the root password to finalize the change. Conversely, uncheck the Available to all users check box to make the connection user-specific.

Commands:
14.7.5. Displaying CPU Statistics The nodecpustats command displays statistical information about the specified CPU, if the CPU is given. If not, it will display the CPU status of the node. If a percent is specified, it will display the percentage of each type of CPU statistics that were recorded over an one (1) second interval. This example shows no CPU specified: This example shows the statistical percentages for CPU number 2: You can control the behavior of the rebooting guest virtual machine by modifying the on_reboot element in the guest virtual machine's configuration file.

Commands:
virsh nodecpustats user: 1056442260000000 system: 401675280000000 idle: 7549613380000000 iowait: 94593570000000
virsh nodecpustats 2 --percent usage: 2.0% user: 1.0% system: 1.0% idle: 98.0% iowait: 0.0%
function::print_ustack Name function::print_ustack - Print out stack for the current task from string. EXPERIMENTAL! Synopsis Arguments stk String with list of hexadecimal addresses for the current task. Description Perform a symbolic lookup of the addresses in the given string, which is assumed to be the result of a prior call to ubacktrace for the current task. Print one line per address, including the address, the name of the function containing the address, and an estimate of its position within that function. Return nothing.

Commands:
function print_ustack(stk:string)
1.4. Document Overview This remainder of this document includes the following chapters: Chapter 2, LVM Components describes the components that make up an LVM logical volume. Chapter 3, LVM Administration Overview provides an overview of the basic steps you perform to configure LVM logical volumes, whether you are using the LVM Command Line Interface (CLI) commands or the LVM Graphical User Interface (GUI). Chapter 4, LVM Administration with CLI Commands summarizes the individual administrative tasks you can perform with the LVM CLI commands to create and maintain logical volumes. Chapter 5, LVM Configuration Examples provides a variety of LVM configuration examples. Chapter 6, LVM Troubleshooting provide instructions for troubleshooting a variety of LVM issues. Chapter 7, LVM Administration with the LVM GUI summarizes the operating of the LVM GUI. Appendix A, The Device Mapper describes the Device Mapper that LVM uses to map logical and physical volumes. Appendix B, The LVM Configuration Files describes the LVM configuration files. Appendix C, LVM Object Tags describes LVM object tags and host tags. Appendix D, LVM Volume Group Metadata describes LVM volume group metadata, and includes a sample copy of metadata for an LVM volume group.

Commands:
A.2. Cluster Creation with Pacemaker in Red Hat Enterprise Linux Release 6.5 and Red Hat Enterprise Linux Release 6.6 (and later) To create a Pacemaker cluster in Red Hat Enterprise Linux 6.5, you must create the cluster and start the cluster services on each node in the cluster. For example, to create a cluster named my_cluster that consists of nodes z1-rhel65.example.com and z2-rhel65.example.com and start cluster services on those nodes, run the following commands from both z1-rhel65.example.com and z2-rhel65.example.com . In Red Hat Enterprise Linux 6.6 and later, you run the cluster creation command from one node of the cluster. The following command, run from one node only, creates the cluster named my_cluster that consists of nodes z1-rhel66.example.com and z2-rhel66.example.com and starts cluster services on those nodes.

Commands:
pcs cluster setup --name my_cluster z1-rhel65.example.com z2-rhel65.example.com pcs cluster start
pcs cluster setup --name my_cluster z1-rhel65.example.com z2-rhel65.example.com pcs cluster start
pcs cluster setup --start --name my_cluster z1-rhel66.example.com z2-rhel66.example.com
Chapter 11. Accessing the CUPS logs in the systemd journal By default, CUPS stores log messages in the systemd journal. This includes: Error messages Access log entries Page log entries Prerequisites CUPS is installed . Procedure Display the log entries: To display all log entries, enter: To display the log entries for a specific print job, enter: To display log entries within a specific time frame, enter: Replace YYYY with the year, MM with the month, and DD with the day. Additional resources journalctl(1) man page on your system

Commands:
journalctl -u cups
journalctl -u cups JID= <print_job_id>
journalectl -u cups --since= <YYYY-MM-DD> --until= <YYYY-MM-DD>
Chapter 11. Enabling encryption on a vSphere cluster You can encrypt your virtual machines after installing OpenShift Container Platform 4.16 on vSphere by draining and shutting down your nodes one at a time. While each virtual machine is shutdown, you can enable encryption in the vCenter web interface. 11.1. Encrypting virtual machines You can encrypt your virtual machines with the following process. You can drain your virtual machines, power them down and encrypt them using the vCenter interface. Finally, you can create a storage class to use the encrypted storage. Prerequisites You have configured a Standard key provider in vSphere. For more information, see Adding a KMS to vCenter Server . Important The Native key provider in vCenter is not supported. For more information, see vSphere Native Key Provider Overview . You have enabled host encryption mode on all of the ESXi hosts that are hosting the cluster. For more information, see Enabling host encryption mode . You have a vSphere account which has all cryptographic privileges enabled. For more information, see Cryptographic Operations Privileges . Procedure Drain and cordon one of your nodes. For detailed instructions on node management, see "Working with Nodes". Shutdown the virtual machine associated with that node in the vCenter interface. Right-click on the virtual machine in the vCenter interface and select VM Policies Edit VM Storage Policies . Select an encrypted storage policy and select OK . Start the encrypted virtual machine in the vCenter interface. Repeat steps 1-5 for all nodes that you want to encrypt. Configure a storage class that uses the encrypted storage policy. For more information about configuring an encrypted storage class, see "VMware vSphere CSI Driver Operator". 11.2. Additional resources Working with nodes vSphere encryption Requirements for encrypting virtual machines

Commands:
5.181. mailman 5.181.1. RHBA-2012:1474 - mailman bug fix update Updated mailman packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. Mailman is a program used to help manage e-mail discussion lists. Bug Fixes BZ# 772998 The reset_pw.py script contained a typo, which could cause the mailman utility to fail with a traceback. The typo has been corrected, and mailman now works as expected. BZ# 799323 The "urlhost" argument was not handled in the newlist script. When running the "newlist" command with the "--urlhost" argument specified, the contents of the index archive page was not created using proper URLs; the hostname was used instead. With this update, "urlhost" is now handled in the newlist script. If the "--urlhost" argument is specified on the command line, the host URL is used when creating the index archive page instead of the hostname. BZ# 832920 Previously, long lines in e-mails were not wrapped in the web archive, sometimes requiring excessive horizontal scrolling. The "white-space: pre-wrap;" CSS style has been added to all templates, so that long lines are now wrapped in browsers that support that style. BZ# 834023 The "From" string in the e-mail body was not escaped properly. A message containing the "From" string at the beginning of a line was split and displayed in the web archive as two or more messages. The "From" string is now correctly escaped, and messages are no longer split in the described scenario. All users of mailman are advised to upgrade to these updated packages, which fix these bugs.

Commands:
1.5. Pacemaker Configuration and Management Tools Pacemaker features two configuration tools for cluster deployment, monitoring, and management. pcs pcs can control all aspects of Pacemaker and the Corosync heartbeat daemon. A command-line based program, pcs can perform the following cluster management tasks: Create and configure a Pacemaker/Corosync cluster Modify configuration of the cluster while it is running Remotely configure both Pacemaker and Corosync remotely as well as start, stop, and display status information of the cluster pcsd Web UI A graphical user interface to create and configure Pacemaker/Corosync clusters, with the same features and abilities as the command-line based pcs utility.

Commands:
14.2.6. Extending a Volume Group In this example, the objective was to extend the new volume group to include an uninitialized entity (partition). Doing so increases the size or number of extents for the volume group. To extend the volume group, ensure that on the left pane the Physical View option is selected within the desired Volume Group. Then click on the Extend Volume Group button. This will display the 'Extend Volume Group' window as illustrated below. On the 'Extend Volume Group' window, you can select disk entities (partitions) to add to the volume group. Ensure that you check the contents of any 'Uninitialized Disk Entities' (partitions) to avoid deleting any critical data (see Figure 14.13, "Uninitialized hard disk" ). In the example, the disk entity (partition) /dev/hda6 was selected as illustrated below. Figure 14.15. Select disk entities Once added, the new volume will be added as 'Unused Space' in the volume group. The figure below illustrates the logical and physical view of the volume group after it was extended. Figure 14.16. Logical and physical view of an extended volume group

Commands:
Chapter 3. Options for embedding applications in a RHEL for Edge image You can embed microservices-based workloads and applications in a Red Hat Enterprise Linux for Edge (RHEL for Edge) image to run in a MicroShift cluster. Embedded applications can be installed directly on edge devices to run in disconnected or offline environments. 3.1. Adding application RPMs to an rpm-ostree image If you have an application that includes APIs, container images, and configuration files for deployment such as manifests, you can build application RPMs. You can then add the RPMs to your RHEL for Edge system image. The following is an outline of the procedures to embed applications or workloads in a fully self-contained operating system image: Build your own RPM that includes your application manifest. Add the RPM to the blueprint you used to install Red Hat build of MicroShift. Add the workload container images to the same blueprint. Create a bootable ISO. For a step-by-step tutorial about preparing and embedding applications in a RHEL for Edge image, use the following tutorial: Embedding applications tutorial 3.2. Adding application manifests to an image for offline use If you have a simple application that includes a few files for deployment such as manifests, you can add those manifests directly to a RHEL for Edge system image. See the "Create a custom file blueprint customization" section of the following RHEL for Edge documentation for an example: Create a custom file blueprint customization 3.3. Embedding applications for offline use If you have an application that includes more than a few files, you can embed the application for offline use. See the following procedure: Embedding applications for offline use 3.4. Additional resources Embedding Red Hat build of MicroShift in an RPM-OSTree image Composing, installing, and managing RHEL for Edge images Preparing for image building Meet Red Hat Device Edge Composing a RHEL for Edge image using image builder command-line Image Builder system requirements

Commands:
Chapter 19. JMX Navigator The JMX Navigator view, shown in Figure 19.1, "JMX Navigator view" , displays all processes that are running in your application and it drives all interactions with the monitoring and testing features. Other areas of the Fuse Integration perspective adapt to display information related to the node selected in the JMX Navigator view. In the JMX Navigator view, its context menu provides the commands needed to activate route tracing and to add JMS destinations. Figure 19.1. JMX Navigator view By default, the JMX Navigator view discovers all JMX servers running on the local machine and lists them under the following categories: Local Processes Server Connections User-Defined Connections Note You can add other JMX servers by using a server's JMX URL. For details, see Section 19.2, "Adding a JMX server" . 19.1. Viewing Processes in JMX Overview The JMX Navigator view lists all known processes in a series of trees. The root for each tree is a JMX server. The first tree in the list is a special Local Processes tree that contains all JMX servers that are running on the local machine. You must connect to one of the JMX servers to see the processes it contains. Viewing processes in a local JMX server To view information about processes in a local JMX server: In the JMX Navigator view, expand Local Processes . Under Local Processes , double-click one of the top-level entries to connect to it. Click the icon that appears to the entry to display a list of its components that are running in the JVM. Viewing processes in alternate JMX servers To view information about processes in an alternate JMX server: Section 19.2, "Adding a JMX server" the JMX server to the JMX Navigator view. In the JMX Navigator view, expand the server's entry by using the icon that appears to the entry. This displays a list of that JMX server's components that are running in the JVM. 19.2. Adding a JMX server Overview In the JMX Navigator view, under the Local Processes branch of the tree, you can see a list of all local JMX servers. You may need to connect to specific JMX servers to see components deployed on other machines. To add a JMX server, you must know the JMX URL of the server you want to add. Procedure To add a JMX server to the JMX Navigator view: In the JMX Navigator view, click New Connection . In the Create a new JMX connection wizard, select Default JMX Connection . Click . Select the Advanced tab. In the Name field, enter a name for the JMX server. The name can be any string. It is used to label the entry in the JMX Navigator tree. In the JMX URL field, enter the JMX URL of the server. If the JMX server requires authentication, enter your user name and password in the Username and Password fields. Click Finish . The new JMX server appears as a branch in the User-Defined Connections tree.

Commands:
10.5.37. LogFormat The LogFormat directive configures the format of the various Web server log files. The actual LogFormat used depends on the settings given in the CustomLog directive (refer to Section 10.5.38, " CustomLog " ). The following are the format options if the CustomLog directive is set to combined : %h (remote host's IP address or hostname) Lists the remote IP address of the requesting client. If HostnameLookups is set to on , the client hostname is recorded unless it is not available from DNS. %l (rfc931) Not used. A hyphen - appears in the log file for this field. %u (authenticated user) Lists the username of the user recorded if authentication was required. Usually, this is not used, so a hyphen - appears in the log file for this field. %t (date) Lists the date and time of the request. %r (request string) Lists the request string exactly as it came from the browser or client. %s (status) Lists the HTTP status code which was returned to the client host. %b (bytes) Lists the size of the document. %\"%{Referer}i\" (referrer) Lists the URL of the webpage which referred the client host to Web server. %\"%{User-Agent}i\" (user-agent) Lists the type of Web browser making the request.

Commands:
Chapter 2. Requirements for scaling storage Before you proceed to scale the storage nodes, refer to the following sections to understand the node requirements for your specific Red Hat OpenShift Data Foundation instance: Platform requirements Resource requirements Storage device requirements Dynamic storage devices Local storage devices Capacity planning Important Always ensure that you have plenty of storage capacity. If storage ever fills completely, it is not possible to add capacity or delete or migrate content away from the storage to free up space completely. Full storage is very difficult to recover. Capacity alerts are issued when cluster storage capacity reaches 75% (near-full) and 85% (full) of total capacity. Always address capacity warnings promptly, and review your storage regularly to ensure that you do not run out of storage space. If storage capacity reaches 85% full state, Ceph may report HEALTH_ERR and prevent IO operations. In this case, you can increase the full ratio temporarily so that cluster rebalance can take place. For steps to increase the full ratio, see Setting Ceph OSD full thresholds using the ODF CLI tool . If you do run out of storage space completely, contact Red Hat Customer Support .

Commands:
Chapter 7. Advisories related to this release The following advisories are issued to document bug fixes and CVE fixes included in this release: RHSA-2023:6738 RHSA-2023:6887 RHEA-2023:6888 RHSA-2023:6889 RHBA-2023:6897 RHBA-2023:6898 Revised on 2024-05-09 14:50:03 UTC

Commands:
Chapter 23. Configuring Direct Deploy When provisioning nodes, director mounts the overcloud base operating system image on an iSCSI mount and then copies the image to disk on each node. Direct deploy is an alternative method that writes disk images from a HTTP location directly to disk on bare metal nodes. 23.1. Configuring the direct deploy interface on the undercloud The iSCSI deploy interface is the default deploy interface. However, you can enable the direct deploy interface to download an image from a HTTP location to the target disk. Note Your overcloud node memory tmpfs must have at least 8GB of RAM. Procedure Create or modify a custom environment file /home/stack/undercloud_custom_env.yaml and specify the IronicDefaultDeployInterface . By default, the Bare Metal service (ironic) agent on each node obtains the image stored in the Object Storage service (swift) through a HTTP link. Alternatively, ironic can stream this image directly to the node through the ironic-conductor HTTP server. To change the service that provides the image, set the IronicImageDownloadSource to http in the /home/stack/undercloud_custom_env.yaml file: Include the custom environment file in the DEFAULT section of the undercloud.conf file. Perform the undercloud installation:

Commands:
parameter_defaults: IronicDefaultDeployInterface: direct
parameter_defaults: IronicDefaultDeployInterface: direct IronicImageDownloadSource: http
custom_env_files = /home/stack/undercloud_custom_env.yaml
openstack undercloud install