mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. Managing Red Hat High Availability Add-On With ccs This chapter describes various administrative tasks for managing the Red Hat High Availability Add-On by means of the ccs command, which is supported as of the Red Hat Enterprise Linux 6.1 release and later. This chapter consists of the following sections: Section 7.1, "Managing Cluster Nodes" Section 7.2, "Starting and Stopping a Cluster" Section 7.3, "Diagnosing and Correcting Problems in a Cluster" 7.1. Managing Cluster Nodes This section documents how to perform the following node-management functions with the ccs command: Section 7.1.1, "Causing a Node to Leave or Join a Cluster" Section 7.1.2, "Adding a Member to a Running Cluster" 7.1.1. Causing a Node to Leave or Join a Cluster You can use the ccs command to cause a node to leave a cluster by stopping cluster services on that node. Causing a node to leave a cluster does not remove the cluster configuration information from that node. Making a node leave a cluster prevents the node from automatically joining the cluster when it is rebooted. To cause a node to leave a cluster, execute the following command, which stops cluster services on the node specified with the -h option: When you stop cluster services on a node, any service that is running on that node will fail over. To delete a node entirely from the cluster configuration, use the --rmnode option of the ccs command, as described in Section 6.4, "Creating and Modifying a Cluster" . To cause a node to rejoin a cluster execute the following command, which starts cluster services on the node specified with the -h option: 7.1.2. Adding a Member to a Running Cluster To add a member to a running cluster, add a node to the cluster as described in Section 6.4, "Creating and Modifying a Cluster" . After updating the configuration file, propagate the file to all nodes in the cluster and be sure to activate the new cluster configuration file, as described in Section 6.15, "Propagating the Configuration File to the Cluster Nodes" . Note When you add a node to a cluster that uses UDPU transport, you must restart all nodes in the cluster for the change to take effect.

Commands:
ccs -h host --stop
ccs -h host --start
Chapter 3. Getting started This chapter guides you through the steps to set up your environment and run a simple messaging program. 3.1. Prerequisites You must complete the installation procedure for your environment. You must have an AMQP 1.0 message broker listening for connections on interface localhost and port 5672 . It must have anonymous access enabled. For more information, see Starting the broker . You must have a queue named amq.topic . For more information, see Creating a queue . 3.2. Running HelloWorld on Red Hat Enterprise Linux The Hello World example creates a connection to the broker, sends a message containing a greeting to the amq.topic queue, and receives it back. On success, it prints the received message to the console. Change to the <install-dir> /examples/netcoreapp3/HelloWorld-simple and use dotnet run to build and execute the program. USD cd <install-dir> /examples/netcoreapp3/HelloWorld-simple USD dotnet run Hello World! 3.3. Running Hello World on Microsoft Windows The Hello World example creates a connection to the broker, sends a message containing a greeting to the amq.topic queue, and receives it back. On success, it prints the received message to the console. Procedure Navigate to <install-dir> and open the amqp.sln solution file in Visual Studio. Select Build Solution from the Build menu to compile the solution. Open a command prompt window and execute the following commands to send and receive a message: > cd <install-dir> \bin\Debug > HelloWorld-simple Hello World!

Commands:
cd <install-dir> /examples/netcoreapp3/HelloWorld-simple dotnet run Hello World!
> cd <install-dir> \bin\Debug > HelloWorld-simple Hello World!
Appendix A. Unsupported JDBC Methods A.1. Unsupported JDBC Methods This appendix lists those JDBC methods that JBoss Data Virtualization does not support, based on the JDK 1.7 JDBC. Unless specified below, JBoss Data Virtualization supports all other JDBC Methods. Those methods listed without comments throw an exception of type SQLException stating that it is not supported. Where specified, some listed methods do not throw an exception, but possibly exhibit unexpected behavior. If no arguments are specified, then all related (overridden) methods are not supported. If an argument is listed then only those forms of the method specified are not supported.

Commands:
Chapter 7. Desktop In Red Hat Enterprise Linux 6, the GUI console has moved from tty7 to tty1. 7.1. GDM Configuration A number of GDM settings are now managed within GConf. The GDM default greeter is called the simple Greeter and is configured using GConf. Default values are stored in GConf in the gdm-simple-greeter.schemas file. Use gconftool2 or gconf-editor to edit these values. The following options exist for the Greeter: /apps/gdm/simple-greeter/banner_message_enable Controls whether the banner message text is displayed. /apps/gdm/simple-greeter/banner_message_text Specifies the text banner message to show on the greeter window. /apps/gdm/simple-greeter/logo_icon_name Set to the themed icon name to use for the greeter logo. /apps/gdm/simple-greeter/disable_restart_buttons Controls whether to show the restart buttons in the login window. /apps/gdm/simple-greeter/wm_use_compiz Controls whether compiz is used as the window manager instead of metacity. Plug-ins can also be disabled using GConf. For example, if you want to disable the sound plug-in then unset the following key: /apps/gdm/simple-greeter/settings-manager-plugins/sound/active .

Commands:
false (Boolean)
NULL (string)
computer (string)
false (Boolean)
false (Booleans)
7.3. Editing a Template Once a template has been created, its properties can be edited. Because a template is a copy of a virtual machine, the options available when editing a template are identical to those in the Edit Virtual Machine window. Editing a Template Click Compute Templates and select a template. Click Edit . Change the necessary properties. Click Show Advanced Options and edit the template's settings as required. The settings that appear in the Edit Template window are identical to those in the Edit Virtual Machine window, but with the relevant fields only. See Section A.1, "Explanation of Settings in the New Virtual Machine and Edit Virtual Machine Windows" for details. Click OK .

Commands:
Chapter 20. Sending cloud events from Data Grid clusters Configure Data Grid as a Knative source by sending CloudEvents to Apache Kafka topics. Important Sending cloud events with Red Hat OpenShift Serverless is available as a technology preview feature. 20.1. Technology preview features Technology preview features or capabilities are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using technology preview features or capabilities for production. These features provide early access to upcoming product features, which enables you to test functionality and provide feedback during the development process. For more information, see Red Hat Technology Preview Features Support Scope . Important This feature is deprecated and will have no effect on Data Grid releases after RHDG 8.4.x. 20.2. Cloud events You can send CloudEvents from Data Grid clusters when entries in caches are created, updated, removed, or expired. Data Grid sends structured events to Kafka in JSON format, as in the following example: { "specversion": "1.0", "source": "/infinispan/<cluster_name>/<cache_name>", "type": "org.infinispan.entry.created", "time": "<timestamp>", "subject": "<key-name>", "id": "key-name:CommandInvocation:node-name:0", "data": { "property": "value" } } Field Description type Prefixes events for Data Grid cache entries with org.infinispan.entry . data Entry value. subject Entry key, converted to string. id Generated identifier for the event. 20.3. Enabling cloud events Configure Data Grid to send CloudEvents . Prerequisites Set up an Kafka cluster that listens for Data Grid topics. Procedure Add spec.cloudEvents to your Infinispan CR. Configure the number of acknowledgements with the spec.cloudEvents.acks field. Values are "0", "1", or "all". List Kafka servers to which Data Grid sends events with the spec.cloudEvents.bootstrapServers field. Specify the Kafka topic for Data Grid events with the spec.cloudEvents.cacheEntriesTopic field. spec: cloudEvents: acks: "1" bootstrapServers: my-cluster-kafka-bootstrap_1.<namespace_1>.svc:9092,my-cluster-kafka-bootstrap_2.<namespace_2>.svc:9092 cacheEntriesTopic: target-topic Apply your changes.

Commands:
{ "specversion": "1.0", "source": "/infinispan/<cluster_name>/<cache_name>", "type": "org.infinispan.entry.created", "time": "<timestamp>", "subject": "<key-name>", "id": "key-name:CommandInvocation:node-name:0", "data": { "property": "value" } }
spec: cloudEvents: acks: "1" bootstrapServers: my-cluster-kafka-bootstrap_1.<namespace_1>.svc:9092,my-cluster-kafka-bootstrap_2.<namespace_2>.svc:9092 cacheEntriesTopic: target-topic
2.2. sVirt Labeling Like other services under the protection of SELinux, sVirt uses process-based mechanisms and restrictions to provide an extra layer of security over guest virtual machines. Under typical use, you should not even notice that sVirt is working in the background. This section describes the labeling features of sVirt. As shown in the following output, when using sVirt, each virtualized guest virtual machine process is labeled and runs with a dynamically generated level. Each process is isolated from other VMs with different levels: The actual disk images are automatically labeled to match the processes, as shown in the following output: The following table outlines the different context labels that can be assigned when using sVirt: Table 2.1. sVirt context labels SELinux Context Type / Description system_u:system_r:svirt_t:MCS1 Guest virtual machine processes. MCS1 is a random MCS field. Approximately 500,000 labels are supported. system_u:object_r:svirt_image_t:MCS1 Guest virtual machine images. Only svirt_t processes with the same MCS fields can read/write these images. system_u:object_r:svirt_image_t:s0 Guest virtual machine shared read/write content. All svirt_t processes can write to the svirt_image_t:s0 files. It is also possible to perform static labeling when using sVirt. Static labels allow the administrator to select a specific label, including the MCS/MLS field, for a guest virtual machine. Administrators who run statically-labeled virtualized guest virtual machines are responsible for setting the correct label on the image files. The guest virtual machine will always be started with that label, and the sVirt system will never modify the label of a statically-labeled virtual machine's content. This allows the sVirt component to run in an MLS environment. You can also run multiple guest virtual machines with different sensitivity levels on a system, depending on your requirements.

Commands:
ps -eZ | grep qemu system_u:system_r:svirt_t:s0:c87,c520 27950 ? 00:00:17 qemu-kvm
ls -lZ /var/lib/libvirt/images/* system_u:object_r:svirt_image_t:s0:c87,c520 image1
Preface Red Hat OpenShift Data Foundation supports deployment on existing Red Hat OpenShift Container Platform (RHOCP) Google Cloud clusters. Note Only internal OpenShift Data Foundation clusters are supported on Google Cloud. See Planning your deployment for more information about deployment requirements. To deploy OpenShift Data Foundation in internal mode, start with the requirements in Preparing to deploy OpenShift Data Foundation chapter and follow the appropriate deployment process based on your requirement: Deploy OpenShift Data Foundation on Google Cloud Deploy standalone Multicloud Object Gateway component

Commands:
20.3.4.3. Generating an RSA Key Pair for Version 1.3 and 1.5 Use the following steps to generate an RSA key pair, which is used by version 1 of the SSH Protocol. If you are only connecting between systems that use DSA, you do not need an RSA version 1.3 or RSA version 1.5 key pair. To generate an RSA (for version 1.3 and 1.5 protocol) key pair, type the following command at a shell prompt: Accept the default file location ( ~/.ssh/identity ). Enter a passphrase different from your account password. Confirm the passphrase by entering it again. The public key is written to ~/.ssh/identity.pub . The private key is written to ~/.ssh/identity . Do not give anyone the private key. Change the permissions of your .ssh directory and your key with the commands chmod 755 ~/.ssh and chmod 644 ~/.ssh/identity.pub . Copy the contents of ~/.ssh/identity.pub into the file ~/.ssh/authorized_keys on the machine to which you wish to connect. If the file ~/.ssh/authorized_keys does not exist, you can copy the file ~/.ssh/identity.pub to the file ~/.ssh/authorized_keys on the remote machine. If you are running GNOME, skip to Section 20.3.4.4, "Configuring ssh-agent with GNOME" . If you are not running GNOME, skip to Section 20.3.4.5, "Configuring ssh-agent " .

Commands:
ssh-keygen -t rsa1
3.4.3. Related Books The following books discuss various issues related to resource monitoring, and are good resources for Red Hat Enterprise Linux system administrators: The System Administrators Guide ; Red Hat, Inc -- Includes a chapter on many of the resource monitoring tools described here. Linux Performance Tuning and Capacity Planning by Jason R. Fink and Matthew D. Sherer; Sams -- Provides more in-depth overviews of the resource monitoring tools presented here, and includes others that might be appropriate for more specific resource monitoring needs. Linux Administration Handbook by Evi Nemeth, Garth Snyder, and Trent R. Hein; Prentice Hall -- Provides a short chapter similar in scope to this book, but includes an interesting section on diagnosing a system that has suddenly slowed down. Linux System Administration: A User's Guide by Marcel Gagne; Addison Wesley Professional -- Contains a small chapter on performance monitoring and tuning.

Commands:
probe::ipmib.ForwDatagrams Name probe::ipmib.ForwDatagrams - Count forwarded packet Synopsis ipmib.ForwDatagrams Values op value to be added to the counter (default value of 1) skb pointer to the struct sk_buff being acted on Description The packet pointed to by skb is filtered by the function ipmib_filter_key . If the packet passes the filter is is counted in the global ForwDatagrams (equivalent to SNMP's MIB IPSTATS_MIB_OUTFORWDATAGRAMS)

Commands:
Chapter 3. Creating system images with Image Builder command-line interface Image Builder is a tool for creating custom system images. To control Image Builder and create your custom system images, use the command-line interface which is currently the preferred method to use Image Builder. 3.1. Image Builder command-line interface Image Builder command-line interface is currently the preferred method to use Image Builder. It offers more functionality than the Chapter 4, Creating system images with Image Builder web console interface . To use this interface, run the composer-cli tool with suitable options and sub-commands. The workflow for the command-line interface can be summarized as follows: 1. Export (save) the blueprint definition to a plain text file 2. Edit this file in a text editor 3. Import (push) the blueprint text file back into Image Builder 4. Run a compose to build an image from the blueprint 5. Export the image file to download it Apart from the basic sub-commands to achieve this procedure, the composer-cli tool offers many sub-commands to examine the state of configured blueprints and composes. To run the composer-cli command as a non-root, the user must be in the weldr or root groups .

Commands:
Chapter 7. Adding developers These are the steps to add a new developer account for access to your application programming interface (API). If you have configured the workflow to invite developers manually, this covers how to add new developers. 7.1. Create a new developer account Follow Accounts link from the Audience section on the Admin Portal. Click Create . As an admin, you can skip even some of the required fields. If you want to invite users to the account securely, you can also skip the password fields. However the email on this main admin account must be unique among all users. 7.2. Set up applications Note There are field restrictions of maximum length and reserved characters for the user_key , app_key , and client_secret fields: Only alphanumeric characters [0-9, a-z, A-Z] , hyphen-minus (-) , between 5 and 256 characters long. No spaces allowed. Further, app_id and client_id have a maximum length of 140 characters. If you want to pre-configure app keys for the account, you can also add an application on behalf of the developer. Otherwise, leave this as one of the initial steps for the developer to take. 7.3. Notify the developer You can either send an email invitation to the developer manually or follow the steps to use the invite developer feature.

Commands:
Chapter 3. Selecting an installed Red Hat build of OpenJDK version for a specific application Some applications require a specific Red Hat build of OpenJDK version to run. If multiple versions of Red Hat build of OpenJDK are installed on the system using the yum package manager or portable bundle, you can select a Red Hat build of OpenJDK version for each application where necessary by setting the value of the JAVA_HOME environment variable or using a wrapper script. Prerequisites Multiple versions of Red Hat build of OpenJDK installed on the machine. Ensure that the application you want to run is installed. Procedure Set the JAVA_HOME environment variable. For example, if Red Hat build of OpenJDK 11 was installed using yum : USD JAVA_HOME=/usr/lib/jvm/java-11-openjdk Note The symbolic link java-11-openjdk is controlled by the alternatives command. Do one of the following: Launch the application using the default, system-wide configuration. Launch the application specifying the JAVA_HOME variable:

Commands:
mvn --version Apache Maven 3.5.4 (Red Hat 3.5.4-5) Maven home: /usr/share/maven Java version: 11.0.9, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-11-openjdk-11.0.9.10-0.el8_0.x86_644/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.18.0-144.el8.x86_64", arch: "amd64", family: "unix"
JAVA_HOME=/usr/lib/jvm/java-11-openjdk mvn --version Apache Maven 3.5.4 (Red Hat 3.5.4-5) Maven home: /usr/share/maven Java version: 11.0.9, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-11-openjdk-11.0.9.10-0.el8_0.x86_64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.18.0-144.el8.x86_64", arch: "amd64", family: "unix"
8.2.4. Creating the LVM Logical Volumes Create logical volumes with mount points such as / , /home/ , and swap space. Remember that /boot cannot be a logical volume. To add a logical volume, click the Add button in the Logical Volumes section. A dialog window as shown in Figure 8.8, "Creating a Logical Volume" appears. Figure 8.8. Creating a Logical Volume Repeat these steps for each volume group you want to create. Note You may want to leave some free space in the logical volume group so you can expand the logical volumes later. The default automatic configuration does not do this, but this manual configuration example does - approximately 1 GB is left as free space for future expansion. Figure 8.9. Pending Logical Volumes Click OK to apply the volume group and all associated logical volumes. The following figure shows the final manual configuration: Figure 8.10. Final Manual Configuration

Commands:
F.3. Edit Menu The Edit menu provides actions to manage the content, structure and properties of your model and project resources. The figure below represents the Edit menu presented when a metadata model is selected. Figure F.4. Edit Menu The Edit menu contains the following actions: New > Child - This menu is created dynamically to support the creation of whatever types of child objects can be created under the selected object. New > Sibling - This menu is created dynamically to support the creation of whatever types of sibling objects can be created under the same parent as the selected object New > Association - This menu is created dynamically to support the creation of whatever types of associations can be created with the selected object. Modeling > - This menu is created dynamically. Various modeling operations are presented based on selected model object type. Undo - Reverses the effect of the most recent command. Redo - Reapplies the most recently undone command. Cut - Deletes the selected object(s) and copies it to the clipboard. Copy - Copies the selected object(s) to the clipboard. Paste - Pastes the contents of the clipboard to the selected context. Paste Special... - Provides additional paste capabilities for complex clipboard objects. Clone - Duplicates the selected object in the same location with the same name. User is able to rename the new object right in the tree. Delete - Deletes the selected object(s). Select All - Select All objects in current view. Rename - Allows a user to rename an object in the tree. Find/Replace - Launches dialog that can be used to search in the current text view, such as a Transformation Editor. Open - Opens the selected object in the appropriate editor. Edit - Opens the selected object in the appropriate specialized editor, such as the Choice Editor or Recursion Editor.. Add Bookmark... - This command adds a bookmark in the active file on the line where the cursor is currently displayed. Add Task... - This command adds a task in the active file on the line where the cursor is currently displayed.

Commands:
Chapter 137. KafkaMirrorMaker2ClusterSpec schema reference Used in: KafkaMirrorMaker2Spec Full list of KafkaMirrorMaker2ClusterSpec schema properties Configures Kafka clusters for mirroring. 137.1. config Use the config properties to configure Kafka options. Standard Apache Kafka configuration may be provided, restricted to those properties not managed directly by AMQ Streams. For client connection using a specific cipher suite for a TLS version, you can configure allowed ssl properties . You can also configure the ssl.endpoint.identification.algorithm property to enable or disable hostname verification. 137.2. KafkaMirrorMaker2ClusterSpec schema properties Property Description alias Alias used to reference the Kafka cluster. string bootstrapServers A comma-separated list of host:port pairs for establishing the connection to the Kafka cluster. string tls TLS configuration for connecting MirrorMaker 2 connectors to a cluster. ClientTls authentication Authentication configuration for connecting to the cluster. The type depends on the value of the authentication.type property within the given object, which must be one of [tls, scram-sha-256, scram-sha-512, plain, oauth]. KafkaClientAuthenticationTls , KafkaClientAuthenticationScramSha256 , KafkaClientAuthenticationScramSha512 , KafkaClientAuthenticationPlain , KafkaClientAuthenticationOAuth config The MirrorMaker 2 cluster config. Properties with the following prefixes cannot be set: ssl., sasl., security., listeners, plugin.path, rest., bootstrap.servers, consumer.interceptor.classes, producer.interceptor.classes (with the exception of: ssl.endpoint.identification.algorithm, ssl.cipher.suites, ssl.protocol, ssl.enabled.protocols). map

Commands: