mtpti5iD/redhat-docs_dataset huggingface dataset:
8.2.6.2. Testing Backups Every type of backup should be tested on a periodic basis to make sure that data can be read from it. It is a fact that sometimes backups are performed that are, for one reason or another, unreadable. The unfortunate part in all this is that many times it is not realized until data has been lost and must be restored from backup. The reasons for this can range from changes in tape drive head alignment, misconfigured backup software, and operator error. No matter what the cause, without periodic testing you cannot be sure that you are actually generating backups from which data can be restored at some later time.

Commands:
3.3.3. Physical Host Devices Certain hardware platforms allow virtual machines to directly access various hardware devices and components. This process in virtualization is known as device assignment , or also as passthrough . PCI device assignment The KVM hypervisor supports attaching PCI devices on the host system to virtual machines. PCI device assignment provides guests with exclusive access to PCI devices for a range of tasks. It enables PCI devices to appear and behave as if they were physically attached to the guest virtual machine. Device assignment is supported on PCI Express devices, with the exception of graphics cards. Parallel PCI devices may be supported as assigned devices, but they have severe limitations due to security and system configuration conflicts. Note For more information on device assignment, refer to the Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide . USB passthrough The KVM hypervisor supports attaching USB devices on the host system to virtual machines. USB device assignment makes it possible for guests to have exclusive access to USB devices for a range of tasks. It also enables USB devices to appear and behave as if they were physically attached to the virtual machine. Note For more information on USB passthrough, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide . SR-IOV SR-IOV (Single Root I/O Virtualization) is a PCI Express standard that extends a single physical PCI function to share its PCI resources as separate, virtual functions (VFs). Each function is capable of being used by a different virtual machine through PCI device assignment. An SR-IOV-capable PCI-e device, provides a Single Root Function (for example, a single Ethernet port) and presents multiple, separate virtual devices as unique PCI device functions. Each virtual device may have its own unique PCI configuration space, memory-mapped registers, and individual MSI-based interrupts. Note For more information on SR-IOV, refer to the Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide . NPIV N_Port ID Virtualization (NPIV) is a functionality available with some Fibre Channel devices. NPIV shares a single physical N_Port as multiple N_Port IDs. NPIV provides similar functionality for Fibre Channel Host Bus Adapters (HBAs) that SR-IOV provides for PCIe interfaces. With NPIV, virtual machines can be provided with a virtual Fibre Channel initiator to Storage Area Networks (SANs). NPIV can provide high density virtualized environments with enterprise-level storage solutions. Note For more information on NPIV, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide .

Commands:
Chapter 18. Header Overview The header language provides a convenient way of accessing header values in the current message. When you supply a header name, the header language performs a case-insensitive lookup and returns the corresponding header value. The header language is part of camel-core . XML example For example, to resequence incoming exchanges according to the value of a SequenceNumber header (where the sequence number must be a positive integer), you can define a route as follows: Java example The same route can be defined in Java, as follows:

Commands:
<camelContext xmlns="http://camel.apache.org/schema/spring"> <route> <from uri=" SourceURL "/> <resequence> <language language="header">SequenceNumber</language> </resequence> <to uri=" TargetURL "/> </route> </camelContext>
from(" SourceURL ") .resequence(header("SequenceNumber")) .to(" TargetURL ");
8.3.3. Manual Pages for Services Manual pages for services contain valuable information, such as what file type to use for a given situation, and Booleans to change the access a service has (such as httpd accessing NFS volumes). This information may be in the standard manual page, or a manual page with selinux prepended or appended. For example, the httpd_selinux (8) manual page has information about what file type to use for a given situation, as well as Booleans to allow scripts, sharing files, accessing directories inside user home directories, and so on. Other manual pages with SELinux information for services include: Samba: the samba_selinux (8) manual page describes that files and directories to be exported via Samba must be labeled with the samba_share_t type, as well as Booleans to allow files labeled with types other than samba_share_t to be exported via Samba. Berkeley Internet Name Domain (BIND): the named (8) manual page describes what file type to use for a given situation (see the Red Hat SELinux BIND Security Profile section). The named_selinux (8) manual page describes that, by default, named cannot write to master zone files, and to allow such access, the named_write_master_zones Boolean must be enabled. The information in manual pages helps you configure the correct file types and Booleans, helping to prevent SELinux from denying access.

Commands:
8.166. pango 8.166.1. RHBA-2014:0585 - pango bug fix update Updated pango packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Pango is a library for laying out and rendering of text, with an emphasis on internationalization. Pango forms the core of text and font handling for the GTK+ widget toolkit. Bug Fixes BZ# 885846 Prior to this update, the Pango library used an incorrect macro for specifying a location of its man pages. Consequently, after installing the pango packages, the man pages were placed in the wrong directory. This update fixes the relevant macro in the Pango spec file and the man pages are now located in the correct directory. BZ# 1086690 Previously, the pango RPM scriptlet did not mask harmless error messages. As a consequence, although the migration was successful, the scriptlet printed error messages related to missing directories after an upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7. This update determines the location of the directory with the cache file, and these harmless error messages no longer appear. Users of pango are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.77. iscsi-initiator-utils 8.77.1. RHBA-2013:1700 - iscsi-initiator-utils bug fix and enhancement update Updated iscsi-initiator-utils packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The iscsi-initiator-utils packages provide the server daemon for the iSCSI protocol, as well as utilities used to manage the daemon. iSCSI (Internet Small Computer System Interface) is a protocol for distributed disk access using SCSI commands sent over Internet Protocol networks. Note The iscsi-initiator-utils packages have been upgraded to upstream version 6.2.0.873, which provides a number of bug fixes and enhancements over the version. (BZ# 916007 ) Bug Fixes BZ# 884427 Previously, database errors could occur if multiple node records in different formats were created for the same iSCSI target portal. Consequently, depending on the file system dependent return order of the readdir syscall, an error occasionally occurred causing an update operation to fail. To fix this bug, multiple node records in different formats have been prevented from existing simultaneously and detected at record creation time. Duplicate node entries no longer exist in the iSCSI database, and updates to records do not result in database errors. BZ# 983553 Prior to this update, a single unreachable target could previously block rescans of others. Consequently, the iscsiadm utility could halt in the D state and the rest of the targets could remain unscanned. To fix this bug, iscsiadm has been made terminable and all the targets have been updated. Now, functioning sessions will be rescanned properly without long delays. BZ# 1001705 When VDMS (Virtual Desktop Server Manager) attempted to add a new record to the iSCSI database, it failed with the following error: iscsiadm: Error while adding record: no available memory. Consequently, due to this error, the host became non-operational when connecting to storage. An upstream patch has been applied and the /var/lib/iscsi file is now successfully attached. Enhancements BZ# 831003 For the bnx2i hardware and potentially other offloading solutions (complementary network technologies for delivering data originally targeted for cellular networks), the iscsistart tool for passing along the VLAN tag from iBFT (iSCSI Boot Firmware Table) to iface_rec (iscsi iface record name) has been implemented to this package. BZ# 917600 With this update, support for managing Flash nodes from the open-iscsi utility has been added to this package. Users of iscsi-initiator-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 17. Business processes in Business Central A business process application created by a citizen developer in Business Central depicts the flow of the business process as a series of steps. Each step executes according to the process flow chart. A process can consist of one or more smaller discrete tasks. As a knowledge worker, you work on processes and tasks that occur during business process execution. As an example, using Red Hat Process Automation Manager, the mortgage department of a financial institution can automate the complete business process for a mortgage loan. When a new mortgage request comes in, a new process instance is created in the mortgage application. Because all requests follow the same set of rules for processing, consistency in every step is ensured. This results in an efficient process that reduces processing time and effort. 17.1. Knowledge worker user Consider the example of a customer account representative processing mortgage loan requests at a financial institution. As a customer account representative, you can perform the following tasks: Accept and decline mortgage requests Search and filter through requests Delegate, claim, and release requests Set a due date and priority on requests View and comment on requests View the request history log

Commands:
Chapter 11. User Defined Functions 11.1. User Defined Functions Teiid Designer enables you to extend Teiid's function library by using custom or User Defined Functions(UDFs). You can define a UDF with follwing properties. Function Name - When you create the function name, remember that: You cannot overload existing Teiid System functions. The function name must be unique among user defined functions in its model for the number of arguments. You can use the same function name for different numbers of types of arguments. Hence, you can overload your user defined functions. The function name cannot contain the '.' character. The function name cannot exceed 255 characters. Input Parameters- Input Parameter defines a type specific signature list. All arguments are considered required. Return Type- the expected type of the returned scalar value. Pushdown - Indicates the expected pushdown behavior. It can be one of REQUIRED, NEVER, ALLOWED. If NEVER or ALLOWED are specified then a Java implementation of the function must be supplied. If REQUIRED is used, then user must extend the Translator for the source and add this function to its pushdown function library. invocationClass/invocationMethod- optional properties indicating the method to invoke when the UDF is not pushed down. Deterministic - if the method always returns the same result for the same input parameters. Defaults to false. It is important to mark the function as deterministic if it returns the same value for the same inputs as this leads to better performance. Even Pushdown required functions need to be added as a UDF to allow Teiid to properly parse and resolve the function. Pushdown scalar functions differ from normal user defined functions in that no code is provided for evaluation in the engine. An exception is raised if a pushdown required function cannot be evaluated by the appropriate source.

Commands:
11.5. Sub-collections 11.5.1. Network VNIC Profile Sub-Collection VNIC (Virtual Network Interface Controller) profiles, also referred to as virtual machine interface profiles, are customized profiles applied to users and groups to limit network bandwidth. Each vnicprofile contains the following elements: Table 11.2. Elements for vnic profiles Element Type Description name string The unique identifier for the profile. description string A plain text description of the profile. network string The unique identifier of the logical network to which the profile applies. port_mirroring Boolean: true or false The default is false . Example 11.6. An XML representation of the network's vnicprofile sub-collection 11.5.2. Network Labels Sub-Collection Network labels are plain text, human-readable labels that allow you to automate the association of logical networks with physical host network interfaces. Each label contains the following elements: Table 11.3. Elements for labels Element Type Description network string The href and id of the networks to which the label is attached. Example 11.7. An XML representation of the network's labels sub-collection 11.5.3. Methods 11.5.3.1. Attach Label to Logical Network Action You can attach labels to a logical network to automate the association of that logical network with physical host network interfaces to which the same label has been attached. Example 11.8. Action to attach a label to a logical network 11.5.3.2. Removing a Label From a Logical Network Removal of a label from a logical network requires a DELETE request. Example 11.9. Removing a label from a logical network

Commands:
<vnic_profile href= "/ovirt-engine/api/vnicprofiles/f9c2f9f1-3ae2-4100-a9a5-285ebb755c0d" id="f9c2f9f1-3ae2-4100-a9a5-285ebb755c0d"> <name>Peanuts</name> <description>shelled</description> <network href= "/ovirt-engine/api/networks/00000000-0000-0000-0000-000000000009" id="00000000-0000-0000-0000-000000000009"/> <port_mirroring>false</port_mirroring> </vnic_profile> </vnic_profiles>
<labels> <label href="/ovirt-engine/api/networks/00000000-0000-0000-0000-000000000000/labels/eth0" id="eth0"> <network href="/ovirt-engine/api/networks/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"/> </label> </labels>
POST /ovirt-engine/api/networks/00000000-0000-0000-0000-000000000000/labels/ HTTP/1.1 Accept: application/xml Content-type: application/xml <label id="Label_001" />
DELETE /ovirt-engine/api/networks/00000000-0000-0000-0000-000000000000/labels/ [label_id] HTTP/1.1 HTTP/1.1 204 No Content
2.2. Defining Directory Needs When designing the directory data, think not only of the data that is currently required but also how the directory (and organization) is going to change over time. Considering the future needs of the directory during the design process influences how the data in the directory are structured and distributed. Look at these points: What should be put in the directory today? What immediate problem is solved by deploying a directory? What are the immediate needs of the directory-enabled application being used? What information is going to be added to the directory in the near future? For example, an enterprise might use an accounting package that does not currently support LDAP but will be LDAP-enabled in a few months. Identify the data used by LDAP-compatible applications, and plan for the migration of the data into the directory as the technology becomes available. What information might be stored in the directory in the future? For example, a hosting company may have future customers with different data requirements than their current customers, such as needing to store images or media files. While this is the hardest answer to anticipate, doing so may pay off in unexpected ways. At a minimum, this kind of planning helps identify data sources that might not otherwise have been considered.

Commands:
Chapter 2. Architectures Red Hat Enterprise Linux 8.1 is distributed with the kernel version 4.18.0-147, which provides support for the following architectures: AMD and Intel 64-bit architectures The 64-bit ARM architecture IBM Power Systems, Little Endian 64-bit IBM Z Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures . For a list of available subscriptions, see Subscription Utilization on the Customer Portal.

Commands:
16.4.4. Shell Scripting with guestfish Once you are familiar with using guestfish interactively, according to your needs, writing shell scripts with it may be useful. The following is a simple shell script to add a new MOTD (message of the day) to a guest:

Commands:
#!/bin/bash - set -e guestname="USD1" guestfish -d "USDguestname" -i <<'EOF' write /etc/motd "Welcome to Acme Incorporated." chmod 0644 /etc/motd EOF
Chapter 7. Red Hat Process Automation Manager reference implementations Red Hat Process Automation Manager provides reference implementations that you can use as starter applications. They are included in the Red Hat Process Automation Manager 7.13.5 Reference Implementations download, available on the Red Hat Process Automation Manager Software Downloads page in the Red Hat Customer Portal. Employee Rostering reference implementation The employee rostering reference implementation enables you to create an application that assigns employees to shifts on various positions in an organization. For example, you can use the application to distribute shifts in a hospital between nurses, guard duty shifts across a number of locations, or shifts on an assembly line between workers. Vehicle route planning reference implementation The vehicle route planning reference implementation enables you to create an application that solves a vehicle route planning problem with real-world maps, roads, and vehicles delivering goods to locations, each with a specific capacity. For more information, see the README file in the vehicle routing ZIP file, included in the reference implementation download. School timetable reference implementation The school timetable reference implementation enables you to build a REST application on Spring Boot that associates lessons with rooms and time slots and avoids conflicts by considering student and teacher constraints. High available event-driven decisioning reference implementation The high available event-driven decisioning reference implementation enables you to deploy Drools engine code that requires stateful processing, including rules developed with complex event processing, in an OpenShift environment. Doing this enables the decision engine to process complex event series with high availability.

Commands:
function::task_state Name function::task_state - The state of the task Synopsis Arguments task task_struct pointer Description Return the state of the given task, one of: TASK_RUNNING (0), TASK_INTERRUPTIBLE (1), TASK_UNINTERRUPTIBLE (2), TASK_STOPPED (4), TASK_TRACED (8), EXIT_ZOMBIE (16), or EXIT_DEAD (32).

Commands:
task_state:long(task:long)
8.2. Memory Tuning Tips To optimize memory performance in a virtualized environment, consider the following: Do not allocate more resources to guest than it will use. If possible, assign a guest to a single NUMA node, providing that resources are sufficient on that NUMA node. For more information on using NUMA, see Chapter 9, NUMA . When increasing the amount of memory a guest virtual machine can use while the guest is running, also referred to as hot plugging , the memory needs to be manually brought online on the guest by one of the following methods: Create a custom udev rule Create a file with a name that ends in the .rules suffix in the /etc/udev/rules.d/ directory: Add the memory onlining to the created file: Reload udev rules: Bring inactive memory online manually after each hot plug

Commands:
touch /etc/udev/rules.d/ rulename .rules
echo 'SUBSYSTEM=="memory", ACTION=="add", ATTR{state}=="offline", ATTR{state}="online"' > /etc/udev/rules.d/ rulename .rules
udevadm control --reload
for mblock in /sys/devices/system/memory/memory*; do echo online > USDmblock/state; done
Chapter 15. command This chapter describes the commands under the command command. 15.1. command list List recognized commands by group Usage: Table 15.1. Command arguments Value Summary -h, --help Show this help message and exit --group <group-keyword> Show commands filtered by a command group, for example: identity, volume, compute, image, network and other keywords Table 15.2. Output formatter options Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated Table 15.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 15.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 15.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack command list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--group <group-keyword>]