mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 20. Application plans Application Plans define the different sets of access rights you might want to allow for consumers of your API. These can determine anything from rate limits, which methods or resources are accessible and which features are enabled. 20.1. How to create an application plan By default, when your 3scale account is created, you are given two plans: Basic and Unlimited. You can keep and edit these, or create your own. You can create as many plans as you need. To create a new application plan, follow these steps: Navigate to [Your_product_name] > Applications > Application Plans . Click the Create Application Plan button. On the Create Application Plan page, enter a name and a system name (system names must be unique) for your new plan. If you want to require applications to get approval before they can access your API, select the Applications require approval? check box. Once you have created a plan, you can provision rate limits and set up paid plans . 20.2. Setting up a default application plan After you have created all your plans, you can select a default plan for when people sign up to register their applications. To select a default application plan: Navigate to [Your_product_name] > Applications > Application Plans . From the drop-down list under Default Plan , select a plan. If you do not indicate a default application plan, when a new user signs up to get access to your API, they will not be created an application by default. In other words, the user will not be able to get access to your API.

Commands:
2.3. Enabling the Required Repositories To install packages signed by Red Hat you must register the target system to the Content Delivery Network. Then, use an entitlement from your subscription pool and enable the required repositories. Enabling the Required Repositories Using Subscription Manager Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted: # subscription-manager register Locate the relevant subscription pools and note down the pool identifiers: # subscription-manager list --available Use the pool identifiers to attach the required subscriptions: # subscription-manager attach --pool= pool_id When a system is attached to a subscription pool with multiple repositories, only the main repository is enabled by default. Others are available, but disabled. Enable any additional repositories: # subscription-manager repos --enable= repository Ensure that all packages currently installed are up to date: # dnf upgrade --nobest Note For versions of Red Hat Enterprise Linux earlier than 8, use the command yum update instead of dnf upgrade : # yum update See also Cannot perform yum update on my RHV manager (ansible conflict)

Commands:
subscription-manager register
subscription-manager list --available
subscription-manager attach --pool= pool_id
subscription-manager repos --enable= repository
dnf upgrade --nobest
yum update
Chapter 11. Component details The following table shows the component versions for each Streams for Apache Kafka release. Note Components like the operators, console, and proxy only apply to using Streams for Apache Kafka on OpenShift. Streams for Apache Kafka Apache Kafka Strimzi Operators Kafka Bridge Oauth Cruise Control Console Proxy 2.7.0 3.7.0 0.40.0 0.28 0.15.0 2.5.128 0.1 0.5.1 2.6.0 3.6.0 0.38.0 0.27 0.14.0 2.5.128 - - 2.5.1 3.5.0 0.36.0 0.26 0.13.0 2.5.123 - - 2.5.0 3.5.0 0.36.0 0.26 0.13.0 2.5.123 - - 2.4.0 3.4.0 0.34.0 0.25.0 0.12.0 2.5.112 - - 2.3.0 3.3.1 0.32.0 0.22.3 0.11.0 2.5.103 - - 2.2.2 3.2.3 0.29.0 0.21.5 0.10.0 2.5.103 - - 2.2.1 3.2.3 0.29.0 0.21.5 0.10.0 2.5.103 - - 2.2.0 3.2.3 0.29.0 0.21.5 0.10.0 2.5.89 - - 2.1.0 3.1.0 0.28.0 0.21.4 0.10.0 2.5.82 - - 2.0.1 3.0.0 0.26.0 0.20.3 0.9.0 2.5.73 - - 2.0.0 3.0.0 0.26.0 0.20.3 0.9.0 2.5.73 - - 1.8.4 2.8.0 0.24.0 0.20.1 0.8.1 2.5.59 - - 1.8.0 2.8.0 0.24.0 0.20.1 0.8.1 2.5.59 - - 1.7.0 2.7.0 0.22.1 0.19.0 0.7.1 2.5.37 - - 1.6.7 2.6.3 0.20.1 0.19.0 0.6.1 2.5.11 - - 1.6.6 2.6.3 0.20.1 0.19.0 0.6.1 2.5.11 - - 1.6.5 2.6.2 0.20.1 0.19.0 0.6.1 2.5.11 - - 1.6.4 2.6.2 0.20.1 0.19.0 0.6.1 2.5.11 - - 1.6.0 2.6.0 0.20.0 0.19.0 0.6.1 2.5.11 - - 1.5.0 2.5.0 0.18.0 0.16.0 0.5.0 - - - 1.4.1 2.4.0 0.17.0 0.15.2 0.3.0 - - - 1.4.0 2.4.0 0.17.0 0.15.2 0.3.0 - - - 1.3.0 2.3.0 0.14.0 0.14.0 0.1.0 - - - 1.2.0 2.2.1 0.12.1 0.12.2 - - - - 1.1.1 2.1.1 0.11.4 - - - - - 1.1.0 2.1.1 0.11.1 - - - - - 1.0 2.0.0 0.8.1 - - - - - Note Strimzi 0.26.0 contains a Log4j vulnerability. The version included in the product has been updated to depend on versions that do not contain the vulnerability.

Commands:
Chapter 1. Introduction to examples Featured Chapter 2, Skupper Hello World A minimal multi-service HTTP application deployed across sites. Chapter 8, Patient Portal A database-backed web application deployed across sites. Chapter 9, Trade Zoo A Kafka-based trading application deployed across sites. Messaging Chapter 3, Accessing ActiveMQ using Skupper Access an ActiveMQ message broker. Chapter 7, Accessing Kafka using Skupper Access a Kafka cluster. Protocols Chapter 5, Accessing an FTP server using Skupper Access an FTP server. Chapter 6, iPerf Perform real-time network throughput measurements using iPerf3. Other Chapter 4, Skupper Camel Integration Example Accessing private on-prem data from Camel

Commands:
Chapter 2. Additional release notes Release notes for additional related components and products not included in the core OpenShift Container Platform 4.17 release notes are available in the following documentation. Important The following release notes are for downstream Red Hat products only; upstream or community release notes for related products are not included. A AWS Load Balancer Operator B Builds for Red Hat OpenShift C cert-manager Operator for Red Hat OpenShift Cluster Observability Operator (COO) Compliance Operator Custom Metrics Autoscaler Operator D Red Hat Developer Hub Operator E External DNS Operator F File Integrity Operator H Hosted control planes K Kube Descheduler Operator L Logging M Migration Toolkit for Containers (MTC) N Network Observability Operator Network-bound Disk Encryption (NBDE) Tang Server Operator O OpenShift API for Data Protection (OADP) Red Hat OpenShift Dev Spaces Red Hat OpenShift distributed tracing platform Red Hat OpenShift GitOps Red Hat OpenShift Local (Upstream CRC documentation) Red Hat OpenShift Pipelines OpenShift sandboxed containers Red Hat OpenShift Serverless Red Hat OpenShift Service Mesh 2.x Red Hat OpenShift Service Mesh 3.x Red Hat OpenShift support for Windows Containers Red Hat OpenShift Virtualization Red Hat build of OpenTelemetry P Power monitoring for Red Hat OpenShift R Run Once Duration Override Operator S Secondary Scheduler Operator for Red Hat OpenShift Security Profiles Operator

Commands:
1.5. Other General Directory Resources The following publications have very detailed and useful information about directories, LDAP, and LDIF: RFC 2849: The LDAP Data Interchange Format (LDIF) Technical Specification, http://www.ietf.org/rfc/rfc2849.txt RFC 2251: Lightweight Directory Access Protocol (v3), http://www.ietf.org/rfc/rfc2251.txt Understanding and Deploying LDAP Directory Services . T. Howes, M. Smith, G. Good, Macmillan Technical Publishing, 1999. All of the Red Hat Directory Server documentation, available at https://access.redhat.com/documentation/en-us/red_hat_directory_server , also contain high-level concepts about using LDAP and managing directory services, as well as Directory Server-specific information.

Commands:
Chapter 4. Configuring the Overcloud after Creation The creation process results in a fully operational Overcloud with IPv6 network. However, the Overcloud requires some post-creation configuration. 4.1. Creating the Overcloud Tenant Network The Overcloud requires a IPv6-based Tenant network for instances. Source the overcloudrc file and create an initial Tenant network in neutron . For example: This creates a basic neutron network called default . Confirm the created network with neutron net-list: 4.2. Creating the Overcloud Public Network This scenario configured the node interfaces to use the External network. However, you still need to create this network on the Overcloud so that we can provide network access. This creates a network called public provides an allocation pool of over 65000 IPv6 addresses for our instances. Create a router to route instance traffic to the External network.

Commands:
source ~/overcloudrc neutron net-create default --provider:physical_network datacentre --provider:network_type vlan --provider:segmentation_id 101 neutron subnet-create default 2001:db8:fd00:6000::/64 --ipv6-ra-mode slaac --ipv6-address-mode slaac --ip-version 6 --name default
neutron net-list
neutron net-create public --router:external --provider:physical_network datacentre --provider:network_type vlan --provider:segmentation_id 100 neutron subnet-create public 2001:db8:0:2::/64 --ip-version 6 --gateway 2001:db8::1 --allocation-pool start=2001:db8:0:2::2,end=2001:db8:0:2::ffff --ip-version 6 --ipv6_address_mode=slaac --ipv6_ra_mode=slaac
neutron router-create public-router neutron router-gateway-set public-router public
Chapter 8. Verifying your IdM and AD trust configuration using IdM Healthcheck Learn more about identifying issues with IdM and an Active Directory trust in Identity Management (IdM) by using the Healthcheck tool. 8.1. IdM and AD trust Healthcheck tests The Healthcheck tool includes several tests for testing the status of your Identity Management (IdM) and Active Directory (AD) trust. To see all trust tests, run ipa-healthcheck with the --list-sources option: You can find all tests under the ipahealthcheck.ipa.trust source: IPATrustAgentCheck This test checks the SSSD configuration when the machine is configured as a trust agent. For each domain in /etc/sssd/sssd.conf where id_provider=ipa ensure that ipa_server_mode is True . IPATrustDomainsCheck This test checks if the trust domains match SSSD domains by comparing the list of domains in sssctl domain-list with the list of domains from ipa trust-find excluding the IPA domain. IPATrustCatalogCheck This test resolves resolves an AD user, Administrator@REALM . This populates the AD Global catalog and AD Domain Controller values in sssctl domain-status output. For each trust domain look up the user with the id of the SID + 500 (the administrator) and then check the output of sssctl domain-status <domain> --active-server to ensure that the domain is active. IPAsidgenpluginCheck This test verifies that the sidgen plugin is enabled in the IPA 389-ds instance. The test also verifies that the IPA SIDGEN and ipa-sidgen-task plugins in cn=plugins,cn=config include the nsslapd-pluginEnabled option. IPATrustAgentMemberCheck This test verifies that the current host is a member of cn=adtrust agents,cn=sysaccounts,cn=etc,SUFFIX . IPATrustControllerPrincipalCheck This test verifies that the current host is a member of cn=adtrust agents,cn=sysaccounts,cn=etc,SUFFIX . IPATrustControllerServiceCheck This test verifies that the current host starts the ADTRUST service in ipactl. IPATrustControllerConfCheck This test verifies that ldapi is enabled for the passdb backend in the output of net conf list. IPATrustControllerGroupSIDCheck This test verifies that the admins group's SID ends with 512 (Domain Admins RID). IPATrustPackageCheck This test verifies that the trust-ad package is installed if the trust controller and AD trust are not enabled. Note Run these tests on all IdM servers when trying to find an issue. 8.2. Screening the trust with the Healthcheck tool Follow this procedure to run a standalone manual test of an Identity Management (IdM) and Active Directory (AD) trust health check using the Healthcheck tool. The Healthcheck tool includes many tests, therefore, you can shorten the results by: Excluding all successful test: --failures-only Including only trust tests: --source=ipahealthcheck.ipa.trust Procedure To run Healthcheck with warnings, errors and critical issues in the trust, enter: Successful test displays empty brackets: Additional resources See man ipa-healthcheck .

Commands:
ipa-healthcheck --list-sources
ipa-healthcheck --source=ipahealthcheck.ipa.trust --failures-only
ipa-healthcheck --source=ipahealthcheck.ipa.trust --failures-only []
5.6. Advanced Storage Technologies Although everything presented in this chapter so far has dealt only with single hard drives directly-attached to a system, there are other, more advanced options that you can explore. The following sections describe some of the more common approaches to expanding your mass storage options. 5.6.1. Network-Accessible Storage Combining network and mass storage technologies can result in a great deal more flexibility for system administrators. There are two benefits that are possible with this type of configuration: Consolidation of storage Simplified administration Storage can be consolidated by deploying high-performance servers with high-speed network connectivity and configured with large amounts of fast storage. Given an appropriate configuration, it is possible to provide storage access at speeds comparable to locally-attached storage. Furthermore, the shared nature of such a configuration often makes it possible to reduce costs, as the expenses associated with providing centralized, shared storage can be less than providing the equivalent storage for each and every client. In addition, free space is consolidated, instead of being spread out (and not widely usable) across many clients. Centralized storage servers can also make many administrative tasks easier. For instance, monitoring free space is much easier when the storage to be monitored exists on a centralized storage server. Backups can be vastly simplified using a centralized storage server. Network-aware backups for multiple clients are possible, but require more work to configure and maintain. There are a number of different networked storage technologies available; choosing one can be difficult. Nearly every operating system on the market today includes some means of accessing network-accessible storage, but the different technologies are incompatible with each other. What is the best approach to determining which technology to deploy? The approach that usually provides the best results is to let the built-in capabilities of the client decide the issue. There are a number of reasons for this: Minimal client integration issues Minimal work on each client system Low per-client cost of entry Keep in mind that any client-related issues are multiplied by the number of clients in your organization. By using the clients' built-in capabilities, you have no additional software to install on each client (incurring zero additional cost in software procurement). And you have the best chance for good support and integration with the client operating system. There is a downside, however. This means that the server environment must be up to the task of providing good support for the network-accessible storage technologies required by the clients. In cases where the server and client operating systems are one and the same, there is normally no issue. Otherwise, it will be necessary to invest time and effort in making the server "speak" the clients' language. However, often this trade-off is more than justified.

Commands:
14.2. Enabling Spring Cache Support (Library Mode) Spring's cache support can be enabled, for both Spring3 and Spring4, either through the xml file or programmatically in the application. Declarative Configuration To enable Spring support declaratively perform the following steps: Add <cache:annotation-driven/> to the xml file. This line enables the standard spring annotations to be used by the application. Define a cache manager using the <infinispan:embedded-cache-manager ... /> . The following example demonstrates these changes: Example 14.4. Sample Declarative Configuration Programmatic Configuration To enable Spring support programmatically perform the following steps: Add the @EnableCaching annotation to the Spring configuration class in use. Define a method returning a SpringEmbeddedCacheManager annotated with @Bean . The following code snippet highlights these changes: Example 14.5. Sample Programmatic Configuration Report a bug

Commands:
<?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:infinispan="http://www.infinispan.org/schemas/spring" xmlns:cache="http://www.springframework.org/schema/cache" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/cache http://www.springframework.org/schema/cache/spring-cache.xsd http://www.infinispan.org/schemas/spring http://www.infinispan.org/schemas/infinispan-spring.xsd"> [...] <cache:annotation-driven/> <infinispan:embedded-cache-manager configuration="classpath:/path/to/cache-config.xml"/> [...]
import org.infinispan.configuration.cache.Configuration; import org.infinispan.configuration.cache.ConfigurationBuilder; import org.infinispan.eviction.EvictionStrategy; import org.infinispan.manager.DefaultCacheManager; import org.infinispan.spring.provider.SpringEmbeddedCacheManager; import org.springframework.cache.annotation.EnableCaching; import org.springframework.context.annotation.Bean; [...] @org.springframework.context.annotation.Configuration @EnableCaching public class Config { [...] @Bean public SpringEmbeddedCacheManager cacheManager() throws Exception { Configuration config = new ConfigurationBuilder() .eviction() .strategy(EvictionStrategy.LRU) .maxEntries(150) .build(); return SpringEmbeddedCacheManager(new DefaultCacheManager(config)); } [...]
Part III. Configuring and viewing your data After you add your OpenShift Container Platform and Microsoft Azure integrations, cost management displays the cost and usage data that is related to running your OpenShift Container Platform clusters on Azure. You might have to wait up to 24 hours for your data to display. On the cost management Overview page, your cost data is in the OpenShift and Infrastructure tabs. To toggle through different views of your cost data, select Perspective . You can also use the global navigation menu to view additional details about your costs by cloud provider. You can also use the global navigation menu to view additional details about your costs by cloud provider. To add other types of integrations, see: Integrating OpenShift Container Platform data into cost management Integrating Amazon Web Services (AWS) data into cost management Integrating Google Cloud data into cost management Integrating Oracle Cloud data into cost management

Commands:
5.189. metacity 5.189.1. RHBA-2012:0994 - metacity bug fix update Updated metacity packages that fix one bug are now available for Red Hat Enterprise Linux 6. Metacity is a window manager that integrates with the GNOME desktop. BZ# 802916 Previously, password dialog boxes did not automatically have the focus after they were opened and could remain covered by a full-screen window. With this update, password dialog boxes are automatically given the focus so that they are raised above full-screen windows, and the problem no longer occurs. All users of metacity are advised to upgrade to these updated packages, which fix this bug.

Commands:
5.2. Run Time Errors and Warnings Runtime errors and warnings occur when the SystemTap instrumentation has been installed and is collecting data on the system. WARNING: Number of errors: N , skipped probes: M Errors and skipped probes occurred during this run. Both N and M are the counts of the number of probes that were not executed due to conditions such as too much time required to execute event handlers over an interval of time. division by 0 The script code performed an invalid division. aggregate element not found A statistics extractor function other than @count was invoked on an aggregate that has not had any values accumulated yet. This is similar to a division by zero. aggregation overflow An array containing aggregate values contains too many distinct key pairs at this time. MAXNESTING exceeded Too many levels of function call nesting were attempted. The default nesting of function calls allowed is 10. MAXACTION exceeded The probe handler attempted to execute too many statements in the probe handler. The default number of actions allowed in a probe handler is 1000. kernel/user string copy fault at ADDR The probe handler attempted to copy a string from kernel or user-space at an invalid address ( ADDR ). pointer dereference fault There was a fault encountered during a pointer dereference operation such as a target variable evaluation.

Commands:
Setting up an NVIDIA GPU for a virtual machine in Red Hat Virtualization Red Hat Virtualization 4.4 How to configure a virtual machine in Red Hat Virtualization to use a dedicated GPU or vGPU. Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract This document describes how to use a host with a graphics processing unit (GPU) to run virtual machines in Red Hat Virtualization for graphics-intensive tasks and software that cannot run without a GPU.

Commands:
12.2.2. Using the ntsysv Utility The ntsysv utility is a command-line application with a simple text user interface to configure which services are to be started in selected runlevels. To start the utility, type ntsysv at a shell prompt as root . Figure 12.2. The ntsysv utility The utility displays the list of available services (the services from the /etc/rc.d/init.d/ directory) along with their current status and a description obtainable by pressing F1 . For a list of used symbols and an explanation of their meaning, see Table 12.3, "Possible service states" . Table 12.3. Possible service states Symbol Description [*] The service is enabled. [ ] The service is disabled. 12.2.2.1. Enabling and Disabling a Service To enable a service, navigate through the list using the Up and Down arrows keys, and select it with the Spacebar . An asterisk ( * ) appears in the brackets. To disable a service, navigate through the list using the Up and Down arrows keys, and toggle its status with the Spacebar . An asterisk ( * ) in the brackets disappears. Once you are done, use the Tab key to navigate to the Ok button, and confirm the changes by pressing Enter . Keep in mind that ntsysv does not actually start or stop the service. If you need to start or stop the service immediately, use the service command as described in Section 12.3.2, "Starting a Service" . 12.2.2.2. Selecting Runlevels By default, the ntsysv utility only affects the current runlevel. To enable or disable services for other runlevels, as root , run the command with the additional --level option followed by numbers from 0 to 6 representing each runlevel you want to configure: ntsysv --level runlevels For example, to configure runlevels 3 and 5, type:

Commands:
~]# ntsysv --level 35