mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Eclipse Temurin features Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. For the list of changes and security fixes that the latest OpenJDK 11 release of Eclipse Temurin includes, see OpenJDK 11.0.19 Released . New features and enhancements Review the following release notes to understand new features and feature enhancements included with the Eclipse Temurin 11.0.19 release: SSLv2Hello and SSLv3 protocols removed from default-enabled TLS protocols SSLv2Hello and SSLv3 are versions of the SSL protocol that are disabled by default, because they have not been considered secure for some time. The SSLv2Hello and SSLv3 protocols are superseded by the more secure and modern TLS protocol and users can switch to TLS versions 1.2 or 1.3. With release OpenJDK 11.0.19, the list of default-enabled protocols no longer includes SSLv2Hello and SSLv3. Therefore, even if you remove SSLv3 from the jdk.tls.disabledAlgorithms security property, the following methods no longer return SSLv3: SSLServerSocket.getEnabledProtocols() SSLEngine.getEnabledProtocols() SSLParameters.getProtocols() Now, if you want to enable SSLv3, you must use the jdk.tls.client.protocols or jdk.tls.server.protocols system property on the command line, or call one of the following methods to enable SSLv3 programmatically: SSLSocket.setEnabledProtocols() SSLServerSocket.setEnabledProtocols() SSLEngine.setEnabledProtocols() See JDK-8190492 (JDK Bug System) . Certigna (Dhimyotis) root certificate authority (CA) certificate added In release OpenJDK 11.0.19, the cacerts truststore includes the Certigna (Dhimyotis) root certificate: Name: Certigna (Dhimyotis) Alias name: certignarootca Distinguished name: CN=Certigna, O=Dhimyotis, C=FR See JDK-8245654 (JDK Bug System) . listRoots method returns all available drives on Windows In releases, the java.io.File.listRoots() method on Windows systems filtered out any disk drives that were not accessible or did not have media loaded. However, this filtering led to observable performance issues. Now, with release OpenJDK 11.0.19, the listRoots method returns all available disk drives unfiltered. See JDK-8208077 (JDK Bug System) . Enhanced Swing platform support In earlier releases of OpenJDK, HTML object tags rendered embedded in Swing HTML components. With release OpenJDK 11.0.19, rendering only occurs if you set the new system property swing.html.object to true. By default, the swing.html.object property is set to false. JDK bug system reference ID: JDK-8296832. Revised on 2024-05-09 16:48:10 UTC

Commands:
Preface As a business analyst, system administrator, or business rules developer, the types of Red Hat Process Automation Manager business assets that you create and the way in which you develop, store, execute, and deploy those assets varies based on the needs of your business automation environment. You can design a decision management architecture that uses Business Central or an external integrated development environment (IDE) for asset development, a built-in or external Git repository for storage and version control, a KIE Server or embedded application for deployment, or other implementation combinations. You can also deploy Red Hat Process Automation Manager into a Red Hat OpenShift Container Platform environment for an enhanced containerized implementation. This document describes basic concepts and options for a Red Hat Process Automation Manager implementation to consider when designing your decision management architecture. To verify the most suitable implementation for your environment, contact your Red Hat Technical Account Manager or Solutions Architect.

Commands:
Chapter 12. Accessing the RADOS Object Gateway S3 endpoint Users can access the RADOS Object Gateway (RGW) endpoint directly. In versions of Red Hat OpenShift Data Foundation, RGW service needed to be manually exposed to create RGW public route. As of OpenShift Data Foundation version 4.7, the RGW route is created by default and is named rook-ceph-rgw-ocs-storagecluster-cephobjectstore .

Commands:
Chapter 2. Dashboard The Dashboard provides an overview of the Red Hat Virtualization system status by displaying a summary of Red Hat Virtualization's resources and utilization. This summary can alert you to a problem and allows you to analyze the problem area. The information in the dashboard is updated every 15 minutes by default from Data Warehouse, and every 15 seconds by default by the Manager API, or whenever the Dashboard is refreshed. The Dashboard is refreshed when the user changes back from another page or when manually refreshed. The Dashboard does not automatically refresh. The inventory card information is supplied by the Manager API and the utilization information is supplied by Data Warehouse. The Dashboard is implemented as a UI plugin component, which is automatically installed and upgraded alongside the Manager. Figure 2.1. The Dashboard 2.1. Prerequisites The Dashboard requires that Data Warehouse is installed and configured. See Installing and Configuring Data Warehouse in the Data Warehouse Guide .

Commands:
Chapter 5. Network Security in a Virtualized Environment 5.1. Network Security Overview In almost all situations, the network is the only way to access systems, applications and management interfaces. As networking plays such a critical role in the management of virtualized systems and the availability of their hosted applications, it is very important to ensure that the network channels both to and from the virtualized systems are secure. Securing the network allows administrators to control access and protect sensitive data from information leaks and tampering.

Commands:
Appendix B. List of tickets by component Component Tickets 389-ds-base BZ#1740693 , BZ#1662461 , BZ#1732053 , BZ#1749236 , BZ#1639342 , BZ#1723545 , BZ#1724914, BZ#1739182 , BZ#1749595 , BZ#1756182 , BZ#1685059 anaconda BZ#1680606, BZ#1712987, BZ#1767612 ansible BZ#1410996 , BZ#1439896, BZ#1660838 bind BZ#1758317 corosync BZ#1413573 criu BZ#1400230 custodia BZ#1403214 desktop BZ#1509444, BZ#1481411 dnf BZ#1461652 fence-agents BZ#1476401 filesystems BZ#1666535, BZ#1274459, BZ#1111712, BZ#1206277, BZ#1477977 firewalld BZ#1738785 , BZ#1723610, BZ#1637675 , BZ#1713823 freeradius BZ#1463673 fwupd BZ#1623466 gnome-shell BZ#1720286 , BZ#1539772, BZ#1481395 hardware-enablement BZ#1660791, BZ#1062759, BZ#1384452, BZ#1519746, BZ#1454918, BZ#1454916 identity-management BZ#1405325 ipa BZ#1711172 , BZ#1544470 , BZ#1754494 , BZ#1733209 , BZ#1691939, BZ#1583950, BZ#1755223 , BZ#1115294 , BZ#1298286 , BZ#1518939 java-1.8.0-openjdk BZ#1498932, BZ#1746874 kernel-rt BZ#1708718 , BZ#1550584 kernel BZ#1801759 , BZ#1713642, BZ#1373519, BZ#1808458 , BZ#1724027, BZ#1708465, BZ#1722855, BZ#1772107, BZ#1737111, BZ#1770232, BZ#1787295, BZ#1807077, BZ#1559615, BZ#1230959, BZ#1460849, BZ#1464377, BZ#1457533, BZ#1503123, BZ#1589397, BZ#1726642 kexec-tools BZ#1723492 libcacard BZ#917867 libguestfs BZ#1387213 libreswan BZ#1375750 libteam BZ#1704451 libvirt BZ#1475770 lorax-composer BZ#1718473 lvm2 BZ#1642162 mariadb BZ#1731062 networking BZ#1712737, BZ#1712918, BZ#1722686, BZ#1698551, BZ#1729033, BZ#1700691, BZ#1711520 , BZ#1062656, BZ#916384, BZ#916382, BZ#755087, BZ#1259547, BZ#1393375 nss BZ#1431210 , BZ#1425514 , BZ#1432142 openscap BZ#1767826 ovmf BZ#653382 pacemaker BZ#1710422 , BZ#1781820 pcs BZ#1433016 perl-Socket BZ#1693293 pki-core BZ#1523330 python-blivet BZ#1632274 python-kdcproxy BZ#1746107 rear BZ#1693608 resource-agents BZ#1513957 rsyslog BZ#1309698 samba BZ#1724991 scap-security-guide BZ#1691336 , BZ#1755192 , BZ#1791583 , BZ#1726698 , BZ#1777862 selinux-policy BZ#1687497, BZ#1727379 , BZ#1651253 , BZ#1752577 services BZ#1749776 sos BZ#1704957 sssd BZ#1068725 storage BZ#1649493, BZ#1642968, BZ#1710533, BZ#1703180, BZ#1109348, BZ#1119909, BZ#1414957 systemd BZ#1284974 tools BZ#1569484 usbguard BZ#1480100 virtualization BZ#1607311, BZ#1746771, BZ#1751054 , BZ#1773478 , BZ#1103193, BZ#1348508, BZ#1299662 , BZ#1661654

Commands:
Chapter 3. Searches 3.1. Performing Searches in Red Hat Virtualization The Administration Portal allows you to manage thousands of resources, such as virtual machines, hosts, users, and more. To perform a search, enter the search query (free-text or syntax-based) into the search bar, available on the main page for each resource. Search queries can be saved as bookmarks for future reuse, so you do not have to reenter a search query each time the specific search results are required. Searches are not case sensitive.

Commands:
5.4.2. Disabling SELinux When SELinux is disabled, SELinux policy is not loaded at all; it is not enforced and AVC messages are not logged. Therefore, all benefits of running SELinux listed in Section 2.1, "Benefits of running SELinux" are lost. Important Red Hat strongly recommends to use permissive mode instead of permanently disabling SELinux. See Section 5.4.1.2, "Permissive Mode" for more information about permissive mode. To permanently disable SELinux, follow the procedure below: Procedure 5.4. Disabling SELinux Configure SELINUX=disabled in the /etc/selinux/config file: Reboot your system. After reboot, confirm that the getenforce command returns Disabled :

Commands:
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= disabled SELINUXTYPE= can take one of these two values: targeted - Targeted processes are protected, mls - Multi Level Security protection. SELINUXTYPE=targeted
~]~ getenforce Disabled
Preface Metrics Store collects logs and metrics from Red Hat Virtualization. The data is transferred from Red Hat Virtualization to Red Hat OpenShift where it is stored and aggregated in Elasticsearch and saved in indexes. The data can then be analyzed and visualized in Kibana. Elasticsearch is a distributed, RESTful search and analytics engine that lets you perform and combine many types of searches. Kibana is an open source analytics and visualization platform designed to work with Elasticsearch. You can easily perform advanced data analysis and visualize your data in a variety of charts and tables.

Commands:
Chapter 1. Introduction to Anaconda customization 1.1. Introduction to Anaconda Customization The Red Hat Enterprise Linux and Fedora installation program, Anaconda , brings many improvements in its most recent versions. One of these improvements is enhanced customizability. You can now write add-ons to extend the base installer functionality, and change the appearance of the graphical user interface. This document will explain how to customize the following: Boot menu - pre-configured options, color scheme and background Appearance of the graphical interface - logo, backgrounds, product name Installer functionality - add-ons which can enhance the installer by adding new Kickstart commands and new screens in the graphical and textual user interfaces Also note that this document applies only to Red Hat Enterprise Linux 8 and Fedora 17 and later. Important Procedures described in this book are written for Red Hat Enterprise Linux 9 or a similar system. On other systems, the tools and applications used (such as genisoimage for creating custom ISO images) may be different, and procedures may need to be adjusted. Support Statement Red Hat supports only customizing the Red Hat Enterprise Linux installation media and images by using Red Hat Enterprise Linux Image Builder. Alternatively, you can use Kickstart to deploy consistent systems in your infrastructure.

Commands:
Chapter 4. Cleaning Integration Test Suite (tempest) resources Before you validate your deployments by using OpenStack Integration Test Suite (tempest), run the cleanup command with the --init-saved-state flag. This command scans your environment to discover resources, for example networks, volumes, images, flavors, projects, and users. The discovered resources are saved in a file called saved_state.json . When the tempest cleanup command is executed all resources not recorded in the saved_state.json file are deleted. Prerequisites An OpenStack environment that contains the Integration Test Suite packages. An Integration Test Suite configuration that corresponds to your OpenStack environment. For more information, see Creating a workspace . One or more completed Integration Test Suite validation tests. 4.1. Performing a dry run Perform a dry run before you execute the cleanup. A dry run lists the files that Integration Test Suite would delete by a cleanup, without actually deleting any files. The dry_run.json file contains the list of files that a cleanup deletes. Procedure Complete the dry run: Review the dry_run.json file to ensure that the cleanup does not delete any files that you require for your environment. 4.2. Performing a tempest clean up Before you run any tempest tests, you must initialize the saved state. This creates the file saved_state.json , which prevents the cleanup from deleting objects that must be kept. Warning If you do not run the cleanup command with the --init-saved-state flag, RHOSP objects are deleted. If you create objects after running the cleanup command with --init-saved-state , those objects can be deleted by subsequent tempest commands. Procedure Initialize the saved state to create the saved_state.json file: Perform the cleanup: The tempest cleanup command deletes tempest resources but does not delete projects or the tempest administrator account. Note You can modify the saved_state.json file to include or exclude objects that you want to retain or remove.

Commands:
tempest cleanup --dry-run
tempest cleanup --init-saved-state
tempest cleanup
Chapter 1. Red Hat Enterprise Linux 6.10 International Languages Red Hat Enterprise Linux 6.10 supports installation of multiple languages and changing of languages based on your requirements. The following languages are supported in Red Hat Enterprise Linux 6.10: East Asian Languages - Japanese, Korean, Simplified Chinese, and Traditional Chinese European Languages - English, German, Spanish, French, Portuguese Brazilian, and Russian, The table below summarizes the currently supported languages, their locales, default fonts installed and packages required for some of the supported languages Table 1.1. Red Hat Enterprise Linux 6 International Languages Territory Language Locale Fonts Package Names China Simplified Chinese zh_CN.UTF-8 AR PL (ShanHeiSun and Zenkai) Uni fonts-chinese, scim-pinyin, scim-tables Japan Japanese ja_JP.UTF-8 Sazanami (Gothic and Mincho) fonts-japanese, scim-anthy Korea Hangul ko_KR.UTF-8 Baekmuk (Batang, Dotum, Gulim, Headline) fonts-korean, scim-hangul Taiwan Traditional Chinese zh_TW.UTF-8 AR PL (ShanHeiSun and Zenkai) Uni fonts-chinese, scim-chewing, scim-tables Brazil Portuguese pt_BR.UTF-8 standard latin fonts France French ft_FR.UTF-8 standard latin fonts Germany German de_DE.UTF-8 standard latin fonts Italy Italy it_IT.UTF-8 standard latin fonts Russia Russian ru_RU.UTF-8 Cyrillic dejavu-lgc-sans-fonts, dejavu-lgc-sans-mono-fonts, dejavu-lgc-serif-fonts, xorg-x11-fonts-cyrillic Spain Spanish es_ES.UTF-8 standard latin fonts

Commands:
15.5.3. Anonymous User Options The following lists directives which control anonymous user access to the server. To use these options, the anonymous_enable directive must be set to YES . anon_mkdir_write_enable - When enabled in conjunction with the write_enable directive, anonymous users are allowed to create new directories within a parent directory which has write permissions. The default value is NO . anon_root - Specifies the directory vsftpd changes to after an anonymous user logs in. There is no default value for this directive. anon_upload_enable - When enabled in conjunction with the write_enable directive, anonymous users are allowed to upload files within a parent directory which has write permissions. The default value is NO . anon_world_readable_only - When enabled, anonymous users are only allowed to download world-readable files. The default value is YES . ftp_username - Specifies the local user account (listed in /etc/passwd ) used for the anonymous FTP user. The home directory specified in /etc/passwd for the user is the root directory of the anonymous FTP user. The default value is ftp . no_anon_password - When enabled, the anonymous user is not asked for a password. The default value is NO . secure_email_list_enable - When enabled, only a specified list of email passwords for anonymous logins are accepted. This is a convenient way to offer limited security to public content without the need for virtual users. Anonymous logins are prevented unless the password provided is listed in /etc/vsftpd.email_passwords . The file format is one password per line, with no trailing white spaces. The default value is NO .

Commands:
5.10. Starting the Cluster Software After you have propagated the cluster configuration to the cluster nodes you can either reboot each node or start the cluster software on each cluster node by running the following commands at each node in this order: service ccsd start service cman start (or service lock_gulmd start for GULM clusters) service fenced start (DLM clusters only) service clvmd start , if CLVM has been used to create clustered volumes Note Shared storage for use in Red Hat Cluster Suite requires that you be running the cluster logical volume manager daemon ( clvmd ) or the High Availability Logical Volume Management agents (HA-LVM). If you are not able to use either the clvmd daemon or HA-LVM for operational reasons or because you do not have the correct entitlements, you must not use single-instance LVM on the shared disk as this may result in data corruption. If you have any concerns please contact your Red Hat service representative. service gfs start , if you are using Red Hat GFS service rgmanager start , if the cluster is running high-availability services ( rgmanager ) Start the Red Hat Cluster Suite management GUI. At the Cluster Configuration Tool tab, verify that the configuration is correct. At the Cluster Status Tool tab verify that the nodes and services are running as expected.

Commands:
4.3. Power Management The Red Hat Virtualization Manager is capable of rebooting hosts that have entered a non-operational or non-responsive state, as well as preparing to power off under-utilized hosts to save power. This functionality depends on a properly configured power management device. The Red Hat Virtualization environment supports the following power management devices: American Power Conversion ( apc ) IBM Bladecenter ( Bladecenter ) Cisco Unified Computing System ( cisco_ucs ) Dell Remote Access Card 5 ( drac5 ) Dell Remote Access Card 7 ( drac7 ) Electronic Power Switch ( eps ) HP BladeSystem ( hpblade ) Integrated Lights Out ( ilo , ilo2 , ilo3 , ilo4 ) Intelligent Platform Management Interface ( ipmilan ) Remote Supervisor Adapter ( rsa ) Fujitsu-Siemens RSB ( rsb ) Western Telematic, Inc ( wti ) HP servers should use ilo3 or ilo4 , Dell servers use drac5 or Integrated Dell Remote Access Controllers ( idrac ), and IBM servers use ipmilan . Integrated Management Module (IMM) uses the IPMI protocol, and therefore IMM users can use ipmilan . Note APC 5.x power management devices are not supported by the apc fence agent. Use the apc_snmp fence agent instead. In order to communicate with the listed power management devices, the Red Hat Virtualization Manager makes use of fence agents. The Red Hat Virtualization Manager allows administrators to configure a fence agent for the power management device in their environment with parameters the device will accept and respond to. Basic configuration options can be configured using the graphical user interface. Special configuration options can also be entered, and are passed un-parsed to the fence device. Special configuration options are specific to a given fence device, while basic configuration options are for functionalities provided by all supported power management devices. The basic functionalities provided by all power management devices are: Status : check the status of the host. Start : power on the host. Stop : power down the host. Restart : restart the host. Actually implemented as stop, wait, status, start, wait, status. Best practice is to test the power management configuration once when initially configuring it, and occasionally after that to ensure continued functionality. Resilience is provided by properly configured power management devices in all of the hosts in an environment. Fencing agents allow the Red Hat Virtualization Manager to communicate with host power management devices to bypass the operating system on a problem host, and isolate the host from the rest of its environment by rebooting it. The Manager can then reassign the SPM role, if it was held by the problem host, and safely restart any highly available virtual machines on other hosts.

Commands:
3.8. Enabling IP Multicast with IGMP The Internet Group Management Protocol (IGMP) enables the administrator to manage routing and subscription to multicast traffic between networks, hosts, and routers. The kernel in Red Hat Enterprise Linux supports IGMPv3. To display multicast information, use the ip maddr show subcommand, for example: Alternatively, look for the MULTICAST string in the ip link show command output, for example: To disable multicast on a device and to check that multicast is disabled on the br0 device: The missing MULTICAST string indicates that multicast is disabled. To enable multicast on the br0 device and to check it is enabled: See the ip Command Cheat Sheet for Red Hat Enterprise Linux article and the ip(8) man page for more information. To check current version of IGMP and IP addresses subscribed for multicasting, see the /proc/net/igmp file: Note IGMP is not enabled in firewalld by default. To enable IGMP for a zone: See the Using Firewalls chapter in the Red Hat Enterprise Linux Security Guide for more information.

Commands:
~]USD ip maddr show dev br0 8: br0 inet 224.0.0.1 inet6 ff02::1 inet6 ff01::1 [output truncated]
~]USD ip link show br0 8: br0: <BROADCAST, MULTICAST ,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000 link/ether 6c:0b:84:67:fe:63 brd ff:ff:ff:ff:ff:ff
~]# ip link set multicast off dev br0 ~]USD ip link show br0 8: br0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000 link/ether 6c:0b:84:67:fe:63 brd ff:ff:ff:ff:ff:ff
~]# ip link set multicast on dev br0 ~]USD ip link show br0 8: br0: <BROADCAST, MULTICAST ,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000 link/ether 6c:0b:84:67:fe:63 brd ff:ff:ff:ff:ff:ff
~]USD cat /proc/net/igmp
~]# firewall-cmd --zone= zone-name --add-protocol=igmp
7.7. RHEA-2013:1686 - new package: sapconf A new sapconf package is now available for Red Hat Enterprise Linux 6. The sapconf package contains a script that checks the basic installation of Red Hat Enterprise Linux and modifies it according to SAP requirements. The script ensures that all necessary packages are installed and that configuration parameters are set correctly to run SAP software. This enhancement update adds the sapconf package to Red Hat Enterprise Linux 6. This package is available through the "Red Hat Enterprise Linux for SAP Business Applications" channel. (BZ# 910838 ) All users who running SAP software on Red Hat Enterprise Linux 6 are advised to install this new package.

Commands: