mtpti5iD/redhat-docs_dataset huggingface dataset:
Preface Open Java Development Kit (OpenJDK) is a free and open-source implementation of the Java Platform, Standard Edition (Java SE). Eclipse Temurin is available in three LTS versions: OpenJDK 8u, OpenJDK 11u, and OpenJDK 17u. Packages for Eclipse Temurin are available for Microsoft Windows and on multiple Linux x86 Operating Systems including Red Hat Enterprise Linux and Ubuntu.

Commands:
Chapter 6. Recommended resource requirements for Red Hat Advanced Cluster Security Cloud Service The recommended resource guidelines were developed by performing a focused test that created the following objects across a given number of namespaces: 10 deployments, with 3 pod replicas in a sleep state, mounting 4 secrets, 4 config maps 10 services, each one pointing to the TCP/8080 and TCP/8443 ports of one of the deployments 1 route pointing to the first of the services 10 secrets containing 2048 random string characters 10 config maps containing 2048 random string characters During the analysis of results, the number of deployments was identified as a primary factor for increasing of used resources. The number of deployments was used for the estimation of required resources. Additional resources Default resource requirements 6.1. Secured cluster services Secured cluster services contain the following components: Sensor Admission controller Collector Note Collector component is not included on this page. Required resource requirements are listed on the default resource requirements page. 6.1.1. Sensor Sensor monitors your Kubernetes and OpenShift Container Platform clusters. These services currently deploy in a single deployment, which handles interactions with the Kubernetes API and coordinates with Collector. Memory and CPU requirements The following table lists the minimum memory and CPU values required to run Sensor on a secured cluster. Deployments CPU Memory < 25,000 2 cores 10 GiB < 50,000 2 cores 20 GiB 6.1.2. Admission controller The admission controller prevents users from creating workloads that violate policies that you configure. Memory and CPU requirements The following table lists the minimum memory and CPU values required to run the admission controller on a secured cluster. Deployments CPU Memory < 25,000 0.5 cores 300 MiB < 50,000 0.5 cores 600 MiB

Commands:
Chapter 2. Installing Kaoto 2.1. Pre-requisites 2.1.1. Microsoft Visual Studio Code Kaoto ships as a Microsoft Visual Studio Code extension. If you haven't installed VS Code on your manchine yet, please do that now. Visit the download page and follow the installation instructions that apply best for you. 2.1.2. Camel CLI To give you the best user experience we recommend to install the Camel CLI, which offers various functionalities for Camel developers. Please follow the below steps to install it. Install JBang following these instructions . Verify that JBang is working by executing the following from a command shell. This should output the version of installed JBang . jbang version Run the following command from a command shell to install the Camel CLI : jbang app install camel@apache/camel Check if the Camel CLI is working by executing the following from a command shell. This should output the version of the installed Camel CLI . camel version 2.1.3. Citrus Testing If you want to work with the Citrus testing framework, we strongly recommend to install the Citrus JBang plugin. Please follow the below steps to install it. Install JBang following these instructions . Verify that JBang is working by executing the following from a command shell. This should output the version of installed JBang . jbang version Run the following command from a command shell to install the Citrus JBang plugin : jbang app install citrus@citrusframework/citrus Check if the Citrus JBang plugin is working by executing the following from a command shell. This should output the version of the installed Citrus JBang plugin . citrus --version 2.2. Installation Important It is recommended to install the Extension Pack for Apache Camel by Red Hat . It will provide a set of tools to manage, edit, run, and debug Camel integrations in various contexts. The following procedure explains how to install VS Code and other essential extensions required to get started with Kaoto. If you do not have Visual Studio Code installed, install it from here . Launch VS Code. Install the Extension Pack for Apache Camel by Red Hat into your Visual Studio Code instance. To run and debug Camel integrations using VS Code UI, install JBang CLI . Optionally, to run Camel integrations from the command line, install Camel CLI . Important Create and select a workspace folder where all the integration will be stored. Selecting a workspace is important to ensure all required commands will be available and behave correctly.

Commands:
jbang version
jbang app install camel@apache/camel
camel version
jbang version
jbang app install citrus@citrusframework/citrus
citrus --version
Chapter 17. EphemeralStorage schema reference Used in: JbodStorage , KafkaClusterSpec , KafkaNodePoolSpec , ZookeeperClusterSpec The type property is a discriminator that distinguishes use of the EphemeralStorage type from PersistentClaimStorage . It must have the value ephemeral for the type EphemeralStorage . Property Description id Storage identification number. It is mandatory only for storage volumes defined in a storage of type 'jbod'. integer sizeLimit When type=ephemeral, defines the total amount of local storage required for this EmptyDir volume (for example 1Gi). string type Must be ephemeral . string

Commands:
Chapter 3. Set Up Eviction 3.1. About Eviction Eviction is the process of removing entries from memory to prevent running out of memory. Entries that are evicted from memory remain in configured cache stores and the rest of the cluster to prevent permanent data loss. If no cache store is configured, and eviction is enabled, data loss is possible. Red Hat JBoss Data Grid executes eviction tasks by utilizing user threads which are already interacting with the data container. JBoss Data Grid uses a separate thread to prune expired cache entries from the cache. Eviction occurs individually on a per node basis, rather than occurring as a cluster-wide operation. Each node uses an eviction thread to analyze the contents of its in-memory container to determine which entries require eviction. The free memory in the Java Virtual Machine (JVM) is not a consideration during the eviction analysis, even as a threshold to initialize entry eviction. In JBoss Data Grid, eviction provides a mechanism to efficiently remove entries from the in-memory representation of a cache, and removed entries will be pushed to a cache store, if configured. This ensures that the memory can always accommodate new entries as they are fetched and that evicted entries are preserved in the cluster instead of lost. Additionally, eviction strategies can be used as required for your configuration to set up which entries are evicted and when eviction occurs. See Also: Section 4.3, "Eviction and Expiration Comparison" Report a bug

Commands:
16.2. Managing ID Views on the Server Side Important The administrator can only manage ID views on the server side; no configuration is available on Red Hat Enterprise Linux 6 clients. This chapter describes ID views from the client side. For complete information about ID views including the server-side functionality, see the Windows Integration Guide for Red Hat Enterprise Linux 7 . From the server, ID views can be added, modified, or deleted. The administrator can define what ID attributes an ID view should override and to which client hosts it should apply.

Commands:
3.5. Removing a System from an Identity Domain To remove a system from an identity domain, use the realm leave command. The command removes the domain configuration from SSSD and the local system. By default, the removal is performed as the default administrator. For AD, the administrator account is called Administrator ; for IdM, it is called admin . If a different user was used to join to the domain, it might be required to perform the removal as that user. To specify a different user, use the -U option: The command first attempts to connect without credentials, but it prompts for a password if required. Note that when a client leaves a domain, the computer account is not deleted from the directory; the local client configuration is only removed. If you want to delete the computer account, run the command with the --remove option specified. For more information about the realm leave command, see the realm (8) man page.

Commands:
realm leave ad.example.com
realm leave ad.example.com -U ' AD.EXAMPLE.COM\user '
Chapter 4. Distribution selection Eclipse Temurin produces several distributions of Red Hat build of OpenJDK. Red Hat provides support for a subset of these distributions. All Eclipse Temurin distributions of Red Hat build of OpenJDK contain the JDK Flight Recorder (JFR) feature. This feature produces diagnostics and profiling data that can be consumed by other applications, such as JDK Mission Control (JMC). To help select a distribution that is right for your needs, see Platform Coverage for Red Hat Support of Eclipse Temurin (Red Hat Customer Portal) . Additional resources Temurin TM Supported Platforms (Adoptium) Eclipse Mission Control (Adoptium) Introduction to JDK Flight Recorder Red Hat build of OpenJDK Revised on 2024-05-10 09:05:07 UTC

Commands:
Preface Red Hat Ansible automation hub provides a place for Red Hat subscribers to quickly find and use content that is supported by Red Hat and our technology partners to deliver automation solutions for the most demanding environments. The Ansible Galaxy client, ansible-galaxy , manages roles and collections from the command line. To ensure that the ansible-galaxy client uses certified, supported Ansible collections whenever possible, update your ansible.cfg file to use Red Hat automation hub as your primary source of Ansible collections.

Commands:
Preface The Red Hat Enterprise Linux 6.4 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.3 and minor release Red Hat Enterprise Linux 6.4. For system administrators and others planning Red Hat Enterprise Linux 6.4 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.4 Technical Notes provide a single, organized source for change tracking and compliance testing. For every user, the Red Hat Enterprise Linux 6.4 Technical Notes provide details of what has changed in this new release. Note The Package Manifest is available as a separate document.

Commands:
Chapter 3. Creating an IBM Power Virtual Server workspace Important IBM Power Virtual Server using installer-provisioned infrastructure is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . 3.1. Creating an IBM Power Virtual Server workspace Use the following procedure to create an IBM Power Virtual Server workspace. Procedure To create an IBM Power Virtual Server workspace, complete step 1 to step 5 from the IBM Cloud documentation for Creating an IBM Power Virtual Server . After it has finished provisioning, retrieve the 32-character alphanumeric Globally Unique Identifier (GUID) of your new workspace by entering the following command: USD ibmcloud resource service-instance <workspace name> 3.2. steps Installing a cluster on IBM Power Virtual Server with customizations

Commands:
ibmcloud resource service-instance <workspace name>
Chapter 12. Scaling clusters by adding or removing brokers Scaling Kafka clusters by adding brokers can increase the performance and reliability of the cluster. Adding more brokers increases available resources, allowing the cluster to handle larger workloads and process more messages. It can also improve fault tolerance by providing more replicas and backups. Conversely, removing underutilized brokers can reduce resource consumption and improve efficiency. Scaling must be done carefully to avoid disruption or data loss. By redistributing partitions across all brokers in the cluster, the resource utilization of each broker is reduced, which can increase the overall throughput of the cluster. Note To increase the throughput of a Kafka topic, you can increase the number of partitions for that topic. This allows the load of the topic to be shared between different brokers in the cluster. However, if every broker is constrained by a specific resource (such as I/O), adding more partitions will not increase the throughput. In this case, you need to add more brokers to the cluster. Adding brokers when running a multi-node Kafka cluster affects the number of brokers in the cluster that act as replicas. The actual replication factor for topics is determined by settings for the default.replication.factor and min.insync.replicas , and the number of available brokers. For example, a replication factor of 3 means that each partition of a topic is replicated across three brokers, ensuring fault tolerance in the event of a broker failure. Example replica configuration default.replication.factor = 3 min.insync.replicas = 2 When you add or remove brokers, Kafka does not automatically reassign partitions. The best way to do this is using Cruise Control. You can use Cruise Control's add-brokers and remove-brokers modes when scaling a cluster up or down. Use the add-brokers mode after scaling up a Kafka cluster to move partition replicas from existing brokers to the newly added brokers. Use the remove-brokers mode before scaling down a Kafka cluster to move partition replicas off the brokers that are going to be removed. Note When scaling down brokers, you cannot specify which specific pod to remove from the cluster. Instead, the broker removal process starts from the highest numbered pod.

Commands:
default.replication.factor = 3 min.insync.replicas = 2
7.94. jss 7.94.1. RHBA-2015:1315 - jss bug fix and enhancement update Updated jss packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. Java Security Services (JSS) provides an interface between Java Virtual Machine and Network Security Services (NSS). It supports most of the security standards and encryption technologies supported by NSS including communication through SSL/TLS network protocols. JSS is primarily utilized by the Certificate Server as a part of the Identity Management System. Bug Fixes BZ# 1190302 Previously, the HASH_ALGORITHM constant was defined incorrectly. As a consequence, object identifiers (OIDs) for SHA-256, SHA-384, and SHA-512 hash functions were incorrect. With this update, the underlying source code has been modified, and the mentioned OIDs are now correct. BZ# 1190303 Prior to this update, the source code for JSS was missing a condition for validating the key strength for the RC4 software stream cipher. As a consequence, JSS did not validate the key strength properly. A patch has been applied to fix this bug, and JSS now performs key strength validation checks as expected. Enhancement BZ# 1167470 The Tomcat service has been updated to support the Transport Layer Security cryptographic protocol version 1.1 (TLSv1.1) and the Transport Layer Security cryptographic protocol version 1.2 (TLSv1.2) using JSS. Users of jss are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 114. AclRuleTransactionalIdResource schema reference Used in: AclRule The type property is a discriminator that distinguishes use of the AclRuleTransactionalIdResource type from AclRuleTopicResource , AclRuleGroupResource , AclRuleClusterResource . It must have the value transactionalId for the type AclRuleTransactionalIdResource . Property Property type Description type string Must be transactionalId . name string Name of resource for which given ACL rule applies. Can be combined with patternType field to use prefix pattern. patternType string (one of [prefix, literal]) Describes the pattern used in the resource field. The supported types are literal and prefix . With literal pattern type, the resource field will be used as a definition of a full name. With prefix pattern type, the resource name will be used only as a prefix. Default value is literal .

Commands:
Chapter 3. Included features Built on the foundation of Red Hat Enterprise Linux, the RHEL for SAP Solutions subscription includes the following additional components: SAP-specific technical components to support S/4HANA, SAP HANA, and SAP Business Applications. High Availability solutions for S/4HANA, SAP HANA, and SAP Business Applications. RHEL System Roles for SAP, which can be used to automate the configuration of a RHEL system to run SAP workloads. Smart Management and Red Hat Insights for lifecycle management and proactive optimization. SAP HANA tested in-place upgrades and kernel live patching capabilities to maximize SAP business uptime. Update Services for SAP Solutions / Extended Update Support, providing up to four years of support on specified minor releases.

Commands:
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.9.0 3.9.0 0.45.0 0.31 0.15.0 2.5.141 0.6 0.9.0 2.8.0 3.8.0 0.43.0 0.30 0.15.0 2.5.138 0.1 0.8.0 2.7.0 3.7.0 0.40.0 0.28 0.15.0 2.5.137 0.1 0.5.1 2.6.0 3.6.0 0.38.0 0.27 0.14.0 2.5.128 - - 2.5.2 3.5.0 (+3.5.2) 0.36.0 0.26 0.13.0 2.5.123 - - 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 - - - - -

Commands:
Chapter 1. Upgrade overview The upgrade procedure for Red Hat Quay depends on the type of installation you are using. The Red Hat Quay Operator provides a simple method to deploy and manage a Red Hat Quay cluster. This is the preferred procedure for deploying Red Hat Quay on OpenShift. The Red Hat Quay Operator should be upgraded using the Operator Lifecycle Manager (OLM) as described in the section "Upgrading Quay using the Quay Operator". The procedure for upgrading a proof of concept or highly available installation of Red Hat Quay and Clair is documented in the section "Standalone upgrade".

Commands:
22.2.4. Starting and Stopping the Server On the server that is sharing directories via Samba, the smb service must be running. View the status of the Samba daemon with the following command: Start the daemon with the following command: Stop the daemon with the following command: To start the smb service at boot time, use the command: You can also use chkconfig , ntsysv , or the Services Configuration Tool to configure which services start at boot time. Refer to Chapter 19, Controlling Access to Services for details. Note To view active connections to the system, execute the command smbstatus .

Commands:
/sbin/service smb status
/sbin/service smb start
/sbin/service smb stop
/sbin/chkconfig --level 345 smb on
4.4.3. Dynamic Configuration with Base Labeling To override the default base security label in dynamic mode, the <baselabel> option can be configured manually in the XML guest configuration, as shown in this example:

Commands:
<seclabel type='dynamic' model='selinux' relabel='yes'> <baselabel>system_u:system_r:svirt_custom_t:s0</baselabel> <label>system_u:system_r:svirt_custom_t:s0:c87,c520</label> <imagelabel>system_u:object_r:svirt_image_t:s0:c87,c520</imagelabel> </seclabel>
19.4. Managing Password Expiration Limits Password policies are applied at the time a password is changed . So, when a password is set, it conforms to the password policy in effect at that time. If the password policy is changed later, that change is not applied, retroactively, to the password. Setting password expiration periods is configured as part of the group password policy. Creating and editing password policies (including the expiration attribute in the policy) is covered in Section 19.3, "Creating and Editing Password Policies" . With password expiration periods, there are two attributes that are related: The maximum lifetime setting given in the password policy ( --maxlife ) The actual date that the password for a given user expires ( krbPasswordExpiration ) Changing the password expiration time in the password policy does not affect the expiration date for a user, until the user password is changed. If the password expiration date needs to be changed immediately, it can be changed by editing the user entry. To force the expiration date to change, reset the krbPasswordExpiration attribute value for the user. This can only be done using ldapmodify. For example, for a single user: Multiple entries can be edited simultaneously by referencing an LDIF file in the -f option with the ldamodify command. Note If an administrator resets a password, it expires the password and forces the user to update the password. When the user updates the password, it automatically uses the new password policies, including a new expiration date.

Commands:
[bjensen@ipaserver ~]USD ldapmodify -D "cn=Directory Manager" -w secret -h ipaserver.example.com -p 389 -vv dn: uid=jsmith,cn=users,cn=accounts,dc=example,dc=com changetype: modify replace: krbpasswordexpiration krbpasswordexpiration: 20140202203734Z -