mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 41. Configuring the environment mode in KIE Server and Business Central You can set KIE Server to run in production mode or in development mode. Development mode provides a flexible deployment policy that enables you to update existing deployment units (KIE containers) while maintaining active process instances for small changes. It also enables you to reset the deployment unit state before updating active process instances for larger changes. Production mode is optimal for production environments, where each deployment creates a new deployment unit. In a development environment, you can click Deploy in Business Central to deploy the built KJAR file to a KIE Server without stopping any running instances (if applicable), or click Redeploy to deploy the built KJAR file and replace all instances. The time you deploy or redeploy the built KJAR, the deployment unit (KIE container) is automatically updated in the same target KIE Server. In a production environment, the Redeploy option in Business Central is disabled and you can click only Deploy to deploy the built KJAR file to a new deployment unit (KIE container) on a KIE Server. Procedure To configure the KIE Server environment mode, set the org.kie.server.mode system property to org.kie.server.mode=development or org.kie.server.mode=production . To configure the deployment behavior for a project in Business Central, go to project Settings General Settings Version and toggle the Development Mode option. Note By default, KIE Server and all new projects in Business Central are in development mode. You cannot deploy a project with Development Mode turned on or with a manually added SNAPSHOT version suffix to a KIE Server that is in production mode.

Commands:
Chapter 2. Preparing your environment for Satellite installation in an IPv6 network You can install and use Satellite in an IPv6 network. Before installing Satellite in an IPv6 network, view the limitations and ensure that you meet the requirements. To provision hosts in an IPv6 network, after installing Satellite, you must also configure Satellite for the UEFI HTTP boot provisioning. For more information, see Section 4.5, "Configuring Satellite for UEFI HTTP boot provisioning in an IPv6 network" . 2.1. Limitations of Satellite installation in an IPv6 network Satellite installation in an IPv6 network has the following limitations: You can install Satellite and Capsules in IPv6-only systems, dual-stack installation is not supported. Although Satellite provisioning templates include IPv6 support for PXE and HTTP (iPXE) provisioning, the only tested and certified provisioning workflow is the UEFI HTTP Boot provisioning. This limitation only relates to users who plan to use Satellite to provision hosts. 2.2. Requirements for Satellite installation in an IPv6 network Before installing Satellite in an IPv6 network, ensure that you meet the following requirements: You must deploy an external DHCP IPv6 server as a separate unmanaged service to bootstrap clients into GRUB2, which then configures IPv6 networking either using DHCPv6 or assigning static IPv6 address. This is required because the DHCP server in Red Hat Enterprise Linux (ISC DHCP) does not provide an integration API for managing IPv6 records, therefore the Capsule DHCP plugin that provides DHCP management is limited to IPv4 subnets. You must deploy an external HTTP proxy server that supports both IPv4 and IPv6. This is required because Red Hat Content Delivery Network distributes content only over IPv4 networks, therefore you must use this proxy to pull content into the Satellite on your IPv6 network. You must configure Satellite to use this dual stack (supporting both IPv4 and IPv6) HTTP proxy server as the default proxy. For more information, see Adding a Default HTTP Proxy to Satellite .

Commands:
Chapter 1. Red Hat OpenShift support for Windows Containers overview Red Hat OpenShift support for Windows Containers is a feature providing the ability to run Windows compute nodes in an OpenShift Container Platform cluster. This is possible by using the Red Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes. With a Red Hat subscription, you can get support for running Windows workloads in OpenShift Container Platform. For more information, see the release notes . For workloads including both Linux and Windows, OpenShift Container Platform allows you to deploy Windows workloads running on Windows Server containers while also providing traditional Linux workloads hosted on Red Hat Enterprise Linux CoreOS (RHCOS) or Red Hat Enterprise Linux (RHEL). For more information, see getting started with Windows container workloads . You need the WMCO to run Windows workloads in your cluster. The WMCO orchestrates the process of deploying and managing Windows workloads on a cluster. For more information, see how to enable Windows container workloads . You can create a Windows MachineSet object to create infrastructure Windows machine sets and related machines so that you can move supported Windows workloads to the new Windows machines. You can create a Windows MachineSet object on multiple platforms. You can schedule Windows workloads to Windows compute nodes. You can perform Windows Machine Config Operator upgrades to ensure that your Windows nodes have the latest updates. You can remove a Windows node by deleting a specific machine. You can disable Windows container workloads by performing the following: Uninstalling the Windows Machine Config Operator Deleting the Windows Machine Config Operator namespace

Commands:
Chapter 109. Checking IdM replication using Healthcheck You can test Identity Management (IdM) replication using the Healthcheck tool. Prerequisites You are using RHEL version 8.1 or newer. 109.1. Replication healthcheck tests The Healthcheck tool tests the Identity Management (IdM) topology configuration and searches for replication conflict issues. To list all tests, run the ipa-healthcheck with the --list-sources option: The topology tests are placed under the ipahealthcheck.ipa.topology and ipahealthcheck.ds.replication sources: IPATopologyDomainCheck This test verifies: That no single server is disconnected from the topology. That servers do not have more than the recommended number of replication agreements. If the test succeeds, the test returns the configured domains. Otherwise, specific connection errors are reported. Note The test runs the ipa topologysuffix-verify command for the domain suffix. It also runs the command for the ca suffix if the IdM Certificate Authority server role is configured on this server. ReplicationConflictCheck The test searches for entries in LDAP matching (&(!(objectclass=nstombstone))(nsds5ReplConflict=*)) . Note Run these tests on all IdM servers when trying to check for issues. Additional resources Solving common replication problems 109.2. Screening replication using Healthcheck Follow this procedure to run a standalone manual test of an Identity Management (IdM) replication topology and configuration using the Healthcheck tool. The Healthcheck tool includes many tests. Therefore, you can shorten the results with: Replication conflict test: --source=ipahealthcheck.ds.replication Correct topology test: --source=ipahealthcheck.ipa.topology Prerequisites You are logged in as the root user. Procedure To run Healthcheck replication conflict and topology checks, enter: Four different results are possible: SUCCESS - the test passed successfully. WARNING - the test passed but there might be a problem. ERROR - the test failed. CRITICAL - the test failed and it affects the IdM server functionality. Additional resources man ipa-healthcheck 109.3. Additional resources Healthcheck in IdM

Commands:
ipa-healthcheck --list-sources
ipa-healthcheck --source=ipahealthcheck.ds.replication --source=ipahealthcheck.ipa.topology
{ "source": "ipahealthcheck.ipa.topology", "check": "IPATopologyDomainCheck", "result": "SUCCESS", "kw": { "suffix": "domain" } }
{ "source": "ipahealthcheck.ipa.topology", "check": "IPATopologyDomainCheck", "result": "ERROR", "uuid": d6ce3332-92da-423d-9818-e79f49ed321f "when": 20191007115449Z "duration": 0.005943 "kw": { "msg": "topologysuffix-verify domain failed, server2 is not connected (server2_139664377356472 in MainThread)" } }
6.2. Configuration Tasks Configuring Red Hat High Availability Add-On software with the ccs consists of the following steps: Ensuring that ricci is running on all nodes in the cluster. Refer to Section 6.3, "Starting ricci " . Creating a cluster. Refer to Section 6.4, "Creating and Modifying a Cluster" . Configuring fence devices. Refer to Section 6.5, "Configuring Fence Devices" . Configuring fencing for cluster members. Refer to Section 6.7, "Configuring Fencing for Cluster Members" . Creating failover domains. Refer to Section 6.8, "Configuring a Failover Domain" . Creating resources. Refer to Section 6.9, "Configuring Global Cluster Resources" . Creating cluster services. Refer to Section 6.10, "Adding a Cluster Service to the Cluster" . Configuring a quorum disk, if necessary. Refer to Section 6.13, "Configuring a Quorum Disk" . Configuring global cluster properties. Refer to Section 6.14, "Miscellaneous Cluster Configuration" . Propagating the cluster configuration file to all of the cluster nodes. Refer to Section 6.15, "Propagating the Configuration File to the Cluster Nodes" .

Commands:
Preface Red Hat OpenShift Container Storage 4.8 supports deployment on existing Red Hat OpenShift Container Platform (RHOCP) using Red Hat OpenStack Platform clusters. Note Both internal and external Openshift Container Storage clusters are supported on Red Hat OpenStack Platform. See Planning your deployment for more information about deployment requirements. To deploy OpenShift Container Storage, start with the requirements in Preparing to deploy OpenShift Container Storage chapter and then follow the appropriate deployment process for your environment: Internal mode Deploying OpenShift Container Storage on Red Hat OpenStack Platform in internal mode . External mode Deploying OpenShift Container Storage on Red Hat OpenStack Platform in external mode

Commands:
B.17.3.2. Incorrect drive device type Symptom The definition of the source image for the CD-ROM virtual drive is not present, despite being added: Solution Correct the XML by adding the missing <source> parameter as follows: A type='block' disk device expects that the source is a physical device. To use the disk with an image file, use type='file' instead.

Commands:
virsh dumpxml domain <domain type='kvm'> <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> </disk> </domain>
<disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/path/to/image.iso'/> <target dev='hdc' bus='ide'/> <readonly/> </disk>
7.167. procps 7.167.1. RHBA-2015:1407 - procps bug fix and enhancement update Updated procps packages that fix two bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The procps packages contain a set of system utilities that provide system information. The procps packages include the following utilities: ps, free, skill, pkill, pgrep, snice, tload, top, uptime, vmstat, w, watch, and pwdx. Bug Fixes BZ# 1163404 Previously, behavior of the libproc library was unreliable when it was loaded with the dlopen() call after the environment was changed with the setenv() call. As a consequence, an invalid memory access error could occur in libproc. With this update, the find_elf_note() function obtains the auxiliary vector values using a different and safer method based on parsing the /proc/self/auxv file, and the described problem no longer occurs. BZ# 1172059 Prior to this update, the stat2proc() function did not process empty files correctly. Consequently, when an empty stat file was processed, the ps utility could terminate unexpectedly with a segmentation fault. Handling of empty stat files has been fixed, and ps no longer crashes in this scenario. Enhancements BZ# 1120580 This update introduces the new "--system" option to the sysctl utility. This option enables sysctl to process configuration files from a group of system directories. BZ# 993072 The new "-h" option has been added to the "free" utility. The purpose of this option is to show all output fields automatically scaled to the shortest three-digit representation including the unit, making the output conveniently human-readable. BZ# 1123311 The "w" utility now includes the "-i" option to display IP addresses instead of host names in the "FROM" column. Users of procps are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 19. Clustering clufter The clufter package, available as a Technology Preview in Red Hat Enterprise Linux 6, provides a tool for transforming and analyzing cluster configuration formats. It can be used to assist with migration from an older stack configuration to a newer configuration that leverages Pacemaker. For information on the capabilities of clufter , see the clufter(1) man page or the output of the clufter -h command. Package: clufter-0.56.2-1 luci support for fence_sanlock The luci tool now supports the sanlock fence agent as a Technology Preview. The agent is available in the luci's list of agents. Package: luci-0.26.0-78 Recovering a node using a hardware watchdog device New fence_sanlock agent and checkquorum.wdmd, included in Red Hat Enterprise Linux 6.4 as a Technology Preview, provide new mechanisms to trigger the recovery of a node using a hardware watchdog device. Tutorials on how to enable this Technology Preview will be available at https://fedorahosted.org/cluster/wiki/HomePage Note that SELinux in enforcing mode is currently not supported. Package: cluster-3.0.12.1-78

Commands:
21.2. Terminology This section explains the terms used throughout this chapter. libguestfs (GUEST FileSystem LIBrary) - the underlying C library that provides the basic functionality for opening disk images, reading and writing files, and so on. You can write C programs directly to this API. guestfish (GUEST Filesystem Interactive SHell) is an interactive shell that you can use from the command line or from shell scripts. It exposes all of the functionality of the libguestfs API. Various virt tools are built on top of libguestfs, and these provide a way to perform specific single tasks from the command line. These tools include virt-df , virt-rescue , virt-resize , and virt-edit . augeas is a library for editing the Linux configuration files. Although this is separate from libguestfs, much of the value of libguestfs comes from the combination with this tool. guestmount is an interface between libguestfs and FUSE. It is primarily used to mount file systems from disk images on your host physical machine. This functionality is not necessary, but can be useful.

Commands:
Deploying OpenShift Data Foundation using IBM Z Red Hat OpenShift Data Foundation 4.17 Instructions on deploying Red Hat OpenShift Data Foundation to use local storage on IBM Z Red Hat Storage Documentation Team Abstract Read this document for instructions about how to install Red Hat OpenShift Data Foundation to use local storage on IBM Z. Note While this document refers only to IBM Z, all information in it also applies to IBM(R) LinuxONE.

Commands:
Chapter 11. Container Images Based on Red Hat Software Collections 3.0 Component Description Supported architectures Application Images rhscl/nodejs-8-rhel7 Node.js 8 platform for building and running applications (EOL) x86_64, s390x, ppc64le rhscl/php-71-rhel7 PHP 7.1 platform for building and running applications (EOL) x86_64 rhscl/python-36-rhel7 Python 3.6 platform for building and running applications (EOL) x86_64, s390x, ppc64le Daemon Images rhscl/nginx-112-rhel7 nginx 1.12 server and a reverse proxy server (EOL) x86_64, s390x, ppc64le Database Images rhscl/mariadb-102-rhel7 MariaDB 10.2 SQL database server (EOL) x86_64 rhscl/mongodb-34-rhel7 MongoDB 3.4 NoSQL database server (EOL) x86_64 rhscl/postgresql-96-rhel7 PostgreSQL 9.6 SQL database server (EOL) x86_64 Legend: x86_64 - AMD64 and Intel 64 architectures s390x - 64-bit IBM Z ppc64le - IBM POWER, little endian All images are based on components from Red Hat Software Collections. The images are available for Red Hat Enterprise Linux 7 through the Red Hat Container Registry. For detailed information about components provided by Red Hat Software Collections 3.0, see the Red Hat Software Collections 3.0 Release Notes . For more information about the Red Hat Developer Toolset 7.0 components, see the Red Hat Developer Toolset 7 User Guide . For information regarding container images based on Red Hat Software Collections 2, see the Using Red Hat Software Collections 2 Container Images . EOL images are no longer supported.

Commands:
Chapter 2. Enabling and using the Red Hat Quay API By leveraging the Red Hat Quay API, you can streamline container registry management, automate tasks, and integrate Red Hat Quay's functionalities into your existing workflow. This can improve efficiency, offer enhanced flexibility (by way of repository management, user management, user permissions, image management, and so on), increase the stability of your organization, repository, or overall deployment, and more. Detailed instructions for how to use the Red Hat Quay API can be found in the Red Hat Quay API guide . In that guide, the following topics are covered: Red Hat Quay token types, including OAuth 2 access tokens, robot account tokens, and OCI referrers tokens, and how to generate these tokens. Enabling the Red Hat Quay API by configuring your config.yaml file. How to use the Red Hat Quay API by passing in your OAuth 2 account token into the desired endpoint. API examples, including one generic example of how an administrator might automate certain tasks. See the Red Hat Quay API guide before attempting to use the API endpoints offered in this chapter.

Commands:
Chapter 8. Fixed issues The issues fixed in Streams for Apache Kafka 2.9 on RHEL. For details of the issues fixed in Kafka 3.9.0, refer to the Kafka 3.9.0 Release Notes. Table 8.1. Streams for Apache Kafka fixed issues Issue Number Description ENTMQST-4324 Make it possible to use Cruise Control to move all data between two JBOD disks ENTMQST-5318 [KAFKA] Improve MirrorMaker logging in case of authorization errors ENTMQST-6234 [BRIDGE] path label in metrics can contain very different values and that makes it hard to work with the metrics 8.1. Security updates Check the latest information about Streams for Apache Kafka security updates in the Red Hat Product Advisories portal. 8.2. Erratas Check the latest security and product enhancement advisories for Streams for Apache Kafka.

Commands:
Appendix A. Automation execution environments precedence Project updates will always use the control plane automation execution environments by default, however, jobs will use the first available automation execution environments as follows: The execution_environment defined on the template (job template or inventory source) that created the job. The default_environment defined on the project that the job uses. The default_environment defined on the organization of the job. The default_environment defined on the organization of the inventory the job uses. The current DEFAULT_EXECUTION_ENVIRONMENT setting (configurable at api/v2/settings/system/ ) Any image from the GLOBAL_JOB_EXECUTION_ENVIRONMENTS setting. Any other global execution environment. Note If more than one execution environment fits a criteria (applies for 6 and 7), the most recently created one is used.

Commands:
Chapter 3. Security and SAP Solutions Enterprises usually have substantial compliance requirements based on the industry, type of customers, geographic location, and more. Such requirements may need specific certifications, cryptographic modules, and support for encryptions. With Red Hat Enterprise Linux for SAP Solutions, Red{nbsp]Hat delivers a stable, security-focused, high-performance foundation for SAP business applications to support such requirements and provide an easy way to set and validate compliance policies. You can learn about processes and practices for securing Red Hat Enterprise Linux systems against local and remote intrusion, exploitation, and malicious activity. These approaches and tools can create a more secure environment for running SAP HANA. Additional resources For more information, see Security hardening guide for SAP HANA . 3.1. SELinux for SAP production environments SELinux is a security technology for process isolation to mitigate attacks via privilege escalation. Configuring SELinux helps you enhance your system's security. SELinux is an implementation of Mandatory Access Control (MAC), and provides an additional layer of security. The SELinux policy defines how users and processes can interact with the files on the system. You can control which users can perform which actions by mapping them to specific SELinux confined users. Additional resources For more information, see Using SELinux for SAP HANA . 3.2. File access policy Daemon for SAP File access policy Daemon fapolicyd is a technology provided in RHEL to determine access rights to files based on a trust database and file or process attributes. It helps customers to ensure data remains protected even in case an attacker has successfully gained control over certain processes. You can configure fapolicyd to secure the environment for running SAP HANA against local and remote intrusion, exploitation, and malicious activity. Additional resources For more information, see Configuring fapolicyd to allow only SAP HANA executables .

Commands:
Chapter 3. Testing requirements for Red Hat OpenStack Platform Application The RHOSP Application Testing Requirements will be required and provided by Red Hat in a test plan for each certification. The following tests are explained in Certification tests of this guide. System Report Test Supportability Test Director Test VNF Configuration Testing Report Test (for VNF only) You are expected to perform System Report, Supportability, and Director test for a regular RHOSP application. For VNF certification along with these three test you also need to perform the VNF Testing Configuration report test.

Commands:
Chapter 12. 4.9 Release Notes 12.1. New Features The following major enhancements have been introduced in Red Hat Update Infrastructure 4.9. Auto update packages on CDS With this update when a CDS is reinstalled, by default, a dnf update will be executed on the CDS host, resulting in RHEL RPMs being updated on the CDS server. Nginx Update With this update the version of nginx has been updated on the RHUA and CDS hosts. The number of versions preserved can now be customized Previously all repository versions were retained as newer versions were added taking up disk space and, in the worst case, the inability to delete a repository. Starting in RHUI version 4.7 only the latest five versions were preserved. With this update the new sub-command rhui-manager repo set_retain_versions has been added. This will allow users the ability to limit the number of versions on the repos that were originally created with no limit. Pulp Database migration to PostgreSQL v.15 With this version the user has the ability to optionally migrate the database used by Pulp to PostgreSQL v.15 . This can be done with the new rhui-installer flag --postgresql-version . For example: rhui-installer --rerun --postgresql-version 15 No longer used, orphan data, can now be cleaned up Previously RPM packages, repodata files, and other related files were kept on the disk even if they were no longer part of a repository. With this update the new sub-command rhui-manager repo orphan_cleanup has been added that can be used to clean up some of this no longer used orphaned data. 12.2. Bug Fixes The following bugs have been fixed in Red Hat Update Infrastructure 4.9 that have a significant impact on users. Avoid synchyronizations hanging if a network outage happens In the past if a network outage happened during a pulp synchronization of a repository the synchronization could hang indefinitely. With this update a network timeout will be leveraged in the underlying code to prevent this condition.

Commands: