mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 29. Adding and removing tracepoints from a running perf collector without stopping or restarting perf By using the control pipe interface to enable and disable different tracepoints in a running perf collector, you can dynamically adjust what data you are collecting without having to stop or restart perf . This ensures you do not lose performance data that would have otherwise been recorded during the stopping or restarting process. 29.1. Adding tracepoints to a running perf collector without stopping or restarting perf Add tracepoints to a running perf collector using the control pipe interface to adjust the data you are recording without having to stop perf and losing performance data. Prerequisites You have the perf user space tool installed as described in Installing perf . Procedure Configure the control pipe interface: Run perf record with the control file setup and events you are interested in enabling: In this example, declaring 'sched:*' after the -e option starts perf record with scheduler events. In a second terminal, start the read side of the control pipe: Starting the read side of the control pipe triggers the following message in the first terminal: In a third terminal, enable a tracepoint using the control file: This command triggers perf to scan the current event list in the control file for the declared event. If the event is present, the tracepoint is enabled and the following message appears in the first terminal: Once the tracepoint is enabled, the second terminal displays the output from perf detecting the tracepoint: 29.2. Removing tracepoints from a running perf collector without stopping or restarting perf Remove tracepoints from a running perf collector using the control pipe interface to reduce the scope of data you are collecting without having to stop perf and losing performance data. Prerequisites You have the perf user space tool installed as described in Installing perf . You have added tracepoints to a running perf collector via the control pipe interface. For more information, see Adding tracepoints to a running perf collector without stopping or restarting perf . Procedure Remove the tracepoint: Note This example assumes you have previously loaded scheduler events into the control file and enabled the tracepoint sched:sched_process_fork . This command triggers perf to scan the current event list in the control file for the declared event. If the event is present, the tracepoint is disabled and the following message appears in the terminal used to configure the control pipe:

Commands:
mkfifo control ack perf.pipe
perf record --control=fifo:control,ack -D -1 --no-buffering -e ' sched:* ' -o - > perf.pipe
cat perf.pipe | perf --no-pager script -i -
Events disabled
echo 'enable sched:sched_process_fork ' > control
event sched:sched_process_fork enabled
bash 33349 [034] 149587.674295: sched:sched_process_fork: comm=bash pid=33349 child_comm=bash child_pid=34056
echo 'disable sched:sched_process_fork ' > control
event sched:sched_process_fork disabled
Appendix A. Capsule Server scalability considerations The maximum number of Capsule Servers that Satellite Server can support has no fixed limit. It was tested that a Satellite Server can support 17 Capsule Servers with 2 vCPUs. However, scalability is highly variable, especially when managing Puppet clients. Capsule Server scalability when managing Puppet clients depends on the number of CPUs, the run-interval distribution, and the number of Puppet managed resources. Capsule Server has a limitation of 100 concurrent Puppet agents running at any single point in time. Running more than 100 concurrent Puppet agents results in a 503 HTTP error. For example, assuming that Puppet agent runs are evenly distributed with less than 100 concurrent Puppet agents running at any single point during a run-interval, a Capsule Server with 4 CPUs has a maximum of 1250 - 1600 Puppet clients with a moderate workload of 10 Puppet classes assigned to each Puppet client. Depending on the number of Puppet clients required, the Satellite installation can scale out the number of Capsule Servers to support them. If you want to scale your Capsule Server when managing Puppet clients, the following assumptions are made: There are no external Puppet clients reporting directly to the Satellite integrated Capsule. All other Puppet clients report directly to an external Capsule. There is an evenly distributed run-interval of all Puppet agents. Note Deviating from the even distribution increases the risk of overloading Satellite Server. The limit of 100 concurrent requests applies. The following table describes the scalability limits using the recommended 4 CPUs. Table A.1. Puppet scalability using 4 CPUs Puppet Managed Resources per Host Run-Interval Distribution 1 3000 - 2500 10 2400 - 2000 20 1700 - 1400 The following table describes the scalability limits using the minimum 2 CPUs. Table A.2. Puppet scalability using 2 CPUs Puppet Managed Resources per Host Run-Interval Distribution 1 1700 - 1450 10 1500 - 1250 20 850 - 700

Commands:
Chapter 6. Configure Public Key based SSH Authentication without a password Configure public key based SSH authentication without a password for the root user on the first hyperconverged host to all hosts, including itself . Do this for all storage and management interfaces, and for both IP addresses and FQDNs. 6.1. Generating SSH key pairs without a password Generating a public/private key pair lets you use key-based SSH authentication. Generating a key pair that does not use a password makes it simpler to use Ansible to automate deployment and configuration processes. Procedure Log in to the first hyperconverged host as the root user. Generate an SSH key that does not use a password. Start the key generation process. Enter a location for the key. The default location, shown in parentheses, is used if no other input is provided. Specify and confirm an empty passphrase by pressing Enter twice. The private key is saved in <location>/<keyname> . The public key is saved in <location>/<keyname>.pub . Warning Your identification in this output is your private key. Never share your private key. Possession of your private key allows someone else to impersonate you on any system that has your public key. 6.2. Copying SSH keys To access a host using your private key, that host needs a copy of your public key. Prerequisites Generate a public/private key pair with no password. Procedure Log in to the first host as the root user. Copy your public key to each host that you want to access, including the host on which you execute the command, using both the front-end and the back-end FQDNs. Enter the password for <user>@<hostname> when prompted. Warning Make sure that you use the file that ends in .pub . Never share your private key. Possession of your private key allows someone else to impersonate you on any system that has your public key. For example, if you are logged in as the root user on server1.example.com , you would run the following commands for a three node deployment:

Commands:
ssh-keygen -t rsa Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa): <location>/<keyname>
Enter passphrase (empty for no passphrase): Enter same passphrase again:
Your identification has been saved in <location>/<keyname>. Your public key has been saved in <location>/<keyname>.pub. The key fingerprint is SHA256:8BhZageKrLXM99z5f/AM9aPo/KAUd8ZZFPcPFWqK6+M root@server1.example.com The key's randomart image is: +---[ECDSA 256]---+ | . . +=| | . . . = o.o| | + . * . o...| | = . . * . + +..| |. + . . So o * ..| | . o . .+ = ..| | o oo ..=. .| | ooo...+ | | .E++oo | +----[SHA256]-----+
ssh-copy-id -i <location>/<keyname>.pub <user>@<hostname>
ssh-copy-id -i <location>/<keyname>.pub root@server1front.example.com ssh-copy-id -i <location>/<keyname>.pub root@server2front.example.com ssh-copy-id -i <location>/<keyname>.pub root@server3front.example.com ssh-copy-id -i <location>/<keyname>.pub root@server1back.example.com ssh-copy-id -i <location>/<keyname>.pub root@server2back.example.com ssh-copy-id -i <location>/<keyname>.pub root@server3back.example.com
8.6. Configure ODBC Options on Microsoft Windows Prerequisites You must have logged into the workstation with administrative rights. You must have used the Control Panel's Data Sources (ODBC) applet to add a new data source name. Each data source name you configure can only access one VDB within a Teiid System. To make more than one VDB available, you need to configure more than one data source name. From the Start menu, select Settings -> Control Panel . The Control Panel displays. Double-click Administrative Tools . Double-click Data Sources (ODBC) . The ODBC Data Source Administrator applet displays. Click the tab associated with the type of DSN you want to add. The Create New Data Source dialog box displays. In the Select a driver for which you want to set up a data source table, select PostgreSQL Unicode . Click Finish . In the Data Source Name edit box, type the name you want to assign to this data source. In the Database edit box, type the name of the virtual database you want to access through this data source. In the Server edit box, type the host name or IP address of your Teiid runtime. Note If you are connecting via a firewall or NAT address, you must enter either the firewall address or the NAT address. In the Port edit box, type the port number to which the system listens for ODBC requests. (By default, Red Hat JBoss Data Virtualization listens for ODBC requests on port 35432.) In the User Name and Password edit boxes, supply the user name and password for the Teiid runtime access. Leave SSL Mode to disabled. (SSL connections are unsupported at present.) Provide any description about the data source in the Description field. Click on the Datasource button and configure the options. Tick Parse Statements , Recognize Unique Indexes , Maximum , Text as LongVarChar and Bool as Char and set MaxVarChar to 255, Max LongVarChar to 8190, Cache Size to 100 and SysTable Prefixes to dd_:. On the second page, click LF , Server side prepare , default , 7.4+ and set the Extra Opts to 0x0. Click Save . You can optionally click Test to validate your connection if Red Hat JBoss Data Virtualization is running. Table 8.1. Primary ODBC Settings for Red Hat JBoss Data Virtualization Name Description Updateable Cursors and Row Versioning Should not be used. Use serverside prepare and Parse Statements and Disallow Premature It is recommended that Use serverside prepare is enabled and Parse Statements/Disallow Premature are disabled. SSL mode See Security Guide https://access.redhat.com/documentation/en/red-hat-jboss-data-virtualization/6.4/paged/security-guide/ Use Declare/Fetch cursors and Fetch Max Count Should be used to better manage resources when large result sets are used. Logging/debug settings can be utilized as needed. Settings that manipulate datatypes, metadata, or optimizations such as Show SystemTables , True is -1 , Backend genetic optimizer , Bytea as LongVarBinary , Bools as Char are ignored by the server and have no client side effect. Any other setting that does have a client-side effect, such as LF to CR/LF conversion , may be used if desired but there is currently no server-side usage of the setting.

Commands:
Chapter 1. Red Hat Integration Red Hat Integration is a comprehensive set of integration and event processing technologies for creating, extending, and deploying container-based integration services across hybrid and multicloud environments. Red Hat Integration provides an agile, distributed, and API-centric solution that organizations can use to connect and share data between applications and systems required in a digital world. Red Hat Integration includes the following capabilities: Real-time messaging Cross-datacenter message streaming API connectivity Application connectors Enterprise integration patterns API management Data transformation Service composition and orchestration Additional resources Understanding enterprise integration

Commands:
7.77. gtk2 7.77.1. RHBA-2013:0493 - gtk2 bug fix update Updated gtk2 packages that fix two bugs are now available for Red Hat Enterprise Linux 6. GIMP Toolkit (GTK+) is a multi-platform toolkit for creating graphical user interfaces. Bug Fixes BZ#882346 Due to a recent change in the behavior of one of the X.Org Server components, GTK+ applications could not use certain key combinations for key bindings. This update makes GTK+ compatible with the new behavior, which ensures that no regressions occur in applications that use the library. BZ#889172 Previously, when switching between the "Recently Used" and "Search" tabs in the "Open Files" dialog box, the "Size" column in the view disappeared. This update ensures the column is visible when the relevant option is selected. Users of GTK+ are advised to upgrade to these updated packages, which fix these bugs.

Commands:
A.9. x86_energy_perf_policy The x86_energy_perf_policy tool allows administrators to define the relative importance of performance and energy efficiency. It is provided by the kernel-tools package. To view the current policy, run the following command: To set a new policy, run the following command: Replace profile_name with one of the following profiles. performance The processor does not sacrifice performance for the sake of saving energy. This is the default value. normal The processor tolerates minor performance compromises for potentially significant energy savings. This is a reasonable saving for most servers and desktops. powersave The processor accepts potentially significant performance decreases in order to maximize energy efficiency. For further details of how to use x86_energy_perf_policy , see the man page:

Commands:
x86_energy_perf_policy -r
x86_energy_perf_policy profile_name
man x86_energy_perf_policy
8.7. abrt 8.7.1. RHBA-2014:1572 - abrt bug fix and enhancement update Updated abrt packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The abrt packages provide the Automatic Bug Reporting Tool. Bug Fix BZ# 1084467 Previously, kernel oops messages were deleted by ABRT, and thus the user was not sufficiently informed about the kernel behavior. With this update, kernel oops messages are kept and also supplemented by an explanation. The behavior can be restored in the newly created /etc/abrt/plugins/oops.conf file (man abrt-oops.conf). In addition, this update adds the following Enhancement BZ# 989530 With this update, ABRT messages include machine host name. Users of abrt are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
Chapter 207. Kubernetes Resources Quota Component Available as of Camel version 2.17 The Kubernetes Resources Quota component is one of Kubernetes Components which provides a producer to execute kubernetes resource quota operations. 207.1. Component Options The Kubernetes Resources Quota component has no options. 207.2. Endpoint Options The Kubernetes Resources Quota endpoint is configured using URI syntax: with the following path and query parameters: 207.2.1. Path Parameters (1 parameters): Name Description Default Type masterUrl Required Kubernetes API server URL String 207.2.2. Query Parameters (20 parameters): Name Description Default Type apiVersion (producer) The Kubernetes API Version to use String dnsDomain (producer) The dns domain, used for ServiceCall EIP String kubernetesClient (producer) Default KubernetesClient to use if provided KubernetesClient operation (producer) Producer operation to do on Kubernetes String portName (producer) The port name, used for ServiceCall EIP String portProtocol (producer) The port protocol, used for ServiceCall EIP tcp String connectionTimeout (advanced) Connection timeout in milliseconds to use when making requests to the Kubernetes API server. Integer synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean caCertData (security) The CA Cert Data String caCertFile (security) The CA Cert File String clientCertData (security) The Client Cert Data String clientCertFile (security) The Client Cert File String clientKeyAlgo (security) The Key Algorithm used by the client String clientKeyData (security) The Client Key data String clientKeyFile (security) The Client Key file String clientKeyPassphrase (security) The Client Key Passphrase String oauthToken (security) The Auth Token String password (security) Password to connect to Kubernetes String trustCerts (security) Define if the certs we used are trusted anyway or not Boolean username (security) Username to connect to Kubernetes String 207.3. Spring Boot Auto-Configuration The component supports 2 options, which are listed below. Name Description Default Type camel.component.kubernetes-resources-quota.enabled Whether to enable auto configuration of the kubernetes-resources-quota component. This is enabled by default. Boolean camel.component.kubernetes-resources-quota.resolve-property-placeholders Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. true Boolean

Commands:
kubernetes-resources-quota:masterUrl
5.5. Issues with Large Number of LUNs When a large number of LUNs are added to a node, using multipathed devices can significantly increase the time it takes for the udev device manager to create device nodes for them. If you experience this problem, you can correct it by deleting the following line in /etc/udev/rules.d/40-multipath.rules : This line causes the udev device manager to run multipath every time a block device is added to the node. Even with this line removed, the multipathd daemon will still automatically create multipathed devices, and multipath will still be called during the boot process for nodes with multipathed root file systems. The only change is that multipathed devices will not be automatically created when the multipathd daemon is not running, which should not be a problem for the vast majority of multipath users.

Commands:
KERNEL!="dm-[0-9]*", ACTION=="add", PROGRAM=="/bin/bash -c '/sbin/lsmod | /bin/grep ^dm_multipath'", RUN+="/sbin/multipath -v0 %M:%m"
Chapter 5. Validating the deployment After you successfully run the playbook, the JBoss Web Server collection automatically installs Red Hat JBoss Web Server on your target hosts. If you have added customized tasks to the playbook, Ansible also automatically deploys any JBoss Web Server applications on your targets hosts, as appropriate. You can optionally check the status of JBoss Web Server by using the systemctl command on the target host or by using the curl command on a remote host. Prerequisites You have run the playbook . Procedure Optional: On the JBoss Web Server host, enter the following command as the root user: In the preceding command, replace <service_name> with the correct service name for your JBoss Web Server installation. The default service name is tomcat . For more information about setting up a service name, see Automating the integration of JBoss Web Server with systemd . Note This step requires that JBoss Web Server is integrated with systemd . Optional: On a remote host , enter the following command as the root user: In the preceding command, replace <target_host> with the IP address or host name of the JBoss Web Server host that you want to access. The preceding command assumes that the JBoss Web Server is accessible through the default port 8080 and that the target firewall and network allow remote access to the port. Note The JBoss Web Server collection also includes a validate.yml playbook in the playbooks folder. You can run the validate.yml playbook if you want the JBoss Web Server collection to perform automated validation checks. For more information about the validate.yml playbook, refer to the information page for the jws_validation role in Ansible automation hub . Additional resources Controlling the JBoss Web Server with systemd

Commands:
systemctl status <service_name>
curl http:// <target_host> :8080/
3.2. libvirt and libvirt Tools The libvirt package provides a hypervisor-independent virtualization API that can interact with the virtualization capabilities of a range of operating systems. It includes: A virtualization layer to securely manage virtual machines on a host. An interface for managing local and networked hosts. The APIs required to provision, create, modify, monitor, control, migrate, and stop virtual machines. Although multiple hosts may be accessed with libvirt simultaneously, the APIs are limited to single node operations. Note Only operations supported by the hypervisor can be performed using libvirt. libvirt focuses on managing single hosts and provides APIs to enumerate, monitor and use the resources available on the managed node, including CPUs, memory, storage, networking and Non-Uniform Memory Access (NUMA) partitions. The management tools do not need to be on the same physical machine as the machines on which the hosts are running. In such a scenario, the machine on which the management tools run communicates with the machines on which the hosts are running using secure protocols. Red Hat Enterprise Linux 7 supports libvirt and includes libvirt -based tools as its default method for virtualization management (as in Red Hat Virtualization Management). The libvirt package is available as free software under the GNU Lesser General Public License. The libvirt project aims to provide a long term stable C API to virtualization management tools, running on top of varying hypervisor technologies. The libvirt package supports Xen on Red Hat Enterprise Linux 5, and KVM on Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, and Red Hat Enterprise Linux 7. Notably, libvirt also provides the two primary tools for controlling virtualization on Red Hat Enterprise Linux 7: virsh and virt-manager .

Commands:
B.2. Using Keytool with JBoss Data Virtualization When using the keytool to manage public key cryptography for JBoss Data Virtualization, use the following options: Set the alias to teiid using the -alias teiid option. Set the algorithm to RSA using the -keyslg RSA option. Set the validity period to 365 days using the -validity 365 option. Set the store type to JKS using the -storetype JKS option.

Commands:
4.136. libhbaapi 4.136.1. RHBA-2011:1605 - libhbaapi bug fix and enhancement update An updated libhbaapi package that fixes multiple bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The Host Bus Adapter API is a C-level project to manage Fibre Channel Host Bus Adapters. The package has been upgraded to upstream version 2.2, which provides a number of bug fixes and enhancements over the version. (BZ# 719585 ) Users are advised to upgrade to this updated libhbaapi package, which fixes these bugs and adds these enhancements.

Commands: