mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Installing Red Hat Gluster Storage Red Hat Gluster Storage can be installed in a data center using Red Hat Gluster Storage Server On-Premise. This chapter describes the three different methods for installing Red Hat Gluster Storage Server: using an ISO image, using a PXE server, or using the Red Hat Satellite Server. For information on launching Red Hat Gluster Storage Server for Public Cloud, see the Red Hat Gluster Storage Administration Guide . Warning Gluster-NFS is considered deprecated as of Red Hat Gluster Storage 3.5. Red Hat no longer recommends the use of Gluster-NFS, and does not support its use in new deployments and existing deployments that upgrade to Red Hat Gluster Storage 3.5.3. You can use NFS-Ganesha as an alternative. Important Technology preview packages will also be installed with this installation of Red Hat Gluster Storage Server. For more information about the list of technology preview features, see chapter Technology Previews in the Red Hat Gluster Storage 3.5 Release Notes . When you clone a virtual machine that has Red Hat Gluster Storage Server installed, you need to remove the /var/lib/glusterd/glusterd.info file (if present) before you clone. If you do not remove this file, all cloned machines will have the same UUID. The file will be automatically recreated with a UUID on initial start-up of the glusterd daemon on the cloned virtual machines. 2.1. Obtaining Red Hat Gluster Storage This chapter details the steps to obtain the Red Hat Gluster Storage software. 2.1.1. Obtaining Red Hat Gluster Storage Server for On-Premise Visit the Software & Download Center in the Red Hat Customer Service Portal ( https://access.redhat.com/downloads ) to obtain the Red Hat Gluster Storage Server for On-Premise installation ISO image files . Use a valid Red Hat Subscription to download the full installation files, obtain a free evaluation installation, or follow the links in this page to purchase a new Red Hat Subscription. To download the Red Hat Gluster Storage Server installation files using a Red Hat Subscription or a Red Hat Evaluation Subscription: Visit the Red Hat Customer Service Portal at https://access.redhat.com/login and enter your user name and password to log in. Click Downloads to visit the Software & Download Center . In the Red Hat Gluster Storage Server area, click Download Software to download the latest version of the software. 2.1.2. Obtaining Red Hat Gluster Storage Server for Public Cloud Red Hat Gluster Storage Server for Public Cloud is pre-integrated, pre-verified, and ready to run the Amazon Machine Image (AMI). This AMI provides a fully POSIX-compatible, highly available, scale-out NAS and object storage solution for the Amazon Web Services (AWS) public cloud infrastructure. For more information about obtaining access to AMI, see https://access.redhat.com/knowledge/articles/145693 .

Commands:
Release Notes Red Hat Ceph Storage 6.0 Release notes for Red Hat Ceph Storage 6.0 Red Hat Ceph Storage Documentation Team

Commands:
service_type: prometheus placement: count: 1 spec: retention_time: "1y" retention_size: "1GB"
If no embedded Grafana Dashboard appeared below, please follow this link to check if Grafana is reachable and there are no HTTPS certificate issues. You may need to reload this page after accepting any Browser certificate exceptions.
ceph config set mgr mgr/dashboard/cross_origin_url http://localhost:4200
time rgw-restore-bucket-index --proceed serp-bu-ver-1 default.rgw.buckets.data NOTICE: This tool is currently considered EXPERIMENTAL. `marker` is e871fb65-b87f-4c16-a7c3-064b66feb1c4.25076.5. `bucket_id` is e871fb65-b87f-4c16-a7c3-064b66feb1c4.25076.5. Error: this bucket appears to be versioned, and this tool cannot work with versioned buckets.
ceph config set osd osd_mclock_force_run_benchmark_on_init true
ceph config rm OSD. OSD_ID osd_mclock_max_capacity_iops_[hdd,ssd]
ceph config rm osd.0 osd_mclock_max_capacity_iops_hdd
Appendix A. Command-line utilities replaced in Red Hat Directory Server 11 The following table lists utilities in Directory Server 10 and earlier versions together with their replacements in Directory Server 11: Directory Server 10 and earlier Directory Server 11 bak2db bak2db.pl dsctl bak2db cl-dump cl-dump.pl dsconf replication dump-changelog cleanallruv.pl dsconf repl-tasks cleanallruv db2bak db2bak.pl dsctl db2bak db2index db2index.pl dsctl db2index db2ldif db2ldif.pl dsctl db2ldif dbgen dsctl ldifgen dbmon.sh dsconf monitor dbmon dbverify dsctl dbverify dn2rdn No replacement. fixup-linkedattrs.pl dsconf plugin linked-attr fixup fixup-memberof.pl dsconf plugin memberof fixup fixup-memberuid.pl dsconf plugin posix-winsync fixup infadd No replacement ldif No replacement ldif2db ldif2db.pl dsctl ldif2db ldif2ldap No replacement migrate-ds.pl No replacement migratecred No replacement mmldif No replacement monitor dsconf backend monitor dsconf backend monitor-suffix ns-accountstatus.pl dsidm user status ns-activate.pl dsidm user unlock ns-inactivate.pl dsidm user lock ns-newpwpolicy.pl dsconf localpwp adduser dsconf localpwp addsubtree remove-ds.pl dsctl remove repl-monitor repl-monitor.pl dsconf replication monitor restart-slapd dsctl restart restoreconfig No replacement rsearch ldclt saveconfig No replacement schema-reload.pl dsconf schema reload setup-ds.pl dscreate start-slapd dsctl start stop-slapd dsctl stop suffix2instance No replacement validate-syntax.pl dsconf schema validate-syntax upgradednformat No replacement usn-tombstone-cleanup.pl dsconf usn cleanup verify-db.pl No replacement vlvindex dsconf backend vlv-index

Commands:
C.4.6. Add the Mapping Information to /etc/crypttab In order for the system to set up a mapping for the device, an entry must be present in the /etc/crypttab file. If the file doesn't exist, create it and change the owner and group to root ( root:root ) and change the mode to 0744 . Add a line to the file with the following format: The <device> field should be given in the form "UUID=<luks_uuid>", where <luks_uuid> is the LUKS uuid as given by the command cryptsetup luksUUID <device> . This ensures the correct device will be identified and used even if the device node (eg: /dev/sda5 ) changes. Note For details on the format of the /etc/crypttab file, read the crypttab(5) man page.

Commands:
<name> <device> none
14.4.4. Active Directory Security Mode (User-Level Security) If you have an Active Directory environment, it is possible to join the domain as a native Active Directory member. Even if a security policy restricts the use of NT-compatible authentication protocols, the Samba server can join an ADS using Kerberos. Samba in Active Directory member mode can accept Kerberos tickets. In smb.conf , the following directives make Samba an Active Directory member server:

Commands:
[GLOBAL] security = ADS realm = EXAMPLE.COM password server = kerberos.example.com
5.5.2.2. Hierarchical Directory Structure While the file systems used in some very old operating systems did not include the concept of directories, all commonly-used file systems today include this feature. Directories are themselves usually implemented as files, meaning that no special utilities are required to maintain them. Furthermore, because directories are themselves files, and directories contain files, directories can therefore contain other directories, making a multi-level directory hierarchy possible. This is a powerful concept with which all system administrators should be thoroughly familiar. Using multi-level directory hierarchies can make file management much easer for you and for your users.

Commands:
Chapter 4. Using the Nexus Repository Manager plugin The Nexus Repository Manager plugin displays the information about your build artifacts in your Developer Hub application. The build artifacts are available in the Nexus Repository Manager. Important The Nexus Repository Manager plugin is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information on Red Hat Technology Preview features, see Technology Preview Features Scope . Additional detail on how Red Hat provides support for bundled community dynamic plugins is available on the Red Hat Developer Support Policy page. The Nexus Repository Manager is a front-end plugin that enables you to view the information about build artifacts. Prerequisites Your Developer Hub application is installed and running. You have installed the Nexus Repository Manager plugin. Procedure Open your Developer Hub application and select a component from the Catalog page. Go to the BUILD ARTIFACTS tab. The BUILD ARTIFACTS tab contains a list of build artifacts and related information, such as VERSION , REPOSITORY , REPOSITORY TYPE , MANIFEST , MODIFIED , and SIZE .

Commands:
Chapter 8. Integrating with Sumo Logic If you are using Sumo Logic , you can forward alerts from Red Hat Advanced Cluster Security for Kubernetes to Sumo Logic. The following steps represent a high-level workflow for integrating Red Hat Advanced Cluster Security for Kubernetes with Sumo Logic: Add a new Custom App in Sumo Logic, set the HTTP source, and get the HTTP URL. Use the HTTP URL to integrate Sumo Logic with Red Hat Advanced Cluster Security for Kubernetes. Identify the policies you want to send notifications for, and update the notification settings for those policies. 8.1. Configuring Sumo Logic Use the Setup Wizard to set up Streaming Data and get the HTTP URL. Procedure Log in to your Sumo Logic Home page and select Setup Wizard . Move your cursor over to Set Up Streaming Data and select Get Started . On the Select Data Type page, select Your Custom App . On the Set Up Collection page, select HTTP Source . Enter a name for Source Category , for example, rhacs and click Continue . Copy the generated URL. 8.2. Configuring Red Hat Advanced Cluster Security for Kubernetes Create a new integration in Red Hat Advanced Cluster Security for Kubernetes by using the HTTP URL. Procedure In the RHACS portal, go to Platform Configuration Integrations . Scroll down to the Notifier Integrations section and select Sumo Logic . Click New Integration ( add icon). Enter a name for Integration Name . Enter the generated HTTP URL in the HTTP Collector Source Address field. Click Test ( checkmark icon) to test that the integration with Sumo Logic is working. Click Create ( save icon) to create the configuration. 8.3. Configuring policy notifications Enable alert notifications for system policies. Procedure In the RHACS portal, go to Platform Configuration Policy Management . Select one or more policies for which you want to send alerts. Under Bulk actions , select Enable notification . In the Enable notification window, select the Sumo Logic notifier. Note If you have not configured any other integrations, the system displays a message that no notifiers are configured. Click Enable . Note Red Hat Advanced Cluster Security for Kubernetes sends notifications on an opt-in basis. To receive notifications, you must first assign a notifier to the policy. Notifications are only sent once for a given alert. If you have assigned a notifier to a policy, you will not receive a notification unless a violation generates a new alert. Red Hat Advanced Cluster Security for Kubernetes creates a new alert for the following scenarios: A policy violation occurs for the first time in a deployment. A runtime-phase policy violation occurs in a deployment after you resolved the runtime alert for a policy in that deployment. 8.4. Viewing alerts in Sumo Logic You can view alerts from Red Hat Advanced Cluster Security for Kubernetes in Sumo Logic. Log in to your Sumo Logic Home page and click Log Search . In the search box, enter _sourceCategory=rhacs . Make sure to use the same Source Category name that you entered while configuring Sumo Logic. Select the time and then click Start .

Commands:
Chapter 27. Red Hat Process Automation Manager clusters By clustering two or more computers, you have the benefits of high availability, enhanced collaboration, and load balancing. High availability decreases the chance of data loss when a single computer fails. When a computer fails, another computer fills the gap by providing a copy of the data that was on the failed computer. When the failed computer comes online again, it resumes its place in the cluster. There are several ways that you can cluster Red Hat Process Automation Manager components. This document describes how to cluster the following scenarios: Chapter 28, Red Hat Process Automation Manager clusters in a development (authoring) environment Chapter 29, KIE Server clusters in a runtime environment

Commands:
11.2. Foreign Table A FOREIGN table is a table that is defined on a physical model that represents a real relational table in source databases like Oracle, SQLServer etc. For relational databases, JBoss Data Virtualization has the capability to automatically retrieve the database schema information upon the deployment of the VDB, if one like to auto import the existing schema. However, the user can use below FOREIGN table semantics, when they would like to explicitly define tables on PHYSICAL models or represent non-relational data as relational data in custom translators. Example 11.2. Example:Create Foreign Table(Created on PHYSICAL model) Note See "create table" in Section A.7, "Productions" .

Commands:
CREATE FOREIGN TABLE Customer (id integer PRIMARY KEY, firstname varchar(25), lastname varchar(25), dob timestamp); CREATE FOREIGN TABLE Order (id integer PRIMARY KEY, customerid integer, saledate date, amount decimal(25,4), CONSTRAINT fk FOREGIN KEY(customerid) REFERENCES Customer(id));
34.3. Setting up a Kerberos-aware NFS Server If any of your NFS clients support only weak cryptography, such as Red Hat Enterprise Linux 5 clients: Update the IdM server Kerberos configuration to enable the weak des-cbc-crc encryption type: On the NFS server, add the following entry to the /etc/krb5.conf file of the NFS server enable weak cryptography support: Obtain a Kerberos ticket: If the NFS host machine has not been added as a client to the IdM domain, create the host entry. See Section 12.3, "Adding Host Entries" . Create the NFS service entry: For more information, see Section 16.1, "Adding and Editing Service Entries and Keytabs" . Retrieve an NFS service keytab for the NFS server using the following ipa-getkeytab command that saves the keys in the /etc/krb5.keytab file: If any of your NFS clients support only weak cryptography, additionally pass the -e des-cbc-crc option to the command to request a DES-encrypted keytab. Verify that the NFS service has been properly configured in IdM, with its keytab, by checking the service entry: Install the nfs-utils package: Run the ipa-client-automount utility to configure the NFS settings: By default, this command enables secure NFS and sets the Domain parameter in the /etc/idmapd.conf file to the IdM DNS domain. If you use a different domain, specify it using the --idmap-domain domain_name parameter. Configure the nfs-idmapd service to start automatically when the system boots: Edit the /etc/exports file and add shares with the krb5p Kerberos security setting: This example shares the /export and /home directories in read-write mode with Kerberos authentication enabled. Re-export the shared directories: Optionally, configure the NFS server as an NFS client. See Section 34.4, "Setting up a Kerberos-aware NFS Client" .

Commands:
ldapmodify -x -D "cn=directory manager" -w password -h ipaserver.example.com -p 389 dn: cn= REALM_NAME ,cn=kerberos,dc=example,dc=com changetype: modify add: krbSupportedEncSaltTypes krbSupportedEncSaltTypes: des-cbc-crc:normal - add: krbSupportedEncSaltTypes krbSupportedEncSaltTypes: des-cbc-crc:special - add: krbDefaultEncSaltTypes krbDefaultEncSaltTypes: des-cbc-crc:special
allow_weak_crypto = true
kinit admin
ipa service-add nfs/ nfs-server.example.com
ipa-getkeytab -s ipaserver.example.com -p nfs/ nfs-server.example.com -k /etc/krb5.keytab
ipa service-show nfs/nfs-server.example.com Principal name: nfs/nfs-server.example.com@IDM.EXAMPLE.COM Principal alias: nfs/nfs-server.example.com@IDM.EXAMPLE.COM Keytab: True Managed by: nfs-server.example.com
yum install nfs-utils
[root@nfs-server ~] ipa-client-automount Searching for IPA server IPA server: DNS discovery Location: default Continue to configure the system with these values? [no]: yes Configured /etc/sysconfig/nfs Configured /etc/idmapd.conf Started rpcidmapd Started rpcgssd Restarting sssd, waiting for it to become available. Started autofs
systemctl enable nfs-idmapd
/export *( rw ,sec=krb5:krb5i:krb5p) /home *( rw ,sec=krb5:krb5i:krb5p)
exportfs -rav
22.3. Write Barrier Considerations Some system configurations do not need write barriers to protect data. In most cases, other methods are preferable to write barriers, since enabling write barriers causes a significant performance penalty. Disabling Write Caches One way to alternatively avoid data integrity issues is to ensure that no write caches lose data on power failures. When possible, the best way to configure this is to disable the write cache. On a simple server or desktop with one or more SATA drives (off a local SATA controller Intel AHCI part), you can disable the write cache on the target SATA drives with the following command: Battery-Backed Write Caches Write barriers are also unnecessary whenever the system uses hardware RAID controllers with battery-backed write cache. If the system is equipped with such controllers and if its component drives have write caches disabled, the controller acts as a write-through cache; this informs the kernel that the write cache data survives a power loss. Most controllers use vendor-specific tools to query and manipulate target drives. For example, the LSI Megaraid SAS controller uses a battery-backed write cache; this type of controller requires the MegaCli64 tool to manage target drives. To show the state of all back-end drives for LSI Megaraid SAS, use: To disable the write cache of all back-end drives for LSI Megaraid SAS, use: Note Hardware RAID cards recharge their batteries while the system is operational. If a system is powered off for an extended period of time, the batteries will lose their charge, leaving stored data vulnerable during a power failure. High-End Arrays High-end arrays have various ways of protecting data in the event of a power failure. As such, there is no need to verify the state of the internal drives in external RAID storage. NFS NFS clients do not need to enable write barriers, since data integrity is handled by the NFS server side. As such, NFS servers should be configured to ensure data persistence throughout a power loss (whether through write barriers or other means).

Commands:
hdparm -W0 / device /
MegaCli64 -LDGetProp -DskCache -LAll -aALL
MegaCli64 -LDSetProp -DisDskCache -Lall -aALL
Chapter 2. Downloading and viewing license information Red Hat's Trusted Profile Analyzer (RHTPA) can analyze both CycloneDX and Software Package Data Exchange (SPDX) SBOM documents. You can download and view license information from uploaded Software Bill of Materials (SBOM) documents, in CycloneDX or SPDX format. To learn more about the differences between the two licenses formats for CycloneDX and SPDX, see the additional resources section. Prerequisites Installation of RHTPA service on Red Hat OpenShift or Red Hat Enterprise Linux. An uploaded CycloneDX 1.3, 1.4, or 1.5 or SPDX 2.2, 2.3 document. Procedure Open a web browser, and log in to the RHTPA console. From the home page, click Search from the navigational sidebar. Find your SBOM from the list. Click the dropdown menu, and click Download License Export . Extract the license information from the downloaded .zip file. Open the comma-separated values (CSV) file to view it. Note The license reference CSV file only applies to SPDX-formatted SBOMs. Additional resources CycloneDX data license information . SPDX handling of licensing information .

Commands:
6.3. Running Infinispan Query DSL-based Queries Once Infinispan Query DSL-based queries have been enabled, obtain a QueryFactory from the Search in order to run a DSL-based query. Obtain a QueryFactory for a Cache In Library mode, obtain a QueryFactory as follows: Example 6.1. Constructing a DSL-based Query When using Remote Querying in Remote Client-Server mode, the Search object resides in package org.infinispan.client.hotrod . See the example in Section 7.2, "Performing Remote Queries via the Hot Rod Java Client" for details. It is also possible to combine multiple conditions with boolean operators, including sub-conditions. For example: Example 6.2. Combining Multiple Conditions This query API simplifies the way queries are written by not exposing the user to the low level details of constructing Lucene query objects. It also has the benefit of being available to remote Hot Rod clients. The following example shows how to write a query for the Book entity. Example 6.3. Querying the Book Entity Report a bug

Commands:
QueryFactory qf = org.infinispan.query.Search.getQueryFactory(cache)
import org.infinispan.query.Search; import org.infinispan.query.dsl.QueryFactory; import org.infinispan.query.dsl.Query; QueryFactory qf = Search.getQueryFactory(cache); Query q = qf.from(User.class) .having("name").eq("John") .toBuilder().build(); List list = q.list(); assertEquals(1, list.size()); assertEquals("John", list.get(0).getName()); assertEquals("Doe", list.get(0).getSurname());
Query q = qf.from(User.class) .having("name").eq("John") .and().having("surname").eq("Doe") .and().not(qf.having("address.street").like("%Tanzania%") .or().having("address.postCode").in("TZ13", "TZ22")) .toBuilder().build();
import org.infinispan.query.Search; import org.infinispan.query.dsl.*; // get the DSL query factory, to be used for constructing the Query object: QueryFactory qf = Search.getQueryFactory(cache); // create a query for all the books that have a title which contains the word "engine": Query query = qf.from(Book.class) .having("title").like("%engine%") .toBuilder().build(); // get the results List<Book> list = query.list();
15.4. Managing Bookmarks You can save a reference to a location by bookmarking it. Procedure 15.3. To bookmark a Location: Select the folder or file you want to bookmark. Press Ctrl + D . The first time a bookmark is activated, the GVFS subsystem looks for existing mounts and spawns a new one if not already present. This way you are able to authenticate even within the open or save dialog. Bookmarks are well integrated in GTK+ and the GNOME Desktop: every application that presents a standard GTK+ open or save dialog (technically called GtkFileChooser ) lists bookmarks in the left panel of the dialog. Also Nautilus and its clones present bookmarks in a sidebar or, more universally, in the Files menu. Note If you have no pages bookmarked yet, the Bookmarks label does not display. Besides Bookmarks , all other available GVFS volumes and mounts are listed in the GtkFileChooser sidebar. Sometimes a bookmark and a GVFS volume combine into a single item to prevent duplication and confusion. Bookmarks then can have eject icon just like GVFS mounts. Bookmarks are located in the ~/.config/gtk-3.0/bookmarks file. In the example below, the bookmarked locations are ~/Music , ~/Pictures , ~/Videos , ~/Downloads , and ~/bin , so the content of the ~/.config/gtk-3.0/bookmarks file looks as follows: Example 15.3. The ~/.config/gtk-3.0/bookmarks File Replace username with the user name you want to use. Procedure 15.4. To edit Bookmarks: Open the Files menu on the top bar. Click Bookmark to open the bookmark editor.

Commands:
file:///home/ username /Music file:///home/ username /Pictures file:///home/ username /Videos file:///home/ username /Downloads file:///home/ username /bin