mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Feature enhancements Cryostat 2.3 includes feature enhancements that build upon the Cryostat 2.2 offerings. User actions on node groups disabled when performing back-end checks From Cryostat 2.3.1 onward, the Topology view of the Cryostat web console automatically disables user actions on groups of target JVMs while back-end checks are in progress. This ensures that users cannot perform actions in the Cryostat web console when, for example, network latency might delay the completion of a back-end check. Settings view In Cryostat 2.3, the Settings view is updated with various enhancements to the visual display of the view and to provide additional settings that you can configure. The updates include the following enhancements: Option to set dark and light display themes for your console Setting options are grouped into categories, for example, General or Advanced Option to configure language settings and date and time formats Automated analysis reports In Cryostat 2.3, the Automated analysis reports are enhanced. Enhancements include the following updates: New user interface to display the Automated analysis reports in the form of cards on your dashboard. You can view and filter the information according to your requirements. Expanded analysis performed on your JFR recordings to incorporate additional categories of errors in the data. Additional error description provided and guidance to help you to troubleshoot. Ability to bookmark URL links With Cryostat 2.3, you can create bookmarks on your browser to the direct URLs of different sections and views of your Cryostat instance. Multiple file upload With Cryostat 2.3, you can upload multiple files simultaneously by using the File upload action on the Cryostat user interface. To upload the selected files, click Upload . When the upload is complete, click Submit . More informative target application connection URL In Cryostat 2.3, the format of the Connection URL of your target application is enhanced to provide more detail about the application that your Cryostat instance is connected to. Previously, if you were running Cryostat on Red Hat OpenShift, this connection URL showed only the IP address information and port number. With this update, the URL format shows the IP address, the namespace in which the application was located, and the port number.

Commands:
8.31. coolkey 8.31.1. RHBA-2014:1611 - coolkey bug fix update Updated coolkey packages that fix one bug are now available for Red Hat Enterprise Linux 6. Coolkey is a smart card support library for the CoolKey, Common Access Card (CAC), and Personal Identity Verification (PIV) smart cards. Bug Fix BZ# 1125987 A certain variable was previously uninitialized in the coolkey code. If that variable inherited a single "magic" value, coolkey could fail to present any certificates or keys that were stored in a smart card controlled by coolkey (a CAC, PIV, or coolkey card). Consequently, although the smart card was recognized, the certificates and keys were not visible to some applications. With this update, that variable is now initialized to a safe value and coolkey now presents its certificates and keys properly. Users of coolkey are advised to upgrade to these updated packages, which fix this bug.

Commands:
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-07-19 07:42:32 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
10.3. Return Values and the Asynchronous API When the asynchronous API is used in Red Hat JBoss Data Grid, the client code requires the asynchronous operation to return either the Future or the NotifyingFuture in order to query the value. Note NotifyingFutures are only available in JBoss Data Grid Library mode. Call the following operation to obtain the result of an asynchronous operation. This operation blocks threads when called. Report a bug

Commands:
Future.get()
Preface The Red Hat Quay application programming interface (API) is an OAuth 2 RESTful API that consists of a set of endpoints for adding, displaying, changing and deleting features for Red Hat Quay. Red Hat Quay abides by the Semantic Versioning (SemVer) specifications . The following conditions are met with each major, minor, and patch release: Major versions of Red Hat Quay might include incompatible API changes. For example, the API of Red Hat Quay 2.0 differs from Red Hat Quay 3.0. Minor versions of Red Hat Quay, for example, 3.y, adds functionality in a backwards compatible manner. Patch versions of Red Hat Quay, for example, 3.y.z, introduces backwards compatible bug fixes. Currently, Red Hat Quay uses the api/v1 endpoint for 3.y.z releases. This guide describes the api/v1 endpoints and the browser-based examples for accessing those endpoints.

Commands:
Chapter 14. Enabling the Red Hat OpenShift Data Foundation console plugin The Data Foundation console plugin is enabled by default. In case, this option was unchecked during OpenShift Data Foundation Operator installation, use the following instructions to enable the console plugin post-deployment either from the graphical user interface (GUI) or command-line interface. Prerequisites You have administrative access to the OpenShift Web Console. OpenShift Data Foundation Operator is installed and running in the openshift-storage namespace. Procedure From user interface In the OpenShift Web Console, click Operators Installed Operators to view all the installed operators. Ensure that the Project selected is openshift-storage . Click on the OpenShift Data Foundation operator. Enable the console plugin option. In the Details tab, click the pencil icon under the Console plugin . Select Enable , and click Save . From command-line interface Execute the following command to enable the console plugin option: Verification steps After the console plugin option is enabled, a pop-up with a message, Web console update is available appears on the GUI. Click Refresh web console from this pop-up for the console changes to reflect. In the Web Console, navigate to Storage and verify if Data Foundation is available.

Commands:
oc patch console.operator cluster -n openshift-storage --type json -p '[{"op": "add", "path": "/spec/plugins", "value": ["odf-console"]}]'
B.47. lldpad B.47.1. RHBA-2010:0857 - lldpad bug fix update An updated lldpad package that fixes dcbx negotiation issues is now available for Red Hat Enterprise Linux 6. The lldpad package adds Link Layer Discovery Protocol (LLDP) support for all ports. Bug Fix BZ# 639414 Previously, lldpad failed to initiate a dcbx negotiation when a "link down" netlink event message was dropped or lost. As a result, a boot failure occurred and the system got suspended. With this update, lldpad dcbx negotiation works as expected. All lldpad users are advised to upgrade to this updated package, which resolves this issue.

Commands:
Chapter 2. Accessing monitoring for user-defined projects When you install a Red Hat OpenShift Service on AWS (ROSA) cluster, monitoring for user-defined projects is enabled by default. With monitoring for user-defined projects enabled, you can monitor your own ROSA 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:
19.3. Eviction and Passivation To ensure that a single copy of an entry remains, either in memory or in a cache store, use passivation in conjunction with eviction. The primary reason to use passivation instead of a normal cache store is that updating entries require less resources when passivation is in use. This is because passivation does not require an update to the cache store. 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug 19.3.1. Eviction and Passivation Usage If the eviction policy caused the eviction of an entry from the cache while passivation is enabled, the following occur as a result: A notification regarding the passivated entry is emitted to the cache listeners. The evicted entry is stored. When an attempt to retrieve an evicted entry is made, the entry is lazily loaded into memory from the cache loader. After the entry and its children are loaded, they are removed from the cache loader and a notification regarding the entry's activation is sent to the cache listeners. 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug 19.3.2. Eviction Example when Passivation is Disabled The following example indicates the state of the memory and the persistent store during eviction operations with passivation disabled. Table 19.1. Eviction when Passivation is Disabled Step Key in Memory Key on Disk Insert keyOne Memory: keyOne Disk: keyOne Insert keyTwo Memory: keyOne , keyTwo Disk: keyOne , keyTwo Eviction thread runs, evicts keyOne Memory: keyTwo Disk: keyOne , keyTwo Read keyOne Memory: keyOne , keyTwo Disk: keyOne , keyTwo Eviction thread runs, evicts keyTwo Memory: keyOne Disk: keyOne , keyTwo Remove keyTwo Memory: keyOne Disk: keyOne 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug 19.3.3. Eviction Example when Passivation is Enabled The following example indicates the state of the memory and the persistent store during eviction operations with passivation enabled. Table 19.2. Eviction when Passivation is Enabled Step Key in Memory Key on Disk Insert keyOne Memory: keyOne Disk: Insert keyTwo Memory: keyOne , keyTwo Disk: Eviction thread runs, evicts keyOne Memory: keyTwo Disk: keyOne Read keyOne Memory: keyOne , keyTwo Disk: Eviction thread runs, evicts keyTwo Memory: keyOne Disk: keyTwo Remove keyTwo Memory: keyOne Disk: 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
Chapter 7. Supplemental certification Open supplemental certifications in the following scenarios: First time certification The bare-metal supplemental certification can be automatically created during a different certification process, for example, when you applied for the Red Hat Enterprise Linux System certification. If it was not automatically created, or if you need to apply for the certification at a later date, open a new supplemental certification above the Red Hat OpenStack Compute Node certification. Recertification Open a supplemental certification to update an existing RHOSP bare-metal certification. You may want to recertify your product, for example, to certify the same system on different versions of a Red Hat platform or because your product has received a significant update. You are responsible for initiating these certifications and notifying Red Hat of any material changes to your product.

Commands:
9.5. Ethernet Bridge Configuration Using iproute The iproute package can be used as an alternative to the bridge-utils. It allows to set bridge port options such as priority , cost or state . To set port options for an interface enp1s0 assigned to a bridge device, using the ip utility, issue the following command as root : To select the available options, using the ip utility, issue the following command as root : For more details on the port options, see the ip-link(8) man page.

Commands:
~]# ip link set enp1s0 type bridge_slave option
~]# ip link help bridge_slave Usage: ... bridge_slave [ state STATE ] [ priority PRIO ] [cost COST ] [ guard {on | off} ] [ hairpin {on | off} ] [ fastleave {on | off} ] [ root_block {on | off} ] [ learning {on | off} ] [ flood {on | off} ]
Chapter 36. Other Tuning Options This section describes other places in JBoss EAP messaging that can be tuned. Use asynchronous send acknowledgements. If you need to send non-transactional, durable messages and do not need a guarantee that they have reached the server by the time the call to send() returns, do not set them to be sent blocking. Instead use asynchronous send acknowledgements to get your send acknowledgements returned in a separate stream. However, in the case of a server crash, some messages might be lost. Use pre-acknowledge mode. With pre-acknowledge mode, messages are acknowledged before they are sent to the client. This reduces the amount of acknowledgment traffic on the wire. However, if that client crashes, messages will not be redelivered if the client reconnects. Disable security. There is a small performance boost when you disable security by setting the security-enabled attribute to false. Disable persistence. You can turn off message persistence altogether by setting persistence-enabled to false . Sync transactions lazily. Setting journal-sync-transactional to false provides better transactional persistent performance at the expense of some possibility of loss of transactions on failure. Sync non-transactional lazily. Setting journal-sync-non-transactional to false provides better non-transactional persistent performance at the expense of some possibility of loss of durable messages on failure. Send messages non-blocking. To avoid waiting for a network round trip for every message sent, set block-on-durable-send and block-on-non-durable-send to false if you are using Jakarta Messaging and JNDI, or set it directly on the ServerLocator by calling the setBlockOnDurableSend() and setBlockOnNonDurableSend() methods. Optimize the consumer-window-size . If you have very fast consumers, you can increase the consumer-window-size to effectively disable consumer flow control. Use the core API instead of the Jakarta Messaging API. Jakarta Messaging operations must be translated into core operations before the server can handle them, resulting in lower performance than when you use the core API. When using the core API, try to use methods that take SimpleString as much as possible. SimpleString , unlike java.lang.String , does not require copying before it is written to the wire, so if you reuse SimpleString instances between calls, you can avoid some unnecessary copying. Note that the core API is not portable to other brokers.

Commands:
1.4. Note on Accessibility The GNOME desktop includes assistive technologies to support users with various impairments and special needs, and to interact with common assistive devices. The Universal access menu provides a quick set up for users with various disabilities. The icon is placed on the top bar and looks like a person surrounded by a circle: All the accessibility features are documented in GNOME Help , which can be easily accessed by opening the Activities overview and typing help . From the GNOME Help menu, select Universal access . Note To access GNOME as a visually impaired person, press the Super + Alt + S key combination, which switches on the screen reader. You can find more details on using Orca screen reader on its help page .

Commands:
Chapter 5. Adding a CA bundle after upgrading Red Hat OpenShift AI 2.18 provides support for using self-signed certificates. If you have upgraded from OpenShift AI 2.7 or earlier versions, you can add self-signed certificates to the OpenShift AI deployments and Data Science Projects in your cluster. There are two ways to add a Certificate Authority (CA) bundle to OpenShift AI. You can use one or both of these methods: For OpenShift clusters that rely on self-signed certificates, you can add those self-signed certificates to a cluster-wide Certificate Authority (CA) bundle ( ca-bundle.crt ) and use the CA bundle in Red Hat OpenShift AI. You can use self-signed certificates in a custom CA bundle ( odh-ca-bundle.crt ) that is separate from the cluster-wide bundle. For more information, see Working with certificates . Prerequisites You have admin access to the DSCInitialization resources in the OpenShift cluster. You installed the OpenShift command line interface ( oc ) as described in Installing the OpenShift CLI . You upgraded Red Hat OpenShift AI from version 2.7 or earlier. If you are working in a new installation of Red Hat OpenShift AI, see Adding a CA bundle . Procedure Log in to the OpenShift as a cluster administrator. Click Operators Installed Operators and then click the Red Hat OpenShift AI Operator. Click the DSC Initialization tab. Click the default-dsci object. Click the YAML tab. Add the following to the spec section, setting the managementState field to Managed : If you want to use self-signed certificates added to a cluster-wide CA bundle, log in to the OpenShift as a cluster administrator and follow the steps as described in Configuring the cluster-wide proxy during installation . If you want to use self-signed certificates in a custom CA bundle that is separate from the cluster-wide bundle, follow these steps: Add the custom certificate to the customCABundle field of the default-dsci object, as shown in the following example: Click Save . The Red Hat OpenShift AI Operator creates an odh-trusted-ca-bundle ConfigMap containing the certificates in all new and existing non-reserved namespaces. Verification If you are using a cluster-wide CA bundle, run the following command to verify that all non-reserved namespaces contain the odh-trusted-ca-bundle ConfigMap: If you are using a custom CA bundle, run the following command to verify that a non-reserved namespace contains the odh-trusted-ca-bundle ConfigMap and that the ConfigMap contains your customCABundle value. In the following command, example-namespace is the non-reserved namespace and examplebundle123 is the customCABundle value.

Commands:
spec: trustedCABundle: managementState: Managed customCABundle: ""
spec: trustedCABundle: managementState: Managed customCABundle: | -----BEGIN CERTIFICATE----- examplebundle123 -----END CERTIFICATE-----
oc get configmaps --all-namespaces -l app.kubernetes.io/part-of=opendatahub-operator | grep odh-trusted-ca-bundle
oc get configmap odh-trusted-ca-bundle -n example-namespace -o yaml | grep examplebundle123
Chapter 5. Compiler and Tools Support for the el_GR@euro, ur_IN, and wal_ET locales has been added The el_GR@euro, ur_IN, and wal_ET locales provide specialized support for newer currency symbols like the Euro, and complete coverage in the instances where the locale was previously unsupported. Users can now specify these locales using the relevant environment variables to take advantage of the new localization support. (BZ# 1101858 ) The Net:SSLeay Perl module now supports restricting of TLS version The Net:SSLeay Perl module has been updated to support explicit specification of the TLS protocol version, which can be used for improving security. To restrict TLS version to 1.1 or 1.2, set the Net::SSLeay::ssl_version variable to 11 or 12 , respectively. (BZ# 1325407 ) The IO::Socket::SSL Perl module now supports restricting of TLS version The Net:SSLeay Perl module has been updated to support explicit specification of the TLS protocol versions 1.1 or 1.2 to improve security, and the IO::Socket::SSL module has been updated accordingly. When a new IO::Socket::SSL object is created, it is now possible to restrict the TLS version to 1.1 or 1.2 by setting the SSL_version option to TLSv1_1 or TLSv1_2 respectively. Alternatively, TLSv11 and TLSv12 can be used. Note that these values are case-sensitive. (BZ# 1331037 ) ca-certificates rebased to version 2.10 The certificate store has been upgraded to include the changes contained in version 2.10 of the Certificate Authority certificate list published by the Mozilla Foundation as part of the Network Security Services (NSS) version 3.27. In order to preserve compatibility with existing PKI deployments and with software based on OpenSSL and GnuTLS, several root CA certificates with an RSA key size of 1024 bits have been kept as trusted by default. See the following Knowledgebase article for instructions on disabling these legacy modifications: https://access.redhat.com/articles/1413643 . (BZ# 1368996 )

Commands:
Chapter 2. Compatibility Matrix for Red Hat Ceph Storage 7.1 The following tables list products and their versions compatible with Red Hat Ceph Storage 7.1. Host Operating System Version Red Hat Enterprise Linux 8.10, 9.4, 9.5 Standard lifecycle 9.4 is included in the product. Important All nodes in the cluster and their clients must use the supported OS version(s) to ensure that the version of the ceph package is the same on all nodes. Using different versions of the ceph package is not supported. Ubuntu is not supported as a deploying host operating system. Note Red Hat Enterprise Linux 8 deployments require a Red Hat Enterprise Linux 9 bootstrap node. Product Version Notes Ansible Supported in a limited capacity. Supported for upgrade and conversion to Cephadm and for other minimal playbooks. Red Hat OpenShift Data Foundation See the Red Hat OpenShift Data Foundation Supportability and Interoperability Checker for detailed external mode version compatibility. Red Hat OpenStack Platform 17.1.3 or later Supports Red Hat Ceph Storage when externally or director deployed. Red Hat OpenStack Services on OpenShift 18.0 or later Supports Red Hat Ceph Storage when externally deployed or with HyperConverged Infrastructure (HCI). Red Hat Satellite 6.x Only registering with the Content Delivery Network (CDN) is supported. Registering with Red Hat Network (RHN) is deprecated and not supported. Client Connector Version Notes S3A 2.8.x, 3.2.x, and trunk Red Hat Ceph Storage as a backup target Version Notes CommVault Cloud Data Management v11 IBM Spectrum Protect Plus 10.1.5 IBM Spectrum Protect server 8.1.8 NetApp AltaVault 4.3.2 and 4.4 Rubrik Cloud Data Management (CDM) 3.2 onwards Trilio, TrilioVault 3.0 S3 target Veeam (object storage) Veeam Availability Suite 9.5 Update 4 Supported on Red Hat Ceph Storage object storage with the S3 protocol Veritas NetBackup for Symantec OpenStorage (OST) cloud backup 7.7 and 8.0 Independent Software vendors Version Notes IBM Spectrum Discover 2.0.3 WekaIO 3.12.2

Commands: