mtpti5iD/redhat-docs_dataset huggingface dataset:
Preface You can convert a standalone Red Hat Virtualization Manager to a self-hosted engine by backing up the standalone Manager and restoring it in a new self-hosted environment. The difference between the two environment types is explained below: Standalone Manager Architecture The Red Hat Virtualization Manager runs on a physical server, or a virtual machine hosted in a separate virtualization environment. A standalone Manager is easier to deploy and manage, but requires an additional physical server. The Manager is only highly available when managed externally with a product such as Red Hat's High Availability Add-On. The minimum setup for a standalone Manager environment includes: One Red Hat Virtualization Manager machine. The Manager is typically deployed on a physical server. However, it can also be deployed on a virtual machine, as long as that virtual machine is hosted in a separate environment. The Manager must run on Red Hat Enterprise Linux 8. A minimum of two hosts for virtual machine high availability. You can use Red Hat Enterprise Linux hosts or Red Hat Virtualization Hosts (RHVH). VDSM (the host agent) runs on all hosts to facilitate communication with the Red Hat Virtualization Manager. One storage service, which can be hosted locally or on a remote server, depending on the storage type used. The storage service must be accessible to all hosts. Figure 1. Standalone Manager Red Hat Virtualization Architecture Self-Hosted Engine Architecture The Red Hat Virtualization Manager runs as a virtual machine on self-hosted engine nodes (specialized hosts) in the same environment it manages. A self-hosted engine environment requires one less physical server, but requires more administrative overhead to deploy and manage. The Manager is highly available without external HA management. The minimum setup of a self-hosted engine environment includes: One Red Hat Virtualization Manager virtual machine that is hosted on the self-hosted engine nodes. The RHV-M Appliance is used to automate the installation of a Red Hat Enterprise Linux 8 virtual machine, and the Manager on that virtual machine. A minimum of two self-hosted engine nodes for virtual machine high availability. You can use Red Hat Enterprise Linux hosts or Red Hat Virtualization Hosts (RHVH). VDSM (the host agent) runs on all hosts to facilitate communication with the Red Hat Virtualization Manager. The HA services run on all self-hosted engine nodes to manage the high availability of the Manager virtual machine. One storage service, which can be hosted locally or on a remote server, depending on the storage type used. The storage service must be accessible to all hosts. Figure 2. Self-Hosted Engine Red Hat Virtualization Architecture

Commands:
Chapter 2. Using the Software Development Kit This chapter defines the modules and classes of the Ruby Software Development Kit and describes their usage. 2.1. Classes The OvirtSDK4 module contains the following software development kit classes: Connection The Connection class is the mechanism for connecting to the server and obtaining the reference to the root of the services tree. See Connecting to the server for details. Types The Type classes implement the types supported by the API. For example, the Vm class is the implementation of the virtual machine type. The classes are data containers and do not contain any logic. You will be working with instances of types. Instances of these classes are used as parameters and return values of service methods. The conversion to or from the underlying representation is handled transparently by the software development kit. Services The Service classes implement the services supported by the API. For example, the VmsService class is the implementation of the service that manages the collection of virtual machines in the system. Instances of these classes are automatically created by the SDK when a service is referenced. For example, a new instance of the VmsService class is created automatically by the SDK when you call the vms_service method of the SystemService class: vms_service = connection.system_service.vms_service Warning Do not create instances of these classes manually. The constructor parameters and methods may change in the future. Error The Error class is the base exception class that the software development kit raises when it reports an error. Certain specific error classes extend the base error class: AuthError - Authentication or authorization failure ConnectionError - Server name cannot be resolved or server is unreachable NotFoundError - Requested object does not exist TimeoutError - Operation time-out Other Classes Other classes (for example, HTTP client classes, readers, and writers) are used for HTTP communication and for XML parsing and rendering. Using these classes is not recommended, because they comprise internal implementation details that may change in the future. Their backwards-compatibility cannot be relied upon.

Commands:
vms_service = connection.system_service.vms_service
3.2.2. Configuration Script The most crucial function of Autotools is the creation of the configure script. This script tests systems for tools, input files, and other features it can use in order to build the project [1] . The configure script generates a Makefile which allows the make tool to build the project based on the system configuration. To create the configure script, first create an input file. Then feed it to an Autotools utility in order to create the configure script. This input file is typically configure.ac or Makefile.am ; the former is usually processed by autoconf , while the later is fed to automake . If a Makefile.am input file is available, the automake utility creates a Makefile template (that is, Makefile. in ), which may see information collected at configuration time. For example, the Makefile may have to link to a particular library if and only if that library is already installed. When the configure script runs, automake will use the Makefile. in templates to create a Makefile . If a configure.ac file is available instead, then autoconf will automatically create the configure script based on the macros invoked by configure.ac . To create a preliminary configure.ac , use the autoscan utility and edit the file accordingly. [1] For information about tests that configure can perform, see the following link: http://www.gnu.org/software/autoconf/manual/autoconf.html#Existing-Tests

Commands:
15.10. Displaying Disk I/O To view the disk I/O for all virtual machines on your system: Make sure that the Disk I/O statistics collection is enabled. To do this, from the Edit menu, select Preferences and click the Stats tab. Select the Disk I/O check box. Figure 15.24. Enabling Disk I/O To enable the Disk I.O display, from the View menu, select Graph , then the Disk I/O check box. Figure 15.25. Selecting Disk I/O The Virtual Machine Manager shows a graph of Disk I/O for all virtual machines on your system. Figure 15.26. Displaying Disk I/O

Commands:
Chapter 1. Getting started with Red Hat Quay configuration Red Hat Quay can be deployed by an independent, standalone configuration, or by using the OpenShift Container Platform Red Hat Quay Operator. How you create, retrieve, update, and validate the Red Hat Quay configuration varies depending on the type of deployment you are using. However, the core configuration options are the same for either deployment type. Core configuration can be set by one of the following options: Directly, by editing the config.yaml file. See "Editing the configuration file" for more information. Programmatically, by using the configuration API. See "Using the configuration API" for more information. Visually, by using the configuration tool UI. Note As of Red Hat Quay 3.10, the configuration tool has been removed on OpenShift Container Platform deployments, meaning that users cannot configure, or reconfigure, directly from the OpenShift Container Platform console. As a workaround, you can deploy the configuration tool locally and create your own configuration bundle. This includes entering the database and storage credentials used for your Red Hat Quay on OpenShift Container Platform deployment, generating a config.yaml file, and using it to deploy Red Hat Quay on OpenShift Container Platform via the command-line interface. To deploy the configuration tool locally, see Getting started with Red Hat Quay and follow the instructions up to "Configuring Red Hat Quay". For standalone deployments of Red Hat Quay, you must supply the minimum required configuration parameters before the registry can be started. The minimum requirements to start a Red Hat Quay registry can be found in the "Retrieving the current configuration" section. If you install Red Hat Quay on OpenShift Container Platform using the Red Hat Quay Operator, you do not need to supply configuration parameters because the Red Hat Quay Operator supplies default information to deploy the registry. After you have deployed Red Hat Quay with the desired configuration, you should retrieve, and save, the full configuration from your deployment. The full configuration contains additional generated values that you might need when restarting or upgrading your system.

Commands:
8.172. RDMA stack 8.172.1. RHSA-2013:1661 - Moderate: RDMA stack security, bug fix, and enhancement update Updated rdma , libibverbs , libmlx4 , librdmacm , qperf , perftest , openmpi , compat-openmpi , infinipath-psm , mpitests , and rds-tools packages that fix two security issues, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE link(s) associated with each description below. Red Hat Enterprise Linux includes a collection of Infiniband and iWARP utilities, libraries and development packages for writing applications that use Remote Direct Memory Access (RDMA) technology. Security Fixes CVE-2013-2561 A flaw was found in the way ibutils handled temporary files. A local attacker could use this flaw to cause arbitrary files to be overwritten as the root user via a symbolic link attack. CVE-2012-4516 It was discovered that librdmacm used a static port to connect to the ib_acm service. A local attacker able to run a specially crafted ib_acm service on that port could use this flaw to provide incorrect address resolution information to librmdacm applications. The CVE-2012-4516 issue was discovered by Florian Weimer of the Red Hat Product Security Team. This advisory updates the following packages to the latest upstream releases, providing a number of bug fixes and enhancements over the versions: Table 8.1. Upgraded packages Package name Upstream version libibverbs 1.1.7 libmlx4 1.0.5 librdmacm 1.0.17 mstflint 3.0 perftest 2.0 qperf 0.4.9 rdma 3.10 Several bugs have been fixed in the openmpi, mpitests, ibutils, and infinipath-psm packages. The most notable changes in these updated packages from the RDMA stack are the following: Multiple bugs in the Message Passing Interface (MPI) test packages were resolved, allowing more of the mpitest applications to pass on the underlying MPI implementations. The libmlx4 package now includes dracut module files to ensure that any necessary custom configuration of mlx4 port types is included in the initramfs dracut builds. Multiple test programs in the perftest and qperf packages now work properly over RoCE interfaces, or when specifying the use of rdmacm queue pairs. The mstflint package has been updated to the latest upstream version, which is now capable of burning firmware on newly released Mellanox Connect-IB hardware. A compatibility problem between the openmpi and infinipath-psm packages has been resolved with new builds of these packages. All RDMA users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements.

Commands:
8.5. Cache Metrics Name Property Description Prepared Plan Cache Size PREPARED_PLAN_CACHE.total-entries Current number of entries in cache. Prepared Plan Cache # of Requests PREPARED_PLAN_CACHE.request-count Total number of requests made against cache. Prepared Plan Cache Hit Ratio % PREPARED_PLAN_CACHE.hit-ratio Percentage of positive cache hits ResultSet Cache Size QUERY_SERVICE_RESULT_SET_CACHE.total-entries Current number of entries in cache. ResultSet Cache # of Requests QUERY_SERVICE_RESULT_SET_CACHE.request-count Total number of requests made against cache. ResultSet Cache Hit Ratio % QUERY_SERVICE_RESULT_SET_CACHE.hit-ratio Percentage of positive cache hits.

Commands:
Chapter 5. Exporting your subscription inventory You can export your full subscription inventory to a CSV file from the Subscription Inventory page in the Hybrid Cloud Console. The CSV file includes information from both the All subscriptions table and Subscription details table. Each line of the CSV file shows the following information about each subscription in your inventory: Name The name of the subscription and the product it applies to, such as Red Hat Ansible Automation Platform, Red Hat OpenShift Container Platform, Red Hat Enterprise Linux Server, or Red Hat Satellite Infrastructure Subscription. SKU The combination of letters and numbers that represent the subscription stock keeping unit (SKU), such as RH00000. Service level The type of service level agreement (SLA) for the subscription, as defined within the terms of the contract, such as Premium, Standard, Self-Support or Layered. Support type The team you contact for support, such as Red Hat support (L1-L3) or Partner support (L3). Capacity name The name of the units used to measure the usage of a Red Hat product, such as sockets, cores, or nodes. Capacity quantity The number of the units used to measure the usage of a Red Hat product, such as 2 Sockets. Contract number The 8-digit number that uniquely identifies the contract that the subscription is purchased under, such as 16521599. Quantity The number of active subscriptions for a SKU, such as 1000. Start date The date that the subscription became active based on the terms of the contract, such as 2023-02-07. End date The date that the subscription expires based on the terms of the contract, such as 2024-02-06. Subscription status The availability status of your Red Hat product subscription, such as Active, Expired, Expiring soon, or Future dated. Prerequisites You are logged in to your Red Hat Hybrid Cloud Console account at console.redhat.com. You have the Subscriptions user role in the role-based access control (RBAC) system for the Red Hat Hybrid Cloud Console. Procedure To export your subscription inventory, complete the following steps: From the Home page, locate Red Hat Insights and click RHEL . From the Red Hat Insights menu, click Business > Subscriptions > Subscription Inventory . From the Subscriptions Inventory page, scroll to the All subscriptions table. From the All subscriptions table header, click the Export icon. Note The .csv filename follows the following format: subscription_inventory_yyyymmddThhmmssZ.csv . For example, if you export the CSV file on the last day of 2023 at the 19th hour of the day, the filename will be similar to subscription_inventory_20231231T192246Z.csv . Verification The exported CSV file is in your Downloads folder by default. Note If there are no valid subscriptions in your inventory, then the exported CSV file will contain no data.

Commands:
Chapter 1. Red Hat JBoss Web Server 6.0 Service Pack 2 Welcome to the Red Hat JBoss Web Server version 6.0 Service Pack 2 release. Red Hat JBoss Web Server is a fully integrated and certified set of components for hosting Java web applications. It consists of an application server (Apache Tomcat servlet container) and the Apache Tomcat Native Library. JBoss Web Server includes the following key components: Apache Tomcat is a servlet container in accordance with the Java Servlet Specification. JBoss Web Server contains Apache Tomcat 10.1. The Apache Tomcat Native Library improves Tomcat scalability, performance, and integration with native server technologies. Tomcat-vault is an extension for the JBoss Web Server that is used for securely storing passwords and other sensitive information used by a JBoss Web Server. The mod_cluster library enables communication between JBoss Web Server and the Apache HTTP Server mod_proxy_cluster module. The mod_cluster library enables you to use the Apache HTTP Server as a load balancer for JBoss Web Server. For more information about configuring mod_cluster , or for information about installing and configuring alternative load balancers such as mod_jk and mod_proxy , see the Apache HTTP Server Connectors and Load Balancing Guide . Apache portable runtime (APR) is a runtime that provides an OpenSSL-based TLS implementation for the HTTP connectors. JBoss Web Server provides a distribution of APR for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the APR package that the operating system provides. OpenSSL is a software library that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols and includes a basic cryptographic library. JBoss Web Server provides a distribution of OpenSSL for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the OpenSSL package that the operating system provides. This release of JBoss Web Server includes some important security updates. This release of JBoss Web Server provides OpenShift images based on Red Hat Enterprise Linux 8.

Commands:
8.171. rdesktop 8.171.1. RHBA-2013:1556 - rdesktop bug fix and enhancement update Updated rdesktop packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The rdesktop package is an open source client for Windows NT Terminal Server and Windows 2000 & 2003 Terminal Services, capable of natively speaking Remote Desktop Protocol (RDP) in order to present the user's NT desktop. Note The rdesktop package has been upgraded to upstream version 1.7.0., which provides a number of bug fixes and enhancements over the version, including fixes for incorrect cursor and scrollbar rendering. (BZ# 852890 , BZ# 914279 ) Bug Fix BZ# 902912 Due to a bug in the rdesktop code, error messages were continuously displayed in the shell while rdesktop was used. This bug has been fixed and messages are no longer generated during an rdesktop session. Enhancement BZ# 701246 With this update, support for Terminal Services on clustered Windows Server 2008 R2 machines has been added to the rdesktop package. Users of rdesktop are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
2.2. Threats to Network Security Bad practices when configuring the following aspects of a network can increase the risk of attack. 2.2.1. Insecure Architectures A misconfigured network is a primary entry point for unauthorized users. Leaving a trust-based, open local network vulnerable to the highly-insecure Internet is much like leaving a door ajar in a crime-ridden neighborhood - nothing may happen for an arbitrary amount of time, but eventually someone exploits the opportunity. 2.2.1.1. Broadcast Networks System administrators often fail to realize the importance of networking hardware in their security schemes. Simple hardware such as hubs and routers rely on the broadcast or non-switched principle; that is, whenever a node transmits data across the network to a recipient node, the hub or router sends a broadcast of the data packets until the recipient node receives and processes the data. This method is the most vulnerable to address resolution protocol ( arp ) or media access control ( MAC ) address spoofing by both outside intruders and unauthorized users on local hosts. 2.2.1.2. Centralized Servers Another potential networking pitfall is the use of centralized computing. A common cost-cutting measure for many businesses is to consolidate all services to a single powerful machine. This can be convenient as it is easier to manage and costs considerably less than multiple-server configurations. However, a centralized server introduces a single point of failure on the network. If the central server is compromised, it may render the network completely useless or worse, prone to data manipulation or theft. In these situations, a central server becomes an open door which allows access to the entire network.

Commands:
Chapter 15. Fixed issues in Red Hat Process Automation Manager 7.13.4 Red Hat Process Automation Manager 7.13.4 provides increased stability and fixed issues listed in this section. 15.1. Business Central Dashbuilder does not support the type MILLISECOND [ RHPAM-4659 ] Standalone Business Central does not start on Red Hat Enterprise Linux (RHEL) [ RHPAM-4715 ] Data filter is not working as expected [ RHPAM-4664 ] 15.2. Process engine You cannot updated the service-level agreement (SLA) because of the date of process instance [ RHPAM-4752 ] Scheduled jobs do not keep configured execution time [ RHPAM-4750 ] PIM removes dynamic task descriptions of human tasks [ RHPAM-4749 ] Processes with timers that have different config and async tasks are triggered at same time using the PER_REQUEST runtime strategy [ RHPAM-4703 ] The EJB timer throws the SessionNotFoundException exception even after the sub process and parent process successfully completes [ RHPAM-4610 ] 15.3. KIE Server The ClassNotFoundException occurs when launching a business application with the command mvn spring-boot:run [ RHDM-1984 ] Behavior of the ClassCastException exception changed after RHPAM 7.13.0 for empty values in the request [ RHPAM-4725 ] The NoSuchMethodError occurs when retrieving Kie server information on SpringBoot [ RHPAM-4714 ] The productized cxf-rt-bindings-soap dependency in kie-camel is invalid [ RHPAM-4683 ] The NullPointerException (NPE) occurs on TupleSetsImpl.setNextTuple with SubnetworkTuple [ RHDM-1968 ] 15.4. Red Hat OpenShift Container Platform Upgrade JBoss Enterprise Application Server to 7.4.12 on RHPAM and BAMOE images [ RHPAM-4762 ] Unable to set direct-verification=true individually in LDAP realm by operator [ RHPAM-4754 ] Unable to connect to an external PostgreSQL database over SSL from kie-server on OpenShift Container Platform [ RHPAM-4740 ] Do not set URL envs if the jdbcUrl property is not set [ RHPAM-4713 ] Legacy datasource scripts do not consider XA properties for the mariadb driver [ RHPAM-4712 ] Correctly set the XA Connection URL property [ RHPAM-4711 ] KIE Server configMap points to SSL routes when SSL is disabled [ RHPAM-4709 ] Can't login into Business Central without SSL configured [ RHPAM-4705 ] NoSuchMethodException : Method setURL not found [ RHPAM-4704 ] The pom.xml file in rhpam-7-openshift-image/quickstarts/router-ext contains the wrong version [ RHPAM-4682 ] 15.5. Decision engine Unnecessary warning message appears when executing a DRL file [ RHPAM-4758 ] The NullPointerException error occurs in MemoryFileSystem when kbase.name is empty in kmodule.xml [ RHPAM-4755 ] With a non-executable model and the mvel dialect, when the modify-block is placed inside a block such as the if-block in RHS, the modify does not work correctly [ RHDM-1985 ] After upgrading to 7.13.2, rules fire incorrectly when BigDecimal equality is involved in a pattern [ RHDM-1974 ] The executable model doesn't resolve bind variables from another pattern of the same type in method call in LHS for property reactivity [ RHDM-1969 ] The executable model doesn't resolve bind variables in a method call in LHS for property reactivity [ RHDM-1967 ]

Commands: