mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 45. ZookeeperClusterTemplate schema reference Used in: ZookeeperClusterSpec Property Description statefulset The statefulset property has been deprecated. Support for StatefulSets was removed in AMQ Streams 2.5. This property is ignored. Template for ZooKeeper StatefulSet . StatefulSetTemplate pod Template for ZooKeeper Pods . PodTemplate clientService Template for ZooKeeper client Service . InternalServiceTemplate nodesService Template for ZooKeeper nodes Service . InternalServiceTemplate persistentVolumeClaim Template for all ZooKeeper PersistentVolumeClaims . ResourceTemplate podDisruptionBudget Template for ZooKeeper PodDisruptionBudget . PodDisruptionBudgetTemplate zookeeperContainer Template for the ZooKeeper container. ContainerTemplate serviceAccount Template for the ZooKeeper service account. ResourceTemplate jmxSecret Template for Secret of the Zookeeper Cluster JMX authentication. ResourceTemplate podSet Template for ZooKeeper StrimziPodSet resource. ResourceTemplate

Commands:
39.3. iSCSI Root When accessing the root partition directly through an iSCSI disk, the iSCSI timers should be set so that iSCSI layer has several chances to try to reestablish a path/session. In addition, commands should not be quickly re-queued to the SCSI layer. This is the opposite of what should be done when dm-multipath is implemented. To start with, NOP-Outs should be disabled. You can do this by setting both NOP-Out interval and timeout to zero. To set this, open /etc/iscsi/iscsid.conf and edit as follows: In line with this, replacement_timeout should be set to a high number. This will instruct the system to wait a long time for a path/session to reestablish itself. To adjust replacement_timeout , open /etc/iscsi/iscsid.conf and edit the following line: After configuring /etc/iscsi/iscsid.conf , you must perform a re-discovery of the affected storage. This will allow the system to load and use any new values in /etc/iscsi/iscsid.conf . For more information on how to discover iSCSI devices, refer to Chapter 36, Scanning iSCSI Targets with Multiple LUNs or Portals . Configuring Timeouts for a Specific Session You can also configure timeouts for a specific session and make them non-persistent (instead of using /etc/iscsi/iscsid.conf ). To do so, run the following command (replace the variables accordingly): Important The configuration described here is recommended for iSCSI sessions involving root partition access. For iSCSI sessions involving access to other types of storage (namely, in systems that use dm-multipath ), refer to Section 39.2, "iSCSI Settings With dm-multipath " .

Commands:
node.conn[0].timeo.noop_out_interval = 0 node.conn[0].timeo.noop_out_timeout = 0
node.session.timeo.replacement_timeout = replacement_timeout
iscsiadm -m node -T target_name -p target_IP : port -o update -n node.session.timeo.replacement_timeout -v USD timeout_value
Chapter 5. OS/JVM certifications This release is supported for use with the following operating system and Java Development Kit (JDK) versions: Operating System Chipset Architecture Java Virtual Machine Red Hat Enterprise Linux 9 x86_64 Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, Oracle JDK 11, Oracle JDK 17 Red Hat Enterprise Linux 8 x86_64 Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, Oracle JDK 11, Oracle JDK 17 Microsoft Windows 2019 Server x86_64 Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, Oracle JDK 11, Oracle JDK 17 Note Red Hat Enterprise Linux 7 and Microsoft Windows 2016 Server are not supported.

Commands:
9.2.2. A Note About Virtual Consoles The Red Hat Enterprise Linux installation program offers more than the dialog boxes of the installation process. Several kinds of diagnostic messages are available to you, as well as a way to enter commands from a shell prompt. The installation program displays these messages on five virtual consoles , among which you can switch using a single keystroke combination. A virtual console is a shell prompt in a non-graphical environment, accessed from the physical machine, not remotely. Multiple virtual consoles can be accessed simultaneously. These virtual consoles can be helpful if you encounter a problem while installing Red Hat Enterprise Linux. Messages displayed on the installation or system consoles can help pinpoint a problem. Refer to Table 9.1, "Console, Keystrokes, and Contents" for a listing of the virtual consoles, keystrokes used to switch to them, and their contents. Generally, there is no reason to leave the default console (virtual console #6) for graphical installations unless you are attempting to diagnose installation problems. Table 9.1. Console, Keystrokes, and Contents console keystrokes contents 1 ctrl + alt + f1 graphical display 2 ctrl + alt + f2 shell prompt 3 ctrl + alt + f3 install log (messages from installation program) 4 ctrl + alt + f4 system-related messages 5 ctrl + alt + f5 other messages

Commands:
Chapter 3. Creating an application using .NET 6.0 Learn how to create a C# hello-world application. Procedure Create a new Console application in a directory called my-app : The output returns: A simple Hello World console application is created from a template. The application is stored in the specified my-app directory. Verification steps Run the project: The output returns:

Commands:
dotnet new console --output my-app
The template "Console Application" was created successfully. Processing post-creation actions Running 'dotnet restore' on my-app /my-app.csproj Determining projects to restore Restored /home/ username / my-app /my-app.csproj (in 67 ms). Restore succeeded.
dotnet run --project my-app
Hello World!
Chapter 4. File storage Ceph File System (CephFS) is a file system compatible with POSIX standards that is built on top of Ceph's distributed object store, called RADOS (Reliable Autonomic Distributed Object Storage). Ceph File System CephFS provides file access to a Red Hat Ceph Storage cluster and uses the POSIX semantics wherever possible. 4.1. File storage common workloads The most common workload for using CephFS is for data security. For more information about securing your data by using CephFS, see Ceph File System . 4.2. Getting started with file storage This section lists the relevant tasks required for working with file storage. Limitations To know about the limitations and POSIX standards to consider when working with Ceph File System, see Ceph File System limitations and the POSIX standards . Setting up the Ceph File System Use the following procedures to setup a Ceph File System. Creating client users for a Ceph File System . Mounting the Ceph File System as a kernel client or Mounting the Ceph File System as a FUSE client . Client features . Basic CephFS CLI commands This information is for a quick reference of basic CephFS CLI commands. For a full list and more detailed information about each command, see Management of Ceph File System volumes, sub-volume groups, and sub-volumes . Creating a Ceph File System volume. Syntax Creating a File System subvolume. Syntax Creating a File System subvolume group. Syntax Listing Ceph File System volumes. Syntax Listing Ceph File System subvolumes. Syntax Listing Ceph File System subvolume groups. Syntax Viewing information about a Ceph File system volume. Syntax Removing a Ceph File System volume. Syntax Removing a file system subvolume. Syntax Removing a file system subvolume group. Syntax Creating a snapshot of a file system subvolume. Syntax 4.3. Deploying the Ceph File System Understand the basic deployment procedures for Ceph File System. Detailed deployment instructions for Ceph File System is found in Deployment of the Ceph File System .

Commands:
ceph fs volume create VOLUME_NAME
ceph fs subvolume create VOLUME_NAME SUBVOLUME_NAME [--size SIZE_IN_BYTES --group_name SUBVOLUME_GROUP_NAME --pool_layout DATA_POOL_NAME --uid UID --gid GID --mode OCTAL_MODE ] [--namespace-isolated]
ceph fs subvolumegroup create VOLUME_NAME GROUP_NAME [--pool_layout DATA_POOL_NAME --uid UID --gid GID --mode OCTAL_MODE ]
ceph fs volume ls
ceph fs subvolume ls VOLUME_NAME
ceph fs subvolumegroup ls VOLUME_NAME
ceph fs volume info VOLUME_NAME
ceph fs volume rm VOLUME_NAME [--yes-i-really-mean-it]
ceph fs subvolume rm VOLUME_NAME SUBVOLUME_NAME
ceph fs subvolumegroup rm VOLUME_NAME GROUP_NAME [--force]
ceph fs subvolume snapshot create VOLUME_NAME SUBVOLUME_NAME SNAP_NAME [--group_name GROUP_NAME ]
3.3. Configuring Storage Devices By default, DM-Multipath includes support for the most common storage arrays that support DM-Multipath. The default configuration values, including supported devices, can be found in the multipath.conf.defaults file. If you need to add a storage device that is not supported by default as a known multipath device, edit the /etc/multipath.conf file and insert the appropriate device information. For example, to add information about the HP Open-V series the entry looks like this, where %n is the device name: For more information on the devices section of the configuration file, see Section 4.5, "Configuration File Devices" .

Commands:
devices { device { vendor "HP" product "OPEN-V." getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n" } }
Chapter 1. Logging into the automation controller dashboard after installation After you install automation controller, you must log in to the Dashboard. Procedure With the login information provided after your installation completed, open a web browser and log in to the automation controller by navigating to its server URL at: https://<CONTROLLER_SERVER_NAME>/ Use the credentials specified during the installation process to login: The default username is admin . The password for admin is the value specified. Click the More Actions icon ... to the desired user. Click Edit . Edit the required details and click Save .

Commands:
Chapter 3. Support and compatibility This section highlights supported version updates in Red Hat Decision Manager 7.13. Note Oracle WebLogic Server (WLS) was not tested or verified for Red Hat Decision Manager 7.13.4 SP2. For a complete list of supported configurations, see Red Hat Decision Manager 7 Supported Configurations . Table 3.1. Supported configurations in Red Hat Decision Manager 7.13 Component Supported Version Notes Red Hat build of Quarkus 2.7.x NA Red Hat JBoss EAP 7.4.x Red Hat Decision Manager now supports Red Hat JBoss EAP version 7.4.2 or later Spring Boot 2.5.12 NA AMQ Streams 2.2 Supported for high-availability event-driven decisions Red Hat JBoss Web Server 5.6 NA Red Hat OpenShift Container Platform 4.12 NA

Commands:
Appendix B. Revision History Revision History Revision 0.0-0.19 Tue Mar 29 2016 Lenka Spackova Updated New Features (dm-cache fully supported; hardware enablement). Revision 0.0-0.18 Fri Oct 23 2015 Lenka Spackova Added zipl known issue. Revision 0.0-0.17 Thu Aug 13 2015 Laura Bailey Updated known issues. Revision 0.0-0.16 Wed Aug 05 2015 Laura Bailey Updated to include Red Hat Access Insights and some minor corrections. Revision 0.0-0.15 Tue Jul 28 2015 Laura Bailey Release of the Red Hat Enterprise Linux 6.7 Release Notes.

Commands:
14.4. Automatic ID Range Extension After Deleting a Replica When you delete a functioning replica, the ipa-replica-manage del command retrieves the ID ranges that were assigned to the replica and adds them as a range to other available IdM replicas. This ensures that ID ranges remain available to be used by other replicas. After you delete a replica, you can verify which ID ranges are configured for other servers by using the ipa-replica-manage dnarange-show and ipa-replica-manage dnanextrange-show commands, described in Section 14.3, "Displaying Currently Assigned ID Ranges" .

Commands:
Appendix C. Applying labels and taints to Red Hat OpenShift node In order to have our control pods run on a dedicated Red Hat OpenShift node, one must set the appropriate labels and taints to the specified node. In this example, we will select one of our Red Hat OpenShift nodes with the role worker the label aap_node_type=control . Get the name of one of the nodes you want to label running Choose a node from the list and note its name, e.g. worker1 Apply the aap_node_type=control label to the node Note Replace <node-name> with the name of the node you want to label. Verify the creation of the label as follows: With the label created, the step is to add a NoSchedule taint to the worker node we have already created a label for. The following command adds a NoSchedule taint to our node: dedicated : This is the key of the taint that is an arbitrary string supplied that identifies the taint. AutomationController : This is an arbitrary value given to the taint. NoSchedule : This is the effect of the taint which specifies no pods that don't tolerate this taint will be scheduled onto this node. By applying this taint to our node, we are telling the Kubernetes scheduler to reserve this node for certain types of workloads that tolerate the taint. In this case, we are reserving the node for workloads with the dedicated=AutomationController toleration. Verify the taint has been applied

Commands:
oc get nodes
oc label node <node-name> aap_node_type=control
oc get nodes --show-labels | grep <node-name>
adm taint nodes <node-name> dedicated=AutomationController:NoSchedule
oc get nodes -o jsonpath='{range.items[*]}{@.metadata.name}{"\t"}{@.spec.taints[*].key}:{@.spec.taints[*].value}{"\n"}{end}' | grep AutomationController
Chapter 16. References The following references are pointers to additional information that is relevant to SELinux but beyond the scope of this guide. Note that due to the rapid development of SELinux, some of this material may only apply to specific releases of Red Hat Enterprise Linux. Books SELinux by Example Mayer, MacMillan, and Caplan Prentice Hall, 2007 SELinux: NSA's Open Source Security Enhanced Linux Bill McCarty O'Reilly Media Inc., 2004 Tutorials and Help Tutorials and talks from Russell Coker http://www.coker.com.au/selinux/talks/ibmtu-2004/ Dan Walsh's Journal http://danwalsh.livejournal.com/ Red Hat Knowledgebase https://access.redhat.com/site/ General Information NSA SELinux main website http://www.nsa.gov/research/selinux/index.shtml NSA SELinux FAQ http://www.nsa.gov/research/selinux/faqs.shtml Mailing Lists NSA SELinux mailing list http://www.nsa.gov/research/selinux/list.shtml Fedora SELinux mailing list http://www.redhat.com/mailman/listinfo/fedora-selinux-list Community SELinux Project Wiki http://selinuxproject.org/page/Main_Page SELinux community page http://selinux.sourceforge.net/ IRC irc.freenode.net, #selinux

Commands:
16.16. Choosing a Disk Encryption Passphrase If you selected the Encrypt System option, the installer prompts you for a passphrase with which to encrypt the partitions on the system. Partitions are encrypted using the Linux Unified Key Setup - refer to Appendix C, Disk Encryption for more information. Figure 16.37. Enter passphrase for encrypted partition Choose a passphrase and type it into each of the two fields in the dialog box. You must provide this passphrase every time that the system boots. Warning If you lose this passphrase, any encrypted partitions and the data on them will become completely inaccessible. There is no way to recover a lost passphrase. Note that if you perform a kickstart installation of Red Hat Enterprise Linux, you can save encryption passphrases and create backup encryption passphrases during installation. Refer to Section C.3.2, "Saving Passphrases" and Section C.3.3, "Creating and Saving Backup Passphrases" .

Commands:
7.194. sendmail 7.194.1. RHBA-2015:1299 - sendmail bug fix update Updated sendmail packages that fix several bugs are now available for Red Hat Enterprise Linux 6. Sendmail is a Mail Transport Agent (MTA) used to send mail between machines. Bug Fixes BZ# 640234 Previously, the sendmail macro MAXHOSTNAMELEN allowed only 63 characters for the host name length. However, in some cases, it was used against the length of a fully-qualified domain name (FQDN), which has a maximum length of 255 characters. Consequently, FQDN resolution did not work correctly in some cases. To fix this bug, MAXHOSTNAMELEN now allows a maximum of 255 characters. BZ# 837007 The sendmail queue runner could previously terminate unexpectedly under certain circumstances. Consequently, sendmail stopped processing the mail queue. This update introduces a fix that prevents the source code from triggering an assertion in the OpenLDAP code when the connection to an LDAP server is lost while making a query. As a result, the assertion no longer causes the queue runner to terminate, and sendmail continues processing the mail queue as expected. BZ# 845821 Under certain circumstances, sendmail previously recorded a very large number of log messages that reported failures to set the close-on-exec flag. The Milter implementation has been modified to perform socket validation before the fnctl() function attempts to set close-on-exec. As a result, fnctl() is no longer called on invalid sockets, and the described log messages no longer occur. BZ# 890227 Prior to this update, the ldap_routing feature did not work as expected. If ldap_routing was used, sendmail reported the "-T<TMPF>" option missing, and the user was required to insert "-T<TMPF>" manually. With this update, the macro for generating configuration for ldap_routing has been fixed, and the user is no longer required to add "-T<TMPF>" manually when using ldap_routing. BZ# 1106852 Previously, the "{client_port}" value could not be used on little-endian machines, for example in mail filters, because it was set incorrectly. This update corrects the "{client_port}" value on little-endian machines. Users of sendmail are advised to upgrade to these updated packages, which fix these bugs.

Commands:
5.2.4. /proc/cpuinfo This virtual file identifies the type of processor used by your system. The following is an example of the output typical of /proc/cpuinfo : processor - Provides each processor with an identifying number. On systems that have one processor, only a 0 is present. cpu family - Authoritatively identifies the type of processor in the system. For an Intel-based system, place the number in front of "86" to determine the value. This is particularly helpful for those attempting to identify the architecture of an older system such as a 586, 486, or 386. Because some RPM packages are compiled for each of these particular architectures, this value also helps users determine which packages to install. model name - Displays the common name of the processor, including its project name. cpu MHz - Shows the precise speed in megahertz for the processor to the thousandths decimal place. cache size - Displays the amount of level 2 memory cache available to the processor. siblings - Displays the number of sibling CPUs on the same physical CPU for architectures which use hyper-threading. flags - Defines a number of different qualities about the processor, such as the presence of a floating point unit (FPU) and the ability to process MMX instructions.

Commands:
processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Xeon(TM) CPU 2.40GHz stepping : 7 cpu MHz : 2392.371 cache size : 512 KB physical id : 0 siblings : 2 runqueue : 0 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm bogomips : 4771.02
17.3. xinetd The xinetd daemon is a TCP wrapped super service which controls access to a subset of popular network services including FTP, IMAP, and Telnet. It also provides service-specific configuration options for access control, enhanced logging, binding, redirection, and resource utilization control. When a client host attempts to connect to a network service controlled by xinetd , the super service receives the request and checks for any TCP wrappers access control rules. If access is allowed, xinetd verifies that the connection is allowed under its own access rules for that service and that the service is not consuming more than its alloted amount of resources or is in breach of any defined rules. It then starts an instance of the requested service and passes control of the connection to it. Once the connection is established, xinetd does not interfere further with communication between the client host and the server.

Commands:
Support Red Hat build of MicroShift 4.18 Using support tools for MicroShift Red Hat OpenShift Documentation Team

Commands:
sudo journalctl -u microshift-etcd.scope
microshift-etcd version
microshift-etcd Version: 4.17.1 Base etcd Version: 3.5.13
microshift-etcd version -o json
{ "major": "4", "minor": "16", "gitVersion": "4.17.1~rc.1", "gitCommit": "140777711962eb4e0b765c39dfd325fb0abb3622", "gitTreeState": "clean", "buildDate": "2024-05-10T16:37:53Z", "goVersion": "go1.21.9" "compiler": "gc", "platform": "linux/amd64", "patch": "", "etcdVersion": "3.5.13" }
etcd: memoryLimitMB: 128
sudo systemctl restart microshift
systemctl show --property=MemoryHigh microshift-etcd.scope
microshift-sos-report
sosreport (version 4.5.1) This command will collect diagnostic and configuration information from this Red Hat Enterprise Linux system and installed applications. An archive containing the collected information will be generated in /var/tmp/sos.o0sznf_8 and may be provided to a Red Hat support representative. Any information provided to Red Hat will be treated in accordance with the published support policies at: Distribution Website : https://www.redhat.com/ Commercial Support : https://www.access.redhat.com/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Setting up archive Setting up plugins Running plugins. Please wait Starting 1/2 microshift [Running: microshift] Starting 2/2 microshift_ovn [Running: microshift microshift_ovn] Finishing plugins [Running: microshift] Finished running plugins Found 1 total reports to obfuscate, processing up to 4 concurrently sosreport-microshift-rhel9-2023-03-31-axjbyxw : Beginning obfuscation sosreport-microshift-rhel9-2023-03-31-axjbyxw : Obfuscation completed Successfully obfuscated 1 report(s) Creating compressed archive A mapping of obfuscated elements is available at /var/tmp/sosreport-microshift-rhel9-2023-03-31-axjbyxw-private_map Your sosreport has been generated and saved in: /var/tmp/sosreport-microshift-rhel9-2023-03-31-axjbyxw-obfuscated.tar.xz Size 444.14KiB Owner root sha256 922e5ff2db25014585b7c6c749d2c44c8492756d619df5e9838ce863f83d4269 Please send this file to your support representative.
oc get namespaces kube-system -o jsonpath={.metadata.uid}
7cf13853-68f4-454e-8f5c-1af748cbfb1a
sudo cat /var/lib/microshift/cluster-id
7cf13853-68f4-454e-8f5c-1af748cbfb1a
sudo cat /var/lib/microshift/cluster-id
7cf13853-68f4-454e-8f5c-1af748cbfb1a
19.9. Configuring Additional Local Domains Creating additional local domains other than the default internal domain is also supported. This can be done using the ovirt-engine-extension-aaa-jdbc extension and allows you to create multiple domains without attaching external directory servers, though the use case may not be common for enterprise environments. Additionally created local domains will not get upgraded autonmatically during standard Red Hat Virtualization upgrades and need to be upgraded manually for each future release. For more information on creating additional local domains and how to upgrade the domains, see the README file at /usr/share/doc/ovirt-engine-extension-aaa-jdbc- version /README.admin .

Commands: