mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. OpenShift Serverless overview OpenShift Serverless provides Kubernetes native building blocks that enable developers to create and deploy serverless, event-driven applications on OpenShift Container Platform. OpenShift Serverless is based on the open source Knative project , which provides portability and consistency for hybrid and multi-cloud environments by enabling an enterprise-grade serverless platform. Note Because OpenShift Serverless releases on a different cadence from OpenShift Container Platform, the OpenShift Serverless documentation is now available as separate documentation sets for each minor version of the product. The OpenShift Serverless documentation is available at https://docs.openshift.com/serverless/ . Documentation for specific versions is available using the version selector dropdown, or directly by adding the version to the URL, for example, https://docs.openshift.com/serverless/1.28 . In addition, the OpenShift Serverless documentation is also available on the Red Hat Portal at https://access.redhat.com/documentation/en-us/red_hat_openshift_serverless/ . For additional information about the OpenShift Serverless life cycle and supported platforms, refer to the Platform Life Cycle Policy . 2.1. Additional resources Extending the Kubernetes API with custom resource definitions Managing resources from custom resource definitions What is serverless?

Commands:
Chapter 5. Model Object Extensions 5.1. Model Object Extensions Teiid Designer in conjunction with JBoss Data Virtualization provides an extensible framework to define custom properties for model objects other than what is defined in the metamodel. These custom property values are added to your VDB and included in your runtime metadata. This additional metadata is available to use in your custom translators for both source query manipulation as well as adjusting your result set data being returned. Teiid Designer introduces a new Model Extension Definition (MED) framework that will replace the EMF based Model Extension metamodel. This MED framework provides the following improvements: Eliminate need for separate EMF metamodel. Simpler approach including reduction of extendable metamodels and metamodel objects (Relational, Web Services, XML Document, User Defined Functions) and replacing EMF terminology with basic object types. Allows metamodels to be extended by multiple MEDs. MEDs are stored in models so no added dependency needed in VDB. Also see: Section 10.8.1, "Managing Model Object Extensions" and Section E.9, "Model Extension Definition Editor" .

Commands:
16.3. Map Reduce Example The following example uses a word count application to demonstrate MapReduce and its distributed task abilities. This example assumes we have a mapping of the key sentence stored on JBoss Data Grid nodes. Key is a String. Each sentence is a String. All words that appear in all sentences must be counted. Example 16.6. Implementing the Distributed Task In this second example, a Collator is defined, which will transform the result of MapReduceTask Map<KOut,VOut> into a String that is returned to a task invoker. The Collator is a transformation function applied to a final result of MapReduceTask. Example 16.7. Defining the Collator Report a bug

Commands:
public class WordCountExample { /** * In this example replace c1 and c2 with * real Cache references * * @param args */ public static void main(String[] args) { Cache c1 = null; Cache c2 = null; c1.put("1", "Hello world here I am"); c2.put("2", "Infinispan rules the world"); c1.put("3", "JUDCon is in Boston"); c2.put("4", "JBoss World is in Boston as well"); c1.put("12","WildFly"); c2.put("15", "Hello world"); c1.put("14", "Infinispan community"); c2.put("15", "Hello world"); c1.put("111", "Infinispan open source"); c2.put("112", "Boston is close to Toronto"); c1.put("113", "Toronto is a capital of Ontario"); c2.put("114", "JUDCon is cool"); c1.put("211", "JBoss World is awesome"); c2.put("212", "JBoss rules"); c1.put("213", "JBoss division of RedHat "); c2.put("214", "RedHat community"); MapReduceTask<String, String, String, Integer> t = new MapReduceTask<String, String, String, Integer>(c1); t.mappedWith(new WordCountMapper()) .reducedWith(new WordCountReducer()); Map<String, Integer> wordCountMap = t.execute(); } static class WordCountMapper implements Mapper<String,String,String,Integer> { /** The serialVersionUID */ private static final long serialVersionUID = -5943370243108735560L; @Override public void map(String key, String value, Collector<String, Integer> collector) { StringTokenizer tokens = new StringTokenizer(value); for(String token : value.split("\\w")) { collector.emit(token, 1); } } } static class WordCountReducer implements Reducer<String, Integer> { /** The serialVersionUID */ private static final long serialVersionUID = 1901016598354633256L; @Override public Integer reduce(String key, Iterator<Integer> iter) { int sum = 0; while (iter.hasNext()) { Integer i = (Integer) iter.next(); sum += i; } return sum; } } }
MapReduceTask<String, String, String, Integer> t = new MapReduceTask<String, String, String, Integer>(cache); t.mappedWith(new WordCountMapper()).reducedWith(new WordCountReducer()); String mostFrequentWord = t.execute( new Collator<String,Integer,String>() { @Override public String collate(Map<String, Integer> reducedResults) { String mostFrequent = ""; int maxCount = 0; for (Entry<String, Integer> e : reducedResults.entrySet()) { Integer count = e.getValue(); if(count > maxCount) { maxCount = count; mostFrequent = e.getKey(); } } return mostFrequent; } }); System.out.println("The most frequent word is " + mostFrequentWord);
3.5.3.2. Rules for Passive Connections The rules for passive connections assign the appropriate firewall mark to connections coming in from the Internet to the floating IP for the service on a wide range of ports - 10,000 to 20,000. Warning If you are limiting the port range for passive connections, you must also configure the VSFTP server to use a matching port range. This can be accomplished by adding the following lines to /etc/vsftpd.conf : pasv_min_port=10000 pasv_max_port=20000 You must also control the address that the server displays to the client for passive FTP connections. In a NAT routed LVS system, add the following line to /etc/vsftpd.conf to override the real server IP address to the VIP, which is what the client sees upon connection. For example: pasv_address=n.n.n.n Replace n.n.n.n with the VIP address of the LVS system. For configuration of other FTP servers, consult the respective documentation. This range should be a wide enough for most situations; however, you can increase this number to include all available non-secured ports by changing 10000:20000 in the commands below to 1024:65535 . The following iptables commands have the net effect of assigning any traffic addressed to the floating IP on the appropriate ports a firewall mark of 21, which is in turn recognized by IPVS and forwarded appropriately: /sbin/iptables -t mangle -A PREROUTING -p tcp -d n.n.n.n /32 --dport 21 -j MARK --set-mark 21 /sbin/iptables -t mangle -A PREROUTING -p tcp -d n.n.n.n /32 --dport 10000:20000 -j MARK --set-mark 21 In the iptables commands, n.n.n.n should be replaced with the floating IP for the FTP virtual server defined in the VIRTUAL SERVER subsection of Piranha Configuration Tool . Warning The commands above take effect immediately, but do not persist through a reboot of the system. To ensure network packet filter settings are restored after a reboot, see Section 3.6, "Saving Network Packet Filter Settings" Finally, you need to be sure that the appropriate service is set to activate on the proper runlevels. For more on this, refer to Section 2.1, "Configuring Services on the LVS Routers" .

Commands:
Chapter 11. Run Red Hat JBoss Data Grid in Library Mode (Multi-Node Setup) 11.1. Sharing JGroup Channels Red Hat JBoss Data Grid offers an easy to use form of clustering using JGroups as the network transport. As a result, JGroups manages the initial operations required to form a cluster for JBoss Data Grid. All caches created from a single CacheManager share the same JGroups channel by default. This JGroups channel is used to multiplex replication/distribution messages. In the following example, all three caches used the same JGroups channel: Example 11.1. Shared JGroups Channel Substitute USDLOCATION with the CacheManager's location. Report a bug

Commands:
EmbeddedCacheManager cm = USDLOCATION Cache<Object, Object> cache1 = cm.getCache("replSyncCache"); Cache<Object, Object> cache2 = cm.getCache("replAsyncCache"); Cache<Object, Object> cache3 = cm.getCache("invalidationSyncCache");
Chapter 4. Updating Red Hat build of OpenJDK 8 for Microsoft Windows using the archive Red Hat build of OpenJDK 8 for Microsoft Windows can be manually update using the archive. Procedure Download the archive of Red Hat build of OpenJDK 8 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. On Command Prompt, update 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 8 for Microsoft Windows installation path: If the path contains spaces, use the shortened path name. Restart Command Prompt to reload the environment variables. Set the value of PATH variable if it is not set already: Restart Command Prompt to reload the environment variables. Verify that java -version works without supplying the full path.

Commands:
C:\> setx /m JAVA_HOME "C:\Progra~1\RedHat\java-8-openjdk-1.8.0_181"
C:\> setx -m PATH "%PATH%;%JAVA_HOME%\bin";
C:\> java -version java version "1.8.0_181" Java(TM) SE Runtime Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
Chapter 3. New Features Automation Hub collection redhat.sap_install version 1.2.1 has the following new features: New sap_ha_pacemaker_cluster role for performing all HA related configuration changes in one role, using the ha_cluster Linux System Role and its enhanced features Improve SID and instance checking in role sap_hana_install , so the role will return successfully if a HANA system with the desired SID and instance number is detected (idempotency) Enable modifying SELinux file labels for SAP directories during preconfiguration and HANA installation, using the selinux Linux System Role New sap_swpm role for performing certain SWPM based installations

Commands:
7.301. gzip 7.301.1. RHBA-2013:0862 - gzip bug fix update Updated gzip packages that fix one bug are now available for Red Hat Enterprise Linux 6. The gzip packages provide the GNU gzip data compression program. Bug Fix BZ# 963195 The O_NONBLOCK flag was recently added to the open() system call. As a consequence gzip did not prevent opening of parity (PAR) and Ots File List (OFL) files that are managed by the SGI Data Migration Facility (DMF). Processing of such files resulted in gzip aborts or corrupted output files. With this update, if an attempt to read a file with the O_NONBLOCK flag fails with the EAGAIN error code, the file is re-read without O_NONBLOCK. The gzip utility no longer aborts or produce corrupted output files in this situation. Users of gzip are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Eclipse Temurin 11 - Extended Lifecycle Support Phase 1 Important The 11.0.25 release in October 2024 was the last release of Eclipse Temurin 11 from Red Hat in the full support phase of the lifecycle. The full support phase for Eclipse Temurin 11 ended on 31 October 2024. See the Eclipse Temurin Life Cycle and Support Policy for details. From November 2024 onward, Red Hat will provide extended lifecycle support phase 1 (ELS‐1) support for new releases of Eclipse Temurin 11 until 31 October 2027. Access to ELS requires an OpenJDK ELS subscription. OpenJDK ELS is not included in any other ELS subscription. For more information about product lifecycle phases and available support levels, see Life Cycle Phases .

Commands:
Chapter 3. Upgrading the CLI and sites Upgrading sites requires the latest version of the Skupper CLI. Note Update all sites to ensure the same version of Service Interconnect is running across your service network. You can expect some minimal downtime during the update process. Procedure Upgrade the skupper CLI: Upgrade each site: Set the context to the site you want to upgrade. Run the upgrade command: This command is not suitable for sites created using the Operator. See the Installation for instructions about upgrading Operator based sites. Note Upgrading Technology Preview Podman sites is not supported. Podman sites were introduced as a Technology Preview feature in version 1.4, however you cannot upgrade these sites to the fully supported Podman sites available in later releases. To workaround this, recreate the Podman site and recreate links and services.

Commands:
dnf upgrade skupper-cli
skupper update
Chapter 31. JmxPrometheusExporterMetrics schema reference Used in: CruiseControlSpec , KafkaClusterSpec , KafkaConnectSpec , KafkaMirrorMaker2Spec , KafkaMirrorMakerSpec , ZookeeperClusterSpec The type property is a discriminator that distinguishes use of the JmxPrometheusExporterMetrics type from other subtypes which may be added in the future. It must have the value jmxPrometheusExporter for the type JmxPrometheusExporterMetrics . Property Description type Must be jmxPrometheusExporter . string valueFrom ConfigMap entry where the Prometheus JMX Exporter configuration is stored. For details of the structure of this configuration, see the Prometheus JMX Exporter . ExternalConfigurationReference

Commands:
16.2.2. Reporting on Disk Quotas Creating a disk usage report entails running the repquota utility. Example 16.5. Output of repquota command For example, the command repquota /home produces this output: To view the disk usage report for all (option -a ) quota-enabled file systems, use the command: While the report is easy to read, a few points should be explained. The -- displayed after each user is a quick way to determine whether the block or inode limits have been exceeded. If either soft limit is exceeded, a + appears in place of the corresponding - ; the first - represents the block limit, and the second represents the inode limit. The grace columns are normally blank. If a soft limit has been exceeded, the column contains a time specification equal to the amount of time remaining on the grace period. If the grace period has expired, none appears in its place.

Commands:
*** Report for user quotas on device /dev/mapper/VolGroup00-LogVol02 Block grace time: 7days; Inode grace time: 7days Block limits File limits User used soft hard grace used soft hard grace ---------------------------------------------------------------------- root -- 36 0 0 4 0 0 kristin -- 540 0 0 125 0 0 testuser -- 440400 500000 550000 37418 0 0
repquota -a
Chapter 12. Accessing S3-compatible object storage with self-signed certificates To use object storage solutions or databases that are deployed in an OpenShift cluster that uses self-signed certificates, you must configure OpenShift AI to trust the cluster's certificate authority (CA). Each namespace has a ConfigMap called kube-root-ca.crt that contains the CA certificates of the internal API Server. Use the following steps to configure OpenShift AI to trust the certificates issued by kube-root-ca.crt . Alternatively, you can add a custom CA bundle by using the OpenShift console, as described in Adding a CA bundle . Prerequisites You have cluster administrator privileges for your OpenShift cluster. You have downloaded and installed the OpenShift command-line interface (CLI). See Installing the OpenShift CLI . You have an object storage solution or database deployed in your OpenShift cluster. Procedure In a terminal window, log in to the OpenShift CLI as shown in the following example: Run the following command to fetch the current OpenShift AI trusted CA configuration and store it in a new file: Add the cluster's kube-root-ca.crt ConfigMap to the OpenShift AI trusted CA configuration: Update the OpenShift AI trusted CA configuration to trust certificates issued by the certificate authorities in kube-root-ca.crt : Verification You can successfully deploy components that are configured to use object storage solutions or databases that are deployed in the OpenShift cluster. For example, a pipeline server that is configured to use a database deployed in the cluster starts successfully. Note You can verify your new certificate configuration by following the steps in the OpenShift AI fraud detection tutorial. Run the script to install local object storage buckets and create connections, and then enable data science pipelines. For more information about running the script to install local object storage buckets, see Running a script to install local object storage buckets and create connections . For more information about enabling data science pipelines, see Enabling data science pipelines .

Commands:
login api.<cluster_name>.<cluster_domain>:6443 --web
get dscinitializations.dscinitialization.opendatahub.io default-dsci -o json | jq -r '.spec.trustedCABundle.customCABundle' > /tmp/my-custom-ca-bundles.crt
get configmap kube-root-ca.crt -o jsonpath="{['data']['ca\.crt']}" >> /tmp/my-custom-ca-bundles.crt
patch dscinitialization default-dsci --type='json' -p='[{"op":"replace","path":"/spec/trustedCABundle/customCABundle","value":"'"USD(awk '{printf "%s\\n", USD0}' /tmp/my-custom-ca-bundles.crt)"'"}]'
probe::stap.cache_add_mod Name probe::stap.cache_add_mod - Adding kernel instrumentation module to cache Synopsis stap.cache_add_mod Values dest_path the path the .ko file is going to (incl filename) source_path the path the .ko file is coming from (incl filename) Description Fires just before the file is actually moved. Note: if moving fails, cache_add_src and cache_add_nss will not fire.

Commands:
4.138. libhugetlbfs 4.138.1. RHEA-2011:1685 - libhugetlbfs bug fix and enhancement update Updated libhugetlbfs packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The libhugetlbfs packages provide the library and utilities that are used to interact with the Linux hugetlbfs file system to make large pages available to applications in a transparent manner. The libhugetlbfs packages have been upgraded to upstream version 2.12, which provide a number of bug fixes and add additional administrator support for using large pages over the version. The libhugetlbfs library and utilities now increase overall system performance, especially for large memory systems. The packages are synchronized with kernel support. (BZ# 630171 ) All users of libhugetlbfs are advised to upgrade to these updated packages which fix these bugs and add this enhancement.

Commands:
Chapter 5. Network Security in a Virtualized Environment 5.1. Network Security Overview In almost all situations, the network is the only way to access systems, applications, and management interfaces. As networking plays such a critical role in the management of virtualized systems and the availability of their hosted applications, it is very important to ensure that the network channels both to and from the virtualized systems are secure. Securing the network allows administrators to control access and protect sensitive data from information leaks and tampering.

Commands:
3.5.4. Modifying Group Settings When a group already exists and you need to specify any of the options now, use the groupmod command. The logic of using groupmod is identical to groupadd as well as its syntax: To change the group ID of a given group, use the groupmod command in the following way: Note Find all files owned by the specified GID in system and change their owner. Do the same for Access Control List (ACL) referring to the GID. It is recommended to check there are no running processes as they keep running with the old GID. To change the name of the group, run the following on the command line. The name of the group will be changed from GROUP_NAME to NEW_GROUP_NAME name. Example 3.21. Changing a Group's Name The following command changes the name of the group schoolmates to crowd :

Commands:
groupmod option(s) groupname
groupmod -g GID_NEW which_group_to_edit
groupmod -n new_groupname groupname
~]# groupmod -n crowd schoolmates
Chapter 131. XML Tokenize The XML Tokenize language is a built-in language in camel-xml-jaxp , which is a truly XML-aware tokenizer that can be used with the Split EIP as the conventional Tokenize to efficiently and effectively tokenize XML documents.. XML Tokenize is capable of not only recognizing XML namespaces and hierarchical structures of the document but also more efficiently tokenizing XML documents than the conventional Tokenize language. 131.1. Dependencies When using xtokenize with Red Hat build of Camel Spring Boot make sure to use the following Maven dependency to have support for auto configuration: <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-xml-jaxp-starter</artifactId> </dependency> Additional dependency In order to use this component, an additional dependency is required as follows: <dependency> <groupId>org.codehaus.woodstox</groupId> <artifactId>woodstox-core-asl</artifactId> <version>4.4.1</version> </dependency> or <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-stax-starter</artifactId> </dependency> 131.2. XML Tokenizer Options The XML Tokenize language supports 4 options, which are listed below. Name Default Java Type Description headerName String Name of header to tokenize instead of using the message body. mode Enum The extraction mode. The available extraction modes are: i - injecting the contextual namespace bindings into the extracted token (default) w - wrapping the extracted token in its ancestor context u - unwrapping the extracted token to its child content t - extracting the text content of the specified element. Enum values: i w u t group Integer To group N parts together. trim Boolean Whether to trim the value to remove leading and trailing whitespaces and line breaks. 131.3. Example See Split EIP which has examples using the XML Tokenize language. 131.4. Spring Boot Auto-Configuration The component supports 3 options, which are listed below. Name Description Default Type camel.language.xtokenize.enabled Whether to enable auto configuration of the xtokenize language. This is enabled by default. Boolean camel.language.xtokenize.mode The extraction mode. The available extraction modes are: i - injecting the contextual namespace bindings into the extracted token (default) w - wrapping the extracted token in its ancestor context u - unwrapping the extracted token to its child content t - extracting the text content of the specified element. String camel.language.xtokenize.trim Whether to trim the value to remove leading and trailing whitespaces and line breaks. true Boolean

Commands:
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-xml-jaxp-starter</artifactId> </dependency>
<dependency> <groupId>org.codehaus.woodstox</groupId> <artifactId>woodstox-core-asl</artifactId> <version>4.4.1</version> </dependency>
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-stax-starter</artifactId> </dependency>