mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Converting virtualization hosts to hyperconverged hosts Follow this process to convert virtualization hosts to hyperconverged hosts. This lets you use and manage the host's local storage as Red Hat Gluster Storage volumes. Log in to the Administration Portal. Move all hosts except the self-hosted engine node into maintenance mode. Click Compute Hosts . For each host except the self-hosted engine node: Select the host to move to maintenance. Click Management Maintenance and click OK . Enable the gluster service in the cluster. Click Compute Clusters and select the cluster. The Edit Cluster window appears. Check the Enable Gluster service checkbox. Click OK . Reinstall all hosts except the self-hosted engine node. Click Compute Hosts . For each host except the self-hosted engine node: Select the host to reinstall. Click Management Reinstall and click OK . Wait for the reinstall to complete and for the hosts to become active again. Move the self-hosted engine node into maintenance mode. Select the self-hosted engine node. Click Management Maintenance and click OK The hosted engine migrates to one of the freshly installed hosts. Reinstall the self-hosted engine node. Select the self-hosted engine node. Click Management Reinstall and click OK . Wait for the reinstall to complete and for the host to become active again. Your hosts are now able to use and manage storage as Red Hat Gluster Storage volumes.

Commands:
Chapter 9. Data Centers 9.1. Data Center Elements The datacenters collection provides information about the data centers in a Red Hat Virtualization environment. An API user accesses this information through the rel="datacenters" link obtained from the entry point URI. The following table shows specific elements contained in a data center resource representation. Table 9.1. Data center elements Element Type Description Properties name string A plain text, human-readable name for the data center. The name is unique across all data center resources. description string A plain text, human-readable description of the data center link rel="storagedomains" relationship A link to the sub-collection for storage domains attached to this data center. link rel="clusters" relationship A link to the sub-collection for clusters attached to this data center. link rel="networks" relationship A link to the sub-collection for networks available to this data center. link rel="permissions" relationship A link to the sub-collection for data center permissions. link rel="quotas" relationship A link to the sub-collection for quotas associated with this data center. local Boolean: true or false Specifies whether the data center is a local data center, such as created in all-in-one instances. storage_format enumerated Describes the storage format version for the data center. A list of enumerated values are available in capabilities . version major= minor= complex The compatibility level of the data center. supported_versions complex A list of possible version levels for the data center, including version major= minor= . mac_pool string The MAC address pool associated with the data center. If no MAC address pool is specified the default MAC address pool is used. status see below The data center status. The status contains one of the following enumerated values: uninitialized , up , maintenance , not_operational , problematic and contend . These states are listed in data_center_states under capabilities .

Commands:
8.151. nmap 8.151.1. RHBA-2014:0683 - nmap bug fix update Updated nmap packages that fix one bug are now available for Red Hat Enterprise Linux 6. The nmap packages provide a network exploration utility and a security scanner. Bug Fix BZ# 1000770 Previously, the ncat utility printed debug messages even in verbose mode. As a consequence, after connecting through an HTTP proxy, a debug message was displayed together with the received data, which could interfere with the automated processing of standard output. With this update, ncat prints debug messages only in verbose mode as expected. Users of nmap are advised to upgrade to these updated packages, which fix this bug.

Commands:
13.3. Creating New Indexes to Existing Databases Learn how to initiate indexing operations on Directory Server. You must create indexes manually because Directory Server does not automatically index databases. Important Before you regenerate the index, searches proceed but can return incorrect or inconsistent results. 13.3.1. Creating an Index While the Instance is Running 13.3.1.1. Creating an Index Using the dsconf backend index reindex Command To recreate the index of a database while the instance is running: 13.3.1.2. Creating an Index Using a cn=tasks Entry The cn=tasks,cn=config entry in the Directory Server configuration is a container entry for temporary entries the server uses to manage tasks. To initiate an index operation, create a task in the cn=index,cn=tasks,cn=config entry. Use the ldapadd utility to add a new index task. For example, to add a task that creates the presence index for the cn attribute in the userRoot database: When the task is completed, the entry is removed from the directory configuration. For further details, about the cn=index,cn=tasks,cn=config entry, see the cn=index section in the Red Hat Directory Server Configuration, Command, and File Reference . 13.3.2. Creating an Index While the Instance Offline After creating an indexing entry or adding additional index types to an existing indexing entry, use the dsconf db2index command: Shut down the instance: Recreate the index: Start the instance:

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com backend index reindex database_name
ldapadd -D "cn=Directory Manager" -W -p 389 -h server.example.com -x dn: cn= example_presence_index ,cn=index,cn=tasks,cn=config objectclass: top objectclass: extensibleObject cn: example presence index nsInstance: userRoot nsIndexAttribute: " cn:pres "
dsctl instance_name stop
dsctl instance_name db2index userRoot [13/Aug/2019:15:25:37.277426483 +0200] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000 [13/Aug/2019:15:25:37.289257996 +0200] - INFO - check_and_set_import_cache - pagesize: 4096, available bytes 1704378368, process usage 22212608 [13/Aug/2019:15:25:37.291738104 +0200] - INFO - check_and_set_import_cache - Import allocates 665772KB import cache. db2index successful
dsctl instance_name start
C.2.3. Choosing a Good Passphrase While dm-crypt/LUKS supports both keys and passphrases, the anaconda installer only supports the use of passphrases for creating and accessing encrypted block devices during installation. LUKS does provide passphrase strengthening but it is still a good idea to choose a good (meaning "difficult to guess") passphrase. Note the use of the term "passphrase", as opposed to the term "password". This is intentional. Providing a phrase containing multiple words to increase the security of your data is important.

Commands:
5.5. Disk Space and Memory Requirements Red Hat Enterprise Linux, like most modern operating systems, uses disk partitions . When you install Red Hat Enterprise Linux, you might have to work with disk partitions. For more information, see Appendix A, An Introduction to Disk Partitions . If you have other operating systems installed on your system, the disk space they use must be separate from the disk space used by Red Hat Enterprise Linux. Note For AMD64/Intel 64 and ARM systems, at least two partitions ( / and swap ) must be dedicated to Red Hat Enterprise Linux. To install Red Hat Enterprise Linux, you must have a minimum of 10 GiB of space in either unpartitioned disk space or in partitions which can be deleted. For more information on partition and disk space recommendations, see the recommended partitioning sizes discussed in Section 8.14.4.4, "Recommended Partitioning Scheme" . Red Hat Enterprise Linux requires minimum the following amount of RAM: Installation type Minimum required RAM Local media installation (USB, DVD) 768 MiB NFS network installation 768 MiB HTTP, HTTPS, or FTP network installation 1.5 GiB Note It may be possible to perform the installation with less memory than listed in this section. However, the exact requirements depend heavily on your environment and exact installation path, and they also change with each new release. Determining the absolute minimum required RAM for your specific use case therefore requires you to test various configurations, and periodically re-test with each new release. Installing Red Hat Enterprise Linux using a Kickstart file has the same minimum RAM requirements as a manual installation. However, if you use a Kickstart file that runs commands which require additional memory or write data to the RAM disk, additional RAM might be necessary. For more information about the minimum requirements and technology limits of Red Hat Enterprise Linux 7, see the Red Hat Enterprise Linux technology capabilities and limits article on the Red Hat Customer Portal.

Commands:
B.12. Guest is Unable to Start with Error: warning: could not open /dev/net/tun Symptom The guest virtual machine does not start after configuring a type='ethernet' (also known as 'generic ethernet') interface in the host system. An error appears either in libvirtd.log , /var/log/libvirt/qemu/ name_of_guest .log , or in both, similar to the below message: Investigation Use of the generic ethernet interface type ( <interface type='ethernet'> ) is discouraged, because using it requires lowering the level of host protection against potential security flaws in QEMU and its guests. However, it is sometimes necessary to use this type of interface to take advantage of some other facility that is not yet supported directly in libvirt . For example, openvswitch was not supported in libvirt until libvirt-0.9.11 , so in older versions of libvirt , <interface type='ethernet'> was the only way to connect a guest to an openvswitch bridge. However, if you configure a <interface type='ethernet'> interface without making any other changes to the host system, the guest virtual machine will not start successfully. The reason for this failure is that for this type of interface, a script called by QEMU needs to manipulate the tap device. However, with type='ethernet' configured, in an attempt to lock down QEMU , libvirt and SELinux have put in place several checks to prevent this. (Normally, libvirt performs all of the tap device creation and manipulation, and passes an open file descriptor for the tap device to QEMU .) Solution Reconfigure the host system to be compatible with the generic ethernet interface. Procedure B.4. Reconfiguring the host system to use the generic ethernet interface Set SELinux to permissive by configuring SELINUX=permissive in /etc/selinux/config : From a root shell, run the command setenforce permissive . In /etc/libvirt/qemu.conf add or edit the following lines: Restart libvirtd . Important Since each of these steps significantly decreases the host's security protections against QEMU guest domains, this configuration should only be used if there is no alternative to using <interface type='ethernet'> . Note For more information on SELinux, refer to the Red Hat Enterprise Linux 6 Security-Enhanced Linux User Guide .

Commands:
warning: could not open /dev/net/tun: no virtual network emulation qemu-kvm: -netdev tap,script=/etc/my-qemu-ifup,id=hostnet0: Device 'tap' could not be initialized
This file controls the state of SELinux on the system. SELINUX= can take one of these three values: enforcing - SELinux security policy is enforced. permissive - SELinux prints warnings instead of enforcing. disabled - No SELinux policy is loaded. SELINUX=permissive SELINUXTYPE= can take one of these two values: targeted - Targeted processes are protected, mls - Multi Level Security protection. SELINUXTYPE=targeted
clear_emulator_capabilities = 0
user = "root"
group = "root"
cgroup_device_acl = [ "/dev/null", "/dev/full", "/dev/zero", "/dev/random", "/dev/urandom", "/dev/ptmx", "/dev/kvm", "/dev/kqemu", "/dev/rtc", "/dev/hpet", "/dev/net/tun",
Chapter 14. Storage rescan-scsi-bus.sh now correctly interprets multiple word device descriptions The rescan-scsi-bus.sh script, found in the sg3_utils package, previously misinterpreted SCSI device types that were described using more than one word, such as Medium Changer or Optical Device . Consequently, when the script was run on systems that had such device types attached, the script printed multiple misleading error messages. With this update, device types described with multiple words are handled correctly, and the proper device type description is returned to the user without any errors. (BZ#1210438) rescan-scsi-bus.sh no longer removes /dev/null When running the rescan-scsi-bus.sh script, due to incorrect syntax in redirecting output to the /dev/null device file while executing the /bin/rm utility, the redirection did not happen but /dev/null was instead interpreted as a file to be removed. As a consequence, running rescan-scsi-bus.sh with the --update option removed /dev/null during execution. This bug has been fixed, and /dev/null is no longer removed by rescan-scsi-bus.sh . (BZ# 1245302 ) Additional result codes are now recognized by sg_persist Previously, some SCSI hosts could return result codes which were not recognized by sg_persist , causing it to output an error message claiming the result code is invalid. This update adds additional return codes, such as DID_NEXUS_FAILURE , and the problem no longer occurs. (BZ#886611) iSCSI boot works correctly in Multi Function mode Due to incorrect handling of Multi Function mode when dealing with the bnx2x driver, booting iSCSI from Storage Area Network (SAN) did not work correctly for some Host Bus Adapters (HBAs). The underlying source code has been fixed, and iSCSI boot now works correctly in Multi Function mode. (BZ#1276545)

Commands:
4.6. Troubleshooting Expiration If expiration does not appear to be working, it may be due to an entry being marked for expiration but not being removed. Multiple-cache operations such as put() are passed a life span value as a parameter. This value defines the interval after which the entry must expire. In cases where eviction is not configured and the life span interval expires, it can appear as if Red Hat JBoss Data Grid has not removed the entry. For example, when viewing JMX statistics, such as the number of entries , you may see an out of date count, or the persistent store associated with JBoss Data Grid may still contain this entry. Behind the scenes, JBoss Data Grid has marked it as an expired entry, but has not removed it. Removal of such entries happens as follows: An entry is passivated/overflowed to disk and is discovered to have expired. The expiration maintenance thread discovers that an entry it has found is expired. Any attempt to use get() or containsKey() for the expired entry causes JBoss Data Grid to return a null value. The expired entry is later removed by the expiration thread. Report a bug

Commands:
10.2.3. Virtual Host Configuration The contents of all <VirtualHost> containers should be migrated in the same way as the main server section as described in Section 10.2.2, "Main Server Configuration" . Important Note that SSL/TLS virtual host configuration has been moved out of the main server configuration file and into /etc/httpd/conf.d/ssl.conf . For more on this topic, refer to the chapter titled Apache HTTP Secure Server Configuration in the System Administrators Guide and the documentation online at the following URL: http://httpd.apache.org/docs-2.0/vhosts/

Commands:
E.2.28. /proc/uptime This file contains information detailing how long the system has been on since its last restart. The output of /proc/uptime is quite minimal: The first value represents the total number of seconds the system has been up. The second value is the sum of how much time each core has spent idle, in seconds. Consequently, the second value may be greater than the overall system uptime on systems with multiple cores.

Commands:
350735.47 234388.90
3.15. Starting a Virtual Machine This Ruby example starts a virtual machine. # Get the reference to the "vms" service: vms_service = connection.system_service.vms_service # Find the virtual machine: vm = vms_service.list(search: 'name=myvm')[0] # Locate the service that manages the virtual machine, as that is where # the action methods are defined: vm_service = vms_service.vm_service(vm.id) # Call the "start" method of the service to start it: vm_service.start # Wait until the virtual machine status is UP: loop do sleep(5) vm = vm_service.get break if vm.status == OvirtSDK4::VmStatus::UP end For more information, see VmService:start .

Commands:
Get the reference to the "vms" service: vms_service = connection.system_service.vms_service Find the virtual machine: vm = vms_service.list(search: 'name=myvm')[0] Locate the service that manages the virtual machine, as that is where the action methods are defined: vm_service = vms_service.vm_service(vm.id) Call the "start" method of the service to start it: vm_service.start Wait until the virtual machine status is UP: loop do sleep(5) vm = vm_service.get break if vm.status == OvirtSDK4::VmStatus::UP end
4.10. Enterprise Information System Support The underlying resource adaptors that represent the Enterprise Information System (EIS) and the EIS itself must support XA transactions to be able to participate in distributed XA transaction using JBoss Data Virtualization. If a source system does not support the XA, then it can not participate in the distributed transaction. However, the source is still eligible to participate in data integration without XA support. Participation in an XA transaction is automatically determined based on the resource adaptor's XA capability. It is the developer's responsibility to ensure they configure an XA resource when they require them to participate in distributed transactions.

Commands:
Chapter 6. Registering the System and Managing Subscriptions The subscription service provides a mechanism to handle Red Hat software inventory and allows you to install additional software or update already installed programs to newer versions using the yum or PackageKit package managers. In Red Hat Enterprise Linux 6 the recommended way to register your system and attach subscriptions is to use Red Hat Subscription Management . Note It is also possible to register the system and attach subscriptions after installation during the firstboot process. For detailed information about firstboot see the Firstboot chapter in the Installation Guide for Red Hat Enterprise Linux 6. Note that firstboot is only available on systems after a graphical installation or after a kickstart installation where a desktop and the X window system were installed and graphical login was enabled. 6.1. Registering the System and Attaching Subscriptions Complete the following steps to register your system and attach one or more subscriptions using Red Hat Subscription Management. Note that all subscription-manager commands are supposed to be run as root . Run the following command to register your system. You will be prompted to enter your user name and password. Note that the user name and password are the same as your login credentials for Red Hat Customer Portal. subscription-manager register Determine the pool ID of a subscription that you require. To do so, type the following at a shell prompt to display a list of all subscriptions that are available for your system: subscription-manager list --available For each available subscription, this command displays its name, unique identifier, expiration date, and other details related to your subscription. To list subscriptions for all architectures, add the --all option. The pool ID is listed on a line beginning with Pool ID . Attach the appropriate subscription to your system by entering a command as follows: subscription-manager attach --pool= pool_id Replace pool_id with the pool ID you determined in the step. To verify the list of subscriptions your system has currently attached, at any time, run: subscription-manager list --consumed Note If you use a firewall or a proxy, you may need additional configuration to allow yum and subscription-manager to work correctly. Refer to the "Setting Firewall Access for Content Delivery" section of the Red Hat Enterprise Linux 6 Subscription Management guide if you use a firewall and to the "Using an HTTP Proxy" section if you use a proxy. For more details on how to register your system using Red Hat Subscription Management and associate it with subscriptions, see the designated solution article . For comprehensive information about subscriptions, see the Red Hat Subscription Management collection of guides.

Commands:
Chapter 12. Security GSSAPI key-exchange algorithms can now be selectively disabled In view of the Logjam security vulnerability, the gss-group1-sha1-* key-exchange methods are no longer considered secure. While there was the possibility to disable this key-exchange method as a normal key exchange, it was not possible to disable it as a GSSAPI key exchange. With this update, the administrator can selectively disable this or other algorithms used by the GSSAPI key exchange. SELinux policy for Red Hat Gluster Storage has been added Previously, SELinux policy for Red Hat Gluster Storage (RHGS) components was missing, and Gluster worked correctly only when SELinux was in permissive mode. With this update, SELinux policy rules for the glusterd (glusterFS Management Service), glusterfsd (NFS sever), smbd , nfsd , rpcd , adn ctdbd processes have been updated providing SELinux support for Gluster. openscap rebase to version 1.2.5 The openscap packages have been upgraded to upstream version 1.2.5, which provides a number of bug fixes and enhancements over the version. Notable enhancements include: * Support for OVAL version 5.11, which brings multiple improvements such as for systemd properties * Introduced native support of xml.bz2 input files * Introduced the oscap-ssh tool for assessing remote systems * Introduced the oscap-docker tool for assessing containers/images scap-security-guide rebase to version 0.1.25 The scap-security-guide tool has been upgraded to upstream version 0.1.25, which provides a number of bug fixes and enhancements over the version. Notable enhancements include: * New security profiles for Red Hat Enterprise Linux 7 Server: Common Profile for General-Purpose Systems, Draft PCI-DSS v3 Control Baseline, Standard System Security Profile, and Draft STIG for Red Hat Enterprise Linux 7 Server. * New security benchmarks for Firefox and Java Runtime Environment (JRE) components running on Red Hat Enterprise Linux 6 and 7. * New scap-security-guide-doc subpackage, which contains HTML-formatted documents containing security guides generated from XCCDF benchmarks (for every security profile shipped in security benchmarks for Red Hat Enterprise Linux 6 and 7, Firefox, and JRE).

Commands: