mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 11. Supported and Unsupported features for IBM Power and IBM Z Table 11.1. List of supported and unsupported features on IBM Power and IBM Z Features IBM Power IBM Z Compact deployment Unsupported Unsupported Dynamic storage devices Unsupported Supported Stretched Cluster - Arbiter Supported Unsupported Federal Information Processing Standard Publication (FIPS) Supported Unsupported Ability to view pool compression metrics Supported Unsupported Automated scaling of Multicloud Object Gateway (MCG) endpoint pods Supported Unsupported Alerts to control overprovision Supported Unsupported Alerts when Ceph Monitor runs out of space Supported Unsupported Deployment of standalone Multicloud Object Gateway component Supported Unsupported Extended OpenShift Data Foundation control plane which allows pluggable external storage such as IBM Flashsystem Unsupported Unsupported IPV6 support Unsupported Unsupported Multus Unsupported Unsupported Multicloud Object Gateway (MCG) bucket replication Supported Unsupported Quota support for object data Supported Unsupported Minimum deployment Unsupported Unsupported Regional-Disaster Recovery (Regional-DR) with Red Hat Advanced Cluster Management (RHACM) Supported Unsupported Metro-Disaster Recovery (Metro-DR) multiple clusters with RHACM Supported Unsupported Single Node solution for Radio Access Network (RAN) Unsupported Unsupported Support for network file system (NFS) services Supported Unsupported Ability to change Multicloud Object Gateway (MCG) account credentials Supported Unsupported Multicluster monitoring in Red Hat Advanced Cluster Management console Supported Unsupported Deletion of expired objects in Multicloud Object Gateway lifecycle Supported Unsupported Agnostic deployment of OpenShift Data Foundation on any Openshift supported platform Unsupported Unsupported Installer provisioned deployment of OpenShift Data Foundation using bare metal infrastructure Unsupported Unsupported Openshift dual stack with OpenShift Data Foundation using IPv4 Unsupported Unsupported Ability to disable Multicloud Object Gateway external service during deployment Unsupported Unsupported Ability to allow overriding of default NooBaa backing store Unsupported Unsupported Allowing ocs-operator to deploy two MGR pods, one active and one standby Unsupported Unsupported

Commands:
Chapter 13. Uninstalling OpenShift Logging You can remove the logging subsystem from your OpenShift Container Platform cluster. 13.1. Uninstalling the logging subsystem for Red Hat OpenShift You can stop log aggregation by deleting the ClusterLogging custom resource (CR). After deleting the CR, there are other logging subsystem components that remain, which you can optionally remove. Deleting the ClusterLogging CR does not remove the persistent volume claims (PVCs). To preserve or delete the remaining PVCs, persistent volumes (PVs), and associated data, you must take further action. Prerequisites The Red Hat OpenShift Logging and Elasticsearch Operators must be installed. Procedure To remove OpenShift Logging: Use the OpenShift Container Platform web console to remove the ClusterLogging CR: Switch to the Administration Custom Resource Definitions page. On the Custom Resource Definitions page, click ClusterLogging . On the Custom Resource Definition Details page, click Instances . Click the Options menu to the instance and select Delete ClusterLogging . Optional: Delete the custom resource definitions (CRD): Switch to the Administration Custom Resource Definitions page. Click the Options menu to ClusterLogForwarder and select Delete Custom Resource Definition . Click the Options menu to ClusterLogging and select Delete Custom Resource Definition . Click the Options menu to Elasticsearch and select Delete Custom Resource Definition . Optional: Remove the Red Hat OpenShift Logging Operator and OpenShift Elasticsearch Operator: Switch to the Operators Installed Operators page. Click the Options menu to the Red Hat OpenShift Logging Operator and select Uninstall Operator . Click the Options menu to the OpenShift Elasticsearch Operator and select Uninstall Operator . Optional: Remove the OpenShift Logging and Elasticsearch projects. Switch to the Home Projects page. Click the Options menu to the openshift-logging project and select Delete Project . Confirm the deletion by typing openshift-logging in the dialog box and click Delete . Click the Options menu to the openshift-operators-redhat project and select Delete Project . Important Do not delete the openshift-operators-redhat project if other global operators are installed in this namespace. Confirm the deletion by typing openshift-operators-redhat in the dialog box and click Delete . To keep the PVCs for reuse with other pods, keep the labels or PVC names that you need to reclaim the PVCs. Optional: If you do not want to keep the PVCs, you can delete them. Warning Releasing or deleting PVCs can delete PVs and cause data loss. Switch to the Storage Persistent Volume Claims page. Click the Options menu to each PVC and select Delete Persistent Volume Claim . If you want to recover storage space, you can delete the PVs. Additional resources Reclaiming a persistent volume manually

Commands:
Chapter 1. Introducing .NET 6.0 .NET is a general-purpose development platform featuring automatic memory management and modern programming languages. Using .NET, you can build high-quality applications efficiently. .NET is available on Red Hat Enterprise Linux (RHEL) and OpenShift Container Platform through certified containers. .NET offers the following features: The ability to follow a microservices-based approach, where some components are built with .NET and others with Java, but all can run on a common, supported platform on RHEL and OpenShift Container Platform. The capacity to more easily develop new .NET workloads on Microsoft Windows. You can deploy and run your applications on either RHEL or Windows Server. A heterogeneous data center, where the underlying infrastructure is capable of running .NET applications without having to rely solely on Windows Server. .NET 6.0 is supported on RHEL 7, RHEL 8, RHEL 9, and OpenShift Container Platform versions 3.11 and later.

Commands:
Chapter 1. RESTful Plug-in 1.1. What is the RESTful Plug-in? The RESTful plug-in for the Ceph Manager ( ceph-mgr ) provides an API for interacting with a Red Hat Ceph Storage cluster. You can use the API to: Show the information about Monitors and OSDs Create or edit pools View and start scheduled processes on OSDs Show configuration options for the cluster, Monitor, and OSDs 1.2. Enabling and Securing the RESTful plug-in The RESTful plug-in offers the REST API access to the status of the cluster over an SSL-secured connection. This section describes how to enable the plug-in and secure it. Prerequisites Ensure that you have at least one ceph-mgr daemon active. See the Installing a Red Hat Ceph Storage section in the Red Hat Ceph Storage 4 Installation Guide . If you use a firewall, ensure that the 8003 port is enabled on the node with the active ceph-mgr daemon. Procedure Use the following commands on a node with the administration keyring. Enable the RESTful plug-in. Configure an SSL certificate. If your organization's certificate authority provides a certificate, set the certificate: Replace hostname with the host name of the host where the active ceph-mgr instance is running, certificate with the path to the certificate file, and key with the path to the key file, for example: If you want to use the certificate on all ceph-mgr instances, omit the hostname part, for example: Alternatively, generate a self-signed certificate. However, using a self-signed certificate does not provide full security benefits of the HTTPS protocol. Create an HTTP user and generate a password for HTTP basic authentication. Replace username with name of the user. For example, to create a user named admin : Connect to the RESTful plug-in web page. Open a web browser and enter the following URL: Replace ceph-mgr with the IP address or host name of the node with the active ceph-mgr daemon: If you used a self-signed certificate, confirm a security exception. Optional. If you want to use a static IP address for the RESTful plug-in, configure a load balancer. Additional Resources The ceph restful --help command The https:// ceph-mgr :8003/doc page, where ceph-mgr is the IP address or host name of the node with the running ceph-mgr instance The Using OpenSSL chapter in the Security Guide for Red Hat Enterprise Linux 7

Commands:
ceph mgr module enable restful
ceph config-key set mgr/restful/ hostname /crt -i certificate ceph config-key set mgr/restful/ hostname /key -i key
ceph config-key set mgr/restful/node1/crt -i restful.crt ceph config-key set mgr/restful/node1/key -i restful.key
ceph config-key set mgr/restful/crt -i restful.crt ceph config-key set mgr/restful/key -i restful.key
ceph restful create-self-signed-cert
ceph restful create-key username
ceph restful create-key admin 3ce361b7-97fb-4820-8edc-1090841f078e
https://_ceph-mgr_:8003
https://node1:8003
Providing feedback on Red Hat Directory Server We appreciate your input on our documentation and products. Please let us know how we could make it better. To do so: For submitting feedback on the Red Hat Directory Server documentation through Jira (account required): Go to the Red Hat Issue Tracker . Enter a descriptive title in the Summary field. Enter your suggestion for improvement in the Description field. Include links to the relevant parts of the documentation. Click Create at the bottom of the dialogue. For submitting feedback on the Red Hat Directory Server product through Jira (account required): Go to the Red Hat Issue Tracker . On the Create Issue page, click . Fill in the Summary field. Select the component in the Component field. Fill in the Description field including: The version number of the selected component. Steps to reproduce the problem or your suggestion for improvement. Click Create .

Commands:
Appendix F. References F.1. About Consistency Consistency is the policy that states whether it is possible for a data record on one node to vary from the same data record on another node. For example, due to network speeds, it is possible that a write operation performed on the master node has not yet been performed on another node in the store, a strong consistency guarantee will ensure that data which is not yet fully replicated is not returned to the application. 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
16.12. Troubleshooting If synchronization does not seem to function properly, see the Windows event log or Directory Server error log for information on any potential problems. Enable replication logging to record synchronization errors Enable replication logging for more detailed information on synchronization to be recorded in the error logs. The replication log level produces more verbose logs from the sync code. Messages related to synchronization traffic (which is the same as replication traffic) can help in diagnosing problems. For details about configuring log levels, see Section 21.3.7, "Configuring the Log Levels" . Error #1: After synchronization, the status returns error 81. One of the sync peer servers has not been properly configured for TLS communication. Examine the Directory Server access log file to see if the connection attempt was received by the Directory Server. There are also helpful messages in the Directory Server's error log file. To narrow down the source of the misconfiguration, try to establish an LDAPS connection to the Directory Server. If this connection attempt fails, check all values (including the port number, host name or IPv4/IPv6 address, search base, and user credentials) to see if any of these are the problem. If all else fails, reconfigure the Directory Server with a new certificate. If the LDAPS connection to the Directory Server is successful, it is likely that the misconfiguration is on Active Directory. Examine the Windows event log file for error messages. Note A common problem is that the certificate authority was not configured as trusted when the Windows sync services certificate database was configured. Error #2: An entry is moved from one subtree on Active Directory to another subtree, but the user is not moved to the corresponding subtree on Directory Server. This is a known issue with synchronizing modrdn operations on Active Directory with entries on Directory Server. To work around it, delete the entry on Active Directory and then add it anew to the new subtree. The deletion and the addition will be properly synchronized to the Directory Server peer.

Commands:
5.2. Using KVM virtio Drivers for New Storage Devices This procedure covers creating new storage devices using the KVM virtio drivers with virt-manager . Alternatively, the virsh attach-disk or virsh attach-interface commands can be used to attach devices using the virtio drivers. Important Ensure the drivers have been installed on the guest before proceeding to install new devices. If the drivers are unavailable the device will not be recognized and will not work. Procedure 5.2. Adding a storage device using the virtio storage driver Open the guest virtual machine by double clicking the name of the guest in virt-manager . Open the Show virtual hardware details tab by clicking . In the Show virtual hardware details tab, click the Add Hardware button. Select hardware type Select Storage as the Hardware type . Figure 5.1. The Add new virtual hardware wizard Select the storage device and driver Create a new disk image or select a storage pool volume. Set the Device type to Disk device and the Bus type to VirtIO to use the virtio drivers. Figure 5.2. The Add New Virtual Hardware wizard Click Finish to complete the procedure. Procedure 5.3. Adding a network device using the virtio network driver Open the guest virtual machine by double clicking the name of the guest in virt-manager . Open the Show virtual hardware details tab by clicking . In the Show virtual hardware details tab, click the Add Hardware button. Select hardware type Select Network as the Hardware type . Figure 5.3. The Add new virtual hardware wizard Select the network device and driver Set the Device model to virtio to use the virtio drivers. Choose the required Host device . Figure 5.4. The Add new virtual hardware wizard Click Finish to complete the procedure. Once all new devices are added, reboot the virtual machine. Virtual machines may not recognize the devices until the guest is rebooted.

Commands:
23.10. Block I/O Tuning <domain> ... <blkiotune> <weight>800</weight> <device> <path>/dev/sda</path> <weight>1000</weight> </device> <device> <path>/dev/sdb</path> <weight>500</weight> </device> </blkiotune> ... </domain> Figure 23.12. Block I/O tuning Although all are optional, the components of this section of the domain XML are as follows: Table 23.7. Block I/O tuning elements Element Description <blkiotune> This optional element provides the ability to tune blkio cgroup tunable parameters for the domain. If this is omitted, it defaults to the operating system provided defaults. <weight> This optional weight element is the overall I/O weight of the guest virtual machine. The value should be within the range 100 - 1000. <device> The domain may have multiple <device> elements that further tune the weights for each host physical machine block device in use by the domain. Note that multiple guest virtual machine disks can share a single host physical machine block device. In addition, as they are backed by files within the same host physical machine file system, this tuning parameter is at the global domain level, rather than being associated with each guest virtual machine disk device (contrast this to the <iotune> element which can be applied to a single <disk> ). Each device element has two mandatory sub-elements, <path> describing the absolute path of the device, and <weight> giving the relative weight of that device, which has an acceptable range of 100 - 1000.

Commands:
<domain> <blkiotune> <weight>800</weight> <device> <path>/dev/sda</path> <weight>1000</weight> </device> <device> <path>/dev/sdb</path> <weight>500</weight> </device> </blkiotune> </domain>
Chapter 1. Metrics overview You can set up a third-party solution to collect live metrics from Satellite Server, archive them for a fixed period of time, and analyze them. Obtaining metrics from Satellite is useful for capacity planning and troubleshooting performance issues. If you need to raise a support case with Red Hat to resolve a performance issue, the archived data provides valuable insight. Note that Red Hat Support can only access the archived data if you upload it to a support case. You can collect the following metrics from Satellite: Basic statistics from the operating system, including system load, memory utilization, and input/output operations Process statistics, including memory and CPU utilization Apache HTTP Server activity statistics PostgreSQL activity statistics Satellite application statistics

Commands:
8.3. Steal Time Accounting Steal time is the amount of CPU time needed by a guest virtual machine that is not provided by the host. Steal time occurs when the host allocates these resources elsewhere: for example, to another guest. Steal time is reported in the CPU time fields in /proc/stat . It is automatically reported by utilities such as top and vmstat . It is displayed as "%st", or in the "st" column. Note that it cannot be switched off. Large amounts of steal time indicate CPU contention, which can reduce guest performance. To relieve CPU contention, increase the guest's CPU priority or CPU quota, or run fewer guests on the host.

Commands:
C.2. Teiid Designer Perspective The Teiid Designer perspective provides access to fundamental model editing and management capabilities. This perspective includes the following main UI components or groups of components: Model Explorer View - Teiid tree view of Model Objects. Server View - JBoss Data Virtualization Server instance view. Provides view of contents for connected instances of installed Teiid runtime. Model Editors - Custom editors targeted for .xmi metadata model files. Properties View - Standard property values for selected workbench objects. Guides View - Guides and Status Views which enhance usability. Miscellaneous Views - Includes the Problems view, Error Log view and the SQL Results view (opened if Preview Data action is performed). Connections Views - Includes information about Connection Profiles, Data Sources and Default Server. Figure C.1. Teiid Designer Perspective Layout

Commands:
Chapter 1. Workflow for deploying and managing RHEL systems in open hybrid cloud environments Use Red Hat Insights to launch and manage your customized RHEL systems images in the open hybrid cloud environments. Currently, you can use Red Hat Insights to deploy and manage the RHEL systems in the following clouds: Amazon Web Services Microsoft Azure Google Cloud Platform You can access the Red Hat Insights with your Red Hat account, a RHEL subscription, and an activation key. No additional SKUs are required. See Creating an activation key . As part of the deployment, by using Red Hat Insights, you can follow an end-to-end workflow to: Define or use existing repositories . Configure integrations to launch your images . Build customized images . Launch the images in your preferred cloud . In addition, you can manage your systems by granting users access, monitoring the inventory of your system infrastructure, and applying patches to improve security and stability.

Commands:
5.4. Backing up ext2, ext3, or ext4 File Systems This procedure describes how to back up the content of an ext4, ext3, or ext2 file system into a file. Prerequisites If the system has been running for a long time, run the e2fsck utility on the partitions before backup: Procedure 5.1. Backing up ext2, ext3, or ext4 File Systems Back up configuration information, including the content of the /etc/fstab file and the output of the fdisk -l command. This is useful for restoring the partitions. To capture this information, run the sosreport or sysreport utilities. For more information about sosreport , see the What is a sosreport and how to create one in Red Hat Enterprise Linux 4.6 and later? Kdowledgebase article. Depending on the role of the partition: If the partition you are backing up is an operating system partition, boot your system into the rescue mode. See the Booting to Rescue Mode section of the System Administrator's Guide . When backing up a regular, data partition, unmount it. Although it is possible to back up a data partition while it is mounted, the results of backing up a mounted data partition can be unpredictable. If you need to back up a mounted file system using the dump utility, do so when the file system is not under a heavy load. The more activity is happening on the file system when backing up, the higher the risk of backup corruption is. Use the dump utility to back up the content of the partitions: Replace backup-file with a path to a file where you want the to store the backup. Replace device with the name of the ext4 partition you want to back up. Make sure that you are saving the backup to a directory mounted on a different partition than the partition you are backing up. Example 5.2. Backing up Multiple ext4 Partitions To back up the content of the /dev/sda1 , /dev/sda2 , and /dev/sda3 partitions into backup files stored in the /backup-files/ directory, use the following commands: To do a remote backup, use the ssh utility or configure a password-less ssh login. For more information on ssh and password-less login, see the Using the ssh Utility and Using Key-based Authentication sections of the System Administrator's Guide . For example, when using ssh : Example 5.3. Performing a Remote Backup Using ssh Note that if using standard redirection, you must pass the -f option separately. Additional Resources For more information, see the dump (8) man page.

Commands:
e2fsck /dev/ device
dump -0uf backup-file /dev/ device
dump -0uf /backup-files/sda1.dump /dev/sda1 # dump -0uf /backup-files/sda2.dump /dev/sda2 # dump -0uf /backup-files/sda3.dump /dev/sda3
dump -0u -f - /dev/ device | ssh root@ remoteserver.example.com dd of= backup-file
Chapter 4. Updating the Red Hat Virtualization Manager Updates to the Red Hat Virtualization Manager are released through the Content Delivery Network. Procedure Check if updated packages are available: Update the setup packages: Update the Red Hat Virtualization Manager with the engine-setup script. The engine-setup script prompts you with some configuration questions, then stops the ovirt-engine service, downloads and installs the updated packages, backs up and updates the database, performs post-installation configuration, and starts the ovirt-engine service. When the script completes successfully, the following message appears: Note The engine-setup script is also used during the Red Hat Virtualization Manager installation process, and it stores the configuration values supplied. During an update, the stored values are displayed when previewing the configuration, and might not be up to date if engine-config was used to update configuration after installation. For example, if engine-config was used to update SANWipeAfterDelete to true after installation, engine-setup will output "Default SAN wipe after delete: False" in the configuration preview. However, the updated values will not be overwritten by engine-setup . Important The update process might take some time. Do not stop the process before it completes. Update the base operating system and any optional packages installed on the Manager: Important If any kernel packages were updated, reboot the machine to complete the update.

Commands:
engine-upgrade-check
yum update ovirt\*setup\* rh\*vm-setup-plugins
engine-setup
Execution of setup completed successfully
yum update