mtpti5iD/redhat-docs_dataset huggingface dataset:
36.6.4. IBM eServer iSeries Systems The /boot/vmlinitrd- <kernel-version> file is installed when you upgrade the kernel. However, you must use the dd command to configure the system to boot the new kernel: As root, issue the command cat /proc/iSeries/mf/side to determine the default side (either A, B, or C). As root, issue the following command, where <kernel-version> is the version of the new kernel and <side> is the side from the command: Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.

Commands:
dd if=/boot/vmlinitrd- <kernel-version> of=/proc/iSeries/mf/ <side> /vmlinux bs=8k
Chapter 1. Getting started overview Use Red Hat Streams for Apache Kafka to create and set up Kafka clusters, then connect your applications and services to those clusters. This guide describes how to install and start using Streams for Apache Kafka on OpenShift Container Platform. You can install the Streams for Apache Kafka operator directly from the OperatorHub in the OpenShift web console. The Streams for Apache Kafka operator understands how to install and manage Kafka components. Installing from the OperatorHub provides a standard configuration of Streams for Apache Kafka that allows you to take advantage of automatic updates. When the Streams for Apache Kafka operator is installed, it provides the resources to install instances of Kafka components. After installing a Kafka cluster, you can start producing and consuming messages. Note If you require more flexibility with your deployment, you can use the installation artifacts provided with Streams for Apache Kafka. For more information on using the installation artifacts, see Deploying and Managing Streams for Apache Kafka on OpenShift . 1.1. Prerequisites The following prerequisites are required for getting started with Streams for Apache Kafka. You have a Red Hat account. JDK 11 or later is installed. An OpenShift 4.12 to 4.15 cluster is available. The OpenShift oc command-line tool is installed and configured to connect to the running cluster. The steps to get started are based on using the OperatorHub in the OpenShift web console, but you'll also use the OpenShift oc CLI tool to perform certain operations. You'll need to connect to your OpenShift cluster using the oc tool. You can install the oc CLI tool from the web console by clicking the '?' help menu, then Command Line Tools . You can copy the required oc login details from the web console by clicking your profile name, then Copy login command . 1.2. Additional resources Strimzi Overview Deploying and Upgrading Streams for Apache Kafka on OpenShift

Commands:
Chapter 20. Authenticating third-party clients through RH-SSO To use the different remote services provided by Business Central or by KIE Server, your client, such as curl, wget, web browser, or a custom REST client, must authenticate through the RH-SSO server and have a valid token to perform the requests. To use the remote services, the authenticated user must have the following roles: rest-all for using Business Central remote services. kie-server for using the KIE Server remote services. Use the RH-SSO Admin Console to create these roles and assign them to the users that will consume the remote services. Your client can authenticate through RH-SSO using one of these options: Basic authentication, if it is supported by the client Token-based authentication 20.1. Basic authentication If you enabled basic authentication in the RH-SSO client adapter configuration for both Business Central and KIE Server, you can avoid the token grant and refresh calls and call the services as shown in the following examples: For web based remote repositories endpoint: For KIE Server: 20.2. Token-based authentication If you want a more secure option of authentication, you can consume the remote services from both Business Central and KIE Server by using a granted token provided by RH-SSO. Procedure In the RH-SSO Admin Console, click the Clients menu item and click Create to create a new client. The Add Client page opens. On the Add Client page, provide the required information to create a new client for your realm. For example: Client ID : kie-remote Client protocol : openid-connect Click Save to save your changes. Change the token settings in Realm Settings : In the RH-SSO Admin Console, click the Realm Settings menu item. Click the Tokens tab. Change the value for Access Token Lifespan to 15 minutes. This gives you enough time to get a token and invoke the service before it expires. Click Save to save your changes. After a public client for your remote clients is created, you can now obtain the token by making an HTTP request to the RH-SSO server's token endpoint using: The user in this command is a Business Central RH-SSO user. For more information, see Section 17.1, "Adding Red Hat Process Automation Manager users" . To view the token obtained from the RH-SSO server, use the following command: You can now use this token to authorize the remote calls. For example, if you want to check the internal Red Hat Process Automation Manager repositories, use the token as shown below:

Commands:
curl http://admin:password@localhost:8080/business-central/rest/repositories
curl http://admin:password@localhost:8080/kie-server/services/rest/server/
RESULT=`curl --data "grant_type=password&client_id=kie-remote&username=admin&password=password" http://localhost:8180/auth/realms/demo/protocol/openid-connect/token`
TOKEN=`echo USDRESULT | sed 's/.*access_token":"//g' | sed 's/".*//g'`
curl -H "Authorization: bearer USDTOKEN" http://localhost:8080/business-central/rest/repositories
4.278. sabayon 4.278.1. RHBA-2011:1273 - sabayon bug fix update Updated sabayon packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Sabayon is a tool to help system administrators and users change and maintain the default behavior of the GNOME desktop. These packages contain the graphical tools which a system administrator uses to manage Sabayon profiles. Bug Fixes BZ# 674012 Previously, when a user configured a custom panel launcher in the profile, Sabayon terminated unexpectedly while getting details of the profile. With this update, a priority level has been set up for sorting in the Details view so that Sabayon no longer crashes while getting the profile details. BZ# 654567 Previously, when a user created a file or folder on the desktop that contained an apostrophe ("'") in the name, Sabayon terminated unexpectedly when saving the profile. With this update, any apostrophe characters in the name are now escaped so that Sabayon no longer crashes and properly saves the profile. All sabayon users are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 20. Installation and Booting The installer displays the number of multipath devices, and number of multipath devices selected, incorrectly Multipath devices are configured properly, but the installer displays the number of devices and number of selected devices incorrectly. There is no known workaround at this point. (BZ#914637) The installer displays the amount of disk space within multipath devices incorrectly Multipath devices are configured properly, but the installer displays disk space and number of devices incorrectly. There is no known workaround at this point. (BZ#1014425) The device.map configuration file generated by Anaconda is sometimes incorrect Due to limitations in the kernel, the device.map configuration file that is used to map BIOS drives to operating system devices might be generated incorrectly in certain situations, particularly when installing from a USB key. As a consequence, booting sometimes fails after installation. To work around this problem, manually update the device.map file in the /boot/grub directory. After updating device.map so that it correctly maps devices on the system, Red Hat Enterprise Linux 6 will boot as expected. (BZ# 1253223 ) The ifup script incorrectly replaces manually-defined default routes If a default route is manually added to the routing table, the ifup script incorrectly replaces it, when setting up other interfaces, if the GATEWAY parameter is specified. To work around this bug, specify a non-zero metric for either the manually-added route, or when adding a route with ifup . (BZ#1090559) Upgrading Red Hat Enterprise Linux 6 on UEFI systems clears the boot loader password When upgrading Red Hat Enterprise Linux 6 on a system with UEFI firmware and a boot loader password set, the boot loader password is removed. As a consequence, modifying the boot record is possible without a password. To work around this problem, make a back up of the password settings from the /boot/efi/EFI/redhat/grub.conf configuration file before upgrading, and then restore the settings to the /boot/efi/EFI/redhat/grub.conf file in the new system. (BZ#1416653)

Commands:
Preface The guidelines in this document frequently refer to the following existing documentation: Upgrading from RHEL 6 to RHEL 7 If you are using SAP HANA, see the Red Hat Knowledgebase solution How do I upgrade from RHEL 6 to RHEL 7 with SAP HANA instead. Note that the upgrade path for SAP HANA is from RHEL 6.10 to RHEL 7.9. Upgrading from RHEL 7 to RHEL 8 This document also includes additional instructions specific to upgrading from RHEL 6 to RHEL 8.

Commands:
Chapter 5. Installing a three-node cluster on AWS In OpenShift Container Platform version 4.17, you can install a three-node cluster on Amazon Web Services (AWS). A three-node cluster consists of three control plane machines, which also act as compute machines. This type of cluster provides a smaller, more resource efficient cluster, for cluster administrators and developers to use for testing, development, and production. You can install a three-node cluster using either installer-provisioned or user-provisioned infrastructure. Note Deploying a three-node cluster using an AWS Marketplace image is not supported. 5.1. Configuring a three-node cluster You configure a three-node cluster by setting the number of worker nodes to 0 in the install-config.yaml file before deploying the cluster. Setting the number of worker nodes to 0 ensures that the control plane machines are schedulable. This allows application workloads to be scheduled to run from the control plane nodes. Note Because application workloads run from control plane nodes, additional subscriptions are required, as the control plane nodes are considered to be compute nodes. Prerequisites You have an existing install-config.yaml file. Procedure Set the number of compute replicas to 0 in your install-config.yaml file, as shown in the following compute stanza: Example install-config.yaml file for a three-node cluster apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0 # ... If you are deploying a cluster with user-provisioned infrastructure: After you create the Kubernetes manifest files, make sure that the spec.mastersSchedulable parameter is set to true in cluster-scheduler-02-config.yml file. You can locate this file in <installation_directory>/manifests . For more information, see "Creating the Kubernetes manifest and Ignition config files" in "Installing a cluster on user-provisioned infrastructure in AWS by using CloudFormation templates". Do not create additional worker nodes. Example cluster-scheduler-02-config.yml file for a three-node cluster apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {} 5.2. steps Installing a cluster on AWS with customizations Installing a cluster on user-provisioned infrastructure in AWS by using CloudFormation templates

Commands:
apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0
apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {}
Chapter 16. Change resources on virtual machines using director Operator To change the CPU, RAM, and disk resources of an OpenStackVMSet custom resource (CR), use the OpenStackControlPlane CRD. 16.1. Change the CPU or RAM of an OpenStackVMSet CR You can use the OpenStackControlPlane CRD to change the CPU or RAM of an OpenStackVMSet custom resource (CR). Procedure Change the number of Controller virtualMachineRole cores to 8: Change the Controller virtualMachineRole RAM size to 22GB: Validate the virtualMachineRole resource: From inside the virtual machine do a graceful shutdown. Shutdown each updated virtual machine one by one. Power on the virtual machine: Replace <VM> with the name of your virtual machine. 16.2. Add additional disks to an OpenStackVMSet CR You can use the OpenStackControlPlane CRD to add additional disks to a virtual machine by editing the additionalDisks property. Procedure Add or update the additionalDisks parameter in the OpenStackControlPlane object: Apply the patch: Validate the virtualMachineRole resource: From inside the virtual machine do a graceful shutdown. Shutdown each updated virtual machine one by one. Power on the virtual machine: Replace <VM> with the name of your virtual machine.

Commands:
oc patch -n openstack osctlplane overcloud --type='json' -p='[{"op": "add", "path": "/spec/virtualMachineRoles/controller/cores", "value": 8 }]'
oc patch -n openstack osctlplane overcloud --type='json' -p='[{"op": "add", "path": "/spec/virtualMachineRoles/controller/memory", "value": 22 }]'
oc get osvmset NAME CORES RAM DESIRED READY STATUS REASON controller 8 22 1 1 Provisioned All requested VirtualMachines have been provisioned
`virtctl start <VM>` to power on the virtual machine.
spec: virtualMachineRoles: Controller: additionalDisks: - baseImageVolumeName: openstack-base-img dedicatedIOThread: false diskSize: 10 name: "data-disk1" storageAccessMode: ReadWriteMany storageClass: host-nfs-storageclass storageVolumeMode: Filesystem
oc patch -n openstack osctlplane overcloud --patch-file controller_add_data_disk1.yaml
oc get osvmset controller -o json | jq .spec.additionalDisks [ { "baseImageVolumeName": "openstack-base-img", "dedicatedIOThread": false, "diskSize": 10, "name": "data-disk1", "storageAccessMode": "ReadWriteMany", "storageClass": "host-nfs-storageclass", "storageVolumeMode": "Filesystem" } ]
`virtctl start <VM>` to power on the virtual machine.
Chapter 6. Creating a kernel-based virtual machine and booting the installation ISO in the VM You can create a kernel-based virtual machine (KVM) and start the Red Hat Enterprise Linux installation. The following instructions are specific for installation on a VM. If you are installing RHEL on a physical system, you can skip this section. Procedure Create a virtual machine with the instance of Red Hat Enterprise Linux as a KVM guest operating system, by using the following virt-install command on the KVM host: Additional resources virt-install man page on your system Creating virtual machines by using the command-line interface

Commands:
virt-install --name=<guest_name> --disk size=<disksize_in_GB> --memory=<memory_size_in_MB> --cdrom <filepath_to_iso> --graphics vnc
Chapter 3. Compatibility Matrix for Red Hat Ceph Storage 5.2 The following tables list products and their versions compatible with Red Hat Ceph Storage 5.2. Host Operating System Version Notes Red Hat Enterprise Linux 9.1, 9.0, 8.6, 8.5, and EUS 8.4 Standard lifecycle 9.1 is included in the product (recommended). Red Hat Enterprise Linux EUS is optional. Important All nodes in the cluster and their clients must use the supported OS version(s) to ensure that the version of the ceph package is the same on all nodes. Using different versions of the ceph package is not supported. Important Red Hat no longer supports using Ubuntu as a host operating system to deploy Red Hat Ceph Storage. Product Version Notes Ansible Supported in a limited capacity. Supported for upgrade and conversion to Cephadm and for other minimal playbooks. Red Hat OpenShift 3.x RBD,Cinder and CephFS drivers are supported. Red Hat OpenShift Data Foundation See the Red Hat OpenShift Data Foundation Supportability and Interoperability Checker for detailed external mode version compatibility. Red Hat OpenStack Platform 16.1, 16.2, and 17.0 Red Hat OpenStack Platform 16.1z8 and 16.2z1 are supported only with external Red Hat Ceph Storage 5.2. Red Hat OpenStack Platform 17.0 supports Red Hat Ceph Storage 5.2 through both external and director deployed. Red Hat Satellite 6.x Only registering with the Content Delivery Network (CDN) is supported. Registering with Red Hat Network (RHN) is deprecated and not supported. Client Connector Version Notes S3A 2.8.x, 3.2.x, and trunk Red Hat Enterprise Linux iSCSI Initiator The latest versions of the iscsi-initiator-utils and device-mapper-multipath packages VMware vSphere versions 6.7 and 7 are supported Red Hat Ceph Storage as a backup target Version Notes CommVault Cloud Data Management v11 IBM Spectrum Protect Plus 10.1.5 IBM Spectrum Protect server 8.1.8 NetApp AltaVault 4.3.2 and 4.4 Rubrik Cloud Data Management (CDM) 3.2 onwards Trilio, TrilioVault 3.0 S3 target Veeam (object storage) Veeam Availability Suite 9.5 Update 4 Supported on Red Hat Ceph Storage object storage with the S3 protocol Veritas NetBackup for Symantec OpenStorage (OST) cloud backup 7.7 and 8.0 Independent Software vendors Version Notes IBM Spectrum Discover 2.0.3 WekaIO 3.12.2

Commands:
A. Revision History Revision History Revision 1-1 2015-02-25 Laura Bailey Rebuild with sort_order Revision 0-40.2.400 2013-10-31 Rudiger Landmann Rebuild with publican 4.0.0 Revision 0-40.2 Thu Dec 13 2012 Martin Prpic Added a note about removal of multilib Python packages. Revision 0-39 Fri May 20 2011 Ryan Lerch Copyedit in the Installation section Revision 1-0 Tue Mar 22 2011 Ryan Lerch Initial Version of the Red Hat Enterprise Linux 6.1 Release Notes

Commands:
5.11.4. Setting Up Polyinstantiated Directories The /tmp/ and /var/tmp/ directories are normally used for temporary storage by all programs, services, and users. Such setup, however, makes these directories vulnerable to race condition attacks, or an information leak based on file names. SELinux offers a solution in the form of polyinstantiated directories. This effectively means that both /tmp/ and /var/tmp/ are instantiated, making them appear private for each user. When instantiation of directories is enabled, each user's /tmp/ and /var/tmp/ directory is automatically mounted under /tmp-inst and /var/tmp/tmp-inst . Follow these steps to enable polyinstantiation of directories: Uncomment the last three lines in the /etc/security/namespace.conf file to enable instantiation of the /tmp/ , /var/tmp/ , and users' home directories: Ensure that in the /etc/pam.d/login file, the pam_namespace.so module is configured for session: Reboot your system.

Commands:
~]USD tail -n 3 /etc/security/namespace.conf /tmp /tmp-inst/ level root,adm /var/tmp /var/tmp/tmp-inst/ level root,adm USDHOME USDHOME/USDUSER.inst/ level
~]USD grep namespace /etc/pam.d/login session required pam_namespace.so
33.8. Managing Print Jobs When you send a print job to the printer daemon, such as printing a text file from Emacs or printing an image from The GIMP , the print job is added to the print spool queue. The print spool queue is a list of print jobs that have been sent to the printer and information about each print request, such as the status of the request, the the job number, and more. During the printing process, the Printer Status icon appears in the Notification Area on the panel. To check the status of a print job, double click the Printer Status, which displays a window similar to Figure 33.12, "GNOME Print Status" . Figure 33.12. GNOME Print Status To cancel a specific print job listed in the GNOME Print Status , select it from the list and select Edit => Cancel Documents from the pulldown menu. To view the list of print jobs in the print spool from a shell prompt, type the command lpq . The last few lines look similar to the following: Example 33.1. Example of lpq output If you want to cancel a print job, find the job number of the request with the command lpq and then use the command lprm job number . For example, lprm 902 would cancel the print job in Example 33.1, "Example of lpq output" . You must have proper permissions to cancel a print job. You can not cancel print jobs that were started by other users unless you are logged in as root on the machine to which the printer is attached. You can also print a file directly from a shell prompt. For example, the command lpr sample.txt prints the text file sample.txt . The print filter determines what type of file it is and converts it into a format the printer can understand.

Commands:
Rank Owner/ID Class Job Files Size Time active user@localhost+902 A 902 sample.txt 2050 01:20:46
Managing configurations using Puppet integration Red Hat Satellite 6.15 Configure Puppet integration in Satellite and use Puppet classes to configure your hosts Red Hat Satellite Documentation Team satellite-doc-list@redhat.com

Commands:
satellite-installer --enable-foreman-cli-puppet --enable-foreman-plugin-puppet --enable-puppet --foreman-proxy-puppet true --foreman-proxy-puppetca true --puppet-server true
satellite-installer --enable-puppet --foreman-proxy-puppet true --foreman-proxy-puppetca true --puppet-server true
<%= snippet 'puppet_setup' %>
dnf install puppet-agent
yum install puppet-agent
. /etc/profile.d/puppet-agent.sh
puppet config set server satellite.example.com --section agent puppet config set environment My_Puppet_Environment --section agent
puppet resource service puppet ensure=running enable=true
puppet ssl bootstrap
puppet ssl bootstrap
satellite-maintain plugin purge-puppet --remove-all-data
satellite-maintain plugin purge-puppet --remove-all-data
puppet module install puppetlabs-ntp -i /etc/puppetlabs/code/environments/production/modules
Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules Notice: Created target directory /etc/puppetlabs/code/environments/production/modules Notice: Downloading from https://forgeapi.puppet.com Notice: Installing -- do not interrupt /etc/puppetlabs/code/environments/production/modules |-| puppetlabs-ntp (v8.3.0) |-- puppetlabs-stdlib (v4.25.1) [/etc/puppetlabs/code/environments/production/modules]
puppet config print modulepath
/etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/environments/common:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules:/usr/share/puppet/modules
puppet module upgrade module name
Successfully updated environments and Puppet classes from the on-disk Puppet installation
0.de.pool.ntp.org, 1.de.pool.ntp.org, 2.de.pool.ntp.org, 3.de.pool.ntp.org
- 0.de.pool.ntp.org - 1.de.pool.ntp.org - 2.de.pool.ntp.org - 3.de.pool.ntp.org
--- parameters: // shortened YAML output classes: ntp: servers: '["0.de.pool.ntp.org","1.de.pool.ntp.org","2.de.pool.ntp.org","3.de.pool.ntp.org"]' environment: production
puppet agent -t
cat /etc/ntp.conf
ntp.conf: Managed by puppet. server 0.de.pool.ntp.org server 1.de.pool.ntp.org server 2.de.pool.ntp.org server 3.de.pool.ntp.org