mtpti5iD/redhat-docs_dataset huggingface dataset:
Deploying OpenShift Data Foundation using Red Hat OpenShift Service on AWS with hosted control planes Red Hat OpenShift Data Foundation 4.18 Instructions for deploying OpenShift Data Foundation using Red Hat OpenShift Service on AWS (ROSA) with hosted control planes (HCP) Red Hat Storage Documentation Team Abstract Read this document for instructions about how to install Red Hat OpenShift Data Foundation using Red Hat OpenShift Container Platform on ROSA with hosted control planes (HCP).

Commands:
Chapter 2. Configuring observability metrics The example dashboards and alerts provided by Connectivity Link use metrics exported by Connectivity Link and Gateway API components to provide insight into your applications, APIs, and Gateways. While not essential, it is best to configure these metrics and set up these dashboards and alerts on your OpenShift cluster. The example dashboards and alerts for observing Connectivity Link functionality use low-level CPU metrics and network metrics available from the user monitoring stack in OpenShift and resource state metrics from Gateway API and Connectivity Link resources. This section provides links to OpenShift documentation on how to configure monitoring and metrics storage and shows how to configure resources to scrape the relevant metrics. Note You must perform these steps on each OpenShift cluster that you want to use Connectivity Link on. Prerequisites You have installed Connectivity Link as described in Installing Connectivity Link on OpenShift . You have set up monitoring for user-defined projects as described in the OpenShift monitoring documentation . Procedure When monitoring for user projects is enabled in OpenShift, this allows the scraping of metrics from the Gateway and Connectivity Link components. To scrape additional metrics in OpenShift, you can install a kube-state-metrics instance, with a custom resource configuration as follows: Some example dashboards aggregate data by request path. By default, OpenShift Service Mesh metrics do not include labels for request paths, however, you can enable these labels as follows: Note This might lead to a high cardinality label where multiple time series are generated, which can have an impact on performance and resource usage. For more details, see the Reliable Insights blog post on cardinality . You can configure scraping of metrics from the various Connectivity Link Operators as follows: Note You must apply additional configuration so that all relevant metrics are scraped. However, this configuration depends on how you deploy your Gateway later. For details on the required steps, see Configuring and deploying Gateway policies with Connectivity Link . Additional information For details on how to enable metrics in OpenShift Service Mesh, see the OpenShift Service Mesh metrics documentation . For more details on Connectivity Link component metrics, see the Kuadrant metrics documentation .

Commands:
apply -f https://raw.githubusercontent.com/Kuadrant/kuadrant-operator/v1.0.1/config/observability/openshift/kube-state-metrics.yaml apply -k https://github.com/Kuadrant/gateway-api-state-metrics/config/kuadrant?ref=0.6.0
apply -f https://raw.githubusercontent.com/Kuadrant/kuadrant-operator/v1.0.1/config/observability/openshift/telemetry.yaml
apply -f https://raw.githubusercontent.com/Kuadrant/kuadrant-operator/v1.0.1/config/observability/prometheus/monitors/operators.yaml
4.275. rsyslog 4.275.1. RHBA-2011:1673 - rsyslog bug fix and enhancement update Updated rsyslog packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The rsyslog packages provide an enhanced, multi-threaded syslog daemon that supports MySQL, syslog/TCP, RFC 3195, permitted sender list, filtering on any message part, and fine grained output format control. Bug Fixes BZ# 661858 Previously, running rsyslog with Transport Layer Security (TLS) and TCP caused extensive memory and CPU consumption. Consequent to this, the system could become unresponsive. The source code has been modified and problems with the memory and CPU consumption no longer occur. BZ# 698705 Prior to this update, the rsyslog initscript created an invalid lock file named rsyslogd. As a consequence, rsyslog and rsyslogd did not match and the rc daemon did not stop the process when shutting down the system. With this update, the source code is modified so that the initscript creates a valid lock file. BZ# 701782 On the IBM System z and PowerPC architectures, the rsyslog daemon did not respect the configuration to send messages using TLS encryption. As a consequence, messages were sent as plain text. With this update, rsyslog is modified to send messages encrypted. BZ# 727208 Previously, the "ActionExecOnlyOnceEveryInterval" directive did not work as expected. If another message came within the time limit, the timeout got reset and would never expire. This problem has been fixed and the timeout now expires as expected. Enhancements BZ# 618488 Previously, rsyslog did not build the omsnmp module by default. This update provides the omsnmp module so that users are able to send syslog messages over Simple Network Management Protocol (SNMP). BZ# 683537 Previously, the rsyslog daemon included /var/log/boot.log in the /etc/logrotate.d/syslog file. The rotation caused a new boot.log file to be created with zero length, while a date was appended to the old one. Eventually, after a certain number of rotations, the boot.log data got lost. With this update, rotation is no longer used for /var/log/boot.log. BZ# 702314 This update includes the new ommail module in the rsyslog package, which can be used for sending emails based on received syslog events. BZ# 737096 This update introduces the new "SpaceLFOnReceive" configuration option and the "RSYSLOG_SysklogdFileFormat" format template. These new features allow users to configure rsyslog to behave like the sysklogd daemon, which was available in releases. Users are advised to upgrade to these updated rsyslog packages, which fix these bugs and add these enhancements.

Commands:
Chapter 146. HeadersMap Available as of Camel 2.20 The camel-headersmap is a faster implementation of a case-insenstive map which can be plugged in and used by Camel at runtime to have slight faster performance in the Camel Message headers. 146.1. Auto detection from classpath To use this implementation all you need to do is to add the camel-headersmap dependency to the classpath, and Camel should auto-detect this on startup and log as follows: For spring-boot there is a camel-headersmap-starter dependency you should use. 146.2. Manual enabling If you use OSGi or the implementation is not added to the classpath, you need to enable this explict such: Or in XML DSL (spring or blueprint XML file) you can declare the factory as a <bean> : and then Camel should detect the bean and use the factory.

Commands:
Detected and using custom HeadersMapFactory: org.apache.camel.component.headersmap.FastHeadersMapFactory@71e9ebae
CamelContext camel = camel.setHeadersMapFactory(new FastHeadersMapFactory());
<bean id="fastMapFactory" class="org.apache.camel.component.headersmap.FastHeadersMapFactory"/>
4.202. omping 4.202.1. RHEA-2011:1576 - omping bug fix and enhancement update An updated omping package that fixes several bugs and adds various enhancements is now available as a Technology Preview for Red Hat Enterprise Linux 6. Open Multicast Ping (omping) is a tool for testing IP multicast functionality, primarily on a LAN (local area network). It allows users to test multicast and receive sufficient information to detect whether a potential problem exists in the network configuration, or lies elsewhere, as might be the case with a bug. The omping package has been upgraded to upstream version 0.0.4, which provides a number of bug fixes and the following enhancements: support for Source Specific Multicast (SSM); support for broadcast; single node mode, which allows users to detect a misconfigured local firewall; more precise and rich statistics; rate limiting; duplicate packet detection. BZ# 696747 Users are advised to upgrade to this updated omping package, which resolves these bugs and adds these enhancements. Note that this package is included as a Technology Preview.

Commands:
Chapter 1. Before you begin 1.1. What is Red Hat JBoss Data Virtualization for OpenShift? Red Hat JBoss Data Virtualization for OpenShift is a Red Hat JBoss Data Virtualization (JDV) image that runs in an OpenShift container. It allows you to quickly and easily create, deploy and scale Red Hat JBoss Data Virtualization sessions in a secure environment. 1.2. Version compatibility and support To see which versions of OpenShift and JDV are compatible, click here: OpenShift and Atomic Platform Tested Integrations . The Red Hat JBoss Data Virtualization for OpenShift image is based on Red Hat JBoss Data Virtualization 6.4. There are some differences in functionality between the JDV for OpenShift image and the standalone version of Red Hat JBoss Data Virtualization: Cached results are automatically replicated to every member of the JDV for OpenShift cluster. The JDV for OpenShift image is built on the Red Hat JBoss Enterprise Application Platform for OpenShift image and has inherited its differences. To read about them, click here: Comparison: EAP and EAP for OpenShift Image . Important The Red Hat Data Grid (RHDG) Hot Rod client is built into the JDV image. Hot Rod clients are compatible with specific Data Grid versions. You must install the version of the JDV image that corresponds to the version of your RHDG instances. JDV version JDV image tag Bundled Hot Rod client version RHDG version JDV 6.4.6 1.5 infinispan-client-hotrod-8.5.0 RHDG 7.2 JDV 6.4.7 and later 1.6 infinispan-client-hotrod-9.4.13 RHDG 7.3

Commands:
C.2. Escaping Unsafe Characters Any unsafe characters in the URL need to be escaped, or substituted with a special sequence of characters. For example, a space is an unsafe character that must be represented as %20 within the URL. Thus, the distinguished name o=example.com corporation must be encoded as o=example.com%20corporation . The following table lists the characters that are considered unsafe within URLs and provides the associated escape characters to use in place of the unsafe character: Unsafe Character Escape Characters space %20 < %3c > %3e " %22 # %23 % %25 { %7b } %7d | %7c \ %5c ^ %5e ~ %7e [ %5b ] %5d ` %60

Commands:
Part II. Configuring Business Central settings and properties As an administrator, you can customize the following on the admin Settings page: Roles : Set the home page, priority, and permissions of a role. Groups : Set the home page, priority, and permissions of a group as well as create and delete groups. Users : Create and delete users, add or remove groups and roles from users, and view user permissions. Artifacts : View M2 repository artifacts, upload artifacts, view, and download JAR files. Data Sources : Add, update, or delete data sources and database drivers. Data Sets : Create, modify, or delete data sets. Projects : View and edit project preferences such as file export properties, space properties, default values, and advanced GAV properties. Artifact Repository : Manage artifact repository properties. Languages : Set the Business Central language. Process Administration : Set the default pagination option in Business Central. Process Designer : Set diagram editor properties. SSH Keys : Add or delete SSH keys. Custom Tasks Administration : Enable or disable default service tasks and upload custom service tasks. Dashbuilder Data Transfer : Import and export Dashbuilder data as ZIP files in Business Central. Profiles : Set the workbench profile as Planner and Rules or Full . Archetypes : View, add, validate, set as default, and delete the archetypes. Used as a template when creating a new project in Business Central. Prerequisites Red Hat JBoss Enterprise Application Platform 7.4.14 is installed. For more information, see Red Hat JBoss Enterprise Application Platform 7.4 Installation Guide . Red Hat Process Automation Manager is installed and running. For more information, see Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 . You are logged in to Business Central with the admin user role.

Commands:
3.8. Red Hat Enterprise MRG Red Hat Enterprise MRG's Realtime component includes Tuna , a tool that allows users to both adjust the tunable values their system and view the results of those changes. While it was developed for use with the Realtime component, it can also be used to tune standard Red Hat Enterprise Linux systems. With Tuna, you can adjust or disable unnecessary system activity, including: BIOS parameters related to power management, error detection, and system management interrupts; network settings, such as interrupt coalescing, and the use of TCP; journaling activity in journaling file systems; system logging; whether interrupts and user processes are handled by a specific CPU or range of CPUs; whether swap space is used; and how to deal with out-of-memory exceptions. For more detailed conceptual information about tuning Red Hat Enterprise MRG with the Tuna interface, refer to the "General System Tuning" chapter of the Realtime Tuning Guide . For detailed instructions about using the Tuna interface, refer to the Tuna User Guide . Both guides are available from http://access.redhat.com/site/documentation/Red_Hat_Enterprise_MRG/ .

Commands:
Chapter 3. OpenShift Container Platform versions AMQ Interconnect 1.10 is supported on the OpenShift Container Platform versions listed in the Supported Configurations page. With OpenShift Container Platform 4.9, deprecated APIs are removed from OpenShift, requiring the following actions before upgrading: You must update to AMQ Interconnect 1.10.2 before you can upgrade to OpenShift Container Platform version 4.9. If you attempt to upgrade to OpenShift Container Platform version 4.9 while an earlier version of the AMQ Interconnect Operator is installed in the cluster, an error is displayed. The Red Hat Integration - AMQ Certificate Manager Operator is not supported on OpenShift Container Platform version 4.9 or later. If you attempt to upgrade to OpenShift Container Platform version 4.9 while the AMQ Certificate Manager Operator is installed in the cluster, an error is displayed. Migrating from the Red Hat Integration - AMQ Certificate Manager Operator is described in Deploying AMQ Interconnect on OpenShift .

Commands:
Chapter 4. Technology Previews Technology Preview features included with Streams for Apache Kafka 2.7. Important Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete; therefore, Red Hat does not recommend implementing any Technology Preview features in production environments. This Technology Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about the support scope, see Technology Preview Features Support Scope . 4.1. KRaft mode KRaft mode is available as a technology preview. Currently, the KRaft mode in Streams for Apache Kafka has the following limitations: Downgrading from KRaft mode to using ZooKeeper is not supported. JBOD storage with multiple disks is not supported. Unregistering Kafka nodes removed from the Kafka cluster. 4.2. Kafka Static Quota plugin configuration Use the technology preview of the Kafka Static Quota plugin to set throughput and storage limits on brokers in your Kafka cluster. You can set a byte-rate threshold and storage quotas to put limits on the clients interacting with your brokers. Example Kafka Static Quota plugin configuration client.quota.callback.class= io.strimzi.kafka.quotas.StaticQuotaCallback client.quota.callback.static.produce= 1000000 client.quota.callback.static.fetch= 1000000 client.quota.callback.static.storage.soft= 400000000000 client.quota.callback.static.storage.hard= 500000000000 client.quota.callback.static.storage.check-interval= 5 See Setting limits on brokers using the Kafka Static Quota plugin .

Commands:
client.quota.callback.class= io.strimzi.kafka.quotas.StaticQuotaCallback client.quota.callback.static.produce= 1000000 client.quota.callback.static.fetch= 1000000 client.quota.callback.static.storage.soft= 400000000000 client.quota.callback.static.storage.hard= 500000000000 client.quota.callback.static.storage.check-interval= 5
Chapter 41. Red Hat Enterprise Linux Atomic Host 7.2.3 41.1. Atomic Host OStree update : New Tree Version: 7.2.3 (hash: d620e841861c746b5a296337c1659e6625abfeff96844099d48540fc93717656) Changes since Tree Version 7.2.2-2 (hash: 8b2cf24b420d659179dc866eab1bb341748839204ba56ed46a86218010789e91) New packages : atomic-pkglayer-2016.1.1.gfbf8dde-2.el7 * 41.2. Extras Updated packages : atomic-1.9-4.gitff44c6a.el7 cockpit-0.96-2.el7 docker-1.9.1-25.el7 docker-distribution-2.3.1-1.el7 * dpdk-2.2.0-2.el7 * etcd-2.2.5-1.el7 kubernetes-1.2.0-0.9.alpha1.gitb57e8bd.el7 python-docker-py-1.7.2-1.el7 New packages : runc-0.0.8-1.git4155b68.el7 (Technology Preview) * The asterisk (*) marks packages which are available for Red Hat Enterprise Linux only. 41.2.1. Container Images Updated : Red Hat Enterprise Linux Container Image (rhel7/rhel) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic Kubernetes-controller Container Image (rhel7/kubernetes-controller-mgr) Red Hat Enterprise Linux Atomic Kubernetes-apiserver Container Image (rhel7/kubernetes-apiserver) Red Hat Enterprise Linux Atomic Kubernetes-scheduler Container Image (rhel7/kubernetes-scheduler) New : Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) (Technology Preview) 41.3. New Features Cockpit has been rebased to version 0.96 Cockpit packages that are part of Red Hat Enterprise Linux Atomic Host 7.2.3 include cockpit-bridge , cockpit-shell , cockpit-docker , and cockpit-ostree . Other cockpit-related software can be added to a Red Hat Enterprise Linux Atomic Host via containers (such as the rhel7/cockpit-ws container). Cockpit 0.96 is compatible with docker 1.10. This version fixes bugs with memory leaks, mostly related to DBus, and various navigation and connection issues. Also, you can now limit concurrent authentication similar to ssshd using the MaxStartups setting. New sub-commands added to the atomic CLI The atomic command-line tool for managing Atomic systems and containers now includes the "top", "diff" and "migrate" sub-commands. For more information on the syntax and usage, see https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/cli-reference/#cli_commands . Support for customization of the host system The new atomic-pkglayer packages contain a tool to install debug packages on Atomic Host systems. It is intended only for use inside the Red Hat Enterprise Linux Atomic Tools container image (rhel7/rhel-tools). It provides a mechanism to add RPM packages to an Atomic Host by allowing you to include them in local ostree layers on the existing system. See Installing RPMs on an Atomic Host with atomic-pkglayer for a description of the atomic-pkglayer tool.

Commands:
Preface The Red Hat Enterprise Linux 6.5 Technical Notes list and document the changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications between minor release Red Hat Enterprise Linux 6.4 and minor release Red Hat Enterprise Linux 6.5. For system administrators and others planning Red Hat Enterprise Linux 6.5 upgrades and deployments, the Technical Notes provide a single, organized record of the bugs fixed in, features added to, and Technology Previews included with this new release of Red Hat Enterprise Linux. For auditors and compliance officers, the Red Hat Enterprise Linux 6.5 Technical Notes provide a single, organized source for change tracking and compliance testing. For every user, the Red Hat Enterprise Linux 6.5 Technical Notes provide details of what has changed in this new release. Note The Package Manifest is available as a separate document.

Commands:
C.3. Examples of LDAP URLs Note The LDAP URL format is described in RFC 4516, which is available at http://www.ietf.org/rfc/rfc4516.txt . Example 1 The following LDAP URL specifies a base search for the entry with the distinguished name dc=example,dc=com . Because no port number is specified, the standard LDAP port number ( 389 ) is used. Because no attributes are specified, the search returns all attributes. Because no search scope is specified, the search is restricted to the base entry dc=example,dc=com . Because no filter is specified, the directory uses the default filter ( objectclass=* ). Example 2 The following LDAP URL retrieves the postalAddress attribute of the entry with the DN dc=example,dc=com : Because no search scope is specified, the search is restricted to the base entry dc=example,dc=com . Because no filter is specified, the directory uses the default filter ( objectclass=* ). Example 3 The following LDAP URL retrieves the cn , mail , and telephoneNumber attributes of the entry for Barbara Jensen: Because no search scope is specified, the search is restricted to the base entry cn=Barbara Jensen,dc=example,dc=com . Because no filter is specified, the directory uses the default filter (objectclass=*) . Example 4 The following LDAP URL specifies a search for entries that have the surname Jensen and are at any level under dc=example,dc=com : Because no attributes are specified, the search returns all attributes. Because the search scope is sub , the search encompasses the base entry dc=example,dc=com and entries at all levels under the base entry. Example 5 The following LDAP URL specifies a search for the object class for all entries one level under dc=example,dc=com : Because the search scope is one , the search encompasses all entries one level under the base entry dc=example,dc=com . The search scope does not include the base entry. Because no filter is specified, the directory uses the default filter ( objectclass=* ). Note The syntax for LDAP URLs does not include any means for specifying credentials or passwords. Search requests initiated through LDAP URLs are unauthenticated, unless the LDAP client that supports LDAP URLs provides an authentication mechanism.

Commands:
ldap://ldap.example.com/dc=example,dc=com
ldap://ldap.example.com/dc=example,dc=com?postalAddress
ldap://ldap.example.com/cn=Barbara%20Jensen,dc=example,dc=com?cn,mail,telephoneNumber
ldap://ldap.example.com/dc=example,dc=com??sub?(sn=Jensen)
ldap://ldap.example.com/dc=example,dc=com?objectClass?one
Appendix A. Revision History Revision History Revision 1.1-10 Wed Mar 08 2017 Jiri Herrmann Updates for the 6.9 GA release Revision 1.1-8 Mon December 20 2016 Jiri Herrmann Updates for the 6.9 beta release Revision 1.1-7 Mon May 02 2016 Jiri Herrmann Updates for the 6.8 GA release Revision 1.1-6 Tue Mar 01 2016 Jiri Herrmann Prepared the book for 6.8 beta publication Revision 1.1-5 Thu Oct 08 2015 Jiri Herrmann Cleaned up the Revision History Revision 1.1-4 Mon Jul 13 2015 Jiri Herrmann Version for 6.7 GA release Revision 1.1-03 Thurs Apr 16 2015 Dayle Parker Preparing document for 6.7 Beta publication.

Commands: