mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Overview of the all-in-one Red Hat OpenStack Platform environment In the all-in-one Red Hat OpenStack Platform (RHOSP) environment this scenario, there is no pre-existing undercloud dependency. Instead, the installer runs an inline heat-all instance to bootstrap the deployment process and convert the selected heat templates into Ansible playbooks that you can execute on a local machine. If you want to perform complex operations, you must deploy a production-level scaled cloud. Workflow To install, configure, and deploy a simple, single-node RHOSP environment, complete the tasks in the following workflow: Prepare your environment. Install packages for the all-in-one environment. Configure the all-in-one environment. Deploy the all-in-one environment. Benefits of the all-in-one installation Composable services. Pre-defined roles. Condensed single-node environment. Playbooks that you can use to run the small-footprint installer in a container and generate Ansible playbooks. Configuration If you want to experiment with configuring roles and services, see Chapter 8, Working with custom roles and services and Section 7.1, "Core heat templates" . Composable roles You can create custom composable roles and deploy specific services for each role. Ansible This installation applies Ansible playbooks automatically with the deployment command. You can also direct the deployment command to output Ansible playbooks that you can use on other environments. For example, you can complete testing in the all-in-one installation, and then apply the verified Ansible playbook to other environments.

Commands:
Chapter 47. Standalone perspectives in Business Central Business Central provides specialized editors for authoring assets based on the asset's format. Business Central has a feature that enables you to use these editors individually. This feature is known as the standalone perspective mode of the editor or simply the standalone perspectives . As a business rules developer, you can embed a standalone perspective in your web application and then use it to edit rules, processes, decision tables, and other assets. After embedding a perspective you can edit an asset in your own application without switching to Business Central. You can use this feature to customize your web application. In addition to standalone perspectives you can also embed standalone custom pages (dashboards) in your applications. You can access a standalone perspective by using a specific web address in a browser with the standalone and perspective parameters. A standalone perspective's web address may also contain additional parameters.

Commands:
7.6. iptables and Connection Tracking iptables includes a module that allows administrators to inspect and restrict connections to services available on an internal network using a method called connection tracking . Connection tracking stores connections in a table, which allows administrators to allow or deny access based on the following connection states: NEW - A packet requesting a new connection, such as an HTTP request. ESTABLISHED - A packet that is part of an existing connection. RELATED - A packet that is requesting a new connection but is part of an existing connection, such as passive FTP connections where the connection port is 20, but the transfer port can be any unused port 1024 or higher. INVALID - A packet that is not part of any connections in the connection tracking table. You can use the stateful functionality of iptables connection tracking with any network protocol, even if the protocol itself is stateless (such as UDP). The following example shows a rule that uses connection tracking to forward only the packets that are associated with an established connection:

Commands:
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
Chapter 2. Configuring client-side notifications When actions and state changes occur in the Cryostat backend, Cryostat uses a WebSocket connection to show notifications in your Cryostat web client. You can enable or disable notifications on your Cryostat web console. Procedure From the Cryostat web console, click the Settings ( ) icon on the upper-right corner of the web console toolbar. Figure 2.1. Settings icon on the Cryostat web console From the Notifications & Messages panel, choose one of the following options: Enable all notifications by setting All Notifications to on. Disable all notifications by setting All Notifications to off. Expand Show more and select notification categories individually. Figure 2.2. Notifications & Messages panel in Settings window Note If you disable a notification category, your web client still receives notifications and stores them locally. Pop-up notifications will not display in the Cryostat web console, but if you re-enable the category, you can access those notifications. Revised on 2024-07-02 14:07:35 UTC

Commands:
7.9. avahi 7.9.1. RHBA-2013:0368 - avahi bug fix update Updated avahi packages that fix one bug are now available for Red Hat Enterprise Linux 6. Avahi is an implementation of the DNS Service Discovery and Multicast DNS specifications for Zero Configuration Networking. It facilitates service discovery on a local network. Avahi and Avahi-aware applications allow you to plug your computer into a network and, with no configuration, view other people to chat with, view printers to print to, and find shared files on other computers. Bug Fix BZ# 599435 Previously, the Avahi library packages required the Avahi daemon packages as a dependency. Consequently, whenever installing some of the Avahi libraries, the Avahi daemon was installed as well, which could pose a security risk in certain environments. This update removes these dependencies so that the Avahi libraries are now installed without the Avahi daemon. All users of avahi are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 19. Virtualization Performance monitoring in KVM guests As a Technology Preview, KVM can virtualize a performance monitoring unit (vPMU) to allow virtual machines to use performance monitoring. Additionally it supports Intel's "architectural PMU" which can be live-migrated across different host CPU versions, using the -cpu host option. The virtual performance monitoring feature allows virtual machine users to identify sources of performance problems in their guests, using their preferred pre-existing profiling tools that work on the host as well as the guest. Note that this is an addition to the existing ability to profile a KVM guest from the host. Package: kernel System monitoring using SNMP As a Technology Preview, Red Hat Enterprise Linux 6 allows Simple Network Management Protocol (SNMP) to be used for system monitoring. This allows KVM hosts to send SNMP traps on events so that hypervisor events can be communicated to the user via standard SNMP protocol. In addition, SNMP is capable of performing basic virtual networking operations, such as starting and stopping the virtual domain. Package: libvirt-snmp Zero-copy compatibility for macvtap-vhost The macvtap-vhost zero-copy capability is available on Red Hat Enterprise Linux 6 as a Technology Preview. This feature allows running networking work loads in very high wire speeds but with low CPU resource consumption, and it does not limit other features such as memory overcommit and guest migration, which is not the case when using PCI device assignment to achieve the wire speed. Note that this feature is disabled by default. Package: qemu-kvm vCPU hot unplug Although hot-plugging a virtual CPU (vCPU) is a supported operation, hot-unplugging a vCPU remains a Technology Preview in Red Hat Enterprise Linux 6, and is strongly recommended not to be used in high-value deployments. Package: libvirt

Commands:
function::print_usyms Name function::print_usyms - Print out user stack from string Synopsis Arguments callers String with list of hexadecimal (user) addresses Description This function performs a symbolic lookup of the addresses in the given string, which are assumed to be the result of prior calls to ustack , ucallers , and similar functions. Prints one line per address, including the address, the name of the function containing the address, and an estimate of its position within that function, as obtained by usymdata . Returns nothing.

Commands:
print_usyms(callers:string)
Chapter 6. Data Source Security 6.1. Data Source Security Data source security is about security considerations when JBoss Data Virtualization connects to data sources it is integrating. The following are other security considerations not already covered. Authorization Any data source level authorization decisions are up to the source systems being integrated. Encryption Encrypting remote data source access is the responsibility for the resource adapter and library/driver used to access the source system. Translators The translator framework also provides hooks for securing access at the datasource level. ExecutionFactory.getConnection may be overridden to initialize the source connection in any number of ways, such as re-authentication, based upon the Subject, execution payload, session variables, and any of the other relevant information accessible via the ExecutionContext and the CommandContext. You may even also modify the generated source SQL in any way that is seen fit in the relevant Execution.

Commands:
Chapter 4. Installing JBoss EAP Important If you are using a Red Hat Enterprise Linux On-Demand virtual machine from the Microsoft Azure Marketplace, you must install JBoss EAP using the ZIP or installer methods. You must not register a Red Hat Enterprise Linux On-Demand virtual machine to Red Hat Subscription Management, as you will be billed twice for that virtual machine. Installing JBoss EAP on a virtual machine in a Microsoft Azure environment is no different from a normal JBoss EAP installation. See the JBoss EAP Installation Guide for instructions.

Commands:
Chapter 4. Reviewing inventories with automation content navigator As a content creator, you can review your Ansible inventory with automation content navigator and interactively delve into the groups and hosts. 4.1. Reviewing inventory from automation content navigator You can review Ansible inventories with the automation content navigator text-based user interface in interactive mode and delve into groups and hosts for more details. Prerequisites A valid inventory file or an inventory plugin. Procedure Start automation content navigator. USD ansible-navigator Optional: type ansible-navigator inventory -i simple_inventory.yml from the command line to view the inventory. Review the inventory. :inventory -i simple_inventory.yml TITLE DESCRIPTION 0│Browse groups Explore each inventory group and group members members 1│Browse hosts Explore the inventory with a list of all hosts Type 0 to brows the groups. NAME TAXONOMY TYPE 0│general all group 1│nodes all group 2│ungrouped all group The TAXONOMY field details the hierarchy of groups the selected group or node belongs to. Type the number corresponding to the group you want to delve into. NAME TAXONOMY TYPE 0│node-0 all▸nodes host 1│node-1 all▸nodes host 2│node-2 all▸nodes host Type the number corresponding to the host you want to delve into, or type :<number> for numbers greater than 9. [node-1] 0│--- 1│ansible_host: node-1.example.com 2│inventory_hostname: node-1 Verification Review the inventory output. TITLE DESCRIPTION 0│Browse groups Explore each inventory group and group members members 1│Browse hosts Explore the inventory with a list of all hosts Additional resources ansible-inventory . How to build your inventory .

Commands:
ansible-navigator
:inventory -i simple_inventory.yml TITLE DESCRIPTION 0│Browse groups Explore each inventory group and group members members 1│Browse hosts Explore the inventory with a list of all hosts
NAME TAXONOMY TYPE 0│general all group 1│nodes all group 2│ungrouped all group
NAME TAXONOMY TYPE 0│node-0 all▸nodes host 1│node-1 all▸nodes host 2│node-2 all▸nodes host
[node-1] 0│--- 1│ansible_host: node-1.example.com 2│inventory_hostname: node-1
TITLE DESCRIPTION 0│Browse groups Explore each inventory group and group members members 1│Browse hosts Explore the inventory with a list of all hosts
Chapter 7. Conclusion When you complete all of the procedures, you will have: created a synclist for Red Hat Ansible Certified Content content. synchronized that content to your private automation hub. designated community collections from Ansible Galaxy to distribute to your users. configured content signing on private automation hub. signed and approved collections for your organization's specific needs. configured Ansible-Galaxy CLI to verify collections before signing them. Users can now view and download collections content from your private automation hub.

Commands:
18.7. Creating Advanced RAID Devices In some cases, you may wish to install the operating system on an array that can't be created after the installation completes. Usually, this means setting up the /boot or root file system arrays on a complex RAID device; in such cases, you may need to use array options that are not supported by Anaconda . To work around this, perform the following procedure: Procedure 18.1. Creating Advanced RAID Devices Insert the install disk. During the initial boot up, select Rescue Mode instead of Install or Upgrade . When the system fully boots into Rescue mode , the user will be presented with a command line terminal. From this terminal, use parted to create RAID partitions on the target hard drives. Then, use mdadm to manually create raid arrays from those partitions using any and all settings and options available. For more information on how to do these, see Chapter 13, Partitions , man parted , and man mdadm . Once the arrays are created, you can optionally create file systems on the arrays as well. Reboot the computer and this time select Install or Upgrade to install as normal. As Anaconda searches the disks in the system, it will find the pre-existing RAID devices. When asked about how to use the disks in the system, select Custom Layout and click . In the device listing, the pre-existing MD RAID devices will be listed. Select a RAID device, click Edit and configure its mount point and (optionally) the type of file system it should use (if you did not create one earlier) then click Done . Anaconda will perform the install to this pre-existing RAID device, preserving the custom options you selected when you created it in Rescue Mode . Note The limited Rescue Mode of the installer does not include man pages. Both the man mdadm and man md contain useful information for creating custom RAID arrays, and may be needed throughout the workaround. As such, it can be helpful to either have access to a machine with these man pages present, or to print them out prior to booting into Rescue Mode and creating your custom arrays.

Commands:
8.204. spice-protocol 8.204.1. RHEA-2013:1573 - spice-protocol enhancement update Updated spice-protocol packages that add various enhancements are now available for Red Hat Enterprise Linux 6. The spice-protocol packages provide header files to describe the SPICE protocol and the QXL para-virtualized graphics card. The SPICE protocol is needed to build newer versions of the spice-client and the spice-server packages. Note The spice-protocol packages have been upgraded to upstream version 0.12.6, which provides a number of enhancements over the version, including file copy support, and end-of-line conversion for copying and pasting text using clipboard when the client and guest conventions differ, or when there are different operating systems running. (BZ# 965812 ) Enhancement BZ# 978410 The continuity of video playbacks over limited bandwidth has improved. There are now fewer occurrences of scenes dropping and pauses, which leads to a better user experience. After this update, the video bit-rate and the playback latency are dynamically adjusted, using periodic reports from the client. The bandwidth and latency estimations of past video playbacks are now used for improving the initial parameter settings of future video playbacks. Users of spice-protocol are advised to upgrade to these updated packages, which add these enhancements.

Commands:
34.2. At and Batch While cron is used to schedule recurring tasks, the at command is used to schedule a one-time task at a specific time and the batch command is used to schedule a one-time task to be executed when the systems load average drops below 0.8. To use at or batch , the at RPM package must be installed, and the atd service must be running. To determine if the package is installed, use the rpm -q at command. To determine if the service is running, use the command /sbin/service atd status . 34.2.1. Configuring At Jobs To schedule a one-time job at a specific time, type the command at time , where time is the time to execute the command. The argument time can be one of the following: HH:MM format - For example, 04:00 specifies 4:00 a.m. If the time is already past, it is executed at the specified time the day. midnight - Specifies 12:00 a.m. noon - Specifies 12:00 p.m. teatime - Specifies 4:00 p.m. month-name day year format - For example, January 15 2002 specifies the 15th day of January in the year 2002. The year is optional. MMDDYY, MM/DD/YY, or MM.DD.YY formats - For example, 011502 for the 15th day of January in the year 2002. now + time - time is in minutes, hours, days, or weeks. For example, now + 5 days specifies that the command should be executed at the same time five days from now. The time must be specified first, followed by the optional date. For more information about the time format, read the /usr/share/doc/at- <version> /timespec text file. After typing the at command with the time argument, the at> prompt is displayed. Type the command to execute, press Enter , and type Ctrl + D . Multiple commands can be specified by typing each command followed by the Enter key. After typing all the commands, press Enter to go to a blank line and type Ctrl + D . Alternatively, a shell script can be entered at the prompt, pressing Enter after each line in the script, and typing Ctrl + D on a blank line to exit. If a script is entered, the shell used is the shell set in the user's SHELL environment, the user's login shell, or /bin/sh (whichever is found first). If the set of commands or script tries to display information to standard out, the output is emailed to the user. Use the command atq to view pending jobs. Refer to Section 34.2.3, "Viewing Pending Jobs" for more information. Usage of the at command can be restricted. For more information, refer to Section 34.2.5, "Controlling Access to At and Batch" for details.

Commands:
Chapter 2. Upgrading the Red Hat Developer Hub Helm Chart You can upgrade to a later version of Red Hat Developer Hub in OpenShift Container Platform by using either the web console or the CLI. OpenShift Container Platform web console In the Developer perspective, click Helm to open the Helm Releases tab. Click the overflow menu on the Helm release that you want to use and select Upgrade . On the Upgrade Helm Release page, select the version of Developer Hub that you want to upgrade to from the chart version drop-down list. Click Upgrade . Note It might take a few minutes to delete the resources in the older versions and to start the newer versions of the Developer Hub pods. Close all open Developer Hub web pages, and log in again to verify that the upgrade was successful. OpenShift Container Platform CLI Log in to the OpenShift Container Platform cluster as the cluster administrator and switch to the project or namespace in which Developer Hub was installed. For a new version of the Developer Hub Helm chart, run the following upgrade command: Note You can also provide extra values to the chart by creating a new-values.yml file on your workstation with values that override the attributes in the installed chart or by adding new attributes.

Commands:
login -u <user> -p <password> https://api.<HOSTNAME>:6443 project <your_namespace>
helm upgrade -i rhdh -f new-values.yml openshift-helm-charts/redhat-developer-hub --version 1.2.6
Chapter 48. Security The tang-nagios and clevis-udisk2 subpackages available as a Technology Preview The tang and clevis packages, which are part of the Red Hat Enterprise Linux Network Bound Disk Encryption (NBDE) project, contain also the tang-nagios and clevis-udisk2 subpackages. These subpackages are provided only as a Technology Preview. (BZ#1467338) USBGuard is now available for IBM Power as a Technology Preview The usbguard packages, which provide system protection against intrusive USB devices, are now available. With this update, the USBGuard software framework for the IBM Power architectures is provided as a Technology Preview. Full support is targeted for a later release of Red Hat Enterprise Linux. Note that USB is not supported on IBM z Systems, and the USBGuard framework cannot be provided on those systems. (BZ# 1467369 )

Commands:
Chapter 5. Preparation for migration Red Hat build of OpenJDK 21 includes changes that might require you to reconfigure your applications, which were already successfully deployed on Red Hat build of OpenJDK version 8, 11, or 17. You can ensure an effective migration plan by completing the following tasks, as appropriate: If you currently use Red Hat build of OpenJDK 8, review the Major differences between Red Hat build of OpenJDK 8 and Red Hat build of OpenJDK 11 section to familiarize yourself with the changes that are available from version 11 onward. If you currently use Red Hat build of OpenJDK 11 or earlier, review the Major differences between Red Hat build of OpenJDK 11 and Red Hat build of OpenJDK 17 section to familiarize yourself with the changes that are available from version 17 onward. Review the Major differences between Red Hat build of OpenJDK 17 and Red Hat build of OpenJDK 21 section to familiarize yourself with the changes that are available from version 21 onward. Integrate the differences into your migration plan. Red Hat provides a migration toolkit for applications (MTA) tool that you can use to help with your migration tasks. You can use the MTA tool to migrate Java applications from Red Hat build of OpenJDK version 8, 11, or 17 to Red Hat build of OpenJDK 21. Additional resources For more information about the installation of Red Hat build of OpenJDK 21 on RHEL, see the Installing and using Red Hat build of OpenJDK 21 on RHEL guide. For more information about the installation of Red Hat build of OpenJDK 21 on Microsoft Windows, see the Installing and using Red Hat build of OpenJDK 21 for Windows guide. For more information about switching between Red Hat build of OpenJDK versions on RHEL, see Interactively selecting a system-wide Red Hat build of OpenJDK version on RHEL in the Configuring Red Hat build of OpenJDK 21 on RHEL guide. For more information about the MTA tool, see the Introduction to the Migration Toolkit for Applications guide.

Commands:
macro::json_output_numeric_value Name macro::json_output_numeric_value - Output a numeric value. Synopsis Arguments name The name of the numeric metric. value The numeric value to output. Description The json_output_numeric_value macro is designed to be called from the 'json_data' probe in the user's script to output a metric's numeric value. This metric should have been added with json_add_numeric_metric .

Commands:
@json_output_numeric_value(name,value)