mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 8. Configuring kdump in the web console The following sections provide an overview of how to setup and test the kdump configuration through the Red Hat Enterprise Linux web console. The web console enables or disables the kdump service at boot time. Further, the web console conveniently enables you to configure the reserved memory for kdump ; or to select the vmcore saving location in an uncompressed or compressed format. Prerequisites See Red Hat Enterprise Linux web console for further details. 8.1. Configuring kdump memory usage and target location in web console The procedure below shows you how to use the Kernel Dump tab in the Red Hat Enterprise Linux web console interface to configure the amount of memory that is reserved for the kdump kernel. The procedure also describes how to specify the target location of the vmcore dump file and how to test your configuration. Prerequisites Introduction to operating the web console Procedure Open the Kernel Dump tab and start the kdump service. Configure the kdump memory usage through the command line . Click the link to the Crash dump location option. Select the Local Filesystem option from the drop-down and specify the directory you want to save the dump in. Alternatively, select the Remote over SSH option from the drop-down to send the vmcore to a remote machine using the SSH protocol. Fill the Server , ssh key , and Directory fields with the remote machine address, ssh key location, and a target directory. Another choice is to select the Remote over NFS option from the drop-down and fill the Mount field to send the vmcore to a remote machine using the NFS protocol. Note Tick the Compression check box to reduce the size of the vmcore file. Test your configuration by crashing the kernel. Warning This step disrupts execution of the kernel and results in a system crash and loss of data. Additional resources For a complete list of currently supported targets for kdump , see Supported kdump targets . For information on how to configure an SSH server and set up a key-based authentication, see Configuring basic system settings in Red Hat Enterprise Linux.

Commands:
8.5.2. Useful Websites http://www.redhat.com/apps/support/ -- The Red Hat support homepage provides easy access to various resources related to the support of Red Hat Enterprise Linux. http://www.disasterplan.com/ -- An interesting page with links to many sites related to disaster recovery. Includes a sample disaster recovery plan. http://web.mit.edu/security/www/isorecov.htm -- The Massachusetts Institute of Technology Information Systems Business Continuity Planning homepage contains several informative links. http://www.linux-backup.net/ -- An interesting overview of many backup-related issues. http://www.linux-mag.com/1999-07/guru_01.html -- A good article from Linux Magazine on the more technical aspects of producing backups under Linux. http://www.amanda.org/ -- The Advanced Maryland Automatic Network Disk Archiver (AMANDA) homepage. Contains pointers to the various AMANDA-related mailing lists and other online resources.

Commands:
Chapter 1. Introduction to Red Hat OpenShift bare-metal hardware certification policies The Red Hat OpenShift Container Platform (RHOCP) bare metal hardware certification policy guide is for hardware vendors who want to certify their bare metal servers with Red Hat. The RHOCP bare-metal certification is divided in the following components: The IPI component, which ensures that your servers can be automatically orchestrated without manual intervention. The Assisted installer component, which ensures that customers can install your servers with the assisted installer for RHOCP. If the servers meet the requirements, you can certify them for the IPI component by deploying it on the Red Hat OpenShift Container Platform through this program. 1.1. Audience This guide is intended for partners who offer their own infrastructure hardware like system servers, or management controllers for use with RHOCP in a supported customer environment. 1.2. Overview of the program The Red Hat OpenShift Container Platform (RHOCP) bare metal hardware certification creates value for customers, because the systems can be managed and automatically deployed and redeployed with RHOCP bare-metal hardware without manual intervention. The certification process, through a series of tests, validates that a certified solution meets the requirements of an enterprise cloud, and is jointly supported by Red Hat and your organization. The RHOCP bare-metal hardware certification program policies include multiple tests each with a series of subtests and checks, which are explained in the document.

Commands:
10.5. Cloning KRA Subsystems Configure the master subsystem and back up the keys. Create the clone subsystem instance using the pkispawn utility: An example of the configuration file required by pkispawn when cloning KRA subsystems: Restart the Directory Server instance used by the clone. Note Restarting the Directory Server reloads the updated schema, which is required for proper performance. Restart the clone instance. For the KRA clone, test to make sure that the master-clone relationship is functioning: Go to the KRA agent's page. Click List Requests . Select Show all requests for the request type and status. Click Submit . Compare the results from the cloned KRA and the master KRA. The results ought to be identical.

Commands:
pkispawn -s <subsystem> -f myconfig.txt
[DEFAULT] pki_admin_password= <Secret.123> pki_client_database_password= <Secret.123> pki_client_pkcs12_password= <Secret.123> pki_ds_password= <Secret.123> pki_security_domain_password= <Secret.123> pki_security_domain_hostname= <master_ca_hostname> pki_security_domain_https_port= <master_ca_https_port> pki_security_domain_user=caadmin [KRA] pki_clone=True pki_clone_pkcs12_password= <Secret.123> pki_clone_pkcs12_path= <path_to_pkcs12_file> pki_clone_replicate_schema=True pki_clone_uri=https:// <master_subsystem_host:master_subsystem_https_port> pki_issuing_ca=https:// <ca_hostname:ca_https_port>
systemctl dirsrv@ instance_name .service
pki-server restart instance_name
Chapter 1. Compatibility Matrix for Red Hat Ceph Storage 5.0 The following tables list products and their versions compatible with Red Hat Ceph Storage 5.0. Host Operating System Version Notes Red Hat Enterprise Linux 8.5, 8.4, and EUS 8.4 Standard lifecycle 8.5 is included in the product (recommended). Red Hat Enterprise Linux EUS is optional. Important All nodes in the cluster and their clients must use the supported OS version(s) to ensure that the version of the ceph package is the same on all nodes. Using different versions of the ceph package is not supported. Important Red Hat no longer supports using Ubuntu as a host operating system to deploy Red Hat Ceph Storage. Product Version Notes Ansible Supported in a limited capacity. Supported for upgrade and conversion to Cephadm and for other minimal playbooks. Red Hat OpenShift 3.x RBD,Cinder and CephFS drivers are supported. Red Hat OpenShift Data Foundation See the Red Hat OpenShift Data Foundation Supportability and Interoperability Checker for detailed external mode version compatibility. Red Hat OpenStack Platform 16.1 and 16.2 Red Hat OpenStack Platform 16.1z8 and 16.2z1 is supported with external Red Hat Ceph Storage 5.0. Red Hat Satellite 6.x Only registering with the Content Delivery Network (CDN) is supported. Registering with Red Hat Network (RHN) is deprecated and not supported. Client Connector Version Notes S3A 2.8.x, 3.2.x, and trunk Red Hat Enterprise Linux iSCSI Initiator The latest versions of the iscsi-initiator-utils and device-mapper-multipath packages VMware vSphere versions 6.7 and 7 are supported Red Hat Ceph Storage as a backup target Version Notes CommVault Cloud Data Management v11 IBM Spectrum Protect Plus 10.1.5 IBM Spectrum Protect server 8.1.8 NetApp AltaVault 4.3.2 and 4.4 Rubrik Cloud Data Management (CDM) 3.2 onwards Trilio, TrilioVault 3.0 S3 target Veeam (object storage) Veeam Availability Suite 9.5 Update 4 Supported on Red Hat Ceph Storage object storage with the S3 protocol Veritas NetBackup for Symantec OpenStorage (OST) cloud backup 7.7 and 8.0 Independent Software vendors Version Notes IBM Spectrum Discover 2.0.3 WekaIO 3.12.2

Commands:
Chapter 2. Red Hat Quay repository overview A repository provides a central location for storing a related set of container images. These images can be used to build applications along with their dependencies in a standardized format. Repositories are organized by namespaces. Each namespace can have multiple repositories. For example, you might have a namespace for your personal projects, one for your company, or one for a specific team within your organization. Private repositories provide control over the users that have access to your images by allowing you to define users or teams who can push to, or pull from, the repository, thereby enhancing the security of your registry. 2.1. Adjusting repository visibility by using the UI You can adjust the visibility of a repository to make it either public of private by using the Red Hat Quay UI. Procedure On the Red Hat Quay UI, click Repositories in the navigation pane. Click the name of a repository. Click Settings in the navigation pane. Click Repository visibility . Click Make private . The repository is made private, and only users on the permissions list can view and interact with it. 2.2. Adjusting repository visibility by using the API The visibility of your repository can be set to private or public by using the POST /api/v1/repository/{repository}/changevisibility command. Prerequisites You have Created an OAuth access token . You have set BROWSER_API_CALLS_XHR_ONLY: false in your config.yaml file. You have created a repository. Procedure You can change the visibility of your repository to public or private by specifying the desired option in the visibility schema. For example: USD curl -X POST \ -H "Authorization: Bearer GCczXwaZ5i21p8hOO09uZqjZSsTYGKteu5PC5UuA" \ -H "Content-Type: application/json" \ -d '{ "visibility": "private" }' \ "https://quay-server.example.com/api/v1/repository/my_namespace/test_repo_three/changevisibility" Example output {"success": true}

Commands:
curl -X POST -H "Authorization: Bearer GCczXwaZ5i21p8hOO09uZqjZSsTYGKteu5PC5UuA" -H "Content-Type: application/json" -d '{ "visibility": "private" }' "https://quay-server.example.com/api/v1/repository/my_namespace/test_repo_three/changevisibility"
success: yes
B.103.2. RHSA-2011:0013 - Moderate: wireshark security update Updated wireshark packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 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. Wireshark is a program for monitoring network traffic. Wireshark was previously known as Ethereal. CVE-2010-4538 An array index error, leading to a stack-based buffer overflow, was found in the Wireshark ENTTEC dissector. If Wireshark read a malformed packet off a network or opened a malicious dump file, it could crash or, possibly, execute arbitrary code as the user running Wireshark. Users of Wireshark should upgrade to these updated packages, which contain a backported patch to correct this issue. All running instances of Wireshark must be restarted for the update to take effect.

Commands:
7.181. perl 7.181.1. RHBA-2013:0444 - perl bug fix update Updated perl packages that fix one bug are now available for Red Hat Enterprise Linux 6. The perl packages provide the high-level programming language Perl, which is commonly used for system administration utilities and web programming. Bug Fix BZ# 720644 Prior to this update, computed Perl strings became corrupted or the interpreter could abort when a string with the "x" operator was repeated more than 2^31 times, for example, "my USDs = "a' x (2**31+1);". This limits the right side of the "x" operator to 2^31 to prevent it from wrapping the internal representation of the count. All users of perl are advised to upgrade to these updated packages, which fix this bug.

Commands:
2.6. Code Table Caching Red Hat JBoss Data Virtualization provides a short cut to creating an internal materialized view table via the lookup function. The lookup function provides a way to accelerate getting a value out of a table when a key value is provided. The function automatically caches all of the key/return pairs for the referenced table. This caching is performed on demand, but will proactively load the results to other members in a cluster. Subsequent lookups against the same table using the same key and return columns will use the cached information. This caching solution is appropriate for integration of "reference data" with transactional or operational data. Reference data is usually static and small data sets that are used frequently. Examples are ISO country codes, state codes, and different types of financial instrument identifiers. This caching mechanism is automatically invoked when the lookup scalar function is used. The lookup function returns a scalar value, so it may be used anywhere an expression is expected. Each time this function is called with a unique combination of referenced table, return column, and key column (the first three arguments to the function). Here is a lookup for country codes: Code table caching does have some limitations: The use of the lookup function automatically performs caching; there is no option to use the lookup function and not perform caching. No mechanism is provided to refresh code tables Only a single key/return column is cached - values will not be session/user specific. The lookup function is a shortcut to create an internal materialized view with an appropriate primary key. In many situations, it may be better to directly create the analogous materialized view rather than to use a code table. Here MatISOCountryCodes is a view selecting from ISOCountryCodes that has been marked as materialized and has a primary key and index on CountryName. The scalar subquery will use the index to lookup the country code for each country name in tbl. Here are some reasons why you should use a materialized view: More control of the possible return columns. Code tables will create a materialized view for each key/value pair. If there are multiple return columns it would be better to have a single materialized view. Proper materialized views have built-in system procedure/table support. More control via the cache hint. The ability to use OPTION NOCACHE. There is almost no performance difference.

Commands:
lookup('ISOCountryCodes', 'CountryCode', 'CountryName', 'United States')
SELECT (SELECT CountryCode From MatISOCountryCodes WHERE CountryName = tbl.CountryName) as cc FROM tbl
Chapter 17. Renaming, copying, or deleting assets After an asset has been created and defined, you can use the Repository View of the Project Explorer to copy, rename, delete, or archive assets as needed. Procedure In Business Central, go to Menu Design Projects and click the project name. Click the asset name and expand the Project Explorer by clicking on the upper-left corner. Click in the Project Explorer toolbar and select Repository View to display the folders and files that make up the asset. Use the icons to each listed asset to copy, rename, delete, or archive the asset as needed. Some of these options may not be available for all assets. Figure 17.1. Copy, rename, delete, or archive assets Use the following toolbar buttons to copy, rename, or delete assets. Figure 17.2. Toolbar options

Commands:
5.10. Configuring IP Address Masquerading IP masquerading is a process where one computer acts as an IP gateway for a network. For masquerading, the gateway dynamically looks up the IP of the outgoing interface all the time and replaces the source address in the packets with this address. You use masquerading if the IP of the outgoing interface can change. A typical use case for masquerading is if a router replaces the private IP addresses, which are not routed on the internet, with the public dynamic IP address of the outgoing interface on the router. To check if IP masquerading is enabled (for example, for the external zone), enter the following command as root : The command prints yes with exit status 0 if enabled. It prints no with exit status 1 otherwise. If zone is omitted, the default zone will be used. To enable IP masquerading, enter the following command as root : To make this setting persistent, repeat the command adding the --permanent option. To disable IP masquerading, enter the following command as root : To make this setting persistent, repeat the command adding the --permanent option. For more information, see: Section 6.3.1, "The different NAT types: masquerading, source NAT, destination NAT, and redirect" Section 6.3.2, "Configuring masquerading using nftables"

Commands:
~]# firewall-cmd --zone=external --query-masquerade
~]# firewall-cmd --zone=external --add-masquerade
~]# firewall-cmd --zone=external --remove-masquerade
1.4. Installing GFS2 In addition to the packages required for the Red Hat High Availability Add-On, you must install the gfs2-utils package for GFS2 and the lvm2-cluster package for the Clustered Logical Volume Manager (CLVM). The lvm2-cluster and gfs2-utils packages are part of ResilientStorage channel, which must be enabled before installing the packages. You can use the following yum install command to install the Red Hat High Availability Add-On software packages: For general information on the Red Hat High Availability Add-On and cluster administration, see the Cluster Administration manual.

Commands:
yum install lvm2-cluster gfs2-utils
Providing feedback on Red Hat documentation We appreciate your feedback on our documentation. To provide feedback, you can highlight the text in a document and add comments. This section explains how to submit feedback. Prerequisites You are logged in to the Red Hat Customer Portal. In the Red Hat Customer Portal, view the document in HTML format. Procedure To provide your feedback, perform the following steps: Click the Feedback button in the top-right corner of the document to see existing feedback. Note The feedback feature is enabled only in the HTML format. Highlight the section of the document where you want to provide feedback. Click the Add Feedback pop-up that appears near the highlighted text. A text box appears in the feedback section on the right side of the page. Enter your feedback in the text box and click Submit . A documentation issue is created. To view the issue, click the issue tracker link in the feedback view.

Commands:
Chapter 131. KafkaMirrorMakerTemplate schema reference Used in: KafkaMirrorMakerSpec Property Property type Description deployment DeploymentTemplate Template for Kafka MirrorMaker Deployment . pod PodTemplate Template for Kafka MirrorMaker Pods . podDisruptionBudget PodDisruptionBudgetTemplate Template for Kafka MirrorMaker PodDisruptionBudget . mirrorMakerContainer ContainerTemplate Template for Kafka MirrorMaker container. serviceAccount ResourceTemplate Template for the Kafka MirrorMaker service account.

Commands:
Chapter 3. Getting started This chapter guides you through the steps to set up your environment and run a simple messaging program. 3.1. Prerequisites You must complete the installation procedure for your environment. You must have an AMQP 1.0 message broker listening for connections on interface localhost and port 5672 . It must have anonymous access enabled. For more information, see Starting the broker . You must have a queue named examples . For more information, see Creating a queue . 3.2. Running Hello World The Hello World example creates a connection to the broker, sends a message containing a greeting to the examples queue, and receives it back. On success, it prints the received message to the console. Change to the examples directory and run the helloworld.rb example. USD cd /usr/share/proton/examples/ruby/ USD ruby helloworld.rb amqp://127.0.0.1 examples Hello World!

Commands:
cd /usr/share/proton/examples/ruby/ ruby helloworld.rb amqp://127.0.0.1 examples Hello World!
5.9.7.2. Enabling Disk Quotas Note The following sections provide a brief overview of the steps necessary to enable disk quotas under Red Hat Enterprise Linux. For a more in-depth treatment of this subject, see the chapter on disk quotas in the System Administrators Guide . To use disk quotas, you must first enable them. This process involves several steps: Modifying /etc/fstab Remounting the file system(s) Running quotacheck Assigning quotas The /etc/fstab file controls the mounting of file systems under Red Hat Enterprise Linux. Because disk quotas are implemented on a per-file-system basis, there are two options -- usrquota and grpquota -- that must be added to that file to enable disk quotas. The usrquota option enables user-based disk quotas, while the grpquota option enables group-based quotas. One or both of these options may be enabled by placing them in the options field for the desired file system. The affected file system(s) then must be unmounted and remounted for the disk quota-related options to take affect. , the quotacheck command is used to create the disk quota files and to collect the current usage information from already existing files. The disk quota files (named aquota.user and aquota.group for user- and group-based quotas) contain the necessary quota-related information and reside in the file system's root directory. To assign disk quotas, the edquota command is used. This utility program uses a text editor to display the quota information for the user or group specified as part of the edquota command. Here is an example: This shows that user matt is currently using over 6GB of disk space, and over 17,000 inodes. No quota (soft or hard) has yet been set for either disk blocks or inodes, meaning that there is no limit to the disk space and inodes that this user can currently use.. Using the text editor displaying the disk quota information, the system administrator can then modify the soft and hard limits as desired: In this example, user matt has been given a soft limit of 6.9GB and a hard limit of 7GB. No soft or hard limit on inodes has been set for this user. Note The edquota program can also be used to set the per-file-system grace period by using the -t option.

Commands:
Disk quotas for user matt (uid 500): Filesystem blocks soft hard inodes soft hard /dev/md3 6618000 0 0 17397 0 0
Disk quotas for user matt (uid 500): Filesystem blocks soft hard inodes soft hard /dev/md3 6618000 6900000 7000000 17397 0 0
Chapter 31. Customizing artifact repository properties In some cases, projects need to resolve external dependencies to build domain model JAR files. A repository contains the needed artifacts and has the following features: The repository is a Maven repository. All snapshots are time stamped. Assets are stored mostly in the local hard drive. By default, the artifact repository is in USDWORKING_DIRECTORY/repositories/kie . Procedure In Business Central, select the Admin icon in the top-right corner of the screen and select Artifact Repository . The Artifact Repository page opens. Make selections and enter information in the Properties section. Click Save .

Commands: