mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 6. Technology Previews Technology Preview features included with Streams for Apache Kafka 2.9. 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 . There are no technology previews for Streams for Apache Kafka 2.9 on RHEL.

Commands:
Chapter 2. Understanding custom back ends A custom back end is a storage server, appliance, or configuration that is not yet fully integrated into the Red Hat OpenStack Platform director. Supported Block Storage back ends are already integrated and pre-configured with built-in director files. For example, Red Hat Ceph and single-back end configurations of Dell EMC PS Series, Dell Storage Center, and NetApp appliances. Some integrated storage appliances support only a single-instance back end. For example, with the pre-configured director files for Dell Storage Center, you can only deploy a single back end. If you want to deploy multiple back end instances of this appliance, you need a custom configuration. Although you can manually configure the Block Storage service by directly editing the /etc/cinder/cinder.conf file on the node where the Block Storage service is located, the director overwrites your configuration when you run the openstack overcloud deploy command. For more information, see Deploying the configured back ends . Deploy the Block Storage back end with the director to ensure that your settings persist through overcloud deployments and updates. If your back end configuration is fully integrated you can edit and invoke the packaged environment files. However, for custom back ends, you must write your own environment file. This document includes the annotated /home/stack/templates/custom-env.yaml file that you can edit for your deployment, see Configuration from sample environment file . This sample file is suitable for configuring the Block Storage service to use two NetApp back ends. For more information about environment files, see Including environment files in an overcloud deployment in the Installing and managing Red Hat OpenStack Platform with director guide. 2.1. Requirements The following additional prerequisite conditions must apply to your environment to configure custom Block Storage back ends: If you are using third-party back end appliances, you have configured them as storage repositories. You have deployed the overcloud with director with the instructions in Installing and managing Red Hat OpenStack Platform with director . You have the username and password of an account with elevated privileges. You can use the same stack user account that you created to deploy the overcloud. You have already planned the resulting configuration that you want for the Block Storage back end in /etc/cinder/cinder.conf . 2.2. Understanding the configuration process Configuring the Block Storage service to use custom back ends involves the following steps: Creating the environment file. For more information, see Creating the custom back end environment file . Deploying the configured back ends. For more information, Deploying the configured back ends . Testing the configured back end. For more information, Testing the configured back ends .

Commands:
5.2.2. Protect portmap With IPTables To further restrict access to the portmap service, it is a good idea to add IPTables rules to the server and restrict access to specific networks. Below are two example IPTables commands that allow TCP connections to the portmap service (listening on port 111) from the 192.168.0/24 network and from the localhost (which is necessary for the sgi_fam service used by Nautilus ). All other packets are dropped. To similarly limit UDP traffic, use the following command. Note Refer to Chapter 7, Firewalls for more information about implementing firewalls with IPTables commands.

Commands:
iptables -A INPUT -p tcp -s! 192.168.0.0/24 --dport 111 -j DROP iptables -A INPUT -p tcp -s 127.0.0.1 --dport 111 -j ACCEPT
iptables -A INPUT -p udp -s! 192.168.0.0/24 --dport 111 -j DROP
Chapter 11. Keeping kernel panic parameters disabled in virtualized environments When configuring a Virtual Machine in RHEL 8, do not enable the softlockup_panic and nmi_watchdog kernel parameters, because the Virtual Machine might suffer from a spurious soft lockup. And that should not require a kernel panic. Find the reasons behind this advice in the following sections. 11.1. What is a soft lockup A soft lockup is a situation usually caused by a bug, when a task is executing in kernel space on a CPU without rescheduling. The task also does not allow any other task to execute on that particular CPU. As a result, a warning is displayed to a user through the system console. This problem is also referred to as the soft lockup firing. Additional resources What is a CPU soft lockup? 11.2. Parameters controlling kernel panic The following kernel parameters can be set to control a system's behavior when a soft lockup is detected. softlockup_panic Controls whether or not the kernel will panic when a soft lockup is detected. Type Value Effect Integer 0 kernel does not panic on soft lockup Integer 1 kernel panics on soft lockup By default, on RHEL 8, this value is 0. The system needs to detect a hard lockup first to be able to panic. The detection is controlled by the nmi_watchdog parameter. nmi_watchdog Controls whether lockup detection mechanisms ( watchdogs ) are active or not. This parameter is of integer type. Value Effect 0 disables lockup detector 1 enables lockup detector The hard lockup detector monitors each CPU for its ability to respond to interrupts. watchdog_thresh Controls frequency of watchdog hrtimer , NMI events, and soft or hard lockup thresholds. Default threshold Soft lockup threshold 10 seconds 2 * watchdog_thresh Setting this parameter to zero disables lockup detection altogether. Additional resources Softlockup detector and hardlockup detector Kernel sysctl 11.3. Spurious soft lockups in virtualized environments The soft lockup firing on physical hosts usually represents a kernel or a hardware bug. The same phenomenon happening on guest operating systems in virtualized environments might represent a false warning. Heavy workload on a host or high contention over some specific resource, such as memory, can cause a spurious soft lockup firing because the host might schedule out the guest CPU for a period longer than 20 seconds. When the guest CPU is again scheduled to run on the host, it experiences a time jump that triggers the due timers. The timers also include the hrtimer watchdog that can report a soft lockup on the guest CPU. Soft lockup in a virtualized environment can be false. You must not enable the kernel parameters that trigger a system panic when a soft lockup reports to a guest CPU. Important To understand soft lockups in guests, it is essential to know that the host schedules the guest as a task, and the guest then schedules its own tasks. Additional resources Virtual machine components and their interaction

Commands:
Chapter 2. Installing the Red Hat Ansible Automation Platform operator on Red Hat OpenShift Container Platform Prerequisites You have installed the Red Hat Ansible Automation Platform catalog in Operator Hub. You have created a StorageClass object for your platform and a persistant volume claim (PVC) with ReadWriteMany access mode. See Dyamic Provisioning for details. To run Red Hat OpenShift Container Platform clusters on Amazon Web Services with ReadWriteMany access mode, you must add NFS or other storage. For information on the AWS Elastic Block Store (EBS) or to use the aws-ebs storage class, see Persistent storage using AWS Elastic Block Store . To use multi-attach ReadWriteMany access mode for AWS EBS, see Attaching a volume to multiple instances with Amazon EBS Multi-Attach . Procedure Log in to Red Hat OpenShift Container Platform. Navigate to Operators OperatorHub . Search for the Red Hat Ansible Automation Platform operator and click Install . Select an Update Channel : stable-2.x : installs a namespace-scoped operator, which limits deployments of automation hub and automation controller instances to the namespace the operator is installed in. This is suitable for most cases. The stable-2.x channel does not require administrator privileges and utilizes fewer resources because it only monitors a single namespace. stable-2.x-cluster-scoped : deploys automation hub and automation controller across multiple namespaces in the cluster and requires administrator privileges for all namespaces in the cluster. Select Installation Mode , Installed Namespace , and Approval Strategy . Click Install . The installation process will begin. When installation is complete, a modal will appear notifying you that the Red Hat Ansible Automation Platform operator is installed in the specified namespace. Click View Operator to view your newly installed Red Hat Ansible Automation Platform operator.

Commands:
4.303. spice-vdagent 4.303.1. RHBA-2011:1577 - spice-vdagent bug fix and enhancement update An updated spice-vdagent package that fixes multiple bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The spice-vdagent package provides a SPICE agent for Linux guests. The spice-vdagent package has been upgraded to upstream version 0.8.1, which provides a number of bug fixes and enhancements over the version. (BZ# 722477 ) Note: the system must be rebooted in order for these changes to take effect. Users are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
7.45. dvd+rw-tools 7.45.1. RHBA-2012:1320 - dvd+rw-tools bug fix update Updated dvd+rw-tools packages that fix one bug are now available for Red Hat Enterprise Linux 6. The dvd+rw-tools packages contain a collection of tools to master DVD+RW/+R media. BZ#807474 Prior to this update, the growisofs utility wrote chunks of 32KB and reported an error during the last chunk when burning ISO image files that were not aligned to 32KB. This update allows the written chunk to be smaller than a multiple of 16 blocks. All users of dvd+rw-tools are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Authenticating with the Guest user To explore Developer Hub features, you can skip configuring authentication and authorization. You can configure Developer Hub to log in as a Guest user and access Developer Hub features. 1.1. Authenticating with the Guest user on an Operator-based installation After an Operator-based installation, you can configure Developer Hub to log in as a Guest user and access Developer Hub features. Prerequisites You installed Developer Hub by using the Operator . You added a custom Developer Hub application configuration , and have sufficient permissions to modify it. Procedure To enable the guest user in your Developer Hub custom configuration, edit your Developer Hub application configuration with following content: app-config-rhdh.yaml fragment auth: environment: development providers: guest: dangerouslyAllowOutsideDevelopment: true Verification Go to the Developer Hub login page. To log in with the Guest user account, click Enter in the Guest tile. In the Developer Hub Settings page, your profile name is Guest . You can use Developer Hub features. 1.2. Authenticating with the Guest user on a Helm-based installation On a Helm-based installation, you can configure Developer Hub to log in as a Guest user and access Developer Hub features. Prerequisites You Installed Developer Hub by using the Helm Chart . Procedure To enable the guest user in your Developer Hub custom configuration, configure your Red Hat Developer Hub Helm Chart with following content: Red Hat Developer Hub Helm Chart configuration fragment upstream: backstage: appConfig: app: baseUrl: 'https://{{- include "janus-idp.hostname" . }}' auth: environment: development providers: guest: dangerouslyAllowOutsideDevelopment: true Verification Go to the Developer Hub login page. To log in with the Guest user account, click Enter in the Guest tile. In the Developer Hub Settings page, your profile name is Guest . You can use Developer Hub features.

Commands:
auth: environment: development providers: guest: dangerouslyAllowOutsideDevelopment: true
upstream: backstage: appConfig: app: baseUrl: 'https://{{- include "janus-idp.hostname" . }}' auth: environment: development providers: guest: dangerouslyAllowOutsideDevelopment: true
2.43. RHEA-2011:0611 - new package: subscription-manager New subscription-manager packages that provide GUI and command line tools for the new Subscription Manager system are now available for Red Hat Enterprise Linux 6. The new Subscription Management tooling will allow users to understand the specific products which have been installed on their machines, and the specific subscriptions which their machines are consuming. This enhancement update adds new subscription-manager packages to Red Hat Enterprise Linux 6. (BZ# 567635 ) All users should install these newly-released packages, which add this enhancement.

Commands:
7.115. logrotate 7.115.1. RHBA-2015:1293 - logrotate bug fix and enhancement update Updated logrotate packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The logrotate utility simplifies the administration of multiple log files, allowing the automatic rotation, compression, removal, and mailing of log files. Bug Fixes BZ# 625034 When the logrotate utility attempted to write its status file while insufficient disk space was available, logrotate wrote only part of the status file and stopped. When the disk space became free again, and log rotate attempted to read its records, logrotate terminated unexpectedly. This bug has been fixed, and logrotate no longer crashes in the aforementioned scenario. BZ# 722209 Previously, the daily cronjob of logrotate redirected all error messages to the /dev/null device file, thus suppressing all the relevant information for troubleshooting. With this update, all error messages containing detailed error reports are mailed to the root user. In addition, the /etc/cron.daily/logrotate file has been marked as a configuration file in RPM. BZ# 1012485 Previously, the /etc/cron.daily/logrotate file had incorrect permissions set. This update changes the permissions to 0700, and /etc/cron.daily/logrotate now conforms to Red Hat security policy GEN003080. BZ# 1117189 The logrotate utility incorrectly deleted data files alphabetically instead of based on their age when the when the "-%d-%m-%Y" date format was used. This update sorts files returned by the glob() function according to the date extension. As a result, when the aforementioned date format is used, the oldest log is now removed as expected. Enhancements BZ# 1125769 The logrotate "olddir" directive now automatically creates a directory if it is not already present. BZ# 1047899 This update adds logrotate features for "size" directive parsing and "maxsize" directive. Users of logrotate are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 2. Deleting an OpenShift Dedicated cluster on AWS As cluster owner, you can delete your OpenShift Dedicated clusters. 2.1. Deleting your cluster You can delete your OpenShift Dedicated cluster in Red Hat OpenShift Cluster Manager. Prerequisites You logged in to OpenShift Cluster Manager . You created an OpenShift Dedicated cluster. Procedure From OpenShift Cluster Manager , click on the cluster you want to delete. Select Delete cluster from the Actions drop-down menu. Type the name of the cluster highlighted in bold, then click Delete . Cluster deletion occurs automatically.

Commands:
4.56. expat 4.56.1. RHSA-2012:0731 - Moderate: expat security update Updated expat packages that fix two security issues are now available for Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Expat is a C library written by James Clark for parsing XML documents. Security Fixes CVE-2012-0876 A denial of service flaw was found in the implementation of hash arrays in Expat. An attacker could use this flaw to make an application using Expat consume an excessive amount of CPU time by providing a specially-crafted XML file that triggers multiple hash function collisions. To mitigate this issue, randomization has been added to the hash function to reduce the chance of an attacker successfully causing intentional collisions. CVE-2012-1148 A memory leak flaw was found in Expat. If an XML file processed by an application linked against Expat triggered a memory re-allocation failure, Expat failed to free the previously allocated memory. This could cause the application to exit unexpectedly or crash when all available memory is exhausted. All Expat users should upgrade to these updated packages, which contain backported patches to correct these issues. After installing the updated packages, applications using the Expat library must be restarted for the update to take effect.

Commands:
Chapter 149. StrimziPodSetSpec schema reference Used in: StrimziPodSet Property Description selector Selector is a label query which matches all the pods managed by this StrimziPodSet . Only matchLabels is supported. If matchExpressions is set, it will be ignored. For more information, see the external documentation for meta/v1 labelselector . LabelSelector pods The Pods managed by this StrimziPodSet. For more information, see the external documentation for core/v1 pods . Map array

Commands:
Chapter 55. Browse Component Available as of Camel version 1.3 The Browse component provides a simple BrowsableEndpoint which can be useful for testing, visualisation tools or debugging. The exchanges sent to the endpoint are all available to be browsed. 55.1. URI format Where someName can be any string to uniquely identify the endpoint. 55.2. Options The Browse component has no options. The Browse endpoint is configured using URI syntax: with the following path and query parameters: 55.2.1. Path Parameters (1 parameters): Name Description Default Type name Required A name which can be any string to uniquely identify the endpoint String 55.2.2. Query Parameters (4 parameters): Name Description Default Type bridgeErrorHandler (consumer) Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN/ERROR level and ignored. false boolean exceptionHandler (consumer) To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions, that will be logged at WARN/ERROR level and ignored. ExceptionHandler exchangePattern (consumer) Sets the default exchange pattern when creating an exchange. ExchangePattern synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean 55.3. Sample In the route below, we insert a browse: component to be able to browse the Exchanges that are passing through: from("activemq:order.in").to("browse:orderReceived").to("bean:processOrder"); We can now inspect the received exchanges from within the Java code: private CamelContext context; public void inspectRecievedOrders() { BrowsableEndpoint browse = context.getEndpoint("browse:orderReceived", BrowsableEndpoint.class); List<Exchange> exchanges = browse.getExchanges(); // then we can inspect the list of received exchanges from Java for (Exchange exchange : exchanges) { String payload = exchange.getIn().getBody(); // do something with payload } } 55.4. See Also Configuring Camel Component Endpoint Getting Started

Commands:
browse:someName[?options]
browse:name
from("activemq:order.in").to("browse:orderReceived").to("bean:processOrder");
private CamelContext context; public void inspectRecievedOrders() { BrowsableEndpoint browse = context.getEndpoint("browse:orderReceived", BrowsableEndpoint.class); List<Exchange> exchanges = browse.getExchanges(); // then we can inspect the list of received exchanges from Java for (Exchange exchange : exchanges) { String payload = exchange.getIn().getBody(); // do something with payload } }
Chapter 3. Inviting users and managing rights Note The invite feature is only available for Pro and Enterprise customers. In order to share the workload of administering your application programming interfaces (APIs), you may wish to invite team members from your organization to access the 3scale Admin Portal. The instructions below describe how to give access rights to the 3scale Admin Portal, to one or more team members. With users , we refer to the members of your team. The 3scale Admin Portal has two types of users: Admins Have full access to all areas and services, and can invite other members if your plan allows it. Members Have limited access to areas of the product, for example, Analytics, the Developer Portal if you are an enterprise customer, also to services. If you create a new 3scale user from a single sign-on (SSO) integration, this user has the member role by default, regardless of the SSO token content. 3scale does not map its roles to SSO roles. 3.1. Navigate to user administration To see the list of users of your 3scale installation, follow these steps in the Admin Portal page: In the navigation bar, click the gear icon located in the upper right of the window. Navigate to Users > Listing from the left side menu. 3.2. Send an invitation From the list of users, you can invite a new team member. To send the invitation: Click on the Invite user link, located on the upper-right side above the list. Enter the email address of the person you want to invite and click Send . As a confirmation of the sending, on the upper-right corner of the window you will see a message: Invitation was successfully sent. . An invitation email will be sent to the address you entered. If the email does not arrive, make sure it was not marked as spam in the recipient's email account. Additionally, you can find the list and status of sent invitations in Users > Invitations . 3.3. Accept the invitation Your new administrator or member must click the link in the invitation email and complete the form to complete the process. Once the form is submitted, their account will be activated. 3.4. Give new users rights There are two main type of rights you can give to members of your team: By area Through analytics, billing, or developer administration. By service Choose which services to give access to members amongst all of your services. Note: This feature is only available for enterprise customers. To give a new user rights, edit the new user by selecting them from the user menu and clicking on Edit . You have the following user roles: Changing their rights to Admin will give them full access to control the Admin Portal. Changing their rights to Member will give you the option of choosing which areas and services the team member has access to. As Member , select an area to list all the available services related to said area. Giving access to certain areas of the Admin Portal will give members access only to the equivalent API: Developer accounts - Applications Gives access to the Account management API. Analytics Gives access to the Analytics API. Billing Gives access to the Billing API.

Commands: