mtpti5iD/redhat-docs_dataset huggingface dataset:
3.6. Configuring Cluster Members Configuring cluster members consists of initially configuring nodes in a newly configured cluster, adding members, and deleting members. The following sections provide procedures for initial configuration of nodes, adding nodes, and deleting nodes: Section 3.6.1, "Initially Configuring Members" Section 3.6.2, "Adding a Member to a Running Cluster" Section 3.6.3, "Deleting a Member from a Cluster" 3.6.1. Initially Configuring Members Creating a cluster consists of selecting a set of nodes (or members) to be part of the cluster. Once you have completed the initial step of creating a cluster and creating fence devices, you need to configure cluster nodes. To initially configure cluster nodes after creating a new cluster, follow the steps in this section. The starting point of the procedure is at the cluster-specific page that you navigate to from Choose a cluster to administer displayed on the cluster tab. At the detailed menu for the cluster (below the clusters menu), click Nodes . Clicking Nodes causes the display of an Add a Node element and a Configure element with a list of the nodes already configured in the cluster. Click a link for a node at either the list in the center of the page or in the list in the detailed menu under the clusters menu. Clicking a link for a node causes a page to be displayed for that link showing how that node is configured. At the bottom of the page, under Main Fencing Method , click Add a fence device to this level . Select a fence device and provide parameters for the fence device (for example port number). Note You can choose from an existing fence device or create a new fence device. Click Update main fence properties and wait for the change to take effect.

Commands:
B.103.3. RHSA-2011:0369 - Moderate: wireshark security update Updated wireshark packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Wireshark is a program for monitoring network traffic. Wireshark was previously known as Ethereal. CVE-2011-0444 A heap-based buffer overflow flaw was found in the Wireshark MAC-LTE dissector. If Wireshark read a malformed packet off a network or opened a malicious dump file, it could crash or, possibly, execute arbitrary code as the user running Wireshark. CVE-2011-0713 A heap-based buffer overflow flaw was found in the way Wireshark processed signaling traces generated by the Gammu utility on Nokia DCT3 phones running in Netmonitor mode. If Wireshark opened a specially-crafted capture file, it could crash or, possibly, execute arbitrary code as the user running Wireshark. CVE-2011-0538 , CVE-2011-1139 , CVE-2011-1140 , CVE-2011-1141 Several denial of service flaws were found in Wireshark. Wireshark could crash or stop responding if it read a malformed packet off a network, or opened a malicious dump file. Users of Wireshark should upgrade to these updated packages, which contain Wireshark version 1.2.15, and resolve these issues. All running instances of Wireshark must be restarted for the update to take effect.

Commands:
Chapter 29. Ruby (DEPRECATED) Overview Ruby is a dynamic, open source programming language with a focus on simplicity and productivity. It has an elegant syntax that is natural to read and easy to write. The Ruby support is part of the camel-script module. Important Ruby in Apache Camel is deprecated and will be removed in a future release. Adding the script module To use Ruby in your routes you need to add a dependency on camel-script to your project as shown in Example 29.1, "Adding the camel-script dependency" . Example 29.1. Adding the camel-script dependency Static import To use the ruby() static method in your application code, include the following import statement in your Java source files: Built-in attributes Table 29.1, "Ruby attributes" lists the built-in attributes that are accessible when using Ruby. Table 29.1. Ruby attributes Attribute Type Value context org.apache.camel.CamelContext The Camel Context exchange org.apache.camel.Exchange The current Exchange request org.apache.camel.Message The IN message response org.apache.camel.Message The OUT message properties org.apache.camel.builder.script.PropertiesFunction Function with a resolve method to make it easier to use the properties component inside scripts. The attributes all set at ENGINE_SCOPE . Example Example 29.2, "Route using Ruby" shows a route that uses Ruby. Example 29.2. Route using Ruby Using the properties component To access a property value from the properties component, invoke the resolve method on the built-in properties attribute, as follows: Where PropKey is the key of the property you want to resolve, where the key value is of String type. For more details about the properties component, see Properties in the Apache Camel Component Reference Guide .

Commands:
<!-- Maven POM File --> <dependencies> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-script</artifactId> <version>USD{camel-version}</version> </dependency> </dependencies>
import static org.apache.camel.builder.script.ScriptBuilder.*;
<camelContext> <route> <from uri="direct:start"/> <choice> <when> <langauge langauge="ruby">USDrequest.headers['user'] == 'admin'</langauge> <to uri="seda:adminQueue"/> </when> <otherwise> <to uri="seda:regularQueue"/> </otherwise> </choice> </route> </camelContext>
.setHeader("myHeader").ruby("properties.resolve( PropKey )")
Chapter 11. Disabling Windows container workloads You can disable the capability to run Windows container workloads by uninstalling the Windows Machine Config Operator (WMCO) and deleting the namespace that was added by default when you installed the WMCO. 11.1. Uninstalling the Windows Machine Config Operator You can uninstall the Windows Machine Config Operator (WMCO) from your cluster. Prerequisites Delete the Windows Machine objects hosting your Windows workloads. Procedure From the Operators OperatorHub page, use the Filter by keyword box to search for Red Hat Windows Machine Config Operator . Click the Red Hat Windows Machine Config Operator tile. The Operator tile indicates it is installed. In the Windows Machine Config Operator descriptor page, click Uninstall . 11.2. Deleting the Windows Machine Config Operator namespace You can delete the namespace that was generated for the Windows Machine Config Operator (WMCO) by default. Prerequisites The WMCO is removed from your cluster. Procedure Remove all Windows workloads that were created in the openshift-windows-machine-config-operator namespace: USD oc delete --all pods --namespace=openshift-windows-machine-config-operator Verify that all pods in the openshift-windows-machine-config-operator namespace are deleted or are reporting a terminating state: USD oc get pods --namespace openshift-windows-machine-config-operator Delete the openshift-windows-machine-config-operator namespace: USD oc delete namespace openshift-windows-machine-config-operator Additional resources Deleting Operators from a cluster Removing Windows nodes

Commands:
oc delete --all pods --namespace=openshift-windows-machine-config-operator
oc get pods --namespace openshift-windows-machine-config-operator
oc delete namespace openshift-windows-machine-config-operator
Chapter 14. Access Control Lists Files and directories have permission sets for the owner of the file, the group associated with the file, and all other users for the system. However, these permission sets have limitations. For example, different permissions cannot be configured for different users. Thus, Access Control Lists (ACLs) were implemented. The Red Hat Enterprise Linux 4 kernel provides ACL support for the ext3 file system and NFS-exported file systems. ACLs are also recognized on ext3 file systems accessed via Samba. Along with support in the kernel, the acl package is required to implement ACLs. It contains the utilities used to add, modify, remove, and retrieve ACL information. The cp and mv commands copy or move any ACLs associated with files and directories. 14.1. Mounting File Systems Before using ACLs for a file or directory, the partition for the file or directory must be mounted with ACL support. If it is a local ext3 file system, it can mounted with the following command: For example: Alternatively, if the partition is listed in the /etc/fstab file, the entry for the partition can include the acl option: If an ext3 file system is accessed via Samba and ACLs have been enabled for it, the ACLs are recognized because Samba has been compiled with the --with-acl-support option. No special flags are required when accessing or mounting a Samba share. 14.1.1. NFS By default, if the file system being exported by an NFS server supports ACLs and the NFS client can read ACLs, ACLs are utilized by the client system. To disable ACLs on NFS shares when configuring the server, include the no_acl option in the /etc/exports file. To disable ACLs on an NFS share when mounting it on a client, mount it with the no_acl option via the command line or the /etc/fstab file.

Commands:
mount -t ext3 -o acl <device-name> <partition>
mount -t ext3 -o acl /dev/VolGroup00/LogVol02 /work
LABEL=/work /work ext3 acl 1 2
14.3. The (Non-transactional) CarMart Quickstart Using JBoss EAP The Carmart (non-transactional) quickstart is supported for JBoss Data Grid's Library Mode with the JBoss EAP container. Report a bug 14.3.1. Quickstart Prerequisites The prerequisites for this quickstart are as follows: Java 6.0 (Java SDK 1.6) or better JBoss Enterprise Application Platform 6.x or JBoss Enterprise Web Server 2.x Maven 3.0 or better Configure the Maven Repository. For details, see Chapter 3, Install and Use the Maven Repositories Report a bug 14.3.2. Build and Deploy the CarMart Quickstart to JBoss EAP The following procedure provides directions to build and deploy the CarMart application to JBoss EAP. Prerequisites Prerequisites for this procedure are as follows: Obtain the supported JBoss Data Grid Library Mode distribution files. Ensure that the JBoss Data Grid and JBoss Enterprise Application Platform Maven repositories are installed and configured. For details, see Chapter 3, Install and Use the Maven Repositories Select a JBoss server to use (JBoss Enterprise Application Platform 6 (or better) or JBoss EAP 6 (or better). Procedure 14.1. Build and Deploy CarMart to JBoss EAP Start JBoss EAP Depending on your operating system, use the appropriate command from the following to start the first instance of your selected application server: For Linux users: For Windows users: Navigate to the Root Directory Open a command line and navigate to the root directory of this quickstart. Build and Deploy the Application Use the following command to build and deploy the application using Maven: Result The target war file ( target/ jboss-carmart.war ) is deployed to the running instance of JBoss EAP. Report a bug 14.3.3. View the CarMart Quickstart on JBoss EAP The following procedure outlines how to view the CarMart quickstart on JBoss EAP: Prerequisite The CarMart quickstart must be built and deployed to be viewed. Procedure 14.2. View the CarMart Quickstart on JBoss EAP To view the application, use your browser to navigate to the following link: Report a bug 14.3.4. Remove the CarMart Quickstart from JBoss EAP The following procedure provides directions to remove a deployed application from JBoss EAP. Procedure 14.3. Remove an Application from JBoss EAP To remove an application, use the following from the root directory of this quickstart: Report a bug

Commands:
USDJBOSS_HOME/bin/standalone.sh
USDJBOSS_HOME\bin\standalone.bat
mvn clean package jboss-as:deploy
http://localhost:8080/jboss-carmart
mvn jboss-as:undeploy
Chapter 3. Installing Windows virtual machines Installing a Windows virtual machine involves the following key steps: Create a blank virtual machine on which to install an operating system. Add a virtual disk for storage. Add a network interface to connect the virtual machine to the network. Attach the Windows guest tools CD to the virtual machine so that VirtIO-optimized device drivers can be installed during the operating system installation. Install a Windows operating system on the virtual machine. See your operating system's documentation for instructions. During the installation, install guest agents and drivers for additional virtual machine functionality. When all of these steps are complete, the new virtual machine is functional and ready to perform tasks. 3.1. Creating a virtual machine When creating a new virtual machine, you specify its settings. You can edit some of these settings later, including the chipset and BIOS type. For more information, see UEFI and the Q35 chipset in the Administration Guide . .Prerequisites Note Before you can use this virtual machine, you must: Install an operating system Install a VirtIO-optimized disk and network drivers Procedure You can change the default virtual machine name length with the engine-config tool. Run the following command on the Manager machine: # engine-config --set MaxVmNameLength= integer Click Compute Virtual Machines . Click New . This opens the New Virtual Machine window. Select an Operating System from the drop-down list. Enter a Name for the virtual machine. Add storage to the virtual machine: under Instance Images , click Attach or Create to select or create a virtual disk . Click Attach and select an existing virtual disk. or Click Create and enter a Size(GB) and Alias for a new virtual disk. You can accept the default settings for all other fields, or change them if required. See Explanation of settings in the New Virtual Disk and Edit Virtual Disk windows for more details on the fields for all disk types. Connect the virtual machine to the network. Add a network interface by selecting a vNIC profile from the nic1 drop-down list at the bottom of the General tab. Specify the virtual machine's Memory Size on the System tab. In the Boot Options tab, choose the First Device that the virtual machine will use to boot. You can accept the default settings for all other fields, or change them if required. For more details on all fields in the New Virtual Machine window, see Explanation of settings in the New Virtual Machine and Edit Virtual Machine Windows . Click OK . The new virtual machine is created and displays in the list of virtual machines with a status of Down .

Commands:
engine-config --set MaxVmNameLength= integer
Chapter 2. Overview of certification process Prerequisites Establish a certification relationship with Red Hat. Establish a test environment consisting of your product and the Red Hat product combination to be certified. Perform preliminary testing to ensure this combination works well. Install the redhat-certification tool. Procedure Create a certification request for a specific system or hardware component using redhat-certification. Red Hat's certification team applies the certification policies to the hardware specifications to create the official test plan. Run the tests specified in the official test plan and submit results using redhat-certification to Red Hat for analysis. The certification team analyzes the test results and marking credit as appropriate and communicating any required retesting. Provide Red Hat with a representative hardware sample that covers the items that are being certified. When all tests have passing results, the certification is complete and the entry is made visible to the public on the external Red Hat Hardware Certification website at Certifications . Additional resources For more information about hardware certification process, see Hardware Certification Program Overview section of the Hardware Certification Test Suite User Guide.

Commands:
Chapter 49. QuotasPluginStrimzi schema reference Used in: KafkaClusterSpec The type property is a discriminator that distinguishes use of the QuotasPluginStrimzi type from QuotasPluginKafka . It must have the value strimzi for the type QuotasPluginStrimzi . Property Property type Description type string Must be strimzi . producerByteRate integer A per-broker byte-rate quota for clients producing to a broker, independent of their number. If clients produce at maximum speed, the quota is shared equally between all non-excluded producers. Otherwise, the quota is divided based on each client's production rate. consumerByteRate integer A per-broker byte-rate quota for clients consuming from a broker, independent of their number. If clients consume at maximum speed, the quota is shared equally between all non-excluded consumers. Otherwise, the quota is divided based on each client's consumption rate. minAvailableBytesPerVolume integer Stop message production if the available size (in bytes) of the storage is lower than or equal to this specified value. This condition is mutually exclusive with minAvailableRatioPerVolume . minAvailableRatioPerVolume number Stop message production if the percentage of available storage space falls below or equals the specified ratio (set as a decimal representing a percentage). This condition is mutually exclusive with minAvailableBytesPerVolume . excludedPrincipals string array List of principals that are excluded from the quota. The principals have to be prefixed with User: , for example User:my-user;User:CN=my-other-user .

Commands:
Chapter 2. Installing the MTA plugin for IntelliJ IDEA You can install the MTA plugin in the Ultimate and the Community Edition releases of IntelliJ IDEA. Prerequisites The following are the prerequisites for the Migration Toolkit for Applications (MTA) installation: Java Development Kit (JDK) is installed. MTA supports the following JDKs: OpenJDK 11 OpenJDK 17 Oracle JDK 11 Oracle JDK 17 Eclipse TemurinTM JDK 11 Eclipse TemurinTM JDK 17 8 GB RAM macOS installation: the value of maxproc must be 2048 or greater. The latest version of mta-cli from the MTA download page Procedure In IntelliJ IDEA, click the Plugins tab on the Welcome screen. Enter Migration Toolkit for Applications in the Search field on the Marketplace tab. Select the Migration Toolkit for Applications (MTA) by Red Hat plugin and click Install . The plugin is listed on the Installed tab.

Commands:
5.8.2. Changing the Default Context As mentioned in Section 5.7, "The file_t and default_t Types" , on file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the file_t type. If it is desirable to use a different default context, mount the file system with the defcontext option. The following example mounts a newly-created file system (on /dev/sda2 ) to the newly-created /test/ directory. It assumes that there are no rules in /etc/selinux/targeted/contexts/files/ that define a context for the /test/ directory: In this example: the defcontext option defines that system_u:object_r:samba_share_t:s0 is "the default security context for unlabeled files" [9] . when mounted, the root directory ( /test/ ) of the file system is treated as if it is labeled with the context specified by defcontext (this label is not stored on disk). This affects the labeling for files created under /test/ : new files inherit the samba_share_t type, and these labels are stored on disk. files created under /test/ while the file system was mounted with a defcontext option retain their labels. [9] Morris, James. "Filesystem Labeling in SELinux". Published 1 October 2004. Accessed 14 October 2008: http://www.linuxjournal.com/article/7426 .

Commands:
~]# mount /dev/sda2 /test/ -o defcontext="system_u:object_r:samba_share_t:s0"
14.4. Retrieving ACLs To determine the existing ACLs for a file or directory, use the getfacl command: It returns output similar to the following: If a directory is specified, and it has a default ACL, the default ACL is also displayed such as:

Commands:
getfacl <filename>
file: file owner: andrius group: andrius user::rw- user:smoore:r-- group::r-- mask::r-- other::r--
file: file owner: andrius group: andrius user::rw- user:smoore:r-- group::r-- mask::r-- other::r-- default:user::rwx default:user:andrius:rwx default:group::r-x default:mask::rwx default:other::r-x
8.115. mesa 8.115.1. RHBA-2013:1559 - mesa bug fix and enhancement update Updated mesa packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. Mesa provides a 3D graphics API that is compatible with Open Graphics Library (OpenGL). It also provides hardware-accelerated drivers for many popular graphics chips. Bug Fixes BZ# 879637 On certain Intel GT2+ processors, segmentation faults could have been reported in the output of the dmesg command after running a Piglit quick-driver test. A patch has been applied to address his bug, and the unwanted behavior no longer occurs. BZ# 908547 Prior to this update, compressed texture size checks were performed in an incorrect manner. Consequently, checking the image size against the compression block size could cause certain applications to terminate unexpectedly. The underlying source code has been modified, and the texture error no longer causes the applications to crash in the described scenario. Enhancements BZ# 818345 Support for future Intel 2D and 3D graphics has been added to allow systems using future Intel processors to be certified through the Red Hat Hardware Certification program. BZ# 957792 With this update, the mesa-private-llvm library has been added. Users of mesa are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 1. Installing the Operating System Before setting up for specific development needs, the underlying system must be set up. Install Red Hat Enterprise Linux in the Workstation variant. Follow the instructions in the Red Hat Enterprise Linux Installation Guide . While installing, pay attention to software selection . Select the Development and Creative Workstation system profile and enable the installation of Add-ons appropriate for your development needs. The relevant Add-ons are listed in each of the following sections focusing on various types of development. To develop applications that cooperate closely with the Linux kernel such as drivers, enable automatic crash dumping with kdump during the installation. After the system itself is installed, register it and attach the required subscriptions. Follow the instructions in Red Hat Enterprise Linux System Administrator's Guide, Chapter 7., Registering the System and Managing Subscriptions . The following sections list the particular subscriptions that must be attached for the respective type of development. More recent versions of development tools and utilities are available as Red Hat Software Collections. For instructions on accessing Red Hat Software Collections, see Red Hat Software Collections Release Notes, Chapter 2., Installation . Additional Resources Red Hat Enterprise Linux Installation Guide - Subscription Manager Red Hat Subscription Management Red Hat Enterprise Linux 7 Package Manifest

Commands: