mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 8. Configure Public Key based SSH Authentication without a password Configure public key based SSH authentication without a password for the root user on the first hyperconverged host to all hosts, including itself . Do this for all storage and management interfaces, and for both IP addresses and FQDNs. 8.1. Generating SSH key pairs without a password Generating a public/private key pair lets you use key-based SSH authentication. Generating a key pair that does not use a password makes it simpler to use Ansible to automate deployment and configuration processes. Procedure Log in to the first hyperconverged host as the root user. Generate an SSH key that does not use a password. Start the key generation process. Enter a location for the key. The default location, shown in parentheses, is used if no other input is provided. Specify and confirm an empty passphrase by pressing Enter twice. The private key is saved in <location>/<keyname> . The public key is saved in <location>/<keyname>.pub . Warning Your identification in this output is your private key. Never share your private key. Possession of your private key allows someone else to impersonate you on any system that has your public key. 8.2. Copying SSH keys To access a host using your private key, that host needs a copy of your public key. Prerequisites Generate a public/private key pair with no password. Procedure Log in to the first host as the root user. Copy your public key to each host that you want to access, including the host on which you execute the command, using both the front-end and the back-end FQDNs. Enter the password for <user>@<hostname> when prompted. Warning Make sure that you use the file that ends in .pub . Never share your private key. Possession of your private key allows someone else to impersonate you on any system that has your public key. For example, if you are logged in as the root user on server1.example.com , you would run the following commands for a three node deployment:

Commands:
ssh-keygen -t rsa Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa): <location>/<keyname>
Enter passphrase (empty for no passphrase): Enter same passphrase again:
Your identification has been saved in <location>/<keyname>. Your public key has been saved in <location>/<keyname>.pub. The key fingerprint is SHA256:8BhZageKrLXM99z5f/AM9aPo/KAUd8ZZFPcPFWqK6+M root@server1.example.com The key's randomart image is: +---[ECDSA 256]---+ | . . +=| | . . . = o.o| | + . * . o...| | = . . * . + +..| |. + . . So o * ..| | . o . .+ = ..| | o oo ..=. .| | ooo...+ | | .E++oo | +----[SHA256]-----+
ssh-copy-id -i <location>/<keyname>.pub <user>@<hostname>
ssh-copy-id -i <location>/<keyname>.pub root@server1front.example.com ssh-copy-id -i <location>/<keyname>.pub root@server2front.example.com ssh-copy-id -i <location>/<keyname>.pub root@server3front.example.com ssh-copy-id -i <location>/<keyname>.pub root@server1back.example.com ssh-copy-id -i <location>/<keyname>.pub root@server2back.example.com ssh-copy-id -i <location>/<keyname>.pub root@server3back.example.com
Preface Red Hat Decision Manager is a subset of Red Hat Process Automation Manager. Starting with this release, the distribution files for Red Hat Decision Manager are replaced with Red Hat Process Automation Manager files. There are no Decision Manager artifacts. The Red Hat Decision Manager subscription, support entitlements, and fees remain the same. Red Hat Decision Manager subscribers will continue to receive full support for the decision management and optimization capabilities of Red Hat Decision Manager. The business process management (BPM) capabilities of Red Hat Process Automation Manager are exclusive to Red Hat Process Automation Manager subscribers. They are available for use by Red Hat Decision Manager subscribers but with development support services only. Red Hat Decision Manager subscribers can upgrade to a full Red Hat Process Automation Manager subscription at any time to receive full support for BPM features. As a developer or system administrator, you can install Red Hat Decision Manager components on Red Hat JBoss EAP, in an Red Hat JBoss EAP clustered environment, on JBoss Web Server, and in other supported environments.

Commands:
2.12. Logical Volume Extension The Red Hat Virtualization Manager uses thin provisioning to overcommit the storage available in a storage pool, and allocates more storage than is physically available. Virtual machines write data as they operate. A virtual machine with a thinly-provisioned disk image will eventually write more data than the logical volume backing its disk image can hold. When this happens, logical volume extension is used to provide additional storage and facilitate the continued operations for the virtual machine. Red Hat Virtualization provides a thin provisioning mechanism over LVM. When using QCOW2 formatted storage, Red Hat Virtualization relies on the host system process qemu-kvm to map storage blocks on disk to logical blocks in a sequential manner. This allows, for example, the definition of a logical 100 GB disk backed by a 1 GB logical volume. When qemu-kvm crosses a usage threshold set by VDSM, the local VDSM instance makes a request to the SPM for the logical volume to be extended by another one gigabyte. VDSM on the host running a virtual machine in need of volume extension notifies the SPM VDSM that more space is required. The SPM extends the logical volume and the SPM VDSM instance causes the host VDSM to refresh volume group information and recognize that the extend operation is complete. The host can continue operations. Logical Volume extension does not require that a host know which other host is the SPM; it could even be the SPM itself. The storage extension communication is done via a storage mailbox. The storage mailbox is a dedicated logical volume on the data storage domain. A host that needs the SPM to extend a logical volume writes a message in an area designated to that particular host in the storage mailbox. The SPM periodically reads the incoming mail, performs requested logical volume extensions, and writes a reply in the outgoing mail. After sending the request, a host monitors its incoming mail for responses every two seconds. When the host receives a successful reply to its logical volume extension request, it refreshes the logical volume map in device mapper to recognize the newly allocated storage. When the physical storage available to a storage pool is nearly exhausted, multiple images can run out of usable storage with no means to replenish their resources. A storage pool that exhausts its storage causes QEMU to return an enospc error , which indicates that the device no longer has any storage available. At this point, running virtual machines are automatically paused and manual intervention is required to add a new LUN to the volume group. When a new LUN is added to the volume group, the Storage Pool Manager automatically distributes the additional storage to logical volumes that need it. The automatic allocation of additional resources allows the relevant virtual machines to automatically continue operations uninterrupted or resume operations if stopped.

Commands:
Chapter 27. Kickstart Installations 27.1. What are Kickstart Installations? Kickstart installations offer a means to automate the installation process, either partially or fully. Kickstart files contain answers to all questions normally asked by the installation program, such as what time zone you want the system to use, how the drives should be partitioned, or which packages should be installed. Providing a prepared Kickstart file when the installation begins therefore allows you to perform the installation automatically, without need for any intervention from the user. This is especially useful when deploying Red Hat Enterprise Linux on a large number of systems at once. Kickstart files can be kept on a single server system and read by individual computers during the installation. This installation method can support the use of a single Kickstart file to install Red Hat Enterprise Linux on multiple machines, making it ideal for network and system administrators. All Kickstart scripts and the log files of their execution are stored in the /tmp directory to assist with debugging installation failures. Note In versions of Red Hat Enterprise Linux, Kickstart allowed for upgrading the system as well. In Red Hat Enterprise Linux 7, this functionality has been removed and system upgrades are instead handled by specialized tools. See Chapter 29, Upgrading Your Current System for details.

Commands:
8.170. quota 8.170.1. RHBA-2013:1548 - quota bug fix and enhancement update Updated quota packages that fix one bug and add two enhancements are now available for Red Hat Enterprise Linux 6. The quota packages contain a suite of system administration tools for monitoring and limiting user and group disk usage on file systems. Bug Fix BZ# 717948 When SELinux denied access to the quotacheck utility, the "quotacheck -c" command did not report any errors and failed with the exit code 0. With this update, quotacheck internals have been changed to propagate any error with an appropriate non-zero exit code, and to print accurate warnings if the old quota file could not be used. As a result, quotacheck now reports errors correctly while initializing quotas on a file system. Enhancements BZ# 890051 The edquota and setquota utilities now support input values entered with the use of multiplicative unit abbreviations (K, M, G, T). BZ# 846120 With this update, the quotacheck utility no longer checks quota files on the GFS2 and XFS file systems. Since these file systems do not have any quota files, the check was redundant. Users of quota are advised to upgrade to these updated packages, which fix this bug and add these enhancements.

Commands:
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-07-03 09:00:33 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Appendix C. Virtualization Restrictions This appendix covers additional support and product restrictions of the virtualization packages in Red Hat Enterprise Linux 7. C.1. System Restrictions Host Systems Red Hat Enterprise Linux with KVM is supported only on the following host architectures: AMD64 and Intel 64 IBM Z IBM POWER8 IBM POWER9 This document primarily describes AMD64 and Intel 64 features and functionalities, but the other supported architectures work very similarly. For details, see Appendix B, Using KVM Virtualization on Multiple Architectures . Guest Systems On Red Hat Enterprise Linux 7, Microsoft Windows guest virtual machines are only supported under specific subscription programs such as Advanced Mission Critical (AMC). If you are unsure whether your subscription model includes support for Windows guests, contact customer support. For more information about Windows guest virtual machines on Red Hat Enterprise Linux 7, see Windows Guest Virtual Machines on Red Hat Enterprise Linux 7 Knowledgebase article .

Commands:
Chapter 75. ListenerStatus schema reference Used in: KafkaStatus Property Property type Description type string The type property has been deprecated. The type property is not used anymore. Use the name property with the same value. The name of the listener. name string The name of the listener. addresses ListenerAddress array A list of the addresses for this listener. bootstrapServers string A comma-separated list of host:port pairs for connecting to the Kafka cluster using this listener. certificates string array A list of TLS certificates which can be used to verify the identity of the server when connecting to the given listener. Set only for tls and external listeners.

Commands:
10.5.65. VirtualHost <VirtualHost> and </VirtualHost> tags create a container outlining the characteristics of a virtual host. The VirtualHost container accepts most configuration directives. A commented VirtualHost container is provided in httpd.conf , which illustrates the minimum set of configuration directives necessary for each virtual host. Refer to Section 10.8, "Virtual Hosts" for more information about virtual hosts. Note The default SSL virtual host container now resides in the file /etc/httpd/conf.d/ssl.conf .

Commands:
Chapter 19. Time Parameters Parameter Description ChronyAclRules Access Control List of NTP clients. By default no clients are permitted. The default value is ['deny all'] . ChronyGlobalPoolOptions Default pool options for the configured NTP pools in chrony.conf. If this is specified, NtpIburstEnable, MaxPoll, and MinPoll are ignored. ChronyGlobalServerOptions Default server options for the configured NTP servers in chrony.conf. If this is specified, NtpIburstEnable, MaxPoll, and MinPoll are ignored. EnablePackageInstall Set to true to enable package installation at deploy time. The default value is false . MaxPoll Specify maximum poll interval of upstream servers for NTP messages, in seconds to the power of two. Allowed values are 4 to 17. The default value is 10 . MinPoll Specify minimum poll interval of upstream servers for NTP messages, in seconds to the power of two. The minimum poll interval defaults to 6 (64 s). Allowed values are 4 to 17. The default value is 6 . NtpIburstEnable Specifies whether to enable the iburst option for every NTP peer. If iburst is enabled, when the NTP server is unreachable NTP will send a burst of eight packages instead of one. This is designed to speed up the initial syncrhonization. The default value is True . NtpPool NTP pool list. Defaults to [], so only NtpServer is used by default. NtpServer NTP servers list. The default value is ['0.pool.ntp.org', '1.pool.ntp.org', '2.pool.ntp.org', '3.pool.ntp.org'] . TimeZone The timezone to be set on the overcloud. The default value is UTC .

Commands:
Chapter 23. KafkaAuthorizationKeycloak schema reference Used in: KafkaClusterSpec The type property is a discriminator that distinguishes use of the KafkaAuthorizationKeycloak type from KafkaAuthorizationSimple , KafkaAuthorizationOpa , KafkaAuthorizationCustom . It must have the value keycloak for the type KafkaAuthorizationKeycloak . Property Property type Description type string Must be keycloak . clientId string OAuth Client ID which the Kafka client can use to authenticate against the OAuth server and use the token endpoint URI. tokenEndpointUri string Authorization server token endpoint URI. tlsTrustedCertificates CertSecretSource array Trusted certificates for TLS connection to the OAuth server. disableTlsHostnameVerification boolean Enable or disable TLS hostname verification. Default value is false . delegateToKafkaAcls boolean Whether authorization decision should be delegated to the 'Simple' authorizer if DENIED by Red Hat Single Sign-On Authorization Services policies. Default value is false . grantsRefreshPeriodSeconds integer The time between two consecutive grants refresh runs in seconds. The default value is 60. grantsRefreshPoolSize integer The number of threads to use to refresh grants for active sessions. The more threads, the more parallelism, so the sooner the job completes. However, using more threads places a heavier load on the authorization server. The default value is 5. grantsGcPeriodSeconds integer The time, in seconds, between consecutive runs of a job that cleans stale grants from the cache. The default value is 300. grantsAlwaysLatest boolean Controls whether the latest grants are fetched for a new session. When enabled, grants are retrieved from Red Hat Single Sign-On and cached for the user. The default value is false . superUsers string array List of super users. Should contain list of user principals which should get unlimited access rights. connectTimeoutSeconds integer The connect timeout in seconds when connecting to authorization server. If not set, the effective connect timeout is 60 seconds. readTimeoutSeconds integer The read timeout in seconds when connecting to authorization server. If not set, the effective read timeout is 60 seconds. httpRetries integer The maximum number of retries to attempt if an initial HTTP request fails. If not set, the default is to not attempt any retries. enableMetrics boolean Enable or disable OAuth metrics. The default value is false . includeAcceptHeader boolean Whether the Accept header should be set in requests to the authorization servers. The default value is true . grantsMaxIdleTimeSeconds integer The time, in seconds, after which an idle grant can be evicted from the cache. The default value is 300.

Commands:
Chapter 2. Known issues NodeJS is no longer included in the .NET 8.0 SDK image. For information on how to port an application that depends on Node.js from an earlier .NET version to the .NET 8.0 image, see the Porting web applications with NodeJS front-ends to build with .NET 8.0 UBI images Knowledgebase solution. The random user used by OpenShift Container Platform is no longer added to the /etc/passwd file on OpenShift Container Platform 3.11. As a result, the .NET Environment.UserName property returns an empty string. The DOTNET_CORE_VERSION and DOTNET_FRAMEWORK environment variables were removed from the image. Instead, The image now includes exact versions of the .NET framework, the ASP.NET Core frameworks, and the SDK version in the DOTNET_VERSION , ASPNET_VERSION , and DOTNET_SDK_VERSION environment variables, respectively.. The DOTNET_SSL_DIRS environment variable used to load certificates from additional directories is no longer handled by the image entrypoint. The default s2i (source-to-image) assemble and run scripts still process the environment variable. To trust certificates in all cases, use SSL_CERT_DIR instead. In .NET 8.0, you can no longer specify the command and its arguments to run in a container as a single string. You need to pass the arguments as separate strings. The new syntax also works for the earlier .NET versions. For example, instead of podman run registry.access.redhat.com/ubi8/dotnet-70 "echo hello" , use podman run registry.access.redhat.com/ubi8/dotnet-80 echo hello . The dnf command is not available. To reduce image size, .NET 8.0 container images use the ubi-minimal base image instead of the ubi base image. The ubi-minimal image uses the microdnf command as its package manager instead of the dnf command. If your Dockerfiles/Containerfiles use the dnf command, you must change them to use the microdnf command instead. For more information about the microdnf command, please see the microdnf man page. See Known Issues in the .NET 8.0 Release Notes for .NET 8.0 RPM packages for a list of known issues and workarounds for RPMs.

Commands:
Chapter 2. Installing virt-v2v virt-v2v is run from a Red Hat Enterprise Linux 64-bit host system. virt-v2v must be installed on the host. Procedure 2.1. Installing virt-v2v Subscribe to the virt-v2v channel on the Red Hat Customer Portal virt-v2v is available on the Red Hat Customer Portal in the Red Hat Enterprise Linux Server (v.6 for 64-bit x86_64) or Red Hat Enterprise Linux Workstation (v.6 for x86_64) channel. Ensure the system is subscribed to the appropriate channel before installing virt-v2v . Note Red Hat Network Classic (RHN) has now been deprecated. Red Hat Subscription Manager should now be used for registration tasks. For more information, see https://access.redhat.com/rhn-to-rhsm . Install the prerequisites If you are converting Windows virtual machines, you must install the libguestfs-winsupport and virtio-win packages. These packages provide support for NTFS and Windows paravirtualized block and network drivers. If you attempt to convert a virtual machine using NTFS without the libguestfs-winsupport package installed, the conversion will fail. If you attempt to convert a virtual machine running Windows without the virtio-win package installed, the conversion will fail giving an error message concerning missing files. The libguestfs-winsupport is available for Red Hat Enterprise Linux Server 6 in the Red Hat Enterprise Linux Server V2V Tools for Windows (v. 6) channel, while the virtio-win package is available in the Red Hat Enterprise Linux Server Supplementary (v. 6) channel. To install these packages, ensure that your system has the required permissions to subscribe to both channels and run the following command as root: Install virt-v2v package As root, run the command: virt-v2v is now installed and ready to use on on your system.

Commands:
subscription-manager repos --enable rhel-6-server-v2vwin-1-rpms --enable rhel-6-server-supplementary-rpms
install virt-v2v
4.297. slapi-nis 4.297.1. RHBA-2011:1700 - slapi-nis bug fix update An updated slapi-nis package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The slapi-nis package provides the NIS server plugin and the schema compatibility plugin for the 389 directory server. Bug Fixes BZ# 694623 Prior to this update, processing an entry referred to large numbers of other entries took an excessive amount of time when the plugin was triggered and caused multiple levels of recursion loading of the ns-slapd process. This update improves the performance of slapi-nis when processing entries that refer to large numbers of other entries. BZ# 730403 Prior to this update, slapi-nis used NSPR RW locks which are not re-entrant. As a consequence, problems could arise and lead to deadlocks. With this update, POSIX-based read-write locking that synchronizes access between threads is used to avoid potential deadlocks. All users of slapi-nis are advised to upgrade to this updated package, which fixes these bugs.

Commands: