mtpti5iD/redhat-docs_dataset huggingface dataset:
12.3. Directory-based Storage Pools This section covers storing guest virtual machines in a directory on the host physical machine. Directory-based storage pools can be created with virt-manager or the virsh command line tools. 12.3.1. Creating a Directory-based Storage Pool with virt-manager Create the local directory Optional: Create a new directory for the storage pool Create the directory on the host physical machine for the storage pool. This example uses a directory named /guest virtual machine_images . Set directory ownership Change the user and group ownership of the directory. The directory must be owned by the root user. Set directory permissions Change the file permissions of the directory. Verify the changes Verify the permissions were modified. The output shows a correctly configured empty directory. Configure SELinux file contexts Configure the correct SELinux context for the new directory. Note that the name of the pool and the directory do not have to match. However, when you shutdown the guest virtual machine, libvirt has to set the context back to a default value. The context of the directory determines what this default value is. It is worth explicitly labeling the directory virt_image_t, so that when the guest virtual machine is shutdown, the images get labeled 'virt_image_t' and are thus isolated from other processes running on the host physical machine. Open the storage pool settings In the virt-manager graphical interface, select the host physical machine from the main window. Open the Edit menu and select Connection Details Figure 12.7. Connection details window Click on the Storage tab of the Connection Details window. Figure 12.8. Storage tab Create the new storage pool Add a new pool (part 1) Press the + button (the add pool button). The Add a New Storage Pool wizard appears. Choose a Name for the storage pool. This example uses the name guest_images . Change the Type to dir: Filesystem Directory . Figure 12.9. Name the storage pool Press the Forward button to continue. Add a new pool (part 2) Change the Target Path field. For example, /guest_images . Verify the details and press the Finish button to create the storage pool. Verify the new storage pool The new storage pool appears in the storage list on the left after a few seconds. Verify the size is reported as expected, 36.41 GB Free in this example. Verify the State field reports the new storage pool as Active . Select the storage pool. In the Autostart field, confirm that the On Boot check box is checked. This will make sure the storage pool starts whenever the libvirtd service starts. Figure 12.10. Verify the storage pool information The storage pool is now created, close the Connection Details window.

Commands:
mkdir /guest_images
chown root:root /guest_images
chmod 700 /guest_images
ls -la /guest_images total 8 drwx------. 2 root root 4096 May 28 13:57 . dr-xr-xr-x. 26 root root 4096 May 28 13:57 ..
semanage fcontext -a -t virt_image_t '/guest_images(/.*)?' restorecon -R /guest_images
Chapter 6. Uninstalling a cluster on RHV You can remove an OpenShift Container Platform cluster from Red Hat Virtualization (RHV). 6.1. Removing a cluster that uses installer-provisioned infrastructure You can remove a cluster that uses installer-provisioned infrastructure from your cloud. Note After uninstallation, check your cloud provider for any resources not removed properly, especially with user-provisioned infrastructure clusters. There might be resources that the installation program did not create or that the installation program is unable to access. Prerequisites You have a copy of the installation program that you used to deploy the cluster. You have the files that the installation program generated when you created your cluster. Procedure On the computer that you used to install the cluster, go to the directory that contains the installation program, and run the following command: USD ./openshift-install destroy cluster \ --dir <installation_directory> --log-level info 1 2 1 For <installation_directory> , specify the path to the directory that you stored the installation files in. 2 To view different details, specify warn , debug , or error instead of info . Note You must specify the directory that contains the cluster definition files for your cluster. The installation program requires the metadata.json file in this directory to delete the cluster. Optional: Delete the <installation_directory> directory and the OpenShift Container Platform installation program. 6.2. Removing a cluster that uses user-provisioned infrastructure When you are finished using the cluster, you can remove a cluster that uses user-provisioned infrastructure from your cloud. Prerequisites Have the original playbook files, assets directory and files, and USDASSETS_DIR environment variable that you used to you install the cluster. Typically, you can achieve this by using the same computer you used when you installed the cluster. Procedure To remove the cluster, enter: USD ansible-playbook -i inventory.yml \ retire-bootstrap.yml \ retire-masters.yml \ retire-workers.yml Remove any configurations you added to DNS, load balancers, and any other infrastructure for this cluster.

Commands:
./openshift-install destroy cluster --dir <installation_directory> --log-level info 1 2
ansible-playbook -i inventory.yml retire-bootstrap.yml retire-masters.yml retire-workers.yml
B.51. lvm2 B.51.1. RHEA-2010:0994 - lvm2 enhancement update Updated lvm2 packages that add various enhancements are now available for Red Hat Enterprise Linux 6. The lvm2 packages contain support for Logical Volume Management (LVM). Enhancements BZ# 661741 Previously, the maximum length of a tag was limited to 128 characters. However, in certain cases, this may have been too restrictive. To remove this restriction, the lvm2 packages have been updated to support tags that are up to 1024 characters long. BZ# 661742 Due to technical limitations, a valid tag can consist of a limited range of characters only. With this update, the list of allowed characters has been extended, and tags can newly contain "/", "=", "!", ":", "#", and "&". Users are advised to upgrade to these updated lvm2 packages, which add these enhancements.

Commands:
B.23.2. RHSA-2010:0889 - Important: freetype security update Updated freetype packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. FreeType is a free, high-quality, portable font engine that can open and manage font files. It also loads, hints, and renders individual glyphs efficiently. The freetype packages for Red Hat Enterprise Linux 4 provide both the FreeType 1 and FreeType 2 font engines. The freetype packages for Red Hat Enterprise Linux 5 and 6 provide only the FreeType 2 font engine. CVE-2010-3855 A heap-based buffer overflow flaw was found in the way the FreeType font rendering engine processed certain TrueType GX fonts. If a user loaded a specially-crafted font file with an application linked against FreeType, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. Note Note: This issue only affects the FreeType 2 font engine. Users are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. The X server must be restarted (log out, then log back in) for this update to take effect.

Commands:
29.5.2. Using opreport on a Single Executable To retrieve more detailed profiled information about a specific executable, use opreport : executable must be the full path to the executable to be analyzed. mode must be one of the following: -l List sample data by symbols. For example, the following is part of the output from running the command opreport -l /lib/tls/libc- version .so : The first column is the number of samples for the symbol, the second column is the percentage of samples for this symbol relative to the overall samples for the executable, and the third column is the symbol name. To sort the output from the largest number of samples to the smallest (reverse order), use -r in conjunction with the -l option. -i symbol-name List sample data specific to a symbol name. For example, the following output is from the command opreport -l -i __gconv_transform_utf8_internal /lib/tls/libc- version .so : The first line is a summary for the symbol/executable combination. The first column is the number of samples for the memory symbol. The second column is the percentage of samples for the memory address relative to the total number of samples for the symbol. The third column is the symbol name. -d List sample data by symbols with more detail than -l . For example, the following output is from the command opreport -l -d __gconv_transform_utf8_internal /lib/tls/libc- version .so : The data is the same as the -l option except that for each symbol, each virtual memory address used is shown. For each virtual memory address, the number of samples and percentage of samples relative to the number of samples for the symbol is displayed. -x symbol-name Exclude the comma-separated list of symbols from the output. session : name Specify the full path to the session or a directory relative to the /var/lib/oprofile/samples/ directory.

Commands:
~]# opreport mode executable
samples % symbol name 12 21.4286 __gconv_transform_utf8_internal 5 8.9286 _int_malloc 4 7.1429 malloc 3 5.3571 __i686.get_pc_thunk.bx 3 5.3571 _dl_mcount_wrapper_check 3 5.3571 mbrtowc 3 5.3571 memcpy 2 3.5714 _int_realloc 2 3.5714 _nl_intern_locale_data 2 3.5714 free 2 3.5714 strcmp 1 1.7857 __ctype_get_mb_cur_max 1 1.7857 __unregister_atfork 1 1.7857 __write_nocancel 1 1.7857 _dl_addr 1 1.7857 _int_free 1 1.7857 _itoa_word 1 1.7857 calc_eclosure_iter 1 1.7857 fopen@@GLIBC_2.1 1 1.7857 getpid 1 1.7857 memmove 1 1.7857 msort_with_tmp 1 1.7857 strcpy 1 1.7857 strlen 1 1.7857 vfprintf 1 1.7857 write
samples % symbol name 12 100.000 __gconv_transform_utf8_internal
vma samples % symbol name 00a98640 12 100.000 __gconv_transform_utf8_internal 00a98640 1 8.3333 00a9868c 2 16.6667 00a9869a 1 8.3333 00a986c1 1 8.3333 00a98720 1 8.3333 00a98749 1 8.3333 00a98753 1 8.3333 00a98789 1 8.3333 00a98864 1 8.3333 00a98869 1 8.3333 00a98b08 1 8.3333
34.5. Kdump Use this screen to select whether or not to use Kdump on this system. Kdump is a kernel crash dumping mechanism. In the event of a system crash, Kdump will capture information from your system that can be invaluable in determining the cause of the crash. Note that if you select this option, you will need to reserve memory for Kdump and that this memory will not be available for any other purpose. Figure 34.16. Kdump screen If you do not want to use Kdump on this system, click Finish . If you want to use Kdump , select the Enable kdump option, then select an amount of memory to reserve for Kdump and click Finish . Figure 34.17. Kdump enabled

Commands:
8.103. keepalived 8.103.1. RHBA-2014:1510 - keepalived bug fix and enhancement update Updated keepalived packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The keepalived packages provide simple and robust facilities for load-balancing and high-availability. The load-balancing framework relies on the well-know and widely used Linux Virtual Server kernel module providing Layer4 network load-balancing. The keepalived daemon implements a set of health checkers to load-balanced server pools according their state. The keepalived daemon also implements the Virtual Router Redundancy Protocol (VRRP), allowing router or director failover to achieve high availability. This update also fixes the following bugs: Note The keepalived packages have been upgraded to upstream version 1.2.13, which provides a number of bug fixes and enhancements over the version. (BZ# 1052380 , BZ# 1077201 ) This update also fixes the following bugs: Bug Fixes BZ# 967641 Previously, the VRRP alert emails sent by the keepalived daemon did not contain the "to" header, which complicated filtering and sorting such messages by email software. With this update, keepalived has been modified to include the "to" header into email alerts as expected. BZ# 1007575 Previously, when keepalived compared the local primary IP address with another IP address, these two addresses had different byte-ordering. Consequently, multiple routers were created in a master state. With this update, the local primary IP address is converted to network byte order before the comparison, thus fixing this bug. The keepalived packages have been upgraded to upstream version 1.2.13, which provides a number of bug fixes and enhancements over the version. (BZ#1052380, BZ#1077201) Users of keepalived are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
8.235. xfsprogs 8.235.1. RHBA-2013:1657 - xfsprogs bug fix update Updated xfsprogs packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The xfsprogs packages contain a set of commands to use the XFS file system, including the mkfs.xfs command to construct an XFS file system. Bug Fixes BZ# 893904 Previously, when the ag_stride option was specified as an option to the xfs_repair command, the command terminated with a segmentation fault. This update modifies the underlying XFS repair code so the ag_stride option is now properly handled. BZ# 950691 Previously on certain file systems, the xfs_repair utility could occasionally emit warnings such as "7f61c041b700: Badness in key lookup (length)". These were harmless errors related to cache lookup failures, however these messages might have concerned users running xfs_repair. This update ensures that these warnings are no longer encountered. BZ# 961501 When stripe geometry was specified manually to the mkfs.xfs command, mkfs.xfs did not properly select "multidisk mode" as it does when stripe geometry is automatically detected. As a result, a less than optimal number of allocation groups was created. With this update, multidisk mode is selected properly, and a larger number of allocation groups is created. BZ# 962394 The xfs_io(8) man page did not contain documentation for the chproj, lsproj, and setfl commands. These commands are now documented in the man page. Also, the man page has been corrected to refer to section 2 of the fallocate() system call. BZ# 962397 Previously, the xfs_logprint command could abort with the "xlog_print_trans_inode: illegal inode type" error when it encountered a multiply-logged inode field. This update modifies the underlying logprint code so that multiply-logged inode fields are now handled properly, and xfs_logprint completes successfully as expected. BZ# 964216 Previously, the xfs_repair utility was unable to properly handle fragmented multi-block version 2 directories, which could, under certain circumstances, result in an xfs_repair segmentation fault. This update modifies the underlying code so xfs_repair can now operate on fragmented version 2 directories as expected. BZ# 987538 The mkfs.xfs(8) man page did not contain a description of the "-d noalign" option, which disables automatic storage geometry detection at mkfs time. With this update, the option is now properly documented. BZ# 1002908 Previously, the xfs_logprint command could fail when encountering a continued inode transaction or a wrapped log. This update modifies the underlying logprint code so that continued inode transactions and wrapped logs are now handled properly, and xfs_logprint completes successfully as expected. Users of xfprogs are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 6. Configuring JBoss EAP for Microsoft Azure Starting JBoss EAP as a Service at Boot on Red Hat Enterprise Linux If you are starting JBoss EAP as a service on Red Hat Enterprise Linux in Microsoft Azure, you must change the following configuration of the JBoss EAP service to ensure that it starts after the Azure virtual machine host name has been initialized. Open /etc/systemd/system/multi-user.target.wants/eap7-standalone.service and add a dependency on waagent.service : Replace the following line: with: Load Balancing with mod_cluster As a result of mod_cluster advertising not being supported in Azure , if you are configuring a JBoss EAP load balancing environment, you must ensure that all balancers and workers are bound to IP addresses that are accessible on your internal Microsoft Azure virtual network. Note Balancers and workers must be bound to the actual internal Azure virtual IP address, for example 172.28.0.2 , and not 0.0.0.0 . Additionally, because of the unavailability of mod_cluster advertising, if you are using JBoss EAP as an Undertow mod_cluster proxy load balancer, you must configure each worker node to use a proxy list containing each balancer's IP address and port, as shown below: ActiveMQ Artemis High Availability JBoss EAP messaging high availability using Artemis shared stores is not supported in Microsoft Azure. To configure JBoss EAP messaging high availability in Azure, you must use a replicated journal with the AZURE_PING JGroups discovery protocol using a TCP JGroups stack. For more information on using a replicated journal, see Data Replication in Configuring Messaging for JBoss EAP. After configuring the TCP JGroups stack with AZURE_PING, you must add the JGroups stack to the discovery-group and broadcast-group jgroups-cluster configurations in the messaging-activemq subsystem. For details, see Server Discovery in Configuring Messaging for JBoss EAP.

Commands:
After=syslog.target network.target
After=syslog.target network.target waagent.service Requires=waagent.service
/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding= proxy-one :add(host=" BALANCER_IP_ADDRESS ", port=" BALANCER_PORT ") /subsystem=modcluster/mod-cluster-config=configuration:list-add(name=proxies,value= proxy-one )
12.7.2. Useful Websites http://www.isc.org/products/BIND/ - The home page of the BIND project containing information about current releases as well as a PDF version of the BIND 9 Administrator Reference Manual . http://www.redhat.com/mirrors/LDP/HOWTO/DNS-HOWTO.html - Covers the use of BIND as a resolving, caching nameserver and the configuration of various zone files necessary to serve as the primary nameserver for a domain.

Commands:
14.15.2.10. snapshot-delete domain snapshot-delete domain deletes the snapshot for the specified domain. To do this, run: This command Deletes the snapshot for the domain named snapshot , or the current snapshot with --current . If this snapshot has child snapshots, changes from this snapshot will be merged into the children. If the option --children is used, then it will delete this snapshot and any children of this snapshot. If --children-only is used, then it will delete any children of this snapshot, but leave this snapshot intact. These two options are mutually exclusive. The --metadata is used it will delete the snapshot's metadata maintained by libvirt , while leaving the snapshot contents intact for access by external tools; otherwise deleting a snapshot also removes its data contents from that point in time.

Commands:
virsh snapshot-delete domain {snapshot | --current} [--metadata] [{--children | --children-only}]
5.3.2. Moving the Data You can move all the used physical extents in /dev/sdc1 to /dev/sdb1 with the pvmove command. The pvmove command can take a long time to execute. After moving the data, you can see that all of the space on /dev/sdc1 is free.

Commands:
pvmove /dev/sdc1 /dev/sdb1 /dev/sdc1: Moved: 14.7% /dev/sdc1: Moved: 30.3% /dev/sdc1: Moved: 45.7% /dev/sdc1: Moved: 61.0% /dev/sdc1: Moved: 76.6% /dev/sdc1: Moved: 92.2% /dev/sdc1: Moved: 100.0%
pvscan PV /dev/sda1 VG myvg lvm2 [17.15 GB / 0 free] PV /dev/sdb1 VG myvg lvm2 [17.15 GB / 10.80 GB free] PV /dev/sdc1 VG myvg lvm2 [17.15 GB / 17.15 GB free] Total: 3 [51.45 GB] / in use: 3 [51.45 GB] / in no VG: 0 [0 ]
4.110. jss 4.110.1. RHBA-2011:1675 - jss bug fix update An updated jss package that fixes various bugs is now available for Red Hat Enterprise Linux 6. JSS is a Java binding to Network Security Services (NSS), which provides SSL/TLS network protocols and other security services in the Public Key Infrastructure (PKI) suite. JSS is primarily utilized by the Certificate Server. Bug Fixes BZ# 660436 The java.net.SocketException was accompanied by a misleading error message because the exception definition was using a variable pointed to a wrong address. With this update, the underlying code has been modified and the exception now uses the correct error message. BZ# 705947 On Luna SA HSM in FIPS mode, Red Hat Certificate System failed to generate a certificate and threw an exception if ECC (Elliptic Curve Cryptography) algorithms was set to higher than SHA1withEC. This occurred because in FIPS mode, the SSL protocol requires ECDH (Elliptic Curve Diffie Hellman), which is not supported by Luna SA. With this update, the ECDH support has been provided by JSS/NSS, and certificates are created and used with SSL correctly. BZ# 733551 In FIPS mode, DRM (Data Recovery Manager) failed to recover keys because it failed to import the respective key. With this update, the key is generated on recovery and the recovery succeeds. All users of jss are advised to upgrade to this updated package, which fixes these bugs.

Commands:
4.99. iptables 4.99.1. RHBA-2012:0335 - iptables bug fix update Updated iptables packages that fix one bug are now available for Red Hat Enterprise Linux 6. The iptables utility controls the network packet filtering code in the Linux kernel. Bug Fix BZ# 786874 The option parser of the iptables utility did not correctly handle the "-m mark" and "-m conmark" options in the same rule. Therefore, the iptables command failed when issued with both options. This update modifies behavior of the option parser so that iptables now works as expected with the "-m mark" and "-m conmark" options specified. All users of iptables are advised to upgrade to these updated packages, which fix this bug.

Commands:
3.15. Example: Start Virtual Machine The virtual environment is complete and the virtual machine contains all necessary components to function. This example starts the virtual machine using the start action. Example 3.18. Start the virtual machine Request: cURL command: The additional message entity sets the virtual machine's boot device to CD-ROM for this boot only. This enables the virtual machine to install Red Hat Enterprise Server 6 from the attached ISO image. The boot device reverts back to disk for all future boots.

Commands:
POST /ovirt-engine/api/vms/6efc0cfa-8495-4a96-93e5-ee490328cf48/start HTTP/1.1 Accept: application/xml Content-type: application/xml <action> <vm> <os> <boot dev="cdrom"/> </os> </vm> </action>
curl -X POST -H "Accept: application/xml" -H "Content-Type: application/xml" -u [USER:PASS] --cacert [CERT] -d "<action><vm><os><boot dev='cdrom'/></os></vm></action>" https:// [RHEVM Host] :443/ovirt-engine/api/vms/6efc0cfa-8495-4a96-93e5-ee490328cf48/start
8.171. pcsc-lite 8.171.1. RHBA-2014:1463 - pcsc-lite bug fix and enhancement update Updated pcsc-lite packages that add one enhancement are now available for Red Hat Enterprise Linux 6. PC/SC Lite provides a Windows SCard compatible interface for communicating with smart cards, smart card readers, and other security tokens. Enhancement BZ# 1092751 This update allows the pcsc-lite packages to be combined with the pcsc-cyberjack packages from the Extra Packages for Enterprise Linux (EPEL) repository. This allows pcsc-lite to support the driver for Reiner SCT cyberJack RFID standard card reader that is included in pcsc-cyberjack. Users of pcsc-lite are advised to upgrade to these updated packages, which add this enhancement.

Commands: