mtpti5iD/redhat-docs_dataset huggingface dataset:
Release notes Red Hat Developer Hub 1.3 Release notes for Red Hat Developer Hub 1.3 Red Hat Customer Content Services

Commands:
import { lightTheme } from &#39;./lightTheme&#39;; // some custom theme import { UnifiedThemeProvider } from &#39;@backstage/theme&#39;; export const lightThemeProvider = ({ children }: { children: ReactNode }) =&gt; ( &lt;UnifiedThemeProvider theme={lightTheme} children={children} /&gt; );
dynamicPlugins: frontend: example.my-custom-theme-plugin: themes: - id: light # &lt;1&gt; title: Light variant: light icon: someIconReference importName: lightThemeProvider
spec: application: replicas: 2 # &lt;1&gt; imagePullSecrets: # &lt;2&gt; - my-secret-name image: quay.io/my/my-rhdh:latest # &lt;3&gt;
spec: deployment: patch: spec: replicas: 2 # &lt;1&gt; imagePullSecrets: # &lt;2&gt; - name: my-secret-name template: metadata: labels: my: true spec: containers: - name: backstage-backend image: quay.io/my/my-rhdh:latest # &lt;3&gt;
dynamicPlugins: cache: # -- Spec of the dynamic plugins root volume claim. # Note that, by default, this is set to use the default storage class, if available in the cluster. volumeClaimSpec: accessModes: - ReadWriteOnce resources: requests: storage: 5Gi storageClassName: null
-- Test pod parameters test: # -- Whether to enable the test-connection pod used for testing the Release using `helm test`. enabled: true image: # -- Test connection pod image registry registry: quay.io # -- Test connection pod image repository. Note that the image needs to have both the `sh` and `curl` binaries in it. repository: curl/curl # -- Test connection pod image tag. Note that the image needs to have both the `sh` and `curl` binaries in it. tag: latest
auditLog: # -- Spec of the audit log volume claim. # Note that, by default, this is set to use the default storage class, if available in the cluster. volumeClaimSpec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi storageClassName: null
import { unstable_ClassNameGenerator as ClassNameGenerator } from &#39;@mui/material/className&#39;; ClassNameGenerator.configure(componentName =&gt; { return componentName.startsWith(&#39;v5-&#39;) ? componentName : `v5-USD{componentName}`; })
3.2. SELinux Contexts for Processes Use the ps -eZ command to view the SELinux context for processes. For example: Open a terminal, such as Applications System Tools Terminal . Run the passwd command. Do not enter a new password. Open a new tab, or another terminal, and run the ps -eZ | grep passwd command. The output is similar to the following: In the first tab/terminal, press Ctrl+C to cancel the passwd application. In this example, when the passwd application (labeled with the passwd_exec_t type) is executed, the user's shell process transitions to the passwd_t domain. Remember that the type defines a domain for processes, and a type for files. Use the ps -eZ command to view the SELinux contexts for running processes. The following is a truncated example of the output, and may differ on your system: The system_r role is used for system processes, such as daemons. Type Enforcement then separates each domain.

Commands:
unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 13212 pts/1 00:00:00 passwd
system_u:system_r:dhcpc_t:s0 1869 ? 00:00:00 dhclient system_u:system_r:sshd_t:s0-s0:c0.c1023 1882 ? 00:00:00 sshd system_u:system_r:gpm_t:s0 1964 ? 00:00:00 gpm system_u:system_r:crond_t:s0-s0:c0.c1023 1973 ? 00:00:00 crond system_u:system_r:kerneloops_t:s0 1983 ? 00:00:05 kerneloops system_u:system_r:crond_t:s0-s0:c0.c1023 1991 ? 00:00:00 atd
Chapter 2. Installing Red Hat build of OpenJDK 11 for Microsoft Windows with the archive This procedure describes how to manually install Red Hat build of OpenJDK 11 for Microsoft Windows using the archive. Procedure Download the archive of Red Hat build of OpenJDK 11 for Microsoft Windows. Extract the contents of an archive to a directory of your choice. Note Extracting the contents of an archive to a directory path that does not contain spaces is recommended. Update the PATH as below: Add the bin directory contained in your Red Hat build of OpenJDK 11 for Microsoft Windows installation path to the %PATH% environment variable: If the path contains spaces, use the shortened path name. Restart Command Prompt to reload the environment variables. Verify the Red Hat build of OpenJDK 11 for Microsoft Windows is successfully installed, run java -version command in a command prompt and you must get the following output: The %JAVA_HOME% environment variable must also be set to use some developer tools. Set the %JAVA_HOME% environment variable as follows: Open Command Prompt as an administrator. Set the value of the environment variable to your Red Hat build of OpenJDK 11 for Microsoft Windows installation path: If the path contains spaces, use the shortened path name. Restart Command Prompt to reload the environment variables.

Commands:
C:\> setx /m PATH "%PATH%;C:\Progra~1\RedHat\java-11-openjdk-11.0.1.13-1\bin"
openjdk version "11.0.3-redhat" 2019-04-16 LTS OpenJDK Runtime Environment 18.9 (build 11.0.3-redhat+7-LTS) OpenJDK 64-Bit Server VM 18.9 (build 11.0.3-redhat+7-LTS, mixed mode)
C:\> setx /m JAVA_HOME "C:\Progra~1\RedHat\java-11-openjdk-11.0.1.13-1"
Chapter 1. Key features AMQ Streams simplifies the process of running Apache Kafka in an OpenShift cluster. This guide is intended as a starting point for building an understanding of AMQ Streams. The guide introduces some of the key concepts behind Kafka, which is central to AMQ Streams, explaining briefly the purpose of Kafka components. Configuration points are outlined, including options to secure and monitor Kafka. A distribution of AMQ Streams provides the files to deploy and manage a Kafka cluster, as well as example files for configuration and monitoring of your deployment . A typical Kafka deployment is described, as well as the tools used to deploy and manage Kafka. 1.1. Kafka capabilities The underlying data stream-processing capabilities and component architecture of Kafka can deliver: Microservices and other applications to share data with extremely high throughput and low latency Message ordering guarantees Message rewind/replay from data storage to reconstruct an application state Message compaction to remove old records when using a key-value log Horizontal scalability in a cluster configuration Replication of data to control fault tolerance Retention of high volumes of data for immediate access 1.2. Kafka use cases Kafka's capabilities make it suitable for: Event-driven architectures Event sourcing to capture changes to the state of an application as a log of events Message brokering Website activity tracking Operational monitoring through metrics Log collection and aggregation Commit logs for distributed systems Stream processing so that applications can respond to data in real time 1.3. How AMQ Streams supports Kafka AMQ Streams provides container images and operators for running Kafka on OpenShift. AMQ Streams operators are purpose-built with specialist operational knowledge to effectively manage Kafka on OpenShift. Operators simplify the process of: Deploying and running Kafka clusters Deploying and running Kafka components Configuring access to Kafka Securing access to Kafka Upgrading Kafka Managing brokers Creating and managing topics Creating and managing users

Commands:
5.3.7. /proc/net/ This directory provides a comprehensive look at various networking parameters and statistics. Each directory and virtual file within this directory describes aspects of the system's network configuration. Below is a partial list of the /proc/net/ directory: arp - Lists the kernel's ARP table. This file is particularly useful for connecting a hardware address to an IP address on a system. atm/ directory - The files within this directory contain Asynchronous Transfer Mode (ATM) settings and statistics. This directory is primarily used with ATM networking and ADSL cards. dev - Lists the various network devices configured on the system, complete with transmit and receive statistics. This file displays the number of bytes each interface has sent and received, the number of packets inbound and outbound, the number of errors seen, the number of packets dropped, and more. dev_mcast - Lists Layer2 multicast groups on which each device is listening. igmp - Lists the IP multicast addresses which this system joined. ip_conntrack - Lists tracked network connections for machines that are forwarding IP connections. ip_tables_names - Lists the types of iptables in use. This file is only present if iptables is active on the system and contains one or more of the following values: filter , mangle , or nat . ip_mr_cache - Lists the multicast routing cache. ip_mr_vif - Lists multicast virtual interfaces. netstat - Contains a broad yet detailed collection of networking statistics, including TCP timeouts, SYN cookies sent and received, and much more. psched - Lists global packet scheduler parameters. raw - Lists raw device statistics. route - Lists the kernel's routing table. rt_cache - Contains the current routing cache. snmp - List of Simple Network Management Protocol (SNMP) data for various networking protocols in use. sockstat - Provides socket statistics. tcp - Contains detailed TCP socket information. tr_rif - Lists the token ring RIF routing table. udp - Contains detailed UDP socket information. unix - Lists UNIX domain sockets currently in use. wireless - Lists wireless interface data.

Commands:
3.5.3. Emulated Storage Devices The host emulates a range of storage devices that can be presented to virtual machines. Each type of storage device is appropriate for specific use cases. Choice between different types of storage devices allows for maximum flexibility and compatibility with guest operating systems. virtio-scsi virtio-scsi is the recommended paravirtualized storage device for guests using large numbers of disks, or advanced storage features such as TRIM. virtio-blk virtio-blk is a paravirtualized storage device suitable for exposing image files to guests. virtio-blk can provide the best disk I/O performance for virtual machines, but has fewer features than virtio-scsi. IDE IDE is recommended for legacy guests that do not support virtio drivers. IDE performance is lower than virtio-scsi or virtio-blk, but it is widely compatible with different systems. CD-ROM ATAPI CD-ROMs and virtio-scsi CD-ROMs are available for presenting ISO files or the host CD-ROM drive to guests. virtio-scsi CD-ROMs can be used with guests that have the virtio-scsi driver installed. ATAPI CD-ROMs offer wider compatibility but lower performance. USB mass storage devices and floppy disks Emulated USB mass storage devices and floppy disks are available when removable media is required. USB mass storage devices are preferable to floppy disks due to their larger capacity.

Commands:
1.2. Per-Invocation Flags Per-invocation flags can be used with data grids in Red Hat JBoss Data Grid to specify behavior for each cache call. Per-invocation flags facilitate the implementation of potentially time saving optimizations. Report a bug 1.2.1. Per-Invocation Flag Functions The putForExternalRead() method in Red Hat JBoss Data Grid's Cache API uses flags internally. This method can load a JBoss Data Grid cache with data loaded from an external resource. To improve the efficiency of this call, JBoss Data Grid calls a normal put operation passing the following flags: The ZERO_LOCK_ACQUISITION_TIMEOUT flag: JBoss Data Grid uses an almost zero lock acquisition time when loading data from an external source into a cache. The FAIL_SILENTLY flag: If the locks cannot be acquired, JBoss Data Grid fails silently without throwing any lock acquisition exceptions. The FORCE_ASYNCHRONOUS flag: If clustered, the cache replicates asynchronously, irrespective of the cache mode set. As a result, a response from other nodes is not required. Combining the flags above significantly increases the efficiency of the operation. The basis for this efficiency is that putForExternalRead calls of this type are used because the client can retrieve the required data from a persistent store if the data cannot be found in memory. If the client encounters a cache miss, it retries the operation. For a detailed list of all flags available for JBoss Data Grid are available in the JBoss Data Grid API Documentation here: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Grid/6.6/html/API_Documentation/files/api/org/infinispan/context/Flag.html Report a bug 1.2.2. Configure Per-Invocation Flags To use per-invocation flags in Red Hat JBoss Data Grid, add the required flags to the advanced cache via the withFlags() method call. Example 1.1. Configuring Per-Invocation Flags Note The called flags only remain active for the duration of the cache operation. To use the same flags in multiple invocations within the same transaction, use the withFlags() method for each invocation. If the cache operation must be replicated onto another node, the flags are also carried over to the remote nodes. Report a bug 1.2.3. Per-Invocation Flags Example In a use case for Red Hat JBoss Data Grid, where a write operation, such as put() , must not return the value, the IGNORE_RETURN_VALUES flag is used. This flag prevents a remote lookup (to get the value) in a distributed environment, which in turn prevents the retrieval of the undesired, potential, value. Additionally, if the cache is configured with a cache loader, this flag prevents the value from being loaded from its cache store. Example 1.2. Using the IGNORE_RETURN_VALUES Flag Report a bug

Commands:
Cache cache = cache.getAdvancedCache() .withFlags(Flag.SKIP_CACHE_STORE, Flag.CACHE_MODE_LOCAL) .put("local", "only");
Cache cache = cache.getAdvancedCache() .withFlags(Flag.IGNORE_RETURN_VALUES) .put("local", "only")
10.5.63. Cache Directives A number of commented cache directives are supplied by the default Apache HTTP Server configuration file. In most cases, uncommenting these lines by removing the hash mark ( # ) from the beginning of the line is sufficient. The following, however, is a list of some of the more important cache-related directives. CacheEnable - Specifies whether the cache is a disk, memory, or file descriptor cache. By default CacheEnable configures a disk cache for URLs at or below / . CacheRoot - Specifies the name of the directory containing cached files. The default CacheRoot is the /var/httpd/proxy/ directory. CacheSize - Specifies how much space the cache can use in kilobytes. The default CacheSize is 5 KB. The following is a list of some of the other common cache-related directives. CacheMaxExpire - Specifies how long HTML documents are retained (without a reload from the originating Web server) in the cache. The default is 24 hours ( 86400 seconds). CacheLastModifiedFactor - Specifies the creation of an expiry (expiration) date for a document which did not come from its originating server with its own expiry set. The default CacheLastModifiedFactor is set to 0.1 , meaning that the expiry date for such documents equals one-tenth of the amount of time since the document was last modified. CacheDefaultExpire - Specifies the expiry time in hours for a document that was received using a protocol that does not support expiry times. The default is set to 1 hour ( 3600 seconds). NoProxy - Specifies a space-separated list of subnets, IP addresses, domains, or hosts whose content is not cached. This setting is most useful for Intranet sites.

Commands:
5.317. sysfsutils 5.317.1. RHBA-2012:1453 - sysfsutils bug fix update Updated sysfsutils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The sysfsutils packages provide a suite of daemons to manage access to remote directories and authentication mechanisms. The sysfsutils suite provides an NSS and PAM interface toward the system and a pluggable backend system to connect to multiple different account sources. It is also the basis to provide client auditing and policy services for projects like FreeIPA. Bug Fix BZ# 671554 Prior to this update, sysfs directories were not closed as expected. As a consequence, the libsysfs library could leak memory in long running programs that frequently opened and closed sysfs directories. This update modifies the underlying code to close sysfs directories as expected. All users of sysfsutils are advised to upgrade to these updated packages, which fix this bug.

Commands:
7.97. krb5 7.97.1. RHBA-2015:1410 - krb5 bug fix and enhancement update Updated krb5 packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. Kerberos is a networked authentication system that allows clients and servers to authenticate to each other with the help of a trusted third party, the Kerberos key distribution center. Bug Fixes BZ# 1075656 Prior to this update, if the Kerberos principal keys were expired, the password change request did not take into account the FAST framework settings for password change requests. Consequently, the pre-auth methods, which require FAST, could not be used for user authentication. This update modifies krb5 to correctly use FAST armor in the password change messages, and the pre-auth methods can be used for user authentication. BZ# 1154130 Previously, after the user set up incremental propagation between a KDC master and slave, an attempt to perform a full synchronization failed with an error message. A patch has been applied to fix this problem, and full synchronization no longer fails after the user sets up incremental propagation between a KDC master and slave. Enhancement BZ# 1170272 This update adds the LocalAuth plug-in API to krb5. SSSD can leverage LocalAuth to allow seamless authentication of Active Directory (AD) users to Red Hat Enterprise Linux Identity Management (IdM) clients. Users of krb5 are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 11. Kafka clients The kafka-clients JAR file contains the Kafka Producer and Consumer APIs together with the Kafka AdminClient API. The Producer API allows applications to send data to a Kafka broker. The Consumer API allows applications to consume data from a Kafka broker. The AdminClient API provides functionality for managing Kafka clusters, including topics, brokers, and other components. 11.1. Adding Kafka clients as a dependency to your Maven project This procedure shows you how to add the AMQ Streams Java clients as a dependency to your Maven project. Prerequisites A Maven project with an existing pom.xml . Procedure Add the Red Hat Maven repository to the <repositories> section of your pom.xml file. Add the clients to the <dependencies> section of your pom.xml file. Build your Maven project.

Commands:
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <!-- ... --> <repositories> <repository> <id>redhat-maven</id> <url>https://maven.repository.redhat.com/ga/</url> </repository> </repositories> <!-- ... --> </project>
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <!-- ... --> <dependencies> <dependency> <groupId>org.apache.kafka</groupId> <artifactId>kafka-clients</artifactId> <version>2.7.0.redhat-00005</version> </dependency> </dependencies> <!-- ... --> </project>
8.194. ql2500-firmware 8.194.1. RHBA-2014:1453 - ql2500-firmware bug fix and enhancement update Updated ql2500-firmware package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The ql2500-firmware package provides the firmware required to run the QLogic 2500 Series of mass storage adapters. Note The ql2500-firmware package has been upgraded to upstream version 7.03.00, which provides a number of bug fixes and enhancements over the version. (BZ# 1076497 ) All users of QLogic 2500 Series Fibre Channel adapters are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
13.2. Understanding Virtual Disks Red Hat Virtualization features Preallocated (thick provisioned) and Sparse (thin provisioned) storage options. Preallocated A preallocated virtual disk allocates all the storage required for a virtual machine up front. For example, a 20 GB preallocated logical volume created for the data partition of a virtual machine will take up 20 GB of storage space immediately upon creation. Sparse A sparse allocation allows an administrator to define the total storage to be assigned to the virtual machine, but the storage is only allocated when required. For example, a 20 GB thin provisioned logical volume would take up 0 GB of storage space when first created. When the operating system is installed it may take up the size of the installed file, and would continue to grow as data is added up to a maximum of 20 GB size. You can view a virtual disk's ID in Storage Disks . The ID is used to identify a virtual disk because its device name (for example, /dev/vda0 ) can change, causing disk corruption. You can also view a virtual disk's ID in /dev/disk/by-id . You can view the Virtual Size of a disk in Storage Disks and in the Disks tab of the details view for storage domains, virtual machines, and templates. The Virtual Size is the total amount of disk space that the virtual machine can use. It is the number that you enter in the Size(GB) field when you create or edit a virtual disk. You can view the Actual Size of a disk in the Disks tab of the details view for storage domains and templates. This is the amount of disk space that has been allocated to the virtual machine so far. Preallocated disks show the same value for Virtual Size and Actual Size . Sparse disks may show different values, depending on how much disk space has been allocated. Note When creating a Cinder virtual disk, the format and type of the disk are handled internally by Cinder and are not managed by Red Hat Virtualization. The possible combinations of storage types and formats are described in the following table. Table 13.1. Permitted Storage Combinations Storage Format Type Note NFS Raw Preallocated A file with an initial size that equals the amount of storage defined for the virtual disk, and has no formatting. NFS Raw Sparse A file with an initial size that is close to zero, and has no formatting. NFS QCOW2 Sparse A file with an initial size that is close to zero, and has QCOW2 formatting. Subsequent layers will be QCOW2 formatted. SAN Raw Preallocated A block device with an initial size that equals the amount of storage defined for the virtual disk, and has no formatting. SAN QCOW2 Sparse A block device with an initial size that is much smaller than the size defined for the virtual disk (currently 1 GB), and has QCOW2 formatting for which space is allocated as needed (currently in 1 GB increments).

Commands: