mtpti5iD/redhat-docs_dataset huggingface dataset:
16.4. Installing virt-who Manually This section will describe how to manually attach the subscription provided by the hypervisor. Procedure 16.2. How to attach a subscription manually List subscription information and find the Pool ID First you need to list the available subscriptions which are of the virtual type. Run the following command in a terminal as root: Note the Pool ID displayed. Copy this ID as you will need it in the step. Attach the subscription with the Pool ID Using the Pool ID you copied in the step run the attach command. Replace the Pool ID XYZ123 with the Pool ID you retrieved. Run the following command in a terminal as root:

Commands:
subscription-manager list --avail --match-installed | grep 'Virtual' -B12 Subscription Name: Red Hat Enterprise Linux ES (Basic for Virtualization) Provides: Red Hat Beta Oracle Java (for RHEL Server) Red Hat Enterprise Linux Server SKU: ------- Pool ID: XYZ123 Available: 40 Suggested: 1 Service Level: Basic Service Type: L1-L3 Multi-Entitlement: No Ends: 01/02/2017 System Type: Virtual
subscription-manager attach --pool=XYZ123 Successfully attached a subscription for: Red Hat Enterprise Linux ES (Basic for Virtualization)
7.188. powerpc-utils 7.188.1. RHBA-2013:0384 - powerpc-utils bug fix and enhancement update Updated powerpc-utils packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The powerpc-utils packages provide various utilities for the PowerPC platform. Note The powerpc-utils packages have been upgraded to upstream version 1.2.13, which provides a number of bug fixes and enhancements over the version, including support for physical Ethernet devices. The snap and hvcsadmin scripts now use the "use strict" construct to prevent a Perl interpreter from allowing usage of unsafe constructs, such as symbolic references, undeclared variables and using strings without quotation marks. The snap script now also enables to add a hostname and timestamp to its output file name by specifying the "-t" option. (BZ#822656) Bug Fixes BZ#739699 The bootlist command is used to read and modify the bootlist in NVRAM so that a system can boot from the correct device. Previously, when using a multipath device as a boot device, the bootlist command used its Linux logical name. However, Open Firmware, which is used on IBM POWER systems, is unable to parse Linux logical names. Therefore booting from a multipath device on IBM POWER systems failed. This update modifies the bootlist script so that bootlist now supports multipath devices as a parameter. The script converts Linux logical names of multipath devices to the path names that are parsable by Open Firmware. Booting from a multipath device on IBM POWER systems now succeeds as expected. BZ#857841 Previously, the "hvcsadmin -status" command did not provide any output if no IBM hypervisor virtual console server (hvcs) adapters were found on the system. This update corrects the hvcsadmin script so that when executing the "hvcsadmin -status" command, the user can now see a message indicating that no hvcs adapters were found. BZ#870212 The lsdevinfo script did not previously take into consideration the "status" attribute for Ethernet devices. This attribute is essential for the End-to-End Virtual Device View feature so the feature did not work without it. This update modifies lsdevinfo so the script now also checks the status of Ethernet devices and sets the status attribute to 1. The End-to-End Virtual Device View feature now works as expected. All users of powerpc-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
12.4. Updating an Object Class This section describes how to update an object class using the command line and the web console. 12.4.1. Updating an Object Class Using the Command Line Use the dsconf utility to update an object class entry. For example: For further details about object class definitions, see Section 12.1.2, "Object Classes" . 12.4.2. Updating an Object Class Using the Web Console To update an object class using the web console: Open the Directory Server user interface in the web console. See Section 1.4, "Logging Into Directory Server Using the Web Console" . Select the instance. Select Schema Objectclasses . Click the Choose Action button to the right of the object class entry you want to edit. Select Edit Object Class . Update the parameters. Click Save .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com schema objectclasses replace examplePerson --oid="2.16.840.1133730.2.123" --desc="Example Person Object Class" --sup="inetOrgPerson" --kind="AUXILIARY" --must="cn" --may exampleDisplayName exampleAlias
Preface Red Hat Trusted Application Pipeline (RHTAP) is not really a single product. Instead, it is a set of products that combine to form a highly automated, customizable, and secure platform for building applications. By default, RHTAP includes the following products: Advanced Cluster Security (ACS) : to scan your artifacts for vulnerabilities. Developer Hub : a self-service portal, to consolidate management of applications across their lifecycle. Enterprise Contract : to validate your artifacts against customizable policies. OpenShift GitOps : to manage Kubernetes deployments and their infrastructure. OpenShift Pipelines : to enable automation and provide visibility for continuous integration and continuous delivery (CI/CD) of software. Quay.io : a container registry, to store your artifacts. Trusted Artifact Signer : to sign and validate the artifacts that RHTAP produces. Trusted Profile Analyzer : to deliver actionable information about your security posture. You can see exactly which versions of these products RHTAP supports in the compatibility and support matrix of our Release notes . Note Red Hat Trusted Application Pipeline supports many alternatives to this default combination of products. Later in the installation process, this documentation explains how to customize your deployment to meet your needs. Because a fully-operational instance of RHTAP involves all of the products listed above, installing RHTAP takes some effort. However, we have automated the vast majority of this process with an installer tool packaged as a container image. Be aware that the RHTAP installer is not a manager: it does not support upgrades. The installer generates your first deployment of RHTAP. But after installation, you must manage each product within RHTAP separately. And while the installer can be run multiple times, doing so after manually changing the configuration of a product may have unpredictable results. Additionally, the products that the installer deploys are production ready, but they are sized for a proof of concept or a very small team. For larger teams, manual reconfiguration of the products is most likely necessary and should be done by following procedures documented for each individual product. Lastly, please be aware that the RHTAP subscription only includes Red Hat Developer Hub, Red Hat Trusted Artifact Signer, Red Hat Trusted Profile Analyzer, and Red Hat Enterprise Contract. The RHTAP installer deploys all the other products listed above, too. But to use them, you must purchase a subscription for OpenShift Plus. Installation steps To install RHTAP using the installer, you must complete the following procedures. Configuring GitHub for RHTAP (Optional) Customizing your installation Installing RHTAP in your cluster (Optional) Completing integrations after installation The following pages of this document explain each of those installation steps in detail.

Commands:
5.5. Configure CXF for a Web Service Data Source: Transport Settings CXF configuration can also control low level aspects of the HTTP transport. Prerequisites The web service data source must be configured and the ConfigFile and EndPointName properties must be configured for CXF. Procedure 5.4. Configure CXF for a Web Service Data Source: Transport Settings Open the CXF configuration file for the web service data source and add your desired transport properties. The following is an example of a CXF configuration file for a web service data source that disables hostname verification: Warning disableCNcheck=true must NOT be used in production.

Commands:
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:jaxws="http://cxf.apache.org/jaxws" xsi:schemaLocation="http://cxf.apache.org/transports/http/configuration http://cxf.apache.org/schemas/configuration/http-conf.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <http-conf:conduit name="{http://teiid.org}teiid.http-conduit"> <http-conf:tlsClientParameters disableCNcheck="tru" /> </http-conf:conduit> </beans>
System-Level Authentication Guide Red Hat Enterprise Linux 7 Using applications and services to configure authentication on local systems Florian Delehaye Red Hat Customer Content Services fdelehay@redhat.com Marc Muehlfeld Red Hat Customer Content Services Filip Hanzelka Red Hat Customer Content Services Lucie Manaskova Red Hat Customer Content Services Aneta Steflova Petrova Red Hat Customer Content Services Tomas Capek Red Hat Customer Content Services Ella Deon Ballard Red Hat Customer Content Services

Commands:
2.4. Uninstalling an IdM Server Note At domain level 0 , the procedure is different. See Section D.3.6, "Removing a Replica" . Prerequisites Before uninstalling a server that serves as a certificate authority (CA), key recovery authority (KRA), or DNS Security Extensions (DNSSEC) server, make sure these services are running on another server in the domain. Warning Removing the last replica that serves as a CA, KRA, or DNSSEC server can seriously disrupt the Identity Management functionality. Procedure To uninstall server.example.com : On another server, use the ipa server-del command to delete server.example.com from the topology: On server.example.com , use the ipa-server-install --uninstall command: Make sure all name server (NS) DNS records pointing to server.example.com are deleted from your DNS zones. This applies regardless of whether you use integrated DNS managed by IdM or external DNS.

Commands:
ipa server-del server.example.com
ipa-server-install --uninstall
Chapter 4. Virtualization New Packages: hyperv-daemons New hyperv-daemons packages have been added to Red Hat Enterprise Linux 6.6. The new packages include the Hyper-V KVP daemon, previously provided by the hypervkvpd package, the Hyper-V VSS daemon, previously provided by the hypervvssd package, and the hv_fcopy daemon, previously provided by the hypervfcopyd package. The suite of daemons provided by hyperv-daemons are needed when a Linux guest is running on a Microsoft Windows host with Hyper-V .

Commands:
Appendix A. Using your subscription AMQ Streams 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 AMQ Streams for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Revised on 2022-11-22 11:34:30 UTC

Commands:
4.23. bltk 4.23.1. RHBA-2011:1227 - bltk bug fix update An updated bltk package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The bltk (Battery Life Tool Kit) package includes binaries and scripts to test battery life. Bug Fixes BZ# 618308 Prior to this update, the bltk tree was corrupted. As a result, the bltk_report script failed. This update modifies the settings of the bltk root path. Now, the report script works as expected. BZ# 679028 Prior to this update, bltk could be installed without requiring the gnuplot binary. As a result, the bltk_plot script exited with an error message when the gnuplot package was not installed and the charts were shown from measured data. This update requires the gnuplot package for its installation. Now, the bltk_plot script no longer exits with an error. All bltk users are advised to upgrade to this updated package, which fixes these bugs.

Commands:
B.10.2. RHBA-2012:0735 - corosync bug fix update Updated corosync packages that fix one bug are now available for Red Hat Enterprise Linux 6 Extended Update Support. The corosync packages provide the Corosync Cluster Engine and C Application Programming Interfaces (APIs) for Red Hat Enterprise Linux cluster software. Bug Fix BZ# 828430 Previously, it was not possible to activate or deactivate debug logs at runtime due to memory corruption in the objdb structure. With this update, the debug logging can now be activated or deactivated on runtime, for example with the command "corosync-objctl -w logging.debug=off". All users of corosync are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 12. Registering RHEL by using Subscription Manager Post-installation, you must register your system to get continuous updates. 12.1. Registering RHEL 8 using the installer GUI You can register a Red Hat Enterprise Linux 8 by using the RHEL installer GUI. Prerequisites You have a valid user account on the Red Hat Customer Portal. See the Create a Red Hat Login page . You have a valid Activation Key and Organization id. Procedure From the Installation Summary screen, under Software , click Connect to Red Hat . Authenticate your Red Hat account using the Account or Activation Key option. Optional: In the Set System Purpose field select the Role , SLA , and Usage attribute that you want to set from the drop-down menu. At this point, your Red Hat Enterprise Linux 8 system has been successfully registered. 12.2. Registration Assistant Registration Assistant is designed to help you choose the most suitable registration option for your Red Hat Enterprise Linux environment. Additional resources For assistance with using a username and password to register RHEL with the Subscription Manager client, see the RHEL registration assistant on the Customer Portal. For assistance with registering your RHEL system to Red Hat Insights, see the Insights registration assistant on the Hybrid Cloud Console. 12.3. Registering your system using the command line You can register your Red Hat Enterprise Linux 8 subscription by using the command line. For an improved and simplified experience registering your hosts to Red Hat, use remote host configuration (RHC). The RHC client registers your system to Red Hat making your system ready for Insights data collection and enabling direct issue remediation from Insights for Red Hat Enterprise Linux. For more information, see RHC registration . Prerequisites You have an active, non-evaluation Red Hat Enterprise Linux subscription. Your Red Hat subscription status is verified. You have not previously received a Red Hat Enterprise Linux 8 subscription. You have successfully installed Red Hat Enterprise Linux 8 and logged into the system as root. Procedure Open a terminal window as a root user. Register your Red Hat Enterprise Linux system by using the activation key: When the system is successfully registered, an output similar to the following is displayed: Additional resources Using an activation key to register a system with Red Hat Subscription Manager Getting Started with RHEL System Registration

Commands:
subscription-manager register --activationkey= <activation_key_name> --org= <organization_ID>
The system has been registered with id: 62edc0f8-855b-4184-b1b8-72a9dc793b96
Chapter 6. Red Hat build of Kogito events add-on The events add-on provides a default implementation in supported target platforms for EventEmitter and EventReceiver interfaces. You can use EventEmitter and EventReceiver interfaces to enable messaging by process, serverless workflow events, and event decision handling. 6.1. Implementing message payload decorator for Red Hat build of Kogito events add-on Any dependent add-on can implement the MessagePayloadDecorator . Prerequisites You have installed the Events add-on in Red Hat build of Kogito. Procedure Create a file named META-INF/services/org.kie.kogito.add-on.cloudevents.message.MessagePayloadDecorator in your class path. Open the file. Enter the full name of your implementation class in the file. Save the file. The MessagePayloadDecoratorProvider loads the file upon application start-up and adds the file to the decoration chain. When Red Hat build of Kogito calls the MessagePayloadDecoratorProvider#decorate , your implementation is part of the decoration algorithm. To use the events add-on, add the following code to the pom.xml file of your project: Events smallrye add-on for {QAURKUS} <dependency> <groupId>org.kie.kogito</groupId> <artifactId>kogito-addons-quarkus-events-smallrye</artifactId> <version>1.15</version> </dependency> Events decisions add-on for {QAURKUS} <dependency> <groupId>org.kie.kogito</groupId> <artifactId>kogito-addons-events-decisions</artifactId> <version>1.15</version> </dependency> Events Kafka add-on for Spring Boot <dependency> <groupId>org.kie.kogito</groupId> <artifactId>kogito-addons-springboot-events-kafka</artifactId> <version>1.15</version> </dependency> Events decisions add-on for Spring Boot <dependency> <groupId>org.kie.kogito</groupId> <artifactId>kogito-addons-springboot-events-decisions</artifactId> <version>1.15</version> </dependency>

Commands:
<dependency> <groupId>org.kie.kogito</groupId> <artifactId>kogito-addons-quarkus-events-smallrye</artifactId> <version>1.15</version> </dependency>
<dependency> <groupId>org.kie.kogito</groupId> <artifactId>kogito-addons-events-decisions</artifactId> <version>1.15</version> </dependency>
<dependency> <groupId>org.kie.kogito</groupId> <artifactId>kogito-addons-springboot-events-kafka</artifactId> <version>1.15</version> </dependency>
<dependency> <groupId>org.kie.kogito</groupId> <artifactId>kogito-addons-springboot-events-decisions</artifactId> <version>1.15</version> </dependency>
3.3.2. Configuring a Backup Fence Device You can define multiple fencing methods for a node. If fencing fails using the first method, the system will attempt to fence the node using the second method, followed by any additional methods you have configured. Use the following procedure to configure a backup fence device for a node. Use the procedure provided in Section 3.3.1, "Configuring a Single Fence Device for a Node" to configure the primary fencing method for a node. Beneath the display of the primary method you defined, click Add Fence Method . Enter a name for the backup fencing method that you are configuring for this node and click Submit . This displays the node-specific screen that now displays the method you have just added, below the primary fence method. Configure a fence instance for this method by clicking Add Fence Instance . This displays a drop-down menu from which you can select a fence device you have previously configured, as described in Section 3.2.1, "Creating a Fence Device" . Select a fence device for this method. If this fence device requires that you configure node-specific parameters, the display shows the parameters to configure. Click Submit . This returns you to the node-specific screen with the fence method and fence instance displayed. You can continue to add fencing methods as needed. You can rearrange the order of fencing methods that will be used for this node by clicking on Move Up and Move Down .

Commands:
1.3. Running LVM in a Cluster The Clustered Logical Volume Manager (CLVM) is a set of clustering extensions to LVM. These extensions allow a cluster of computers to manage shared storage (for example, on a SAN) using LVM. The clmvd daemon is the key clustering extension to LVM. The clvmd daemon runs in each cluster computer and distributes LVM metadata updates in a cluster, presenting each cluster computer with the same view of the logical volumes. Figure 1.2, "CLVM Overview" shows a CLVM overview in a Red Hat cluster. Figure 1.2. CLVM Overview Logical volumes created with CLVM on shared storage are visible to all computers that have access to the shared storage. CLVM allows a user to configure logical volumes on shared storage by locking access to physical storage while a logical volume is being configured. CLVM uses the locking services provided by the high availability symmetric infrastructure. Note Shared storage for use in Red Hat Cluster Suite requires that you be running the cluster logical volume manager daemon ( clvmd ) or the High Availability Logical Volume Management agents (HA-LVM). If you are not able to use either the clvmd daemon or HA-LVM for operational reasons or because you do not have the correct entitlements, you must not use single-instance LVM on the shared disk as this may result in data corruption. If you have any concerns please contact your Red Hat service representative. Note CLVM requires changes to the lvm.conf file for cluster-wide locking. For information on configuring the lvm.conf file to support CLVM, see Section 3.1, "Creating LVM Volumes in a Cluster" . You configure LVM volumes for use in a cluster with the standard set of LVM commands or the LVM graphical user interface, as described in Chapter 4, LVM Administration with CLI Commands and Chapter 7, LVM Administration with the LVM GUI . For information on installing LVM in a Red Hat Cluster, see Configuring and Managing a Red Hat Cluster .

Commands: