mtpti5iD/redhat-docs_dataset huggingface dataset:
1.6. Using Network Kernel Tunables with sysctl Using certain kernel tunables through the sysctl utility, you can adjust network configuration on a running system and directly affect the networking performance. To change network settings, use the sysctl commands. For permanent changes that persist across system restarts, add lines to the /etc/sysctl.conf file. To display a list of all available sysctl parameters, enter as root : For more details on network kernel tunables using sysctl , see the Using PTP with Multiple Interfaces section in the System Administrator's Guide. For more information on network kernel tunables, see the Network Interface Tunables section in the Kernel Administration Guide.

Commands:
~]# sysctl -a
Chapter 1. Preparing to install JBoss EAP You can choose to install an instance of JBoss EAP using any of the three types of installers. Depending on your requirements, each installer type is useful in certain situations. 1.1. JBoss EAP installation methods You can choose one of several methods to install JBoss EAP. Each method is best used in certain situations. The following table provides a brief overview of each type of installation and links to the sections that cover the relevant processes. Table 1.1. Installer Types Method Description Installer installation You can run the installer on a console or as a graphical wizard. Both options provide step-by-step instructions for installing and configuring the server instance. The Installer Installation is the preferred method to install JBoss EAP on all supported platforms. The installer also provides an additional setup option, including Quickstarts and configuration of the Maven repository. Archive installation The archive installation is suitable for installation on all supported operating systems. Use this method if you want to extract the instance manually. The archive installation provides a default installation of JBoss EAP, and you must implement any configuration changes after the installation. Note If you plan to use JBoss Operations Network (JBoss ON) to deploy and install JBoss EAP patches, install the target JBoss EAP instances using the archive installation method. RPM installation You can install JBoss EAP using RPM packages on supported installations of Red Hat Enterprise Linux 6+. 1.2. The EAP_HOME variable You can use the variable, EAP_HOME , to denote the path for the JBoss EAP installation. Set the EAP_HOME variable to the actual path for the JBoss EAP installation. The path set for the EAP_HOME variable stays the same and does not change after patching or updating an instance of the JBoss EAP. Note EAP_HOME is not an environment variable. JBOSS_HOME is the environment variable used in scripts. Depending on the installation option you choose to install JBoss EAP, you can locate the installation directory or the default path as follows: If you installed JBoss EAP using the archive installation method, the installation directory is the jboss-eap-7.4 directory where you extracted the archive. If you installed JBoss EAP using the installer application, the default path for EAP_HOME is USD{user.home}/EAP-7.4.0 : For Red Hat Enterprise Linux and Solaris: /home/ USER_NAME /EAP-7.4.0/ For Microsoft Windows: C:\Users\ USER_NAME \EAP-7.4.0\ If you installed JBoss EAP using the RPM installation method, the installation directory is /opt/rh/eap7/root/usr/share/wildfly/ .

Commands:
8.143. perl-CGI-Session 8.143.1. RHBA-2013:0851 - perl-CGI-Session bug fix update An updated perl-CGI-Session package that fixes one bug is now available for Red Hat Enterprise Linux 6. CGI-Session is a Perl5 library that provides an easy, reliable and modular session management system across HTTP requests. Persistency is a key feature for such applications as shopping carts, login/authentication routines, and application that need to carry data across HTTP requests. Bug Fix BZ# 657359 Previously, several build-time dependencies were missing in the package. As a consequence, the package could not be rebuilt from source. This update adds the missing dependencies to the package, which can now be rebuilt from source as expected. Users of perl-CGI-Session are advised to upgrade to this updated package, which fixes this bug.

Commands:
2.9. Deploying the Adapter Once the RAR file is built, deploy it using the CLI or Management Console. Once the adapter's RAR file has been deployed you can create an instance of this connector to use with your Translator. Creating an instance of this adapter is the same as creating a Connection Factory. There are two ways you can do this: Edit the server configuration file and add the following XML in the "resource-adapters" subsystem. <!-- If susbsytem is already defined, only copy the contents under it and edit to suit your needs --> <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"> <resource-adapters> <resource-adapter> <archive>teiid-connector-sample.rar</archive> <transaction-support>NoTransaction</transaction-support> <connection-definitions> <connection-definition class-name="org.teiid.resource.adapter.MyManagedConnectionFactory" jndi-name="USD{jndi-name}" enabled="true" use-java-context="true" pool-name="sample-ds"> <config-property name="UserName">jdoe</config-property> <config-property name="Count">12</config-property> </connection-definition> </connection-definitions> </resource-adapter> </resource-adapters> </subsystem> There are more properties that you can define in this file; for example, for pooling, transactions, and security. Refer to the Red Hat JBoss Enterprise Application Platform documentation for all the available properties. See https://access.redhat.com/site/documentation/JBoss_Enterprise_Application_Platform/ . You can use the web-based Management Console to create a new ConnectionFactory .

Commands:
<!-- If susbsytem is already defined, only copy the contents under it and edit to suit your needs --> <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"> <resource-adapters> <resource-adapter> <archive>teiid-connector-sample.rar</archive> <transaction-support>NoTransaction</transaction-support> <connection-definitions> <connection-definition class-name="org.teiid.resource.adapter.MyManagedConnectionFactory" jndi-name="USD{jndi-name}" enabled="true" use-java-context="true" pool-name="sample-ds"> <config-property name="UserName">jdoe</config-property> <config-property name="Count">12</config-property> </connection-definition> </connection-definitions> </resource-adapter> </resource-adapters> </subsystem>
2.2.10.3. Perl Documentation The perldoc tool provides documentation on language and core modules. To learn more about a module, use perldoc module_name . For example, perldoc CGI will display the following information about the CGI core module: For details on Perl functions, use perldoc -f function_name . For example, perldoc -f split wil display the following information about the split function: Current PerlDoc documentation can be found on perldoc.perl.org . Core and external modules are documented on the Comprehensive Perl Archive Network .

Commands:
NAME CGI - Handle Common Gateway Interface requests and responses SYNOPSIS use CGI; my USDq = CGI->new; [...] DESCRIPTION CGI.pm is a stable, complete and mature solution for processing and preparing HTTP requests and responses. Major features including processing form submissions, file uploads, reading and writing cookies, query string generation and manipulation, and processing and preparing HTTP headers. Some HTML generation utilities are included as well. [...] PROGRAMMING STYLE There are two styles of programming with CGI.pm, an object-oriented style and a function-oriented style. In the object-oriented style you create one or more CGI objects and then use object methods to create the various elements of the page. Each CGI object starts out with the list of named parameters that were passed to your CGI script by the server. [...]
split /PATTERN/,EXPR,LIMIT split /PATTERN/,EXPR split /PATTERN/ split Splits the string EXPR into a list of strings and returns that list. By default, empty leading fields are preserved, and empty trailing ones are deleted. (If all fields are empty, they are considered to be trailing.) In scalar context, returns the number of fields found. In scalar and void context it splits into the @_ array. Use of split in scalar and void context is deprecated, however, because it clobbers your subroutine arguments. If EXPR is omitted, splits the USD_ string. If PATTERN is also omitted, splits on whitespace (after skipping any leading whitespace). Anything matching PATTERN is taken to be a delimiter separating the fields. (Note that the delimiter may be longer than one character.) [...]
Chapter 2. Getting started with OpenShift Virtualization You can install and configure a basic OpenShift Virtualization environment to explore its features and functionality. Note Cluster configuration procedures require cluster-admin privileges. 2.1. Before you begin Review the installation requirements . Review the storage features required for cloning, snapshots, and live migration. See Using a CSI-enabled storage provider for details. Install the OpenShift Virtualization Operator . Install the virtctl tool . 2.2. Getting started Create a virtual machine Create a RHEL virtual machine using the wizard. Create a Windows virtual machine: Create and customize Windows boot sources . Create a Windows virtual machine using the wizard. Install VirtIO drivers and the QEMU guest agent on the Windows virtual machine. Connect to a virtual machine Connect to the serial console or VNC console of a virtual machine using the web console. Connect to a virtual machine using SSH . Connect to a Windows virtual machine using RDP . Manage a virtual machine Stop, start, pause, and restart a virtual machine from the web console . Manage a virtual machine, expose a port, and connect to the serial console of a virtual machine from the command line with virtctl . 2.3. steps Connect VMs to secondary networks Connect a virtual machine to a Linux bridge network . Connect a virtual machine to an SR-IOV network . Monitor your OpenShift Virtualization environment Monitor resources, details, status, and top consumers on the Virtualization Overview page . View high-level information about your virtual machines on the Virtual Machines dashboard . View virtual machine logs . Automate your deployments Automate virtual machine deployments with Ansible. Automate Windows virtual machine deployments with sysprep . 2.4. Additional resources About the Kubernetes NMState Operator Specifying nodes for virtual machines Live migration Virtual machine templates Configuring local storage Backup and restore

Commands:
10.6. Multi-Source Models: SELECT, UPDATE and DELETE A multi-source query against a SELECT/UPDATE/DELETE may affect any subset of the sources based upon the evaluation of the WHERE clause. The multi-source column may not be targeted in an update change set. The sum of the update counts for UPDATEs/DELETEs will be returned as the resultant update count. When running under a transaction in a mode that detects the need for a transaction and multiple updates may performed or a transactional read is required and multiple sources may be read from, a transaction will be started to enlist each source.

Commands:
14.6. Configuring the radvd daemon for IPv6 routers The router advertisement daemon ( radvd ) sends router advertisement messages which are required for IPv6 stateless autoconfiguration. This allows users to automatically configure their addresses, settings, routes and choose a default router based on these advertisements. To configure the radvd daemon: Install the radvd daemon: Set up the /etc/radvd.conf file. For example: Note If you want to additionally advertise DNS resolvers along with the router advertisements, add the RDNSS <ip> <ip> <ip> { }; option in the /etc/radvd.conf file. To configure a DHCPv6 service for your subnets, you can set the AdvManagedFlag to on , so the router advertisements allow clients to automatically obtain an IPv6 address when a DHCPv6 service is available. For more details on configuring the DHCPv6 service, see Section 14.5, "DHCP for IPv6 (DHCPv6)" Enable the radvd daemon: Start the radvd daemon immediately: To display the content of router advertisement packages and the configured values sent by the radvd daemon, use the radvdump command: For more information on the radvd daemon, see the radvd(8) , radvd.conf(5) , radvdump(8) man pages.

Commands:
~]# sudo yum install radvd
interface enp1s0 { AdvSendAdvert on; MinRtrAdvInterval 30; MaxRtrAdvInterval 100; prefix 2001:db8:1:0::/64 { AdvOnLink on; AdvAutonomous on; AdvRouterAddr off; }; };
~]# sudo systemctl enable radvd.service
~]# sudo systemctl start radvd.service
~]# radvdump Router advertisement from fe80::280:c8ff:feb9:cef9 (hoplimit 255) AdvCurHopLimit: 64 AdvManagedFlag: off AdvOtherConfigFlag: off AdvHomeAgentFlag: off AdvReachableTime: 0 AdvRetransTimer: 0 Prefix 2002:0102:0304:f101::/64 AdvValidLifetime: 30 AdvPreferredLifetime: 20 AdvOnLink: off AdvAutonomous: on AdvRouterAddr: on Prefix 2001:0db8:100:f101::/64 AdvValidLifetime: 2592000 AdvPreferredLifetime: 604800 AdvOnLink: on AdvAutonomous: on AdvRouterAddr: on AdvSourceLLAddress: 00 80 12 34 56 78
C.3. CacheContainerStats org.infinispan.stats.impl.CacheContainerStatsImpl The CacheContainerStats component contains statistics such as timings, hit/miss ratio, and operation information. Table C.5. Attributes Name Description Type Writable averageReadTime Cache container total average number of milliseconds for all read operations in this cache container. long No averageRemoveTime Cache container total average number of milliseconds for all remove operations in this cache container. long No averageWriteTime Cache container total average number of milliseconds for all write operations in this cache container. long No evictions Cache container total number of cache eviction operations. long No hitRatio Cache container total percentage hit/(hit+miss) ratio for this cache. double No hits Cache container total number of cache attribute hits. long No misses Cache container total number of cache attribute misses. long No numberOfEntries Cache container total number of entries currently in all caches from this cache container. int No readWriteRatio Cache container read/writes ratio in all caches from this cache container. double No removeHits Cache container total number of removal hits. double No removeMisses Cache container total number of cache removals where keys were not found. long No statisticsEnabled Enables or disables the gathering of statistics by this component. boolean Yes stores Cache container total number of cache attribute put operations. long No Report a bug

Commands:
Chapter 9. MTR 1.2.0 9.1. New features This section describes the new features of the Migration Toolkit for Runtimes (MTR) 1.2.0. Decompilation and analysis of applications based on Java 17 Rules Override enhancement: A new condition has been added for overriding an existing rule. In addition to matching rulesetId and ruleId , the target technology in the override ruleset must match one of the targets that the user specified for running the analysis. Eclipse Plugin Java 17 compatibility Upgrade of the Windup Operator: Adopted Quarkus 2.13.7.Final and the Quarkus Operator SDK 4.0.8 9.1.1. New rulesets and targets OpenJDK 21: Rules to support the upgrading to OpenJDK 21. Red Hat JBoss Web Server 6: Rules to support the upgrade of JWS and Tomcat applications to JWS 6 and Tomcat 10. Camel 4: Comprehensive rulesets supporting upgrade to all Y-stream releases of Camel 3 and Camel 4. More migration rules to support Red Hat JBoss EAP 8 and Hibernate 6. Java/Jakarta EE to Quarkus: New rulesets support migrating Java/Jakarta EE applications to Quarkus 3. These rulesets cover the quarkification of the project, along with JAX-RS and CDI technologies. Additional rules that support this migration path are still under development and will be made available in future Z-stream releases. 9.2. Known issues For a complete list of all known issues, see the list of MTR 1.2.0 known issues in Jira. 9.3. Resolved issues For a complete list of all issues resolved in this release, see the list of MTR 1.2.0 resolved issues in Jira.

Commands:
Chapter 6. Viewing the history of your JBoss EAP server changes using the Management CLI The JBoss EAP Management CLI allows you to easily view the history of all the updates and reverts that you applied on your JBoss EAP server. The Management CLI provides you with a comprehensive list of changes on your JBoss EAP server when you run the installer history command. These include updates, reverts and other modifications to the channel configuration. If you need more detailed information about a particular change, you can investigate futher it by appending --revision=<Installation state> to the command. This allows you to access the specific revision's details and gain deeper insights into the changes to your JBoss EAP server. 6.1. Prerequisite You have a JBoss EAP server installed. 6.2. Viewing the history of your JBoss EAP server changes in a stand-alone or a managed domain The following example describes how to use the JBoss EAP Management CLI to view the history of updates, reverts, or configuration changes on your JBoss EAP server in a stand-alone or a managed domain. Procedure Launch the Management CLI: EAP_HOME/bin/jboss-cli.sh View the history of JBoss EAP changes: View the history of JBoss EAP changes in a stand-alone server: [standalone@localhost:9990 /] installer history View the history of JBoss EAP changes in a managed domain: [domain@localhost:9990 /] installer history --host=target-host

Commands:
EAP_HOME/bin/jboss-cli.sh
[standalone@localhost:9990 /] installer history
[domain@localhost:9990 /] installer history --host=target-host
2.4. Multipath Devices in Logical Volumes After creating multipath devices, you can use the multipath device names just as you would use a physical device name when creating an LVM physical volume. For example, if /dev/mapper/mpatha is the name of a multipath device, the following command will mark /dev/mapper/mpatha as a physical volume. You can use the resulting LVM physical device when you create an LVM volume group just as you would use any other LVM physical device. Note If you attempt to create an LVM physical volume on a whole device on which you have configured partitions, the pvcreate command will fail. Note that the Anaconda and Kickstart installation programs create empty partition tables if you do not specify otherwise for every block device. If you wish to use the whole device rather than a partition, you must remove the existing partitions from the device. You can remove existing partitions with the kpartx -d and the fdisk commands. If your system has block devices that are greater that 2Tb, you can use the parted command to remove partitions. When you create an LVM logical volume that uses active/passive multipath arrays as the underlying physical devices, you should include filters in the /etc/lvm/lvm.conf file to exclude the disks that underlie the multipath devices. This is because if the array automatically changes the active path to the passive path when it receives I/O, multipath will failover and failback whenever LVM scans the passive path if these devices are not filtered. For active/passive arrays that require a command to make the passive path active, LVM prints a warning message when this occurs. To filter all SCSI devices in the LVM configuration file ( lvm.conf ), include the following filter in the devices section of the file.

Commands:
pvcreate /dev/mapper/mpatha
filter = [ "r/block/", "r/disk/", "r/sd.*/", "a/.*/" ]
Chapter 1. The Ceph Object Gateway Ceph Object Gateway, also known as RADOS Gateway (RGW), is an object storage interface built on top of the librados library to provide applications with a RESTful gateway to Ceph storage clusters. Ceph Object Gateway supports three interfaces: S3-compatibility: Provides object storage functionality with an interface that is compatible with a large subset of the Amazon S3 RESTful API. Swift-compatibility: Provides object storage functionality with an interface that is compatible with a large subset of the OpenStack Swift API. The Ceph Object Gateway is a service interacting with a Ceph storage cluster. Since it provides interfaces compatible with OpenStack Swift and Amazon S3, the Ceph Object Gateway has its own user management system. Ceph Object Gateway can store data in the same Ceph storage cluster used to store data from Ceph block device clients; however, it would involve separate pools and likely a different CRUSH hierarchy. The S3 and Swift APIs share a common namespace, so you can write data with one API and retrieve it with the other. Administrative API: Provides an administrative interface for managing the Ceph Object Gateways. Administrative API requests are done on a URI that starts with the admin resource end point. Authorization for the administrative API mimics the S3 authorization convention. Some operations require the user to have special administrative capabilities. The response type can be either XML or JSON by specifying the format option in the request, but defaults to the JSON format. Additional Resources See the Red Hat Ceph Storage Developer Guide for details on the available APIs in Red Hat Ceph Storage.

Commands:
21.2. Using JMX with Red Hat JBoss Data Grid Management in Red Hat JBoss Data Grid instances aims to expose as much relevant statistical information as possible. This information allows administrators to view the state of each instance. While a single installation can comprise of tens or hundreds of such instances, it is essential to expose and present the statistical information for each of them in a clear and concise manner. In JBoss Data Grid, JMX is used in conjunction with JBoss Operations Network (JON) to expose this information and present it in an orderly and relevant manner to the administrator. Report a bug

Commands:
API overview OpenShift Container Platform 4.13 Overview content for the OpenShift Container Platform API Red Hat OpenShift Documentation Team

Commands:
oc debug node/<node>
chroot /host
systemctl cat kubelet
/etc/systemd/system/kubelet.service.d/20-logging.conf [Service] Environment="KUBELET_LOG_LEVEL=2"
echo -e "[Service]\nEnvironment=\"KUBELET_LOG_LEVEL=8\"" > /etc/systemd/system/kubelet.service.d/30-logging.conf
systemctl daemon-reload
systemctl restart kubelet
rm -f /etc/systemd/system/kubelet.service.d/30-logging.conf
systemctl daemon-reload
systemctl restart kubelet
apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfig metadata: labels: machineconfiguration.openshift.io/role: master name: 99-master-kubelet-loglevel spec: config: ignition: version: 3.2.0 systemd: units: - name: kubelet.service enabled: true dropins: - name: 30-logging.conf contents: | [Service] Environment="KUBELET_LOG_LEVEL=2"
oc adm node-logs --role master -u kubelet
oc adm node-logs --role worker -u kubelet
journalctl -b -f -u kubelet.service
sudo tail -f /var/log/containers/*
- for n in USD(oc get node --no-headers | awk '{print USD1}'); do oc adm node-logs USDn | gzip > USDn.log.gz; done