mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 91. JarArtifact schema reference Used in: Plugin Property Property type Description url string URL of the artifact which will be downloaded. Streams for Apache Kafka does not do any security scanning of the downloaded artifacts. For security reasons, you should first verify the artifacts manually and configure the checksum verification to make sure the same artifact is used in the automated build. Required for jar , zip , tgz and other artifacts. Not applicable to the maven artifact type. sha512sum string SHA512 checksum of the artifact. Optional. If specified, the checksum will be verified while building the new container. If not specified, the downloaded artifact will not be verified. Not applicable to the maven artifact type. insecure boolean By default, connections using TLS are verified to check they are secure. The server certificate used must be valid, trusted, and contain the server name. By setting this option to true , all TLS verification is disabled and the artifact will be downloaded, even when the server is considered insecure. type string Must be jar .

Commands:
Appendix D. Removing the Red Hat Virtualization Manager You can use the engine-cleanup command to remove specific components or all components of the Red Hat Virtualization Manager. Note A backup of the Manager database and a compressed archive of the PKI keys and configuration are always automatically created. These files are saved under /var/lib/ovirt-engine/backups/ , and include the date and engine- and engine-pki- in their file names respectively. Procedure Run the following command on the Manager machine: You are prompted whether to remove all Red Hat Virtualization Manager components: Type Yes and press Enter to remove all components: Type No and press Enter to select the components to remove. You can select whether to retain or remove each component individually: You are given another opportunity to change your mind and cancel the removal of the Red Hat Virtualization Manager. If you choose to proceed, the ovirt-engine service is stopped, and your environment's configuration is removed in accordance with the options you selected. Remove the Red Hat Virtualization packages:

Commands:
engine-cleanup
Do you want to remove all components? (Yes, No) [Yes]:
Do you want to remove Engine database content? All data will be lost (Yes, No) [No]: Do you want to remove PKI keys? (Yes, No) [No]: Do you want to remove PKI configuration? (Yes, No) [No]: Do you want to remove Apache SSL configuration? (Yes, No) [No]:
During execution engine service will be stopped (OK, Cancel) [OK]: ovirt-engine is about to be removed, data will be lost (OK, Cancel) [Cancel]:OK
yum remove rhvm* vdsm-bootstrap
Chapter 10. Desktop and Graphics Graphics Updates and New Hardware Support Graphics updates in Red Hat Enterprise Linux 6.5 include the following: Support for future Intel and AMD devices Spice improvements Improved multi monitor support and touch screen support Updated gdm Updates to the gdm application include fixes of password expiration messages, mutli-seat support and local interoperability problems. Upgraded Evolution The Evolution application has been upgraded to upstream version 2.32 to improve interoperability with Microsoft Exchange. This includes the new Exchange Web Service (EWS), improved meeting support and improved folder support. Rebased LibreOffice In Red Hat Enterprise Linux 6.5 release, LibreOffice has been upgraded to upstream version 4.0.4. Support for AMD GPUs Support for the latest AMD graphics processor units (GPUs) has been added to Red Hat Enterprise Linux 6.5 Alias Support in NetworkManager Alias support has been added to NetworkManager. However, users are strongly recommended to use the multiple or secondary IP feature instead.

Commands:
Chapter 10. Run Red Hat JBoss Data Grid in Library Mode (Single-Node Setup) 10.1. Create a Main Method in the Quickstart Class Create a new Quickstart class by following the outlined steps: Prerequisites These quickstarts use the Infinispan quickstarts located at https://github.com/infinispan/infinispan-quickstart . The following procedure uses the infinispan-quickstart/embedded-cache quickstart. Procedure 10.1. Create a Main Method in the Quickstart Class Create the Quickstart.java File Create a file called Quickstart.java at your project's location. Add the Quickstart Class Add the following class and method to the Quickstart.java file: Copy Dependencies and Compile Java Classes Use the following command to copy all project dependencies to a directory and compile the Java classes from your project: Run the Main Method Use the following command to run the main method: Report a bug

Commands:
package com.mycompany.app; import org.infinispan.manager.DefaultCacheManager import org.infinispan.Cache public class Quickstart { public static void main(String args[]) throws Exception { Cache<Object, Object> cache = new DefaultCacheManager().getCache(); } }
mvn clean compile dependency:copy-dependencies -DstripVersion
java -cp target/classes/:target/dependency/* com.mycompany.app.Quickstart
Chapter 42. PodDisruptionBudgetTemplate schema reference Used in: CruiseControlTemplate , KafkaBridgeTemplate , KafkaClusterTemplate , KafkaConnectTemplate , KafkaMirrorMakerTemplate , ZookeeperClusterTemplate Full list of PodDisruptionBudgetTemplate schema properties A PodDisruptionBudget (PDB) is an OpenShift resource that ensures high availability by specifying the minimum number of pods that must be available during planned maintenance or upgrades. Streams for Apache Kafka creates a PDB for every new StrimziPodSet or Deployment . By default, the PDB allows only one pod to be unavailable at any given time. You can increase the number of unavailable pods allowed by changing the default value of the maxUnavailable property. StrimziPodSet custom resources manage pods using a custom controller that cannot use the maxUnavailable value directly. Instead, the maxUnavailable value is automatically converted to a minAvailable value when creating the PDB resource, which effectively serves the same purpose, as illustrated in the following examples: If there are three broker pods and the maxUnavailable property is set to 1 in the Kafka resource, the minAvailable setting is 2 , allowing one pod to be unavailable. If there are three broker pods and the maxUnavailable property is set to 0 (zero), the minAvailable setting is 3 , requiring all three broker pods to be available and allowing zero pods to be unavailable. Example PodDisruptionBudget template configuration # ... template: podDisruptionBudget: metadata: labels: key1: label1 key2: label2 annotations: key1: label1 key2: label2 maxUnavailable: 1 # ... 42.1. PodDisruptionBudgetTemplate schema properties Property Property type Description metadata MetadataTemplate Metadata to apply to the PodDisruptionBudgetTemplate resource. maxUnavailable integer Maximum number of unavailable pods to allow automatic Pod eviction. A Pod eviction is allowed when the maxUnavailable number of pods or fewer are unavailable after the eviction. Setting this value to 0 prevents all voluntary evictions, so the pods must be evicted manually. Defaults to 1.

Commands:
template: podDisruptionBudget: metadata: labels: key1: label1 key2: label2 annotations: key1: label1 key2: label2 maxUnavailable: 1
B.99. upstart B.99.1. RHBA-2010:0848 - upstart bug fix update An updated upstart package that fixes a bug in utmp table updating is now available. Upstart is an event-based replacement for the /sbin/init daemon, which handles starting of tasks and services during boot, stopping them during shut down, and supervising them while the system is running. Bug Fix BZ# 636487 When a mingetty session is terminated, the relevant entry in the utmp table is now correctly set to "DEAD_PROCESS". All users are advised to upgrade to this updated package, which resolves this issue. Note that after installing this update, a system reboot is required for the above changes to take effect.

Commands:
8.5. Multicast Considerations When multiple applications listen to a multicast group, the kernel code that handles multicast frames is required by design to duplicate network data for each individual socket. This duplication is time-consuming and occurs in the softirq context. Adding multiple listeners on a single multicast group therefore has a direct impact on the softirq context's execution time. Adding a listener to a multicast group implies that the kernel must create an additional copy for each frame received for that group. The effect of this is minimal at low traffic volume and small listener numbers. However, when multiple sockets listen to a high-traffic multicast group, the increased execution time of the softirq context can lead to frame drops at both the network card and the socket queue. Increased softirq runtimes translate to reduced opportunity for applications to run on heavily-loaded systems, so the rate at which multicast frames are lost increases as the number of applications listening to a high-volume multicast group increases. Resolve this frame loss by optimizing your socket queues and NIC hardware buffers, as described in Section 8.4.2, "Socket Queue" or Section 8.4.1, "NIC Hardware Buffer" . Alternatively, you can optimize an application's socket use; to do so, configure the application to control a single socket and disseminate the received network data quickly to other user-space processes.

Commands:
probe::nfsd.write Name probe::nfsd.write - NFS server writing data to a file for client Synopsis nfsd.write Values offset the offset of file fh file handle (the first part is the length of the file handle) vlen read blocks file argument file, indicates if the file has been opened. client_ip the ip address of client count read bytes size read bytes vec struct kvec, includes buf address in kernel address and length of each buffer

Commands:
Index A arptables, Direct Routing Using arptables D direct routing and arptables, Direct Routing Using arptables and firewalld, Direct Routing Using firewalld F firewalld, Direct Routing Using firewalld FTP, Configuring FTP (see also Load Balancer ) H HAProxy, haproxy HAProxy and Keepalived, keepalived and haproxy J job scheduling, Keepalived , keepalived Scheduling Overview K Keepalived configuration, A Basic Keepalived configuration configuration file, Creating the keapalived.conf file initial configuration, Initial Load Balancer Configuration with Keepalived job scheduling, keepalived Scheduling Overview scheduling, job, keepalived Scheduling Overview Keepalived configuration Direct Routing, Keepalived Direct Routing Configuration keepalived daemon, keepalived keepalived.conf, Creating the keapalived.conf file Keepalivedd LVS routers primary node, Initial Load Balancer Configuration with Keepalived L least connections (see job scheduling, Keepalived ) Load Balancer direct routing and arptables, Direct Routing Using arptables and firewalld, Direct Routing Using firewalld requirements, hardware, Direct Routing , Load Balancer Using Direct Routing requirements, network, Direct Routing , Load Balancer Using Direct Routing requirements, software, Direct Routing , Load Balancer Using Direct Routing HAProxy, haproxy HAProxy and Keepalived, keepalived and haproxy Keepalived, A Basic Keepalived configuration , Keepalived Direct Routing Configuration keepalived daemon, keepalived multi-port services, Multi-port Services and Load Balancer FTP, Configuring FTP NAT routing requirements, hardware, The NAT Load Balancer Network requirements, network, The NAT Load Balancer Network requirements, software, The NAT Load Balancer Network packet forwarding, Turning on Packet Forwarding and Nonlocal Binding routing methods NAT, Routing Methods routing prerequisites, Configuring Network Interfaces for Load Balancer with NAT three-tier, A Three-Tier keepalived Load Balancer Configuration LVS NAT routing enabling, Enabling NAT Routing on the LVS Routers overview of, Load Balancer Overview real servers, Load Balancer Overview M multi-port services, Multi-port Services and Load Balancer (see also Load Balancer ) N NAT enabling, Enabling NAT Routing on the LVS Routers routing methods, Load Balancer , Routing Methods network address translation (see NAT) P packet forwarding, Turning on Packet Forwarding and Nonlocal Binding (see also Load Balancer) R real servers configuring services, Configuring Services on the Real Servers round robin (see job scheduling, Keepalived ) routing prerequisites for Load Balancer , Configuring Network Interfaces for Load Balancer with NAT S scheduling, job (Keepalived ), keepalived Scheduling Overview W weighted least connections (see job scheduling, Keepalived ) weighted round robin (see job scheduling, Keepalived )

Commands:
10.4. Managing Transport and SSL Settings Using Management CLI To manage JBoss Data Virtualization transport settings, you can use the same commands as those used for the base JBoss Data Virtualization settings, specifying a particular transport in the command. For example: Available transport names are listed under transport when you run the following command to output current JBoss Data Virtualization settings:

Commands:
/subsystem=teiid/transport= TRANSPORT_NAME :read-resource
/subsystem=teiid:read-resource
5.2.2. Block-Based Addressing Block-based addressing is much more straightforward than geometry-based addressing. With block-based addressing, every data block is given a unique number. This number is passed from the computer to the mass storage device, which then internally performs the conversion to the geometry-based address required by the device's control circuitry. Because the conversion to a geometry-based address is always done by the device itself, it is always consistent, eliminating the problem inherent with giving the device geometry-based addressing.

Commands:
7.9. Setting up a Standalone KRA or OCSP This section describes how to install a standalone KRA and OCSP. A standalone installation provides the flexibility to use a non-Certificate System CA to issue the certificates, because the CSRs generated during the installation are not automatically submitted to the CA and imported into the subsystem. Additionally, a KRA or an OCSP installed in standalone mode is not part of the CA's security domain, and the connector in the CA for key archival will not be configured. To install a standalone KRA or OCSP: Create a configuration file, such as /root/config.txt , with the following content: For a standalone KRA, add the following section to the configuration file: For a standalone OCSP, add the following section to the configuration file: To use an LDAPS connection to Directory Server running on the same host, add the following parameters to the DEFAULT section in the configuration file: Note For security reasons, Red Hat recommends using an encrypted connection to Directory Server. If you use a self-signed certificate in Directory Server, use the following command to export it from the Directory Server's Network Security Services (NSS) database: Proceed with the steps described in the section called "Starting the Installation of a Subsystem with an External CA" .

Commands:
[ DEFAULT ] pki_admin_password= password pki_client_database_password= password pki_client_pkcs12_password= password pki_ds_password= password pki_token_password= password pki_client_database_purge=False pki_security_domain_name= EXAMPLE pki_standalone=True pki_external_step_two=False
[KRA] pki_admin_email= kraadmin@example.com pki_ds_base_dn= dc=kra,dc=example,dc=com pki_ds_database= kra pki_admin_nickname= kraadmin pki_audit_signing_nickname= kra_audit_signing pki_sslserver_nickname= sslserver pki_storage_nickname= kra_storage pki_subsystem_nickname= subsystem pki_transport_nickname= kra_transport pki_standalone=True
[OCSP] pki_admin_email= ocspadmin@example.com pki_ds_base_dn= dc=ocsp,dc=example,dc=com pki_ds_database= ocsp pki_admin_nickname= ocspadmin pki_audit_signing_nickname= ocsp_audit_signing pki_ocsp_signing_nickname= ocsp_signing pki_sslserver_nickname= sslserver pki_subsystem_nickname= subsystem pki_standalone=True
pki_ds_secure_connection=True pki_ds_secure_connection_ca_pem_file= path_to_CA_or_self-signed_certificate
certutil -L -d /etc/dirsrv/slapd- instance_name / -n "server-cert" -a -o /root/ds.crt
Providing feedback on Red Hat documentation If you have a suggestion to improve this documentation, or find an error, you can contact technical support at https://access.redhat.com to open a request. Important Disclaimer : Links contained in this document to external websites are provided for convenience only. Red Hat has not reviewed the links and is not responsible for the content or its availability. The inclusion of any link to an external website does not imply endorsement by Red Hat of the website or their entities, products or services. You agree that Red Hat is not responsible or liable for any loss or expenses that may result due to your use of (or reliance on) the external site or content.

Commands:
Providing feedback on Red Hat documentation We appreciate your feedback on our documentation. Let us know how we can improve it. Use the Create Issue form in Red Hat Jira to provide your feedback. The Jira issue is created in the Red Hat Satellite Jira project, where you can track its progress. Prerequisites Ensure you have registered a Red Hat account . Procedure Click the following link: Create Issue . If Jira displays a login error, log in and proceed after you are redirected to the form. Complete the Summary and Description fields. In the Description field, include the documentation URL, chapter or section number, and a detailed description of the issue. Do not modify any other fields in the form. Click Create .

Commands:
Chapter 1. RHEL image builder description To deploy a system, create a system image. To create RHEL system images, use the RHEL image builder tool. You can use RHEL image builder to create customized system images of RHEL, including system images prepared for deployment on cloud platforms. RHEL image builder automatically handles the setup details for each output type and is therefore easier to use and faster to work with than manual methods of image creation. You can access the RHEL image builder functionalities by using the command line in the composer-cli tool, or the graphical user interface in the RHEL web console. Note From RHEL 8.3 onward, the osbuild-composer back end replaces lorax-composer . The new service provides REST APIs for image building. 1.1. RHEL image builder terminology RHEL image builder uses the following concepts: Blueprint A blueprint is a description of a customized system image. It lists the packages and customizations that will be part of the system. You can edit blueprints with customizations and save them as a particular version. When you create a system image from a blueprint, the image is associated with the blueprint in the RHEL image builder interface. Create blueprints in the TOML format. Compose Composes are individual builds of a system image, based on a specific version of a particular blueprint. Compose as a term refers to the system image, the logs from its creation, inputs, metadata, and the process itself. Customizations Customizations are specifications for the image that are not packages. This includes users, groups, and SSH keys. 1.2. RHEL image builder output formats RHEL image builder can create images in multiple output formats shown in the following table. Table 1.1. RHEL image builder output formats Description CLI name File extension QEMU Image qcow2 .qcow2 Disk Archive tar .tar Amazon Web Services raw .raw Microsoft Azure vhd .vhd Google Cloud Platform gce .tar.gz VMware vSphere vmdk .vmdk VMware vSphere ova .ova Openstack openstack .qcow2 RHEL for Edge Commit edge-commit .tar RHEL for Edge Container edge-container .tar RHEL for Edge Installer edge-installer .iso RHEL for Edge Raw Image edge-raw-image .raw.xz RHEL for Edge Simplified Installer edge-simplified-installer .iso RHEL for Edge AMI edge-ami .ami RHEL for Edge VMDK edge-vsphere .vmdk RHEL Installer image-installer .iso Oracle Cloud Infrastructure .oci .qcow2 To check the supported types, run the command: 1.3. Supported architectures for image builds RHEL image builder supports building images for the following architectures: AMD and Intel 64-bit ( x86_64 ) ARM64 ( aarch64 ) IBM Z ( s390x ) IBM POWER systems However, RHEL image builder does not support multi-architecture builds. It only builds images of the same system architecture that it is running on. For example, if RHEL image builder is running on an x86_64 system, it can only build images for the x86_64 architecture. 1.4. Additional resources RHEL image builder additional documentation index

Commands:
composer-cli compose types
Chapter 1. About networking Red Hat OpenShift Networking is an ecosystem of features, plugins and advanced networking capabilities that extend Kubernetes networking with the advanced networking-related features that your cluster needs to manage its network traffic for one or multiple hybrid clusters. This ecosystem of networking capabilities integrates ingress, egress, load balancing, high-performance throughput, security, inter- and intra-cluster traffic management and provides role-based observability tooling to reduce its natural complexities. The following list highlights some of the most commonly used Red Hat OpenShift Networking features available on your cluster: Primary cluster network provided by either of the following Container Network Interface (CNI) plugins: OVN-Kubernetes network plugin , the default plugin About the OVN-Kubernetes network plugin Certified 3rd-party alternative primary network plugins Cluster Network Operator for network plugin management Ingress Operator for TLS encrypted web traffic DNS Operator for name assignment MetalLB Operator for traffic load balancing on bare metal clusters IP failover support for high-availability Additional hardware network support through multiple CNI plugins, including for macvlan, ipvlan, and SR-IOV hardware networks IPv4, IPv6, and dual stack addressing Hybrid Linux-Windows host clusters for Windows-based workloads Red Hat OpenShift Service Mesh for discovery, load balancing, service-to-service authentication, failure recovery, metrics, and monitoring of services Single-node OpenShift Network Observability Operator for network debugging and insights Submariner for inter-cluster networking Red Hat Service Interconnect for layer 7 inter-cluster networking

Commands:
8.4.8. Adding the Optional and Supplementary Repositories Optional and Supplementary subscription channels provide additional software packages for Red Hat Enterprise Linux that cover open source licensed software (in the Optional channel) and proprietary licensed software (in the Supplementary channel). Before subscribing to the Optional and Supplementary channels see the Scope of Coverage Details . If you decide to install packages from these channels, follow the steps documented in the article called How to access Optional and Supplementary channels, and -devel packages using Red Hat Subscription Manager (RHSM)? on the Red Hat Customer Portal.

Commands: