mtpti5iD/redhat-docs_dataset huggingface dataset:
3.16. Example: Check System Events The start action for the vm1 creates several entries in the events collection. This example lists the events collection and identifies events specific to the API starting a virtual machine. Example 3.19. List the events collection Request: cURL command: Result: The following events occur: id="101" - The API authenticates with the admin user's user name and password. id="102" - The API, acting as the admin user, starts vm1 on the hypervisor host. id="103" - The API logs out of the admin user account.

Commands:
GET /ovirt-engine/api/events HTTP/1.1 Accept: application/xml
curl -X GET -H "Accept: application/xml" -u [USER:PASS] --cacert [CERT] https:// [RHEVM Host] :443/ovirt-engine/api/events
<events> <event id="103" href="/ovirt-engine/api/events/103"> <description>User admin logged out.</description> <code>31</code> <severity>normal</severity> <time>2011-06-29T17:42:41.544+10:00</time> <user id="80b71bae-98a1-11e0-8f20-525400866c73" href="/ovirt-engine/api/users/80b71bae-98a1-11e0-8f20-525400866c73"/> </event> <event id="102" href="/ovirt-engine/api/events/102"> <description>vm1 was started by admin (Host: hypervisor).</description> <code>153</code> <severity>normal</severity> <time>2011-06-29T17:42:41.499+10:00</time> <user id="80b71bae-98a1-11e0-8f20-525400866c73" href="/ovirt-engine/api/users/80b71bae-98a1-11e0-8f20-525400866c73"/> <vm id="6efc0cfa-8495-4a96-93e5-ee490328cf48" href="/ovirt-engine/api/vms/6efc0cfa-8495-4a96-93e5-ee490328cf48"/> <host id="0656f432-923a-11e0-ad20-5254004ac988" href="/ovirt-engine/api/hosts/0656f432-923a-11e0-ad20-5254004ac988"/> </event> <event id="101" href="/ovirt-engine/api/events/101"> <description>User admin logged in.</description> <code>30</code> <severity>normal</severity> <time>2011-06-29T17:42:40.505+10:00</time> <user id="80b71bae-98a1-11e0-8f20-525400866c73" href="/ovirt-engine/api/users/80b71bae-98a1-11e0-8f20-525400866c73"/> </event> </events>
Chapter 6. Using the dynamic plugins cache The dynamic plugins cache in Red Hat Developer Hub (RHDH) enhances the installation process and reduces platform boot time by storing previously installed plugins. If the configuration remains unchanged, this feature prevents the need to re-download plugins on subsequent boots. When you enable dynamic plugins cache: The system calculates a checksum of each plugin's YAML configuration (excluding pluginConfig ). The checksum is stored in a file named dynamic-plugin-config.hash within the plugin's directory. During boot, if a plugin's package reference matches the installation and the checksum is unchanged, the download is skipped. Plugins that are disabled since the boot are automatically removed. 6.1. Enabling the dynamic plugins cache To enable the dynamic plugins cache in RHDH, the plugins directory dynamic-plugins-root must be a persistent volume. For Helm chart installations, a persistent volume named dynamic-plugins-root is automatically created. For operator-based installations, you must manually create the PersistentVolumeClaim (PVC) as follows: kind: PersistentVolumeClaim apiVersion: v1 metadata: name: dynamic-plugins-root spec: accessModes: - ReadWriteOnce resources: requests: storage: 5Gi --- apiVersion: rhdh.redhat.com/v1alpha3 kind: Backstage metadata: name: developer-hub spec: deployment: patch: spec: template: spec: volumes: - USDpatch: replace name: dynamic-plugins-root persistentVolumeClaim: claimName: dynamic-plugins-root Note Future versions of the RHDH operator are planned to automatically create the PVC. 6.2. Configuring the dynamic plugins cache You can set the following optional dynamic plugin cache parameters: forceDownload : Set to true to force a reinstall of the plugin, bypassing the cache. Default is false . For example, modify your dynamic-plugins.yaml file as follows: plugins: - disabled: false forceDownload: true package: 'oci://quay.io/example-org/example-plugin:v1.0.0!internal-backstage-plugin-example'

Commands:
kind: PersistentVolumeClaim apiVersion: v1 metadata: name: dynamic-plugins-root spec: accessModes: - ReadWriteOnce resources: requests: storage: 5Gi --- apiVersion: rhdh.redhat.com/v1alpha3 kind: Backstage metadata: name: developer-hub spec: deployment: patch: spec: template: spec: volumes: - USDpatch: replace name: dynamic-plugins-root persistentVolumeClaim: claimName: dynamic-plugins-root
plugins: - disabled: false forceDownload: true package: 'oci://quay.io/example-org/example-plugin:v1.0.0!internal-backstage-plugin-example'
E.3. Installing GRUB In a vast majority of cases, GRUB is installed and configured by default during the installation of Red Hat Enterprise Linux. However, if for some reason GRUB is not installed, or if you need to install it again, it is possible to install grub manually. On systems without UEFI firmware, a valid GRUB configuration file must be present at /boot/grub/grub.conf . You can use the grub-install script (part of the grub package) to install GRUB. For example: Replace disk with the device name of your system's boot drive such as /dev/sda . On systems with UEFI firmware, a valid GRUB configuration file must be present at /boot/efi/EFI/redhat/grub.conf . An image of GRUB's first-stage boot loader is available on the EFI System Partitition in the directory EFI/redhat/ with the filename grubx64.efi , and you can use the efibootmgr command to install this image into your system's EFI System Partition. For example: Replace disk with the name of the device containing the EFI System Partition (such as /dev/sda ) and partition_number with the partition number of your EFI System Partition (the default value is 1, meaning the first partition on the disk). Important The grub package does not automatically update the system boot loader when the package is updated using Yum or RPM . Therefore, updating the package will not automatically update the actual boot loader on your system. Use the grub-install command manually every time after the package is updated. For additional information about installing GRUB , see the GNU GRUB Manual and the grub-install(8) man page. For information about the EFI System Partition, see Section 9.18.1, "Advanced Boot Loader Configuration" . For information about the efibootmgr tool, see the efibootmgr(8) man page.

Commands:
grub-install disk
efibootmgr -c -d disk -p partition_number -l /EFI/redhat/grubx64.efi -L "grub_uefi"
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 2025-03-05 17:05:35 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Chapter 6. Creating Ansible playbooks with the all-in-one Red Hat OpenStack Platform environment The deployment command applies Ansible playbooks to the environment automatically. However, you can modify the deployment command to generate Ansible playbooks without applying them to the deployment, and run the playbooks later. Include the --output-only option in the deploy command to generate the standalone-ansible-XXXXX directory. This directory contains a set of Ansible playbooks that you can run on other hosts. To generate the Ansible playbook directory, run the deploy command with the option --output-only : To run the Ansible playbooks, run the ansible-playbook command, and include the inventory.yaml file and the deploy_steps_playbook.yaml file:

Commands:
[stack@all-in-one]USD sudo openstack tripleo deploy --templates --local-ip=USDIP/USDNETMASK -e /usr/share/openstack-tripleo-heat-templates/environments/standalone/standalone-tripleo.yaml -r /usr/share/openstack-tripleo-heat-templates/roles/Standalone.yaml -e USDHOME/containers-prepare-parameters.yaml -e USDHOME/standalone_parameters.yaml --output-dir USDHOME --standalone --output-only
[stack@all-in-one]USD cd standalone-ansible-XXXXX [stack@all-in-one]USD sudo ansible-playbook -i inventory.yaml deploy_steps_playbook.yaml
3.17. Searching for Templates The following table describes all search options for templates. Table 3.13. Searching for Templates Property (of resource or resource-type) Type Description (Reference) Vms. Vms-prop String The property of the virtual machines associated with the template. Hosts. hosts-prop String The property of the hosts associated with the template. Events. events-prop String The property of the events associated with the template. Users. users-prop String The property of the users associated with the template. name String The name of the template. domain String The domain of the template. os String The type of operating system. creationdate Integer The date on which the template was created. Date format is mm/dd/yy . childcount Integer The number of virtual machines created from the template. mem Integer Defined memory. description String The description of the template. status String The status of the template. cluster String The cluster associated with the template. datacenter String The data center associated with the template. quota String The quota associated with the template. sortby List Sorts the returned results by one of the resource properties. page Integer The page number of results to display. Example Template: Events.severity >= normal and Vms.uptime > 0 This example returns a list of templates where events of normal or greater severity have occurred on virtual machines derived from the template, and the virtual machines are still running.

Commands:
Chapter 3. Removing disabled applications from the dashboard After your administrator has disabled your unused applications, you can manually remove them from the Red Hat OpenShift AI dashboard. Disabling and removing unused applications allows you to focus on the applications that you are most likely to use. Prerequisites You are logged in to Red Hat OpenShift AI. Your administrator has disabled the application that you want to remove, as described in Disabling applications connected to OpenShift AI . Procedure In the OpenShift AI interface, click Enabled . On the Enabled page, tiles for disabled applications are denoted with a Disabled label. Click Disabled on the tile for the application that you want to remove. Click the link to remove the application tile. Verification The tile for the disabled application no longer appears on the Enabled page.

Commands:
probe::nfsd.proc.write Name probe::nfsd.proc.write - NFS server writing data to file for client Synopsis nfsd.proc.write Values offset the offset of file gid requester's group id vlen read blocks fh file handle (the first part is the length of the file handle) size read bytes vec struct kvec, includes buf address in kernel address and length of each buffer stable argp->stable version nfs version uid requester's user id count read bytes client_ip the ip address of client proto transfer protocol

Commands:
5.171. lm_sensors 5.171.1. RHBA-2012:1309 - lm_sensors bug fixes Updated lm_sensors packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The lm_sensors packages provide a set of modules for general SMBus access and hardware monitoring. Bug Fixes BZ# 610000 , BZ# 623587 Prior to this update, the sensors-detect script did not detect all GenuineIntel CPUs. As a consequence, lm_sensors did not load coretemp module automatically. This update uses a more generic detection for Intel CPUs. Now, the coretemp module is loaded as expected. BZ# 768365 Prior to this update, the sensors-detect script reported an error when running without user-defined input. This behavior had no impact on the function but could confuse users. This update modifies the underlying code to allow for the sensors-detect script to run without user. All users of lm_sensors are advised to upgrade to these updated packages, which fix these bugs.

Commands:
probe::signal.wakeup Name probe::signal.wakeup - Sleeping process being wakened for signal Synopsis signal.wakeup Values pid_name Name of the process to wake resume Indicates whether to wake up a task in a STOPPED or TRACED state state_mask A string representation indicating the mask of task states to wake. Possible values are TASK_INTERRUPTIBLE, TASK_STOPPED, TASK_TRACED, TASK_WAKEKILL, and TASK_INTERRUPTIBLE. sig_pid The PID of the process to wake

Commands:
Chapter 1. Eclipse Temurin 11 - End of full support Important The 11.0.25 release is the last release of Eclipse Temurin 11 that Red Hat plans to fully support. The full support for Eclipse Temurin 11 ends on 31 October 2024. See the Eclipse Temurin Life Cycle and Support Policy for details. Red Hat will provide extended life cycle support (ELS) phase 1 support for Eclipse Temurin 11 until 31 October 2027. For more information about product life cycle phases and available support levels, see Life Cycle Phases .

Commands:
7.69. gnome-packagekit 7.69.1. RHBA-2013:0280 - gnome-packagekit bug fix update An updated gnome-packagekit package that fixes four bugs is now available. gnome-packagekit provides session applications for the PackageKit API. Bug Fixes BZ# 744980 If a package adds or removes a .repo file while updates are being installed, PackageKit (packagekitd) sends a RepoListChanged() message. If Software Update (/usr/bin/gpk-update-viewer) was being used to install these updates it responded to the message by attempting to refresh the available updates list. This resulted in said list going blank. As of this update, gpk-update-viewer ignores such signals from packagekitd, leaving the available updates list visible and unchanged. BZ# 744906 When a 64-bit Red Hat Enterprise Linux instance had both 32-bit and 64-bit versions of a package installed, and an update for both packages was available and presented in the Software Update (/usr/bin/gpk-update-viewer) window, the summary and package name appeared for both architectures. Package size and the errata note only presented for the 32-bit version, however. For the 64-bit version, the size column remained blank. And, when the 64-bit version was selected in Software list, the display pane below presented a 'Loading...' message rather than the errata note. With this update, gpk-update-viewer seeks out the exact package ID before falling back to the package name, ensuring both package versions are found and associated meta-data displayed when more than one package architecture is installed. BZ# 694793 When an application is installed using the Add/Remove Software interface (/usr/bin/gpk-application), a dialogue box appears immediately post-install offering a Run button. Clicking this button launches the newly-installed program. Previously, under some circumstances, an improperly assigned pointer value meant clicking this Run button caused gpk-application to crash (segfault). With this update, the pointer is correctly assigned and gpk-application no longer crashes when launching a newly-installed application. BZ#669798 Previously, it was possible for an ordinary user to shutdown their system or log-out from a session while the PackageKit update tool was running. Depending on the transaction PackageKit was engaged in when the shutdown or logout was initiated, this could damage the RPM database and, consequently, damage the system. With this update, when ordinary users attempting to shutdown or log out while PackageKit is running an update, PackageKit inhibits the process and presents the user with an alert: Note: this update does not prevent a root user (or other user with equivalent administrative privileges) from shutting the system down or logging an ordinary user out of their session. All PackageKit users should install this update which resolves these issues.

Commands:
A transaction that cannot be interrupted is running.
Chapter 6. Post-deployment configuration After the overcloud deployment finishes, complete the following steps to validate the functionality. Procedure Create a test instance in the availability zones. In this example, the new instance runs on the distributed compute node (DCN). The specific AZ is targeted using the --availability-zone parameter: Create a volume on the first availability zone. This volume uses the cinder active/active service running on the dcn0 nodes. Note This step depends on the cinder availability zone configuration, which is defined by CinderStorageAvailabilityZone . For more information, see Deploying availability zones in the Storage Guide . You now have two separate HCI stacks, with a Ceph cluster deployed by each one. For more information on HCI, see Hyperconverged Infrastructure Guide . 6.1. Checking container health Verify that the container is functioning correctly. Procedure Log in to the node that is running the Ceph MON service by using SSH. Run the following command to view container health: Replace CLUSTERNAME with the name of the cluster, for example, dcn0 . The default value is ceph . Confirm that the health status of the cluster is HEALTH_OK and that all of the OSDs are up .

Commands:
openstack server create --flavor m1.tiny --image cirros --network private --security-group basic dcn-instance --availability-zone dcn0
openstack volume create --size 1 --availability-zone dcn0 myvol
podman exec ceph-mon-USDHOSTNAME ceph -s --cluster CLUSTERNAME
11.8. Procedures and Functions A user can define one of the following functions: Source Procedure ("CREATE FOREIGN PROCEDURE") - a stored procedure in source Source Function ("CREATE FOREIGN FUNCTION") - A function that is supported by the source, where JBoss Data Virtualization will pushdown to source instead of evaluating in the JBoss Data Virtualization engine. Virtual Procedure ("CREATE VIRTUAL PROCEDURE") - Similar to stored procedure, however this is defined using the JBoss Data Virtualization Procedure language and evaluated in the JBoss Data Virtualization engine. Function/UDF ("CREATE VIRTUAL FUNCTION") - A user defined function, that can be defined using the Teiid procedure language or can have the implementation defined using a JAVA Class. Here is an example procedure: Here is an example function:

Commands:
CREATE VIRTUAL PROCEDURE CustomerActivity(customerid integer) RETURNS (name varchar(25), activitydate date, amount decimal) AS BEGIN END
CREATE VIRTUAL FUNCTION CustomerRank(customerid integer) RETURNS integer AS BEGIN END
probe::netfilter.bridge.local_in Name probe::netfilter.bridge.local_in - Called on a bridging packet destined for the local computer Synopsis netfilter.bridge.local_in Values llcproto_stp Constant used to signify Bridge Spanning Tree Protocol packet pf Protocol family -- always " bridge " nf_drop Constant used to signify a 'drop' verdict br_msg Message age in 1/256 secs indev Address of net_device representing input device, 0 if unknown nf_queue Constant used to signify a 'queue' verdict br_fd Forward delay in 1/256 secs br_mac Bridge MAC address brhdr Address of bridge header br_rid Identity of root bridge nf_accept Constant used to signify an 'accept' verdict outdev_name Name of network device packet will be routed to (if known) br_flags BPDU flags br_prid Protocol identifier br_htime Hello time in 1/256 secs protocol Packet protocol br_bid Identity of bridge br_rmac Root bridge MAC address br_max Max age in 1/256 secs br_type BPDU type nf_stop Constant used to signify a 'stop' verdict br_cost Total cost from transmitting bridge to root nf_stolen Constant used to signify a 'stolen' verdict length The length of the packet buffer contents, in bytes llcpdu Address of LLC Protocol Data Unit outdev Address of net_device representing output device, 0 if unknown nf_repeat Constant used to signify a 'repeat' verdict indev_name Name of network device packet was received on (if known) br_poid Port identifier br_vid Protocol version identifier

Commands:
Chapter 1. Console APIs 1.1. ConsoleCLIDownload [console.openshift.io/v1] Description ConsoleCLIDownload is an extension for configuring openshift web console command line interface (CLI) downloads. Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer). Type object 1.2. ConsoleExternalLogLink [console.openshift.io/v1] Description ConsoleExternalLogLink is an extension for customizing OpenShift web console log links. Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer). Type object 1.3. ConsoleLink [console.openshift.io/v1] Description ConsoleLink is an extension for customizing OpenShift web console links. Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer). Type object 1.4. ConsoleNotification [console.openshift.io/v1] Description ConsoleNotification is the extension for configuring openshift web console notifications. Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer). Type object 1.5. ConsolePlugin [console.openshift.io/v1] Description ConsolePlugin is an extension for customizing OpenShift web console by dynamically loading code from another service running on the cluster. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object 1.6. ConsoleQuickStart [console.openshift.io/v1] Description ConsoleQuickStart is an extension for guiding user through various workflows in the OpenShift web console. Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer). Type object 1.7. ConsoleYAMLSample [console.openshift.io/v1] Description ConsoleYAMLSample is an extension for customizing OpenShift web console YAML samples. Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer). Type object

Commands: