mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 35. GAV check management In Business Central, projects are identified by the Group ID , Artifact ID , and Version (GAV) Maven naming convention. GAV values differentiate projects and project versions as well as identify dependencies with particular projects. By default, Business Central detects duplicate GAVs. This feature can be disabled by users with the admin role. 35.1. Configuring GAV checks and child GAV edition This procedure describes how to configure GAV checks in Business Central. Procedure In Business Central, go to Menu Design Projects and click the project name. In the project window, click the Settings tab. In the General Settings tab, perform any of the following tasks: To enable other projects to have the same GAV, select the Disable GAV conflict check check box. To enable child projects to have GAV edition, select the Allow child GAV edition check box. Click Save . Note You can click Reset to undo all changes. Click Save to confirm the changes. Note Duplicate GAV detection is disabled for projects in Development Mode . To enable duplicate GAV detection in Business Central, go to project Settings General Settings Version and toggle the Development Mode option to OFF (if applicable). 35.2. Configuring GAV checks for all projects This procedure describes how to configure GAV checks for all projects in Business Central. You can also disable GAV checks at system startup. Procedures In Business Central, select the Admin icon in the top-right corner of the screen and select Projects . The Projects window opens. In the Advanced GAV preferences tab, perform any of the following tasks: To enable other projects to have the same GAV, select the Disable GAV conflict check check box. To enable child projects to have GAV edition, select the Allow child GAV edition check box. Click Save . Note You can also disable the duplicate GAV detection feature by setting the org.guvnor.project.gav.check.disabled system property to true for Business Central at system startup:

Commands:
~/EAP_HOME/bin/standalone.sh -c standalone-full.xml -Dorg.guvnor.project.gav.check.disabled=true
Chapter 5. Performance Co-Pilot (PCP) 5.1. PCP Overview and Resources Red Hat Enterprise Linux 7 provides support for Performance Co-Pilot ( PCP ), a suite of tools, services, and libraries for monitoring, visualizing, storing, and analyzing system-level performance measurements. Its light-weight distributed architecture makes it particularly well-suited for centralized analysis of complex systems. Performance metrics can be added using the Python, Perl, C++, and C interfaces. Analysis tools can use the client APIs (Python, C++, C) directly, and rich web applications can explore all available performance data using a JSON interface. PCP allows: the monitoring and management of real-time data the logging and retrieval of historical data You can use historical data to analyze patterns with issues by comparing live results with archived data. The Performance Metric Collection Daemon ( pmcd ) is responsible for collecting performance data on the host system, and various client tools, such as pminfo or pmstat , can be used to retrieve, display, archive, and process this data on the same host or over the network. The pcp package provides the command-line tools and underlying functionality. The graphical tool requires the pcp-gui package. For a list of system services and tools that are distributed with PCP, see Table A.1, "System Services Distributed with Performance Co-Pilot in Red Hat Enterprise Linux 7" and Table A.2, "Tools Distributed with Performance Co-Pilot in Red Hat Enterprise Linux 7" . Resources The manual page named PCPIntro serves as an introduction to Performance Co-Pilot. It provides a list of available tools as well as a description of available configuration options and a list of related manual pages. By default, comprehensive documentation is installed in the /usr/share/doc/pcp-doc/ directory, notably the Performance Co-Pilot User's and Administrator's Guide and Performance Co-Pilot Programmer's Guide . For information on PCP, see the Index of Performance Co-Pilot (PCP) articles, solutions, tutorials and white papers on the Red Hat Customer Portal. If you need to determine what PCP tool has the functionality of an older tool you are already familiar with, see the Side-by-side comparison of PCP tools with legacy tools Red Hat Knowledgebase article. See the official PCP documentation for an in-depth description of the Performance Co-Pilot and its usage. If you want to start using PCP on Red Hat Enterprise Linux quickly, see the PCP Quick Reference Guide . The official PCP website also contains a list of frequently asked questions .

Commands:
Chapter 2. Supported configurations For more information about supported and tested configurations for Java Virtual Machines (JVMs) and JBoss EAP 8.0, including commonly used operating systems, databases, and JMS brokers, see the Red Hat JBoss Enterprise Application Platform 8.0 supported configurations Knowledgebase article on the Red Hat Customer Portal. For more information about included modules, supported standards, and Red Hat JBoss Enterprise Application Platform component details, see the following support documents: Red Hat JBoss Enterprise Application Platform (EAP) 8 Included Modules Red Hat JBoss Enterprise Application Platform Supported Standards Red Hat JBoss Enterprise Application Platform Component Details OpenShift images Builder and Runtime images are supported for OpenJDK 17 / RHEL 8 on Intel, IBM systems Z & P, and ARM architectures. Red Hat build of Keycloak SAML adapters support You can now install Red Hat build of Keycloak SAML adapters using the Keycloak SAML adapter Galleon feature pack. For information about Red Hat build of Keycloak, see the Red Hat build of Keycloak product page . MariaDB Driver logging dependency In JBoss EAP 8.0, the MariaDB Driver includes a dependency on the org.slf4j module to improve logging functionality. This prevents possible errors when slf4j classes are unavailable, and ensures proper handling of log messages. When deploying the MariaDB Driver module, you must ensure the slf4j dependencies are available to leverage this enhancement. For more information, see How to configure MariaDB driver 3.0+ as a JBoss Module in EAP 7 / 8 . JBoss EAP 8.0 Operator JBoss EAP 8.0 now supports the EAP operator. You can now deploy your JBoss EAP 8.0 applications using the JBoss EAP operator. For more information, see JBoss EAP Operator Support Policy .

Commands:
Appendix A. Comparison between Ceph Ansible and Cephadm The Red Hat Ceph Storage 6 introduces a new deployment tool, Cephadm, for the containerized deployment of the storage cluster. The tables compare Cephadm with Ceph-Ansible playbooks for managing the containerized deployment of a Ceph cluster for day one and day two operations. Table A.1. Day one operations Description Ceph-Ansible Cephadm Installation of the Red Hat Ceph Storage cluster Run the site-container.yml playbook. Run cephadm bootstrap command to bootstrap the cluster on the admin node. Addition of hosts Use the Ceph Ansible inventory. Run ceph orch add host HOST_NAME to add hosts to the cluster. Addition of monitors Run the add-mon.yml playbook. Run the ceph orch apply mon command. Addition of managers Run the site-container.yml playbook. Run the ceph orch apply mgr command. Addition of OSDs Run the add-osd.yml playbook. Run the ceph orch apply osd command to add OSDs on all available devices or on specific hosts. Addition of OSDs on specific devices Select the devices in the osd.yml file and then run the add-osd.yml playbook. Select the paths filter under the data_devices in the osd.yml file and then run ceph orch apply -i FILE_NAME .yml command. Addition of MDS Run the site-container.yml playbook. Run the ceph orch apply FILESYSTEM_NAME command to add MDS. Addition of Ceph Object Gateway Run the site-container.yml playbook. Run the ceph orch apply rgw commands to add Ceph Object Gateway. Table A.2. Day two operations Description Ceph-Ansible Cephadm Removing hosts Use the Ansible inventory. Run ceph orch host rm HOST_NAME to remove the hosts. Removing monitors Run the shrink-mon.yml playbook. Run ceph orch apply mon to redeploy other monitors. Removing managers Run the shrink-mon.yml playbook. Run ceph orch apply mgr to redeploy other managers. Removing OSDs Run the shrink-osd.yml playbook. Run ceph orch osd rm OSD_ID to remove the OSDs. Removing MDS Run the shrink-mds.yml playbook. Run ceph orch rm SERVICE_NAME to remove the specific service. Exporting Ceph File System over NFS Protocol. Not supported on Red Hat Ceph Storage 4. Run ceph nfs export create command. Deployment of Ceph Object Gateway Run the site-container.yml playbook. Run ceph orch apply rgw SERVICE_NAME to deploy Ceph Object Gateway service. Removing Ceph Object Gateway Run the shrink-rgw.yml playbook. Run ceph orch rm SERVICE_NAME to remove the specific service. Block device mirroring Run the site-container.yml playbook. Run ceph orch apply rbd-mirror command. Minor version upgrade of Red Hat Ceph Storage Run the infrastructure-playbooks/rolling_update.yml playbook. Run ceph orch upgrade start command. Upgrading from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 6 Run infrastructure-playbooks/rolling_update.yml playbook. Upgrade using Cephadm is not supported. Deployment of monitoring stack Edit the all.yml file during installation. Run the ceph orch apply -i FILE .yml after specifying the services. Additional Resources For more details on using the Ceph Orchestrator, see the Red Hat Ceph Storage Operations Guide .

Commands:
Chapter 1. Available tools with the API Representational State Transfer (REST) relies on a stateless, client-server, and cacheable communications protocol, usually the HTTP protocol. You might find it helpful to see which API calls the user interface makes in sequence. To do this, you can use the UI from Firebug or Chrome with developer plugins. Another option is to use Charles Proxy . This offers a visualizer that you might find helpful. While it is commercial software, it can insert itself as an operating system X proxy and intercept both requests from web browsers, curl and other API consumers. Further options include the following: Fiddler mitmproxy Paros

Commands:
B.38.4. RHSA-2011:0329 - Important: kernel security update Updated kernel packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. The kernel packages contain the Linux kernel, the core of any Linux operating system. CVE-2011-0714 , Important A use-after-free flaw was found in the Linux kernel's RPC server sockets implementation. A remote attacker could use this flaw to trigger a denial of service by sending a corrupted packet to a target system. Red Hat would like to thank Adam Prince for reporting this issue. Users should upgrade to these updated packages, which contain a backported patch to correct this issue. The system must be rebooted for this update to take effect.

Commands:
probe::tcpmib.InSegs Name probe::tcpmib.InSegs - Count an incoming tcp segment Synopsis tcpmib.InSegs Values op value to be added to the counter (default value of 1) sk pointer to the struct sock being acted on Description The packet pointed to by skb is filtered by the function tcpmib_filter_key (or ipmib_filter_key for tcp v4). If the packet passes the filter is is counted in the global InSegs (equivalent to SNMP's MIB TCP_MIB_INSEGS)

Commands:
8.193. ql2400-firmware 8.193.1. RHBA-2014:1452 - ql2400-firmware bug fix and enhancement update An updated ql2400-firmware package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The ql2400-firmware package provides the firmware required to run the QLogic 2400 Series of mass storage adapters. Note The ql2400-firmware package has been upgraded to upstream version 7.03.00, which provides a number of bug fixes and enhancements over the version. (BZ# 1054301 ) All users of QLogic 2400 Series Fibre Channel adapters are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
B.26. git B.26.1. RHSA-2010:1003 - Moderate: git security update Updated git packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Git is a fast, scalable, distributed revision control system. CVE-2010-3906 A cross-site scripting (XSS) flaw was found in gitweb, a simple web interface for Git repositories. A remote attacker could perform an XSS attack against victims by tricking them into visiting a specially-crafted gitweb URL. All gitweb users should upgrade to these updated packages, which contain a backported patch to correct this issue.

Commands:
1.5. DM Multipath Setup Overview DM Multipath includes compiled-in default settings that are suitable for common multipath configurations. The basic procedure for configuring your system with DM Multipath is as follows: Install the device-mapper-multipath rpm. Create the configuration file and enable multipathing with the mpathconf command. You can also start the multipath daemon with this command if you do not need to edit the configuration file. If necessary, edit the multipath.conf configuration file to modify default values and save the updated file. Start the multipath daemon. For detailed setup instructions for multipath configuration see Chapter 3, Setting Up DM Multipath .

Commands:
9.3. Hardware RAID versus Software RAID There are two possible RAID approaches: Hardware RAID and Software RAID. 9.3.1. Hardware RAID The hardware-based array manages the RAID subsystem independently from the host and presents to the host only a single disk per RAID array. An example of a Hardware RAID device would be one that connects to a SCSI controller and presents the RAID arrays as a single SCSI drive. An external RAID system moves all RAID handling "intelligence" into a controller located in the external disk subsystem. The whole subsystem is connected to the host via a normal SCSI controller and appears to the host as a single disk. RAID controllers also come in the form of cards that act like a SCSI controller to the operating system but handle all of the actual drive communications themselves. In these cases, you plug the drives into the RAID controller just like you would a SCSI controller, but then you add them to the RAID controller's configuration, and the operating system never knows the difference.

Commands:
15.5.5. Directory Options The following lists directives which affect directories. dirlist_enable - When enabled, users are allowed to view directory lists. The default value is YES . dirmessage_enable - When enabled, a message is displayed whenever a user enters a directory with a message file. This message is found within the directory being entered. The name of this file is specified in the message_file directive and is .message by default. The default value is NO . Note, in Red Hat Enterprise Linux, the value is set to YES . force_dot_files - When enabled, files beginning with a dot ( . ) are listed in directory listings, with the exception of the . and .. files. The default value is NO . hide_ids - When enabled, all directory listings show ftp as the user and group for each file. The default value is NO . message_file - Specifies the name of the message file when using the dirmessage_enable directive. The default value is .message . text_userdb_names - When enabled, text usernames and group names are used in place of UID and GID entries. Enabling this option may slow performance of the server. The default value is NO . use_localtime - When enabled, directory listings reveal the local time for the computer instead of GMT. The default value is NO .

Commands:
39.2. Memory Usage The free command displays the total amount of physical memory and swap space for the system as well as the amount of memory that is used, free, shared, in kernel buffers, and cached. The command free -m shows the same information in megabytes, which are easier to read. If you prefer a graphical interface for free , you can use the GNOME System Monitor . To start it from the desktop, go to System => Administration => System Monitor or type gnome-system-monitor at a shell prompt (such as an XTerm). Click on the Resources tab. Figure 39.2. GNOME System Monitor - Resources tab

Commands:
total used free shared buffers cached Mem: 645712 549720 95992 0 176248 224452 -/+ buffers/cache: 149020 496692 Swap: 1310712 0 1310712
total used free shared buffers cached Mem: 630 536 93 0 172 219 -/+ buffers/cache: 145 485 Swap: 1279 0 1279
3.11. RHEA-2011:1724 - new package: python-ipaddr A new python-ipaddr package is now available for Red Hat Enterprise Linux 6. The python-ipaddr package is a library for working with IPv4 and IPv6 addresses for the Python programming environment. This enhancement update adds the python-ipaddr package to Red Hat Enterprise Linux 6. (BZ# 726773 ) This is being added as part of the Tech Preview of FCoE (Fibre Channel over Ethernet) target mode, as a dependency of fcoe-target-utils. It is recommended to install this library only as a prerequisite for running fcoe-target-utils, and it should not be used independently.

Commands:
Chapter 8. Run a Red Hat JBoss Data Grid as a Node without Endpoints Services send messages using channels to communicate with each other. An endpoint is a communications point for these services and is used to send and receive the messages sent through the channels. As a result, a node with no endpoints can communicate with other nodes in the same cluster, but not with clients. Report a bug 8.1. Benefits of a Node Without Endpoints The primary benefit for creating a node without endpoints in Red Hat JBoss Data Grid involves data replication. A node without any endpoints cannot be accessed by the client directly. As a result, they are primarily used to replicate data from other nodes that can communicate with clients. The result is a node with a backup copy of the data that cannot be accessed by the client, which protects it from failure via an error sent by the client. Report a bug

Commands:
13.10. Keyboard Configuration To add multiple keyboard layouts to your system, select Keyboard from the Installation Summary screen. Upon saving, the keyboard layouts are immediately available in the installation program and you can switch between them by using the keyboard icon located at all times in the upper right corner of the screen. Initially, only the language you selected in the welcome screen is listed as the keyboard layout in the left pane. You can either replace the initial layout or add more layouts. However, if your language does not use ASCII characters, you might need to add a keyboard layout that does, to be able to properly set a password for an encrypted disk partition or the root user, among other things. Figure 13.7. Keyboard Configuration To add an additional layout, click the + button, select it from the list, and click Add . To delete a layout, select it and click the - button. Use the arrow buttons to arrange the layouts in order of preference. For a visual preview of the keyboard layout, select it and click the keyboard button. To test a layout, use the mouse to click inside the text box on the right. Type some text to confirm that your selection functions correctly. To test additional layouts, you can click the language selector at the top on the screen to switch them. However, it is recommended to set up a keyboard combination for switching layout. Click the Options button at the right to open the Layout Switching Options dialog and choose a combination from the list by selecting its check box. The combination will then be displayed above the Options button. This combination applies both during the installation and on the installed system, so you must configure a combination here in order to use one after installation. You can also select more than one combination to switch between layouts. Important If you use a layout that cannot accept Latin characters, such as Russian , Red Hat recommends additionally adding the English (United States) layout and configuring a keyboard combination to switch between the two layouts. If you only select a layout without Latin characters, you might be unable to enter a valid root password and user credentials later in the installation process. This can prevent you from completing the installation. Once you have made your selection, click Done to return to the Installation Summary screen. Note To change your keyboard configuration after you have completed the installation, visit the Keyboard section of the Settings dialogue window.

Commands:
6.2. Displaying Information on Failed Devices You can use the -P argument of the lvs or vgs command to display information about a failed volume that would otherwise not appear in the output. This argument permits some operations even though the metatdata is not completely consistent internally. For example, if one of the devices that made up the volume group vg failed, the vgs command might show the following output. If you specify the -P argument of the vgs command, the volume group is still unusable but you can see more information about the failed device. In this example, the failed device caused both a linear and a striped logical volume in the volume group to fail. The lvs command without the -P argument shows the following output. Using the -P argument shows the logical volumes that have failed. The following examples show the output of the pvs and lvs commands with the -P argument specified when a leg of a mirrored logical volume has failed.

Commands:
vgs -o +devices Volume group "vg" not found
vgs -P -o +devices Partial mode. Incomplete volume groups will be activated read-only. VG #PV #LV #SN Attr VSize VFree Devices vg 9 2 0 rz-pn- 2.11T 2.07T unknown device(0) vg 9 2 0 rz-pn- 2.11T 2.07T unknown device(5120),/dev/sda1(0)
lvs -a -o +devices Volume group "vg" not found
lvs -P -a -o +devices Partial mode. Incomplete volume groups will be activated read-only. LV VG Attr LSize Origin Snap% Move Log Copy% Devices linear vg -wi-a- 20.00G unknown device(0) stripe vg -wi-a- 20.00G unknown device(5120),/dev/sda1(0)
root@link-08 ~]# vgs -a -o +devices -P Partial mode. Incomplete volume groups will be activated read-only. VG #PV #LV #SN Attr VSize VFree Devices corey 4 4 0 rz-pnc 1.58T 1.34T my_mirror_mimage_0(0),my_mirror_mimage_1(0) corey 4 4 0 rz-pnc 1.58T 1.34T /dev/sdd1(0) corey 4 4 0 rz-pnc 1.58T 1.34T unknown device(0) corey 4 4 0 rz-pnc 1.58T 1.34T /dev/sdb1(0)
lvs -a -o +devices -P Partial mode. Incomplete volume groups will be activated read-only. LV VG Attr LSize Origin Snap% Move Log Copy% Devices my_mirror corey mwi-a- 120.00G my_mirror_mlog 1.95 my_mirror_mimage_0(0),my_mirror_mimage_1(0) [my_mirror_mimage_0] corey iwi-ao 120.00G unknown device(0) [my_mirror_mimage_1] corey iwi-ao 120.00G /dev/sdb1(0) [my_mirror_mlog] corey lwi-ao 4.00M /dev/sdd1(0)
About Red Hat OpenShift Service Mesh 3.0.0tp1 About OpenShift Service Mesh Red Hat OpenShift Documentation Team

Commands:
apiVersion: sailoperator.io/v1alpha1 kind: Istio metadata: name: default spec: version: v1.22.3 namespace: istio-system updateStrategy: type: InPlace values: pilot: resources: requests: cpu: 100m memory: 1024Mi
oc explain istios.spec.values
apiVersion: sailoperator.io/v1alpha1 kind: IstioCNI metadata: name: default spec: version: v1.22.3 namespace: istio-cni values: cni: cniConfDir: /etc/cni/net.d excludeNamespaces: - kube-system