mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 24. Setting Up A Remote Diskless System The Network Booting Service (provided by system-config-netboot ) is no longer available in Red Hat Enterprise Linux 6. Deploying diskless systems is now possible in this release without the use of system-config-netboot . To set up a basic remote diskless system booted over PXE, you need the following packages: tftp-server xinetd dhcp syslinux dracut-network Remote diskless system booting requires both a tftp service (provided by tftp-server ) and a DHCP service (provided by dhcp ). The tftp service is used to retrieve kernel image and initrd over the network via the PXE loader. The following sections outline the necessary procedures for deploying remote diskless systems in a network environment. 24.1. Configuring a tftp Service for Diskless Clients The tftp service is disabled by default. To enable it and allow PXE booting via the network, set the Disabled option in /etc/xinetd.d/tftp to no . To configure tftp , perform the following steps: Procedure 24.1. To configure tftp The tftp root directory ( chroot ) is located in /var/lib/tftpboot . Copy /usr/share/syslinux/pxelinux.0 to /var/lib/tftpboot/ , as in: cp /usr/share/syslinux/pxelinux.0 /var/lib/tftpboot/ Create a pxelinux.cfg directory inside the tftp root directory: mkdir -p /var/lib/tftpboot/pxelinux.cfg/ You will also need to configure firewall rules properly to allow tftp traffic; as tftp supports TCP wrappers, you can configure host access to tftp via /etc/hosts.allow . For more information on configuring TCP wrappers and the /etc/hosts.allow configuration file, refer to the Red Hat Enterprise Linux 6 Security Guide ; man hosts_access also provides information about /etc/hosts.allow . After configuring tftp for diskless clients, configure DHCP, NFS, and the exported file system accordingly. Refer to Section 24.2, "Configuring DHCP for Diskless Clients" and Section 24.3, "Configuring an Exported File System for Diskless Clients" for instructions on how to do so.

Commands:
Chapter 17. Policies You can configure access policies for certain services in the overcloud. To configure policies for a service, set the respective policy parameter with a hash value containing the service's policies. For example: OpenStack Identity (keystone) uses the KeystonePolicies parameter. Set this parameter in the parameter_defaults section of an environment file: OpenStack Compute (nova) uses the NovaApiPolicies parameter. Set this parameter in the parameter_defaults section of an environment file: For a full list of policy parameters, see "Policy Parameters" in the Overcloud Parameters guide.

Commands:
parameter_defaults: KeystonePolicies: { keystone-context_is_admin: { key: context_is_admin, value: 'role:admin' } }
parameter_defaults: NovaApiPolicies: { nova-context_is_admin: { key: 'compute:get_all', value: '@' } }
Installing on OCI OpenShift Container Platform 4.17 Installing OpenShift Container Platform on Oracle Cloud Infrastructure Red Hat OpenShift Documentation Team

Commands:
cat ~/.ssh/id_rsa.put
Error: 400-InvalidParameter, DNS Label oci-demo does not follow Oracle requirements Suggestion: Please update the parameter(s) in the Terraform config as per error message DNS Label oci-demo does not follow Oracle requirements Documentation: https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/core_vcn
./openshift-install version
./openshift-install 4.17.0 built from commit ae7977b7d1ca908674a0d45c5c243c766fa4b2ca release image registry.ci.openshift.org/origin/release:4.17ocp-release@sha256:0da6316466d60a3a4535d5fed3589feb0391989982fba59d47d4c729912d6363 release architecture amd64
mkdir ~/<directory_name>
install-config.yaml apiVersion: v1 baseDomain: <base_domain> 1 networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 network type: OVNKubernetes machineNetwork: - cidr: <ip_address_from_cidr> 2 serviceNetwork: - 172.30.0.0/16 compute: - architecture: amd64 3 hyperthreading: Enabled name: worker replicas: 0 controlPlane: architecture: amd64 4 hyperthreading: Enabled name: master replicas: 3 platform: external: platformName: oci 5 cloudControllerManager: External sshKey: <public_ssh_key> 6 pullSecret: '<pull_secret>' 7
apiVersion: v1beta1 metadata: name: <cluster_name> 1 namespace: <cluster_namespace> 2 rendezvousIP: <ip_address_from_CIDR> 3 bootArtifactsBaseURL: <server_URL> 4
./openshift-install agent create image --log-level debug
./openshift-install agent wait-for install-complete --log-level debug
export KUBECONFIG=~/auth/kubeconfig
oc get nodes -A
NAME STATUS ROLES AGE VERSION main-0.private.agenttest.oraclevcn.com Ready control-plane, master 7m v1.27.4+6eeca63 main-1.private.agenttest.oraclevcn.com Ready control-plane, master 15m v1.27.4+d7fa83f main-2.private.agenttest.oraclevcn.com Ready control-plane, master 15m v1.27.4+d7fa83f
oc get co
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE authentication 4.17.0-0 True False False 6m18s baremetal 4.17.0-0 True False False 2m42s network 4.17.0-0 True True False 5m58s Progressing: ... ...
Chapter 4. Monitor the OpenStack Platform See the Sensu documentation for further details about the Sensu stack infrastructure: https://docs.sensu.io/sensu-core/1.7/overview/architecture/ Red Hat supplies a set of check scripts in the osops-tools-monitoring-oschecks package. The majority of the check scripts only check the API connection to the OpenStack component. However, certain scripts also perform additional OpenStack resource tests for OpenStack Compute (nova), OpenStack Block Storage (cinder), OpenStack Image (glance), and OpenStack Networking (neutron). For example, the OpenStack Identity (keystone) API check returns the following result when keystone is running:

Commands:
OK: Got a token, Keystone API is working.
5.216. numactl 5.216.1. RHBA-2012:0828 - numactl bug fix and enhancement update Updated numactl packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The numactl packages provide a simple Non-Uniform Memory Access (NUMA) policy support and consist of the numactl program to run other programs with a specific NUMA policy and the libnuma library to do allocations in applications using the NUMA policy. The numactl packages have been upgraded to upstream version 2.0.7, which provides a number of bug fixes and enhancements over the version. (BZ# 645066 ) Bug Fix BZ# 751764 Prior to this update, the man page for the numastat tool was not included in the numactl package. This update adds the missing numastat man page to numactl. All users of numactl are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
23.10. Improving Accuracy Previously, test results indicated that disabling the tickless kernel capability could significantly improve the stability of the system clock, and thus improve the PTP synchronization accuracy (at the cost of increased power consumption). The kernel tickless mode can be disabled by adding nohz=off to the kernel boot option parameters. However, recent improvements applied to kernel-3.10.0-197.el7 have greatly improved the stability of the system clock and the difference in stability of the clock with and without nohz=off should be much smaller now for most users. The ptp4l and phc2sys applications can be configured to use a new adaptive servo. The advantage over the PI servo is that it does not require configuration of the PI constants to perform well. To make use of this for ptp4l , add the following line to the /etc/ptp4l.conf file: clock_servo linreg After making changes to /etc/ptp4l.conf , restart the ptp4l service from the command line by issuing the following command as root : To make use of this for phc2sys , add the following line to the /etc/sysconfig/phc2sys file: -E linreg After making changes to /etc/sysconfig/phc2sys , restart the phc2sys service from the command line by issuing the following command as root :

Commands:
~]# service ptp4l restart
~]# service phc2sys restart
10.2.4.9. The mod_authz_ldap Module Red Hat Enterprise Linux ships with the mod_authz_ldap module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. The mod_ssl module is required when using the mod_authz_ldap module. Important The mod_authz_ldap module does not authenticate a user to an LDAP directory using an encrypted password hash. This functionality is provided by the experimental mod_auth_ldap module. Refer to the mod_auth_ldap module documentation online at http://httpd.apache.org/docs-2.0/mod/mod_auth_ldap.html for details on the status of this module. The /etc/httpd/conf.d/authz_ldap.conf file configures the mod_authz_ldap module. Refer to /usr/share/doc/mod_authz_ldap- <version> /index.html (replacing <version> with the version number of the package) or http://authzldap.othello.ch/ for more information on configuring the mod_authz_ldap third party module.

Commands:
C.4.2. Optional: Fill the Device with Random Data Filling <device> (eg: /dev/sda3 ) with random data before encrypting it greatly increases the strength of the encryption. The downside is that it can take a very long time. Warning The commands below will destroy any existing data on the device. The best way, which provides high quality random data but takes a long time (several minutes per gigabyte on most systems): Fastest way, which provides lower quality random data:

Commands:
dd if=/dev/urandom of=<device>
badblocks -c 10240 -s -w -t random -v <device>
5.13. bacula 5.13.1. RHBA-2012:1469 - bacula bug fix update Updated bacula packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. The bacula packages provide a tool set that allows you to manage the backup, recovery, and verification of computer data across a network of different computers. Bug Fixes BZ# 728693 Prior to this update, the logwatch tool did not check the "/var/log/bacula*" file. As a consequence, the logwatch report was incomplete. This update adds all log files to the logwatch configuration file. Now, the logwatch report is complete. BZ# 728697 Prior to this update, the bacula tool itself created the "/var/spool/bacula/log" file. As a consequence, this log file used an incorrect SELinux context. This update modifies the underlying code to create the /var/spool/bacula/log file in the bacula package. Now, this log file has the correct SELinux context. BZ# 729008 Prior to this update, the bacula packages were built without the CFLAGS variable "USDRPM_OPT_FLAGS". As a consequence, the debug information was not generated. This update modifies the underlying code to build the packages with CFLAGS="USDRPM_OPT_FLAGS. Now, the debug information is generated as expected. BZ# 756803 Prior to this update, the perl script which generates the my.conf file contained a misprint. As a consequence, the port variable was not set correctly. This update corrects the misprint. Now, the port variable is set as expected. BZ# 802158 Prior to this update, values for the "show pool" command was obtained from the "res->res_client" item. As a consequence, the output displayed incorrect job and file retention values. This update uses the "res->res_pool" item to obtain the correct values. BZ# 862240 Prior to this update, bacula-storage-common utility wrongly removed alternatives for the bcopy function during the update. As a consequence, the Link to bcop.{mysql,sqlite,postgresql} disappeared after updating. This update modifies the underlying code to remove these links directly in storage-{mysql,sqlite,postgresql} and not in bacula-storage-common. All users of bacula are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 14. Viewing threads You can view and monitor the state of threads. Procedure Click the Runtime tab and then the Threads subtab. The Threads page lists active threads and stack trace details for each thread. By default, the thread list shows all threads in descending ID order. To sort the list by increasing ID, click the ID column label. Optionally, filter the list by thread state (for example, Blocked ) or by thread name. To drill down to detailed information for a specific thread, such as the lock class name and full stack trace for that thread, in the Actions column, click More .

Commands:
9.6. Sample Time Based Expressions The following command configures an expression that is true if now is any time in the year 2005. The following command configures an expression that is true from 9am to 5pm, Monday through Friday. Note that the hours value of 16 matches up to 16:59:59, as the numeric value (hour) still matches. The following command configures an expression that is true when there is a full moon on Friday the 13th.

Commands:
pcs constraint location Webserver rule score=INFINITY date-spec years=2005
pcs constraint location Webserver rule score=INFINITY date-spec hours="9-16" weekdays="1-5"
pcs constraint location Webserver rule date-spec weekdays=5 monthdays=13 moon=4
3.2. Configuring an LVM Volume with an ext4 File System This use case requires that you create an LVM logical volume on storage that is shared between the nodes of the cluster. The following procedure creates an LVM logical volume and then creates an ext4 file system on that volume. In this example, the shared partition /dev/sdb1 is used to store the LVM physical volume from which the LVM logical volume will be created. Note LVM volumes and the corresponding partitions and devices used by cluster nodes must be connected to the cluster nodes only. Since the /dev/sdb1 partition is storage that is shared, you perform this procedure on one node only, Create an LVM physical volume on partition /dev/sdb1 . Create the volume group my_vg that consists of the physical volume /dev/sdb1 . Create a logical volume using the volume group my_vg . You can use the lvs command to display the logical volume. Create an ext4 file system on the logical volume my_lv .

Commands:
pvcreate /dev/sdb1 Physical volume "/dev/sdb1" successfully created
vgcreate my_vg /dev/sdb1 Volume group "my_vg" successfully created
lvcreate -L450 -n my_lv my_vg Rounding up size to full physical extent 452.00 MiB Logical volume "my_lv" created
lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert my_lv my_vg -wi-a---- 452.00m
mkfs.ext4 /dev/my_vg/my_lv mke2fs 1.42.7 (21-Jan-2013) Filesystem label= OS type: Linux
5.350. virt-top and ocaml-libvirt 5.350.1. RHBA-2012:0959 - virt-top and ocaml-libvirt bug fix update Updated virt-top and ocaml-libvirt packages that fix two bugs are now available. The virt-top utility displays statistics of virtualized domains and uses many of the same keys and command line options as the top utility. The ocaml-libvirt package provides OCaml (Objective CAML) bindings for libvirt, allowing users to write OCaml programs and scripts which control virtualization features. Bug Fix BZ# 737728 Output of the "virt-top -1" command (which displays physical CPU usage) did not contain all the needed information from libvirt in order to provide accurate accounting of physical CPU usage. With this update, the underlying source code has been modified to address this issue, and the "virt-top -1" output now displays accurate statistics. All users of virt-top and ocaml-libvirt are advised to upgrade to these updated packages, which resolve these issues.

Commands:
3.6.3. Deleting a Member from a Cluster To delete a member from an existing cluster that is currently in operation, follow the steps in this section. The starting point of the procedure is at the Choose a cluster to administer page (displayed on the cluster tab). Click the link of the node to be deleted. Clicking the link of the node to be deleted causes a page to be displayed for that link showing how that node is configured. Note To allow services running on a node to fail over when the node is deleted, skip the step. Disable or relocate each service that is running on the node to be deleted: Note Repeat this step for each service that needs to be disabled or started on another node. Under Services on this Node , click the link for a service. Clicking that link cause a configuration page for that service to be displayed. On that page, at the Choose a task drop-down box, choose to either disable the service are start it on another node and click Go . Upon confirmation that the service has been disabled or started on another node, click the cluster tab. Clicking the cluster tab causes the Choose a cluster to administer page to be displayed. At the Choose a cluster to administer page, click the link of the node to be deleted. Clicking the link of the node to be deleted causes a page to be displayed for that link showing how that node is configured. On that page, at the Choose a task drop-down box, choose Delete this node and click Go . When the node is deleted, a page is displayed that lists the nodes in the cluster. Check the list to make sure that the node has been deleted.

Commands:
4.4.3. Resizing Logical Volumes To reduce the size of a logical volume, use the lvreduce command. If the logical volume contains a file system, be sure to reduce the file system first (or use the LVM GUI) so that the logical volume is always at least as large as the file system expects it to be. The following command reduces the size of logical volume lvol1 in volume group vg00 by 3 logical extents.

Commands:
lvreduce -l -3 vg00/lvol1
B.3. The guest virtual machine cannot be started: internal error guest CPU is not compatible with host CPU Symptom Running on an Intel Core i7 processor (which virt-manager refers to as Nehalem , or the older Core 2 Duo, referred to as Penryn ), a KVM guest (or domain) is created using virt-manager . After installation, the guest's processor is changed to match the host's CPU. The guest is then unable to start and reports this error: Additionally, clicking Copy host CPU configuration in virt-manager shows Pentium III instead of Nehalem or Penryn . Investigation The /usr/share/libvirt/cpu_map.xml file lists the flags that define each CPU model. The Nehalem and Penryn definitions contain this: <feature name='nx'/> As a result, the NX (or No eXecute ) flag needs to be presented to identify the CPU as Nehalem or Penryn . However, in /proc/cpuinfo , this flag is missing. Solution Nearly all new BIOSes allow enabling or disabling of the No eXecute bit. However, if disabled, some CPUs do not report this flag and thus libvirt detects a different CPU. Enabling this functionality instructs libvirt to report the correct CPU. Refer to your hardware documentation for further instructions on this subject.

Commands:
2012-02-06 17:49:15.985+0000: 20757: error : qemuBuildCpuArgStr:3565 : internal error guest CPU is not compatible with host CPU
<feature name='nx'/>
Chapter 2. Supported Configurations The only virtual machine operating systems supported for using JBoss EAP in Microsoft Azure are: Red Hat Enterprise Linux 7 Red Hat Enterprise Linux 8 Microsoft Windows Server 2016 Microsoft Windows Server 2019 The Red Hat Cloud Access program allows you to use a JBoss EAP subscription to install JBoss EAP on your own Azure virtual machine or one of the above On-Demand operating systems from the Microsoft Azure Marketplace. Note that virtual machine operating system subscriptions are separate from a JBoss EAP subscription. Other than the above operating system restrictions, see the Customer Portal for further information on supported configurations for JBoss EAP , such as supported Java Development Kit (JDK) vendors and versions. 2.1. JBoss EAP 7.4 OpenJDK images available in Microsoft Azure In JBoss EAP 7.4, you can now use OpenJDK 8 images on Red Hat Enterprise Linux 8 virtual machines in Microsoft Azure via Azure Templates. Additional resources JBoss EAP on Azure Migrate JBoss EAP applications to JBoss EAP on Azure App Service Migrate JBoss EAP applications to JBoss EAP on Azure VMs Migrate JBoss EAP applications to Azure Red Hat OpenShift 2.2. Unsupported Features There are some unsupported features when using JBoss EAP in a Microsoft Azure environment. ActiveMQ Artemis High Availability Using a Shared Store JBoss EAP messaging high availability using Artemis shared stores is not supported in Microsoft Azure. To configure JBoss EAP messaging high availability in Azure, see the instructions in the ActiveMQ Artemis High Availability section. mod_custer Advertising If you want to use JBoss EAP as an Undertow mod_cluster proxy load balancer, the mod_cluster advertisement functionally is unsupported because of Azure UDP multicast limitations. You must configure mod_cluster load balancing to use a proxy list instead of advertising . Virtual Machine Scale Set Transactions in Microsoft Azure Virtual Machine Scale Set (VMSS) is unsupported because the automatic scale down feature does not wait for all transactions to be completed during the scale down process. This could cause data integrity issues. Microsoft Azure VMSS destroys an EAP VM and does not support proper shutdown, which results in the following limitation for EAP clustering: VMSS should be supported for the configurations, in which the server-side state for HA needs to be externalized to a third-party service, such as Red Hat Data Grid. JBoss EAP supports VMSS for HttpSessions externalization, but not for the stateful session bean. Azure App Service JTS is not supported in the JBoss EAP Azure App Service offering. Note Although JTS is not supported, Jakarta Transactions are supported under the following conditions: The automatic removal of instances is disabled. Instances are not removed manually, for example, by reducing the number of running instances using the Azure dashboard. Also, transactions over Jakarta Enterprise Beans-remoting are not supported.

Commands:
function::strtol Name function::strtol - strtol - Convert a string to a long. Synopsis Arguments str String to convert. base The base to use General Syntax strtol:long (str:string, base:long) Description This function converts the string representation of a number to an integer. The base parameter indicates the number base to assume for the string (eg. 16 for hex, 8 for octal, 2 for binary).

Commands:
function strtol:long(str:string,base:long)
Chapter 3. Deploying collectd and rsyslog Deploy collectd and rsyslog on the hosts to collect logs and metrics. Note You do not need to repeat this procedure for new hosts. The Manager configures the hosts automatically. Procedure Log in to the Manager machine using SSH. Copy /etc/ovirt-engine-metrics/config.yml.example to create /etc/ovirt-engine-metrics/config.yml.d/config.yml : Edit the ovirt_env_name and elasticsearch_host parameters in config.yml and save the file. These parameters are mandatory and are documented in the file. Note If you add a Manager or an Elasticsearch installation, copy the Manager's public key to your Metrics Store virtual machine using the following commands: Deploy collectd and rsyslog on the hosts:

Commands:
cp /etc/ovirt-engine-metrics/config.yml.example /etc/ovirt-engine-metrics/config.yml.d/config.yml
mytemp=USD(mktemp -d) cp /etc/pki/ovirt-engine/keys/engine_id_rsa USDmytemp ssh-keygen -y -f USDmytemp/engine_id_rsa > USDmytemp/engine_id_rsa.pub ssh-copy-id -i USDmytemp/engine_id_rsa.pub root@{elasticsearch_host} rm -rf USDmytemp
/usr/share/ovirt-engine-metrics/setup/ansible/configure_ovirt_machines_for_metrics.sh