mtpti5iD/redhat-docs_dataset huggingface dataset:
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 2025-03-12 09:30:30 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
4.52. dump 4.52.1. RHBA-2011:1095 - dump bug fix update Updated dump packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The dump package contains both "dump" and "restore" commands. The "dump" command examines files in a file system, determines which ones need to be backed up, and copies those files to a specified disk, tape, or other storage medium. The "restore" command performs the inverse function of "dump"; it can restore a full backup of a file system. Subsequent incremental backups can then be layered on top of the full backup. Single files and directory subtrees may also be restored from full or partial backups. Bug Fixes BZ# 702593 Prior to this update, the dump utility passed wrong arguments to the "clone(2)" system call. As a result, dump became unresponsive when executed on the S/390 or IBM System z architecture. This bug has been fixed in this update so that dump now passes correct arguments and no longer hangs. BZ# 691434 Under certain circumstances, the dump utility could have failed to detect holes in files correctly. When a user attempted to restore an erroneous backup using the "restore" command, an error message "Missing blocks at end of [path], assuming hole" could have been displayed. In such case, the backup could have not been restored properly. This bug has been fixed in this update so that dump now handles holes in files as expected. BZ# 658890 Prior to this update, the "dump -w" command did not recognize ext4 file systems as supported. With this update, the bug has been fixed so that "dump -w" now recognizes the ext4 file systems as supported. All users of dump should upgrade to these updated packages, which fix these bugs.

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 use Bring-Your-Own-Host (BYOH) Windows instances to repurpose Windows Server VMs and bring them to OpenShift Container Platform. BYOH Windows instances benefit users who are looking to mitigate major disruptions in the event that a Windows server goes offline. You can use BYOH Windows instances as nodes on OpenShift Container Platform 4.8 and later versions. You can disable Windows container workloads by performing the following: Uninstalling the Windows Machine Config Operator Deleting the Windows Machine Config Operator namespace

Commands:
15.4. Shared Storage Example: NFS for a Simple Migration Important This example uses NFS to share guest virtual machine images with other KVM host physical machines. Although not practical for large installations, it is presented to demonstrate migration techniques only. Do not use this example for migrating or running more than a few guest virtual machines. In addition, it is required that the synch parameter is enabled. This is required for proper export of the NFS storage. iSCSI storage is a better choice for large deployments. For configuration details, see Section 13.2.3.5, "iSCSI-based storage pools" . For detailed information on configuring NFS, opening IP tables, and configuring the firewall, see Red Hat Linux Storage Administration Guide . Make sure that NFS file locking is not used as it is not supported in KVM. Export your libvirt image directory Migration requires storage to reside on a system that is separate to the migration target systems. On this separate system, export the storage by adding the default image directory to the /etc/exports file: Change the hostname parameter as required for your environment. Start NFS Install the NFS packages if they are not yet installed: Make sure that the ports for NFS in iptables (2049, for example) are opened and add NFS to the /etc/hosts.allow file. Start the NFS service: Mount the shared storage on the source and the destination On the migration source and the destination systems, mount the /var/lib/libvirt/images directory: Warning Whichever directory is chosen for the source host physical machine must be exactly the same as that on the destination host physical machine. This applies to all types of shared storage. The directory must be the same or the migration with virt-manager will fail.

Commands:
/var/lib/libvirt/images *.example.com (rw,no_root_squash,sync)
yum install nfs-utils
systemctl start nfs-server
mount storage_host :/var/lib/libvirt/images /var/lib/libvirt/images
B.5. Add a Certificate to a Truststore Using Keytool Procedure B.3. Add a Certificate to a Truststore Using Keytool Run the keytool -import -alias ALIAS -file public.cert -storetype TYPE -keystore server.truststore command: If the specified truststore already exists, enter the existing password for that truststore, otherwise enter a new password: Enter yes when prompted to trust the certificate: Result The certificate in public.cert has been added to the new truststore named server.truststore .

Commands:
keytool -import -alias teiid -file public.cert -storetype JKS -keystore server.truststore
Enter keystore password: <password>
Owner: CN=<user's name>, OU=<dept name>, O=<company name>, L=<city>, ST=<state>, C=<country> Issuer: CN=<user's name>, OU=<dept name>, O=<company name>, L=<city>, ST=<state>, C=<country> Serial number: 416d8636 Valid from: Fri Jul 31 14:47:02 CDT 2009 until: Sat Jul 31 14:47:02 CDT 2010 Certificate fingerprints: MD5: 22:4C:A4:9D:2E:C8:CA:E8:81:5D:81:35:A1:84:78:2F SHA1: 05:FE:43:CC:EA:39:DC:1C:1E:40:26:45:B7:12:1C:B9:22:1E:64:63 Trust this certificate? [no]: yes
11.6. Preparing and Adding Red Hat Gluster Storage 11.6.1. Preparing Red Hat Gluster Storage For information on setting up and configuring Red Hat Gluster Storage, see the Red Hat Gluster Storage Installation Guide . For the Red Hat Gluster Storage versions that are supported with Red Hat Virtualization, see https://access.redhat.com/articles/2356261 . 11.6.2. Adding Red Hat Gluster Storage To use Red Hat Gluster Storage with Red Hat Virtualization, see Configuring Red Hat Virtualization with Red Hat Gluster Storage . For the Red Hat Gluster Storage versions that are supported with Red Hat Virtualization, see https://access.redhat.com/articles/2356261 .

Commands:
29.2.3. Separating Kernel and User-space Profiles By default, kernel mode and user mode information is gathered for each event. To configure OProfile to ignore events in kernel mode for a specific counter, execute the following command: Execute the following command to start profiling kernel mode for the counter again: To configure OProfile to ignore events in user mode for a specific counter, execute the following command: Execute the following command to start profiling user mode for the counter again: When the OProfile daemon writes the profile data to sample files, it can separate the kernel and library profile data into separate sample files. To configure how the daemon writes to sample files, execute the following command as root: choice can be one of the following: none - Do not separate the profiles (default). library - Generate per-application profiles for libraries. kernel - Generate per-application profiles for the kernel and kernel modules. all - Generate per-application profiles for libraries and per-application profiles for the kernel and kernel modules. If --separate=library is used, the sample file name includes the name of the executable as well as the name of the library. Note These configuration changes will take effect when the OProfile profiler is restarted.

Commands:
~]# opcontrol --event= event-name : sample-rate : unit-mask :0
~]# opcontrol --event= event-name : sample-rate : unit-mask :1
~]# opcontrol --event= event-name : sample-rate : unit-mask : kernel :0
~]# opcontrol --event= event-name : sample-rate : unit-mask : kernel :1
~]# opcontrol --separate= choice
4.8. VSS Transaction Flow In processing a backup, the requester and the writers coordinate to do several things: to provide a stable system image from which to back up data (the shadow copied volume), to group files together on the basis of their usage, and to store information on the saved data. This must all be done with minimal interruption of the writer's normal work flow. A requester (in our case the Backup Vendor) queries writers for their metadata, processes this data, notifies the writers prior to the beginning of the shadow copy and of the backup operations, and then notifies the writers again after the shadow copy and backup operations end. Here is how the QEMU VSS provider is registered in Windows OS after the Guest Tools installation:

Commands:
C:\Users\Administrator>vssadmin list providers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Provider name: 'QEMU Guest Agent VSS Provider' Provider type: Software Provider Id: {3629d4ed-ee09-4e0e-9a5c-6d8ba2872aef} Version: 0.12.1
4.2.5. Off-Line Backup Storage Off-line backup storage takes a step beyond hard drive storage in terms of capacity (higher) and speed (slower). Here, capacities are effectively limited only by your ability to procure and store the removable media. The actual technologies used in these devices varies widely. Here are the more popular types: Magnetic tape Optical disk Of course, having removable media means that access times become even longer, particularly when the desired data is on media not currently loaded in the storage device. This situation is alleviated somewhat by the use of robotic devices capable of automatically loading and unloading media, but the media storage capacities of such devices are still finite. Even in the best of cases, access times are measured in seconds, which is much longer than the relatively slow multi-millisecond access times typical for a high-performance hard drive. Now that we have briefly studied the various storage technologies in use today, let us explore basic virtual memory concepts.

Commands:
Chapter 4. Revoking two-factor authentication when your authenticator device is lost You can revoke the two-factor authentication protection on your Red Hat account when your authenticator device is lost and you have no recovery codes available, or when you have no other way to log in to your account with two-factor authentication enabled. Red Hat Customer Service can do this immediately with a phone call or with a seven-day email response. All requests to revoke two-factor authentication must be made by phone. You cannot revoke two-factor authentication with an email request or other online request. See Section 2.2, "Verifying your account information" for information about setting up your contact phone number. Important Account verification through a phone call from Red Hat Customer Service to your account phone number is the only method approved by the Red Hat security teams for quickly allowing two-factor authentication settings to be revoked. There are no exceptions to this process. Note Password resets are done through email, using the email address for your account. You cannot revoke two-factor authentication through email, and you cannot reset your password through a phone call. 4.1. Revoking two-factor authentication immediately To immediately revoke two-factor authentication on your account, you must be reachable by phone. Red Hat Customer Service places a call to the phone number of record for your account. This two-step process with outgoing call confirmation protects the security of your account. It is the only method approved by the Red Hat security team that allows two-factor authentication settings to be revoked by phone. If you can't accept a return call from Red Hat Customer Service , the two-factor authentication on your account can't be quickly revoked. After two-factor authentication is revoked, you can log in using your valid password. Depending on your organization policy, you might be required to immediately enable two-factor authentication after you log in. 4.2. Revoking two-factor authentication with a 7-day waiting period When you cannot accept a call to the phone number of record for your account, the Red Hat Customer Service team sends an email notification to the email address associated with your account. The email notifies the account holder that two-factor authentication will be revoked in 7 days. You can reply to the notification email if you decide you do not want two-factor authentication revoked.

Commands:
Chapter 37. MetadataTemplate schema reference Used in: BuildConfigTemplate , DeploymentTemplate , InternalServiceTemplate , PodDisruptionBudgetTemplate , PodTemplate , ResourceTemplate , StatefulSetTemplate Full list of MetadataTemplate schema properties Labels and Annotations are used to identify and organize resources, and are configured in the metadata property. For example: # ... template: pod: metadata: labels: label1: value1 label2: value2 annotations: annotation1: value1 annotation2: value2 # ... The labels and annotations fields can contain any labels or annotations that do not contain the reserved string strimzi.io . Labels and annotations containing strimzi.io are used internally by AMQ Streams and cannot be configured. 37.1. MetadataTemplate schema properties Property Description labels Labels added to the OpenShift resource. map annotations Annotations added to the OpenShift resource. map

Commands:
template: pod: metadata: labels: label1: value1 label2: value2 annotations: annotation1: value1 annotation2: value2
8.127. libvpd 8.127.1. RHEA-2014:1429 - libvpd enhancement update Updated libvpd packages that add various enhancements are now available for Red Hat Enterprise Linux 6. The libvpd packages contain the classes that are used to access Vital Product Data (VPD) created by vpdupdate in the lsvpd package. Note The libvpd packages have been upgraded to upstream version 2.2.3, which provides a number of enhancements over the version. Specifically, the updated libvpd packages prevent segmentation faults from occurring when fetching the corrupted Vital Product Data (VPD) database. In addition, support for vpdupdate command automation has been added for cases of changes happening to device configuration on run time. During hot plugs, the changes made to the device configuration are now caught by an udev rule and are handled by libvpd correctly. (BZ# 739122 ) Users of libvpd are advised to upgrade to these updated packages, which add these enhancements.

Commands:
12.4. Disabling and Re-enabling Host Entries Active hosts can be accessed by other services, hosts, and users within the domain. There can be situations when it is necessary to remove a host from activity. However, deleting a host removes the entry and all the associated configuration, and it removes it permanently. 12.4.1. Disabling Host Entries Disabling a host prevents domain users from access it without permanently removing it from the domain. This can be done by using the host-disable command. For example: Important Disabling a host entry not only disables that host. It disables every configured service on that host as well. 12.4.2. Re-enabling Hosts This section describes how to re-enable a disabled IdM host. Disabling a host removes its active keytabs, which removed the host from the IdM domain without otherwise touching its configuration entry. To re-enable a host, use the ipa-getkeytab command, adding: the -s option to specify which IdM server to request the keytab from the -p option to specify the principal name the -k option to specify the file to which to save the keytab. For example, to request a new host keytab from server.example.com for client.example.com , and store the keytab in the /etc/krb5.keytab file: Note You can also use the administrator's credentials, specifying -D "uid=admin,cn=users,cn=accounts,dc=example,dc=com" . It is important that the credentials correspond to a user allowed to create the keytab for the host. If you run the ipa-getkeytab command on an active IdM client or server, then you can run it without any LDAP credentials ( -D and -w ) if the user has a TGT obtained using, for example, kinit admin . To run the command directly on the disabled host, supply LDAP credentials to authenticate to the IdM server.

Commands:
[jsmith@ipaserver ~]USD kinit admin [jsmith@ipaserver ~]USD ipa host-disable server.example.com
ipa-getkeytab -s server.example.com -p host/client.example.com -k /etc/krb5.keytab -D "cn=directory manager" -w password
14.2.2. Adding Unallocated Volumes to a Volume Group Once initialized, a volume will be listed in the 'Unallocated Volumes' list. The figure below illustrates an unallocated partition (Partition 3). The respective buttons at the bottom of the window allow you to: create a new volume group, add the unallocated volume to an existing volume group, remove the volume from LVM. To add the volume to an existing volume group, click on the Add to Existing Volume Group button. Figure 14.7. Unallocated Volumes Clicking on the Add to Existing Volume Group button will display a pop-up window listing the existing volume groups to which you can add the physical volume you are about to initialize. A volume group may span across one or more hard disks. Example 14.3. Add a physical volume to volume group In this example only one volume group exists as illustrated below. Once added to an existing volume group the new logical volume is automatically added to the unused space of the selected volume group. You can use the unused space to: create a new logical volume (click on the Create New Logical Volume(s) button), select one of the existing logical volumes and increase the extents (see Section 14.2.6, "Extending a Volume Group" ), select an existing logical volume and remove it from the volume group by clicking on the Remove Selected Logical Volume(s) button. You cannot select unused space to perform this operation. The figure below illustrates the logical view of 'VolGroup00' after adding the new volume group. Figure 14.8. Logical view of volume group In the figure below, the uninitialized entities (partitions 3, 5, 6 and 7) were added to 'VolGroup00'. Figure 14.9. Logical view of volume group

Commands:
8. Security 8.1. Technology Previews OpenSCAP OpenSCAP is a set of open source libraries that support the Security Content Automation Protocol (SCAP) standards from the National Institute of Standards and Technology (NIST). OpenSCAP supports the SCAP components: Common Vulnerabilities and Exposures (CVE) Common Platform Enumeration (CPE) Common Configuration Enumeration (CCE) Common Vulnerability Scoring System (CVSS) Open Vulnerability and Assessment Language (OVAL) Extensible Configuration Checklist Description Format (XCCDF) Additionally, the openSCAP package includes an application to generate SCAP reports about system configuration. This package is considered a Technology Preview in Red Hat Enterprise Linux 6. TPM TPM hardware can create, store and use RSA keys securely (without ever being exposed in memory), verify a platform's software state using cryptographic hashes and more. The user space libraries, trousers and tpm-tools are considered a Technology Preview in this Red Hat Enterprise Linux 6.

Commands:
probe::ioscheduler_trace.elv_completed_request Name probe::ioscheduler_trace.elv_completed_request - Fires when a request is Synopsis ioscheduler_trace.elv_completed_request Values elevator_name The type of I/O elevator currently enabled. rq Address of request. name Name of the probe point rq_flags Request flags. disk_minor Disk minor number of request. disk_major Disk major no of request. Description completed.

Commands:
B.58. nss_db B.58.1. RHBA-2011:0941 - nss_db bug fix update An updated nss_db package that fixes a bug is now available for Red Hat Enterprise Linux 6 Extended Update Support. The nss_db package contains a set of C library extensions which allow Berkeley Databases to be used as a primary source of aliases, groups, hosts, networks, protocols, users, services, or shadow passwords instead of, or in addition to, using flat files or NIS (Network Information Service). Bug Fix BZ# 718202 When a module does not provide its own method for retrieving a user's list of supplemental group memberships, the libc library's default method is used instead to get that information by examining all of the groups known to the module. Consequently, applications which attempted to retrieve the information from multiple threads simultaneously, interfered with each other and each received an incomplete result set. This update provides a module-specific method which prevents this interference in the nss_db module. Users of nss_db are advised to upgrade to this updated package, which fixes this bug.

Commands: