mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 20. Shared File Service (manila) Parameters You can modify the manila service with shared file service parameters. Parameter Description ApacheCertificateKeySize Override the private key size used when creating the certificate for this service. ApacheTimeout The timeout in seconds for Apache, which defines duration Apache waits for I/O operations. The default value is 90 . CephClusterName The Ceph cluster name. The default value is ceph . CephConfigPath The path where the Ceph Cluster configuration files are stored on the host. The default value is /var/lib/tripleo-config/ceph . CertificateKeySize Specifies the private key size used when creating the certificate. The default value is 2048 . EnableSQLAlchemyCollectd Set to true to enable the SQLAlchemy-collectd server plugin. The default value is false . ManilaCephClientUserName Ceph client username for manila integration. The default value is manila . ManilaCephFSCephFSProtocolHelperType Protocol type ( CEPHFS or NFS ) when cephfs back end is enabled. Set via manila cephfs environment files. The default value is CEPHFS . ManilaCronDbPurgeAge Cron to purge database entries marked as deleted and older than USDage - Age. The default value is 30 . ManilaCronDbPurgeDestination Cron to purge database entries marked as deleted and older than USDage - Log destination. The default value is /var/log/manila/manila-rowsflush.log . ManilaCronDbPurgeHour Cron to purge database entries marked as deleted and older than USDage - Hour. The default value is 0 . ManilaCronDbPurgeMaxDelay Cron to purge database entries marked as deleted and older than USDage - Max Delay. The default value is 3600 . ManilaCronDbPurgeMinute Cron to purge database entries marked as deleted and older than USDage - Minute. The default value is 1 . ManilaCronDbPurgeMonth Cron to purge database entries marked as deleted and older than USDage - Month. The default value is * . ManilaCronDbPurgeMonthday Cron to purge database entries marked as deleted and older than USDage - Month Day. The default value is * . ManilaCronDbPurgeUser Cron to purge database entries marked as deleted and older than USDage - User. The default value is manila . ManilaCronDbPurgeWeekday Cron to purge database entries marked as deleted and older than USDage - Week Day. The default value is * . ManilaEnabledShareProtocols List of protocols to be allowed for share creation in manila. When not set, the list is inferred via the storage back end/s enabled. ManilaIPv6 Set to True to enable IPv6 access in manila. The default value is False . ManilaPassword The password for the shared file service account. ManilaStorageAvailabilityZone The OpenStack Shared File Systems (manila) service's storage availability zone. The default value is nova . ManilaWorkers Set the number of workers for manila::wsgi::apache. The default value is equal to the number of vCPU cores on the physical node. MemcacheUseAdvancedPool Use the advanced (eventlet safe) memcached client pool. The default value is true . NotificationDriver Driver or drivers to handle sending notifications. The default value is noop .

Commands:
7.2. Profiles for file system performance The tuned-adm tool allows users to easily swap between a number of profiles that have been designed to enhance performance for specific use cases. The profiles that are particularly useful in improving storage performance are: latency-performance A server profile for typical latency performance tuning. It disables tuned and ktune power-saving mechanisms. The cpuspeed mode changes to performance . The I/O elevator is changed to deadline for each device. The cpu_dma_latency parameter is registered with a value of 1 (the lowest possible latency) for power management quality-of-service to limit latency where possible. throughput-performance A server profile for typical throughput performance tuning. This profile is recommended if the system does not have enterprise-class storage. It is the same as latency-performance , except: kernel.sched_min_granularity_ns (scheduler minimal preemption granularity) is set to 10 milliseconds, kernel.sched_wakeup_granularity_ns (scheduler wake-up granularity) is set to 15 milliseconds, vm.dirty_ratio (virtual memory dirty ratio) is set to 40%, and transparent huge pages are enabled. enterprise-storage This profile is recommended for enterprise-sized server configurations with enterprise-class storage, including battery-backed controller cache protection and management of on-disk cache. It is the same as the throughput-performance profile, except: readahead value is set to 4x , and non root/boot file systems are re-mounted with barrier=0 . More information about tuned-adm is available on the man page ( man tuned-adm ), or in the Power Management Guide available from http://access.redhat.com/site/documentation/Red_Hat_Enterprise_Linux/ .

Commands:
3.2.2.2. Multiple Authentication Methods Using multiple authentication methods, or multi-factor authentication, increases the level of protection against unauthorized access, and as such should be considered when hardening a system to prevent it from being compromised. Users attempting to log in to a system that uses multi-factor authentication must successfully complete all specified authentication methods in order to be granted access. Use the AuthenticationMethods configuration directive in the /etc/ssh/sshd_config file to specify which authentication methods are to be utilized. Note that it is possible to define more than one list of required authentication methods using this directive. If that is the case, the user must complete every method in at least one of the lists. The lists need to be separated by blank spaces, and the individual authentication-method names within the lists must be comma-separated. For example: An sshd daemon configured using the above AuthenticationMethods directive only grants access if the user attempting to log in successfully completes either publickey authentication followed by gssapi-with-mic or by keyboard-interactive authentication. Note that each of the requested authentication methods needs to be explicitly enabled using a corresponding configuration directive (such as PubkeyAuthentication ) in the /etc/ssh/sshd_config file. Refer to the AUTHENTICATION section of ssh(1) for a general list of available authentication methods.

Commands:
AuthenticationMethods publickey,gssapi-with-mic publickey,keyboard-interactive
Chapter 7. Using the Topology plugin Topology is a front-end plugin that enables you to view the workloads as nodes that power any service on the Kubernetes cluster. 7.1. Enable users to use the Topology plugin The Topology plugin is defining additional permissions. When Authorization is enabled, to enable users to use the Topology plugin, grant them: The topology.view.read read permission to view the Topology panel. The kubernetes.proxy use permission to view the pod logs. The catalog-entity read permission to view the Red Hat Developer Hub software catalog items. Prerequisites You are managing Authorization by using external files . Procedure Add the following permission policies to your rbac-policy.csv file to create a topology-viewer role that has access to the Topology plugin features, and add the role to the users requiring this authorization: 1 Grants the user the ability to see the Topology panel. 2 Grants the user the ability to view the pod logs. 3 Grants the user the ability to see the catalog item. 7.2. Using the Topology plugin Prerequisites Your Red Hat Developer Hub instance is installed and running. You have installed the Topology plugin. You have enabled the users to use the Topology plugin . Procedure Open your RHDH application and select a component from the Catalog page. Go to the TOPOLOGY tab and you can view the workloads such as deployments or pods as nodes. Select a node and a pop-up appears on the right side that contains two tabs: Details and Resources . The Details and Resources tabs contain the associated information and resources for the node. Click the Open URL button on the top of a node. Click the Open URL button to access the associated Ingresses and run your application in a new tab.

Commands:
g, user:default/<YOUR_USERNAME>, role:default/topology-viewer p, role:default/topology-viewer, topology.view.read, read, allow 1 p, role:default/topology-viewer, kubernetes.proxy, use, allow 2 p, role:default/topology-viewer, catalog-entity, read, allow 3
Chapter 21. Kernel Certain NIC firmware can become unresponsive with the bnx2x driver Due to a bug in the unload sequence of the pre-boot drivers, the firmware of some internet adapters can become unresponsive after the bnx2x driver takes over the device. The bnx2x driver detects the problem and returns the message in the kernel log: To work around this problem, apply the latest NIC firmware updates provided by your hardware vendor. As a result, unloading of the pre-boot firmware now works as expected and the firmware no longer hangs after bnx2x takes over the device. (BZ#1012684) e1000e cards might not get an IPv4 address Some e1000e network interface cards (NICs) might fail to get an IPv4 address assigned after the system is rebooted. To work around this problem, add the following line to the /etc/sysconfig/network-scripts/ifcfg-<interface> file: (BZ#822725) The ecb kernel module fails when dracut is not upgraded When upgrading only the kernel rpm from Red Hat Enterprise Linux 6.7 to version 6.8, upgrade the dracut package to the latest version (dracut-004-409.el6.rpm). Upgrading dracut enables the ecb module to work. The ecb kernel module is needed by the drbg kernel module when using the Advanced Encryption Standard (AES) implementation on non-x86 architectures. If you do not upgrade dracut , the drbg AES implementation fails with a warning message, although other drbg modules still work. (BZ#1315832) Guests sometimes fail to boot on ESXi 5.5 When running Red Hat Enterprise Linux 7 guests on a VMware ESXi 5.5 hypervisor, certain components currently initialize with incorrect memory type range register (MTRR) values or incorrectly reconfigure MTRR values across boots. This sometimes causes the guest kernel to panic or the guest to become unresponsive during boot. To work around this problem, add the `disable_mtrr_trim` option to the guest's kernel command line, which enables the guest to continue booting when MTRRs are configured incorrectly. Note that with this option, the guest prints `WARNING: BIOS bug` messages during boot, which you can safely ignore. (BZ#1422774) File-system corruption due to incorrect flushing of cache has been fixed but I/O operations can be slower Due to a bug in the megaraid_sas driver, file-system corruption previously occurred in some cases when the file system was used with a disk-write back cache during system shutdown, reboot, or power loss. This update fixes megaraid_sas to transfer the flush cache commands correctly to the raid card. As a result, if you also update the raid card firmware, the file-system corruption no longer occurs under the described circumstances. With Broadcom megaraid_sas raid adapter, you can check the functionality in the system log (dmesg). The proper functionality is indicated by the following text string: Note that this fix can slow down I/O operations because the cache is now flushed properly. (BZ#1392499)

Commands:
Storm stats were not updated for 3 times.
LINKDELAY=10
FW supports sync cache Yes
Chapter 32. Basic System Recovery When things go wrong, there are ways to fix problems. However, these methods require that you understand the system well. This chapter contains information on common problems you might face and it also describes installation program rescue mode , which can be used to fix these problems. 32.1. Common Problems You might need to boot into installation program rescue mode for any of the following reasons: You are unable to boot into Red Hat Enterprise Linux normally. You are having hardware or software problems, and you want to recover data from your system's hard drive. You forgot the root password. 32.1.1. Unable to Boot into Red Hat Enterprise Linux This problem is often caused by the installation of another operating system after you have installed Red Hat Enterprise Linux. Some other operating systems assume that you have no other operating system(s) on your computer. They overwrite the Master Boot Record (MBR) that originally contained the GRUB2 boot loader. If the boot loader is overwritten in this manner, you cannot boot Red Hat Enterprise Linux unless you can boot into installation program rescue mode and reconfigure the boot loader. Another common problem occurs when using a partitioning tool to resize a partition or create a new partition from free space after installation, and it changes the order of your partitions. If the partition number of your / partition changes, the boot loader might not be able to find it to mount the partition. To fix this problem, you will need to reinstall the boot loader. See Section 32.2.2, "Reinstalling the Boot Loader" for instructions on how to do this. 32.1.2. Hardware and Software Problems This category includes a wide variety of different situations. Two examples include failing hard drives and specifying an invalid root device or kernel in the boot loader configuration file. If either of these occur, you might not be able to reboot into Red Hat Enterprise Linux. However, if you boot into installation program rescue mode, you might be able to resolve the problem or at least get copies of your most important files. 32.1.3. Resetting the Root Password See the corresponding section in the Red Hat Enterprise Linux 7 System Administrator's Guide .

Commands:
Chapter 2. Building Containers It is necessary to maintain a mechanism that permits you to update your containers, so that they can be patched when security vulnerabilities that apply to those containers are discovered. An understanding of how containers are built helps maintain them properly. To minimize the risk of having security vulnerabilities in your containers, you need to make it possible to update your containers so that you can apply security patches to them. To make your containers reliably updateable you need to leverage as much of the existing packaging infrastructure and tooling as possible. This means that you will have to use Yum. In this respect, running containers is no different than running any other distribution. All the rules that you're familiar with apply: you should use RPM if you can.

Commands:
Appendix A. Revision History Revision History Revision 6.6.0-2 Fri Jun 23 2017 John Brier Removed unsupported mixed mode cluster from features table. Revision 6.6.0-1 Wed 7 Sep 2016 Christian Huffman Updating for 6.6.1. Revision 6.6.0-0 Mon 25 Jan 2016 Christian Huffman Initial draft for 6.6.0.

Commands:
Part III. Advanced Features in Red Hat JBoss Data Grid Red Hat JBoss Data Grid includes some advanced features. Some of these features are listed in the JBoss Data Grid Administration and Configuration Guide with instructions for a basic configuration. The JBoss Data Grid Developer Guide explores these features and others in more detail and with instructions for more advanced usage. The advanced features explored in this guide are as follows: Transactions Marshalling Listeners and Notifications The Infinispan CDI Module MapReduce Distributed Execution Interoperability and Compatibility Mode Report a bug

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

Commands:
Chapter 7. Important user and group account information for Active Directory accounts All user and group accounts must be local accounts. This is to ensure that there are no authentication conflicts between local accounts on your Satellite Server and accounts in your Active Directory domain. Your system is not affected by this conflict if your user and group accounts exist in both /etc/passwd and /etc/group files. For example, to check if entries for puppet , apache , foreman and foreman-proxy groups exist in both /etc/passwd and /etc/group files, enter the following commands:

Commands:
grep 'puppet\|apache\|foreman\|foreman-proxy' /etc/passwd /etc/group
1.2.3.3. Nikto Nikto is an excellent common gateway interface (CGI) script scanner. Nikto not only checks for CGI vulnerabilities but does so in an evasive manner, so as to elude intrusion detection systems. It comes with thorough documentation which should be carefully reviewed prior to running the program. If you have Web servers serving up CGI scripts, Nikto can be an excellent resource for checking the security of these servers. More information about Nikto can be found at the following URL: http://cirt.net/nikto2

Commands:
14.5.2. New Backends tdbsam The tdbsam backend provides an ideal database backend for local servers, servers that do not need built-in database replication, and servers that do not require the scalability or complexity of LDAP. The tdbsam backend includes all of the smbpasswd database information as well as the previously-excluded SAM information. The inclusion of the extended SAM data allows Samba to implement the same account and system access controls as seen with Windows NT/2000/2003-based systems. The tdbsam backend is recommended for 250 users at most. Larger organizations should require Active Directory or LDAP integration due to scalability and possible network infrastructure concerns. ldapsam The ldapsam backend provides an optimal distributed account installation method for Samba. LDAP is optimal because of its ability to replicate its database to any number of servers using the OpenLDAP slurpd daemon. LDAP databases are light-weight and scalable, perfect for most organizations, especially large enterprises. LDAP is definitely the "wave of the future" with regards to Samba. Improvements to LDAP are constantly being added into Samba such as easing installation and configuration issues. mysqlsam The mysqlsam backend uses a MySQL-based database backend. This is useful for sites that already implement MySQL. xmlsam The xmlsam backend uses account and password data that are stored in an XML formatted file. This method can be useful for migration of different backend databases or backups.

Commands:
4.19. IBM BladeCenter Table 4.20, "IBM BladeCenter" lists the fence device parameters used by fence_bladecenter , the fence agent for IBM BladeCenter. Table 4.20. IBM BladeCenter luci Field cluster.conf Attribute Description Name name A name for the IBM BladeCenter device connected to the cluster. IP Address or Hostname ipaddr The IP address or host name assigned to the device. IP port (optional) ipport TCP port to use for connection with the device. Login login The login name used to access the device. Password passwd The password used to authenticate the connection to the device. Password Script (optional) passwd_script The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. Power Wait (seconds) power_wait Number of seconds to wait after issuing a power off or power on command. Power Timeout (seconds) power_timeout Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. Shell Timeout (seconds) shell_timeout Number of seconds to wait for a command prompt after issuing a command. The default value is 3. Login Timeout (seconds) login_timeout Number of seconds to wait for a command prompt after login. The default value is 5. Times to Retry Power On Operation retry_on Number of attempts to retry a power on operation. The default value is 1. Use SSH secure Indicates that system will use SSH to access the device. When using SSH, you must specify either a password, a password script, or an identity file. SSH Options ssh_options SSH options to use. The default value is -1 -c blowfish . Path to SSH Identity File identity_file The identity file for SSH. Figure 4.14, "IBM BladeCenter" shows the configuration screen for adding an IBM BladeCenter fence device. Figure 4.14. IBM BladeCenter The following command creates a fence device instance for an IBM BladeCenter device: The following is the cluster.conf entry for the fence_bladecenter device:

Commands:
ccs -f cluster.conf --addfencedev bladecentertest1 agent=fence_bladecenter ipaddr=192.168.0.1 login=root passwd=password123 power_wait=60
<fencedevices> <fencedevice agent="fence_bladecenter" ipaddr="192.168.0.1" login="root" name="bladecentertest1" passwd="password123" power_wait="60"/> </fencedevices>
12.5. Base Execution Properties The following execution properties are shared by all translators. Table 12.1. Base Execution Properties Name Description Default Immutable Set to true to indicate that the source never changes. false RequiresCriteria Set to true to indicate that source SELECT/UPDATE/DELETE queries require a WHERE clause. false SupportsOrderBy Set to true to indicate that the ORDER BY clause is supported. false SupportsOuterJoins Set to true to indicate that OUTER JOINs are supported. false SupportsFullOuterJoins If outer joins are supported, true indicates that FULL OUTER JOINs are supported. false SupportsInnerJoins Set to true to indicate that INNER JOINs are supported. false SupportedJoinCriteria If joins are supported, defines what criteria may be used as the join criteria. May be one of (ANY, THETA, EQUI, or KEY). ANY MaxInCriteriaSize If in criteria are supported, defines what the maximum number of in entries are per predicate. -1 indicates no limit. -1 MaxDependentInPredicates If IN criteria are supported, defines what the maximum number of predicates that can be used for a dependent join. Values less than 1 indicate to use only one IN predicate per dependent value pushed. -1 DirectQueryProcedureName f the direct query procedure is supported on the translator, this property indicates the name of the procedure. native SupportsDirectQueryProcedure Set to true to indicate the translator supports the direct execution of commands false ThreadBound Set to true to indicate the translator's Executions should be processed by only a single thread false CopyLobs If true, then returned LOBs (clob, blob, sql/xml) will be copied by the engine in a memory-safe manner. Use this option if the source does not support memory-safe LOBs or you want to disconnect LOBs from the source connection. false Note Only a subset of the supports metadata can be set through execution properties. If more control is needed, see Red Hat JBoss Data Virtualization Development Guide: Server Development . There are no base importer settings.

Commands: