mtpti5iD/redhat-docs_dataset huggingface dataset:
8.71. glusterfs 8.71.1. RHBA-2014:1576 - glusterfs bug fix and enhancement update Updated glusterfs packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. Red Hat Storage is software-only, scale-out storage that provides flexible and affordable unstructured data storage for an enterprise. GlusterFS, a key building block of Red Hat Storage, is based on a stackable user-space design and can deliver exceptional performance for diverse workloads. GlusterFS aggregates various storage servers over network interconnections into one large, parallel network file system. This update also fixes the following bugs: Note The glusterfs packages have been upgraded to upstream version 3.6.0, which provides a number of bug fixes and enhancements over the version. (BZ# 1095604 ) This update also fixes the following bugs: Bug Fixes BZ# 1044797 When trying to mount a remote gluster share using the "backupvolfile-server" option, the process failed and returned an "Invalid argument" error message. A new mount point option, backup-volfile-servers, has been added to provide backward compatibility and allows remote gluster shares to be mounted successfully. BZ# 1119205 Previously, when updating the gluster utility from Red Hat Enterprise Linux 6.5 to version 6.6, glusterfs-libs POSTIN scriptlet terminated unexpectedly. The underlying source code has been patched, and POSTIN no longer fails. The glusterfs packages have been upgraded to upstream version 3.6.0, which provides a number of bug fixes and enhancements over the version. (BZ#1095604) Users of glusterfs are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 3. Updating Red Hat build of OpenJDK container images To ensure that an Red Hat build of OpenJDK container with Java applications includes the latest security updates, rebuild the container. Procedure Pull the base Red Hat build of OpenJDK image. Deploy the Red Hat build of OpenJDK application. For more information, see Deploying Red Hat build of OpenJDK applications in containers . The Red Hat build of OpenJDK container with the Red Hat build of OpenJDK application is updated. Additional resources For more information, see Red Hat OpenJDK Container images .

Commands:
Chapter 2. Admin REST API Red Hat build of Keycloak comes with a fully functional Admin REST API with all features provided by the Admin Console. To invoke the API you need to obtain an access token with the appropriate permissions. The required permissions are described in the Server Administration Guide. You can obtain a token by enabling authentication for your application using Red Hat build of Keycloak; see the Securing Applications and Services Guide. You can also use direct access grant to obtain an access token. 2.1. Examples of using CURL 2.1.1. Authenticating with a username and password Note The following example assumes that you created the user admin with the password password in the master realm as shown in the Getting Started Guide tutorial. Procedure Obtain an access token for the user in the realm master with username admin and password password : curl \ -d "client_id=admin-cli" \ -d "username=admin" \ -d "password=password" \ -d "grant_type=password" \ "http://localhost:8080/realms/master/protocol/openid-connect/token" Note By default this token expires in 1 minute The result will be a JSON document. Invoke the API you need by extracting the value of the access_token property. Invoke the API by including the value in the Authorization header of requests to the API. The following example shows how to get the details of the master realm: curl \ -H "Authorization: bearer eyJhbGciOiJSUz..." \ "http://localhost:8080/admin/realms/master" 2.1.2. Authenticating with a service account To authenticate against the Admin REST API using a client_id and a client_secret , perform this procedure. Procedure Make sure the client is configured as follows: client_id is a confidential client that belongs to the realm master client_id has Service Accounts Enabled option enabled client_id has a custom "Audience" mapper Included Client Audience: security-admin-console Check that client_id has the role 'admin' assigned in the "Service Account Roles" tab. curl \ -d "client_id=<YOUR_CLIENT_ID>" \ -d "client_secret=<YOUR_CLIENT_SECRET>" \ -d "grant_type=client_credentials" \ "http://localhost:8080/realms/master/protocol/openid-connect/token" 2.2. Additional resources Server Administration Guide Securing Applications and Services Guide API Documentation

Commands:
curl -d "client_id=admin-cli" -d "username=admin" -d "password=password" -d "grant_type=password" "http://localhost:8080/realms/master/protocol/openid-connect/token"
curl -H "Authorization: bearer eyJhbGciOiJSUz..." "http://localhost:8080/admin/realms/master"
curl -d "client_id=<YOUR_CLIENT_ID>" -d "client_secret=<YOUR_CLIENT_SECRET>" -d "grant_type=client_credentials" "http://localhost:8080/realms/master/protocol/openid-connect/token"
Chapter 29. Schedules From the navigation panel, click Views Schedules to access your configured schedules. The schedules list can be sorted by any of the attributes from each column using the directional arrows. You can also search by name, date, or the name of the month in which a schedule runs. Each schedule has a corresponding Actions column that has options to enable or disable that schedule using the On or Off toggle to the schedule name. Click the Edit icon to edit a schedule. If you are setting up a template, a project, or an inventory source, click the Schedules tab to configure schedules for these resources. When you create a schedule, they are listed by the following: Name Click the schedule name to open its details. Type This identifies whether the schedule is associated with a source control update or a system-managed job schedule. run The scheduled run of this task. 29.1. Adding a new schedule You can only create schedules from a template, project, or inventory source, and not directly on the main Schedules screen. To create a new schedule: Procedure Click the Schedules tab of the resource that you are configuring. This can be a template, project, or inventory source. Click Add . This opens the Create New Schedule window. Enter the appropriate details into the following fields: Name : Enter the name. Optional: Description : Enter a description. Start date/time : Enter the date and time to start the schedule. Local time zone : The start time that you enter must be in this time zone. Repeat frequency : Appropriate scheduling options display depending on the frequency you select. The Schedule Details display when you establish a schedule, enabling you to review the schedule settings and a list of the scheduled occurrences in the selected Local Time Zone . Important Jobs are scheduled in UTC. Repeating jobs that run at a specific time of day can move relative to a local time zone when Daylight Savings Time shifts occur. The system resolves the local time zone based time to UTC when the schedule is saved. To ensure your schedules are correctly created, set your schedules in UTC time. Click Save . Use the On or Off toggle to stop an active schedule or activate a stopped schedule.

Commands:
5.257. python-configshell 5.257.1. RHBA-2012:0856 - python-configshell bug fix and enhancement update Updated python-configshell packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The python-configshell packages provide a library for implementing configuration command line interfaces for the Python programming environment. The python-configshell package has been upgraded to version 1.1.fb4 which provides a number of bug fixes and enhancements over the version, and adds support for the configuration shell functionality of fcoe-target-utils packages. (BZ# 765977 ) All users of python-configshell are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
7.76. hwdata 7.76.1. RHEA-2015:1349 - hwdata enhancement update An updated hwdata package that adds one enhancement is now available for Red Hat Enterprise Linux 6. The hwdata package contains tools for accessing and displaying hardware identification and configuration data. Enhancement BZ# 1170975 The PCI, USB, and vendor ID files have been updated with information about recently released hardware. Hardware utility tools that use these ID files are now able to correctly identify recently released hardware. Users of hwdata are advised to upgrade to this updated package, which adds this enhancement.

Commands:
13.7. Configuring a System to Authenticate Using OpenLDAP This section provides a brief overview of how to configure OpenLDAP user authentication. Unless you are an OpenLDAP expert, more documentation than is provided here is necessary. Refer to the references provided in Section 13.9, "Additional Resources" for more information. Install the Necessary LDAP Package First, make sure that the appropriate packages are installed on both the LDAP server and the LDAP client machines. The LDAP server needs the openldap-servers package. The openldap , openldap-clients , and nss_ldap packages need to be installed on all LDAP client machines. Edit the Configuration Files On the server, edit the /etc/openldap/slapd.conf file on the LDAP server to make sure it matches the specifics of the organization. Refer to Section 13.6.1, "Editing /etc/openldap/slapd.conf " for instructions about editing slapd.conf . On the client machines, both /etc/ldap.conf and /etc/openldap/ldap.conf need to contain the proper server and search base information for the organization. To do this, run the graphical Authentication Configuration Tool ( system-config-authentication ) and select Enable LDAP Support under the User Information tab. It is also possible to edit these files by hand. On the client machines, the /etc/nsswitch.conf must be edited to use LDAP. To do this, run the Authentication Configuration Tool ( system-config-authentication ) and select Enable LDAP Support under the User Information tab. If editing /etc/nsswitch.conf by hand, add ldap to the appropriate lines. For example: 13.7.1. PAM and LDAP To have standard PAM-enabled applications use LDAP for authentication, run the Authentication Configuration Tool ( system-config-authentication ) and select Enable LDAP Support under the the Authentication tab. For more about configuring PAM, refer to Chapter 16, Pluggable Authentication Modules (PAM) and the PAM man pages.

Commands:
passwd: files ldap shadow: files ldap group: files ldap
4.25. Fence kdump Table 4.26, "Fence kdump" lists the fence device parameters used by fence_dkump , the fence agent for kdump crash recovery service. Note that fence_kdump is not a replacement for traditional fencing methods; The fence_kdump agent can detect only that a node has entered the kdump crash recovery service. This allows the kdump crash recovery service to complete without being preempted by traditional power fencing methods. Table 4.26. Fence kdump luci Field cluster.conf Attribute Description Name name A name for the fence_kdump device. IP Family family IP network family. The default value is auto . IP Port (optional) ipport IP port number that the fence_kdump agent will use to listen for messages. The default value is 7410. Operation Timeout (seconds) (optional) timeout Number of seconds to wait for message from failed node. Node name nodename Name or IP address of the node to be fenced.

Commands:
8.196. scsi-target-utils 8.196.1. RHBA-2013:1684 - scsi-target-utils bug fix update Updated scsi-target-utils packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The scsi-target-utils packages contain a daemon and tools to setup Small Computer System Interface (SCSI) targets. Currently, software Internet SCSI (iSCSI) and iSCSI Extensions for RDMA (iSER) targets are supported. Bug Fixes BZ# 910638 Previously, the tgtadm utility did not check for the presence of the libaio library to enable the asynchronous I/O types of backend storage. Consequently, attempts to add a new iSCSI target device with the "tgtadm --bstype aio" command failed with an "invalid request" error message. This update adds libaio as a runtime dependency. Now, using the "--bstype aio" option with the tgtadm utility no longer fails and attempts to add a new logical unit work as expected. BZ# 813636 Prior to this update, when interruptions were occurring in the network, then reconnection of the TCP protocol did not work properly. As a consequence, memory leaks occurred in the tgtd daemon under these circumstances. This bug has been fixed and the TCP reconnection now works correctly in the described scenario. BZ# 865739 Previously, the tgtd daemon did not report its exported targets properly if configured to report them to an Internet Storage Name Service (iSNS) server. Consequently, running the "iscsiadm -m discoverydb -t isns" command failed. This bug has been fixed and tgtd now reports its exported targets correctly in the described scenario. BZ# 922270 Previously, it was not possible to supply command-line parameters to the tgtd daemon. With this update, it is possible to set the TGTD_OPTIONS variable containing the parameters and use it in the /etc/sysconfig/tgtd file. Users of scsi-target-utils are advised to upgrade to these updated packages, which fix these bugs. All running scsi-target-utils services must be restarted for the update to take effect.

Commands:
Chapter 2. Preparing your environment for managing IdM using Ansible playbooks As a system administrator managing Identity Management (IdM), when working with Red Hat Ansible Engine, it is good practice to do the following: Create a subdirectory dedicated to Ansible playbooks in your home directory, for example ~/MyPlaybooks . Copy and adapt sample Ansible playbooks from the /usr/share/doc/ansible-freeipa/* and /usr/share/doc/rhel-system-roles/* directories and subdirectories into your ~/MyPlaybooks directory. Include your inventory file in your ~/MyPlaybooks directory. Using this practice, you can find all your playbooks in one place and you can run your playbooks without invoking root privileges. Note You only need root privileges on the managed nodes to execute the ipaserver , ipareplica , ipaclient and ipabackup ansible-freeipa roles. These roles require privileged access to directories and the dnf software package manager. Follow this procedure to create the ~/MyPlaybooks directory and configure it so that you can use it to store and run Ansible playbooks. Prerequisites You have installed an IdM server on your managed nodes, server.idm.example.com and replica.idm.example.com . You have configured DNS and networking so you can log in to the managed nodes, server.idm.example.com and replica.idm.example.com , directly from the control node. You know the IdM admin password. Procedure Create a directory for your Ansible configuration and playbooks in your home directory: Change into the ~/MyPlaybooks/ directory: Create the ~/MyPlaybooks/ansible.cfg file with the following content: Create the ~/MyPlaybooks/inventory file with the following content: This configuration defines two host groups, eu and us , for hosts in these locations. Additionally, this configuration defines the ipaserver host group, which contains all hosts from the eu and us groups. Optional: Create an SSH public and private key. To simplify access in your test environment, do not set a password on the private key: Copy the SSH public key to the IdM admin account on each managed node: These commands require that you enter the IdM admin password. Additional resources Installing an Identity Management server using an Ansible playbook How to build your inventory

Commands:
mkdir ~/MyPlaybooks/
cd ~/MyPlaybooks
[defaults] inventory = /home/ your_username /MyPlaybooks/inventory [privilege_escalation] become=True
[eu] server.idm.example.com [us] replica.idm.example.com [ipaserver:children] eu us
ssh-keygen
ssh-copy-id admin@server.idm.example.com ssh-copy-id admin@replica.idm.example.com
Chapter 39. AdditionalVolume schema reference Used in: PodTemplate Property Property type Description name string Name to use for the volume. Required. secret SecretVolumeSource Secret to use populate the volume. configMap ConfigMapVolumeSource ConfigMap to use to populate the volume. emptyDir EmptyDirVolumeSource EmptyDir to use to populate the volume. persistentVolumeClaim PersistentVolumeClaimVolumeSource PersistentVolumeClaim object to use to populate the volume. csi CSIVolumeSource CSIVolumeSource object to use to populate the volume.

Commands:
Chapter 6. System Configuration 6.1. ACPI 6.1.1. CPU hotplug ACPI CPU hotplug is available as a Technology Preview in Red Hat Enterprise Linux 6.5. This is a platform-specific feature; as such, details of its use are outside the scope of this document. Important Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. However, these features are not fully supported under Red Hat Enterprise Linux Subscription Level Agreements, may not be functionally complete, and are not intended for production use. During the development of a Technology Preview feature, additional components may become available to the public for testing. Because Technology Preview features are still under development, Red Hat cannot guarantee the stability of such features. As a result, if you are using Technology Preview features, you may not be able to seamlessly upgrade to subsequent releases of that feature. While Red Hat intends to fully support Technology Preview features in future releases, we may discover that a feature does not meet the standards for enterprise usingbility. If this happens, we cannot guarantee that Technology Preview features will be released in a supported manner. Some Technology Preview features may only be available for specific hardware architectures. The CONFIG_ACPI_HOTPLUG_CPU configuration option must be enabled in order to use this feature. Additionally, if the platform implements the optional ACPI _OST method, the following configuration options must also be enabled. There are no harmful effects associated with enabling these configuration for all platforms. CONFIG_ACPI_HOTPLUG_CPU CONFIG_ACPI_HOTPLUG_MEMORY or CONFIG_ACPI_HOTPLUG_MEMORY_MODULE CONFIG_ACPI_CONTAINER or CONFIG_ACPI_CONTAINER_MODULE

Commands:
B.2. Log in to JBoss Dashboard Builder Prerequisites Red Hat JBoss Data Virtualization must be installed and running. You must have a JBoss Dashboard Builder user account. Procedure B.1. Log in to the JBoss Dashboard Builder Navigate to JBoss Dashboard Builder Navigate to JBoss Dashboard Builder in your web browser. The default location is http://localhost:8080/dashboard . Log in to JBoss Dashboard Builder Enter the Username and Password of a valid JBoss Dashboard Builder user.

Commands:
14.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. The following types are used with OpenShift. Different types allow you to configure flexible access: Process types openshift_t The OpenShift process is associated with the openshift_t SELinux type. Types on executables openshift_cgroup_read_exec_t SELinux allows files with this type to transition an executable to the openshift_cgroup_read_t domain. openshift_cron_exec_t SELinux allows files with this type to transition an executable to the openshift_cron_t domain. openshift_initrc_exec_t SELinux allows files with this type to transition an executable to the openshift_initrc_t domain. Writable types openshift_cgroup_read_tmp_t This type allows OpenShift control groups (cgroup) read and access temporary files in the /tmp/ directory. openshift_cron_tmp_t This type allows storing temporary files of the OpenShift cron jobs in /tmp/ . openshift_initrc_tmp_t This type allows storing the OpenShift initrc temporary files in /tmp/ . openshift_log_t Files with this type are treated as OpenShift log data, usually stored under the /var/log/ directory. openshift_rw_file_t OpenShift have permission to read and to write to files labeled with this type. openshift_tmp_t This type is used for storing the OpenShift temporary files in /tmp/ . openshift_tmpfs_t This type allows storing the OpenShift data on a tmpfs file system. openshift_var_lib_t This type allows storing the OpenShift files in the /var/lib/ directory. openshift_var_run_t This type allows storing the OpenShift files in the /run/ or /var/run/ directory.

Commands:
Appendix E. Performance Recommendations E.1. Concurrent Startup for Large Clusters When starting a large number of instances, each managing a large number of caches, in parallel this may take a while as rebalancing attempts to distribute the data evenly as each node joins the cluster. To limit the number of rebalancing attempts made during the initial startup of the cluster disable rebalancing temporarily by following the below steps: Start the first node in the cluster. Set JMX attribute jboss.infinispan/CacheManager/"clustered"/LocalTopologyManager/rebalancingEnabled to false , as seen in Section C.13, "LocalTopologyManager" . Start the remaining nodes in the cluster. Re-enable the JMX attribute jboss.infinispan/CacheManager/"clustered"/LocalTopologyManager/rebalancingEnabled by setting this value back to true , as seen in Section C.13, "LocalTopologyManager" . Report a bug

Commands:
18.12.10.4. ARP/RARP Protocol ID: arp or rarp Rules of this type should either go into the root or arp/rarp chain. Table 18.6. ARP and RARP protocol types Attribute Name Datatype Definition srcmacaddr MAC_ADDR MAC address of sender srcmacmask MAC_MASK Mask applied to MAC address of sender dstmacaddr MAC_ADDR MAC address of destination dstmacmask MAC_MASK Mask applied to MAC address of destination hwtype UINT16 Hardware type protocoltype UINT16 Protocol type opcode UINT16, STRING Opcode valid strings are: Request, Reply, Request_Reverse, Reply_Reverse, DRARP_Request, DRARP_Reply, DRARP_Error, InARP_Request, ARP_NAK arpsrcmacaddr MAC_ADDR Source MAC address in ARP/RARP packet arpdstmacaddr MAC _ADDR Destination MAC address in ARP/RARP packet arpsrcipaddr IP_ADDR Source IP address in ARP/RARP packet arpdstipaddr IP_ADDR Destination IP address in ARP/RARP packet gratuitous BOOLEAN Boolean indiating whether to check for a gratuitous ARP packet comment STRING text string up to 256 characters

Commands: