mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 6. Install additional software You need to perform some additional configuration for access to software and updates. Ensure you have access to software updates: Configure software repository access using the web console . If your hyperconverged hosts use disk encryption, Install disk encryption software . 6.1. Configuring software access 6.1.1. Configuring software repository access using the Web Console Prerequisites This process is for hyperconverged hosts based on Red Hat Virtualization 4. Procedure On each hyperconverged host: Log in to the Web Console. Use the management FQDN and port 9090, for example, https://server1.example.com:9090/ . Click Subscriptions . Click Register System . Enter your Customer Portal user name and password. Click Done . The Red Hat Virtualization Host subscription is automatically attached to the system. Enable the Red Hat Virtualization 4 repository to allow later updates to the Red Hat Virtualization Host: (Optional) If you use disk encryption, execute the following on each Network-Bound Disk Encryption (NBDE) key server: Log in to the NBDE key server. Register the NBDE key server with Red Hat. Attach the subscription pool: Enable the repositories required for disk encryption software: For NBDE key servers based on Red Hat Enterprise Linux 8: For NBDE key servers based on Red Hat Enterprise Linux 7: 6.2. Installing software 6.2.1. Installing disk encryption software The Network-Bound Disk Encryption key server requires an additional package to support disk encryption. Prerequisites Configuring software repository access using the web console . Procedure On each Network-Bound Disk Encryption (NBDE) key server, install the server-side packages.

Commands:
subscription-manager repos --enable=rhvh-4-for-rhel-8-x86_64-rpms
subscription-manager register --username= username --password= password
subscription-manager attach --pool= pool_id
subscription-manager repos --enable="rhel-8-for-x86_64-baseos-rpms" --enable="rhel-8-for-x86_64-appstream-rpms"
subscription-manager repos --enable="rhel-7-server-rpms"
yum install tang -y
Chapter 147. KafkaNodePoolStatus schema reference Used in: KafkaNodePool Property Description conditions List of status conditions. Condition array observedGeneration The generation of the CRD that was last reconciled by the operator. integer nodeIds Node IDs used by Kafka nodes in this pool. integer array clusterId Kafka cluster ID. string replicas The current number of pods being used to provide this resource. integer labelSelector Label selector for pods providing this resource. string

Commands:
Chapter 1. Introduction This document has been created to help Red Hat OpenStack Platform partners in their efforts to integrate solutions with Red Hat OpenStack Platform director as the tool used to install and manage the deployment lifecycle of an OpenStack Platform environment. Integration with the director enables seamless adoption of your technology. You can find broad benefits in an optimization of resources, reduction in deployment times and reduction in lifecycle management costs. Looking forward, OpenStack Platform director integration is a strong move toward providing rich integration with existing enterprise management systems and processes. Within the Red Hat product portfolio, tools such as CloudForms are expected to have visibility into director's integrations and provide broader exposure for management of service deployment. 1.1. Partner Integration Requirements You must meet several prerequisites before meaningful integration work can be completed with the director. These requirements are not limited to technical integration and also include various levels of partner solution documentation. The goal is to create a shared understanding of the entire integration as a basis for Red Hat engineering, partner managers, and support resources to facilitate work. The first requirement is related to Red Hat OpenStack Platform solution certification. To be included with OpenStack Platform director, the partner solution must first be certified with Red Hat OpenStack Platform. OpenStack Plug-in Certification Guides Red Hat OpenStack Certification Policy Guide Red Hat OpenStack Certification Workflow Guide OpenStack Application Certification Guides Red Hat OpenStack Application Policy Guide Red Hat OpenStack Application Workflow Guide OpenStack Bare Metal Certification Guides Red Hat OpenStack Platform Hardware Bare Metal Certification Policy Guide Red Hat OpenStack Platform Hardware Bare Metal Certification Workflow Guide

Commands:
7.100. lasso 7.100.1. RHBA-2015:1253 - lasso bug fix update Updated lasso packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The lasso packages provide the Lasso library that implements the Liberty Alliance Single Sign-On standards, including the SAML and SAML2 specifications. It allows handling of the whole life-cycle of SAML-based federations and provides bindings for multiple languages. Bug Fix BZ# 1160636 , BZ# 1167796 Users of the lasso packages could previously experience several problems related to Red Hat Enterprise Linux interoperability with Microsoft Active Directory Federation Services (ADFS). Authentication against ADFS failed when using the mod_auth_mellon module. In addition, in Apache sessions, the limit for the number of elements was insufficient and multi-value variables were not supported. Also, the MellonCond parameter did not work when used together with the MellonSetEnv(NoPrefix) parameter. This update fixes the above described problems with ADFS interoperability. Users of lasso are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 7. gnome-session The gnome-session program has also been updated in Red Hat Enterprise Linux 7. It starts the GNOME Desktop as it used to; nonetheless, some of its components have changed. gnome-session-properties The gnome-session-properties application is still part of the gnome-session package. However, its functionality has been limited to managing startup programs for individual users, and saving currently running applications when logging out. The latter functionality has been kept from Red Hat Enterprise Linux 6. named session The Save now button is able to save a session in a specific time and to name it. The saved sessions are restored on login. When you click Automatically remember running applications when logging out in gnome-session-properties , the list of saved applications is shown on login as well. With this update, it is also possible to create multiple layouts and rename them, or to be able to select multiple user sessions for one user account. Getting More Information For detailed information on session management, see Chapter 14, Session Management . For information on how to manage startup (autostart) applications for all users, see Section 14.3.5, "Adding an Autostart Application for All Users" .

Commands:
probe::ipmib.InDiscards Name probe::ipmib.InDiscards - Count discarded inbound packets Synopsis ipmib.InDiscards Values op value to be added to the counter (default value of 1) skb pointer to the struct sk_buff being acted on Description The packet pointed to by skb is filtered by the function ipmib_filter_key . If the packet passes the filter is is counted in the global InDiscards (equivalent to SNMP's MIB STATS_MIB_INDISCARDS)

Commands:
Chapter 38. Mail Transport Agent (MTA) Configuration A Mail Transport Agent (MTA) is essential for sending email. A Mail User Agent (MUA) such as Evolution , Mozilla Mail , Thunderbird , and Mutt , is used to read and compose email. When a user sends an email from an MUA, the message is handed off to the MTA, which sends the message through a series of MTAs until it reaches its destination. Even if a user does not plan to send email from the system, some automated tasks or system programs might use the /bin/mail command to send email containing log messages to the root user of the local system. Red Hat Enterprise Linux 4 provides three MTAs: Sendmail, Postfix, and Exim. If all three are installed, sendmail is the default MTA. The Mail Transport Agent Switcher allows for the selection of either sendmail , postfix , or exim as the default MTA for the system. The system-switch-mail RPM package must be installed to use the text-based version of the Mail Transport Agent Switcher program. If you want to use the graphical version, the system-switch-mail-gnome package must also be installed. To start the Mail Transport Agent Switcher , select Applications (the main menu on the panel) => Preferences => More Preferences => Mail Transport Agent Switcher , or type the command system-switch-mail at a shell prompt (for example, in an XTerm or GNOME terminal). The program automatically detects if the X Window System is running. If it is running, the program starts in graphical mode as shown in Figure 38.1, " Mail Transport Agent Switcher " . If X is not detected, it starts in text-mode. To force Mail Transport Agent Switcher to run in text-mode, use the command system-switch-mail-nox . Figure 38.1. Mail Transport Agent Switcher If you select OK to change the MTA, the selected mail daemon is enabled to start at boot time, and the unselected mail daemons are disabled so that they do not start at boot time. The selected mail daemon is started, and any other mail daemon is stopped; thus making the changes take place immediately. For more information about email protocols and MTAs, refer to the Reference Guide .

Commands:
3.3. Logical Volume Backup Metadata backups and archives are automatically created whenever there is a configuration change for a volume group or logical volume, unless this feature is disabled in the lvm.conf file. By default, the metadata backup is stored in the /etc/lvm/backup file and the metadata archives are stored in the /etc/lvm/archive file. How long the metadata archives stored in the /etc/lvm/archive file are kept and how many archive files are kept is determined by parameters you can set in the lvm.conf file. A daily system backup should include the contents of the /etc/lvm directory in the backup. Note that a metadata backup does not back up the user and system data contained in the logical volumes. You can manually back up the metadata to the /etc/lvm/backup file with the vgcfgbackup command. You can restore metadata with the vgcfgrestore command. The vgcfgbackup and vgcfgrestore commands are described in Section 4.3.13, "Backing Up Volume Group Metadata" .

Commands:
Chapter 2. Accessing monitoring for user-defined projects When you install a OpenShift Dedicated cluster, monitoring for user-defined projects is enabled by default. With monitoring for user-defined projects enabled, you can monitor your own OpenShift Dedicated projects without the need for an additional monitoring solution. The dedicated-admin user has default permissions to configure and access monitoring for user-defined projects. Note Custom Prometheus instances and the Prometheus Operator installed through Operator Lifecycle Manager (OLM) can cause issues with user-defined project monitoring if it is enabled. Custom Prometheus instances are not supported. Optionally, you can disable monitoring for user-defined projects during or after a cluster installation.

Commands:
20.14. Displaying a URI for Connection to a Graphical Display Running the virsh domdisplay command will output a URI that can then be used to connect to the graphical display of the guest virtual machine via VNC, SPICE, or RDP. The optional --type can be used to specify the graphical display type. If the argument --include-password is used, the SPICE channel password will be included in the URI. Example 20.36. How to display the URI for SPICE The following example displays the URI for SPICE, which is the graphical display that the virtual machine guest1 is using: For more information about connection URIs, see the libvirt upstream pages .

Commands:
virsh domdisplay --type spice guest1 spice://192.0.2.1:5900
5.2.16. /proc/loadavg This file provides a look at the load average in regard to both the CPU and IO over time, as well as additional data used by uptime and other commands. A sample /proc/loadavg file looks similar to the following: The first three columns measure CPU and IO utilization of the last one, five, and 10 minute periods. The fourth column shows the number of currently running processes and the total number of processes. The last column displays the last process ID used.

Commands:
0.20 0.18 0.12 1/80 11206
Chapter 4. Exporting compliance data for selected systems Perform the following procedures to export a report showing compliance issues impacting your systems, based on filtering in place at the time of export. 4.1. Exporting a report for a single policy Perform the following steps to export a compliance report for a single policy. Procedure Navigate to the Security > Compliance > Reports tab and log in if necessary. Click on the policy to view the report. Apply filters as needed to refine results. Click View policy for more detailed information such as compliance threshold and business objective. At the top of the systems list, click the download icon to the right of the Remediate button and select Export to CSV or Export to JSON , based on your export preferences. Choose to open or save the file. Then click OK . 4.2. Exporting a report for selected systems Perform the following steps to export a compliance report for selected systems. Procedure Navigate to Security > Compliance > Systems and log in if necessary. Apply filters as needed to refine results. Select the systems you want to see in the report by checking the box to each system name. At the top of the systems list, click the download icon and select Export to CSV or Export to JSON , based on your export preferences. Choose to open or save the file. Then click OK .

Commands:
5.7. atlas 5.7.1. RHBA-2012:0402 - atlas bug fix update Updated atlas packages that fix one bug are now available for Red Hat Enterprise Linux 6. The ATLAS (Automatically Tuned Linear Algebra Software) project is a research effort focusing on applying empirical techniques providing portable performance. The atlas packages provide C and Fortran77 interfaces to a portably efficient BLAS (Basic Linear Algebra Subprograms) implementation and routines from LAPACK (Linear Algebra PACKKage). Bug Fix BZ# 723350 Previously, binary files from the base atlas package contained illegal instructions from an incompatible instruction set (3DNow!). As a consequence, an "Illegal instruction" error was displayed. This update disables usage of the instruction set. All users of atlas are advised to upgrade to these updated packages, which fix this bug.

Commands:
20.19. Creating a Dump File of a Guest Virtual Machine's Core Using virsh dump One of the methods of troubleshooting guest virtual machines (in addition to kdump and pvpanic ) is using the virsh dump domain corefilepath [ --bypass-cache ] { --live | --crash | --reset } [ --verbose ] [ --memory-only ] [ --format = format ] command. This creates a dump file containing the core of the guest virtual machine so that it can be analyzed, for example by the crash utility . Specifically, running virsh dump command dumps the guest virtual machine core to a file specified by the core file path that you supply. Note that some hypervisors may give restrictions on this action and may require the user to manually ensure proper permissions on the file and path specified in the corefilepath parameter. This command is supported with SR-IOV devices as well as other passthrough devices. The following arguments are supported and have the following effect: --bypass-cache - The file saved will not bypass the host's file system cache. It has no effect on the content of the file. Note that selecting this option may slow down the dump operation. --live will save the file as the guest virtual machine continues to run and will not pause or stop the guest virtual machine. --crash puts the guest virtual machine in a crashed status rather than leaving it in a paused state while the dump file is saved. The guest virtual machine will be listed as "Shut off", with the reason as "Crashed". --reset - When the dump file is successfully saved, the guest virtual machine will reset. --verbose displays the progress of the dump process --memory-only - Running a dump using this option will create a dump file where the contents of the dump file will only contain the guest virtual machine's memory and CPU common register file. This option should be used in cases where running a full dump will fail. This may happen when a guest virtual machine cannot be live migrated (due to a passthrough PCI device). You can save the memory-only dump using the --format= format option. The following formats are available: elf - the default, uncompressed format kdump-zlib - kdump-compressed format with zlib compression kdump-lzo - kdump-compressed format with LZO compression kdump-snappy - kdump-compressed format with Snappy compression Important The crash utility no longer supports the default core dump file format of the virsh dump command. If you use crash to analyze a core dump file created by virsh dump , you must use the --memory-only option. Additionally, you must also use the --memory-only option when creating a core dump file to attach to a Red Hat Suport Case. Note that the entire process can be monitored using the virsh domjobinfo command and can be canceled using the virsh domjobabort command. Example 20.47. How to create a dump file with virsh The following example creates a dump file of the guest1 virtual machine's core, saves it into the core/file/path.file file, and then resets the guest. The most common scenario for using this command is if your guest virtual machine is not behaving properly:

Commands:
virsh dump guest1 core/file/path.file --memory-only --reset
6.6. Other Ext4 File System Utilities Red Hat Enterprise Linux 6 also features other utilities for managing ext4 file systems: e2fsck Used to repair an ext4 file system. This tool checks and repairs an ext4 file system more efficiently than ext3, thanks to updates in the ext4 disk structure. e2label Changes the label on an ext4 file system. This tool also works on ext2 and ext3 file systems. quota Controls and reports on disk space (blocks) and file (inode) usage by users and groups on an ext4 file system. For more information on using quota , refer to man quota and Section 16.1, "Configuring Disk Quotas" . As demonstrated in Section 6.2, "Mounting an Ext4 File System" , the tune2fs utility can also adjust configurable file system parameters for ext2, ext3, and ext4 file systems. In addition, the following tools are also useful in debugging and analyzing ext4 file systems: debugfs Debugs ext2, ext3, or ext4 file systems. e2image Saves critical ext2, ext3, or ext4 file system metadata to a file. For more information about these utilities, refer to their respective man pages.

Commands:
Chapter 8. Copying files between buckets To copy files between buckets in your object store from your workbench, use the copy() method. Prerequisites You have cloned the odh-doc-examples repository to your workbench. You have opened the s3client_examples.ipynb file in your workbench. You have installed Boto3 and configured an S3 client. You know the key of the source file that you want to copy, and the bucket that the file is stored in. Procedure In the notebook, locate the following instructions to copy files between buckets: Within the copy_source block, replace <bucket_name> with the name of the source bucket and <key> with the key of the source file, as shown in the example. Replace the <destination_bucket> with the name of the bucket to copy to, and <destination_key> with the name of the key to copy to, as shown in the example. Execute the code cell. Verification Locate the following instructions to list objects in a bucket. Replace <bucket_name> with the name of the destination bucket, as shown in the example, and run the code cell. The file that you copied is displayed in the output.

Commands:
#Copying files between buckets #Replace the placeholder values with your own. copy_source = { 'Bucket': '<bucket_name>', 'Key': '<key>' } s3_client.copy(copy_source, '<destination bucket>', '<destination_key>')
copy_source = { 'Bucket': 'aqs086-image-registry', 'Key': 'series43-image12-086.csv' }
s3_client.copy(copy_source, 'aqs971-image-registry', '/tmp/series43-image12-086.csv')
#Copy Verification bucket_name = '<bucket_name>' for key in s3_client.list_objects_v2(Bucket=bucket_name)['Contents']: print(key['Key'])
#Copy Verification bucket_name = 'aqs971-image-registry' for key in s3_client.list_objects_v2(Bucket=bucket_name)['Contents']: print(key['Key']).
function::print_ustack Name function::print_ustack - Print out stack for the current task from string. Synopsis Arguments stk String with list of hexadecimal addresses for the current task. Description Perform a symbolic lookup of the addresses in the given string, which is assumed to be the result of a prior call to ubacktrace for the current task. Print one line per address, including the address, the name of the function containing the address, and an estimate of its position within that function. Return nothing. NOTE it is recommended to use print_usyms instead of this function.

Commands:
print_ustack(stk:string)
Appendix D. Command-Line Tools AMQ Broker includes a set of command-line interface (CLI) tools so you can manage your messaging journal. The table below lists the name for each tool and its description. Tool Description exp Exports the message data using a special and independent XML format. imp Imports the journal to a running broker using the output provided by exp . data Prints reports about journal records and compacts their data. encode Shows an internal format of the journal encoded to String. decode Imports the internal journal format from encode. For a full list of commands available for each tool, use the help parameter followed by the tool's name. In the example below, the CLI output lists all the commands available to the data tool after the user entered the command ./artemis help data . You can use the help at the tool for more information on how to execute each of the tool's commands. For example, the CLI lists more information about the data print command after the user enters the ./artemis help data print .

Commands:
./artemis help data NAME artemis data - data tools group (print|imp|exp|encode|decode|compact) (example ./artemis data print) SYNOPSIS artemis data artemis data compact [--broker <brokerConfig>] [--verbose] [--paging <paging>] [--journal <journal>] [--large-messages <largeMessges>] [--bindings <binding>] artemis data decode [--broker <brokerConfig>] [--suffix <suffix>] [--verbose] [--paging <paging>] [--prefix <prefix>] [--file-size <size>] [--directory <directory>] --input <input> [--journal <journal>] [--large-messages <largeMessges>] [--bindings <binding>] artemis data encode [--directory <directory>] [--broker <brokerConfig>] [--suffix <suffix>] [--verbose] [--paging <paging>] [--prefix <prefix>] [--file-size <size>] [--journal <journal>] [--large-messages <largeMessges>] [--bindings <binding>] artemis data exp [--broker <brokerConfig>] [--verbose] [--paging <paging>] [--journal <journal>] [--large-messages <largeMessges>] [--bindings <binding>] artemis data imp [--host <host>] [--verbose] [--port <port>] [--password <password>] [--transaction] --input <input> [--user <user>] artemis data print [--broker <brokerConfig>] [--verbose] [--paging <paging>] [--journal <journal>] [--large-messages <largeMessges>] [--bindings <binding>] COMMANDS With no arguments, Display help information print Print data records information (WARNING: don't use while a production server is running)
./artemis help data print NAME artemis data print - Print data records information (WARNING: don't use while a production server is running) SYNOPSIS artemis data print [--bindings <binding>] [--journal <journal>] [--paging <paging>] OPTIONS --bindings <binding> The folder used for bindings (default ../data/bindings) --journal <journal> The folder used for messages journal (default ../data/journal) --paging <paging> The folder used for paging (default ../data/paging)