mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 59. Defining data tables for guided rule templates After you create a guided rule template and add template keys for field values, a data table is displayed in the Data table of the guided rule templates designer. Each column in the data table corresponds to a template key that you added in the guided rule template. Use this table to define values for each template key row by row. Each row of values that you define in the data table for that template results in a rule. Procedure In the guided rule templates designer, click the Data tab to view the data table. Each column in the data table corresponds to a template key that you added in the guided rule template. Note If you did not add any template keys to the rule template, then this data table does not appear and the template does not function as a genuine template but essentially as an individual guided rule. For this reason, template keys are fundamental in creating guided rule templates. Click Add row and define the data values for each template key column to generate that rule (row). Continue adding rows and defining data values for each rule that will be generated. You can click Add row for each new row, or click the plus icon ( ) or minus icon to add or remove rows. Figure 59.1. Sample data table for a guided rule template To view the DRL code, click the Source tab in the guided rule templates designer. Example: As a visual aid, click the grid icon in the upper-left corner of the data table to toggle cell merging on and off, if needed. Cells in the same column with identical values are merged into a single cell. Figure 59.2. Merge cells in a data table You can then use the expand/collapse icon [+/-] in the upper-left corner of each newly merged cell to collapse the rows corresponding to the merged cell, or to re-expand the collapsed rows. Figure 59.3. Collapse merged cells After you define the template key data for all rules and adjust the table display as needed, click Validate in the upper-right toolbar of the guided rule templates designer to validate the guided rule template. If the rule template validation fails, address any problems described in the error message, review all components in the rule template and data defined in the data table, and try again to validate the rule template until the rule template passes. Click Save in the guided rule templates designer to save your work.

Commands:
rule "PaymentRules_6" when Customer( internetService == false , phoneService == false , TVService == true ) then RecurringPayment fact0 = new RecurringPayment(); fact0.setAmount( 5 ); insertLogical( fact0 ); end rule "PaymentRules_5" when Customer( internetService == false , phoneService == true , TVService == false ) then RecurringPayment fact0 = new RecurringPayment(); fact0.setAmount( 5 ); insertLogical( fact0 ); end //Other rules omitted for brevity.
4.152. libvirt-qmf 4.152.1. RHBA-2012:0525 - libvirt-qmf bug fix update Updated libvirt-qmf packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libvirt-qmf packages provide an interface with libvirt using Qpid Management Framework (QMF), which utilizes the Advanced Message Queuing Protocol (AMQP). AMQP is an open standard application layer protocol providing reliable transport of messages. Bug Fix BZ# 807931 Qpid APIs using the libpidclient and libpidcommon libraries are not application binary interface (ABI) stable. These dependencies have been removed so that Qpid rebuilds do not affect the libvirt-qmf packages. All users of libvirt-qmf are advised to upgrade to these updated packages, which fix this bug.

Commands:
9.10. Balloon Driver The balloon driver allows guests to express to the hypervisor how much memory they require. The balloon driver allows the host to efficiently allocate and memory to the guest and allow free memory to be allocated to other guests and processes. Guests using the balloon driver can mark sections of the guest's RAM as not in use (balloon inflation). The hypervisor can free the memory and use the memory for other host processes or other guests on that host. When the guest requires the freed memory again, the hypervisor can reallocate RAM to the guest (balloon deflation).

Commands:
Chapter 1. Planning Red Hat Gluster Storage Installation This chapter outlines the minimum hardware and software installation requirements for a successful installation, configuration, and operation of a Red Hat Gluster Storage Server environment. 1.1. About Red Hat Gluster Storage Red Hat Gluster Storage is a software-only, scale-out storage that provides flexible and affordable unstructured data storage for the enterprise. Red Hat Gluster Storage 3.5 provides new opportunities to unify data storage and infrastructure, increase performance, and improve availability and manageability in order to meet a broader set of an organization's storage challenges and requirements. GlusterFS, a key building block of Red Hat Gluster Storage, is based on a stackable user space design and can deliver exceptional performance for diverse workloads. GlusterFS aggregates various storage servers over network interconnects into one large parallel network file system. The POSIX compatible GlusterFS servers, which use XFS file system format to store data on disks, can be accessed using industry standard access protocols including NFS and CIFS. Red Hat Gluster Storage can be deployed in the private cloud or datacenter using Red Hat Gluster Storage Server for On-Premise. Red Hat Gluster Storage can be installed on commodity servers or virtual machines and storage hardware resulting in a powerful, massively scalable, and highly available NAS environment. Additionally, Red Hat Gluster Storage can be deployed in the public cloud using Red Hat Gluster Storage Server for Public Cloud, for example, within the Amazon Web Services (AWS) cloud. It delivers all the features and functionality possible in a private cloud or datacenter to the public cloud by providing massively scalable and highly available NAS in the cloud. Red Hat Gluster Storage Server for On-Premise Red Hat Gluster Storage Server for On-Premise enables enterprises to treat physical storage as a virtualized, scalable, and centrally managed pool of storage by using commodity server and storage hardware. Red Hat Gluster Storage Server for Public Cloud Red Hat Gluster Storage Server for Public Cloud packages GlusterFS as an Amazon Machine Image (AMI) for deploying scalable NAS in the AWS public cloud. This powerful storage server provides a highly available, scalable, virtualized, and centrally managed pool of storage for Amazon users. Storage node A storage node can be a physical server, a virtual machine, or a public cloud machine image running one instance of Red Hat Gluster Storage.

Commands:
4.5.6. Logging Configuration Clicking on the Logging tab displays the Logging Configuration page, which provides an interface for configuring logging settings. You can configure the following settings for global logging configuration: Checking Log Debugging Messages enables debugging messages in the log file. Checking Log Messages to Syslog enables messages to syslog . You can select the Syslog Message Facility and the Syslog Message Priority . The Syslog Message Priority setting indicates that messages at the selected level and higher are sent to syslog . Checking Log Messages to Log File enables messages to the log file. You can specify the Log File Path name. The logfile message priority setting indicates that messages at the selected level and higher are written to the log file. You can override the global logging settings for specific daemons by selecting one of the daemons listed beneath the Daemon-specific Logging Overrides heading at the bottom of the Logging Configuration page. After selecting the daemon, you can check whether to log the debugging messages for that particular daemon. You can also specify the syslog and log file settings for that daemon. Click Apply for the logging configuration changes you have specified to take effect.

Commands:
Chapter 15. Configuring API tokens Red Hat Advanced Cluster Security for Kubernetes (RHACS) requires API tokens for some system integrations, authentication processes, and system functions. You can configure tokens using the RHACS web interface. Note To prevent privilege escalation, when you create a new token, your role's permissions limit the permission you can assign to that token. For example, if you only have read permission for the Integration resource, you cannot create a token with write permission. If you want a custom role to create tokens for other users to use, you must assign the required permissions to that custom role. Use short-lived tokens for machine-to-machine communication, such as CI/CD pipelines, scripts, and other automation. Also, use the roxctl central login command for human-to-machine communication, such as roxctl CLI or API access. The majority of cloud service providers support OIDC identity tokens, for example, Microsoft Entra ID, Google Cloud Identity Platform, and AWS Cognito. OIDC identity tokens issued by these services can be used for RHACS short-lived access. 15.1. Creating an API token Procedure In the RHACS portal, go to Platform Configuration Integrations . Scroll to the Authentication Tokens category, and then click API Token . Click Generate Token . Enter a name for the token and select a role that provides the required level of access (for example, Continuous Integration or Sensor Creator ). Click Generate . Important Copy the generated token and securely store it. You will not be able to view it again. Additional resources Using an authentication provider to authenticate with roxctl Configuring short-lived access Using Azure Entra ID service principals for machine to machine auth with RHACS 15.2. About API token expiration API tokens expire one year from the creation date. RHACS alerts you in the web interface and by sending log messages to Central when a token will expire in less than one week. The log message process runs once an hour. Once a day, the process lists the tokens that are expiring and creates a log message for each one. Log messages are issued once a day and appear in Central logs. Logs have the format as shown in the following example: Warn: API Token [token name] (ID [token ID]) will expire in less than X days. You can change the default settings for the log message process by configuring the environment variables shown in the following table: Environment variable Default value Description ROX_TOKEN_EXPIRATION_NOTIFIER_INTERVAL 1h (1 hour) The frequency at which the log message background loop that lists tokens and creates the logs will run. ROX_TOKEN_EXPIRATION_NOTIFIER_BACKOFF_INTERVAL 24h (1 day) The frequency at which the loop lists tokens and issues notifications. ROX_TOKEN_EXPIRATION_DETECTION_WINDOW 168h (1 week) The time period before expiration of the token that will cause the notification to be generated.

Commands:
Warn: API Token [token name] (ID [token ID]) will expire in less than X days.
30.8. Statistics Files in /sys Statistics for a running VDO volume may be read from files in the /sys/kvdo/ volume_name /statistics directory, where volume_name is the name of thhe VDO volume. This provides an alternate interface to the data produced by the vdostats utility suitable for access by shell scripts and management software. There are files in the statistics directory in addition to the ones listed in the table below. These additional statistics files are not guaranteed to be supported in future releases. Table 30.10. Statistics files File Description dataBlocksUsed The number of physical blocks currently in use by a VDO volume to store data. logicalBlocksUsed The number of logical blocks currently mapped. physicalBlocks The total number of physical blocks allocated for a VDO volume. logicalBlocks The maximum number of logical blocks that can be mapped by a VDO volume. mode Indicates whether a VDO volume is operating normally, is in recovery mode, or is in read-only mode.

Commands:
Chapter 9. File Systems The CephFS kernel client is fully supported with Red Hat Ceph Storage 3 The Ceph File System (CephFS) kernel module enables Red Hat Enterprise Linux nodes to mount Ceph File Systems from Red Hat Ceph Storage clusters. The kernel client in Red Hat Enterprise Linux is a more efficient alternative to the Filesystem in Userspace (FUSE) client included with Red Hat Ceph Storage. Note that the kernel client currently lacks support for CephFS quotas. The CephFS kernel client was introduced in Red Hat Enterprise Linux 7.3 as a Technology Preview, and since the release of Red Hat Ceph Storage 3, CephFS is fully supported. For more information, see the Ceph File System Guide for Red Hat Ceph Storage 3: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/ceph_file_system_guide/ . (BZ#1205497) XFS now supports modifying labels on mounted file systems You can now modify the label attribute of mounted XFS file systems using the xfs_io utility: Previously, it was only possible to modify labels on unmounted file systems using the xfs_admin utility, which is still supported. (BZ# 1322930 ) pNFS SCSI layout is now fully supported for client and server Client and server support for parallel NFS (pNFS) SCSI layouts is now fully supported. It was first introduced in Red Hat Enterprise Linux 7.3 as a Technology Preview. Building on the work of block layouts, the pNFS layout is defined across SCSI devices and contains sequential series of fixed-size blocks as logical units that must be capable of supporting SCSI persistent reservations. The Logical Unit (LU) devices are identified by their SCSI device identification, and fencing is handled through the assignment of reservations. (BZ#1305092) ima-evm-utils is now fully supported on AMD64 and Intel 64 The ima-evm-utils package is now fully supported when used on the AMD64 and Intel 64 architecture. Note that on other architectures, ima-evm-utils remains in Technology Preview. The ima-evm-utils package provides utilities to label the file system and verify the integrity of your system at run time using the Integrity Measurement Architecture (IMA) and Extended Verification Module (EVM) features. These utilities enable you to monitor if files have been accidentally or maliciously altered. (BZ#1627278)

Commands:
xfs_io -c "label -s new-label" /mount-point
Installing Red Hat Virtualization as a standalone Manager with local databases Red Hat Virtualization 4.4 Installing the Red Hat Virtualization Manager and its databases on the same server Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract This document describes how to install a standalone Manager environment - where the Red Hat Virtualization Manager is installed on either a physical server or a virtual machine hosted in another environment - with the Manager database and the Data Warehouse service and database installed on the same machine as the Manager. If this is not the configuration you want to use, see the other Installation Options in the Product Guide .

Commands:
3.9. The SET Statement Execution properties are set on the connection using the SET statement. The SET statement is not yet a language feature of JBoss Data Virtualization and is handled only in the JDBC client. SET Syntax: SET [PAYLOAD] (parameter|SESSION AUTHORIZATION) value SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL (READ UNCOMMITTED|READ COMMITTED|REPEATABLE READ|SERIALIZABLE) Syntax Rules: The parameter must be an identifier. If quoted, it can contain spaces and other special characters, but otherwise it can not. The value may be either a non-quoted identifier or a quoted string literal value. If payload is specified, for example, SET PAYLOAD x y , then a session scoped payload properties object will have the corresponding name value pair set. The payload object is not fully session scoped. It will be removed from the session when the XAConnection handle is closed/returned to the pool (assumes the use of TeiidDataSource). The session scoped payload is superseded by usage of the TeiidStatement.setPayload . Using SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL is equivalent to calling Connection.setTransactionIsolation with the corresponding level. The SET statement is most commonly used to control planning and execution. SET SHOWPLAN (ON|DEBUG|OFF) SET NOEXEC (ON|OFF) The following is an example of how to use the SET statement to enable a debug plan: The SET statement may also be used to control authorization. A SET SESSION AUTHORIZATION statement will perform a reauthentication (see Section 2.6, "Reauthentication" ) given the credentials currently set on the connection. The connection credentials may be changed by issuing a SET PASSWORD statement.

Commands:
Statement s = connection.createStatement(); s.execute("SET SHOWPLAN DEBUG"); Statement s1 = connection.createStatement(); ResultSet rs = s1.executeQuery("select col from table"); ResultSet planRs = s1.executeQuery("SHOW PLAN"); planRs.next(); String debugLog = planRs.getString("DEBUG_LOG"); Query Plan without executing the query s.execute("SET NOEXEC ON"); s.execute("SET SHOWPLAN DEBUG"); e.execute("SET NOEXEC OFF");
Statement s = connection.createStatement(); s.execute("SET PASSWORD 'someval'"); s.execute("SET SESSION AUTHORIZATION 'newuser'");
Chapter 24. Tags 24.1. Tag Elements The tags collection provides information about tags in a Red Hat Virtualization environment. An API user accesses this information through the rel="tags" link obtained from the entry point URI. The following table shows specific elements contained in a tag resource representation. Table 24.1. Tag elements Element Type Description Properties host GUID A reference to the host which the tag is attached. user GUID A reference to the user which the tag is attached. vm GUID A reference to the VM which the tag is attached. parent complex A reference to the VM which the tag is attached.

Commands:
Chapter 2. Installing .NET 8.0 .NET 8.0 is included in the AppStream repositories for RHEL 8. The AppStream repositories are enabled by default on RHEL 8 systems. You can install the .NET 8.0 runtime with the latest 8.0 Software Development Kit (SDK). When a newer SDK becomes available for .NET 8.0, you can install it by running sudo yum install . Prerequisites Installed and registered RHEL 8.9 with attached subscriptions. For more information, see Performing a standard RHEL 8 installation . Procedure Install .NET 8.0 and all of its dependencies: Verification steps Verify the installation: The output returns the relevant information about the .NET installation and the environment.

Commands:
sudo yum install dotnet-sdk-8.0 -y
dotnet --info
Chapter 4. Validating the syntax of existing attribute values With syntax validation, the Directory Server checks if an attribute value follows the rules of the syntax provided in the definition of that attribute. The Directory Server records the results of syntax validation tasks in the /var/log/dirsrv/slapd-instance_name/errors file. Manual syntax validation is required if: You have the syntax validation disabled in the nsslapd-syntaxcheck parameter. Note Red Hat recommends that syntax validation should not be disabled. You migrate data from a server with disabled or without syntax validation. 4.1. Creating a syntax validation task using the dsconf schema validate-syntax command With the dsconf schema validate-syntax command, you can create a syntax validation task to check every modified attribute and ensure that the new value has the required syntax. Procedure To create a syntax validation task, enter: # dsconf -D "cn=Directory Manager" ldap://server.example.com schema validate-syntax -f '(objectclass=inetorgperson)' ou=People,dc=example,dc=com In the example output, the command creates a task that validates the syntax of all values in the ou=People,dc=example,dc=com sub-tree which match the (objectclass=inetorgperson) filter. 4.2. Creating a syntax validation task using a cn task entry The cn=tasks,cn=config entry in the Directory Server configuration is a container entry for temporary entries used by the server for managing tasks. You can initiate a syntax validation operation by creating a task in the cn=syntax validate,cn=tasks,cn=config entry. Procedure To initiate a syntax validation operation, create a task in the cn=syntax validate,cn=tasks,cn=config entry as follows: # ldapadd -D "cn=Directory Manager" -W -p 389 -H ldap://server.example.com -x dn: cn=example_syntax_validate,cn=syntax validate,cn=tasks,cn=config objectclass: extensibleObject cn: cn=example_syntax_validate basedn: ou=People,dc=example,dc=com filter: (objectclass=inetorgperson) In the example output, the command creates a task that validates the syntax of all values in the ou=People,dc=example,dc=com sub-tree that is similar to the (objectclass=inetorgperson) filter. When the task completes, Directory Server deletes the entry from the directory configuration. Additional resources Configuration and schema reference

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com schema validate-syntax -f '(objectclass=inetorgperson)' ou=People,dc=example,dc=com
ldapadd -D "cn=Directory Manager" -W -p 389 -H ldap://server.example.com -x dn: cn=example_syntax_validate,cn=syntax validate,cn=tasks,cn=config objectclass: extensibleObject cn: cn=example_syntax_validate basedn: ou=People,dc=example,dc=com filter: (objectclass=inetorgperson)
Chapter 2. Eclipse Temurin features Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. For the list of changes and security fixes that the latest OpenJDK 8 release of Eclipse Temurin includes, see OpenJDK 8u422 Released . New features and enhancements Review the following release notes to understand new features and feature enhancements that the Eclipse Temurin 8.0.422 release provides: System properties for controlling the keep-alive behavior of HTTPURLConnection OpenJDK 8.0.422 includes the following new system properties that you can use to control the keep-alive behavior of HTTPURLConnection in situations where the server does not specify a keep-alive time: The http.keepAlive.time.server property controls the number of seconds before an idle connection to a server is closed. The http.keepAlive.time.proxy property controls the number of seconds before an idle connection to a proxy is closed. Note If the server or proxy specifies a keep-alive time in a Keep-Alive response header, this keep-alive time takes precedence over any value that you specify for the http.keepAlive.time.server or http.keepAlive.time.proxy property. See JDK-8278067 (JDK Bug System) . GlobalSign R46 and E46 root certificates added In OpenJDK 8.0.422, the cacerts truststore includes two GlobalSign TLS root certificates: Certificate 1 Name: GlobalSign Alias name: globalsignr46 Distinguished name: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE Certificate 2 Name: GlobalSign Alias name: globalsigne46 Distinguished name: CN=GlobalSign Root E46, O=GlobalSign nv-sa, C=BE See JDK-8316138 (JDK Bug System) . Revised on 2024-08-02 13:17:59 UTC

Commands: