mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 34. Configuring Maven using settings.xml file Java application development uses the Apache Maven build automation tool to build and manage software projects. Maven uses Project Object Model (POM) configuration XML files to define both, the project properties and the build process. Maven uses repositories to store Java libraries, plug-ins, and other build artifacts. Repositories can be either local or remote. A local repository is a download of artifacts from a remote repository cached on a local machine. A remote repository is any other repository accessed using common protocols, such as http:// when located on an HTTP server, or file:// when located on a file server. The default repository is the public remote Maven 2 Central Repository. Configuration of Maven is performed by modifying the settings.xml file. You can either configure global Maven settings in the M2_HOME/conf/settings.xml file, or user-level settings in the USER_HOME/.m2/settings.xml file. Additional resources Configuring an external Maven repository for Business Central and KIE Server Packaging and deploying a Red Hat Decision Manager project in Maven Maven settings and repositories for Red Hat Decision Manager System integration with Maven Welcome to Apache Maven Apache Maven Project - Introduction to Repositories Apache Maven Parent POMs Reference .

Commands:
5.93. gnome-system-monitor 5.93.1. RHBA-2012:0769 - gnome-system-monitor bug fix update An updated gnome-system-monitor package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The gnome-system-monitor utility allows users to graphically view and manipulate the running processes on the system, and provides an overview of available resources such as CPU and memory. Bug Fixes BZ# 682011 Prior to this update, the gnome-system-monitor failed to correctly parse the contents of the /proc/cpuinfo file if it included an informational entry about the machine model on 64-bit PowerPC architectures. As a consequence, a false "Unknown CPU model" processor was incorrectly reported by the application. This update changes the parsing code to discard such information when it does not identify an additional processor. BZ# 692956 Prior to this update, the gnome-system-monitor parser code expected a certain string to identify the CPU speed which is not used for all architectures. As a consequence, the gnome-system-monitor could fail to correctly parse the processor speed from /proc/cpuinfo when a different string was used, for example on 64-bit PowerPC. This update changes the parsing code to support different string types used on such architectures. All users of gnome-system-monitor are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Chapter 12. Creating a kernel-based virtual machine and booting the installation ISO in the VM You can create a kernel-based virtual machine (KVM) and start the Red Hat Enterprise Linux installation. The following instructions are specific for installation on a VM. If you are installing RHEL on a physical system, you can skip this section. Procedure Create a virtual machine with the instance of Red Hat Enterprise Linux as a KVM guest operating system, by using the following virt-install command on the KVM host: Additional resources virt-install man page on your system Creating virtual machines by using the command-line interface

Commands:
virt-install --name=<guest_name> --disk size=<disksize_in_GB> --memory=<memory_size_in_MB> --cdrom <filepath_to_iso> --graphics vnc
Chapter 13. Allowing JavaScript-based access to the API server from additional hosts 13.1. Allowing JavaScript-based access to the API server from additional hosts The default OpenShift Container Platform configuration only allows the web console to send requests to the API server. If you need to access the API server or OAuth server from a JavaScript application using a different hostname, you can configure additional hostnames to allow. Prerequisites Access to the cluster as a user with the cluster-admin role. Procedure Edit the APIServer resource: USD oc edit apiserver.config.openshift.io cluster Add the additionalCORSAllowedOrigins field under the spec section and specify one or more additional hostnames: apiVersion: config.openshift.io/v1 kind: APIServer metadata: annotations: release.openshift.io/create-only: "true" creationTimestamp: "2019-07-11T17:35:37Z" generation: 1 name: cluster resourceVersion: "907" selfLink: /apis/config.openshift.io/v1/apiservers/cluster uid: 4b45a8dd-a402-11e9-91ec-0219944e0696 spec: additionalCORSAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) 1 1 The hostname is specified as a Golang regular expression that matches against CORS headers from HTTP requests against the API server and OAuth server. Note This example uses the following syntax: The (?i) makes it case-insensitive. The // pins to the beginning of the domain and matches the double slash following http: or https: . The \. escapes dots in the domain name. The (:|\z) matches the end of the domain name (\z) or a port separator (:) . Save the file to apply the changes.

Commands:
oc edit apiserver.config.openshift.io cluster
apiVersion: config.openshift.io/v1 kind: APIServer metadata: annotations: release.openshift.io/create-only: "true" creationTimestamp: "2019-07-11T17:35:37Z" generation: 1 name: cluster resourceVersion: "907" selfLink: /apis/config.openshift.io/v1/apiservers/cluster uid: 4b45a8dd-a402-11e9-91ec-0219944e0696 spec: additionalCORSAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) 1
Chapter 4. Networking dashboards Networking metrics are viewable in dashboards within the OpenShift Container Platform web console, under Observe Dashboards . 4.1. Network Observability Operator If you have the Network Observability Operator installed, you can view network traffic metrics dashboards by selecting the Netobserv dashboard from the Dashboards drop-down list. For more information about metrics available in this Dashboard , see Network Observability metrics dashboards . 4.2. Networking and OVN-Kubernetes dashboard You can view both general networking metrics as well as OVN-Kubernetes metrics from the dashboard. To view general networking metrics, select Networking/Linux Subsystem Stats from the Dashboards drop-down list. You can view the following networking metrics from the dashboard: Network Utilisation , Network Saturation , and Network Errors . To view OVN-Kubernetes metrics select Networking/Infrastructure from the Dashboards drop-down list. You can view the following OVN-Kuberenetes metrics: Networking Configuration , TCP Latency Probes , Control Plane Resources , and Worker Resources . 4.3. Ingress Operator dashboard You can view networking metrics handled by the Ingress Operator from the dashboard. This includes metrics like the following: Incoming and outgoing bandwidth HTTP error rates HTTP server response latency To view these Ingress metrics, select Networking/Ingress from the Dashboards drop-down list. You can view Ingress metrics for the following categories: Top 10 Per Route , Top 10 Per Namespace , and Top 10 Per Shard .

Commands:
Chapter 2. Upgrading a host operating system from RHEL 8 to RHEL 9 You can perform a Red Hat Ceph Storage host operating system upgrade from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 using the Leapp utility. Prerequisites A running Red Hat Ceph Storage 5.3 cluster. The following are the supported combinations of containerized Ceph daemons. For more information, see the How colocation works and its advantages section in the Red Hat Ceph Storage Installation Guide . Ceph Metadata Server ( ceph-mds ), Ceph OSD ( ceph-osd ), and Ceph Object Gateway ( radosgw ) Ceph Monitor ( ceph-mon ) or Ceph Manager ( ceph-mgr ), Ceph OSD ( ceph-osd ), and Ceph Object Gateway ( radosgw ) Ceph Monitor ( ceph-mon ), Ceph Manager ( ceph-mgr ), Ceph OSD ( ceph-osd ), and Ceph Object Gateway ( radosgw ) Procedure Deploy Red Hat Ceph Storage 5.3 on Red Hat Enterprise Linux 8.8 with service. Note Verify that the cluster contains two admin nodes, so that while performing host upgrade in one admin node (with _admin label), the second admin can be used for managing clusters. For full instructions, see Red Hat Ceph Storage installation in the Red Hat Ceph Storage Installation Guide and Deploying the Ceph daemons using the service specifications in the Operations guide . Set the noout flag on the Ceph OSD. Example Perform host upgrade one node at a time using the Leapp utility. Put respective node maintenance mode before performing host upgrade using Leapp. Syntax Example Enable the ceph tools repo manually when executing the leapp command with the --enablerepo parameter. Example Refer to Upgrading RHEL 8 to RHEL 9 within the Red Hat Enterprise Linux product documentation on the Red Hat Customer Portal. Important After performing in-place upgrade from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9, you need to manually enable and start the logrotate.timer service. Verify the new IMAGE_ID and VERSION of the Ceph cluster: Example Continue with the Red Hat Ceph Storage 5.3 to Red Hat Ceph Storage 8 upgrade by following the Upgrading the Red Hat Ceph Storage cluster steps in the Red Hat Ceph Storage Upgrade Guide .

Commands:
ceph osd set noout
ceph orch host maintenance enter HOST
ceph orch host maintenance enter host01
leapp upgrade --enablerepo rhceph-5-tools-for-rhel-9-x86_64-rpms
systemctl start logrotate.timer systemctl enable logrotate.timer
ceph version ceph orch ps
Chapter 3. Resilient and non-resilient data pools What are resilient pools and a non-resilient pools? A resilient data pool enables data to replicate or encode its data. The non-resilient data pool does not enable to replicate or encode its data. A non-resilient pool is also called replica1 , and is not protected from data loss. A small cluster with non-resilient data pools does its own replication and does not need replication from Red Hat Ceph Storage as it does its own replication. Cluster utilization with data pools With smaller configurations, the cluster utilization reduces because of the loss of resiliency. The recovery is limited by host utilization and might potentially impact production input/output operations per second (IOPS). When there is a single node of failure, you can add a third node to limit the host utilization and for Red Hat Ceph Storage to recover to full replication.

Commands:
Chapter 3. Use conventions in the API Automation controller uses a standard REST API, rooted at /api/ on the server. The API is versioned for compatibility reasons. You can see what API versions are available by querying /api/ . You might have to specify the content or type on POST or PUT requests: PUT : Update a specific resource (by an identifier) or a collection of resources. You can also use PUT to create a specific resource if you know the resource identifier before-hand. POST : Create a new resource. Also acts as a catch-all verb for operations that do not fit into the other categories. All URIs not ending with "/" receive a 301 redirect. Note The formatting of extra_vars attached to Job Template records is preserved. YAML is returned as YAML with formatting and comments preserved, and JSON is returned as JSON.

Commands:
23.2.4. DHCP Relay Agent The DHCP Relay Agent ( dhcrelay ) allows for the relay of DHCP and BOOTP requests from a subnet with no DHCP server on it to one or more DHCP servers on other subnets. When a DHCP client requests information, the DHCP Relay Agent forwards the request to the list of DHCP servers specified when the DHCP Relay Agent is started. When a DHCP server returns a reply, the reply is broadcast or unicast on the network that sent the original request. The DHCP Relay Agent listens for DHCP requests on all interfaces unless the interfaces are specified in /etc/sysconfig/dhcrelay with the INTERFACES directive. To start the DHCP Relay Agent, use the command service dhcrelay start .

Commands:
8.69. glib2 8.69.1. RHBA-2014:1538 - glib2 bug fix and enhancement update Updated glib2 packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. GLib is a low-level core library that forms the basis for projects such as GTK+ and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system. Note The glib2 packages have been upgraded to upstream version 2.28.8, which provides a number of bug fixes and enhancements over the version. (BZ# 1101398 ) Users of glib2 are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
probe::signal.checkperm Name probe::signal.checkperm - Check being performed on a sent signal Synopsis signal.checkperm Values pid_name Name of the process receiving the signal task A task handle to the signal recipient sig_name A string representation of the signal sinfo The address of the siginfo structure name Name of the probe point sig The number of the signal si_code Indicates the signal type sig_pid The PID of the process receiving the signal

Commands:
Chapter 16. Pluggable Authentication Modules (PAM) Programs which grant users access to a system verify each user's identity through a process called authentication . Historically, each such program had its own way of performing the task of authentication. Under Red Hat Enterprise Linux, many such programs are configured to use a centralized authentication mechanism called Pluggable Authentication Modules or PAM . PAM uses a pluggable, modular architecture, which affords the system administrator a great deal of flexibility in setting authentication policies for the system. In most situations, the default PAM configuration file for a PAM-aware application is sufficient. However, sometimes it may become necessary to edit a PAM configuration file. Because misconfiguration of PAM can compromise system security, it is important to understand the structure of these files before making any modifications (refer to Section 16.3, "PAM Configuration File Format" for more information). 16.1. Advantages of PAM PAM offers the following advantages: It provides a common authentication scheme that can be used with a wide variety of applications. It allows a large amount of flexibility and control over authentication for both system administrators and application developers. It allows application developers to develop programs without creating their own authentication scheme.

Commands:
Chapter 1. Migration to Red Hat build of OpenJDK 17 The Migrating to Red Hat build of OpenJDK 17 from earlier versions guide provides information on how to upgrade your Java applications in Red Hat build of OpenJDK version 8 or 11 to Red Hat build of OpenJDK 17. This guide describes changes in the Red Hat build of OpenJDK 17 release, including new features and deprecated or removed APIs, that might impact your migration from an earlier version of Red Hat build of OpenJDK. If you are migrating from Red Hat build of OpenJDK 8, this guide also describes the changes that were introduced in Red Hat build of OpenJDK 11. If you want to migrate from Red Hat build of OpenJDK 8, ensure that you also familiarize yourself with the major differences between versions 8 and 11 . The OpenJDK project is known for its conservative approach to providing updates and for providing backward compatibility. However, to guarantee the evolution, security and stability of the project, the Red Hat build of OpenJDK project might sometimes introduce a few incompatibilities across major releases of Red Hat build of OpenJDK. These incompatibilities are relevant for the following scenarios: When you use APIs that are considered obsolete or unsecure When you access internals of the project that are considered implementation details and not public or supported API details Note Red Hat recommends that you migrate to the latest supported Red Hat build of OpenJDK distribution. 1.1. About Red Hat build of OpenJDK distributions OpenJDK is the free and open source reference implementation of the Java Platform, Standard Edition (Java SE). Red Hat build of OpenJDK distributions are based on the upstream OpenJDK 8u, OpenJDK 11u, OpenJDK 17u, and OpenJDK 21u projects. The Shenandoah Garbage Collector is included in all supported versions of Red Hat build of OpenJDK. All versions of Red Hat build of OpenJDK provide the following benefits: Multi-platform Red Hat build of OpenJDK is supported on RHEL and Microsoft Windows, so you can standardize applications on a single Java platform across desktop, data center, and hybrid cloud environments. Frequent releases Red Hat delivers quarterly updates of JRE and JDK for Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, and Red Hat build of OpenJDK 21 distributions. These updates are available as archive, RPM, and Windows MSI-based installer files and container images. Long-term support Red Hat supports the recently released Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, and Red Hat build of OpenJDK 21 distributions. Additional resources For more information about the support lifecycle, see OpenJDK Life Cycle and Support Policy .

Commands:
5.2.24. /proc/partitions This file contains partition block allocation information. A sampling of this file from a basic system looks similar to the following: Most of the information here is of little importance to the user, except for the following columns: major - The major number of the device with this partition. The major number in the /proc/partitions , ( 3 ), corresponds with the block device ide0 , in /proc/devices . minor - The minor number of the device with this partition. This serves to separate the partitions into different physical devices and relates to the number at the end of the name of the partition. #blocks - Lists the number of physical disk blocks contained in a particular partition. name - The name of the partition.

Commands:
major minor #blocks name 3 0 19531250 hda 3 1 104391 hda1 3 2 19422585 hda2 253 0 22708224 dm-0 253 1 524288 dm-1
B.3. Adding a JBoss Dashboard Builder User A JBoss Dashboard Builder user is added in the same way as a JBoss Data Virtualization user. Two roles are provided for setting JBoss Dashboard Builder permissions: user - a user has permission to view the dashboard admin - a user has permission to modify the dashboard Important If a JBoss Dashboard Builder user wants their JBoss Data Virtualization permissions applied to the data they are accessing, then the external datasource defined in JBoss Dashboard Builder must use local connection and set PassthroughAuthentication to true on the URL; otherwise, the default username and password defined for the datasource are used. Example B.1. The PassthroughAuthentication property set on the connection URL

Commands:
jdbc:teiid: VDBName ;PassthroughAuthentication="true"
Chapter 11. Optional capabilities and products in the web console You can further customize the OpenShift Container Platform web console by adding additional capabilities to your existing workflows and integrations through products. 11.1. Enhancing the OpenShift Container Platform web console with Operators Cluster administrators can install Operators on clusters in the OpenShift Container Platform web console by using the OperatorHub to provide customization outside of layered products for developers. For example, the Web Terminal Operator allows you to start a web terminal in your browser with common CLI tools for interacting with the cluster. Additional resources Understanding OperatorHub Installing the web terminal 11.2. Red Hat OpenShift Pipelines in the web console Red Hat OpenShift Pipelines is a cloud-native, continuous integration and continuous delivery (CI/CD) solution based on Kubernetes resources. Install the Red Hat OpenShift Pipelines Operator using the OperatorHub in the OpenShift Container Platform web console. Once the Operator is installed, you can create and modify pipeline objects on Pipelines page. Additional resources Working with Red Hat OpenShift Pipelines in the web console Pipeline execution statistics in the web console 11.3. Red Hat OpenShift Serverless in the web console Red Hat OpenShift Serverless enables developers to create and deploy serverless, event-driven applications on OpenShift Container Platform. You can use the OpenShift Container Platform web console OperatorHub to install the OpenShift Serverless Operator. Additional resources Installing the OpenShift Serverless Operator from the web console . 11.4. Red Hat Developer Hub in the OpenShift Container Platform web console The Red Hat Developer Hub is a platform you can use to experience a streamlined development environment. Red Hat Developer Hub is driven by a centralized software catalog, providing efficiency to your microservices and infrastructure. It enables your product team to deliver quality code without any compromises. A quick start is available for you to learn more about how to install the developer hub. 11.4.1. Installing the Red Hat Developer Hub using the OpenShift Container Platform web console The web console provides a quick start with instructions on how to install the Red Hat Developer Hub Operator. Prerequisites You must be logged in to the OpenShift Container Platform web console with admin privileges. Procedure On the Overview page of the Administrator perspective, click Install Red Hat Developer Hub (RHDH) with an Operator in the Getting started resources tile. A quick start pane is displayed with instructions for you to install the Red Hat Developer Hub with an Operator. Follow the quick start for instructions on how to install the Operator, create a Red Hat Developer Hub instance, and add your instance to the OpenShift Console Application menu. Verification You can click the Application launcher link that is displayed to verify your Application tab is available. Verify your Janus IDP instance can be opened. Additional resources Product Documentation for Red Hat Developer Hub

Commands:
Appendix D. Additional Resources To learn more about virtualization and Red Hat Enterprise Linux, see the following resources. D.1. Online Resources http://www.libvirt.org/ is the official upstream website for the libvirt virtualization API. https://virt-manager.org/ is the upstream project website for the Virtual Machine Manager (virt-manager), the graphical application for managing virtual machines. Red Hat Virtualization - http://www.redhat.com/products/cloud-computing/virtualization/ Red Hat product documentation - https://access.redhat.com/documentation/en/ Virtualization technologies overview - http://virt.kernelnewbies.org

Commands: