mtpti5iD/redhat-docs_dataset huggingface dataset:
Preface The Red Hat build of Cryostat is a container-native implementation of JDK Flight Recorder (JFR) that you can use to securely monitor the Java Virtual Machine (JVM) performance in workloads that run on an OpenShift Container Platform cluster. You can use Cryostat 2.1 to start, stop, retrieve, archive, import, and export JFR data for JVMs inside your containerized applications by using a web console or an HTTP API. Depending on your use case, you can store and analyze your recordings directly on your Red Hat OpenShift cluster by using the built-in tools that Cryostat provides or you can export recordings to an external monitoring application to perform a more in-depth analysis of your recorded data. Important Red Hat build of Cryostat is a Technology Preview feature only. 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. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope (Red Hat Customer Portal).

Commands:
7.219. tuned 7.219.1. RHBA-2015:1376 - tuned bug fix update Updated tuned packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The tuned packages contain a daemon that tunes system settings dynamically. It does so by monitoring the usage of several system components periodically. Bug Fixes BZ# 1129936 Previously, the tuned service did not support direct-access storage devices (DASDs). As a consequence, DASDs were ignored by tuned and as a result were not configured. This update adds support for DASDs to tuned, and DASDs are now properly configured. BZ# 1036049 On Red Hat Enterprise Linux 6, the /etc/sysctl.conf file is the default configuration file for the sysctl tool settings and overrides can be specified in the /etc/sysctl.d/ directory. The tuned service previously handled the settings the opposite way, which is common in certain distributions. Consequently, the configuration specified in /etc/sysctl.d/ could be overridden by /etc/sysctl.conf. The way tuned handles /etc/sysctl.conf and /etc/sysctl.d/ has been reversed to match the Red Hat Enterprise Linux 6 logic. As a result, /etc/sysctl.conf is now processed first and can be overridden by settings in /etc/sysctl.d/. BZ# 1159963 Prior to this update, the tuned service did not support Xen Virtual Storage Devices (XVDs). Consequently, XVDs were ignored by tuned and were not configured. Support for XVDs has been added to tuned, and XVDs are now properly configured. BZ# 1174253 Previously, the value of the vm.max_map_count sysctl settings was set too low (1,000,000) in the sap-netweaver tuned profile, which could affect performance. With this update, vm.max_map_count is set to 2,000,000, which is a value recommended by SAP documentation. BZ# 1017366 Previously, certain files from the tuned packages could be incorrectly considered to differ from the RPM database. As a consequence, RPM verification performed by running the "rpm -V tuned" command could fail and it could be indicated that the files were changed despite not being touched by the user. This update excludes several attributes, such as size, md5sum, and mtime, from the verification of the files, and RPM verification no longer fails. BZ# 1064062 Due to a typographical error in the latency-performance profile in the SYSCTL_POST variable, the /etc/sysctl.d/* files were not processed by the tuned service. This update fixes the typographical error, and the /etc/sysctl.d/* files are now correctly processed by tuned. Users of tuned are advised to upgrade to these updated packages, which fix these bugs.

Commands:
C.4. Fonts Red Hat Enterprise Linux uses Fontconfig subsystem to manage and display fonts under the X Window System. It simplifies font management and provides advanced display features, such as anti-aliasing. This system is used automatically for applications programmed using the Qt 3 or GTK+ 2 graphical toolkits, or their newer versions. The Fontconfig font subsystem allows applications to directly access fonts on the system and use the X FreeType interface library ( Xft ) or other rendering mechanisms to render Fontconfig fonts with advanced features such as anti-aliasing. Graphical applications can use the Xft library with Fontconfig to draw text to the screen. Note Fontconfig uses the /etc/fonts/fonts.conf configuration file, which should not be edited by hand. Warning Any system where the user expects to run remote X applications needs to have the fonts group installed. This can be done by selecting the group in the installer, and also by running the yum groupinstall fonts command after installation. C.4.1. Adding Fonts to Fontconfig Adding new fonts to the Fontconfig subsystem is a straightforward process: To add fonts for an individual user, copy the new fonts into the .fonts/ directory in the user's home directory. To add fonts system-wide, copy the new fonts into the /usr/share/fonts/ directory. It is a good idea to create a new subdirectory, such as local/ or similar, to help distinguish between user-installed and default fonts. Run the fc-cache command as root to update the font information cache: In this command, replace <path-to-font-directory> with the directory containing the new fonts (either /usr/share/fonts/local/ or /home/ <user> /.fonts/ ). Note Individual users may also install fonts interactively, by typing fonts:/// into the Nautilus address bar, and dragging the new font files there.

Commands:
fc-cache <path-to-font-directory>
Chapter 5. Creating mirroring StorageClass resource The block volumes with mirroring enabled must be created using a new StorageClass that has additional imageFeatures required to enable faster image replication between managed clusters. The new features are exclusive-lock , object-map , and fast-diff . The default OpenShift Data Foundation StorageClass ocs-storagecluster-ceph-rbd does not include these features. Note This resource must be created on the Primary managed cluster and the Secondary managed cluster . Procedure Save the following YAML to filename ocs-storagecluster-ceph-rbdmirror.yaml . Create the file on both the managed clusters. Example output:

Commands:
allowVolumeExpansion: true apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: ocs-storagecluster-ceph-rbdmirror parameters: clusterID: openshift-storage csi.storage.k8s.io/controller-expand-secret-name: rook-csi-rbd-provisioner csi.storage.k8s.io/controller-expand-secret-namespace: openshift-storage csi.storage.k8s.io/fstype: ext4 csi.storage.k8s.io/node-stage-secret-name: rook-csi-rbd-node csi.storage.k8s.io/node-stage-secret-namespace: openshift-storage csi.storage.k8s.io/provisioner-secret-name: rook-csi-rbd-provisioner csi.storage.k8s.io/provisioner-secret-namespace: openshift-storage imageFeatures: layering,exclusive-lock,object-map,fast-diff imageFormat: "2" pool: ocs-storagecluster-cephblockpool provisioner: openshift-storage.rbd.csi.ceph.com reclaimPolicy: Delete volumeBindingMode: Immediate
oc create -f ocs-storagecluster-ceph-rbdmirror.yaml
storageclass.storage.k8s.io/ocs-storagecluster-ceph-rbdmirror created
Chapter 8. Approving developers This section shows how to make approvals for any step in the signup workflow. Once you have implemented the signup workflow with manual approval steps, you have a few options. The approval process is slightly different depending on the trigger and what is being approved. If you receive an email notification, follow the instructions in the following section. Otherwise, it depends on whether you want to approve an account, a service, or an application. 8.1. Approve from email notification If you, as the admin, receive an email notification that one of your developers has an item pending approval, you can copy/paste the URL for the item into your browser, and it will take you directly to the page to make the approval. 8.2. Account approval To search for specific accounts or filter all accounts that are in a pending (for approval) state, navigate to Audience > Accounts > Listing . To show only the pending accounts, select Pending in the dropdown list State and click Search . You can make individual approvals directly on each row, or select several rows at a time and perform a bulk approval. 8.3. Service approval To search for specific subscriptions to a service or filter all subscriptions that are in a pending (for approval) state, navigate to Audience > Accounts > Subscriptions . To view Subscriptions, enable Service Plans in Audience > Accounts > Usage Rules . You can select one subscription or several at a time and perform a bulk approval. 8.4. Application approval To search for applications or filter all applications that are in a pending (for approval) state: Navigate to Audience > Applications > Listing . Select "pending" in the dropdown list State and click Search . You can select one application or several at a time and perform a bulk approval. You can also start from the details page for a developer account, select which application you wish to approve from there, and make the approval on the application details page.

Commands:
24.2. Red Hat Virtualization Manager Log Files Table 24.2. Service Activity Log File Description /var/log/ovirt-engine/engine.log Reflects all Red Hat Virtualization Manager GUI crashes, Active Directory lookups, Database issues, and other events. /var/log/ovirt-engine/host-deploy Log files from hosts deployed from the Red Hat Virtualization Manager. /var/lib/ovirt-engine/setup-history.txt Tracks the installation and upgrade of packages associated with the Red Hat Virtualization Manager. /var/log/httpd/ovirt-requests-log Logs files from requests made to the Red Hat Virtualization Manager via HTTPS, including how long each request took. A Correlation-Id header is included to allow you to compare requests when comparing a log file with /var/log/ovirt-engine/engine.log . /var/log/ovn-provider/ovirt-provider-ovn.log Logs the activities of the OVN provider. For information about Open vSwitch logs, see the Open vSwitch documentation .

Commands:
Chapter 5. Technology previews This section describes bugs with significant impact on users that were fixed in this release of Red Hat Ceph Storage. In addition, the section includes descriptions of fixed known issues found in versions. Important Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. See the support scope for Red Hat Technology Preview features for more details. 5.1. Crimson OSD Newly implemented Crimson-OSD of the core Ceph object storage daemon (OSD) component replaces ceph-osd With this enhancement, the generation ceph-osd is implemented for multi-core scalability and to improve performance with fast network and storage devices, employing state-of-the-art technologies that includes DPDK and SPDK. Crimson aims to be compatible with an earlier version of OSD daemon with the class ceph-osd. For more information, see Crimson (Technology Preview) . 5.2. Ceph Object gateway Object storage archive zone in Red Hat Ceph Storage With this enhancement, the archive zone receives all objects from the production zones and keeps every version for every object, providing the user with an object catalogue that contains the full history of the object. This provides a secured object storage deployment that guarantees data retrieval even if the object/buckets in the production zones have been lost or compromised. For more information, see Configuring the archive zone (Technology Preview) . Protect object storage data outside of a production cluster using per-bucket enable and disable sync to an archive zone As an administrator, you can now recover any version of any object that has existed on the primary site from the archive zone. In the case of data loss or a ransomware attack, valid versions of all objects are accessible, if needed. For more information, see Configuring the archive zone (Technology Preview) . 5.3. RADOS Balancing Red Hat Ceph Storage cluster using read balancer With this release, to ensure that each device gets its fair share of primary OSDs so that read requests get distributed across OSDs in the cluster, evenly, read balancer is implemented. Read balancing is cheap and the operation is fast as there is no data movement involved. Read balancing supports replicated pools only. Erasure coded pools are not supported. For more information, see Balancing Red Hat Ceph Storage cluster using read balancer (Technology Preview) and Ceph rebalancing and recovery .

Commands:
Chapter 5. Technology preview This section describes Technology Preview features in AMQ Broker 7.10. Important 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 for production. For more information, see Red Hat Technology Preview Features Support Scope . New attributes for configuring address limits for paging You can configure the following new attributes to set individual and global address limits based on the number of messages. max-size-messages is the maximum number of messages allowed for the address before the broker executes the policy specified for the address-full-policy. The default value is -1, which means that there is no message limit. global-max-messages is the total number of messages that the broker can use for all addresses. When this limit is reached, for the address associated with an incoming message, the broker executes the policy that is specified as a value for the address-full-policy. The default value is -1, which means that there is no message limit. Note If limits that are set for the max-size-bytes or global-max-size attributes are reached before the limits set for the max-size-message or global-max-messages attributes, the broker executes the address-full policy.

Commands:
B.2.4. Uninstalling Uninstalling a package is just as simple as installing one. Type the following command at a shell prompt: Note Notice that we used the package name foo , not the name of the original package file , foo-1.0-1.el6.x86_64 . If you attempt to uninstall a package using the rpm -e command and the original full file name, you will receive a package name error. You can encounter dependency errors when uninstalling a package if another installed package depends on the one you are trying to remove. For example: Similar to how we searched for a shared object library (i.e. a <library_name> .so. <number> file) in Section B.2.2.3, "Unresolved Dependency" , we can search for a 64-bit shared object library using this exact syntax (and making sure to quote the file name): Warning Although we can force rpm to remove a package that gives us a Failed dependencies error (using the --nodeps option), this is not recommended, and may cause harm to other installed applications. Installing or removing packages with rpm --nodeps can cause applications to misbehave and/or crash, and can cause serious package management problems or, possibly, system failure. For these reasons, it is best to heed such warnings; the package manager-whether RPM , Yum or PackageKit -shows us these warnings and suggests possible fixes because accounting for dependencies is critical. The Yum package manager can perform dependency resolution and fetch dependencies from online repositories, making it safer, easier and smarter than forcing rpm to carry out actions without regard to resolving dependencies.

Commands:
-e foo
-e ghostscript error: Failed dependencies: libgs.so.8()(64bit) is needed by (installed) libspectre-0.2.2-3.el6.x86_64 libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.el6.x86_64 libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.el6.x86_64 ghostscript is needed by (installed) printer-filters-1.1-4.el6.noarch
~]# rpm -q --whatprovides "libgs.so.8()(64bit)" ghostscript-8.70-1.el6.x86_64
3.11. Desktop libwacom component The Lenovo X220 Tablet Touchscreen is not supported in the kernel shipped with Red Hat Enterprise Linux 6.3. wacomcpl package, BZ# 769466 The wacomcpl package has been deprecated and has been removed from the package set. The wacomcpl package provided graphical configuration of Wacom tablet settings. This functionality is now integrated into the GNOME Control Center. gnome-settings-daemon component, BZ# 826128 On some tablets, using the NVIDIA Graphics drivers to configure Twinview causes the tablet motions to be incorrectly mapped to the laptop screen instead of the tablet itself. Using the stylus on the tablet moves the cursor on the laptop screen. acroread component Running a AMD64 system without the sssd-client.i686 package installed, which uses SSSD for getting information about users, causes acroread to fail to start. To work around this issue, manually install the sssd-client.i686 package. kernel component, BZ# 681257 With newer kernels, such as the kernel shipped in Red Hat Enterprise Linux 6.1, Nouveau has corrected the Transition Minimized Differential Signaling (TMDS) bandwidth limits for pre-G80 NVIDIA chipsets. Consequently, the resolution auto-detected by X for some monitors may differ from that used in Red Hat Enterprise Linux 6.0. fprintd component When enabled, fingerprint authentication is the default authentication method to unlock a workstation, even if the fingerprint reader device is not accessible. However, after a 30 second wait, password authentication will become available. evolution component Evolution's IMAP backend only refreshes folder contents under the following circumstances: when the user switches into or out of a folder, when the auto-refresh period expires, or when the user manually refreshes a folder (that is, using the menu item Folder Refresh ). Consequently, when replying to a message in the Sent folder, the new message does not immediately appear in the Sent folder. To see the message, force a refresh using one of the methods describe above. anaconda component The clock applet in the GNOME panel has a default location of Boston, USA. Additional locations are added via the applet's preferences dialog. Additionally, to change the default location, left-click the applet, hover over the desired location in the Locations section, and click the Set... button that appears. xorg-x11-server component, BZ# 623169 In some multi-monitor configurations (for example, dual monitors with both rotated), the cursor confinement code produces incorrect results. For example, the cursor may be permitted to disappear off the screen when it should not, or be prevented from entering some areas where it should be allowed to go. Currently, the only workaround for this issue is to disable monitor rotation.

Commands:
Chapter 6. Registering virtual machines to use a host-based subscription Use an auto-attach activation key to register virtual machines so that they inherit a subscription from their hypervisor. Note This procedure is only valid if you have Simple Content Access (SCA) disabled on Satellite. You are not required to attach subscriptions to Activation Keys if you have SCA enabled. Instead, follow the Registering Hosts procedure in Managing hosts to register virtual machines. Note that SCA is enabled by default for newly created organizations. To learn more about SCA, see Simple Content Access . For more information about activation keys, see Managing Activation Keys in Managing Content . Prerequisites Create an activation key with auto-attach enabled and no subscriptions attached. Attach a host-based subscription to the virtual machine's hypervisor. Create and deploy a virt-who configuration that queries the virtual machine's hypervisor. Procedure Configure the virtual machine to register with Satellite Server: Register the virtual machine using the auto-attach activation key: The virtual machine receives a temporary subscription while Satellite Server waits for virt-who to provide information about which hypervisor the virtual machine is running on. After virt-who provides this information, Satellite Server attaches a permanent subscription to the virtual machine. If the virtual machine migrates to another hypervisor that reports to virt-who and has a host-based subscription attached, the virtual machine inherits a subscription from that hypervisor. If the hypervisor does not have a host-based subscription attached, Satellite Server automatically attaches a host-based subscription to the hypervisor, and the virtual machine inherits that subscription. If the virtual machine migrates to another hypervisor that does not report to virt-who, or there are insufficient subscriptions available to attach to the hypervisor, the virtual machine cannot inherit a subscription. To avoid this, either ensure that all hypervisors the virtual machine can migrate to have host-based subscriptions attached and report to virt-who, or limit the virtual machine's migration to specific hypervisors.

Commands:
yum install http:// satellite.example.com /pub/katello-ca-consumer-latest.noarch.rpm
subscription-manager register --org= organization_label --activationkey= activation_key_name
Chapter 5. Knative CLI for use with OpenShift Serverless The Knative ( kn ) CLI enables simple interaction with Knative components on OpenShift Container Platform. 5.1. Key features The Knative ( kn ) CLI is designed to make serverless computing tasks simple and concise. Key features of the Knative CLI include: Deploy serverless applications from the command line. Manage features of Knative Serving, such as services, revisions, and traffic-splitting. Create and manage Knative Eventing components, such as event sources and triggers. Create sink bindings to connect existing Kubernetes applications and Knative services. Extend the Knative CLI with flexible plugin architecture, similar to the kubectl CLI. Configure autoscaling parameters for Knative services. Scripted usage, such as waiting for the results of an operation, or deploying custom rollout and rollback strategies. 5.2. Installing the Knative CLI See Installing the Knative CLI .

Commands:
12.4. Containers Using the libvirt-lxc Tooling Have Been Deprecated The following libvirt-lxc packages are deprecated since Red Hat Enterprise Linux 7.1: libvirt-daemon-driver-lxc libvirt-daemon-lxc libvirt-login-shell Future development on the Linux containers framework is now based on the docker command-line interface. libvirt-lxc tooling may be removed in a future release of Red Hat Enterprise Linux (including Red Hat Enterprise Linux 7) and should not be relied upon for developing custom container management applications.

Commands: