mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Overview Red Hat OpenShift Data Foundation is software-defined storage that is optimized for container environments. It runs as an operator on OpenShift Container Platform to provide highly integrated and simplified persistent storage management for containers. Red Hat OpenShift Data Foundation is integrated into the latest Red Hat OpenShift Container Platform to address platform services, application portability, and persistence challenges.It provides a highly scalable backend for the generation of cloud-native applications, built on a technology stack that includes Red Hat Ceph Storage, the Rook.io Operator, and NooBaa's Multicloud Object Gateway technology. Red Hat OpenShift Data Foundation provides a trusted, enterprise-grade application development environment that simplifies and enhances the user experience across the application lifecycle in a number of ways: Provides block storage for databases. Shared file storage for continuous integration, messaging, and data aggregation. Object storage for cloud-first development, archival, backup, and media storage. Scale applications and data exponentially. Attach and detach persistent data volumes at an accelerated rate. Stretch clusters across multiple data-centers or availability zones. Establish a comprehensive application container registry. Support the generation of OpenShift workloads such as Data Analytics, Artificial Intelligence, Machine Learning, Deep Learning, and Internet of Things (IoT). Dynamically provision not only application containers, but data service volumes and containers, as well as additional OpenShift Container Platform nodes, Elastic Block Store (EBS) volumes and other infrastructure services. 1.1. About this release Red Hat OpenShift Data Foundation 4.13 ( RHBA-2023:3734 and RHSA-2023:3742 ) is now available. New enhancements, features, and known issues that pertain to OpenShift Data Foundation 4.13 are included in this topic. Red Hat OpenShift Data Foundation 4.13 is supported on the Red Hat OpenShift Container Platform version 4.13. For more information, see Red Hat OpenShift Data Foundation Supportability and Interoperability Checker . For Red Hat OpenShift Data Foundation life cycle information, refer to the layered and dependent products life cycle section in Red Hat OpenShift Container Platform Life Cycle Policy .

Commands:
5.3. Resource-Specific Parameters For any individual resource, you can use the following command to display the parameters you can set for that resource. For example, the following command displays the parameters you can set for a resource of type LVM .

Commands:
pcs resource describe standard:provider:type | type
pcs resource describe LVM Resource options for: LVM volgrpname (required): The name of volume group. exclusive: If set, the volume group will be activated exclusively. partial_activation: If set, the volume group will be activated even only partial of the physical volumes available. It helps to set to true, when you are using mirroring logical volumes.
11.4.2.6. Spam Filters Because it is called by Sendmail, Postfix, and Fetchmail upon receiving new emails, Procmail can be used as a powerful tool for combating spam. This is particularly true when Procmail is used in conjunction with SpamAssassin. When used together, these two applications can quickly identify spam emails, and sort or destroy them. SpamAssassin uses header analysis, text analysis, blacklists, a spam-tracking database, and self-learning Bayesian spam analysis to quickly and accurately identify and tag spam. The easiest way for a local user to use SpamAssassin is to place the following line near the top of the ~/.procmailrc file: The /etc/mail/spamassassin/spamassassin-default.rc contains a simple Procmail rule that activates SpamAssassin for all incoming email. If an email is determined to be spam, it is tagged in the header as such and the title is prepended with the following pattern: The message body of the email is also prepended with a running tally of what elements caused it to be diagnosed as spam. To file email tagged as spam, a rule similar to the following can be used: This rule files all email tagged in the header as spam into a mailbox called spam . Since SpamAssassin is a Perl script, it may be necessary on busy servers to use the binary SpamAssassin daemon ( spamd ) and client application ( spamc ). Configuring SpamAssassin this way, however, requires root access to the host. To start the spamd daemon, type the following command as root: To start the SpamAssassin daemon when the system is booted, use an initscript utility, such as the Services Configuration Tool ( system-config-services ), to turn on the spamassassin service. Refer to Section 1.4.2, "Runlevel Utilities" for more information about initscript utilities. To configure Procmail to use the SpamAssassin client application instead of the Perl script, place the following line near the top of the ~/.procmailrc file. For a system-wide configuration, place it in /etc/procmailrc :

Commands:
INCLUDERC=/etc/mail/spamassassin/spamassassin-default.rc
*****SPAM*****
:0 Hw * ^X-Spam-Status: Yes spam
service spamassassin start
INCLUDERC=/etc/mail/spamassassin/spamassassin-spamc.rc
13.3. Removing a Partition Warning Do not attempt to remove a partition on a device that is in use. Procedure 13.3. Remove a Partition Before removing a partition, do one of the following: Boot into rescue mode, or Unmount any partitions on the device and turn off any swap space on the device. Start the parted utility: Replace device with the device on which to remove the partition: for example, /dev/sda . View the current partition table to determine the minor number of the partition to remove: Remove the partition with the command rm . For example, to remove the partition with minor number 3: The changes start taking place as soon as you press Enter , so review the command before committing to it. After removing the partition, use the print command to confirm that it is removed from the partition table: Exit from the parted shell: Examine the content of the /proc/partitions file to make sure the kernel knows the partition is removed: Remove the partition from the /etc/fstab file. Find the line that declares the removed partition, and remove it from the file. Regenerate mount units so that your system registers the new /etc/fstab configuration:

Commands:
parted device
(parted) print
(parted) rm 3
(parted) print
(parted) quit
cat /proc/partitions
systemctl daemon-reload
8.7. Date & Time To configure time zone, date, and optionally settings for network time, select Date & Time at the Installation Summary screen. There are three ways for you to select a time zone: Using your mouse, click on the interactive map to select a specific city. A red pin appears indicating your selection. You can also scroll through the Region and City drop-down menus at the top of the screen to select your time zone. Select Etc at the bottom of the Region drop-down menu, then select your time zone in the menu adjusted to GMT/UTC, for example GMT+1 . If your city is not available on the map or in the drop-down menu, select the nearest major city in the same time zone. Alternatively you can use a Kickstart file, which will allow you to specify some additional time zones which are not available in the graphical interface. See the timezone command in timezone (required) for details. Note The list of available cities and regions comes from the Time Zone Database (tzdata) public domain, which is maintained by the Internet Assigned Numbers Authority (IANA). Red Hat cannot add cities or regions into this database. You can find more information at the official website, available at http://www.iana.org/time-zones . Specify a time zone even if you plan to use NTP (Network Time Protocol) to maintain the accuracy of the system clock. If you are connected to the network, the Network Time switch will be enabled. To set the date and time using NTP, leave the Network Time switch in the ON position and click the configuration icon to select which NTP servers Red Hat Enterprise Linux should use. To set the date and time manually, move the switch to the OFF position. The system clock should use your time zone selection to display the correct date and time at the bottom of the screen. If they are still incorrect, adjust them manually. Note that NTP servers might be unavailable at the time of installation. In such a case, enabling them will not set the time automatically. When the servers become available, the date and time will update. Once you have made your selection, click Done to return to the Installation Summary screen. Note To change your time zone configuration after you have completed the installation, visit the Date & Time section of the Settings dialog window.

Commands:
12.3. Enabling LDAP-based Enrollment Profiles To install with LDAP-based profiles set the pki_profile_in_ldap=True option in the [CA] section of the pkispawn configuration file. Note In this case, profile files will still appear in /var/lib/pki/ instance_name /ca/profiles/ca/ , but will be ignored. To enable LDAP-based profiles on an existing instance, change the following in the instance's CS.cfg : Then, import profiles manually into the database using either the pki command line utility or a custom script.

Commands:
subsystem.1.class=com.netscape.cmscore.profile.LDAPProfileSubsystem
14.2. Setting Access ACLs There are two types of ACLs: access ACLs and default ACLs . An access ACL is the access control list for a specific file or directory. A default ACL can only be associated with a directory; if a file within the directory does not have an access ACL, it uses the rules of the default ACL for the directory. Default ACLs are optional. ACLs can be configured: Per user Per group Via the effective rights mask For users not in the user group for the file The setfacl utility sets ACLs for files and directories. Use the -m option to add or modify the ACL of a file or directory: Rules ( <rules> ) must be specified in the following formats. Multiple rules can be specified in the same command if they are separated by commas. u: <uid> : <perms> Sets the access ACL for a user. The user name or UID may be specified. The user may be any valid user on the system. g: <gid> : <perms> Sets the access ACL for a group. The group name or GID may be specified. The group may be any valid group on the system. m: <perms> Sets the effective rights mask. The mask is the union of all permissions of the owning group and all of the user and group entries. o: <perms> Sets the access ACL for users other than the ones in the group for the file. White space is ignored. Permissions ( <perms> ) must be a combination of the characters r , w , and x for read, write, and execute. If a file or directory already has an ACL, and the setfacl command is used, the additional rules are added to the existing ACL or the existing rule is modified. For example, to give read and write permissions to user andrius: To remove all the permissions for a user, group, or others, use the -x option and do not specify any permissions: For example, to remove all permissions from the user with UID 500:

Commands:
setfacl -m <rules> <files>
setfacl -m u:andrius:rw /project/somefile
setfacl -x <rules> <files>
setfacl -x u:500 /project/somefile
Chapter 5. Fixed issues The issues fixed in AMQ Streams 2.1 are shown in the following table. For details of the issues fixed in Kafka 3.1.0, refer to the Kafka 3.1.0 Release Notes . Issue Number Description ENTMQST-3595 Cluster operator missing Java options to be passed to Kafka bridge ENTMQST-3835 Connector gets restarted on every reconciliation when tasks.max is set ENTMQST-3763 Errors when scaling-down ZooKeeper nodes ENTMQST-3422 Failure to run on FIPS-enabled clusters ENTMQST-3417 Fix leaking keystores/truststores in ZooKeeperScaler ENTMQST-3583 JVM options provided by the Cluster Operator are ignored ENTMQST-3345 Kafka upgrade, with inter broker protocol and log message format as M.m.p, fails with misleading error ENTMQST-3411 KafkaExporter, CruiseControl and EntityOperator pods are rolled on clients CA renewal ENTMQST-3325 KafkaMirrorMaker2 conditions do not reflect the state of the MM2 connectors ENTMQST-3504 OptimizationFailureException due to invalid CPU utilization ENTMQST-3585 Pass Java system properties to Cruise Control ENTMQST-3856 Rack Awareness doesn't work for connectors ENTMQST-3354 Set the base image in Kafka Connect Build properly when it is specified in the custom resource ENTMQST-3826 The /tmp volume is not big enough for the compression libraries ENTMQST-3584 The strimzi_resources{kind="Kafka"} metric is not removed when the Kafka related namespace is deleted ENTMQST-3839 The broker is stuck in an inconsistent state after ZooKeeper disconnection ENTMQST-2331 ZooKeeper, Kafka, and EntityOperator certificates are not renewed using your own cluster CA certificate Table 5.1. Fixed common vulnerabilities and exposures (CVEs) Issue Number Description ENTMQST-2851 CVE-2021-3520 lz4: memory corruption due to an integer overflow bug caused by memmove argument ENTMQST-3631 CVE-2021-43797 netty: control chars in header names may lead to HTTP request smuggling

Commands:
11.3. Editing Users Editing Users in the Web UI Select the Identity Users tab. Search the Active users , Stage users , or Preserved users category to find the user to edit. Click the name of the user to edit. Figure 11.10. Selecting a User to Edit Edit the user attribute fields as required. Click Save at the top of the page. Figure 11.11. Save Modified User Attributes After you update user details in the web UI, the new values are not synchronized immediately. It might take up to approximately 5 minutes before the new values are reflected at the client system. Editing Users from the Command Line To modify a user in the active or preserved states, use the ipa user-mod command. To modify a user in the stage state, use the ipa stageuser-mod command. The ipa user-mod and ipa stageuser-mod commands accept the following options: the user login, which identifies the user account to be modified options specifying the new attribute values For a complete list of user entry attributes that can be modified from the command line, see the list of options accepted by ipa user-mod and ipa stageuser-mod . To display the list of options, run the commands with the --help option added. Simply adding an attribute option to ipa user-mod or ipa stageuser-mod overwrites the current attribute value. For example, the following changes a user's title or adds a new title if the user did not yet have a title specified: For LDAP attributes that are allowed to have multiple values, IdM also accepts multiple values. For example, a user can have two email addresses saved in their user account. To add an additional attribute value without overwriting the existing value, use the --addattr option together with the option to specify the new attribute value. For example, to add a new email address to a user account that already has an email address specified: To set two attribute values at the same time, use the --addattr option twice: The ipa user-mod command also accepts the --setattr option for setting attribute values and the --delattr option for deleting attribute values. These options are used in a way similar to using --addattr . For details, see the output of the ipa user-mod --help command. Note To overwrite the current email address for a user, use the --email option. However, to add an additional email address, use the mail option with the --addattr option:

Commands:
ipa user-mod user_login --title= new_title
ipa user-mod user --addattr=mobile= new_mobile_number -------------------- Modified user "user" -------------------- User login: user Mobile Telephone Number: mobile_number, new_mobile_number
ipa user-mod user --addattr=mobile= mobile_number_1 --addattr=mobile= mobile_number_2
ipa user-mod user --email= email@example.com ipa user-mod user --addattr=mail= another_email@example.com
Chapter 46. Using standalone custom pages(dashboards) Apart from standalone perspectives, you can also embed custom pages, also known as dashboards, in your application. For accessing the custom pages from your application, provide the name of the custom page as the value of the perspective parameter. Note that the perspective parameter is case-sensitive. Procedure Log in to Business Central. In a web browser, enter the custom page's web address in the address bar, for example, http://localhost:8080/business-central/kie-wb.jsp?standalone=true&perspective=CustomPageName The standalone custom page opens in the browser. Replace the value, CustomPageName , with the name of the custom page you want to use in the standalone mode.

Commands:
Chapter 10. Scheduling resources Taints and tolerations allow the node to control which pods should (or should not) be scheduled on them. A node selector specifies a map of key/value pairs that are defined using custom labels on nodes and selectors specified in pods. For the pod to be eligible to run on a node, the pod must have the same key/value node selector as the label on the node. 10.1. Network Observability deployment in specific nodes You can configure the FlowCollector to control the deployment of Network Observability components in specific nodes. The spec.agent.ebpf.advanced.scheduling , spec.processor.advanced.scheduling , and spec.consolePlugin.advanced.scheduling specifications have the following configurable settings: NodeSelector Tolerations Affinity PriorityClassName Sample FlowCollector resource for spec.<component>.advanced.scheduling apiVersion: flows.netobserv.io/v1beta2 kind: FlowCollector metadata: name: cluster spec: # ... advanced: scheduling: tolerations: - key: "<taint key>" operator: "Equal" value: "<taint value>" effect: "<taint effect>" nodeSelector: <key>: <value> affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: name operator: In values: - app-worker-node priorityClassName: """ # ... Additional resources Understanding taints and tolerations Assign Pods to Nodes (Kubernetes documentation) Pod Priority and Preemption (Kubernetes documentation)

Commands:
apiVersion: flows.netobserv.io/v1beta2 kind: FlowCollector metadata: name: cluster spec: advanced: scheduling: tolerations: - key: "<taint key>" operator: "Equal" value: "<taint value>" effect: "<taint effect>" nodeSelector: <key>: <value> affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: name operator: In values: - app-worker-node priorityClassName: """
4.3. Shared Storage Example: NFS for a Simple Migration Important This example uses NFS to share guest virtual machine images with other KVM host physical machines. Although not practical for large installations, it is presented to demonstrate migration techniques only. Do not use this example for migrating or running more than a few guest virtual machines. In addition, it is required that the sync parameter is enabled. This is required for proper export of the NFS storage. In addition, it is strongly recommended that the NFS is mounted on source host physical machine, and the guest virtual machine's image needs to be created on the NFS mounted directory located on source host physical machine. It should also be noted that NFS file locking must not be used as it is not supported in KVM. iSCSI storage is a better choice for large deployments. Refer to Section 12.5, "iSCSI-based Storage Pools" for configuration details. Also note, that the instructions provided in this section are not meant to replace the detailed instructions found in Red Hat Linux Storage Administration Guide . Refer to this guide for information on configuring NFS, opening IP tables, and configuring the firewall. Create a directory for the disk images This shared directory will contain the disk images for the guest virtual machines. To do this create a directory in a location different from /var/lib/libvirt/images . For example: Add the new directory path to the NFS configuration file The NFS configuration file is a text file located in /etc/exports . Open the file and edit it adding the path to the new file you created in step 1. Start NFS Make sure that the ports for NFS in iptables (2049, for example) are opened and add NFS to the /etc/hosts.allow file. Start the NFS service: Mount the shared storage on both the source and the destination Mount the /var/lib/libvirt/images directory on both the source and destination system, running the following command twice. Once on the source system and again on the destination system. Warning Make sure that the directories you create in this procedure is compliant with the requirements as outlined in Section 4.1, "Live Migration Requirements" . In addition, the directory may need to be labeled with the correct SELinux label. For more information consult the NFS chapter in the Red Hat Enterprise Linux Storage Administration Guide .

Commands:
mkdir /var/lib/libvirt-img/images
echo "/var/lib/libvirt-img/images" >> /etc/exports/[NFS-Config-FILENAME.txt]
service nfs start
mount source_host :/var/lib/libvirt-img/images /var/lib/libvirt/images
Preface Open Java Development Kit (OpenJDK) is a free and open source implementation of the Java Platform, Standard Edition (Java SE). The Red Hat build of OpenJDK is available in two versions, Red Hat build of OpenJDK 8u and Red Hat build of OpenJDK 11u. Packages for the Red Hat build of OpenJDK are made available on Red Hat Enterprise Linux and Microsoft Windows and shipped as a JDK and JRE in the Red Hat Ecosystem Catalog.

Commands:
12.5. Tracking Certificates with certmonger certmonger can monitor expiration date of a certificate and automatically renew the certificate at the end of its validity period. To track a certificate in this way, run the getcert start-tracking command. Note It is not required that you run getcert start-tracking after running getcert request , because the getcert request command by default automatically tracks and renews the requested certificate. The getcert start-tracking command is intended for situations when you have already obtained the key and certificate through some other process, and therefore you have to manually instruct certmonger to start the tracking. The getcert start-tracking command takes several options: -r automatically renews the certificate when its expiration date is close if the key pair already exists. This option is used by default. -I sets a name for the tracking request. certmonger uses this name to refer to the combination of storage locations and request options, and it is also displayed in the output of the getcert list command. If you do not specify this option, certmonger assigns an automatically generated a name for the task. To cancel tracking for a certificate, run the stop-tracking command.

Commands:
getcert start-tracking -I cert1-tracker -d /export/alias -n ServerCert