mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix C. Ceph firewall ports These are the general firewall ports used by various components in Red Hat Ceph Storage. Port Port type Component 3260 and 5000 TCP Ceph iSCSI Gateway (Deprecated) 6800-7300 TCP Ceph OSDs 3300 TCP Ceph clients and Ceph daemons connecting to the Ceph Monitor daemon. This port is preferred over 6789. 6789 TCP Ceph clients and Ceph daemons connecting to the Ceph Monitor daemon. This port is considered if port 3300 fails.

Commands:
17.15. Creating Tunnels This section will demonstrate how to implement different tunneling scenarios. 17.15.1. Creating Multicast Tunnels A multicast group is setup to represent a virtual network. Any guest virtual machines whose network devices are in the same multicast group can talk to each other even across host physical machines. This mode is also available to unprivileged users. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first four network types thus providing appropriate routing. The multicast protocol is compatible the guest virtual machine user mode. Note that the source address that you provide must be from the address used for the multicast address block. To create a multicast tunnel place the following XML details into the <devices> element: ... <devices> <interface type='mcast'> <mac address='52:54:00:6d:90:01'> <source address='230.0.0.1' port='5558'/> </interface> </devices> ... Figure 17.28. Multicast tunnel domain XMl example 17.15.2. Creating TCP Tunnels A TCP client-server architecture provides a virtual network. In this configuration, one guest virtual machine provides the server end of the network while all other guest virtual machines are configured as clients. All network traffic is routed between the guest virtual machine clients via the guest virtual machine server. This mode is also available for unprivileged users. Note that this mode does not provide default DNS or DHCP support and it does not provide outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first four network types thus providing appropriate routing. To create a TCP tunnel place the following XML details into the <devices> element: ... <devices> <interface type='server'> <mac address='52:54:00:22:c9:42'> <source address='192.168.0.1' port='5558'/> </interface> ... <interface type='client'> <mac address='52:54:00:8b:c9:51'> <source address='192.168.0.1' port='5558'/> </interface> </devices> ... Figure 17.29. TCP tunnel domain XMl example

Commands:
<devices> <interface type='mcast'> <mac address='52:54:00:6d:90:01'> <source address='230.0.0.1' port='5558'/> </interface> </devices>
<devices> <interface type='server'> <mac address='52:54:00:22:c9:42'> <source address='192.168.0.1' port='5558'/> </interface> <interface type='client'> <mac address='52:54:00:8b:c9:51'> <source address='192.168.0.1' port='5558'/> </interface> </devices>
Chapter 6. Configuring the heap size for Red Hat build of OpenJDK application on RHEL You can configure Red Hat build of OpenJDK to use a customized heap size. Procedure Add the maximum heap size option to the java command when running your application. For example, to set the maximum heap size to 100 megabytes, use the -Xmx100m option: Additional resources For more information about the Xmx option, see -Xmxsize in the Java documentation . Revised on 2024-05-09 16:46:06 UTC

Commands:
java -Xmx100m <your_application_name>
14.3. Using OpenSSH Certificate Authentication 14.3.1. Introduction to SSH Certificates Using public key cryptography for authentication requires copying the public key from every client to every server that the client intends to log into. This system does not scale well and can be an administrative burden. Using a public key from a certificate authority ( CA ) to authenticate client certificates removes the need to copy keys between multiple systems. While the X.509 Public Key Infrastructure Certificate system provides a solution to this issue, there is a submission and validation process, with associated fees, to go through in order to get a certificate signed. As an alternative, OpenSSH supports the creation of simple certificates and associated CA infrastructure. OpenSSH certificates contain a public key, identity information, and validity constraints. They are signed with a standard SSH public key using the ssh-keygen utility. The format of the certificate is described in /usr/share/doc/openssh- version /PROTOCOL.certkeys . The ssh-keygen utility supports two types of certificates: user and host. User certificates authenticate users to servers, whereas host certificates authenticate server hosts to users. For certificates to be used for user or host authentication, sshd must be configured to trust the CA public key.

Commands:
Preface Two-factor authentication adds an additional layer of security to the login process. In addition to a Red Hat login and a strong password, a one-time code is required to complete the login action. One-time codes generated by an authentication application on a smart phone. Recovery code authentication generates a list of one-time codes that you can use as a backup if your authentication application is not available. Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message .

Commands:
Chapter 2. Preparing a RHEL 6 system for the upgrade This procedure describes the steps that are necessary before performing an in-place upgrade to RHEL 7. Prerequisites You have verified that your system setup can be upgraded from RHEL 6 to RHEL 7. See Planning an upgrade for more information. Procedure Ensure that your system is registered to Red Hat Subscription Management (RHSM) . If your RHEL 6 system is registered to Red Hat Network (RHN), you must migrate to RHSM. See Migrating from RHN to RHSM in Red Hat Enterprise Linux for details. Ensure that you have access to the latest RHEL 6 content. If you use the yum-plugin-versionlock plug-in to lock packages to a specific version, clear the lock: See How to restrict yum to install or upgrade a package to a fixed specific package version? for more information. Enable the Extras repository, which contains necessary packages for a pre-upgrade assessment and an in-place upgrade. For the Server variant on the 64-bit Intel architecture on server edition: For IBM POWER, big endian systems: For the IBM Z architecture: For the HPC Compute Node variant on the 64-bit Intel architecture: Install the Preupgrade Assistant and Red Hat Upgrade Tool: Note If your system does not have internet access, you can download the Preupgrade Assistant and Red Hat Upgrade Tool from the Red Hat Customer Portal . For more information, see How to install preupgrade assessment packages on an offline system for RHEL 6.10 to RHEL 7.9 upgrade . Remove all unsupported package groups: Replace group_name with each unsupported group name. To locate a list of installed group names, run yum grouplist . Check Known Issues and apply workarounds where applicable. Especially, on systems with multiple network interfaces: If the system has static routes configured, replace the static route file. See redhat-upgrade-tool fails to reconfigure the static routes on the network interfaces, preventing the upgrade to happen for more information. If the system runs NetworkManager , stop NetworkManager prior to running the upgrade tool. See redhat-upgrade-tool fails to reconfigure the network interfaces, preventing the upgrade to happen for more information. Update all packages to their latest RHEL 6 version: Reboot the system: Back up all your data before performing the upgrade to prevent potential data loss. Verification Verify that you are registered with the Red Hat Subscription Manager: The Loaded plug-ins: entry must contain subscription-manager . Verify that only supported package groups are installed:

Commands:
yum versionlock clear
subscription-manager repos --enable rhel-6-server-extras-rpms --enable rhel-6-server-optional-rpms
subscription-manager repos --enable rhel-6-for-power-extras-rpms --enable rhel-6-for-power-optional-rpms
subscription-manager repos --enable rhel-6-for-system-z-extras-rpms --enable rhel-6-for-system-z-optional-rpms
subscription-manager repos --enable rhel-6-for-hpc-node-extras-rpms --enable rhel-6-for-hpc-node-optional-rpms
yum install preupgrade-assistant preupgrade-assistant-el6toel7 redhat-upgrade-tool
yum groupremove group_name
yum update
reboot
yum update
yum grouplist
6.4. Configuring the Caller Identity Login Module Procedure 6.1. Configure the Caller Identity Login Module Create the Login Module Configure authentication modules using the Management Console according to the following specification: Configure the Data Source Configure the datasource according to the following specification. Configure the Connection Factory Configure the resource adapter according to the following specification: Result When a user logs in with a password, the same password will also be set on the logged in Subject after authentication. These credentials can be extracted by the data source by asking for Subject's private credentials.

Commands:
<security-domain name="my-security-domain" cache-type="default"> <authentication> <login-module code="org.picketbox.datasource.security.CallerIdentityLoginModule" module="org.picketbox" flag="required"> <module-option name="password-stacking" value="useFirstPass"/> <module-option name="userName" value="guest"/> <module-option name="password" value="guest"/> </login-module> </authentication> </security-domain>
<datasource jndi-name="java:/mysql-ds" pool-name="mysql-ds" enabled="true"> <connection-url>jdbc:mysql://localhost:3306/txns</connection-url> <driver>mysql</driver> <pool><allow-multiple-users/></pool> <security> <security-domain>my-security-domain</security-domain> </security> </datasource>
<resource-adapter> <archive>teiid-connector-ldap.rar</archive> <transaction-support>NoTransaction</transaction-support> <connection-definitions> <connection-definition class-name="org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory" jndi-name="java:/ldapDS" enabled="true" use-java-context="true" pool-name="ldap-ds"> <config-property name="LdapUrl">ldap://ldapServer:389</config-property> <config-property name="LdapAdminUserDN">cn=???,ou=???,dc=???</config-property> <config-property name="LdapAdminUserPassword">pass</config-property> <config-property name="LdapTxnTimeoutInMillis">-1</config-property> <security> <security-domain>my-security-domain</security-domain> </security> </connection-definition> </connection-definitions> </resource-adapter>
2.6. Testing the Configuration The specifics of a procedure for testing your cluster configuration will depend on the high availability application you are running in the cluster, but in general you can check whether the application is running and whether it fails over as follows. Verify that the service you created is running with the clustat command, which you can run on either cluster node. In this example, the service example_apache is running on node1.example.com . Check whether the service is operational. How you do this depends on the application. For example, if you are running an Apache web server, point a browser to the URL you defined for the server to see if the display is correct. Shut down the cluster software on the node on which the service is running, which you can determine from the clustat display. Click on the cluster name beneath Manage Clusters from the menu on the left side of the luci Homebase page. This displays the nodes that constitute the cluster. Select the node you want to leave the cluster by clicking the check box for that node. Select the Leave Cluster function from the menu at the top of the page. This causes a message to appear at the top of the page indicating that the node is being stopped. Refresh the page to see the updated status of the node. Run the clustat command again to see if the service is now running on the other cluster node. If it is, check again to see if the service is still operational. For example, if you are running an apache web server, check whether you can still display the website. Make sure you have the node you disabled rejoin the cluster by returning to the cluster node display, selecting the node, and selecting Join Cluster .

Commands:
clustat Cluster Status for exampleHA @ Thu Sep 29 12:17:39 2011 Member Status: Quorate Member Name ID Status ------ ---- ---- ------ node1.example.com 1 Online, Local node2.example.com 2 Online Service Name Owner (Last) State ------ ---- ----- ------ ----- service:example_apache node-01.example.com started
Chapter 4. Important links Red Hat AMQ 7 Supported Configurations Red Hat AMQ 7 Component Details AMQ Clients 2.9 Release Notes AMQ Clients 2.8 Release Notes AMQ Clients 2.7 Release Notes AMQ Clients 2.6 Release Notes AMQ Clients 2.5 Release Notes AMQ Clients 2.4 Release Notes AMQ Clients 2.3 Release Notes AMQ Clients 2.2 Release Notes AMQ Clients 2.1 Release Notes AMQ Clients 2.0 Release Notes AMQ Clients 1.2 Release Notes AMQ Clients 1.1 Release Notes Revised on 2022-09-09 13:59:27 UTC

Commands:
Chapter 3. API configuration examples 3.1. external_registry_config object reference { "is_enabled": True, "external_reference": "quay.io/redhat/quay", "sync_interval": 5000, "sync_start_date": datetime(2020, 0o1, 0o2, 6, 30, 0), "external_registry_username": "fakeUsername", "external_registry_password": "fakePassword", "external_registry_config": { "verify_tls": True, "unsigned_images": False, "proxy": { "http_proxy": "http://insecure.proxy.corp", "https_proxy": "https://secure.proxy.corp", "no_proxy": "mylocalhost", }, }, } 3.2. rule_rule object reference { "root_rule": {"rule_kind": "tag_glob_csv", "rule_value": ["latest", "foo", "bar"]}, }

Commands:
{ "is_enabled": True, "external_reference": "quay.io/redhat/quay", "sync_interval": 5000, "sync_start_date": datetime(2020, 0o1, 0o2, 6, 30, 0), "external_registry_username": "fakeUsername", "external_registry_password": "fakePassword", "external_registry_config": { "verify_tls": True, "unsigned_images": False, "proxy": { "http_proxy": "http://insecure.proxy.corp", "https_proxy": "https://secure.proxy.corp", "no_proxy": "mylocalhost", }, }, }
{ "root_rule": {"rule_kind": "tag_glob_csv", "rule_value": ["latest", "foo", "bar"]}, }
Chapter 18. Running Red Hat Process Automation Manager Use this procedure to run Red Hat Process Automation Manager on Red Hat JBoss EAP in standalone mode. Prerequisites Red Hat Process Automation Manager is installed and configured. Note If you changed the default host ( localhost ) or the default port ( 9990 ), then before you run Red Hat Process Automation Manager, you must edit the business-central.war/WEB-INF/classes/datasource-management.properties and business-central.war/WEB-INF/classes/security-management.properties files as described in Solution 3519551 . Procedure In a terminal application, navigate to EAP_HOME /bin . Run the standalone configuration: On Linux or UNIX-based systems: USD ./standalone.sh -c standalone-full.xml On Windows: standalone.bat -c standalone-full.xml Note If you deployed Business Central without KIE Server, you can start Business Central with the standalone.sh script without specifying the standalone-full.xml file. In this case, ensure that you make any configuration changes to the standalone.xml file before starting Business Central. On Linux or UNIX-based systems: On Windows: standalone.bat In a web browser, open the URL localhost:8080/business-central . If you configured Red Hat Process Automation Manager to run from a domain name, replace localhost with the domain name, for example: http://www.example.com:8080/business-central Log in using the credentials of the user that you created for Business Central in Section 14.4, "Creating users" .

Commands:
./standalone.sh -c standalone-full.xml
standalone.bat -c standalone-full.xml
./standalone.sh
standalone.bat
Appendix A. New features of RPM in RHEL 7 This list documents most noticable changes in RPM packaging between Red Hat Enterprise Linux 6 and 7. A new command, rpmkeys , used for keyring import and signature verification has been added. A new command, rpmspec , used for spec queries and parsed output has been added. A new command, rpmsign , used for package signing has been added. The posix.exec() and os.exit() extensions embedded in %{lua:... } scripts fail the script unless called from a child process created with the posix.fork() scriptlet. The %pretrans scriptlet failure causes the package installation to be skipped. Scriptlets can be macro-expanded and queryformat-expanded at runtime. Pre-transaction and post-transaction scriptlet dependencies can now be correctly expressed with Requires(pretrans) and Requires(posttrans) scriptlets. The OrderWithRequires tag for supplying additional ordering hints has been added. The tag follows Requires tag syntax, but does not generate actual dependencies. The ordering hints are treated as if they were Requires when calculating the transaction order, only if the involved packages are present in the same transaction. The %license flag can be used in the %files section. This flag can be used similar to the %doc flag to mark files as licenses, which need to be installed despite the --nodocs option. The %autosetup macro for automating patch application, with optional distributed version control system integration has been added. The automatic dependency generator has been rewritten into extensible and customizable rule based system with built-in filtering. The OpenPGP V3 public keys are no longer supported.

Commands:
B.8. cluster B.8.1. RHBA-2011:1178 - cluster and gfs2-utils bug fix update Updated cluster and gfs2-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The cluster packages contain the core clustering libraries for Red Hat High Availability as well as utilities to maintain GFS2 file systems for users of Red Hat Resilient Storage. Bug Fix BZ# 681027 Due to an incorrect call of a function from the libxml2 library, each update of cluster configuration caused the configuration library to leak a small amount of memory. This update applies a patch that removes this incorrect function call, and updating cluster configuration no longer leads to memory leaks. All users of Red Hat High Availability and Red Hat Resilient Storage are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Overview of Red Hat Certificate System Subsystems Every common PKI operation - issuing, renewing and revoking certificates; archiving and recovering keys; publishing CRLs and verifying certificate status - are carried out by interoperating subsystems within Red Hat Certificate System. The functions of each individual subsystem and the way that they work together to establish a robust and local PKI is described in this chapter. 1.1. Uses for Certificates The purpose of certificates is to establish trust. Their usage varies depending on the kind of trust they are used to ensure. Some kinds of certificates are used to verify the identity of the presenter; others are used to verify that an object or item has not been tampered with. For information on how certificates are used, the types of certificates, or how certificates establish identities and relationships, see the Certificates and Authentication section in the Red Hat Certificate System Planning, Installation, and Deployment Guide .

Commands:
7.152. mt-st 7.152.1. RHBA-2012:1409 - mt-st bug fix update Updated mt-st packages that fix one bug are now available for Red Hat Enterprise Linux 6. The mt-st package contains the mt and st tape drive management programs. Mt (for magnetic tape drives) and st (for SCSI tape devices) can control rewinding, ejecting, skipping files and blocks and more. Bug Fix BZ#820245 Prior this update, the stinit init script did not support standard actions like "status" or "restart". As a consequence, an error code was returned. This update modifies the underlying code to use all use all standard actions. All users of mt-st are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 4. Designing the Directory Tree The directory tree provides a way to see the data stored by the directory service. The types of information stored in the directory, the physical nature of the enterprise, the applications used with the directory, and the types of replication implemented shape the design of the directory tree. This chapter outlines the steps for designing the directory tree. 4.1. Introduction to the Directory Tree The directory tree provides a means for the directory data to be named and referred to by client applications. The directory tree interacts closely with other design decisions, including the choices available distributing, replicating, or controlling access to the directory data. Invest time to properly design the directory tree before deployment. A properly designed directory tree can save considerable time and effort both during the deployment phase, and later when the directory service is in operation. A well-designed directory tree provides the following: Simplified directory data maintenance. Flexibility in creating replication policies and access controls. Support for the applications using the directory service. Simplified directory navigation for directory users. The structure of the directory tree follows the hierarchical LDAP model. A directory tree provides a way to organize the data in different logical ways, such as by group, personnel, or place. It also determines how to partition data across multiple servers. For example, each database needs data to be partitioned at the suffix level. Without the proper directory tree structure, it may not be able to spread the data across multiple servers efficiently. In addition, replication is constrained by the type of directory tree structure used. Carefully define partitions for replication to work. To replicate only portions of the directory tree, take that into account during the design process. To use access controls on branch points, also consider that in the directory tree design. Note Directory Server supports a concept for hierarchical navigation and organization of directory information called virtual directory information tree views. See Section 4.4, "Virtual Directory Information Tree Views" before designing the directory tree.

Commands: