mtpti5iD/redhat-docs_dataset huggingface dataset:
F.11. Help Menu The Help Menu shown below contains no Teiid Designer specific actions. See Eclipse Workbench documentation for details. Figure F.14. Help Menu The individual actions are described below: Red Hat Central - Launches the Red Hat Central view. Help Contents - Launches the Help Window. All of Designer's online documentation is accessible from there as well. Search - Launches the Help Search view, which can be used to search for phrases in the documentation. Show Contextual Help - Launches the Help Search view. Show Active Keybindings... - Launches a dialog describing existing key assist bindings. Tips and Tricks... - Launches a dialog to select one of any contributed Tips and Tricks help pages. Cheat Sheets... - Launches a dialog to select one of any contributed Eclipse cheat sheets. Project Examples... - A JBoss contributed action which provides quick access to import various project examples into your workspace. Check for Updates... - provides access to retrieve updates to installed Eclipse software. Install New Software... - provides access to install new software into your workbench. About JBoss Developer Studio - Launches the About dialog.

Commands:
Appendix C. Reverting Satellite Server to download content from Red Hat CDN If your environment changes from disconnected to connected, you can reconfigure a disconnected Satellite Server to download content directly from the Red Hat CDN. Procedure In the Satellite web UI, navigate to Content > Subscriptions . Click Manage Manifest . Switch to the CDN Configuration tab. Select Red Hat CDN . Edit the URL field to point to the Red Hat CDN URL: https://cdn.redhat.com Click Update . Satellite Server is now configured to download content from the Red Hat CDN the time that it synchronizes repositories. CLI procedure Log in to the Satellite Server using SSH. Use Hammer to reconfigure the CDN:

Commands:
hammer organization configure-cdn --name=" My_Organization " --type=redhat_cdn
4.284. sblim-sfcb 4.284.1. RHBA-2011:1547 - sblim-sfcb bug fix update An updated sblim-sfcb package that fixes multiple bugs is now available for Red Hat Enterprise Linux 6. Small Footprint CIM Broker (sblim-sfcb) is a Common Information Model (CIM) server conforming to the CIM Operations over the HTTP protocol. The SFCB CIM server is robust and resource-efficient, and is therefore particularly-suited for embedded and resource-constrained environments. The sblim-sfcb package supports providers written against the Common Manageability Programming Interface (CMPI). The sblim-sfcb package has been upgraded to upstream version 1.3.11, which provides a number of bug fixes over the version. (BZ# 633580 ) Bug Fixes BZ# 618080 When using the sfcbrepos command without the "-c" option to specify the location of the CIM schema, an error message occurred. The issue was caused by using the default CIM schema location (the /usr/lib/sfcb/CIM/ directory), which does not exist on Red Hat Enterprise Linux systems. This issue has been fixed and sfcbrepos now reflects the correct CIM schema location (the /usr/share/mof/cim-current/ directory). BZ# 618081 The sfcb system group, which is used by PAM for basic authentication, was not created automatically during package installation. This issue has been fixed and the group is now created correctly. BZ# 620303 The sblim-sfcb package was compiled without the Unix domain socket local connection functionality. This issue has been fixed and this feature is now enabled in the SFCB CIM server. BZ# 745261 Due to missing checks on pointer validity when freeing memory in certain parts of the code, the SBLIM Web-Based Enterprise Management (WBEM) Command Line Interface (sblim-wbemcli) terminated unexpectedly with a segmentation fault upon successful completion of a CIM request. With this update, the missing checks have been added, pointers are now tested for NULL before an attemp to free the memory and set to NULL explicitly after the memory is freed. Segmentation faults no longer occur and sblim-wbemcli no longer crashes in the scenario described. All users of sblim-sfcb are advised to upgrade to this updated package, which fixes these bugs.

Commands:
8.5. Snapshot Deletion You can delete individual snapshots that are no longer required. Deleting a snapshot removes the ability to restore a virtual disk to that particular restoration point. It does not necessarily reclaim the disk space consumed by the snapshot, nor does it delete the data. The disk space will only be reclaimed if a subsequent snapshot has overwritten the data of the deleted snapshot. For example, if the third snapshot out of five snapshots is deleted, the unchanged data in the third snapshot must be preserved on the disk for the fourth and fifth snapshots to be usable; however, if the fourth or fifth snapshot has overwritten the data of the third, then the third snapshot has been made redundant and the disk space can be reclaimed. Aside from potential disk space reclamation, deleting a snapshot may also improve the performance of the virtual machine. Figure 8.4. Snapshot Deletion Snapshot deletion is handled as an asynchronous block job in which VDSM maintains a record of the operation in the recovery file for the virtual machine so that the job can be tracked even if VDSM is restarted or the virtual machine is shut down during the operation. Once the operation begins, the snapshot being deleted cannot be previewed or used as a restoration point, even if the operation fails or is interrupted. In operations in which the active layer is to be merged with its parent, the operation is split into a two-stage process during which data is copied from the active layer to the parent layer, and disk writes are mirrored to both the active layer and the parent. Finally, the job is considered complete once the data in the snapshot being deleted has been merged with its parent snapshot and VDSM synchronizes the changes throughout the image chain. Note If the deletion fails, fix the underlying problem (for example, a failed host, an inaccessible storage device, or even a temporary network issue) and try again.

Commands:
Chapter 12. Nested Virtualization 12.1. Overview As of Red Hat Enterprise Linux 7.5, nested virtualization is available as a Technology Preview for KVM guest virtual machines. With this feature, a guest virtual machine (also referred to as level 1 or L1 ) that runs on a physical host ( level 0 or L0 ) can act as a hypervisor, and create its own guest virtual machines ( L2 ). Nested virtualization is useful in a variety of scenarios, such as debugging hypervisors in a constrained environment and testing larger virtual deployments on a limited amount of physical resources. However, note that nested virtualization is not supported or recommended in production user environments, and is primarily intended for development and testing. Nested virtualization relies on host virtualization extensions to function, and it should not be confused with running guests in a virtual environment using the QEMU Tiny Code Generator (TCG) emulation, which is not supported in Red Hat Enterprise Linux.

Commands:
3.4. Setting Up Multipathing in the initramfs File System You can set up multipathing in the initramfs file system. After configuring multipath, you can rebuild the initramfs file system with the multipath configuration files by executing the dracut command with the following options: If you run multipath from the initramfs file system and you make any changes to the multipath configuration files, you must rebuild the initramfs file system for the changes to take effect.

Commands:
dracut --force --add multipath
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-05-30 17:22:46 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
8.2. Understanding the Default Behavior of Controller and Port Interfaces When controlling teamed port interfaces using the NetworkManager daemon, and especially when fault finding, keep the following in mind: Starting the controller interface does not automatically start the port interfaces. Starting a port interface always starts the controller interface. Stopping the controller interface also stops the port interfaces. A controller without ports can start static IP connections. A controller without ports waits for ports when starting DHCP connections. A controller with a DHCP connection waiting for ports completes when a port with a carrier is added. A controller with a DHCP connection waiting for ports continues waiting when a port without a carrier is added. Warning The use of direct cable connections without network switches is not supported for teaming. The failover mechanisms described here will not work as expected without the presence of network switches. See the Red Hat Knowledgebase article Why is bonding not supported with direct connection using crossover cables? for more information.

Commands:
5.3.4. Deleting a Member from a Cluster To delete a member from an existing cluster that is currently in operation, follow the steps in this section. Note that nodes must be stopped before being deleted unless you are deleting all of the nodes in the cluster at once. From the cluster-specific page, click Nodes along the top of the cluster display. This displays the nodes that constitute the cluster. This is also the default page that appears when you click on the cluster name beneath Manage Clusters from the menu on the left side of the luci Homebase page. Note To allow services running on a node to fail over when the node is deleted, skip the step. Disable or relocate each service that is running on the node to be deleted. For information on disabling and relocating services, see Section 5.5, "Managing High-Availability Services" . Select the node or nodes to delete. Click Delete . The Nodes page indicates that the node is being removed. Refresh the page to see the current status. Important Removing a cluster node from the cluster is a destructive operation that cannot be undone.

Commands:
3.12. Creating a Virtual Disk To ensure that a newly created virtual machine has access to persistent storage you must create and attach a disk. This Ruby example creates and attaches a virtual storage disk to a virtual machine. # Locate the virtual machines service and use it to find the virtual # machine: vms_service = connection.system_service.vms_service vm = vms_service.list(search: 'name=myvm')[0] # Locate the service that manages the disk attachments of the virtual # machine: disk_attachments_service = vms_service.vm_service(vm.id).disk_attachments_service # Use the "add" method of the disk attachments service to add the disk. # Note that the size of the disk, the `provisioned_size` attribute, is # specified in bytes, so to create a disk of 10 GiB the value should # be 10 * 2^30. disk_attachment = disk_attachments_service.add( OvirtSDK4::DiskAttachment.new( disk: { name: 'mydisk', description: 'My disk', format: OvirtSDK4::DiskFormat::COW, provisioned_size: 10 * 2**30, storage_domains: [{ name: 'mydata' }] }, interface: OvirtSDK4::DiskInterface::VIRTIO, bootable: false, active: true ) ) # Wait until the disk status is OK: disks_service = connection.system_service.disks_service disk_service = disks_service.disk_service(disk_attachment.disk.id) loop do sleep(5) disk = disk_service.get break if disk.status == OvirtSDK4::DiskStatus::OK end For more information, see http://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4/DiskAttachmentsService:add .

Commands:
Locate the virtual machines service and use it to find the virtual machine: vms_service = connection.system_service.vms_service vm = vms_service.list(search: 'name=myvm')[0] Locate the service that manages the disk attachments of the virtual machine: disk_attachments_service = vms_service.vm_service(vm.id).disk_attachments_service Use the "add" method of the disk attachments service to add the disk. Note that the size of the disk, the `provisioned_size` attribute, is specified in bytes, so to create a disk of 10 GiB the value should be 10 * 2^30. disk_attachment = disk_attachments_service.add( OvirtSDK4::DiskAttachment.new( disk: { name: 'mydisk', description: 'My disk', format: OvirtSDK4::DiskFormat::COW, provisioned_size: 10 * 2**30, storage_domains: [{ name: 'mydata' }] }, interface: OvirtSDK4::DiskInterface::VIRTIO, bootable: false, active: true ) ) Wait until the disk status is OK: disks_service = connection.system_service.disks_service disk_service = disks_service.disk_service(disk_attachment.disk.id) loop do sleep(5) disk = disk_service.get break if disk.status == OvirtSDK4::DiskStatus::OK end
Chapter 5. Using the API For more information, see the AMQ C++ API reference and AMQ C++ example suite . 5.1. Handling messaging events AMQ C++ is an asynchronous event-driven API. To define how the application handles events, the user implements callback methods on the messaging_handler class. These methods are then called as network activity or timers trigger new events. Example: Handling messaging events struct example_handler : public proton::messaging_handler { void on_container_start(proton::container& cont) override { std::cout << "The container has started\n"; } void on_sendable(proton::sender& snd) override { std::cout << "A message can be sent\n"; } void on_message(proton::delivery& dlv, proton::message& msg) override { std::cout << "A message is received\n"; } }; These are only a few common-case events. The full set is documented in the API reference . 5.2. Creating a container The container is the top-level API object. It is the entry point for creating connections, and it is responsible for running the main event loop. It is often constructed with a global event handler. Example: Creating a container int main() { example_handler handler {}; proton::container cont {handler}; cont.run(); } 5.3. Setting the container identity Each container instance has a unique identity called the container ID. When AMQ C++ makes a connection, it sends the container ID to the remote peer. To set the container ID, pass it to the proton::container constructor. Example: Setting the container identity proton::container cont {handler, "job-processor-3" }; If the user does not set the ID, the library will generate a UUID when the container is constucted.

Commands:
struct example_handler : public proton::messaging_handler { void on_container_start(proton::container& cont) override { std::cout << "The container has started\n"; } void on_sendable(proton::sender& snd) override { std::cout << "A message can be sent\n"; } void on_message(proton::delivery& dlv, proton::message& msg) override { std::cout << "A message is received\n"; } };
int main() { example_handler handler {}; proton::container cont {handler}; cont.run(); }
proton::container cont {handler, "job-processor-3" };
7.45. efibootmgr 7.45.1. RHBA-2015:1431 - efibootmgr bug fix update Updated efibootmgr packages that fix one bug are now available for Red Hat Enterprise Linux 6. The efibootmgr utility is responsible for the boot loader installation on Unified Extensible Firmware Interface (UEFI) systems. Bug Fix BZ# 1151681 Previously, when the installation of the Generation 2 Virtual Machine (Gen2 VM) on the Hyper-V 2012 and R2 host was completed, the VM disappeared from the Virtual Machines list. As a consequence, the Hyper-V Manager could no longer load the VM settings, which rendered the VM unusable. With this update, the bug in the efibootmgr packages has been fixed so that the VM settings are accessible in the described scenario. Users of efibootmgr are advised to upgrade to these updated packages, which fix this bug.

Commands:
4.36. crontabs 4.36.1. RHBA-2011:0872 - crontabs bug fix update An updated crontabs package that fixes one bug is now available for Red Hat Enterprise Linux 6. The crontabs package contains root crontab files and directories. You will need to install the cron daemon to run the jobs from crontabs. The cron daemon such as cronie or fcron checks the crontab files to see when particular commands are scheduled to be executed. If commands are scheduled, it executes them. Crontabs handles a basic system function, so it should be installed on your system. Bug Fix BZ# 609544 Prior to this update, an example included in the /etc/crontab file contained an omission. It did not state that defining a job in crontab requires a username to be defined. The missing information has been added to the /etc/crontab file in this update. All users of crontabs are advised to upgrade to this updated package, which fixes this bug.

Commands:
35.2. Viewing Log Files Most log files are in plain text format. You can view them with any text editor such as Vi or Emacs . Some log files are readable by all users on the system; however, root privileges are required to read most log files. To view system log files in an interactive, real-time application, use the Log Viewer . To start the application, go to Applications (the main menu on the panel) => System Tools => System Logs , or type the command system-logviewer at a shell prompt. The application only displays log files that exist; thus, the list might differ from the one shown in Figure 35.1, " Log Viewer " . To filter the contents of the log file for keywords, type the keyword(s) in the Filter for text field, and click Filter . Click Reset to reset the contents. Figure 35.1. Log Viewer By default, the currently viewable log file is refreshed every 30 seconds. To change the refresh rate, select Edit => Preferences from the pulldown menu. The window shown in Figure 35.2, "Log File Locations" appears. In the Log Files tab, click the up and down arrows beside the refresh rate to change it. Click Close to return to the main window. The refresh rate is changed immediately. To refresh the currently viewable file manually, select File => Refresh Now or press Ctrl + R . On the Log Files tab in the Preferences, the log file locations can be modified. Select the log file from the list, and click the Edit button. Type the new location of the log file or click the Browse button to locate the file location using a file selection dialog. Click OK to return to the preferences, and click Close to return to the main window. Figure 35.2. Log File Locations

Commands:
Chapter 1. About specialized hardware and driver enablement Many applications require specialized hardware or software that depends on kernel modules or drivers. You can use driver containers to load out-of-tree kernel modules on Red Hat Enterprise Linux CoreOS (RHCOS) nodes. To deploy out-of-tree drivers during cluster installation, use the kmods-via-containers framework. To load drivers or kernel modules on an existing OpenShift Container Platform cluster, OpenShift Container Platform offers several tools: The Driver Toolkit is a container image that is a part of every OpenShift Container Platform release. It contains the kernel packages and other common dependencies that are needed to build a driver or kernel module. The Driver Toolkit can be used as a base image for driver container image builds on OpenShift Container Platform. The Special Resource Operator (SRO) orchestrates the building and management of driver containers to load kernel modules and drivers on an existing OpenShift or Kubernetes cluster. The Node Feature Discovery (NFD) Operator adds node labels for CPU capabilities, kernel version, PCIe device vendor IDs, and more.

Commands:
Chapter 11. Supported and Unsupported features for IBM Power and IBM Z Table 11.1. List of supported and unsupported features on IBM Power and IBM Z Features IBM Power IBM Z Compact deployment Unsupported Unsupported Dynamic storage devices Unsupported Supported Stretched Cluster - Arbiter Supported Unsupported Federal Information Processing Standard Publication (FIPS) Unsupported Unsupported Ability to view pool compression metrics Supported Unsupported Automated scaling of Multicloud Object Gateway (MCG) endpoint pods Supported Unsupported Alerts to control overprovision Supported Unsupported Alerts when Ceph Monitor runs out of space Supported Unsupported Extended OpenShift Data Foundation control plane which allows pluggable external storage such as IBM Flashsystem Unsupported Unsupported IPV6 support Unsupported Unsupported Multus Unsupported Unsupported Multicloud Object Gateway (MCG) bucket replication Supported Unsupported Quota support for object data Supported Unsupported Minimum deployment Unsupported Unsupported Regional-Disaster Recovery (Regional-DR) with Red Hat Advanced Cluster Management (RHACM) Supported Unsupported Metro-Disaster Recovery (Metro-DR) multiple clusters with RHACM Supported Supported Single Node solution for Radio Access Network (RAN) Unsupported Unsupported Support for network file system (NFS) services Supported Unsupported Ability to change Multicloud Object Gateway (MCG) account credentials Supported Unsupported Multicluster monitoring in Red Hat Advanced Cluster Management console Supported Unsupported Deletion of expired objects in Multicloud Object Gateway lifecycle Supported Unsupported Agnostic deployment of OpenShift Data Foundation on any Openshift supported platform Unsupported Unsupported Installer provisioned deployment of OpenShift Data Foundation using bare metal infrastructure Unsupported Unsupported Openshift dual stack with OpenShift Data Foundation using IPv4 Unsupported Unsupported Ability to disable Multicloud Object Gateway external service during deployment Unsupported Unsupported Ability to allow overriding of default NooBaa backing store Supported Unsupported Allowing ocs-operator to deploy two MGR pods, one active and one standby Supported Unsupported Disaster Recovery for brownfield deployments Unsupported Supported Automatic scaling of RGW Unsupported Unsupported

Commands: