mtpti5iD/redhat-docs_dataset huggingface dataset:
12.3. Creating an Object Class This section describes how to create a object class using the command line and the web console. 12.3.1. Creating an Object Class Using the Command Line Use the ldapmodify utility to create a new object class entry. For example: For further details about object class definitions, see Section 12.1.2, "Object Classes" . 12.3.2. Creating an Object Class Using the Web Console To create 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 Add ObjectClass . Select the parent object class. Enter an object class name and, optionally, set a object identifier (OID). Select the object class kind. Enter the required and allowed attributes in the corresponding fields: Click Add .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com schema objectclasses add examplePerson --oid="2.16.840.1133730.2.123" --desc="Example Person Object Class" --sup="inetOrgPerson" --kind="AUXILIARY" --must="cn" --may exampleDateOfBirth examplePreferredOS
Appendix H. 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 Red Hat AMQ Streams entries in the JBOSS INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Registering Your System for Packages To install RPM packages on Red Hat Enterprise Linux, your system must be registered. If you are using zip or tar files, this step is not required. Go to access.redhat.com . Navigate to Registration Assistant . Select your OS version and continue to the page. Use the listed command in your system terminal to complete the registration. To learn more see How to Register and Subscribe a System to the Red Hat Customer Portal . Revised on 2021-08-18 09:26:20 UTC

Commands:
2.6. Authentication Figure 2.9. Authentication In the Authentication section, select whether to use shadow passwords and MD5 encryption for user passwords. These options are highly recommended and chosen by default. The Authentication Configuration options allow you to configure the following methods of authentication: NIS LDAP Kerberos 5 Hesiod SMB Name Switch Cache These methods are not enabled by default. To enable one or more of these methods, click the appropriate tab, click the checkbox to Enable , and enter the appropriate information for the authentication method. Refer to Chapter 26, Authentication Configuration for more information about the options.

Commands:
Part III. Designing a decision service using DRL rules As a business rules developer, you can define business rules using the DRL (Drools Rule Language) designer in Business Central. DRL rules are defined directly in free-form .drl text files instead of in a guided or tabular format like other types of rule assets in Business Central. These DRL files form the core of the decision service for your project. Note You can also design your decision service using Decision Model and Notation (DMN) models instead of rule-based or table-based assets. For information about DMN support in Red Hat Process Automation Manager 7.13, see the following resources: Getting started with decision services (step-by-step tutorial with a DMN decision service example) Designing a decision service using DMN models (overview of DMN support and capabilities in Red Hat Process Automation Manager) Prerequisites The space and project for the DRL rules have been created in Business Central. Each asset is associated with a project assigned to a space. For details, see Getting started with decision services .

Commands:
Chapter 1. Overview of AMQ Interconnect AMQ Interconnect is a lightweight AMQP message router for building scalable, available, and performant messaging networks. 1.1. Key features You can use AMQ Interconnect to flexibly route messages between any AMQP-enabled endpoints, including clients, servers, and message brokers. AMQ Interconnect provides the following benefits: Connects clients and message brokers into an internet-scale messaging network with uniform addressing Supports high-performance direct messaging Uses redundant network paths to route around failures Streamlines the management of large deployments 1.2. Supported standards and protocols AMQ Interconnect supports the following industry-recognized standards and network protocols: Version 1.0 of the Advanced Message Queueing Protocol (AMQP) Modern TCP with IPv6 Note The details of distributed transactions (XA) within AMQP are not provided in the 1.0 version of the specification. AMQ Interconnect does not support XA transactions. Additional resources OASIS AMQP 1.0 Specification . 1.3. Supported configurations AMQ Interconnect is supported on Red Hat Enterprise Linux 7 and 8. See Red Hat AMQ 7 Supported Configurations for more information. 1.4. Document conventions In this document, sudo is used for any command that requires root privileges. You should always exercise caution when using sudo , as any changes can affect the entire system. For more information about using sudo , see The sudo Command .

Commands:
4.2. General Properties of Fencing Devices Note To disable a fencing device/resource, you can set the target-role as you would for a normal resource. Note To prevent a specific node from using a fencing device, you can configure location constraints for the fencing resource. Table 4.1, "General Properties of Fencing Devices" describes the general properties you can set for fencing devices. Refer to Section 4.3, "Displaying Device-Specific Fencing Options" for information on fencing properties you can set for specific fencing devices. Note For information on more advanced fencing configuration properties, see Section 4.9, "Additional Fencing Configuration Options" Table 4.1. General Properties of Fencing Devices Field Type Default Description priority integer 0 The priority of the stonith resource. Devices are tried in order of highest priority to lowest. pcmk_host_map string A mapping of host names to ports numbers for devices that do not support host names. For example: node1:1;node2:2,3 tells the cluster to use port 1 for node1 and ports 2 and 3 for node2 pcmk_host_list string A list of machines controlled by this device (Optional unless pcmk_host_check=static-list ). pcmk_host_check string dynamic-list How to determine which machines are controlled by the device. Allowed values: dynamic-list (query the device), static-list (check the pcmk_host_list attribute), none (assume every device can fence every machine)

Commands:
Chapter 12. Distributed tracing 12.1. Enabling distributed tracing The client offers distributed tracing based on the Jaeger implementation of the OpenTracing standard. Use the following steps to enable tracing in your application: Install the tracing dependencies. Red Hat Enterprise Linux 7 USD sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm USD sudo yum install python2-pip USD pip install --user --upgrade setuptools USD pip install --user opentracing jaeger-client Red Hat Enterprise Linux 8 USD sudo dnf install python3-pip USD pip3 install --user opentracing jaeger-client Register the global tracer in your program. Example: Global tracer configuration from proton.tracing import init_tracer tracer = init_tracer(" <service-name> ") For more information about Jaeger configuration, see Jaeger Sampling . When testing or debugging, you may want to force Jaeger to trace a particular operation. See the Jaeger Python client documentation for more information. To view the traces your application captures, use the Jaeger Getting Started to run the Jaeger infrastructure and console.

Commands:
sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm sudo yum install python2-pip pip install --user --upgrade setuptools pip install --user opentracing jaeger-client
sudo dnf install python3-pip pip3 install --user opentracing jaeger-client
from proton.tracing import init_tracer tracer = init_tracer(" <service-name> ")
10.2.4.7. The mod_python Module Configuration for mod_python has moved from httpd.conf to the /etc/httpd/conf.d/python.conf file. For this file to be loaded, and hence for mod_python to work, the statement Include conf.d/*.conf must be in httpd.conf as described in Section 10.2.1.3, "Dynamic Shared Object (DSO) Support" .

Commands:
3.11. Software Collection /var/run/ Files Support PID files are one example of files usually located underneath the /var/run/ package_name / directory. When packaging PID files into your Software Collection, you are advised to use the nfsmountable macro and store the PID files in the following directory: where software_collection is the name of your Software Collection and package_name is the name of the package included in your Software Collection. Following this naming convention avoids file conflicts with the base system installation, while it makes it possible for your Software Collection to use /var/run/ features, for example the tmpfs file system for PID files. For more information on using the nfsmountable macro, see Section 3.1, "Using Software Collections over NFS" .

Commands:
/var/run/ software_collection - package_name /
5.9. Port Forwarding Using firewalld , you can set up ports redirection so that any incoming traffic that reaches a certain port on your system is delivered to another internal port of your choice or to an external port on another machine. 5.9.1. Adding a Port to Redirect Before you redirect traffic from one port to another port, or another address, you need to know three things: which port the packets arrive at, what protocol is used, and where you want to redirect them. To redirect a port to another port: To redirect a port to another port at a different IP address: Add the port to be forwarded: Enable masquerade: Example 5.1. Redirecting TCP Port 80 to Port 88 on the Same Machine To redirect the port: Redirect the port 80 to port 88 for TCP traffic: Make the new settings persistent: Check that the port is redirected: 5.9.2. Removing a Redirected Port To remove a redirected port: To remove a forwarded port redirected to a different address: Remove the forwarded port: Disable masquerade: Note Redirecting ports using this method only works for IPv4-based traffic. For IPv6 redirecting setup, you need to use rich rules. For more information, see Section 5.15, "Configuring Complex Firewall Rules with the "Rich Language" Syntax" . To redirect to an external system, it is necessary to enable masquerading. For more information, see Section 5.10, "Configuring IP Address Masquerading" . Example 5.2. Removing TCP Port 80 forwarded to Port 88 on the Same Machine To remove the port redirection: List redirected ports: Remove the redirected port from the firewall:: Make the new settings persistent:

Commands:
~]# firewall-cmd --add-forward-port=port= port-number :proto= tcp|udp|sctp|dccp :toport= port-number
~]# firewall-cmd --add-forward-port=port= port-number :proto= tcp|udp :toport= port-number :toaddr= IP
~]# firewall-cmd --add-masquerade
~]# firewall-cmd --add-forward-port=port=80:proto=tcp:toport=88
~]# firewall-cmd --runtime-to-permanent
~]# firewall-cmd --list-all
~]# firewall-cmd --remove-forward-port=port= port-number :proto=<tcp|udp>:toport= port-number :toaddr=<IP>
~]# firewall-cmd --remove-forward-port=port= port-number :proto=<tcp|udp>:toport= port-number :toaddr=<IP>
~]# firewall-cmd --remove-masquerade
~]# firewall-cmd --list-forward-ports port=80:proto=tcp:toport=88:toaddr=
~]# firewall-cmd --remove-forward-port=port=80:proto=tcp:toport=88:toaddr=
~]# firewall-cmd --runtime-to-permanent
Chapter 5. Deploying and updating an overcloud with containers This chapter provides info on how to create a container-based overcloud and keep it updated. 5.1. Deploying an overcloud This procedure demonstrates how to deploy an overcloud with minimum configuration. The result will be a basic two-node overcloud (1 Controller node, 1 Compute node). Procedure Source the stackrc file: Run the deploy command and include the file containing your overcloud image locations (usually overcloud_images.yaml ): Wait until the overcloud completes deployment. 5.2. Updating an overcloud For information on updating a containerized overcloud, see the Keeping Red Hat OpenStack Platform Updated guide.

Commands:
source ~/stackrc
(undercloud) USD openstack overcloud deploy --templates -e /home/stack/templates/overcloud_images.yaml --ntp-server pool.ntp.org
6.4. Additional Resources This section includes various resources that can be used to learn more about account and resource management, and the Red Hat Enterprise Linux-specific subject matter discussed in this chapter. 6.4.1. Installed Documentation The following resources are installed in the course of a typical Red Hat Enterprise Linux installation and can help you learn more about the subject matter discussed in this chapter. User Management Tool Help menu entry - Learn how to manage user accounts and groups. passwd(5) man page - Learn more about the file format information for the /etc/passwd file. group(5) man page - Learn more about the file format information for the /etc/group file. shadow(5) man page - Learn more about the file format information for the /etc/shadow file. useradd(8) man page - Learn how to create or update user accounts. userdel(8) man page - Learn how to delete user accounts. usermod(8) man page - Learn how to modify user accounts. passwd(1) man page - Learn how to update a user's password. chpasswd(8) man page - Learn how to update many users' passwords at one time. chage(1) man page - Learn how to change user password aging information. chfn(1) man page - Learn how to change a user's GECOS ( finger ) information. chsh(1) man page - Learn how to change a user's login shell. groupadd(8) man page - Learn how to create a new group. groupdel(8) man page - Learn how to delete a group. groupmod(8) man page - Learn how to modify a group. gpasswd(1) man page - Learn how to administer the /etc/group and /etc/gshadow files. grpck(1) man page - Learn how to verify the integrity of the /etc/group and /etc/gshadow files. chgrp(1) man page - Learn how to change group-level ownership. chmod(1) man page - Learn how to change file access permissions. chown(1) man page - Learn how to change file owner and group.

Commands:
Chapter 1. Introduction 1.1. What is in This Guide? This guide provides information on installing virtualization software and configuring guest machines on a Red Hat Enterprise Linux virtualization host. The initial chapters in this guide outline the prerequisites to enable a Red Hat Enterprise Linux host machine to deploy virtualization. System requirements, compatible hardware, support and product restrictions are covered in detail. Basic host configuration, including mandatory and optional virtualization packages, are covered in Chapter 5, Installing the Virtualization Packages . Guest virtual machine installation is covered in detail starting from Chapter 6, Guest Virtual Machine Installation Overview , with procedures for installing fully virtualized Red Hat Enterprise Linux guests and Windows paravirtualized guests using virt-manager and virsh. More detailed information on networking, PCI device configuration, SR-IOV, KVM guest timing management, and troubleshooting help for libvirt and SR-IOV is included later in the guide. Note This book provides guidance for virtualization host configuration and guest installation. For more detailed system configuration information, refer to the Red Hat Enterprise Linux - Virtualization Administration Guide .

Commands:
2.5. RHEA-2011:0562 - new package: ding-libs New ding-libs packages are now available for Red Hat Enterprise Linux 6. Ding-libs is a set of helpful libraries used by SSSD and other projects. Ding-libs provides utility functions to manipulate filesystem pathnames (libpath_utils), a hash table which dynamically resizes to achieve optimal storage and access time properties (libdhash), a data type to collect data in a hierarchical structure for easy iteration and serialization (libcollection), a dynamically growing, reference-counted array (libref_array), and a library to process configuration files in initialization format (INI) into a library collection data structure (libini_config). This enhancement update adds the ding-libs packages to Red Hat Enterprise Linux 6. (BZ# 644073 ) All users requiring ding-libs are advised to install these new packages.

Commands:
A.2.4. The dmsetup deps Command The dmsetup deps device command provides a list of (major, minor) pairs for devices referenced by the mapping table for the specified device. If you do not specify a device name, the output is information about all of the currently configured Device Mapper devices. The following example shows the command to list the dependencies of all currently configured mapped devices. The following example shows the command to list the dependencies only of the device lock_stress-grant--02.1722 :

Commands:
dmsetup deps testgfsvg-testgfslv3: 1 dependencies : (8, 16) testgfsvg-testgfslv2: 1 dependencies : (8, 16) testgfsvg-testgfslv1: 1 dependencies : (8, 16) VolGroup00-LogVol01: 1 dependencies : (8, 2) VolGroup00-LogVol00: 1 dependencies : (8, 2)
dmsetup deps lock_stress-grant--02.1722 3 dependencies : (253, 33) (253, 32) (253, 31)
10.5.21. DocumentRoot DocumentRoot is the directory which contains most of the HTML files which are served in response to requests. The default DocumentRoot , for both the non-secure and secure Web servers, is the /var/www/html directory. For example, the server might receive a request for the following document: The server looks for the following file in the default directory: To change the DocumentRoot so that it is not shared by the secure and the non-secure Web servers, refer to Section 10.8, "Virtual Hosts" .

Commands:
http://example.com/foo.html
/var/www/html/foo.html
B.2. Pacemaker Installation in Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 Red Hat Enterprise Linux 6.5 and later releases support cluster configuration with Pacemaker, using the pcs configuration tool. There are, however, some differences in cluster installation between Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 when using Pacemaker. The following commands install the Red Hat High Availability Add-On software packages that Pacemaker requires in Red Hat Enterprise Linux 6 and prevent corosync from starting without cman . You must enter these commands on each node in the cluster. On each node in the cluster, you set up a password for the pcs administration account named hacluster , and you start and enable the pcsd service. On one node in the cluster, you then authenticate the administration account for the nodes of the cluster. In Red Hat Enterprise Linux 7, you run the following commands on each node in the cluster to install the Red Hat High Availability Add-On software packages that Pacemaker requires, set up a password for the pcs administration account named hacluster , and start and enable the pcsd service, In Red Hat Enterprise Linux 7, as in Red Hat Enterprise Linux 6, you authenticate the administration account for the nodes of the cluster by running the following command on one node in the cluster. For further information on installation in Red Hat Enterprise Linux 7, see Chapter 1, Red Hat High Availability Add-On Configuration and Management Reference Overview and Chapter 4, Cluster Creation and Administration .

Commands:
yum install pacemaker cman pcs chkconfig corosync off chkconfig cman off
passwd hacluster service pcsd start chkconfig pcsd on
pcs cluster auth [ node ] [...] [-u username ] [-p password ]
yum install pcs pacemaker fence-agents-all passwd hacluster systemctl start pcsd.service systemctl enable pcsd.service
pcs cluster auth [ node ] [...] [-u username ] [-p password ]
3.3. Domain XML Configuration The host-based configuration of each KVM guest virtual machine (also referred to as a domain ) is stored in the guest's XML configuration (or domain XML ). This includes the settings for virtual hardware, boot options, resource allocation, network interfaces, and more. Using an application or utility that persistently modifies a guest property, such as virsh setmem , writes this change into the guest's XML configuration, which the hypervisor then reads when booting the guest and modifies the virtual machine accordingly. To display the XML configuration of a specific guest, use the virsh dumpxml guestname command. To edit the XML configuration of a guest, use one of the following: The virsh commands - Persistent changes made to a guest virtual machine using virsh commands are recorded in the domain XML. The virt-xml command - This command configures the domain XML file of a specified guest according to the provided options. The Virtual Machine Manager - Changes made to a guest virtual machine in the Virtual Machine Manager are recorded in the domain XML. Note For the rare cases in which the domain XML files must be edited directly, use the virsh edit guestname . This command opens the domain XML configuration of the specified guest in the text editor determined by root's bash configuration, by default vi . To change the editor for virsh edit , set or modify the EDITOR variable in the .bashrc file of the intended user. For example, for the root user, this file is located in the /root/ directory. For the modifications performed using virsh edit to take effect, save the edited XML configuration and restart the guest. Warning Do not edit the XML configuration of a guest by opening it as a file in a text editor, for example by using gedit /etc/libvirt/qemu/guestname.xml . Changes made this way do not take effect and are automatically overwritten. For detailed information on domain XML configuration files, see the Virtualization Deployment and Administration Guide .

Commands: