mtpti5iD/redhat-docs_dataset huggingface dataset:
Preface Open Java Development Kit (Red Hat build of OpenJDK) is a free and open-source implementation of the Java Platform, Standard Edition (Java SE). Eclipse Temurin is available in three LTS versions: Red Hat build of OpenJDK 8u, Red Hat build of OpenJDK 11u, and Red Hat build of OpenJDK 17u. Packages for Eclipse Temurin are made available on Microsoft Windows and on multiple Linux x86 Operating Systems including Red Hat Enterprise Linux and Ubuntu.

Commands:
Chapter 14. Idling applications Cluster administrators can idle applications to reduce resource consumption. This is useful when the cluster is deployed on a public cloud where cost is related to resource consumption. If any scalable resources are not in use, OpenShift Container Platform discovers and idles them by scaling their replicas to 0 . The time network traffic is directed to the resources, the resources are unidled by scaling up the replicas, and normal operation continues. Applications are made of services, as well as other scalable resources, such as deployment configs. The action of idling an application involves idling all associated resources. 14.1. Idling applications Idling an application involves finding the scalable resources (deployment configurations, replication controllers, and others) associated with a service. Idling an application finds the service and marks it as idled, scaling down the resources to zero replicas. You can use the oc idle command to idle a single service, or use the --resource-names-file option to idle multiple services. 14.1.1. Idling a single service Procedure To idle a single service, run: USD oc idle <service> 14.1.2. Idling multiple services Idling multiple services is helpful if an application spans across a set of services within a project, or when idling multiple services in conjunction with a script to idle multiple applications in bulk within the same project. Procedure Create a file containing a list of the services, each on their own line. Idle the services using the --resource-names-file option: USD oc idle --resource-names-file <filename> Note The idle command is limited to a single project. For idling applications across a cluster, run the idle command for each project individually. 14.2. Unidling applications Application services become active again when they receive network traffic and are scaled back up their state. This includes both traffic to the services and traffic passing through routes. Applications can also be manually unidled by scaling up the resources. Procedure To scale up a DeploymentConfig, run: USD oc scale --replicas=1 dc <dc_name> Note Automatic unidling by a router is currently only supported by the default HAProxy router. Note Services do not support automatic unidling if you configure Kuryr-Kubernetes as an SDN.

Commands:
oc idle <service>
oc idle --resource-names-file <filename>
oc scale --replicas=1 dc <dc_name>
8.149. perl-Test-Memory-Cycle 8.149.1. RHBA-2013:0859 - perl-Test-Memory-Cycle bug fix update An updated perl-Test-Memory-Cycle package that fixes one bug is now available for Red Hat Enterprise Linux 6. The perl-Test-Memory-Cycle package provides possibility to search for circular references, which cannot be collected by the Perl's garbage collector. Bug Fix BZ# 621089 Previously, the perl-Test-Memory-Cycle package was missing a build requirement. Consequently, the package could not be built. This update adds the perl-CGI package build requirement to the perl-Test-Memory-Cycle.spec file and perl-Test-Memory-Cycle can now be built as expected. Users of perl-Test-Memory-Cycle are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 2. Compatibility and support matrix Red Hat Trusted Application Pipeline, or RHTAP, installs on OpenShift Container Platform. Product Version OpenShift Container Platform 4.15, 4.14, 4.13 RHTAP installs the following products and components during installation: Products installed with RHTAP Version Red Hat Developer Hub 1.1.x Red Hat Trusted Artifact Signer 1.0.x Red Hat Trusted Profile Analyzer 1.0.0 OpenShift Pipelines 1.14.x OpenShift GitOps 1.12.x RHTAP also integrates with the following products or components to help protect your software supply chain: Product Version Red Hat Advanced Cluster Security 4.3 Quay 3.10

Commands:
10.3. Changing JBoss Data Virtualization Settings Using Management CLI To edit a particular JBoss Data Virtualization setting, run the following command within the Management CLI: Note To change translator and transport (including SSL) settings refer to Section 10.4, "Managing Transport and SSL Settings Using Management CLI" and Section 10.5, "Managing Translator Settings Using Management CLI" . For example: For more information about the Management CLI, refer to the Red Hat JBoss Enterprise Application Platform Administration and Configuration Guide . Note After modifying any of these settings, you will be prompted to reload the server. Changes to these settings will not take effect until the server is restarted. You can reload the server by running the reload command from within the Management CLI. After the server reloads, you may have to reconnect by running the connect command to continue working within the Management CLI.

Commands:
/subsystem=teiid:write-attribute(name= SETTING_NAME , value= VALUE )
/subsystem=teiid:write-attribute(name=max-active-plans, value=50)
Appendix B. Revision History Revision History Revision 10.13-59 Mon May 21 2018 Marek Suchanek Asynchronous update. Revision 10.14-00 Fri Apr 6 2018 Marek Suchanek Preparing document for 7.5 GA publication. Revision 10.13-58 Fri Mar 23 2018 Marek Suchanek New sections: pqos. Revision 10.13-57 Wed Feb 28 2018 Marek Suchanek Asynchronous update. Revision 10.13-50 Thu Jul 27 2017 Milan Navratil Document version for 7.4 GA publication. Revision 10.13-44 Tue Dec 13 2016 Milan Navratil Asynchronous update. Revision 10.08-38 Wed Nov 11 2015 Jana Heves Version for 7.2 GA release. Revision 0.3-23 Tue Feb 17 2015 Laura Bailey Building for RHEL 7.1 GA. Revision 0.3-3 Mon Apr 07 2014 Laura Bailey Rebuilding for RHEL 7.0 GA.

Commands:
9.4. Setting Addresses for Devices Many devices have an optional <address> sub-element which is used to describe where the device is placed on the virtual bus presented to the guest virtual machine. If an address (or any optional attribute within an address) is omitted on input, libvirt will generate an appropriate address; but an explicit address is required if more control over layout is required. See Figure 9.6, "XML example for PCI device assignment" for domain XML device examples including an <address> element. Every address has a mandatory attribute type that describes which bus the device is on. The choice of which address to use for a given device is constrained in part by the device and the architecture of the guest virtual machine. For example, a <disk> device uses type='drive' , while a <console> device would use type='pci' on i686 or x86_64 guest virtual machine architectures. Each address type has further optional attributes that control where on the bus the device will be placed as described in the table: Table 9.1. Supported device address types Address type Description type='pci' PCI addresses have the following additional attributes: domain (a 2-byte hex integer, not currently used by qemu) bus (a hex value between 0 and 0xff, inclusive) slot (a hex value between 0x0 and 0x1f, inclusive) function (a value between 0 and 7, inclusive) multifunction controls turning on the multifunction bit for a particular slot/function in the PCI control register By default it is set to 'off', but should be set to 'on' for function 0 of a slot that will have multiple functions used. type='drive' Drive addresses have the following additional attributes: controller (a 2-digit controller number) bus (a 2-digit bus number target (a 2-digit bus number) unit (a 2-digit unit number on the bus) type='virtio-serial' Each virtio-serial address has the following additional attributes: controller (a 2-digit controller number) bus (a 2-digit bus number) slot (a 2-digit slot within the bus) type='ccid' A CCID address, for smart-cards, has the following additional attributes: bus (a 2-digit bus number) slot attribute (a 2-digit slot within the bus) type='usb' USB addresses have the following additional attributes: bus (a hex value between 0 and 0xfff, inclusive) port (a dotted notation of up to four octets, such as 1.2 or 2.1.3.1) type='isa' ISA addresses have the following additional attributes: iobase irq

Commands:
4.4.3. Limiting Root Access Rather than completely deny access to the root user, the administrator may want to allow access only via setuid programs, such as su or sudo . 4.4.3.1. The su Command Upon typing the su command, the user is prompted for the root password and, after authentication, is given a root shell prompt. Once logged in via the su command, the user is the root user and has absolute administrative access to the system. In addition, once a user has become root, it is possible for them to use the su command to change to any other user on the system without being prompted for a password. Because this program is so powerful, administrators within an organization may wish to limit who has access to the command. One of the simplest ways to do this is to add users to the special administrative group called wheel . To do this, type the following command as root: In the command, replace <username> with the username you want to add to the wheel group. To use the User Manager for this purpose, go to the Main Menu Button (on the Panel) => System Settings => Users & Groups or type the command system-config-users at a shell prompt. Select the Users tab, select the user from the user list, and click Properties from the button menu (or choose File => Properties from the pull-down menu). Then select the Groups tab and click on the wheel group, as shown in Figure 4.2, " Groups Pane" . Figure 4.2. Groups Pane , open the PAM configuration file for su ( /etc/pam.d/su ) in a text editor and remove the comment # from the following line: Doing this permits only members of the administrative group wheel to use the program. Note The root user is part of the wheel group by default.

Commands:
usermod -G wheel <username>
auth required /lib/security/USDISA/pam_wheel.so use_uid
Chapter 13. Clustering Dynamic schema generation The introduction of dynamic schema generation provides a lot of flexibility for end users to plug into Red Hat Enterprise Linux High Availability Add-on custom resource and fence agents, and still retain the possibility to validate their /etc/cluster.conf configuration file against those agents. It is a strict requirement that custom agents provide correct metadata output and that the agents must be installed on all cluster nodes. Clustered Samba on GFS2 Support for Samba in a clustered environment is now fully supported in Red Hat Enterprise Linux 6.2. Samba clustering relies on a clustered file system being available and shared on all nodes. In the Red Hat Enterprise Linux context, Samba clustering has been configured to work with GFS2, the native shared storage file system. Clustered Samba (more specifically CTDB) provides the ability for the metadata to span multiple physical hosts in a cluster. CTDB will automatically recover and repair node-specific databases in case of node failures. It also provides high availability features like node monitoring and failover. Support for redundant ring for standalone Corosync Red Hat Enterprise Linux 6.2 introduces support for redundant ring with autorecovery feature as a Technology Preview. Refer to the Technical Notes for a list of known issues associated with this Technology Preview. corosync-cpgtool The corosync-cpgtool now specifies both interfaces in a dual ring configuration. This feature is a Technology Preview. Disabling rgmanager in /etc/cluster.conf As a consequence of converting the /etc/cluster.conf configuration file to be used by pacemaker , rgmanager must be disabled. The risk of not doing this is high; after a successful conversion, it would be possible to start rgmanager and pacemaker on the same host, managing the same resources. Consequently, Red Hat Enterprise Linux 6.2 includes a feature (as a Technology Preview) that forces the following requirements: rgmanager must refuse to start if it sees the <rm disabled="1"> flag in /etc/cluster.conf . rgmanager must stop any resources and exit if the <rm disabled="1"> flag appears in /etc/cluster.conf during a reconfiguration.

Commands:
13.3. Configuring Soft-RoCE RoCE can be implemented both in the hardware and in the software. Soft-RoCE is the software implementation of the RDMA transport. Prerequisites Since Red Hat Enterprise Linux 7.4, the Soft-RoCE driver is already merged into the kernel. The user-space driver also is merged into the rdma-core package. Soft-RoCE is also known as RXE. To start, stop and configure RXE, use the rxe_cfg script. To view options for rxe_cfg , enter rxe_cfg help . Procedure 13.2. Configuring Soft-RoCE As the root user, enter the following command to display the current configuration status of RXE: To load the RXE kernel module and start RXE, enter as root : Optionally, to verify that the RXE kernel module is loaded, enter: Before adding a new RXE device over an Ethernet interface, the corresponding interface should be opened and has a valid IP address assigned. To add a new RXE device, for example igb_1 : The rxe0 in the RDEV column indicates that rxe is enabled for the igb_1 device. To verify the status of an RXE device, use the ibv_devices command: Alternatively, enter the ibstat for a detailed status: Removing an RXE device If you want to remove an RXE device, enter: Verifying Connectivity of an RXE device The following examples show how to verify connectivity of an RXE device on the server and client side. Example 13.1. Verifying Connectivity of an RXE device on the Server Side Example 13.2. Verifying Connectivity of an RXE device on the Client Side

Commands:
~]# rxe_cfg rdma_rxe module not loaded Name Link Driver Speed NMTU IPv4_addr RDEV RMTU igb_1 yes igb mlx4_1 no mlx4_en mlx4_2 no mlx4_en
~]# rxe_cfg start Name Link Driver Speed NMTU IPv4_addr RDEV RMTU igb_1 yes igb mlx4_1 no mlx4_en mlx4_2 no mlx4_en
~]# lsmod |grep rdma_rxe rdma_rxe 111129 0 ip6_udp_tunnel 12755 1 rdma_rxe udp_tunnel 14423 1 rdma_rxe ib_core 236827 15 rdma_cm,ib_cm,iw_cm,rpcrdma,mlx4_ib,ib_srp,ib_ucm,ib_iser,ib_srpt,ib_umad,ib_uverbs,rdma_rxe,rdma_ucm,ib_ipoib,ib_isert
~]# rxe_cfg add igb_1
~]# rxe_cfg status Name Link Driver Speed NMTU IPv4_addr RDEV RMTU igb_1 yes igb rxe0 1024 (3) mlx4_1 no mlx4_en mlx4_2 no mlx4_en
~]# ibv_devices device node GUID ------ ---------------- mlx4_0 0002c90300b3cff0 rxe0 a2369ffffe018294
~]# ibstat rxe0 CA 'rxe0' CA type: Number of ports: 1 Firmware version: Hardware version: Node GUID: 0xa2369ffffe018294 System image GUID: 0x0000000000000000 Port 1: State: Active Physical state: LinkUp Rate: 2.5 Base lid: 0 LMC: 0 SM lid: 0 Capability mask: 0x00890000 Port GUID: 0xa2369ffffe018294 Link layer: Ethernet
~]# rxe_cfg remove igb_1
~]USD ibv_rc_pingpong -d rxe0 -g 0 local address: LID 0x0000, QPN 0x000012, PSN 0xe2965f, GID fe80::290:faff:fe29:486a remote address: LID 0x0000, QPN 0x000011, PSN 0x4bf206, GID fe80::290:faff:fe29:470a 8192000 bytes in 0.05 seconds = 1244.06 Mbit/sec 1000 iters in 0.05 seconds = 52.68 usec/iter
~]USD ibv_rc_pingpong -d rxe0 -g 0 172.31.40.4 local address: LID 0x0000, QPN 0x000011, PSN 0x4bf206, GID fe80::290:faff:fe29:470a remote address: LID 0x0000, QPN 0x000012, PSN 0xe2965f, GID fe80::290:faff:fe29:486a 8192000 bytes in 0.05 seconds = 1245.72 Mbit/sec 1000 iters in 0.05 seconds = 52.61 usec/iter
Chapter 4. Debug Parameters These parameters allow you to set debug mode on a per-service basis. The Debug parameter acts as a global parameter for all services and the per-service parameters can override the effects of global parameter on individual services. Parameter Description BarbicanDebug Set to True to enable debugging OpenStack Key Manager (barbican) service. CinderDebug Set to True to enable debugging on OpenStack Block Storage (cinder) services. ConfigDebug Whether to run configuration management (e.g. Puppet) in debug mode. The default value is False . Debug Set to True to enable debugging on all services. The default value is False . GlanceDebug Set to True to enable debugging OpenStack Image Storage (glance) service. HeatDebug Set to True to enable debugging OpenStack Orchestration (heat) services. HorizonDebug Set to True to enable debugging OpenStack Dashboard (horizon) service. IronicDebug Set to True to enable debugging OpenStack Bare Metal (ironic) services. KeystoneDebug Set to True to enable debugging OpenStack Identity (keystone) service. ManilaDebug Set to True to enable debugging OpenStack Shared File Systems (manila) services. MemcachedDebug Set to True to enable debugging Memcached service. NeutronDebug Set to True to enable debugging OpenStack Networking (neutron) services. NovaDebug Set to True to enable debugging OpenStack Compute (nova) services. OctaviaDebug Set to True to enable debugging OpenStack Load Balancing-as-a-Service (octavia) services. SaharaDebug Set to True to enable debugging OpenStack Clustering (sahara) services.

Commands:
10.5.15. SuexecUserGroup The SuexecUserGroup directive, which originates from the mod_suexec module, allows the specification of user and group execution privileges for CGI programs. Non-CGI requests are still processed with the user and group specified in the User and Group directives. Note The SuexecUserGroup directive replaces the Apache HTTP Server 1.3 configuration of using the User and Group directives inside the configuration of VirtualHosts sections.

Commands:
8.5. Using OpenSCAP with Red Hat Satellite When running multiple Red Hat Enterprise Linux systems, it is important to keep all your systems compliant with your security policy and perform security scans and evaluations remotely from one location. This can be achieved by using Red Hat Satellite 5.5 or later with the spacewalk-oscap package installed on your Satellite client. The package is available from the Red Hat Network Tools channel. This solution supports two methods of performing security compliance scans, viewing and further processing of the scan results. You can either use the OpenSCAP Satellite Web Interface or run commands and scripts from the Satellite API . For more information about this solution to security compliance, its requirements and capabilities, see the Red Hat Satellite documentation .

Commands:
5.36. cpuspeed 5.36.1. RHBA-2012:1404 - cpuspeed bug fix update Updated cpuspeed packages that fix four bugs are now available for Red Hat Enterprise Linux 6. The cpuspeed packages provide a daemon to manage the CPU frequency scaling. Bug Fixes BZ# 642838 Prior to this update, the PCC driver used the "userspace" governor was loaded instead of the "ondemand" governor when loading. This update modifies the init script to also check the PCC driver. BZ# 738463 Prior to this update, the cpuspeed init script tried to set cpufrequency system files on a per core basis which was a deprecated procedure. This update sets thresholds globally. BZ# 616976 Prior to this update, the cpuspeed tool did not reset MIN and MAX values, when the configuration file was emptied. As a consequence, the MIN_SPEED or MAX_SPEED values were not reset as expected. This update adds conditionals in the init script to check these values. Now, the MIN_SPEED or MAX_SPEED values are reset as expected. BZ# 797055 Prior to this update, the init script did not handle the IGNORE_NICE parameter as expected. As a consequence, "-n" was added to command options when the IGNORE_NICE parameter was set. This update modifies the init script to stop adding the NICE option when using the IGNORE_NICE parameter. All users of cpuspeed are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Appendix A. Using your subscription Apicurio Registry is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing your account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading ZIP and TAR files To access ZIP or TAR files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat Integration entries in the Integration and Automation category. Select the desired Apicurio Registry product. The Software Downloads page opens. Click the Download link for your component. Revised on 2024-12-20 16:57:47 UTC

Commands:
Chapter 5. Red Hat Developer Hub integration with Amazon Web Services (AWS) You can integrate your Red Hat Developer Hub application with Amazon Web Services (AWS), which can help you streamline your workflows within the AWS ecosystem. Integrating the Developer Hub resources with AWS provides access to a comprehensive suite of tools, services, and solutions. The integration with AWS requires the deployment of Developer Hub in Elastic Kubernetes Service (EKS) using one of the following methods: The Helm chart The Red Hat Developer Hub Operator

Commands: