mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Adding user preferences You can change the default preferences for your profile to meet your requirements. You can set your default project, topology view (graph or list), editing medium (form or YAML), language preferences, and resource type. The changes made to the user preferences are automatically saved. 4.1. Setting user preferences You can set the default user preferences for your cluster. Procedure Log in to the OpenShift Container Platform web console using your login credentials. Use the masthead to access the user preferences under the user profile. In the General section: In the Theme field, you can set the theme that you want to work in. The console defaults to the selected theme each time you log in. In the Perspective field, you can set the default perspective you want to be logged in to. You can select the Administrator or the Developer perspective as required. If a perspective is not selected, you are logged into the perspective you last visited. In the Project field, select a project you want to work in. The console defaults to the project every time you log in. In the Topology field, you can set the topology view to default to the graph or list view. If not selected, the console defaults to the last view you used. In the Create/Edit resource method field, you can set a preference for creating or editing a resource. If both the form and YAML options are available, the console defaults to your selection. In the Language section, select Default browser language to use the default browser language settings. Otherwise, select the language that you want to use for the console. In the Notifications section, you can toggle display notifications created by users for specific projects on the Overview page or notification drawer. In the Applications section: You can view the default Resource type . For example, if the OpenShift Serverless Operator is installed, the default resource type is Serverless Deployment . Otherwise, the default resource type is Deployment . You can select another resource type to be the default resource type from the Resource Type field.

Commands:
2.4. Saving a Configuration Change to a File When using the pcs command, you can use the -f option to save a configuration change to a file without affecting the active CIB. If you have previously configured a cluster and there is already an active CIB, you use the following command to save the raw xml a file. For example, the following command saves the raw xml from the CIB into a file name testfile . The following command creates a resource in the file testfile1 but does not add that resource to the currently running cluster configuration. You can push the current content of testfile to the CIB with the following command.

Commands:
pcs cluster cib filename
pcs cluster cib testfile
pcs -f testfile1 resource create VirtualIP ocf:heartbeat:IPaddr2 ip=192.168.0.120 cidr_netmask=24 op monitor interval=30s
pcs cluster cib-push filename
24.3. Problems After Installation 24.3.1. Remote Graphical Desktops and XDMCP If you have installed the X Window System and would like to log in to your Red Hat Enterprise Linux system using a graphical login manager, enable the X Display Manager Control Protocol (XDMCP). This protocol allows users to remotely log in to a desktop environment from any X Window System compatible client (such as a network-connected workstation or X11 terminal). To enable remote login using XDMCP, edit the /etc/gdm/custom.conf file on the Red Hat Enterprise Linux system with a text editor such as vi or nano . In the [xdcmp] section, add the line Enable=true , save the file, and exit the text editor. To enable this change, you will need to restart the X Window System. First, switch to runlevel 4: The graphical display will close, leaving only a terminal. When you reach the login: prompt, enter your username and password. Then, as root in the terminal, switch to runlevel 5 to return to the graphical interface and start the X11 server: From the client machine, start a remote X11 session using X . For example: The command connects to the remote X11 server via XDMCP (replace s390vm.example.com with the hostname of the remote X11 server) and displays the remote graphical login screen on display :1 of the X11 server system (usually accessible by using the Ctrl - Alt - F8 key combination). You can also access remote desktop sessions using a nested X11 server, which opens the remote desktop as a window in your current X11 session. Xnest allows users to open a remote desktop nested within their local X11 session. For example, run Xnest using the following command, replacing s390vm.example.com with the hostname of the remote X11 server:

Commands:
/sbin/init 4
/sbin/init 5
X :1 -query s390vm.example.com
Xnest :1 -query s390vm.example.com
6.10. Host Devices 6.10.1. Adding a Host Device to a Virtual Machine Virtual machines can be directly attached to the host devices for improved performance if a compatible host has been configured for direct device assignment. Host devices are devices that are physically plugged into the host, including SCSI (for example tapes, disks, changers), PCI (for example NICs, GPUs, and HBAs), and USB (for example mice, cameras, and disks). Adding Host Devices to a Virtual Machine Click Compute Virtual Machines . Click a virtual machine's name to go to the details view. Click the Host Devices tab to list the host devices already attached to this virtual machine. A virtual machine can only have devices attached from the same host. If a virtual machine has attached devices from one host, and you attach a device from another host, the attached devices from the host will be automatically removed. Attaching host devices to a virtual machine requires the virtual machine to be in a Down state. If the virtual machine is running, the changes will not take effect until after the virtual machine has been shut down. Click Add device to open the Add Host Devices window. Use the Pinned Host drop-down menu to select a host. Use the Capability drop-down menu to list the pci , scsi , or usb_device host devices. Select the check boxes of the devices to attach to the virtual machine from the Available Host Devices pane and click the directional arrow button to transfer these devices to the Host Devices to be attached pane, creating a list of the devices to attach to the virtual machine. When you have transferred all desired host devices to the Host Devices to be attached pane, click OK to attach these devices to the virtual machine and close the window. These host devices will be attached to the virtual machine when the virtual machine is powered on. 6.10.2. Removing Host Devices from a Virtual Machine If you are removing all host devices directly attached to the virtual machine in order to add devices from a different host, you can instead add the devices from the desired host, which will automatically remove all of the devices already attached to the virtual machine. Procedure Click Compute Virtual Machines . Select a virtual machine to go to the details view. Click the Host Devices tab to list the host devices attached to the virtual machine. Select the host device to detach from the virtual machine, or hold Ctrl to select multiple devices, and click Remove device to open the Remove Host Device(s) window. Click OK to confirm and detach these devices from the virtual machine. 6.10.3. Pinning a Virtual Machine to Another Host You can use the Host Devices tab in the details view of a virtual machine to pin it to a specific host. If the virtual machine has any host devices attached to it, pinning it to another host automatically removes the host devices from the virtual machine. Pinning a Virtual Machine to a Host Click a virtual machine name and click the Host Devices tab. Click Pin to another host to open the Pin VM to Host window. Use the Host drop-down menu to select a host. Click OK to pin the virtual machine to the selected host.

Commands:
Chapter 21. KafkaAuthorizationSimple schema reference Used in: KafkaClusterSpec Full list of KafkaAuthorizationSimple schema properties For simple authorization, Streams for Apache Kafka uses Kafka's built-in authorization plugins: the StandardAuthorizer for KRaft mode and the AclAuthorizer for ZooKeeper-based cluster management. ACLs allow you to define which users have access to which resources at a granular level. Configure the Kafka custom resource to use simple authorization. Set the type property in the authorization section to the value simple , and configure a list of super users. Access rules are configured for the KafkaUser , as described in the ACLRule schema reference . 21.1. superUsers A list of user principals treated as super users, so that they are always allowed without querying ACL rules. An example of simple authorization configuration apiVersion: kafka.strimzi.io/v1beta2 kind: Kafka metadata: name: my-cluster namespace: myproject spec: kafka: # ... authorization: type: simple superUsers: - CN=client_1 - user_2 - CN=client_3 # ... Note The super.user configuration option in the config property in Kafka.spec.kafka is ignored. Designate super users in the authorization property instead. For more information, see Kafka broker configuration . 21.2. KafkaAuthorizationSimple schema properties The type property is a discriminator that distinguishes use of the KafkaAuthorizationSimple type from KafkaAuthorizationOpa , KafkaAuthorizationKeycloak , KafkaAuthorizationCustom . It must have the value simple for the type KafkaAuthorizationSimple . Property Property type Description type string Must be simple . superUsers string array List of super users. Should contain list of user principals which should get unlimited access rights.

Commands:
apiVersion: kafka.strimzi.io/v1beta2 kind: Kafka metadata: name: my-cluster namespace: myproject spec: kafka: # authorization: type: simple superUsers: - CN=client_1 - user_2 - CN=client_3 #
Chapter 13. Installing a three-node cluster on Azure In OpenShift Container Platform version 4.15, you can install a three-node cluster on Microsoft Azure. A three-node cluster consists of three control plane machines, which also act as compute machines. This type of cluster provides a smaller, more resource efficient cluster, for cluster administrators and developers to use for testing, development, and production. You can install a three-node cluster using either installer-provisioned or user-provisioned infrastructure. Note Deploying a three-node cluster using an Azure Marketplace image is not supported. 13.1. Configuring a three-node cluster You configure a three-node cluster by setting the number of worker nodes to 0 in the install-config.yaml file before deploying the cluster. Setting the number of worker nodes to 0 ensures that the control plane machines are schedulable. This allows application workloads to be scheduled to run from the control plane nodes. Note Because application workloads run from control plane nodes, additional subscriptions are required, as the control plane nodes are considered to be compute nodes. Prerequisites You have an existing install-config.yaml file. Procedure Set the number of compute replicas to 0 in your install-config.yaml file, as shown in the following compute stanza: Example install-config.yaml file for a three-node cluster apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0 # ... If you are deploying a cluster with user-provisioned infrastructure: After you create the Kubernetes manifest files, make sure that the spec.mastersSchedulable parameter is set to true in cluster-scheduler-02-config.yml file. You can locate this file in <installation_directory>/manifests . For more information, see "Creating the Kubernetes manifest and Ignition config files" in "Installing a cluster on Azure using ARM templates". Do not create additional worker nodes. Example cluster-scheduler-02-config.yml file for a three-node cluster apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {} 13.2. steps Installing a cluster on Azure with customizations Installing a cluster on Azure using ARM templates

Commands:
apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0
apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {}
18.8. IPv6 The introduction of the -generation Internet Protocol, called IPv6, expands beyond the 32-bit address limit of IPv4 (or IP). IPv6 supports 128-bit addresses, and carrier networks that are IPv6 aware are therefore able to address a larger number of routable addresses than IPv4. Red Hat Enterprise Linux supports IPv6 firewall rules using the Netfilter 6 subsystem and the ip6tables command. In Red Hat Enterprise Linux 5, both IPv4 and IPv6 services are enabled by default. The ip6tables command syntax is identical to iptables in every aspect except that it supports 128-bit addresses. For example, use the following command to enable SSH connections on an IPv6-aware network server: For more information about IPv6 networking, refer to the IPv6 Information Page at http://www.ipv6.org/ .

Commands:
ip6tables -A INPUT -i eth0 -p tcp -s 3ffe:ffff:100::1/128 --dport 22 -j ACCEPT
Chapter 8. Tuning the Replication Performance 8.1. Improving the Multi-supplier Replication Efficiency The replication latency in a multi-supplier replication environment, especially if the servers are connected using a wide area network (WAN), can be high in case of multiple suppliers are receiving updates at the same time. This happens when one suppliers exclusively accesses a replica without releasing it for a long time. In such situations, other suppliers cannot send updates to this consumer, which increases the replication latency. To release a replica after a fixed amount of time, set the nsds5ReplicaReleaseTimeout parameter on replication suppliers and hubs. Note The 60 seconds default value is ideal for most environments. A value set too high or too low can have a negative impact on the replication performance. If the value is set too low, replication servers are constantly reacquiring one another, and servers are not able to send many updates. In a high-traffic replication environment, a longer timeout can improve situations where one supplier exclusively accesses a replica. However, in most cases, a value higher than 120 seconds slows down replication. 8.1.1. Setting the Replication Release Timeout Using the Command Line To set the replication release timeout using the command line: Set the timeout value: This command sets the replication release timeout value for the dc=example,dc=com suffix to 70 seconds. Restart the Directory Server instance: 8.1.2. Setting the Replication Release Timeout Using the Web Console To set the replication release timeout using the Web Console: Open the Directory Server user interface in the web console. For details, see Logging Into Directory Server Using the Web Console section in the Red Hat Directory Server Administration Guide . Select the instance. Open the Replication menu, and select Configuration . Click Show Advanced Settings . Set the timeout value in the Replication Release Timeout field. Click Save . Click the Actions button, and select Restart Instance .

Commands:
dsconf -D "cn=Directory Manager" ldap://supplier.example.com replication set --suffix=" dc=example,dc=com " --repl-release-timeout= 70
dsctl instance_name restart
4.4. GLOBAL SETTINGS The GLOBAL SETTINGS panel is where the you define the networking details for the primary LVS router's public and private network interfaces. Figure 4.3. The GLOBAL SETTINGS Panel The top half of this panel sets up the primary LVS router's public and private network interfaces. These are the interfaces already configured in Section 3.1.1, "Configuring Network Interfaces for LVS with NAT" . Primary server public IP In this field, enter the publicly routable real IP address for the primary LVS node. Primary server private IP Enter the real IP address for an alternative network interface on the primary LVS node. This address is used solely as an alternative heartbeat channel for the backup router and does not have to correlate to the real private IP address assigned in Section 3.1.1, "Configuring Network Interfaces for LVS with NAT" . You may leave this field blank, but doing so will mean there is no alternate heartbeat channel for the backup LVS router to use and therefore will create a single point of failure. Note The private IP address is not needed for Direct Routing configurations, as all real servers as well as the LVS directors share the same virtual IP addresses and should have the same IP route configuration. Note The primary LVS router's private IP can be configured on any interface that accepts TCP/IP, whether it be an Ethernet adapter or a serial port. Use network type Click the NAT button to select NAT routing. Click the Direct Routing button to select direct routing. The three fields deal specifically with the NAT router's virtual network interface connecting the private network with the real servers. These fields do not apply to the direct routing network type. NAT Router IP Enter the private floating IP in this text field. This floating IP should be used as the gateway for the real servers. NAT Router netmask If the NAT router's floating IP needs a particular netmask, select it from drop-down list. NAT Router device Use this text field to define the device name of the network interface for the floating IP address, such as eth1:1 . Note You should alias the NAT floating IP address to the Ethernet interface connected to the private network. In this example, the private network is on the eth1 interface, so eth1:1 is the floating IP address. Warning After completing this page, click the ACCEPT button to make sure you do not lose any changes when selecting a new panel.

Commands:
Chapter 6. Device Drivers 6.1. New drivers Network drivers MT7921E 802.11ax wireless driver (mt7921e.ko.xz) Realtek 802.11ax wireless core module (rtw89_core.ko.xz) Realtek 802.11ax wireless PCI driver (rtw89_pci.ko.xz) ntb_netdev (ntb_netdev.ko.xz) Intel(R) Ethernet Protocol Driver for RDMA (irdma.ko.xz) Intel(R) PCI-E Non-Transparent Bridge Driver (ntb_hw_intel.ko.xz) Graphics drivers and miscellaneous drivers Generic Counter interface (counter.ko.xz) Intel Quadrature Encoder Peripheral driver (intel-qep.ko.xz) AMD (R) PCIe MP2 Communication Driver (amd_sfh.ko.xz) Driver to initialize some steering wheel joysticks from Thrustmaster (hid-thrustmaster.ko.xz) HID over I2C ACPI driver (i2c-hid-acpi.ko.xz) Intel PMC Core Driver (intel_pmc_core.ko.xz) ThinkLMI Driver (think-lmi.ko.xz) Processor Thermal Reporting Device Driver (int3401_thermal.ko.xz) Processor Thermal Reporting Device Driver (processor_thermal_device_pci.ko.xz) Processor Thermal Reporting Device Driver (processor_thermal_device_pci_legacy.ko.xz) TI TPS6598x USB Power Delivery Controller Driver (tps6598x.ko.xz) 6.2. Updated drivers Network drivers Intel(R) PRO/1000 Network Driver (e1000e.ko.xz) has been updated. Intel(R) Ethernet Switch Host Interface Driver (fm10k.ko.xz) has been updated. Intel(R) Ethernet Connection XL710 Network Driver (i40e.ko.xz) has been updated. Intel(R) Ethernet Adaptive Virtual Function Network Driver (iavf.ko.xz) has been updated. Intel(R) Gigabit Ethernet Network Driver (igb.ko.xz) has been updated. Intel(R) Gigabit Virtual Function Network Driver (igbvf.ko.xz) has been updated. Intel(R) 2.5G Ethernet Linux Driver (igc.ko.xz) has been updated. Intel(R) 10 Gigabit PCI Express Network Driver (ixgbe.ko.xz) has been updated. Intel(R) 10 Gigabit Virtual Function Network Driver (ixgbevf.ko.xz) has been updated. Mellanox 5th generation network adapters (ConnectX series) core driver (mlx5_core.ko.xz) has been updated. VMware vmxnet3 virtual NIC driver (vmxnet3.ko.xz) has been updated to version 1.6.0.0-k. Storage drivers Emulex LightPulse Fibre Channel SCSI driver (lpfc.ko.xz) has been updated to version 0:14.0.0.4. Broadcom MegaRAID SAS Driver (megaraid_sas.ko.xz) has been updated to version 07.719.03.00-rh1. LSI MPT Fusion SAS 3.0 Device Driver (mpt3sas.ko.xz) has been updated to version 39.100.00.00. QLogic Fibre Channel HBA Driver (qla2xxx.ko.xz) has been updated to version 10.02.06.200-k. Driver for Microchip Smart Family Controller (smartpqi.ko.xz) has been updated to version 2.1.12-055. Graphics and miscellaneous driver updates Standalone drm driver for the VMware SVGA device (vmwgfx.ko.xz) has been updated to version 2.18.1.0.

Commands:
7.3. Caching Caching options can be configured with virt-manager during guest installation, or on an existing guest virtual machine by editing the guest XML configuration. Table 7.1. Caching options Caching Option Description Cache=none I/O from the guest is not cached on the host, but may be kept in a writeback disk cache. Use this option for guests with large I/O requirements. This option is generally the best choice, and is the only option to support migration. Cache=writethrough I/O from the guest is cached on the host but written through to the physical medium. This mode is slower and prone to scaling problems. Best used for small number of guests with lower I/O requirements. Suggested for guests that do not support a writeback cache (such as Red Hat Enterprise Linux 5.5 and earlier), where migration is not needed. Cache=writeback I/O from the guest is cached on the host. To configure the cache mode in the guest XML, use virsh edit to edit the cache setting inside the driver tag, specifying none , writeback , or writethrough . For example, to set the cache as writeback : <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/>

Commands:
<disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/>
2.6. Verifying the Integrity of Back-end Databases The dsctl dbverify command enables administrators to verify the integrity of back-end databases. For example, to verify the userroot database: Optionally, list the back-end databases of the instance: You need the name of the database in a later step. Stop the Directory Server instance: Verify the database: If the verification process reported any problems, fix them manually or restore a backup. Start the Directory Server instance:

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com backend suffix list dc=example,dc=com ( userroot )
dsctl instance_name stop
dsctl instance_name dbverify userroot [04/Feb/2020:13:11:02.453624171 +0100] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000 [04/Feb/2020:13:11:02.465339507 +0100] - WARN - ldbm_instance_add_instance_entry_callback - ldbm instance userroot already exists [04/Feb/2020:13:11:02.468060144 +0100] - ERR - ldbm_config_read_instance_entries - Failed to add instance entry cn=userroot,cn=ldbm database,cn=plugins,cn=config [04/Feb/2020:13:11:02.471079045 +0100] - ERR - bdb_config_load_dse_info - failed to read instance entries [04/Feb/2020:13:11:02.476173304 +0100] - ERR - libdb - BDB0522 Page 0: metadata page corrupted [04/Feb/2020:13:11:02.481684604 +0100] - ERR - libdb - BDB0523 Page 0: could not check metadata page [04/Feb/2020:13:11:02.484113053 +0100] - ERR - libdb - /var/lib/dirsrv/slapd-instance_name/db/userroot/entryrdn.db: BDB0090 DB_VERIFY_BAD: Database verification failed [04/Feb/2020:13:11:02.486449603 +0100] - ERR - dbverify_ext - verify failed(-30970): /var/lib/dirsrv/slapd-instance_name/db/userroot/entryrdn.db dbverify failed
dsctl instance_name start