mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 5. Monitoring CodeReady Workspaces This chapter describes how to configure CodeReady Workspaces to expose metrics and how to build an example monitoring stack with external tools to process data exposed as metrics by CodeReady Workspaces. 5.1. Enabling and exposing CodeReady Workspaces metrics This section describes how to enable and expose CodeReady Workspaces metrics. Procedure Set the CHE_METRICS_ENABLED=true environment variable, which will expose the 8087 port as a service on the che-master host. When Red Hat CodeReady Workspaces is installed from the OperatorHub, the environment variable is set automatically if the default CheCluster CR is used: spec: metrics: enable: true 5.2. Collecting CodeReady Workspaces metrics with Prometheus This section describes how to use the Prometheus monitoring system to collect, store, and query metrics about CodeReady Workspaces. Prerequisites CodeReady Workspaces is exposing metrics on port 8087 . See Enabling and exposing CodeReady Workspaces metrics . Prometheus 2.9.1 or later is running. The Prometheus console is running on port 9090 with a corresponding service and route . See First steps with Prometheus . Procedure Configure Prometheus to scrape metrics from the 8087 port: Example 5.1. Prometheus configuration example apiVersion: v1 kind: ConfigMap metadata: name: prometheus-config data: prometheus.yml: |- global: scrape_interval: 5s 1 evaluation_interval: 5s 2 scrape_configs: 3 - job_name: 'che' static_configs: - targets: ['[che-host]:8087'] 4 1 Rate, at which a target is scraped. 2 Rate, at which recording and alerting rules are re-checked (not used in the system at the moment). 3 Resources Prometheus monitors. In the default configuration, a single job called che , scrapes the time series data exposed by the CodeReady Workspaces server. 4 Scrape metrics from the 8087 port. Verification steps Use the Prometheus console to query and view metrics. Metrics are available at: http:// <che-server-url> :9090/metrics . For more information, see Using the expression browser . Additional resources First steps with Prometheus . Configuring Prometheus . Querying Prometheus . Prometheus metric types .

Commands:
spec: metrics: enable: true
apiVersion: v1 kind: ConfigMap metadata: name: prometheus-config data: prometheus.yml: |- global: scrape_interval: 5s 1 evaluation_interval: 5s 2 scrape_configs: 3 - job_name: 'che' static_configs: - targets: ['[che-host]:8087'] 4
11.4. Table Options You can use the following options when creating a table or view. See "create table body" in Section A.7, "Productions" . Any others properties defined will be considered as extension metadata. Property Data Type or Allowed Values Description UUID string This is the unique identifier for a view. MATERIALIZED 'TRUE'|'FALSE' This is applicable to views only. It defines if a table is materialized. MATERIALIZED_TABLE 'table.name' This is applicable to views only. If this view is being materialized to a external database, this defines the name of the table that is being materialized. CARDINALITY int Costing information. Number of rows in the table. Used for planning purposes UPDATABLE 'TRUE'|'FALSE' Defines if the view is allowed to update or not ANNOTATION string Description of the view

Commands:
Chapter 4. Models 4.1. Guiding through the process To make the process of using Teiid Designer to build models more as easy as posssible, a guides view (See Section D.19, "Guides View" ) has been introduced. It provides action sets which bring together the actions necessary to develop models for specific use-cases. Action sets are available for the following scenarios: Consuming a SOAP Web Service Modelling from a Flat File Source (a text file) Modelling from a JDBC Data Source Modelling from a Local XML File Source Modelling from a Remote XML File Source Modelling from a Red Hat JBoss Data Virtualization Data Source (deployed on server) Connecting to a Red Hat JBoss Data Virtualization Server Creating a REST WAR

Commands:
Preface The Red Hat build of Cryostat is a container-native implementation of JDK Flight Recorder (JFR) that you can use to securely monitor the Java Virtual Machine (JVM) performance in workloads that run on an OpenShift Container Platform cluster. You can use Cryostat 3.0 to start, stop, retrieve, archive, import, and export JFR data for JVMs inside your containerized applications by using a web console or an HTTP API. Depending on your use case, you can store and analyze your recordings directly on your Red Hat OpenShift cluster by using the built-in tools that Cryostat provides or you can export recordings to an external monitoring application to perform a more in-depth analysis of your recorded data. Important Red Hat build of Cryostat is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope .

Commands:
Chapter 8. Assisted installer certification tests The assisted installer tests ensure that the HUT can be installed successfully by using the assisted installer for Red Hat OpenShift Container Platform. The tests verify single-node clusters only. If you want to certify multiple bare-metal servers, you must install each of them as a single-node cluster. The following RHEL and RHOCP combinations are supported: RHEL 9.2 or 9.4 with RHOCP 4.13, 4.14, or 4.15 The test plan consists on the following tests: 8.1. Self check test The self-check test confirms that all required software packages for certification are installed and unaltered, ensuring the test environment is ready for certification. Certification packages must not be modified for testing or any other purpose. Success Criteria The test environment includes all necessary certification packages and the packages have not been modified. 8.2. Assisted installer test The assisted installer test queries the assisted installer APIs to collect basic information about the assisted installer and the HUT cluster. Before you run the test, generate an OpenShift Manager API token and export it as the value of the OFFLINE_TOKEN variable. For example: The test will prompt for the cluster ID if unable to determine it. Success Criteria The test connects to the assisted installer APIs and collects the information successfully. 8.3. Sosreport test The Sosreport test connects to the HUT cluster and collects information about the cluster's hardware and configuration. The sos_reports/manifest.json file contains details about node hostnames and the commands run by this test. Success Criteria The test correctly collects the information from the Single node OpenShift (SNO) cluster's master node. 8.4. Cluster inspection test The cluster inspection test invokes the Cloud-native Network Function (CNF) test. It is a backlog test and is available only in the preview mode. Additional resources For more information about assisted installer tests, see Running the assisted installer tests .

Commands:
export OFFLINE_TOKEN=<value_of_your_token>
Chapter 1. Backup and recovery of Red Hat Ansible Automation Platform To safeguard against unexpected data loss and application errors, it is critical that you perform periodic backups of your Red Hat Ansible Automation Platform deployment. In addition to data loss prevention, backups allow you to fall back to a different deployment state. 1.1. About backup and recovery Red Hat recommends backing up deployments of Red Hat Ansible Automation Platform in your Red Hat OpenShift Container Platform environment to prevent data loss. A backup resource of your Red Hat Ansible Automation Platform deployment includes the following: Custom deployment of specific values in the spec section of the {PlatormNameShort} custom resource object Back up of the postgresql database secret_key , admin_password , and broadcast_websocket secrets Database configuration Note Be sure to secure your backup resources because they can include sensitive information. 1.1.1. Backup recommendations Recovering from data loss requires that you plan for and create backup resources of your Red Hat Ansible Automation Platform deployments on a regular basis. At a minimum, Red Hat recommends backing up deployments of Red Hat Ansible Automation Platform under the following circumstances: Before upgrading your Red Hat Ansible Automation Platform deployments Before upgrading your Openshift cluster Once per week. This is particularly important if your environment is configured for automatic upgrades.

Commands:
4.306. star 4.306.1. RHBA-2011:0932 - star bug fix update An updated star package that fixes one bug is now available for Red Hat Enterprise Linux 6. The star utility is a tape- and disk-archiving tool similar to tar that supports saving Access Control List (ACLs) permission information. Bug Fix BZ# 611402 Under certain circumstances, the star utility could have terminated unexpectedly with a segmentation fault when used with a file which name was exactly 100 characters long. This segmentation fault has been fixed in this update and no longer occurs. All users of star are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 2. Setting Mission Control for Red Hat build of OpenJDK 11 for Microsoft Windows This procedure describe how to install and set Mission Control for Red Hat build of OpenJDK 11 for Microsoft Windows. Prerequisites Red Hat build of OpenJDK 11 for Microsoft Windows is installed on the system. Procedure Extract the archive. In the Mission Control directory, open the JMC client executable file. On the command line, start the JMC lient by entering jmc or the the full path to the JMC executable. On the JMC Client screen, create a new connection from the File menu, choose your JVM, and start JMX console. As the result you should be getting an overview page with Processors, Memory consumption, Java heap use, JVM CPU usage, etc.

Commands:
JAVA_HOME\missioncontrol\jmc.exe
Chapter 93. ZipArtifact schema reference Used in: Plugin Property Property type Description url string URL of the artifact which will be downloaded. Streams for Apache Kafka does not do any security scanning of the downloaded artifacts. For security reasons, you should first verify the artifacts manually and configure the checksum verification to make sure the same artifact is used in the automated build. Required for jar , zip , tgz and other artifacts. Not applicable to the maven artifact type. sha512sum string SHA512 checksum of the artifact. Optional. If specified, the checksum will be verified while building the new container. If not specified, the downloaded artifact will not be verified. Not applicable to the maven artifact type. insecure boolean By default, connections using TLS are verified to check they are secure. The server certificate used must be valid, trusted, and contain the server name. By setting this option to true , all TLS verification is disabled and the artifact will be downloaded, even when the server is considered insecure. type string Must be zip .

Commands:
7.61. ghostscript 7.61.1. RHBA-2015:1343 - ghostscript bug fix update Updated ghostscript packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The Ghostscript suite contains utilities for rendering PostScript and PDF documents. Ghostscript translates PostScript code to common, bitmap formats so that the code can be displayed or printed. Bug Fixes BZ# 994452 Previously, a text intended for rendering in mode 3 (invisible) was not included in the PDF output of the pdfwrite device. As a consequence, text selection from documents with an invisible text, such as Optical character recognition (OCR) output, failed. With this update, mode 3 text is included in the PDF output, and copying a text from such PDF files now works as expected. BZ# 1027534 Prior to this update, some PDF files containing embedded objects were erroneously treated as portable collections, leading to a "/syntaxerror" error when processing these files. A fix has been applied so that only PDF files with "/Collection" attributes are treated as portable collections, and files with embedded objects are now processed correctly. BZ# 1060026 Correct PDF/A files could not be created due to a lack of support. This update backports improved support for creating PDF/A files from upstream, and correct PDF/A files can now be produced. BZ# 1105520 Previously, if an error occurred in the ghostscript interpreter in between allocating an array and initializing its contents, garbage collection could cause the interpreter to terminate unexpectedly while attempting to deallocate memory. A patch from upstream which immediately sets the array elements to null objects after allocation fixes this bug, and the ghostscript interpreter no longer crashes in the described scenario. Users of ghostscript are advised to upgrade to these updated packages, which fix these bugs.

Commands:
1.4. About Authorization Authorization is a mechanism for granting or denying access to a resource based on identity. It is implemented as a set of declarative security roles which can be added to principals. JBoss EAP 6 uses a modular system to configure authorization. Each security domain may contain one or more authorization policies. Each policy has a basic module which defines its behavior. It is configured through specific flags and attributes. The easiest way to configure the authorization subsystem is by using the web-based management console. Authorization is different from authentication, and usually happens after authentication. Many of the authentication modules also handle authorization.

Commands:
Chapter 23. Policy: Group Policy Object Access Control Group Policy is a Microsoft Windows feature that enables administrators to centrally manage policies for users and computers in AD environments. A group policy object (GPO) is a collection of policy settings, such as name and value pairs, that are stored on a domain controller (DC) and can be applied to policy targets, such as computers and users. GPO policy settings related to Windows logon rights are commonly used to manage computer-based access control in AD environments. SSSD can retrieve GPOs applicable to host systems and AD users; based on the retrieved GPO configuration, it determines if a user is allowed to log on to a particular host. Therefore, with the GPO-based access control provided by SSSD, the administrator can define login policies that are honored by both Red Hat Enterprise Linux and Windows clients centrally on the AD DC. Note SSSD only allows using GPO for the computer-based access control. Other GPO-related access control options are currently not supported. Warning Note that SSSD only handles rules that apply to a whole site, domain, or AD organizational unit (OU). If you want to apply the SSSD-supported GPO-based access control to a specific machine, you can create a new OU in the AD domain, move the machine to the OU, and then link the GPO to this OU. 23.1. Configuring GPO-Based Access Control GPO-based access control can be configured in the /etc/sssd/sssd.conf file. The ad_gpo_access_control option specifies the mode in which the GPO-based access control runs. It can be set to the following values: ad_gpo_access_control = permissive The permissive value specifies that GPO-based access control is evaluated but not enforced; a syslog message is recorded every time access would be denied. This is the default setting. ad_gpo_access_control = enforcing The enforcing value specifies that GPO-based access control is evaluated and enforced. ad_gpo_access_control = disabled The disabled value specifies that GPO-based access control is neither evaluated nor enforced. Important Before starting to use the GPO-based access control and setting ad_gpo_access_control to enforcing mode, it is recommended to ensure that ad_gpo_access_control is set to permissive mode and examine the logs. By reviewing the syslog messages, you can test and adjust the current GPO settings as necessary before finally setting the enforcing mode. The following parameters related to the GPO-based access control can also be specified in the sssd.conf file: The ad_gpo_map_* options and the ad_gpo_default_right option configure which PAM services are mapped to specific Windows logon rights. The ad_gpo_cache_timeout option specifies the interval during which subsequent access control requests can reuse the files stored in the cache, instead of retrieving them from the DC anew. For a detailed list of available GPO parameters as well as their descriptions and default values, see the sssd-ad (5) man page.

Commands:
3.2. Configuring IP Networking with nmtui As a system administrator, you can configure a network interface using the NetworkManager's tool, nmtui . See Section 2.5, "NetworkManager Tools" . This procedure describes how to configure networking using the text user interface tool, nmtui . Prerequisites The nmtui tool is used in a terminal window. It is contained in the NetworkManager-tui package, but it is not installed along with NetworkManager by default. To install NetworkManager-tui : To verify that NetworkManager is running, see Section 2.3, "Checking the Status of NetworkManager" . Procedure Start the nmtui tool: The text user interface appears. Figure 3.1. The NetworkManager Text User Interface starting menu To navigate, use the arrow keys or press Tab to step forwards and press Shift + Tab to step back through the options. Press Enter to select an option. The Space bar toggles the status of a check box. To apply changes after a modified connection which is already active requires a reactivation of the connection. In this case, follow the procedure below: Procedure Select the Activate a connection menu entry. Figure 3.2. Activate a Connection Select the modified connection. On the right, click the Deactivate button. Figure 3.3. Deactivate the Modified Connection Choose the connection again and click the Activate button. Figure 3.4. Reactivate the Modified Connection The following commands are also available: nmtui edit connection-name If no connection name is supplied, the selection menu appears. If the connection name is supplied and correctly identified, the relevant Edit connection screen appears. nmtui connect connection-name If no connection name is supplied, the selection menu appears. If the connection name is supplied and correctly identified, the relevant connection is activated. Any invalid command prints a usage message. Note that nmtui does not support all types of connections. In particular, you cannot edit VPNs, wireless network connections using WPA Enterprise, or Ethernet connections using 802.1X .

Commands:
~]# yum install NetworkManager-tui
~]USD nmtui
4.2.2. Normal scheduling policies There are three normal scheduling policies: SCHED_OTHER , SCHED_BATCH and SCHED_IDLE . However, the SCHED_BATCH and SCHED_IDLE policies are intended for very low priority jobs, and as such are of limited interest in a performance tuning guide. SCHED_OTHER , or SCHED_NORMAL The default scheduling policy. This policy uses the Completely Fair Scheduler (CFS) to provide fair access periods for all threads using this policy. CFS establishes a dynamic priority list partly based on the niceness value of each process thread. (Refer to the Deployment Guide for more details about this parameter and the /proc file system.) This gives users some indirect level of control over process priority, but the dynamic priority list can only be directly changed by the CFS.

Commands:
Chapter 22. Hardware Enablement Runtime Instrumentation for IBM System z Support for the Runtime Instrumentation feature is available as a Technology Preview in Red Hat Enterprise Linux 7.2 on IBM System z. Runtime Instrumentation enables advanced analysis and execution for a number of user-space applications available with the IBM zEnterprise EC12 system. LSI Syncro CS HA-DAS adapters Red Hat Enterprise Linux 7.1 included code in the megaraid_sas driver to enable LSI Syncro CS high-availability direct-attached storage (HA-DAS) adapters. While the megaraid_sas driver is fully supported for previously enabled adapters, the use of this driver for Syncro CS is available as a Technology Preview. Support for this adapter is provided directly by LSI, your system integrator, or system vendor. Users deploying Syncro CS on Red Hat Enterprise Linux 7.2 are encouraged to provide feedback to Red Hat and LSI. For more information on LSI Syncro CS solutions, please visit http://www.lsi.com/products/shared-das/pages/default.aspx .

Commands:
8.75. gpxe 8.75.1. RHBA-2014:1574 - gpxe bug fix update An updated gpxe package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The gpxe package provides gPXE, an open source Pre-boot Execution Environment (PXE) implementation and boot loader. Bug Fixes BZ# 1057249 The PXE booting did not respect the specified boot order when multiple NICs of the same type were configured for a virtual machine. Instead, the gPXE image attempted to boot from all NICs supported by the loaded image in the PCI bus scan order. This resulted in boot delays, attempting to perform a PXE boot on unintended devices, as well as in booting from unintended devices in case of success. This update provides the gPXE boot image with the PCI address of the intended boot device, ensuring that the image only attempts to boot on the intended device. BZ# 1105189 HTTP requests generated by gPXE set wrong TCP flag (SYN & PSH) in the first packet of a session. Consequently, when using a firewall, the TCP packet flow would be blocked and the HTTP module integrated with gPXE would not work. With this update, gPXE no longer set the PSH flag in the first packet of a session and the system now boots as expected. Users of gpxe are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Chapter 9. Using the Ceph block device Python module The rbd python module provides file-like access to Ceph block device images. In order to use this built-in tool, import the rbd and rados Python modules. Prerequisites A running Red Hat Ceph Storage cluster. Root-level access to the node. Procedure Connect to RADOS and open an IO context: cluster = rados.Rados(conffile='my_ceph.conf') cluster.connect() ioctx = cluster.open_ioctx('mypool') Instantiate an :class:rbd.RBD object, which you use to create the image: To perform I/O on the image, instantiate an :class:rbd.Image object: This writes 'foo' to the first 600 bytes of the image. Note that data cannot be :type:unicode - librbd does not know how to deal with characters wider than a :c:type:char . Close the image, the IO context and the connection to RADOS: To be safe, each of these calls must to be in a separate :finally block: This can be cumbersome, so the Rados , Ioctx , and Image classes can be used as context managers that close or shut down automatically. Using them as context managers, the above example becomes:

Commands:
cluster = rados.Rados(conffile='my_ceph.conf') cluster.connect() ioctx = cluster.open_ioctx('mypool')
rbd_inst = rbd.RBD() size = 4 * 1024**3 # 4 GiB rbd_inst.create(ioctx, 'myimage', size)
image = rbd.Image(ioctx, 'myimage') data = 'foo' * 200 image.write(data, 0)
image.close() ioctx.close() cluster.shutdown()
import rados import rbd cluster = rados.Rados(conffile='my_ceph_conf') try: ioctx = cluster.open_ioctx('my_pool') try: rbd_inst = rbd.RBD() size = 4 * 1024**3 # 4 GiB rbd_inst.create(ioctx, 'myimage', size) image = rbd.Image(ioctx, 'myimage') try: data = 'foo' * 200 image.write(data, 0) finally: image.close() finally: ioctx.close() finally: cluster.shutdown()
with rados.Rados(conffile='my_ceph.conf') as cluster: with cluster.open_ioctx('mypool') as ioctx: rbd_inst = rbd.RBD() size = 4 * 1024**3 # 4 GiB rbd_inst.create(ioctx, 'myimage', size) with rbd.Image(ioctx, 'myimage') as image: data = 'foo' * 200 image.write(data, 0)