mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 130. KafkaMirrorMakerProducerSpec schema reference Used in: KafkaMirrorMakerSpec Full list of KafkaMirrorMakerProducerSpec schema properties Configures a MirrorMaker producer. 130.1. abortOnSendFailure Use the producer.abortOnSendFailure property to configure how to handle message send failure from the producer. By default, if an error occurs when sending a message from Kafka MirrorMaker to a Kafka cluster: The Kafka MirrorMaker container is terminated in OpenShift. The container is then recreated. If the abortOnSendFailure option is set to false , message sending errors are ignored. 130.2. config Use the producer.config properties to configure Kafka options for the producer as keys. The values can be one of the following JSON types: String Number Boolean Exceptions You can specify and configure the options listed in the Apache Kafka configuration documentation for producers . However, Streams for Apache Kafka takes care of configuring and managing options related to the following, which cannot be changed: Kafka cluster bootstrap address Security (encryption, authentication, and authorization) Interceptors Properties with the following prefixes cannot be set: bootstrap.servers interceptor.classes sasl. security. ssl. If the config property contains an option that cannot be changed, it is disregarded, and a warning message is logged to the Cluster Operator log file. All other supported options are forwarded to MirrorMaker, including the following exceptions to the options configured by Streams for Apache Kafka: Any ssl configuration for supported TLS versions and cipher suites Important The Cluster Operator does not validate keys or values in the config object provided. If an invalid configuration is provided, the MirrorMaker cluster might not start or might become unstable. In this case, fix the configuration so that the Cluster Operator can roll out the new configuration to all MirrorMaker nodes. 130.3. KafkaMirrorMakerProducerSpec schema properties Property Property type Description bootstrapServers string A list of host:port pairs for establishing the initial connection to the Kafka cluster. abortOnSendFailure boolean Flag to set the MirrorMaker to exit on a failed send. Default value is true . authentication KafkaClientAuthenticationTls , KafkaClientAuthenticationScramSha256 , KafkaClientAuthenticationScramSha512 , KafkaClientAuthenticationPlain , KafkaClientAuthenticationOAuth Authentication configuration for connecting to the cluster. config map The MirrorMaker producer config. Properties with the following prefixes cannot be set: ssl., bootstrap.servers, sasl., security., interceptor.classes (with the exception of: ssl.endpoint.identification.algorithm, ssl.cipher.suites, ssl.protocol, ssl.enabled.protocols). tls ClientTls TLS configuration for connecting MirrorMaker to the cluster.

Commands:
2.8.2.2. Enabling and Disabling the Firewall Select one of the following options for the firewall: Disabled - Disabling the firewall provides complete access to your system and does no security checking. This should only be selected if you are running on a trusted network (not the Internet) or need to configure a custom firewall using the iptables command line tool. Warning Firewall configurations and any customized firewall rules are stored in the /etc/sysconfig/iptables file. If you choose Disabled and click OK , these configurations and firewall rules will be lost. Enabled - This option configures the system to reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is needed, you can choose to allow specific services through the firewall. If you are connecting your system to the Internet, but do not plan to run a server, this is the safest choice.

Commands:
13.2.3. Preparing an Initial RAM Disk Update Important This is an advanced procedure that you should consider only if you cannot perform a driver update with any other method. The Red Hat Enterprise Linux installation program can load updates for itself early in the installation process from a RAM disk - an area of your computer's memory that temporarily behaves as if it were a disk. You can use this same capability to load driver updates. To perform a driver update during installation, your computer must be able to boot from a yaboot installation server, and you must have one available on your network. Refer to Chapter 30, Setting Up an Installation Server for instructions on using a yaboot installation server. To make the driver update available on your installation server: Place the driver update image file on your installation server. Usually, you would do this by downloading it to the server from a location on the Internet specified by Red Hat or your hardware vendor. Names of driver update image files end in .iso . Copy the driver update image file into the /tmp/initrd_update directory. Rename the driver update image file to dd.img . At the command line, change into the /tmp/initrd_update directory, type the following command, and press Enter : Copy the file /tmp/initrd_update.img into the directory the holds the target that you want to use for installation. This directory is placed under the /var/lib/tftpboot/yaboot/ directory. For example, /var/lib/tftpboot/yaboot/rhel6/ might hold the yaboot installation target for Red Hat Enterprise Linux 6. Edit the /var/lib/tftpboot/yaboot/yaboot.conf file to include an entry that includes the initial RAM disk update that you just created, in the following format: Where target is the target that you want to use for installation. Refer to Section 13.3.4, "Select an Installation Server Target That Includes a Driver Update" to learn how to use an initial RAM disk update during installation. Example 13.1. Preparing an initial RAM disk update from a driver update image file In this example, driver_update.iso is a driver update image file that you downloaded from the Internet to a directory on your installation server. The target on your installation server that you want to boot from is located in /var/lib/tftpboot/yaboot/rhel6/ At the command line, change to the directory that holds the file and enter the following commands: Edit the /var/lib/tftpboot/yaboot/yaboot.conf file and include the following entry:

Commands:
find . | cpio --quiet -o -H newc | gzip -9 >/tmp/initrd_update.img
image= target /vmlinuz label= target -dd initrd= target /initrd.img, target /dd.img
cp driver_update.iso /tmp/initrd_update/dd.img cd /tmp/initrd_update find . | cpio --quiet -c -o -H newc | gzip -9 >/tmp/initrd_update.img cp /tmp/initrd_update.img /tftpboot/yaboot/rhel6/dd.img
image=rhel6/vmlinuz label=rhel6-dd initrd=rhel6/initrd.img,rhel6/dd.img
Framework for upgrades (16.2 to 17.1) Red Hat OpenStack Platform 17.1 In-place upgrades from Red Hat OpenStack Platform 16.2 to 17.1 OpenStack Documentation Team rhos-docs@redhat.com Abstract This guide contains information on the framework for the in-place upgrades across long-life versions. This framework includes tools to upgrade your OpenStack Platform environment from one long life version to the long life version. In this case, the guide focuses on upgrading from Red Hat OpenStack Platform 16.2 (Train) to 17.1 (Wallaby).

Commands:
Appendix G. Revision History Revision History Revision 6.6.0-7 Wed Jun 28 2017 John Brier JDG-982: Removed Important box with references to unsupported mixed mode cluster. Revision 6.6.0-6 Thur May 25 2017 John Brier JDG-984: Added links to protocol interoperability to match Developer Guide Revision 6.6.0-5 Fri Apr 28 2017 John Brier BZ-1445952: Clarified the differences between reaper thread in Remote Client-Server Mode and Library Mode. Also changed wakeUpInterval to interval in C/S mode. Revision 6.6.0-4 Wed Sep 7 2016 Christian Huffman Updating for 6.6.1. Revision 6.6.0-3 Thu Mar 10 2016 Christian Huffman Included section on Google Compute Engine. Revision 6.6.0-2 Thu Mar 10 2016 Christian Huffman BZ-1313478: Included all possible configurations for datasources. BZ-1315900: Added chapter on configuring JBoss Data Grid with Microsoft Azure. Revision 6.6.0-1 Wed Feb 24 2016 Christian Huffman BZ-1310604: Clarified the versions in which externalization of HTTP sessions is supported. Revision 6.6.0-0 Thu 7 Jan 2016 Christian Huffman , Rakesh Ghatvisve Initial draft for 6.6.0. BZ-1269547: Documented Hot Rod Cross Site Failover. BZ-1269548: Documented eviction maximum entries configuration. Updated versions.

Commands:
Chapter 6. Fixed Common Vulnerabilities and Exposures This section details Common Vulnerabilities and Exposures (CVEs) fixed in the AMQ Broker 7.8 release. ENTMQBR-3755 - CVE-2020-13932 - mqtt-client: activemq: remote XSS in web console diagram plugin [amq-7] ENTMQBR-3382 - CVE-2015-5183 Hawtio: HTTPOnly and Secure attributes not set on cookies [amq-7] ENTMQBR-4037 - CVE-2019-12749 - DBusServer DBUS_COOKIE_SHA1 authentication bypass ENTMQBR-4068 - CVE-2019-9827 - hawtio: server side request forgery via initial /proxy/ substring of a URI [amq-7.7.0] ENTMQBR-4158 - CVE-2020-27216 - jetty: local temporary directory hijacking vulnerability [amq-7]

Commands:
Chapter 1. Key features Red Hat Service Interconnect is a Red Hat build of the open source Skupper project. Skupper introduces a service network, linking services across the hybrid cloud. A service network enables communication between services running in different network locations. It allows geographically distributed services to connect as if they were all running in the same site. The following are key features of Skupper: Private to public site connectivity: You expose only specific services and ports to a remote site. Minimal effort: A few skupper CLI commands to expose services from one site to another. Security: mTLS for all cross site communication. Load balancing and failover of services.

Commands:
probe::tcpmib.OutSegs Name probe::tcpmib.OutSegs - Count the sending of a TCP segment Synopsis tcpmib.OutSegs Values sk pointer to the struct sock being acted on op value to be added to the counter (default value of 1) Description The packet pointed to by skb is filtered by the function tcpmib_filter_key . If the packet passes the filter is is counted in the global OutSegs (equivalent to SNMP's MIB TCP_MIB_OUTSEGS)

Commands:
Chapter 3. Using the OpenShift Container Platform dashboard to get cluster information The OpenShift Container Platform web console captures high-level information about the cluster. 3.1. About the OpenShift Container Platform dashboards page Access the OpenShift Container Platform dashboard, which captures high-level information about the cluster, by navigating to Home Overview from the OpenShift Container Platform web console. The OpenShift Container Platform dashboard provides various cluster information, captured in individual dashboard cards. The OpenShift Container Platform dashboard consists of the following cards: Details provides a brief overview of informational cluster details. Status include ok , error , warning , in progress , and unknown . Resources can add custom status names. Cluster ID Provider Version Cluster Inventory details number of resources and associated statuses. It is helpful when intervention is required to resolve problems, including information about: Number of nodes Number of pods Persistent storage volume claims Bare metal hosts in the cluster, listed according to their state (only available in metal3 environment) Status helps administrators understand how cluster resources are consumed. Click on a resource to jump to a detailed page listing pods and nodes that consume the largest amount of the specified cluster resource (CPU, memory, or storage). Cluster Utilization shows the capacity of various resources over a specified period of time, to help administrators understand the scale and frequency of high resource consumption, including information about: CPU time Memory allocation Storage consumed Network resources consumed Pod count Activity lists messages related to recent activity in the cluster, such as pod creation or virtual machine migration to another host. 3.2. Recognizing resource and project limits and quotas You can view a graphical representation of available resources in the Topology view of the web console Developer perspective. If a resource has a message about resource limitations or quotas being reached, a yellow border appears around the resource name. Click the resource to open a side panel to see the message. If the Topology view has been zoomed out, a yellow dot indicates that a message is available. If you are using List View from the View Shortcuts menu, resources appear as a list. The Alerts column indicates if a message is available.

Commands:
1.2. New and Changed Features This section lists new and changed features of the GFS2 file system and the GFS2 documentation that are included with the initial and subsequent releases of Red Hat Enterprise Linux 7. 1.2.1. New and Changed Features for Red Hat Enterprise Linux 7.0 Red Hat Enterprise Linux 7.0 includes the following documentation and feature updates and changes. For Red Hat Enterprise Linux 7, a cluster that includes a GFS2 file system requires that you configure your cluster with Pacemaker according to the procedure described in Chapter 5, Configuring a GFS2 File System in a Cluster . The gfs2_tool command is not supported in Red Hat Enterprise Linux 7. Replacement functions for the gfs2_tool are summarized in Section 1.5, "Replacement Functions for gfs2_tool in Red Hat Enterprise Linux 7" . 1.2.2. New and Changed Features for Red Hat Enterprise Linux 7.1 For Red Hat Enterprise Linux 7.1, Appendix A, GFS2 Performance Analysis with Performance Co-Pilot has been updated. In addition, small technical corrections and clarifications have been made throughout the document. 1.2.3. New and Changed Features for Red Hat Enterprise Linux 7.2 Small technical corrections and clarifications have been made throughout the document. 1.2.4. New and Changed Features for Red Hat Enterprise Linux 7.4 As of Red Hat Enterprise Linux 7.4, Security Enhanced Linux (SELinux) is supported for use with GFS2 file systems. For information on SELinux and GFS2, see Section 2.5.3, "SELinux on GFS2" .

Commands:
Chapter 11. Viewing diagnostics Use the Diagnostics tab to view diagnostic information about the JVM via the JVM DiagnosticCommand and HotspotDiangostic interfaces. Note The functionality is similar to the Diagnostic Commands view in Java Mission Control (jmc) or the command line tool jcmd. The plugin will provide corresponding jcmd commands in some scenarios. Procedure To retrieve the number of instances of loaded classes and the amount of bytes they take up, click Class Histogram . If the operation is repeated, the tab shows the difference since last run. To view the JVM diagnostic flag setting, click the JVM flags . For a running JVM, you can also modify the flag settings. Additional resources The supported JVM depends on the platform, for more information go to one of the following sources: http://www.oracle.com/technetwork/java/vmoptions-jsp-140102.html http://openjdk.java.net/groups/hotspot/docs/RuntimeOverview.html

Commands:
4.9.4. Specifying Units To specify the unit for the LVM report display, use the --units argument of the report command. You can specify (b)ytes, (k)ilobytes, (m)egabytes, (g)igabytes, (t)erabytes, (e)xabytes, (p)etabytes, and (h)uman-readable. The default display is human-readable. You can override the default by setting the units parameter in the global section of the lvm.conf file. The following example specifies the output of the pvs command in megabytes rather than the default gigabytes. By default, units are displayed in powers of 2 (multiples of 1024). You can specify that units be displayed in multiples of 1000 by capitalizing the unit specification (B, K, M, G, T, H). The following command displays the output as a multiple of 1024, the default behavior. The following command displays the output as a multiple of 1000. You can also specify (s)ectors (defined as 512 bytes) or custom units. The following example displays the output of the pvs command as a number of sectors. The following example displays the output of the pvs command in units of 4 megabytes.

Commands:
pvs --units m PV VG Fmt Attr PSize PFree /dev/sda1 lvm2 -- 17555.40M 17555.40M /dev/sdb1 new_vg lvm2 a- 17552.00M 17552.00M /dev/sdc1 new_vg lvm2 a- 17552.00M 17500.00M /dev/sdd1 new_vg lvm2 a- 17552.00M 17552.00M
pvs PV VG Fmt Attr PSize PFree /dev/sdb1 new_vg lvm2 a- 17.14G 17.14G /dev/sdc1 new_vg lvm2 a- 17.14G 17.09G /dev/sdd1 new_vg lvm2 a- 17.14G 17.14G
pvs --units G PV VG Fmt Attr PSize PFree /dev/sdb1 new_vg lvm2 a- 18.40G 18.40G /dev/sdc1 new_vg lvm2 a- 18.40G 18.35G /dev/sdd1 new_vg lvm2 a- 18.40G 18.40G
pvs --units s PV VG Fmt Attr PSize PFree /dev/sdb1 new_vg lvm2 a- 35946496S 35946496S /dev/sdc1 new_vg lvm2 a- 35946496S 35840000S /dev/sdd1 new_vg lvm2 a- 35946496S 35946496S
pvs --units 4m PV VG Fmt Attr PSize PFree /dev/sdb1 new_vg lvm2 a- 4388.00U 4388.00U /dev/sdc1 new_vg lvm2 a- 4388.00U 4375.00U /dev/sdd1 new_vg lvm2 a- 4388.00U 4388.00U
4.2. Tracking Entry Modifications through Operational Attributes Using the default settings, Directory Server tracks the following operational attributes for every entry: creatorsName : The distinguished name (DN) of the user who initially created the entry. createTimestamp : The times stamp in Greenwich Mean Time (GMT) format when the entry was created. modifiersName : The distinguished name of the user who last modified the entry. modifyTimestamp : The time stamp in the GMT format for when the entry was last modified. Note that operational attributes are not returned in default searches. You must explicitly request these attributes in queries. For details, see Section 14.4.7, "Searching for Operational Attributes" . Important Red Hat recommends not disabling tracking these operational attributes. If disabled, entries do not get a unique ID assigned in the nsUniqueID attribute and replication does not work. 4.2.1. Entries Modified or Created by a Database Link When an entry is created or modified over a database link, the creatorsName and modifiersName attributes contain the name of the user who is granted proxy authorization rights on the remote server. In this case, the attributes do not display the original creator or latest modifier of the entry. However, the access logs show both the proxy user ( dn ) and the original user ( authzid ). For example: 4.2.2. Enabling Tracking of Modifications By default, Directory Server tracks modifications in operational attributes. Note Red Hat recommends not disabling this feature. This section describes how to re-enable tracking of modifications in case that you disabled the feature. 4.2.2.1. Enabling Tracking Of Modifications Using the Command Line To re-enable tracking of entry modifications using the command line: Set the nsslapd-lastmod parameter to on : Optionally, to regenerate the missing nsUniqueID attributes: Export the database into an LDAP Data Interchange Format (LDIF) file. See Section 6.2.1, "Exporting Data into an LDIF File Using the Command Line" . Import the database from the LDIF file. See Section 6.1.2, "Importing Using the Command Line" .

Commands:
[23/May/2018:18:13:56.145747965 +051800] conn=1175 op=0 BIND dn="cn=proxy admin,ou=People,dc=example,dc=com" method=128 version=3 [23/May/2018:18:13:56.575439751 +051800] conn=1175 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=proxy admin,ou=people,dc=example,dc=com" [23/May/2018:18:13:56.744359706 +051800] conn=1175 op=1 SRCH base="dc=example,dc=com" scope=2 filter="(objectClass=*)" attrs=ALL authzid="uid=user_name,ou=People,dc=example,dc=com"
dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-lastmod=on
Installing on OCI OpenShift Container Platform 4.14 Installing OpenShift Container Platform on Oracle Cloud Infrastructure Red Hat OpenShift Documentation Team

Commands:
Error: 400-InvalidParameter, DNS Label oci-demo does not follow Oracle requirements Suggestion: Please update the parameter(s) in the Terraform config as per error message DNS Label oci-demo does not follow Oracle requirements Documentation: https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/core_vcn
./openshift-install version
./openshift-install 4.15.0 built from commit ae7977b7d1ca908674a0d45c5c243c766fa4b2ca release image registry.ci.openshift.org/origin/release:4.15ocp-release@sha256:0da6316466d60a3a4535d5fed3589feb0391989982fba59d47d4c729912d6363 release architecture amd64
install-config.yaml apiVersion: v1 baseDomain: <base_domain> 1 networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 network type: OVNKubernetes machineNetwork: - cidr: <ip_address_from_cidr> 2 serviceNetwork: - 172.30.0.0/16 compute: - architecture: amd64 3 hyperthreading: Enabled name: worker replicas: 0 controlPlane: architecture: amd64 4 hyperthreading: Enabled name: master replicas: 3 platform: external: platformName: oci 5 cloudControllerManager: External sshKey: <public_ssh_key> 6 pullSecret: '<pull_secret>' 7
./openshift-install agent create image --log-level debug
apiVersion: v1alpha1 metadata: name: <cluster_name> 1 namespace: <cluster_namespace> 2 rendezvousIP: <ip_address_from_CIDR> 3 bootArtifactsBaseURL: <server_URL> 4
./openshift-install agent wait-for install-complete --log-level debug
export KUBECONFIG=~/auth/kubeconfig
oc get nodes -A
NAME STATUS ROLES AGE VERSION main-0.private.agenttest.oraclevcn.com Ready control-plane, master 7m v1.27.4+6eeca63 main-1.private.agenttest.oraclevcn.com Ready control-plane, master 15m v1.27.4+d7fa83f main-2.private.agenttest.oraclevcn.com Ready control-plane, master 15m v1.27.4+d7fa83f
oc get co
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE authentication 4.15.0-0 True False False 6m18s baremetal 4.15.0-0 True False False 2m42s network 4.15.0-0 True True False 5m58s Progressing: ... ...