mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Running an Ansible Playbook from Satellite You can run an Ansible Playbook on a host or host group by executing a remote job in Satellite. Limitation of host parameters in Ansible Playbook job templates When you execute an Ansible Playbook on multiple hosts, Satellite renders the playbook for all hosts in the batch, but only uses the rendered playbook of the first host to execute it on all hosts in the batch. Therefore, you cannot modify the behavior of the playbook per host by using a host parameter in the template control flow constructs. Host parameters are translated into Ansible variables, so you can use them to control the behavior in native Ansible constructs. For more information, see BZ#2282275 . Prerequisites Ansible plugin in Satellite is enabled. Remote job execution is configured. For more information, see Chapter 4, Configuring and setting up remote jobs . You have an Ansible Playbook ready to use. Procedure In the Satellite web UI, navigate to Monitor > Jobs . Click Run Job . In Job category , select Ansible Playbook . In Job template , select Ansible - Run playbook . Click . Select the hosts on which you want to run the playbook. In the playbook field, paste the content of your Ansible Playbook. Follow the wizard to complete setting the remote job. For more information, see Section 4.21, "Executing a remote job" . Click Submit to run the Ansible Playbook on your hosts. Additional resources Alternatively, you can import Ansible Playbooks from Capsule Servers. For more information, see the following resources: Section 4.7, "Importing an Ansible Playbook by name" Section 4.8, "Importing all available Ansible Playbooks"

Commands:
9.5. Enabling and Disabling User Accounts User accounts can be deactivated or disabled . A disabled user cannot log into IdM or its related services (like Kerberos) and he cannot perform any tasks. However, the user account still exists within Identity Management and all of the associated information remains unchanged. Note Any existing connections remain valid until the Kerberos TGT and other tickets expire. Once the ticket expires, the user cannot renew the ticket. 9.5.1. From the Web UI Multiple users can be disabled from the full users list by selecting the checkboxes by the desired users and then clicking the Disable link at the top of the list. Figure 9.2. Disable/Enable Options at the Top of the Users List A user account can also be disabled from the user's individual entry page. Open the Identity tab, and select the Users subtab. Click the name of the user to deactivate or activate. In the actions drop-down menu, select the Disable item. Click the Accept button. When a user account is disabled, it is signified by a minus (-) icon for the user status in the user list and by the username on the entry page. Additionally, the text for the user is gray (to show it is inactive) instead of black. Figure 9.3. Disable Icon for User Status 9.5.2. From the Command Line Users are enabled and disabled using user-enable and user-disable commands. All that is required is the user login. For example:

Commands:
[bjensen@server ~]USD ipa user-disable jsmith
13.4. Setting a Partition Type The partition type, not to be confused with the file system type, is used by a running system only rarely. However, the partition type matters to on-the-fly generators, such as systemd-gpt-auto-generator , which use the partition type to, for example, automatically identify and mount devices. You can start the fdisk utility and use the t command to set the partition type. The following example shows how to change the partition type of the first partition to 0x83, default on Linux: The parted utility provides some control of partition types by trying to map the partition type to 'flags', which is not convenient for end users. The parted utility can handle only certain partition types, for example LVM or RAID. To remove, for example, the lvm flag from the first partition with parted , use: For a list of commonly used partition types and hexadecimal numbers used to represent them, see the Partition Types table in the Partitions: Turning One Drive Into Many appendix of the Red Hat Enterprise Linux 7 Installation Guide .

Commands:
fdisk /dev/sdc Command (m for help): t Selected partition 1 Partition type (type L to list all types): 83 Changed type of partition 'Linux LVM' to 'Linux'.
parted /dev/sdc 'set 1 lvm off'
Chapter 1. Bare Metal Provisioning service (ironic) functionality You use the Bare Metal Provisioning service (ironic) components to provision and manage physical machines as bare-metal instances for your cloud users. To provision and manage bare-metal instances, the Bare Metal Provisioning service interacts with the following Red Hat OpenStack Services on OpenShift (RHOSO) services: The Compute service (nova) provides scheduling, tenant quotas, and a user-facing API for virtual machine instance management. The Identity service (keystone) provides request authentication and assists the Bare Metal Provisioning service to locate other RHOSO services. The Image service (glance) manages disk and instance images and image metadata. The Networking service (neutron) provides DHCP and network configuration, and provisions the virtual or physical networks that instances connect to on boot. The Object Storage service (swift) exposes temporary image URLs for some drivers. Bare Metal Provisioning service components The Bare Metal Provisioning service consists of services, named ironic-* . The following services are the core Bare Metal Provisioning services: Bare Metal Provisioning API ( ironic-api ) This service provides the external REST API to users. The API sends application requests to the Bare Metal Provisioning conductor over remote procedure call (RPC). Bare Metal Provisioning conductor ( ironic-conductor ) This service uses drivers to perform the following bare-metal node management tasks: Adds, edits, and deletes bare-metal nodes. Powers bare-metal nodes on and off with IPMI, Redfish, or other vendor-specific protocol. Provisions, deploys, and cleans bare metal nodes. Bare Metal Provisioning inspector ( ironic-inspector ) This service discovers the hardware properties of a bare-metal node that are required for scheduling bare-metal instances, and creates the Bare Metal Provisioning service ports for the discovered ethernet MACs. Bare Metal Provisioning database This database tracks hardware information and state. Bare Metal Provisioning agent ( ironic-python-agent ) This service runs in a temporary ramdisk to provide ironic-conductor and ironic-inspector services with remote access, in-band hardware control, and hardware introspection. Provisioning a bare-metal instance You can configure the Bare Metal Provisioning service to use PXE, iPXE, or virtual media to provision physical machines as bare-metal instances: PXE or iPXE: The Bare Metal Provisioning service provisions the bare-metal instances by using network boot. Virtual media: The Bare Metal Provisioning service provisions the bare-metal instances by creating a temporary ISO image and requesting the Baseboard Management Controller (BMC) to attach and boot to that image.

Commands:
3.13. Attaching an ISO Image to a Virtual Machine This Ruby example attaches a CD-ROM to a virtual machine and changes it to an ISO image in order to install the guest operating system. # Get the reference to the "vms" service: vms_service = connection.system_service.vms_service # Find the virtual machine: vm = vms_service.list(search: 'name=myvm')[0] # Locate the service that manages the virtual machine: vm_service = vms_service.vm_service(vm.id) # Locate the service that manages the CDROM devices of the VM: cdroms_service = vm_service.cdroms_service # List the first CDROM device: cdrom = cdroms_service.list[0] # Locate the service that manages the CDROM device you just found: cdrom_service = cdroms_service.cdrom_service(cdrom.id) # Change the CD of the VM to 'my_iso_file.iso'. By default this # operation permanently changes the disk that is visible to the # virtual machine after the boot, but it does not have any effect # on the currently running virtual machine. If you want to change the # disk that is visible to the current running virtual machine, change # the `current` parameter's value to `true`. cdrom_service.update( OvirtSDK4::Cdrom.new( file: { id: 'CentOS-7-x86_64-DVD-1511.iso' } ), current: false ) For more information, see VmService:cdroms_service .

Commands:
Get the reference to the "vms" service: vms_service = connection.system_service.vms_service Find the virtual machine: vm = vms_service.list(search: 'name=myvm')[0] Locate the service that manages the virtual machine: vm_service = vms_service.vm_service(vm.id) Locate the service that manages the CDROM devices of the VM: cdroms_service = vm_service.cdroms_service List the first CDROM device: cdrom = cdroms_service.list[0] Locate the service that manages the CDROM device you just found: cdrom_service = cdroms_service.cdrom_service(cdrom.id) Change the CD of the VM to 'my_iso_file.iso'. By default this operation permanently changes the disk that is visible to the virtual machine after the next boot, but it does not have any effect on the currently running virtual machine. If you want to change the disk that is visible to the current running virtual machine, change the `current` parameter's value to `true`. cdrom_service.update( OvirtSDK4::Cdrom.new( file: { id: 'CentOS-7-x86_64-DVD-1511.iso' } ), current: false )
14.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: smbd_anon_write Having this Boolean enabled allows smbd to write to a public directory, such as an area reserved for common files that otherwise has no special access restrictions. samba_create_home_dirs Having this Boolean enabled allows Samba to create new home directories independently. This is often done by mechanisms such as PAM. samba_domain_controller When enabled, this Boolean allows Samba to act as a domain controller, as well as giving it permission to execute related commands such as useradd , groupadd , and passwd . samba_enable_home_dirs Enabling this Boolean allows Samba to share users' home directories. samba_export_all_ro Export any file or directory, allowing read-only permissions. This allows files and directories that are not labeled with the samba_share_t type to be shared through Samba. When the samba_export_all_ro Boolean is enabled, but the samba_export_all_rw Boolean is disabled, write access to Samba shares is denied, even if write access is configured in /etc/samba/smb.conf , as well as Linux permissions allowing write access. samba_export_all_rw Export any file or directory, allowing read and write permissions. This allows files and directories that are not labeled with the samba_share_t type to be exported through Samba. Permissions in /etc/samba/smb.conf and Linux permissions must be configured to allow write access. samba_run_unconfined Having this Boolean enabled allows Samba to run unconfined scripts in the /var/lib/samba/scripts/ directory. samba_share_fusefs This Boolean must be enabled for Samba to share fusefs file systems. samba_share_nfs Disabling this Boolean prevents smbd from having full access to NFS shares through Samba. Enabling this Boolean will allow Samba to share NFS volumes. use_samba_home_dirs Enable this Boolean to use a remote server for Samba home directories. virt_use_samba Allow virtual machine access to CIFS files. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, enter the following command: Enter the following command to view description of a particular Boolean: Note that the additional policycoreutils-devel package providing the sepolicy utility is required for this command to work.

Commands:
~]USD getsebool -a | grep service_name
~]USD sepolicy booleans -b boolean_name
10.9.2. Related Books Apache Desktop Reference by Ralf S. Engelschall; Addison Wesley - Written by ASF member and mod_ssl author Ralf Engelschall, the Apache Desktop Reference provides a concise but comprehensive reference guide to using the Apache HTTP Server at compilation, configuration, and run time. This book is available online at http://www.apacheref.com/ . Professional Apache by Peter Wainwright; Wrox Press Ltd - Professional Apache is from Wrox Press Ltd's "Programmer to Programmer" series and is aimed at both experienced and novice Web server administrators. Administering Apache by Mark Allan Arnold; Osborne Media Group - This book is targeted at Internet Service Providers who aim to provide more secure services. Apache Server Unleashed by Richard Bowen, et al; SAMS BOOKS - An encyclopedic source for the Apache HTTP Server. Apache Pocket Reference by Andrew Ford, Gigi Estabrook; O'Reilly - This is the latest addition to the O'Reilly Pocket Reference series. System Administrators Guide ; Red Hat, Inc - Contains a chapter about configuring the Apache HTTP Server using the HTTP Configuration Tool and a chapter about configuring the Apache HTTP Server Secure Server. Security Guide ; Red Hat, Inc - The Server Security chapter explains ways to secure Apache HTTP Server and other services.

Commands:
Chapter 5. Known issues This section documents known issues found in this release of Red Hat Ceph Storage. 5.1. The Cephadm utility Cephadm does not maintain the OSD weight when draining an OSD Cephadm does not maintain the OSD weight when draining an OSD. Due to this, if the ceph orch osd rm <osd-id> command is run and later, the OSD removal is stopped, Cephadm will not set the crush weight of the OSD back to its original value. The crush weight will remain at 0. As a workaround, users have to manually adjust the crush weight of the OSD to its original value, or complete removal of the OSD and deploy a new one. Users should be careful when cancelling a ceph orch osd rm operation, as the crush weight of the OSD will not be returned to its original value before the removal process begins. Bugzilla:2247211 Repeated use of the Ceph Object Gateway realm bootstrap command causes setting the zonegroup hostname to fail Setting the zonegroup hostnames using the Ceph Object Gateway realm bootstrap command fails when being done multiple times. Due to this, the repeated use of the Ceph Object Gateway realm bootstrap command to recreate a realm/zonegroup/zone does not work properly with zonegroup_hostnames field and the hostnames will not be set in the zonegroup. As a workaround, set the zonegroup hostnames manually using the radosgw-admin tool. Bugzilla:2241321 5.2. Ceph Object Gateway Processing a query on a large Parquet object causes Ceph Object gateway processes to stop Previously, in some cases, upon processing a query on a Parquet object, that object would be read chunk after chunk and these chunks could be quite big. This would cause the Ceph Object Gateway to load a large buffer into memory that is too big for a low-end machine; especially, when Ceph Object Gateway is co-located with OSD processes, which consumes a large amount of memory. This situation would trigger the OS to kill the Ceph Object Gateway process. As a workaround, place the Ceph Object Gateway on a separate node and as a result, more memory is left for Ceph Object gateway, enabling it to complete processing successfully. Bugzilla:2275323 Current RGW STS implementation does not support encryption keys larger than 1024 bytes The current RGW STS implementation does not support encryption keys larger than 1024 bytes. As a workaround, in Keycloak: realm settings - keys , edit the 'rsa-enc-generated' provider to have priority 90 rather than 100 and keySize as 1024 instead of 2048. Bugzilla:2276931 Intel QAT Acceleration for Object Compression & Encryption Intel QuickAssist Technology (QAT) is implemented to help reduce node CPU usage and improve the performance of Ceph Object Gateway when enabling compression and encryption. In this release, QAT can only be configured on new setups (Greenfield), which is a limitation of this feature. QAT Ceph Object Gateway daemons cannot be configured in the same cluster as non-QAT (regular) Ceph Object Gateway daemons. Bugzilla:2284394

Commands:
Chapter 21. Interceptors JBoss EAP messaging supports interceptors to intercept packets entering and exiting the server. Incoming and outgoing interceptors are called for every packet entering or exiting the server respectively. This allows custom code to be executed, such as for auditing or filtering packets. Interceptors can modify the packets they intercept. This makes interceptors powerful, but also potentially dangerous. 21.1. Implementing Interceptors An interceptor must implement the Interceptor interface: package org.apache.artemis.activemq.api.core.interceptor; public interface Interceptor { boolean intercept(Packet packet, RemotingConnection connection) throws ActiveMQException; } The returned boolean value is important: if true is returned, the process continues normally if false is returned, the process is aborted, no other interceptors will be called and the packet will not be processed further by the server. Interceptor classes should be added to JBoss EAP as a module. See Create a Custom Module in the JBoss EAP Configuration Guide for more information. 21.2. Configuring Interceptors After adding their module to JBoss EAP as a custom module, both incoming and outgoing interceptors are added to the messaging subsystem configuration by using the management CLI. Note You must start JBoss EAP in administrator only mode before the new interceptor configuration will be accepted. See Running JBoss EAP in Admin-only Mode in the JBoss EAP Configuration Guide for details. Restart the server in normal mode after the new configuration is processed. Each interceptor should be added according to the example management CLI command below. The examples assume each interceptor has already been added to JBoss EAP as a custom module. Adding an outgoing interceptor follows a similar syntax, as the example below illustrates.

Commands:
package org.apache.artemis.activemq.api.core.interceptor; public interface Interceptor { boolean intercept(Packet packet, RemotingConnection connection) throws ActiveMQException; }
/subsystem=messaging-activemq/server=default:list-add(name=incoming-interceptors, value={name => "foo.bar.MyIncomingInterceptor", module=>"foo.bar.interceptors"})
/subsystem=messaging-activemq/server=default:list-add(name=outgoing-interceptors, value={name => "foo.bar.MyOutgoingInterceptor", module=>"foo.bar.interceptors"})
Appendix C. Using AMQ Broker with the examples The Red Hat build of Apache Qpid JMS examples require a running message broker with a queue named queue . Use the procedures below to install and start the broker and define the queue. C.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . C.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... C.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named queue . USD <broker-instance-dir> /bin/artemis queue create --name queue --address queue --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. C.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2023-12-06 12:44:04 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name queue --address queue --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
Chapter 1. Recommended practices for installing large clusters Apply the following practices when installing large clusters or scaling clusters to larger node counts. 1.1. Recommended practices for installing large scale clusters When installing large clusters or scaling the cluster to larger node counts, set the cluster network cidr accordingly in your install-config.yaml file before you install the cluster: networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 machineCIDR: 10.0.0.0/16 networkType: OpenShiftSDN serviceNetwork: - 172.30.0.0/16 The default cluster network cidr 10.128.0.0/14 cannot be used if the cluster size is more than 500 nodes. It must be set to 10.128.0.0/12 or 10.128.0.0/10 to get to larger node counts beyond 500 nodes.

Commands:
networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 machineCIDR: 10.0.0.0/16 networkType: OpenShiftSDN serviceNetwork: - 172.30.0.0/16