mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Configuring encryption Configure encryption for your Data Grid. 4.1. Enabling TLS encryption Encryption can be independently enabled for endpoint and cluster transport. Prerequisites A secret containing a certificate or a keystore. Endpoint and cluster should use different secrets. A credentials keystore containing any password needed to access the keystore. See Adding credentials keystore . Procedure Set the secret name in the deploy configuration. Provide the name of the secret containing the keystore: deploy: ssl: endpointSecretName: "tls-secret" transportSecretName: "tls-transport-secret" Enable cluster transport TLS. deploy: infinispan: cacheContainer: transport: urn:infinispan:server:15.0:securityRealm: > "cluster-transport" 1 server: security: securityRealms: - name: cluster-transport serverIdentities: ssl: keystore: 2 alias: "server" path: "/etc/encrypt/transport/cert.p12" credentialReference: 3 store: credentials alias: keystore truststore: 4 path: "/etc/encrypt/transport/cert.p12" credentialReference: 5 store: credentials alias: truststore 1 Configures the transport stack to use the specified security-realm to provide cluster encryption. 2 Configure the keystore path in the transport realm. The secret is mounted at /etc/encrypt/transport . 3 5 Configures the truststore with the same keystore allowing the nodes to authenticate each other. 4 Alias and password must be provided in case the secret contains a keystore. Enable endpoint TLS. deploy: infinispan: server: security: securityRealms: - name: default serverIdentities: ssl: keystore: path: "/etc/encrypt/endpoint/keystore.p12" 1 alias: "server" 2 credentialReference: store: credentials 3 alias: keystore 4 1 Configure the keystore path in the endpoint realm; secret is mounted at /etc/encrypt/endpoint . 2 Alias must be provided in case the secret contains a keystore. 3 4 Any password must be provided with via credentials keystore. Additional resources Data Grid Security Guide

Commands:
deploy: ssl: endpointSecretName: "tls-secret" transportSecretName: "tls-transport-secret"
deploy: infinispan: cacheContainer: transport: urn:infinispan:server:15.0:securityRealm: > "cluster-transport" 1 server: security: securityRealms: - name: cluster-transport serverIdentities: ssl: keystore: 2 alias: "server" path: "/etc/encrypt/transport/cert.p12" credentialReference: 3 store: credentials alias: keystore truststore: 4 path: "/etc/encrypt/transport/cert.p12" credentialReference: 5 store: credentials alias: truststore
deploy: infinispan: server: security: securityRealms: - name: default serverIdentities: ssl: keystore: path: "/etc/encrypt/endpoint/keystore.p12" 1 alias: "server" 2 credentialReference: store: credentials 3 alias: keystore 4
Chapter 7. Using the dynamic plugins cache The dynamic plugins cache in Red Hat Developer Hub (RHDH) enhances the installation process and reduces platform boot time by storing previously installed plugins. If the configuration remains unchanged, this feature prevents the need to re-download plugins on subsequent boots. When you enable dynamic plugins cache: The system calculates a checksum of each plugin's YAML configuration (excluding pluginConfig ). The checksum is stored in a file named dynamic-plugin-config.hash within the plugin's directory. During boot, if a plugin's package reference matches the installation and the checksum is unchanged, the download is skipped. Plugins that are disabled since the boot are automatically removed. 7.1. Enabling the dynamic plugins cache To enable the dynamic plugins cache in RHDH, the plugins directory dynamic-plugins-root must be a persistent volume. For Helm chart installations, a persistent volume named dynamic-plugins-root is automatically created. For operator-based installations, you must manually create the PersistentVolumeClaim (PVC) as follows: kind: PersistentVolumeClaim apiVersion: v1 metadata: name: dynamic-plugins-root spec: accessModes: - ReadWriteOnce resources: requests: storage: 5Gi --- apiVersion: rhdh.redhat.com/v1alpha2 kind: Backstage metadata: name: developer-hub spec: deployment: patch: spec: template: spec: volumes: - USDpatch: replace name: dynamic-plugins-root persistentVolumeClaim: claimName: dynamic-plugins-root Note Future versions of the RHDH operator are planned to automatically create the PVC. 7.2. Configuring the dynamic plugins cache You can set the following optional dynamic plugin cache parameters: forceDownload : Set to true to force a reinstall of the plugin, bypassing the cache. Default is false . For example, modify your dynamic-plugins.yaml file as follows: plugins: - disabled: false forceDownload: true package: 'oci://quay.io/example-org/example-plugin:v1.0.0!internal-backstage-plugin-example'

Commands:
kind: PersistentVolumeClaim apiVersion: v1 metadata: name: dynamic-plugins-root spec: accessModes: - ReadWriteOnce resources: requests: storage: 5Gi --- apiVersion: rhdh.redhat.com/v1alpha2 kind: Backstage metadata: name: developer-hub spec: deployment: patch: spec: template: spec: volumes: - USDpatch: replace name: dynamic-plugins-root persistentVolumeClaim: claimName: dynamic-plugins-root
plugins: - disabled: false forceDownload: true package: 'oci://quay.io/example-org/example-plugin:v1.0.0!internal-backstage-plugin-example'
Chapter 22. IBM Z References 22.1. IBM Z Publications Current versions of the Linux on IBM Z publications can be found at http://www.ibm.com/developerworks/linux/linux390/documentation_red_hat.html . They include: Linux on System z - How to use FC-attached SCSI devices with Linux on System z9 and zSeries . IBM . 2008. SC33-8413. Linux on System z - How to Improve Performance with PAV . IBM . 2008. SC33-8414. z/VM - Getting Started with Linux on System z . IBM . 2009. SC24-6194.

Commands:
18.3.2. Installation using X11 The direct connection from the X11 client to an X11 server on your local workstation requires an IP connection from your System z to your workstation. If the network and firewalls prevent such connections, use X11 forwarding or VNC instead. The graphical installation program requires the DNS and hostname to be set correctly, and the Linux installation system must be allowed to open applications on your display. You can ensure this by setting the parameter display=workstationname:0.0 in the parameter file, where workstationname is the hostname of the client workstation connecting to the Linux image. Alternatively, you can set the display environment variable and run loader manually after having logged in with SSH as user root . By default you log in as user install . This starts the loader automatically and does not allow overriding the display environment variable. To permit X11 clients to open applications on the X11 server on your workstation, use the xauth command. To manage X11 authorization cookies with xauth , you must log in to the Linux installation system using SSH as user root . For details on xauth and how to manage authorization cookies, refer to the xauth manpage. In contrast to setting up X11 authorizations with xauth , you can use xhost to permit the Linux installation system to connect to the X11 server: Replace linuxvm with the hostname or IP address of the Linux installation system. This allows linuxvm to make connections to the X11 server. If the graphical installation does not begin automatically, verify the display= variable settings in the parameter file. If performing an installation under z/VM, rerun the installation to load the new parameter file on the reader.

Commands:
xhost + linuxvm
5.4. Custom Listeners for Embedded Cache Custom Listeners for an embedded cache can be registered through the customListener parameter as shown below: Using Java Using Blueprint The instance of myCustomListener must exist. Users are encouraged to extend the org.apache.camel.component.infinispan.embedded.InfinispanEmbeddedCustomListener and annotate the resulting class with the @Listener annotation from org.infinispan.notifications . Note Custom filters and converters for embedded caches are currently not supported. Report a bug

Commands:
from("infinispan://?cacheContainer=#myCustomContainer&cacheName=customCacheName&customListener=#myCustomListener") .to("mock:result");
<bean id="myCustomContainer" org.infinispan.manager.DefaultCacheManager" init-method="start" destroy-method="stop"> <argument value="infinispan.xml" /> </bean> <bean id="myCustomListener" class="org.example.com.CustomListener"/> <camelContext id="route" xmlns="http://camel.apache.org/schema/blueprint"> <route> <from uri="infinispan://?cacheContainer=#myCustomContainer&cacheName=customCacheName&customListener=#myCustomListener"/> <to uri="mock:result"/> </route> </camelContext>
Chapter 6. Known issues This section lists the known issues for AMQ Streams 1.8. 6.1. SMTP appender for log4j AMQ Streams ships with a potentially vulnerable version of log4j ( log4j-1.2.17.redhat-3 ). The vulnerability lies with the SMTP appender functionality, which is not used by AMQ Streams in its default configuration. Table 6.1. CVE issue Issue Number Description ENTMQST-1934 CVE-2020-9488 log4j: improper validation of certificate with host mismatch in SMTP appender [amq-st-1]. Workaround If you are using the SMTP appender, ensure that mail.smtp.ssl.checkserveridentity is set to true .

Commands:
Chapter 1. Understanding the Web Console 1.1. Understanding the oVirt Machines tab The oVirt Machines tab provides an overview of the virtual machines running in the hyperconverged cluster. To view this tab, browse to the Web Console interface for your server (for example, http://server1.example.com:9090 ), log in, and click the hostname and oVirt Machines . The oVirt Machines tab This tab is divided into a number of subtabs. Host The Host subtab shows information about virtual machines that are available on this hyperconverged host. Clicking on each virtual machine shows a summary of that machine, as well as various management operations. See Managing virtual machines using the Web Console for more information about virtual machine operations. Cluster The Cluster subtab shows information about virtual machines that are available in the hyperconverged cluster. The Host column lets you easily navigate to the appropriate location for managing each virtual machine. The Action column shows any operations you can perform from this hyperconverged host. The Cluster subtab Templates The Templates subtab shows the template images that you can use to create new virtual machines. The Templates subtab VDSM The VDSM subtab shows the current contents of the vdsm.conf file and provides an easy way to edit the file's contents. See VDSM and Hooks in the Red Hat Virtualization 4.4 documentation for more information about VDSM. The VDSM subtab 1.2. Understanding the virtual machine summary In the Web Console, the Host subtab on the oVirt Machines tab shows information about virtual machines that are available on this hyperconverged host. Clicking on each virtual machine shows a summary of that machine, as well as various management operations. The summary is divided into a number of sections that display different types of information and operations. Overview This section shows basic information about the virtual machine's compute resources and capabilities. The Overview section of the virtual machine summary Usage This section shows the memory and CPU usage of this virtual machine. The Usage section of the virtual machine summary Disks This section shows details about the storage devices available to this virtual machine. The Disks section of the virtual machine summary Console This section shows options for connecting to the console of the virtual machine. Graphics Console (VNC) Graphics Console in Desktop Viewer oVirt This section shows virtualization related information about the virtual machine and provides a way to migrate the virtual machine to another hyperconverged host. See Migrating a virtual machine to a different hyperconverged host using the Web Console for more details about migrating virtual machines. The oVirt section of the virtual machine summary See Managing virtual machines using the Web Console for more information about any of the virtual machine operations mentioned in this section.

Commands:
Chapter 6. Maintenance procedures 6.1. Update RHEL and the RHEL HA Add-On Please refer to Recommendations: Applying package updates in a RHEL High Availability cluster , for more information. Note For two-node cluster setups it is not necessary to manually move the resources to the other HA cluster node before placing the HA cluster node in standby mode (putting the HA cluster node in standby mode will take care of moving or stopping the resources running on the HA cluster node based on the HA cluster configuration). Also, to minimize downtime of the SAP system it is recommended to first update the HA cluster node running the "less critical" resources, like the ERS instance. When the HA cluster node has been updated and it has been verified that the resources that were running on the node before the update was started are running again, the other HA cluster node running the "critical" resources, like the (A)SCS instance, can be updated as well.

Commands:
14.5.4. Editing and Displaying a Description and Title of a Domain The following command is used to show or modify the description and title of a domain, but does not configure it: These values are user fields that allow storage of arbitrary textual data to allow easy identification of domains. Ideally, the title should be short, although this is not enforced by libvirt. The options --live or --config select whether this command works on live or persistent definitions of the domain. If both --live and --config are specified, the --config option will be implemented first, where the description entered in the command becomes the new configuration setting which is applied to both the live configuration and persistent configuration setting. The --current option will modify or get the current state configuration and will not be persistent. The --current option will be used if neither --live nor --config , nor --current are specified. The --edit option specifies that an editor with the contents of current description or title should be opened and the contents saved back afterwards. Using the --title option will show or modify the domain's title field only and not include its description. In addition, if neither --edit nor --new-desc are used in the command, then only the description is displayed and cannot be modified. For example, the following command changes the guest virtual machine's title from testvm to TestVM-4F and will change the description to Guest VM on fourth floor :

Commands:
virsh desc [domain-name] [[ --live ] [ --config ] | [ --current ]] [ --title ] [ --edit ] [ --new-desc New description or title message]
virsh desc testvm --current --title TestVM-4F --new-desc Guest VM on fourth floor
1.5. Tags 1.5.1. Using Tags to Customize Interactions with Red Hat Virtualization After your Red Hat Virtualization platform is set up and configured to your requirements, you can customize the way you work with it using tags. Tags allow system resources to be arranged into groups or categories. This is useful when many objects exist in the virtualization environment and the administrator wants to concentrate on a specific set of them. This section describes how to create and edit tags, assign them to hosts or virtual machines and search using the tags as criteria. Tags can be arranged in a hierarchy that matches a structure, to fit the needs of the enterprise. To create, modify, and remove Administration Portal tags, click the Tags icon ( ) in the header bar. 1.5.2. Creating a Tag Create tags so you can filter search results using tags. Procedure Click the Tags icon ( ) in the header bar. Click Add to create a new tag, or select a tag and click New to create a descendant tag. Enter the Name and Description of the new tag. Click OK . 1.5.3. Modifying a Tag You can edit the name and description of a tag. Modifying a Tag Click the Tags icon ( ) in the header bar. Select the tag you want to modify and click Edit . Change the Name and Description fields as necessary. Click OK . 1.5.4. Deleting a Tag When a tag is no longer needed, remove it. Procedure Click the Tags icon ( ) in the header bar. Select the tag you want to delete and click Remove . A message warns you that removing the tag will also remove all descendants of the tag. Click OK . You have removed the tag and all its descendants. The tag is also removed from all the objects that it was attached to. 1.5.5. Adding and Removing Tags to and from Objects You can assign tags to and remove tags from hosts, virtual machines, and users. Procedure Select the object(s) you want to tag or untag. Click More Actions ( ), then click Assign Tags . Select the check box to assign a tag to the object, or clear the check box to detach the tag from the object. Click OK . The specified tag is now added or removed as a custom property of the selected object(s). 1.5.6. Searching for Objects Using Tags Enter a search query using tag as the property and the desired value or set of values as criteria for the search. The objects tagged with the specified criteria are listed in the results list. Note If you search for objects using tag as the property and the inequality operator ( != ), for example, Host: Vms.tag!=server1 , the results list does not include untagged objects. 1.5.7. Customizing Hosts with Tags You can use tags to store information about your hosts. You can then search for hosts based on tags. For more information on searches, see Searches . Procedure Click Compute Hosts and select a host. Click More Actions ( ), then click Assign Tags . Select the check boxes of applicable tags. Click OK . You have added extra, searchable information about your host as tags.

Commands:
B.9. compat-dapl B.9.1. RHBA-2011:0343 - compat-dapl bug fix update Updated compat-dapl packages that fix a bug are now available for Red Hat Enterprise Linux 6. The DAT programming API provides a means of utilizing high performance network technologies, such as InfiniBand and iWARP, without needing to write your program to use those technologies directly. This package contains the libraries that implement version 1.2 of the DAT API. The current (and recommended version for any new code) is 2.0. These 1.2 libraries are provided solely for backward compatibility. Bug Fix BZ# 673992 Under certain error conditions, an error in the code path in compat-dapl did not allow the cp_ptr entry to be cleaned up correctly in the internal link list. This could cause new connections to fail. This update includes a backported fix from uDAPL 2.0 which ensures the entry is cleaned up correctly and subsequent connections work as expected. Users should upgrade to these updated packages, which fix this bug.

Commands:
9.6. Setting the Minimum TLS Encryption Protocol Version By default, Directory Server sets sslVersionMin parameter automatically based on the system-wide crypto policy. The following table provides an overview of the TLS version in sslVersionMin Directory Server uses based on the system-wide crypto policy profile: Table 9.2. Overview of System-wide Crypto Policy Profiles and the Minimum TLS Version They Define Profile Minimum TLS Version DEFAULT TLS 1.2 FUTURE TLS 1.2 FIPS TLS 1.2 LEGACY TLS 1.0 For further details about system-wide crypto policy, how to change the profile, and opting-out services of system-wide crypto policies, see the Using system-wide cryptographic policies section in the RHEL 8 Security Hardening guide. Alternatively, you can manually set sslVersionMin to higher value than the one defined in the crypto policy profile:

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com security set --tls-protocol-min="TLS1.3"
Chapter 1. Introduction to AMQ Broker on OpenShift Container Platform Red Hat AMQ Broker 7.11 is available as a containerized image for use with OpenShift Container Platform (OCP) 4.12, 4.13, 4.14 or 4.15. AMQ Broker is based on Apache ActiveMQ Artemis. It provides a message broker that is JMS-compliant. After you have set up the initial broker pod, you can quickly deploy duplicates by using OpenShift Container Platform features. 1.1. Version compatibility and support For details about OpenShift Container Platform image version compatibility, see: OpenShift Container Platform 4.x Tested Integrations Note All deployments of AMQ Broker on OpenShift Container Platform now use RHEL 8 based images. 1.2. Unsupported features Master-slave-based high availability High availability (HA) achieved by configuring master and slave pairs is not supported. Instead, AMQ Broker uses the HA capabilities provided in OpenShift Container Platform. External clients cannot use the topology information provided by AMQ Broker When an AMQ Core Protocol JMS Client or an AMQ JMS Client connects to a broker in an OpenShift Container Platform cluster, the broker can send the client the IP address and port information for each of the other brokers in the cluster, which serves as a failover list for clients if the connection to the current broker is lost. The IP address provided for each broker is an internal IP address, which is not accessible to clients that are external to the OpenShift Container Platform cluster. To prevent external clients from trying to connect to a broker using an internal IP address, set the following configuration in the URI used by the client to initially connect to a broker. Client Configuration AMQ Core Protocol JMS Client useTopologyForLoadBalancing=false AMQ JMS Client failover.amqpOpenServerListAction=IGNORE 1.3. Document conventions This document uses the following conventions for the sudo command, file paths, and replaceable values. The sudo command In this document, sudo is used for any command that requires root privileges. You should always exercise caution when using sudo , as any changes can affect the entire system. For more information about using sudo , see Managing sudo access . About the use of file paths in this document In this document, all file paths are valid for Linux, UNIX, and similar operating systems (for example, /home/... ). If you are using Microsoft Windows, you should use the equivalent Microsoft Windows paths (for example, C:\Users\... ). Replaceable values This document sometimes uses replaceable values that you must replace with values specific to your environment. Replaceable values are lowercase, enclosed by angle brackets ( < > ), and are styled using italics and monospace font. Multiple words are separated by underscores ( _ ) . For example, in the following command, replace <project_name> with your own project name. USD oc new-project <project_name>

Commands:
oc new-project <project_name>