mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 13. Setting up a high-availability CUPS print server environment If your clients require access to printers without interruption, you can set up CUPS on multiple hosts and use the print queue browsing feature to provide high availability. Print clients then automatically configure print queues shared by the different print servers. If a client sends a print job to its local print queue, CUPS on the client routes the job to one of the print servers which processes the job and sends it to the printer. Procedure Set up CUPS on two or more servers: Install and configure CUPS . Enable TLS encryption . Add print queues to all CUPS instances by using the lpadmin utility or the web interface . If you use the web interface, ensure that you select the Share this printer option while you add the printer. The lpadmin utility enables this setting by default. Important For the high-availability scenario, each queue on one print server requires a queue with exactly the same queue name on the other servers. You can display the queue names on each server by using the lpstat -e command. Optional: You can configure the queues on each server to refer to different printers. On print clients: Edit the /etc/cups/cups-browsed.conf file, and add BrowsePoll directives for each CUPS print server: Enable and start both the cups and cups-browsed service: Verification Display the available printers on a client: The example output shows that the Demo-printer queue uses the implicitclass back end. As a result, cups-browsed routes print jobs for this queue to the hosts specified in the BrowsePoll directives on this client. Additional resources High-availability printing in Red Hat Enterprise Linux (Red Hat Knowledgebase)

Commands:
BrowsePoll print_server_1.example.com:631 BrowsePoll print_server_2.example.com:631
systemctl enable --now cups cups-browsed
lpstat -t device for Demo-printer: implicitclass://Demo-printer/ Demo-printer accepting requests since Fri 22 Nov 2024 11:54:59 AM CET printer Demo-printer is idle. enabled since Fri 22 Nov 2024 11:54:59 AM CET
Chapter 23. Customizing the branding of Business Central You can customize the branding of the Business Central login page and application header by replacing the images with your own. 23.1. Customizing the Business Central login page You can customize the company logo and the project logo on the Business Central login page. Procedure Start Red Hat JBoss EAP and open Business Central in a web browser. Copy an SVG format image to the EAP_HOME /standalone/deployments/business-central.war/img/ directory in your Red Hat Process Automation Manager installation. In the EAP_HOME /standalone/deployments/business-central.war/img/ directory, either move or rename the existing redhat_logo.png file. Rename your PNG file redhat_logo.png . To change the project logo that appears above the User name and Password fields, replace the default image BC_Logo.png with a new SVG file. Force a full reload of the login page, bypassing the cache, to view the changes. For example, in most Linux and Windows web browsers, press Ctrl+F5. 23.2. Customizing Business Central application header You can customize the Business Central application header. Procedure Start Red Hat JBoss EAP, open Business Central in a web browser, and log in with your user credentials. Copy your new application header image in the SVG format to the EAP_HOME /standalone/deployments/business-central.war/banner/ directory in your Red Hat Process Automation Manager installation. Open the EAP_HOME /standalone/deployments/business-central.war/banner/banner.html file in a text editor. Replace logo.png in the <img> tag with the file name of your new image:admin-and-config/ Force a full reload of the login page, bypassing the cache, to view the changes. For example, in most Linux and Windows web browsers, press Ctrl+F5.

Commands:
<img src="banner/logo.png"/>
6.3.3. Colocating Sets of Resources If your configuration requires that you create a set of resources that is colocated and started in order, you can configure a resource group that contains those resources, as described in Section 5.5, "Resource Groups" . If, however, you need to colocate a set of resources but the resources do not necessarily need to start in order, you can create a colocation constraint on a set or sets of resources with the pcs constraint colocation set command. You can set the following options for a set of resources with the pcs constraint colocation set command. sequential , which can be set to true or false to indicate whether the members of the set must be colocated with each other. Setting sequential to false allows the members of this set to be colocated with another set listed later in the constraint, regardless of which members of this set are active. Therefore, this option makes sense only if another set is listed after this one in the constraint; otherwise, the constraint has no effect. role , which can be set to Stopped , Started , Master , or Slave . For information on multi-state resources, see Section 8.2, "Multi-State Resources: Resources That Have Multiple Modes" . You can set the following constraint options for a set of resources following the setoptions parameter of the pcs constraint colocation set command. kind , to indicate how to enforce the constraint. For information on this option, see Table 6.2, "Properties of an Order Constraint" . symmetrical , to indicate the order in which to stop the resources. If true, which is the default, stop the resources in the reverse order. Default value: true id , to provide a name for the constraint you are defining. When listing members of a set, each member is colocated with the one before it. For example, "set A B" means "B is colocated with A". However, when listing multiple sets, each set is colocated with the one after it. For example, "set C D sequential=false set A B" means "set C D (where C and D have no relation between each other) is colocated with set A B (where B is colocated with A)". The following command creates a colocation constraint on a set or sets of resources.

Commands:
pcs constraint colocation set resource1 resource2 [ resourceN ]... [ options ] [set resourceX resourceY ... [ options ]] [setoptions [ constraint_options ]]
3.16. RHEA-2011:1726 - new package: python-urwid A new python-urwid package is now available for Red Hat Enterprise Linux 6. The python-urwid package provides a library for development of text user interface applications in the Python programming environment. This enhancement update adds the python-urwid package to Red Hat Enterprise Linux 6 as part of the Technology Preview of Fibre Channel over Ethernet (FCoE) target mode. (BZ# 726775 ) Important This package is provided as a dependency of the fcoe-target-utils package. It is recommended to install it only as a prerequisite for running fcoe-target-utils, and not to use it independently. All users who want to use the Technology Preview of Fibre Channel over Ethernet target mode should install this newly-released package, which adds this enhancement.

Commands:
7.162. numad 7.162.1. RHBA-2013:0358 - numad bug fix and enhancement update Updated numad packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The numad packages provide a daemon for NUMA (Non-Uniform Memory Architecture) systems. Numad monitors NUMA characteristics and manages placement of processes and memory to minimize memory latency. Bug Fix BZ# 825153 Prior to this update, the "-lpthread" linker flag was supplied from both the Makefile and from the spec file. As a consequence, the numad packages encountered linkage problems and failed to build when trying to rebuild these packages from the source rpm. With this update, the flag is supplied only from the specfile and rebuilding the packages no longer fails. Enhancement BZ#830919 This update upgrades the numad source code to version 20121015 to be fully supported by Red Hat Enterprise Linux 6. All users of numad are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
Chapter 5. Deprecated functionality This part provides an overview of functionality that has been deprecated in Red Hat Satellite 6.15. Deprecated functionality will likely not be supported in future releases of this product and is not recommended for new deployments. For the most recent list of deprecated functionality within a particular major release, refer to the latest version of release documentation. The support status of deprecated functionality remains unchanged within Red Hat Satellite 6.15. For information about the length of support, see Red Hat Enterprise Linux Life Cycle and Red Hat Enterprise Linux Application Streams Life Cycle . Deprecated hardware components are not recommended for new deployments on the current or future releases. Hardware driver updates are limited to security and critical fixes only. Red Hat recommends replacing this hardware as soon as reasonably feasible. A package can be deprecated and not recommended for further use. Under certain circumstances, a package can be removed from a product. Product documentation then identifies more recent packages that offer functionality similar, identical, or more advanced to the one deprecated, and provides further recommendations. Entitlement-based subscription management Simple Content Access (SCA) will be the only subscription management mode as of Satellite 6.16. Entitlements Entitlement-based Subscription Management will be removed in Satellite 6.16. It is recommended to use Simple Content Access, which simplifies the entitlement experience for administrators in regards to subscriptions as a substitute. Jira:SAT-20195 Snapshot based backup The snapshot based backup functionality is deprecated and will be removed in a future release. Jira:SAT-20862 Asynchronous SSH remote execution mode The async-ssh remote execution mode was deprecated in 6.13. If you have unstable connectivity between Capsules and managed hosts, use the pull mode instead. For more information about pull mode, see Transport Modes for Remote Execution in Managing hosts . Provisioning on Red Hat Virtualization The integration of Red Hat Virtualization (RHV) with Satellite was deprecated in 6.13. All the existing compute resources of RHV type will be removed and the hosts associated with RHV will be disconnected. Bootstrap.py The bootstrap.py script used to register a host to Satellite or Capsule was deprecated in 6.9. It has been replaced by the curl command created with the global registration template. Jira:SAT-21137

Commands:
Part I. Getting started with decision services in Red Hat Process Automation Manager As a business rules developer, you can use Business Central in Red Hat Decision Manager or the Red Hat Decision Manager DMN modeler in VS Code to design a variety of decision services. Red Hat Decision Manager provides example projects with example business assets directly in Business Central as a reference. This document describes how to create and test an example traffic violation project based on the Traffic_Violation sample project included in Business Central. This sample project uses a Decision Model and Notation (DMN) model to define driver penalty and suspension rules in a traffic violation decision service. You can follow the steps in this document to create the project and the assets it contains, or open and review the existing Traffic_Violation sample project. For more information about the DMN components and implementation in Red Hat Decision Manager, see Designing a decision service using DMN models . Prerequisites Red Hat JBoss Enterprise Application Platform 7.4 is installed. For installation information, see Red Hat JBoss Enterprise Application Platform 7.4 Installation Guide . Red Hat Process Automation Manager is installed and configured with KIE Server. For more information see Installing and configuring Red Hat Decision Manager on Red Hat JBoss EAP 7.4 . Red Hat Decision Manager is running and you can log in to Business Central with the developer role. For more information, see Planning a Red Hat Decision Manager installation .

Commands:
Chapter 13. Installing kdump The kdump service is installed and activated by default on the new versions of RHEL 9 installations. 13.1. What is kdump kdump is a service that provides a crash dumping mechanism and generates a crash dump or a vmcore dump file. vmcore includes the contents of the system memory for analysis and troubleshooting. kdump uses the kexec system call to boot into the second kernel, capture kernel , without a reboot. This kernel captures the contents of the crashed kernel's memory and saves it into a file. The second kernel is available in a reserved part of the system memory. Important A kernel crash dump can be the only information available if a system failure occur. Therefore, operational kdump is important in mission-critical environments. Red Hat advises to regularly update and test kexec-tools in your normal kernel update cycle. This is important when you install new kernel features. If you have multiple kernels on a machine, you can enable kdump for all installed kernels or for specified kernels only. When you install kdump , the system creates a default /etc/kdump.conf file. /etc/kdump.conf includes the default minimum kdump configuration, which you can edit to customize the kdump configuration. 13.2. Installing kdump using Anaconda The Anaconda installer provides a graphical interface screen for kdump configuration during an interactive installation. You can enable kdump and reserve the required amount of memory. Procedure On the Anaconda installer, click KDUMP and enable kdump : In Kdump Memory Reservation , select Manual ` if you must customize the memory reserve. In KDUMP > Memory To Be Reserved (MB) , set the required memory reserve for kdump . = Installing kdump on the command line Installation options such as custom Kickstart installations, in some cases does not install or enable kdump by default. The following procedure helps you enable kdump in this case. Prerequisites An active RHEL subscription. A repository containing the kexec-tools package for your system CPU architecture. Fulfilled requirements for kdump configurations and targets. For details, see Supported kdump configurations and targets . Procedure Check if kdump is installed on your system: Output if the package is installed: Output if the package is not installed: Install kdump and other necessary packages:

Commands:
rpm -q kexec-tools
kexec-tools-2.0.22-13.el9.x86_64
package kexec-tools is not installed
dnf install kexec-tools
7.192. seabios 7.192.1. RHEA-2015:1355 - seabios enhancement update An updated seabios package that adds one enhancement is now available for Red Hat Enterprise Linux 6. The seabios package contains an open-source legacy BIOS implementation which can be used as a coreboot payload. It implements the standard BIOS calling interfaces that a typical x86 proprietary BIOS implements. Enhancement BZ# 1131530 The user can now access the boot menu by pressing the ESC key. Previously, the boot menu could only be accessed by pressing the F12 key. However, one some platforms, F12 can be unavailable. For example, systems running the OS X operating system can intercept certain function keys, including F12. With this update, the user can use either ESC or F12 to access the boot menu. Therefore, seabios avoids these potential problems associated with F12. Users of seabios are advised to upgrade to this updated package, which adds this enhancement.

Commands:
Chapter 3. Networking Operators overview OpenShift Container Platform supports multiple types of networking Operators. You can manage the cluster networking using these networking Operators. 3.1. Cluster Network Operator The Cluster Network Operator (CNO) deploys and manages the cluster network components in an OpenShift Container Platform cluster. This includes deployment of the Container Network Interface (CNI) default network provider plugin selected for the cluster during installation. For more information, see Cluster Network Operator in OpenShift Container Platform . 3.2. DNS Operator The DNS Operator deploys and manages CoreDNS to provide a name resolution service to pods. This enables DNS-based Kubernetes Service discovery in OpenShift Container Platform. For more information, see DNS Operator in OpenShift Container Platform . 3.3. Ingress Operator When you create your OpenShift Container Platform cluster, pods and services running on the cluster are each allocated IP addresses. The IP addresses are accessible to other pods and services running nearby but are not accessible to external clients. The Ingress Operator implements the Ingress Controller API and is responsible for enabling external access to OpenShift Container Platform cluster services. For more information, see Ingress Operator in OpenShift Container Platform . 3.4. External DNS Operator The External DNS Operator deploys and manages ExternalDNS to provide the name resolution for services and routes from the external DNS provider to OpenShift Container Platform. For more information, see Understanding the External DNS Operator . 3.5. Network Observability Operator The Network Observability Operator is an optional Operator that allows cluster administrators to observe the network traffic for OpenShift Container Platform clusters. The Network Observability Operator uses the eBPF technology to create network flows. The network flows are then enriched with OpenShift Container Platform information and stored in Loki. You can view and analyze the stored network flows information in the OpenShift Container Platform console for further insight and troubleshooting. For more information, see About Network Observability Operator .

Commands:
Chapter 4. Setting up the test environment The first step towards certifying your product is setting up the environment where you can run the tests. The test environment consists of one system: System 1: Acts as a host under test (HUT) 4.1. Setting up a system that acts as a host under test A system on which the product that needs certification is installed or configured is referred to as the host under test (HUT). Prerequisites The HUT has RHEL version 8 or 9 installed. For convenience, Red Hat provides kickstart files to install the HUT's operating system. Follow the instructions in the file that is appropriate for your system before launching the installation process. Procedure Configure the Red Hat Certification repository: Use your RHN credentials to register your system using Red Hat Subscription Management: Display the list of available subscriptions for your system: Search for the subscription which provides the Red Hat Certification (for RHEL Server) repository and make a note of the subscription and its Pool ID. Attach the subscription to your system: Replace the pool_ID with the Pool ID of the subscription. Note You don't have to attach the subscription to your system, if you enable the option Simple content access for Red Hat Subscription Management . For more details, see How do I enable Simple Content Access for Red Hat Subscription Management? Subscribe to the Red Hat Certification channel: On RHEL 8: Replace HOSTTYPE with the system architecture. To find out the system architecture, run Example: On RHEL 9: Replace HOSTTYPE with the system architecture. To find out the system architecture, run Example: Install cloud test suite package: steps See Chapter 5, Downloading the test plan from Red Hat Certification Portal

Commands:
subscription-manager register
subscription-manager list --available*
subscription-manager attach --pool= <pool_ID >
subscription-manager repos --enable=cert-1-for-rhel-8- <HOSTTYPE> -rpms
uname -m
subscription-manager repos --enable=cert-1-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=cert-1-for-rhel-9- <HOSTTYPE> -rpms
uname -m
subscription-manager repos --enable=cert-1-for-rhel-9-x86_64-rpms
yum install redhat-certification-cloud
Chapter 1. Enabling and giving access to the Role-Based Access Control (RBAC) feature The Role-Based Access Control (RBAC) feature is disabled by default. Enable the RBAC plugin and declare policy administrators to start using RBAC features. The permission policies for users and groups in the Developer Hub are managed by permission policy administrators. Only permission policy administrators can access the Role-Based Access Control REST API. Prerequisites You have added a custom Developer Hub application configuration , and have sufficient permissions to modify it. You have enabled an authentication provider . Procedure The RBAC plugin is installed but disabled by default. To enable the ./dynamic-plugins/dist/janus-idp-backstage-plugin-rbac plugin, edit your dynamic-plugins.yaml with the following content. dynamic-plugins.yaml fragment plugins: - package: ./dynamic-plugins/dist/janus-idp-backstage-plugin-rbac disabled: false See Installing and viewing dynamic plugins . Declare policy administrators to enable a select number of authenticated users to configure RBAC policies through the REST API or Web UI, instead of modifying the CSV file directly. The permissions can be specified in a separate CSV file referenced in the app-config-rhdh ConfigMap, or permissions can be created using the REST API or Web UI. To declare users such as <your_policy_administrator_name> as policy administrators, edit your custom Developer Hub ConfigMap, such as app-config-rhdh , and add following code to the app-config-rhdh.yaml content: app-config.yaml fragment permission: enabled: true rbac: admin: users: - name: user:default/ <your_policy_administrator_name> Verification Sign out from the existing Red Hat Developer Hub session and log in again using the declared policy administrator account. With RBAC enabled, most features are disabled by default. Navigate to the Catalog page in RHDH. The Create button is not visible. You cannot create new components. Navigate to the API page. The Register button is not visible. steps Explicitly enable permissions to resources in Developer Hub.

Commands:
plugins: - package: ./dynamic-plugins/dist/janus-idp-backstage-plugin-rbac disabled: false
permission: enabled: true rbac: admin: users: - name: user:default/ <your_policy_administrator_name>