mtpti5iD/redhat-docs_dataset huggingface dataset:
Configuring OpenShift Data Foundation for Metro-DR stretch cluster Red Hat OpenShift Data Foundation 4.9 Instructions on how to configure OpenShift Data Foundation between two different geographical locations for providing storage infrastructure with disaster recovery capabilities. Red Hat Storage Documentation Team Abstract The intent of this solution guide is to detail the steps and commands necessary to deploy OpenShift Data Foundation along with Kubernetes zone topology labels to achieve a highly available storage infrastructure. Important Configuring OpenShift Data Foundation for Metro-DR is a technology preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

Commands:
B.5. Internal error cannot find character device (null) Symptom This error message appears when attempting to connect to a guest virtual machine's console: Investigation This error message shows that there is no serial console configured for the guest virtual machine. Solution Set up a serial console in the guest's XML file. Procedure B.1. Setting up a serial console in the guest's XML Add the following XML to the guest virtual machine's XML using virsh edit : <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> Set up the console in the guest kernel command line. To do this, either log in to the guest virtual machine to edit the /boot/grub/grub.conf file directly, or use the virt-edit command line tool. Add the following to the guest kernel command line: Run the followings command:

Commands:
virsh console test2 Connected to domain test2 Escape character is ^] error: internal error cannot find character device (null)
<serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console>
console=ttyS0,115200
virsh start vm && virsh console vm
Chapter 47. New Drivers Storage Drivers cxgbit libnvdimm mpt2sas nd_blk nd_btt nd_e820 nd_pmem nvme Network Drivers ath10k_core (BZ#1298484) ath10k_pci (BZ#1298484) bnxt_en (BZ#1184635) brcmfmac brcmsmac brcmutil btbcm btcoexist btintel btrtl c_can c_can_pci c_can_platform can-dev cc770 cc770_platform ems_pci ems_usb esd_usb2 fjes geneve hfi1 i40iw iwl3945 iwl4965 iwldvm iwlegacy iwlmvm iwlwifi (BZ#1298113) kvaser_pci kvaser_usb macsec mwifiex mwifiex_pcie mwifiex_sdio mwifiex_usb mwl8k peak_pci peak_usb plx_pci qed qede rdmavt rt2800lib rt2800mmio rt2800pci rt2800usb rt2x00lib rt2x00mmio rt2x00pci rt2x00usb rt61pci rt73usb rtl_pci rtl_usb rtl8187 rtl8188ee rtl8192c-common rtl8192ce rtl8192cu rtl8192de rtl8192ee rtl8192se rtl8723-common rtl8723ae rtl8723be rtl8821ae rtlwifi sja1000 sja1000_platform slcan softing uas usb_8dev vcan Graphics Drivers and Miscellaneous Drivers amdgpu amdkfd gp2ap002a00f gpio-ich gpio-viperboard idma64 int3400_thermal leds-lt3593 ledtrig-gpio nfit pci-hyperv pwm-lpss qat_c3xxx qat_c3xxxvf qat_c62x qat_c62xvf qat_dh895xccvf regmap-spi rotary_encoder rtc-rx4581 rtsx_usb rtsx_usb_sdmmc sht15 target_core_user tpm_st33zp24 tpm_st33zp24_i2c virt-dma virtio-gpu zram

Commands:
Chapter 11. Renaming an IdM server You cannot change the host name of an existing Identity Management (IdM) server. However, you can replace the server with a replica of a different name. Procedure Install a new replica that will replace the existing server, ensuring the replica has the required host name and IP address. For details, see Installing an IdM replica . Important If the server you are uninstalling is the certificate revocation list (CRL) publisher server, make another server the CRL publisher server before proceeding. For details on how this is done in the context of a migration procedure, see the following sections: Stopping CRL generation on a RHEL 7 IdM CA server Starting CRL generation on the new RHEL 8 IdM CA server Stop the existing IdM server instance. Uninstall the existing server as described in Uninstalling an IdM server .

Commands:
ipactl stop
6.2. Local Mode Using Red Hat JBoss Data Grid's local mode instead of a map provides a number of benefits. Caches offer features that are unmatched by simple maps, such as: Write-through and write-behind caching to persist data. Entry eviction to prevent the Java Virtual Machine (JVM) running out of memory. Support for entries that expire after a defined period. JBoss Data Grid is built around a high performance, read-based data container that uses techniques such as optimistic and pessimistic locking to manage lock acquisitions. JBoss Data Grid also uses compare-and-swap and other lock-free algorithms, resulting in high throughput multi- CPU or multi-core environments. Additionally, JBoss Data Grid's Cache API extends the JDK 's ConcurrentMap , resulting in a simple migration process from a map to JBoss Data Grid. Report a bug 6.2.1. Configure Local Mode (Remote Client-Server Mode) A local cache can be added to any cache container. The following example demonstrates how to add the local-cache element. Procedure 6.2. The local-cache Element The local-cache element specifies information about the local cache used with the cache container using the following parameters: The name parameter specifies the name of the local cache to use. The start parameter indicates when the cache container starts, i.e. whether it will start lazily when requested or "eagerly" when the server starts up. Valid values for this parameter are EAGER and LAZY . The batching parameter specifies whether batching is enabled for the local cache. If statistics are enabled at the container level, per-cache statistics can be selectively disabled for caches that do not require monitoring by setting the statistics attribute to false . The index attribute of the indexing parameter specifies the type of indexing used for the local cache. Valid values for this attribute are NONE , LOCAL and ALL . Alternatively, create a DefaultCacheManager with the "no-argument" constructor. Both of these methods create a local default cache. Local and clustered caches are able to coexist in the same cache container, however where the container is without a <transport/> it can only contain local caches. The container used in the example can only contain local caches as it does not have a <transport/> . The cache interface extends the ConcurrentMap and is compatible with multiple cache systems. Report a bug 6.2.2. Configure Local Mode (Library Mode) In Red Hat JBoss Data Grid's Library mode, setting a cache's mode parameter to local equals not specifying a clustering mode at all. In the case of the latter, the cache defaults to local mode, even if its cache manager defines a transport. Set the cluster mode to local as follows: Report a bug

Commands:
<cache-container name="local" default-cache="default" statistics="true"> <local-cache name="default" start="EAGER" batching="false" statistics="true"> <indexing index="NONE"> <property name="default.directory_provider">ram</property> </indexing> </local-cache>
<clustering mode="local" />
Appendix D. S3 supported and unsupported verbs This information lists the latest supported and unsupported S3 verbs. Table D.1. Supported verbs Action API AbortMultipartUpload S3 CompleteMultipartUpload S3 CopyObject S3 CreateBucket S3 CreateMultipartUpload S3 DeleteBucket S3 DeleteBucketCORS S3 DeleteBucketEncryption S3 DeleteBucketLifecycle S3 DeleteBucketPolicy S3 DeleteBucketReplication S3 DeleteBucketTagging S3 DeleteBucketWebsite S3 DeleteObject S3 DeleteObjects S3 DeleteObjectTagging S3 GetBucketAcl S3 GetBucketCORS S3 GetBucketEncryption S3 GetBucketLocation S3 GetBucketNotificationConfiguration S3 GetBucketPolicy S3 GetBucketPolicyStatus S3 GetBucketReplication S3 GetBucketRequestPayment S3 GetBucketTagging S3 GetBucketVersioning S3 GetBucketWebsite S3 GetObject S3 GetObjectAcl S3 GetObjectAttributes S3 GetObjectLegalHold S3 GetObjectLockConfiguration S3 GetObjectRetention S3 GetObjectTagging S3 GetObjectTorrent S3 HeadBucket S3 HeadObject S3 ListBuckets S3 ListMultipartUploads S3 ListObjects S3 ListObjectsV2 S3 ListObjectVersions S3 ListParts S3 PutBucketAcl S3 PutBucketCORS S3 PutBucketEncryption S3 PutBucketLifecycle S3 PutBucketLifecycleConfiguration S3 PutBucketNotificationConfiguration S3 PutBucketPolicy S3 PutBucketReplication S3 PutBucketRequestPayment S3 PutBucketTagging S3 PutBucketVersioning S3 PutBucketWebsite S3 PutObject S3 PutObjectAcl S3 PutObjectLegalHold S3 PutObjectLockConfiguration S3 PutObjectRetention S3 PutObjectTagging S3 SelectObjectContent S3 UploadPart S3 UploadPartCopy S3 AssumeRole STS AssumeRoleWithWebIdentity STS GetSessionToken STS CreateOpenIDConnectProvider IAM CreateRole IAM DeleteOpenIDConnectProvider IAM DeleteRole IAM GetOpenIDConnectProvider IAM GetRole IAM ListRoles IAM DeleteBucketNotification S3 extension CreateTopic SNS GetTopicAttributes SNS DeleteTopic SNS ListTopics SNS Table D.2. Unsupported verbs Action API DeleteBucketInventoryConfiguration S3 DeleteIntelligentTieringConfiguration S3 GetBucketInventoryConfiguration S3 GetBucketLogging S3 GetIntelligentTieringConfiguration S3 ListBucketIntelligentTieringConfigurations S3 ListBucketInventoryConfigurations S3 PutBucketIntelligentTieringConfiguration S3 PutBucketInventoryConfiguration S3 PutBucketLogging S3 RestoreObject S3 AssumeRoleWithSAML STS DecodeAuthorizationMessage STS GetAccessKeyInfo STS GetCallerIdentity STS GetFederationToken STS AttachGroupPolicy IAM AttachRolePolicy IAM AttachUserPolicy IAM CreatePolicy IAM CreateSAMLProvider IAM DeletePolicy IAM DeleteSAMLProviders IAM GetPolicy IAM GetSAMLProviders IAM ListOpenIDConnectProviders IAM ListPolicies IAM ListSAMLProviders IAM

Commands:
B.5. Vaults B.5.1. Users Cannot Access Their Vault Due To Insufficient 'add' Privilege A user is unable to access his or her own user vault or add new user vaults. The following error message appears: What this means: The user's vault container is owned by another user. Typically, this situation occurs after another user, such as admin , creates the first user vault for the first user. The first user then cannot access any vaults in his or her own vault container. To fix the problem: Add the intended user as the owner of the vault container: Log in as admin . Add user as the container owner: Both admin and user now have access to the user's vault container because they are both the owners of the container. Optional. Verify that the user can now create a new user vault: Additional Resources Section 25.4, "Storing a User's Personal Secret"

Commands:
ipa: ERROR: Insufficient access: Insufficient 'add' privilege to add the entry 'cn=testvault,cn=user,cn=users,cn=vaults,cn=kra,dc=example,dc=com'.
kinit admin
ipa vaultcontainer-add-owner --user= user --users= user Owner users: admin, user Vault user: user ------------------------ Number of owners added 1 ------------------------
kinit user ipa vault-add testvault2 ------------------------ Added vault "testvault2" ------------------------
function::print_ubacktrace Name function::print_ubacktrace - Print stack back trace for current user-space task. Synopsis Arguments None Description Equivalent to print_ustack( ubacktrace ), except that deeper stack nesting may be supported. Returns nothing. See print_backtrace for kernel backtrace. Note To get (full) backtraces for user space applications and shared shared libraries not mentioned in the current script run stap with -d /path/to/exe-or-so and/or add --ldd to load all needed unwind data.

Commands:
print_ubacktrace()
Appendix B. Revision History Revision History Revision 3.5-2 Tue Sep 04 2018 Red Hat Gluster Storage Documentation Team Updates for Red Hat Gluster Storage 3.5 release. Revision 3.5-1 Tue Feb 06 2018 Laura Bailey Clarified that this document is for the non-hyperconverged virtualization and storage use case (BZ#1402404)

Commands:
20.3. Sending Commands with echo The virsh echo [--shell][--xml] arguments command displays the specified argument in the specified format. The formats you can use are --shell and --xml . Each argument queried is displayed separated by a space. The --shell option generates output that is formatted in single quotes where needed, so it is suitable for copying and pasting into the bash mode as a command. If the --xml argument is used, the output is formatted for use in an XML file, which can then be saved or used for guest's configuration.

Commands:
24.3. Configuring an Exported File System for Diskless Clients Prerequisites Install the necessary packages. See Chapter 24, Setting up a Remote Diskless System Configure the tftp service. See Section 24.1, "Configuring a tftp Service for Diskless Clients" . Configure DHCP. See Section 24.2, "Configuring DHCP for Diskless Clients" . Procedure The root directory of the exported file system (used by diskless clients in the network) is shared via NFS. Configure the NFS service to export the root directory by adding it to /etc/exports . For instructions on how to do so, see the Section 8.6.1, "The /etc/exports Configuration File" . To accommodate completely diskless clients, the root directory should contain a complete Red Hat Enterprise Linux installation. You can either clone an existing installation or install a new base system: To synchronize with a running system, use the rsync utility: Replace hostname.com with the hostname of the running system with which to synchronize via rsync . Replace exported-root-directory with the path to the exported file system. To install Red Hat Enterprise Linux to the exported location, use the yum utility with the --installroot option: The file system to be exported still needs to be configured further before it can be used by diskless clients. To do this, perform the following procedure: Procedure 24.2. Configure File System Select the kernel that diskless clients should use ( vmlinuz- kernel-version ) and copy it to the tftp boot directory: Create the initrd (that is, initramfs- kernel-version .img ) with NFS support: Change the initrd's file permissions to 644 using the following command: Warning If the initrd's file permissions are not changed, the pxelinux.0 boot loader will fail with a "file not found" error. Copy the resulting initramfs- kernel-version .img into the tftp boot directory as well. Edit the default boot configuration to use the initrd and kernel in the /var/lib/tftpboot/ directory. This configuration should instruct the diskless client's root to mount the exported file system ( /exported/root/directory ) as read-write. Add the following configuration in the /var/lib/tftpboot/pxelinux.cfg/default file: Replace server-ip with the IP address of the host machine on which the tftp and DHCP services reside. The NFS share is now ready for exporting to diskless clients. These clients can boot over the network via PXE.

Commands:
rsync -a -e ssh --exclude='/proc/*' --exclude='/sys/*' hostname.com :/ exported-root-directory
yum install @Base kernel dracut-network nfs-utils --installroot= exported-root-directory --releasever=/
cp /boot/vmlinuz- kernel-version /var/lib/tftpboot/
dracut --add nfs initramfs- kernel-version .img kernel-version
chmod 644 initramfs- kernel-version .img
default rhel7 label rhel7 kernel vmlinuz- kernel-version append initrd=initramfs- kernel-version .img root=nfs: server-ip : /exported/root/directory rw
Chapter 2. Learn more about OpenShift Container Platform Use the following sections to find content to help you learn about and use OpenShift Container Platform. 2.1. Architect Learn about OpenShift Container Platform Plan an OpenShift Container Platform deployment Additional resources Enterprise Kubernetes with OpenShift Tested platforms OpenShift blog Architecture Security and compliance What's new in OpenShift Container Platform Networking OpenShift Container Platform life cycle Backup and restore 2.2. Cluster Administrator Learn about OpenShift Container Platform Deploy OpenShift Container Platform Manage OpenShift Container Platform Additional resources Enterprise Kubernetes with OpenShift Installing OpenShift Container Platform Using Insights to identify issues with your cluster Getting Support Architecture Post installation configuration Logging OpenShift Knowledgebase articles OpenShift Interactive Learning Portal Networking About OpenShift Container Platform monitoring OpenShift Container Platform Life Cycle Storage Backup and restore Updating a cluster 2.3. Application Site Reliability Engineer (App SRE) Learn about OpenShift Container Platform Deploy and manage applications Additional resources OpenShift Interactive Learning Portal Projects Getting Support Architecture Operators OpenShift Knowledgebase articles Logging OpenShift Container Platform Life Cycle Blogs about logging Monitoring 2.4. Developer Learn about application development in OpenShift Container Platform Deploy applications Getting started with OpenShift for developers (interactive tutorial) Creating applications Red Hat Developers site Builds Red Hat OpenShift Dev Spaces (formerly Red Hat CodeReady Workspaces) Operators Images Developer-focused CLI

Commands:
Chapter 49. System and Subscription Management YUM 4 available as Technology Preview YUM version 4, a generation of the YUM package manager, is now available as a Technology Preview in the Red Hat Enterprise Linux 7 Extras channel . YUM 4 is based on the DNF technology and offers the following advantages over the standard YUM 3 used on RHEL 7: Increased performance Support for modular content Well-designed stable API for integration with tooling To install YUM 4 , run the yum install nextgen-yum4 command. Make sure to install the dnf-plugin-subscription-manager package, which includes the subscription-manager plug-in. This plug-in is required for accessing protected repositories provided by the Red Hat Customer Portal or Red Hat Satellite 6, and for automatic updates of the /etc/yum.repos.d/redhat.repo file. To manage packages, use the yum4 command and its particular options the same way as the yum command. For detailed information about differences between the new YUM 4 tool and YUM 3 , see http://dnf.readthedocs.io/en/latest/cli_vs_yum.html . (BZ# 1461652 , BZ# 1558411 ) For instructions on how to enable the Extras channel, see the Knowledgebase article How to subscribe to the Extras channel/repo .

Commands:
Chapter 10. Logging 10.1. Configuring logging Red Hat build of Rhea uses the JavaScript debug module to implement logging. For example, to enable detailed client logging, set the DEBUG environment variable to rhea* : Example: Enabling detailed logging USD export DEBUG=rhea* USD <your-client-program> 10.2. Enabling protocol logging The client can log AMQP protocol frames to the console. This data is often critical when diagnosing problems. To enable protocol logging, set the DEBUG environment variable to rhea:frames : Example: Enabling protocol logging USD export DEBUG=rhea:frames USD <your-client-program>

Commands:
export DEBUG=rhea* <your-client-program>
export DEBUG=rhea:frames <your-client-program>
Chapter 1. Introduction to Federal Information Processing Standards (FIPS) The Federal Information Processing Standards (FIPS) provides guidelines and requirements for improving security and interoperability across computer systems and networks. The FIPS 140-2 and 140-3 series apply to cryptographic modules at both the hardware and software levels. The National Institute of Standards and Technology in the United States implements a cryptographic module validation program with searchable lists of both in-process and approved cryptographic modules. Red Hat Enterprise Linux (RHEL) brings an integrated framework to enable FIPS 140 compliance system-wide. When operating under FIPS mode, software packages using cryptographic libraries are self-configured according to the global policy. Most of the packages provide a way to change the default alignment behavior for compatibility or other needs. Red Hat build of OpenJDK 8 is a FIPS policy-aware package. Additional resources For more information on how to install RHEL with FIPS mode enabled, see Installing a RHEL 8 system with FIPS mode enabled . For more information on how to enable FIPS mode after installing RHEL, see Switching the system to FIPS mode . For more information on how to run Red Hat build of OpenJDK in FIPS mode on RHEL. See Running OpenJDK in FIPS mode on RHEL . For more information on Red Hat compliance with Government Standards, see Government Standards .

Commands:
function::get_loadavg_index Name function::get_loadavg_index - Get the load average for a specified interval Synopsis Arguments indx The load average interval to capture. Description This function returns the load average at a specified interval. The three load average values 1, 5 and 15 minute average corresponds to indexes 0, 1 and 2 of the avenrun array - see linux/sched.h. Please note that the truncated-integer portion of the load average is returned. If the specified index is out-of-bounds, then an error message and exception is thrown.

Commands:
get_loadavg_index:long(indx:long)
Chapter 81. token This chapter describes the commands under the token command. 81.1. token issue Issue new token Usage: Table 81.1. Command arguments Value Summary -h, --help Show this help message and exit Table 81.2. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns Table 81.3. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 81.4. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 81.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show. 81.2. token revoke Revoke existing token Usage: Table 81.6. Positional arguments Value Summary <token> Token to be deleted Table 81.7. Command arguments Value Summary -h, --help Show this help message and exit

Commands:
openstack token issue [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty]
openstack token revoke [-h] <token>