mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Custom user attributes You can add custom user attributes to the registration page and account management console with a custom theme. 4.1. Registration page Use this procedure to enter custom attributes in the registration page. Procedure Copy the template themes/base/login/register.ftl to the login type of your custom theme. Open the copy in an editor. For example, to add a mobile number to the registration page, add the following snippet to the form: <div class="form-group"> <div class="USD{properties.kcLabelWrapperClass!}"> <label for="user.attributes.mobile" class="USD{properties.kcLabelClass!}">Mobile number</label> </div> <div class="USD{properties.kcInputWrapperClass!}"> <input type="text" class="USD{properties.kcInputClass!}" id="user.attributes.mobile" name="user.attributes.mobile" value="USD{(register.formData['user.attributes.mobile']!'')}"/> </div> </div> Ensure the name of the input html element starts with user.attributes . In the example above, the attribute will be stored by Red Hat Single Sign-On with the name mobile . To see the changes, make sure your realm is using your custom theme for the login theme and open the registration page. 4.2. Account Management Console Use this procedure to manage custom attributes in the user profile page in the account management console. Procedure Copy the template themes/base/account/account.ftl to the account type of your custom theme. Open the copy in an editor. As an example to add a mobile number to the account page add the following snippet to the form: <div class="form-group"> <div class="col-sm-2 col-md-2"> <label for="user.attributes.mobile" class="control-label">Mobile number</label> </div> <div class="col-sm-10 col-md-10"> <input type="text" class="form-control" id="user.attributes.mobile" name="user.attributes.mobile" value="USD{(account.attributes.mobile!'')}"/> </div> </div> Ensure the name of the input html element starts with user.attributes . To see the changes, make sure your realm is using your custom theme for the account theme and open the user profile page in the account management console. 4.3. Additional resources See Themes for how to create a custom theme.

Commands:
<div class="form-group"> <div class="USD{properties.kcLabelWrapperClass!}"> <label for="user.attributes.mobile" class="USD{properties.kcLabelClass!}">Mobile number</label> </div> <div class="USD{properties.kcInputWrapperClass!}"> <input type="text" class="USD{properties.kcInputClass!}" id="user.attributes.mobile" name="user.attributes.mobile" value="USD{(register.formData['user.attributes.mobile']!'')}"/> </div> </div>
<div class="form-group"> <div class="col-sm-2 col-md-2"> <label for="user.attributes.mobile" class="control-label">Mobile number</label> </div> <div class="col-sm-10 col-md-10"> <input type="text" class="form-control" id="user.attributes.mobile" name="user.attributes.mobile" value="USD{(account.attributes.mobile!'')}"/> </div> </div>
Chapter 6. Configure key based SSH authentication without a password Configure key-based SSH authentication without a password for the root user from the host to itself. 6.1. Generating SSH key pairs without a password Generating a public/private key pair lets you use key-based SSH authentication. Generating a key pair that does not use a password makes it simpler to use Ansible to automate deployment and configuration processes. Procedure Log in to the first hyperconverged host as the root user. Generate an SSH key that does not use a password. Start the key generation process. Enter a location for the key. The default location, shown in parentheses, is used if no other input is provided. Specify and confirm an empty passphrase by pressing Enter twice. The private key is saved in <location>/<keyname> . The public key is saved in <location>/<keyname>.pub . Warning Your identification in this output is your private key. Never share your private key. Possession of your private key allows someone else to impersonate you on any system that has your public key. 6.2. Copying SSH keys To access a host using your private key, that host needs a copy of your public key. Prerequisites Generate a public/private key pair with no password. Procedure Log in to the host as the root user. Copy the public key to the same host: Enter the password for root@<hostname> when prompted. Warning Make sure that you use the file that ends in .pub . Never share your private key. Possession of your private key allows someone else to impersonate you on any system that has your public key. For example, if you are logged in as the root user on server1.example.com , you would run the following commands:

Commands:
ssh-keygen -t rsa Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa): <location>/<keyname>
Enter passphrase (empty for no passphrase): Enter same passphrase again:
Your identification has been saved in <location>/<keyname>. Your public key has been saved in <location>/<keyname>.pub. The key fingerprint is SHA256:8BhZageKrLXM99z5f/AM9aPo/KAUd8ZZFPcPFWqK6+M root@server1.example.com The key's randomart image is: +---[ECDSA 256]---+ | . . +=| | . . . = o.o| | + . * . o...| | = . . * . + +..| |. + . . So o * ..| | . o . .+ = ..| | o oo ..=. .| | ooo...+ | | .E++oo | +----[SHA256]-----+
ssh-copy-id -i <location>/<keyname>.pub root@<hostname>
ssh-copy-id -i <location>/<keyname>.pub root@server1.example.com
Appendix A. Revision History Revision History Revision 1.0-31 Thu Apr 28 2016 Jana Heves Red Hat Enterprise Linux 6.8 GA release of the Resource Management Guide Revision 1.0-29 Tue May 12 2015 Radek Biba Asynchronous update. Revision 1.0-26 Thu Oct 10 2014 Peter Ondrejka Red Hat Enterprise Linux 6.6 GA release of the Resource Management Guide Revision 1.0-16 Thu Feb 21 2013 Martin Prpic Red Hat Enterprise Linux 6.4 GA release of the Resource Management Guide Revision 1.0-7 Wed Jun 20 2012 Martin Prpic Red Hat Enterprise Linux 6.3 GA release of the Resource Management Guide . Revision 1.0-6 Tue Dec 6 2011 Martin Prpic Red Hat Enterprise Linux 6.2 GA release of the Resource Management Guide Revision 1.0-5 Thu May 19 2011 Martin Prpic Red Hat Enterprise Linux 6.1 GA release of the Resource Management Guide Revision 1.0-0 Tue Nov 9 2010 Rudiger Landmann Feature-complete version for GA

Commands:
Chapter 4. KafkaSpec schema reference Used in: Kafka Property Description kafka Configuration of the Kafka cluster. KafkaClusterSpec zookeeper Configuration of the ZooKeeper cluster. ZookeeperClusterSpec entityOperator Configuration of the Entity Operator. EntityOperatorSpec clusterCa Configuration of the cluster certificate authority. CertificateAuthority clientsCa Configuration of the clients certificate authority. CertificateAuthority cruiseControl Configuration for Cruise Control deployment. Deploys a Cruise Control instance when specified. CruiseControlSpec jmxTrans The jmxTrans property has been deprecated. JMXTrans is deprecated and related resources removed in AMQ Streams 2.5. As of AMQ Streams 2.5, JMXTrans is not supported anymore and this option is ignored. JmxTransSpec kafkaExporter Configuration of the Kafka Exporter. Kafka Exporter can provide additional metrics, for example lag of consumer group at topic/partition. KafkaExporterSpec maintenanceTimeWindows A list of time windows for maintenance tasks (that is, certificates renewal). Each time window is defined by a cron expression. string array

Commands:
Chapter 5. Setting BIOS parameters for system tuning The BIOS plays a key role in the functioning of the system. By configuring the BIOS parameters correctly you can significantly improve the system performance. Note Every system and BIOS vendor uses different terms and navigation methods. For more information about BIOS settings, see the BIOS documentation or contact the BIOS vendor. 5.1. Disabling power management to improve response times BIOS power management options help save power by changing the system clock frequency or by putting the CPU into one of various sleep states. These actions are likely to affect how quickly the system responds to external events. To improve response times, disable all power management options in the BIOS. 5.2. Improving response times by disabling error detection and correction units Error Detection and Correction (EDAC) units are devices for detecting and correcting errors signaled from Error Correcting Code (ECC) memory. Usually EDAC options range from no ECC checking to a periodic scan of all memory nodes for errors. The higher the EDAC level, the more time the BIOS uses. This may result in missing crucial event deadlines. To improve response times, turn off EDAC. If this is not possible, configure EDAC to the lowest functional level. 5.3. Improving response time by configuring System Management Interrupts System Management Interrupts (SMIs) are a hardware vendors facility to ensure that the system is operating correctly. The BIOS code usually services the SMI interrupt. SMIs are typically used for thermal management, remote console management (IPMI), EDAC checks, and various other housekeeping tasks. If the BIOS contains SMI options, check with the vendor and any relevant documentation to determine the extent to which it is safe to disable them. Warning While it is possible to completely disable SMIs, Red Hat strongly recommends that you do not do this. Removing the ability of your system to generate and service SMIs can result in catastrophic hardware failure.

Commands:
1.10.3. REDUNDANCY The REDUNDANCY panel allows you to configure of the backup LVS router node and set various heartbeat monitoring options. Figure 1.33. The REDUNDANCY Panel Redundant server public IP The public real IP address for the backup LVS router. Redundant server private IP The backup router's private real IP address. The rest of the panel is for configuring the heartbeat channel, which is used by the backup node to monitor the primary node for failure. Heartbeat Interval (seconds) Sets the number of seconds between heartbeats - the interval that the backup node will check the functional status of the primary LVS node. Assume dead after (seconds) If the primary LVS node does not respond after this number of seconds, then the backup LVS router node will initiate failover. Heartbeat runs on port Sets the port at which the heartbeat communicates with the primary LVS node. The default is set to 539 if this field is left blank.

Commands:
3.3. Setting Preferences 3.3.1. Setting Preferences The ModeShape Preferences dialog allows for resource versioning to be set along with specific file types and folders that you never wish to have published to or unpublished from a ModeShape repository. Procedure 3.3. Setting preferences Open ModeShape Preferences dialog. The ModeShape Preferences dialog is accessed by navigating to Window -> Preferences -> Content Repository -> Publishing . This dialog allows you to set whether resource versioning will be used for your ModeShape repository or not. Figure 3.7. ModeShape Preferences dialog Activate resource versioning. Click the Enable resource versioning checkbox to activate resource versioning. 3.3.2. Ignored Resources You can manage the resources to be published using the Ignored Resources menu. Procedure 3.4. Manage Ignored Resources Open Ignored Resources Preferences dialog. To open the Ignored Resources dialog, click Window -> Preferences -> Content Repository -> Publishing -> Ignored Resources . On this screen you can manage the resources that will not be published to your ModeShape repository. The current excluded file types and folders are presented as the list of checkbox items that appear under the Ignored Resources heading. Figure 3.8. ModeShape: Ignored Resources Preferences dialog Add a new resource to the Ignored Resources list. To add a new file extension type or folder name to be filtered from publishing, click the New button, enter the details and click the Apply button so that your preference changes are saved. Remove a resource from the Ignored Resources list. To remove an entry, select an entry from the list in the Preferences dialog and click the Remove button. Ensure that you click the Apply button so that your preference changes are saved. Note If you decide to ignore a resource that has been published in the past, ensure that all instances are unpublished before ignoring it, otherwise you will not be able to unpublish the resource either. That said, this can be an effective way of ensuring a resource cannot be unpublished by accident. Remember though that, since preference settings are only local to your working environment, in a multi-user ModeShape repository someone else could unpublish it.

Commands:
1.8.4.2. Firewall Marks Firewall marks are an easy and efficient way to a group ports used for a protocol or group of related protocols. For example, if LVS is deployed to run an e-commerce site, firewall marks can be used to bundle HTTP connections on port 80 and secure, HTTPS connections on port 443. By assigning the same firewall mark to the virtual server for each protocol, state information for the transaction can be preserved because the LVS router forwards all requests to the same real server after a connection is opened. Because of its efficiency and ease-of-use, administrators of LVS should use firewall marks instead of persistence whenever possible for grouping connections. However, you should still add persistence to the virtual servers in conjunction with firewall marks to ensure the clients are reconnected to the same server for an adequate period of time.

Commands:
21.2. Displaying Log Files You can display the Directory Server log files using the command line and web console: 21.2.1. Displaying Log Files Using the Command Line To display the log files using the command line, use the utilities included in Red Hat Enterprise Linux, such as less , more , and cat . For example: To display the locations of log files: Note If logging for a log type is not enabled, the corresponding log file does not exist. 21.2.2. Displaying Log Files Using the Web Console To display the Directory Server log files: 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. Open the Monitoring menu. Open the Logging menu, and select the log file you want to display. Optionally, you can apply the following settings to the log file viewer: Set the number of lines to display in the Log Lines To Show field. Enable automatically displaying new log entries by selecting Continuously Refresh . Click the Refresh button to apply the changes.

Commands:
less /var/log/dirsrv/slapd- instance_name /access
dsconf -D "cn=Directory Manager" ldap://server.example.com config get nsslapd-accesslog nsslapd-errorlog nsslapd-auditlog nsslapd-auditfaillog nsslapd-accesslog: /var/log/dirsrv/slapd- instance_name /access nsslapd-errorlog: /var/log/dirsrv/slapd- instance_name /errors nsslapd-auditlog: /var/log/dirsrv/slapd- instance_name /audit nsslapd-auditfaillog: /var/log/dirsrv/slapd- instance_name /audit-failure
Appendix B. Revision History Revision History Revision 0.2-8 Thu Apr 27 2017 Lenka Spackova Red Hat Access Labs renamed to Red Hat Customer Portal Labs. Revision 0.2-7 Tue Mar 21 2017 Jiri Herrmann Updated a Virtualization Known Issue. Revision 0.2-6 Mon Mar 13 2017 Lenka Spackova Added a known issue to Authentication and Interoperability. Revision 0.2-5 Fri Dec 16 2016 Lenka Spackova Updated the Red Hat Software Collections chapter. Revision 0.2-4 Thu Oct 27 2016 Lenka Spackova Added two known issues to General Updates. Revision 0.2-3 Wed Oct 25 2016 Jiri Herrmann Added a virtualization known issue ( fsgsbase and smep ). Revision 0.2-1 Wed Sep 07 2016 Lenka Spackova Added an SSSD known issue (Authentication and Interoperability). Revision 0.2-0 Mon Aug 29 2016 Lenka Spackova Added two known issues (Installation and Booting). Revision 0.1-9 Mon Aug 01 2016 Lenka Spackova Updated a known issue regarding limited CPU support for Windows 10 guests (Virtualization). Revision 0.1-8 Fri Jul 01 2016 Lenka Spackova Fixed commands in an SSSD feature. Revision 0.1-6 Wed Jun 08 2016 Lenka Spackova Added an SSSD feature (new default values for group names). Revision 0.1-4 Fri Jun 03 2016 Lenka Spackova Added Bugzilla numbers to individual descriptions. Revision 0.1-3 Fri May 27 2016 Lenka Spackova Added new known issues (SSSD, ReaR). Revision 0.1-2 Mon May 16 2016 Lenka Spackova Added a new feature to Clustering (fence agent). Revision 0.1-1 Thu May 12 2016 Lenka Spackova Added known issues related to ReaR . Revision 0.1-0 Tue May 10 2016 Lenka Spackova Release of the Red Hat Enterprise Linux 6.8 Release Notes. Revision 0.0-5 Tue Mar 15 2016 Lenka Spackova Release of the Red Hat Enterprise Linux 6.8 Beta Release Notes.

Commands:
F.4.2. Runlevel Utilities One of the best ways to configure runlevels is to use an initscript utility . These tools are designed to simplify the task of maintaining files in the SysV init directory hierarchy and relieves system administrators from having to directly manipulate the numerous symbolic links in the subdirectories of /etc/rc.d/ . Red Hat Enterprise Linux provides three such utilities: /sbin/chkconfig - The /sbin/chkconfig utility is a simple command line tool for maintaining the /etc/rc.d/init.d/ directory hierarchy. /usr/sbin/ntsysv - The ncurses-based /sbin/ntsysv utility provides an interactive text-based interface, which some find easier to use than chkconfig . Services Configuration Tool - The graphical Services Configuration Tool ( system-config-services ) program is a flexible utility for configuring runlevels. Refer to the chapter titled Services and Daemons in the Red Hat Enterprise Linux Deployment Guide for more information regarding these tools.

Commands:
Chapter 5. JBoss EAP Security JBoss EAP offers the ability to configure security for its own interfaces and services as well as provide security for applications that are running on it. See the Security Architecture guide for an overview of general security concepts as well as JBoss EAP-specific security concepts. See How to Configure Server Security for information on securing JBoss EAP itself. See How to Configure Identity Management for information on providing security for applications deployed to JBoss EAP. See How to Set Up SSO with Kerberos for information on configuring single sign-on for JBoss EAP using Kerberos. See How To Set Up SSO with SAML v2 for information on configuring single sign-on for JBoss EAP using SAML v2.

Commands:
Chapter 2. Apache Maven and Red Hat Process Automation Manager Spring Boot applications Apache Maven is a distributed build automation tool used in Java application development to create, manage, and build software projects. Maven uses standard configuration files called Project Object Model (POM) files to define projects and manage the build process. POM files describe the module and component dependencies, build order, and targets for the resulting project packaging and output using an XML file. This ensures that the project is built in a correct and uniform manner. A Maven repository stores Java libraries, plug-ins, and other build artifacts. The default public repository is the Maven 2 Central Repository, but repositories can be private and internal within a company to share common artifacts among development teams. Repositories are also available from third parties. You can use the online Maven repository with your Spring Boot projects or you can download the Red Hat Process Automation Manager Maven repository. The recommended approach is to use the online Maven repository with your Spring Boot projects. Maven settings used with a repository manager or repository on a shared server provide better control and manageability of projects.

Commands:
9.7. Storage Devices Storage devices and storage pools can use the block device drivers to attach storage devices to virtualized guests. Note that the storage drivers are not storage devices. The drivers are used to attach a backing storage device, file or storage pool volume to a virtualized guest. The backing storage device can be any supported type of storage device, file, or storage pool volume. The IDE driver exposes an emulated block device to guests. The emulated IDE driver can be used to attach any combination of up to four virtualized IDE hard disks or virtualized IDE CD-ROM drives to each virtualized guest. The emulated IDE driver is also used to provide virtualized DVD-ROM drives. The VirtIO driver exposes a para-virtualized block device to guests. The para-virtualized block driver is a driver for all storage devices supported by the hypervisor attached to the virtualized guest (except for floppy disk drives, which must be emulated).

Commands:
Chapter 5. Developer previews This section describes the developer preview features introduced in Red Hat OpenShift Data Foundation 4.14. Important Developer preview feature is subject to Developer preview support limitations. Developer preview releases are not intended to be run in production environments. The clusters deployed with the developer preview features are considered to be development clusters and are not supported through the Red Hat Customer Portal case management system. If you need assistance with developer preview features, reach out to the ocs-devpreview@redhat.com mailing list and a member of the Red Hat Development Team will assist you as quickly as possible based on availability and work schedules. 5.1. Custom timeouts for the reclaim space operation OpenShift Data Foundation now allows you to set a custom timeout value for the reclaim space operation. Previously, depending on RBD volume size and its data pattern, the reclaim space operation might have failed with the error context deadline exceeded . Adjusting the timeout value avoids this error. For more information, see the knowledgebase article Customize timeouts for Reclaim Space Operation . 5.2. Expansion of encrypted RBD volumes OpenShift Data Foundation now enables resize capability on encrypted RBD persistent volume claims (PVCs). For more information, see the knowledgebase article Enabling resize for encrypted RBD PVC . 5.3. IPV6 support for external mode OpenShift Data Foundation now allows users to use the IPv6 Red Hat Ceph Storage external standalone Ceph cluster to connect with the IPV6 OpenShift Container Platform cluster. Users can pass the IPv6 endpoints using the same endpoint flags while running the python script. 5.4. Network File System supports export sharing across namespaces When OpenShift Data Foundation is used to dynamically create an NFS-export, the PersistentVolumeClaim is used to access the NFS-export in a pod. It is not immediately possible to use the same NFS-export for a different application in another OpenShift Namespace. You can now create a second PersistentVolume that can be bound to a second PersistentVolumeClaim in another OpenShift namespace. For more information, see the knowledgebase article ODF provisioned NFS/PersistentVolume sharing between Namespaces . 5.5. Data compression on the wire Data compression on the wire helps in multi-availability zones deployment by lowering latency and network costs. It also helps in cases where the network bandwidth is a bottleneck for performance. For more information, see the knowledgeabase article In-transit compression .

Commands: