mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Hybrid Cloud Console User Access The User Access feature is an implementation of role-based access control (RBAC) that controls access to various services hosted on the Red Hat Hybrid Cloud Console. Users with the Organization Administrator role use the User Access feature to grant other users access to services hosted on the Hybrid Cloud Console. An Organization Administrator can assign the special role User Access Administrator to other users who do not have the Organization Administrator role. Users with the User Access Administrator role can manage user access on the Red Hat Hybrid Cloud Console . User access on Red Hat Hybrid Cloud Console uses an additive model, which means that actions are only permitted, not denied. To control access, users with the Organization Administrator role assign the appropriate roles with the desired permissions to groups, then add users to those groups. The access permitted to an individual user is the sum of all roles assigned to all groups to which that user belongs. Additional resources For detailed information about the User Access feature for the Organization Administrator role, see the User Access Configuration Guide for Role-based Access Control (RBAC) with FedRAMP . For a list of quick starts about the User Access feature for the Organization Administrator role, see the Identity & Access Management Learning Resources page. 3.1. The User Access groups, roles, and permissions User Access uses the following categories to determine the level of user access that an Organization Administrator can grant to the supported Red Hat Hybrid Cloud Console services. The access provided to any authorized user depends on the group that the user belongs to and the roles assigned to that group. Group : A collection of users belonging to an account which provides the mapping of roles to users. An Organization Administrator can use groups to assign one or more roles to a group and to include one or more users in a group. You can create a group with no roles and no users. Roles : A set of permissions that provide access to a given service, such as Insights. The permissions to perform certain operations are assigned to specific roles. Roles are assigned to groups. For example, you might have a read role and a write role for a service. Adding both roles to a group grants all members of that group read and write permissions to that service. Permissions : A discrete action that can be requested of a service. Permissions are assigned to roles. 3.2. Viewing your permissions to services Your Organization Administrator grants and manages your access to the different services in the Red Hat Hybrid Cloud Console. You can view your permissions for each service on the console. Prerequisites You are logged in to the Hybrid Cloud Console. Procedure Click your user avatar in the upper right of the Red Hat Hybrid Cloud Console window. A drop-down list appears. Click My User Access . The My User Access page opens. Select a services group, for example Red Hat Enterprise Linux. A table of services appears. Your permissions are listed in the Operation column.

Commands:
7.115. libical 7.115.1. RHBA-2013:0471 - libical bug fix update Updated libical packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libical packages provide a reference implementation of the iCalendar data type and serialization format used in dozens of calendaring and scheduling products. Bug Fix BZ#664332 The libical packages can be configured to abort when parsing improperly formatted iCalendar data, primarily useful for testing and debugging. In Red Hat Enterprise Linux this behavior is disabled, but some parts of the libical source code were improperly checking for this option. Consequently, the library aborted even if configured not to do so. The underlying source code has been modified and libical no longer aborts in the described scenario. All users of libical are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 115. KafkaUserTlsExternalClientAuthentication schema reference Used in: KafkaUserSpec The type property is a discriminator that distinguishes use of the KafkaUserTlsExternalClientAuthentication type from KafkaUserTlsClientAuthentication , KafkaUserScramSha512ClientAuthentication . It must have the value tls-external for the type KafkaUserTlsExternalClientAuthentication . Property Property type Description type string Must be tls-external .

Commands:
4.5.3. Network Configuration Clicking on the Network tab displays the Network Configuration page, which provides an interface for configuring the network transport type. You can use this tab to select one of the following options: UDP Multicast and Let Cluster Choose the Multicast Address This is the default setting. With this option selected, the Red Hat High Availability Add-On software creates a multicast address based on the cluster ID. It generates the lower 16 bits of the address and appends them to the upper portion of the address according to whether the IP protocol is IPv4 or IPv6: For IPv4 - The address formed is 239.192. plus the lower 16 bits generated by Red Hat High Availability Add-On software. For IPv6 - The address formed is FF15:: plus the lower 16 bits generated by Red Hat High Availability Add-On software. Note The cluster ID is a unique identifier that cman generates for each cluster. To view the cluster ID, run the cman_tool status command on a cluster node. UDP Multicast and Specify the Multicast Address Manually If you need to use a specific multicast address, select this option enter a multicast address into the Multicast Address text box. If you do specify a multicast address, you should use the 239.192.x.x series (or FF15:: for IPv6) that cman uses. Otherwise, using a multicast address outside that range may cause unpredictable results. For example, using 224.0.0.x (which is "All hosts on the network") may not be routed correctly, or even routed at all by some hardware. If you specify or modify a multicast address, you must restart the cluster for this to take effect. For information on starting and stopping a cluster with Conga , see Section 5.4, "Starting, Stopping, Restarting, and Deleting Clusters" . Note If you specify a multicast address, make sure that you check the configuration of routers that cluster packets pass through. Some routers may take a long time to learn addresses, seriously impacting cluster performance. UDP Unicast (UDPU) As of the Red Hat Enterprise Linux 6.2 release, the nodes in a cluster can communicate with each other using the UDP Unicast transport mechanism. It is recommended, however, that you use IP multicasting for the cluster network. UDP Unicast is an alternative that can be used when IP multicasting is not available. For GFS2 deployments using UDP Unicast is not recommended. Click Apply . When changing the transport type, a cluster restart is necessary for the changes to take effect.

Commands:
7.154. pcp 7.154.1. RHBA-2015:1300 - pcp bug fix and enhancement update Updated pcp packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. Performance Co-Pilot (PCP) is a suite of tools, services, and libraries for acquisition, archiving, and analysis of system-level performance measurements. Its light-weight, distributed architecture makes it particularly well-suited to centralized analysis of complex systems. Note The pcp packages have been upgraded to upstream version 3.10.3, which provides numerous bug fixes and enhancements over the version. (BZ# 1158681 ) Bug Fixes BZ# 1158681 New kernel metrics: memory, vCPU, device mapper, nfs4.1 operations, more per-cgroup metrics New Performance Metrics Domain Agents (PMDA): NVIDIA, Linux, 389 Directory Server, hardware event counters, CIFS, activeMQ New vCPU and MemAvailable pmchart views New pmiostat, pcp-dmcache, pcp2graphite, ganglia2pcp tools Nanosecond resolution event timestamps The pmParseUnitsStr() function added to the Performance Metrics Application Programming Interface (PMAPI) ACAO header JSON responses added to the Performance Metrics Web Daemon (pmwebd) The "ruleset" extensions to the pmie language Support for Python v3 and Python API extensions Support for xz compression for daily archives Support for long form of command-line options Support for active service probing in libpcp Support for new sysstat versions and sar2pcp fixes Direct support for PCP archive in the pmatop utility BZ# 1196540 Previously, on IBM S/390 platforms, unanticipated formatting in the /proc/cpuinfo file negatively affected the PCP Linux kernel PMDA. As a consequence, the agent terminated unexpectedly with a segmentation fault when accessing certain processor related performance metrics. This update fixes parsing of /proc/cpuinfo for IBM S/390, and all PCP processor metrics are now fully functional and robust on this platform. BZ# 1131022 Previously, the PCP pmlogger daemon start script started the daemon only if the pmlogger service was enabled by the "chkconfig on" command. Consequently, the daemon silently failed to start when the service was disabled. With this update, additional diagnostics have been added to the start script. Now, when attempting to start the pmlogger daemon with the pmlogger service disabled, the user is properly informed and given instructions on how to eliminate the problem. Users of pcp are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
7.33. cronie 7.33.1. RHBA-2015:0754 - cronie bug fix update Updated cronie packages that fix one bug are now available for Red Hat Enterprise Linux 6. The cronie packages contain the standard UNIX daemon crond that runs specified programs at scheduled times and related tools. They are a fork of the original vixie-cron cron implementation and have security and configuration enhancements like the ability to use pam and SELinux. Bug Fix BZ# 1204175 Due to a regression in parsing the /etc/anacrontab file caused by the cronie erratum released in the Fastrack channel, environment variables set in the /etc/anacrontab file were not recognized, and error messages were logged. These updated cronie packages fix the regression, and the variables are now set correctly for anacron jobs. Users of cronie are advised to upgrade to these updated packages, which fix this bug. 7.33.2. RHBA-2015:0704 - cronie bug fix and enhancement update Updated cronie packages that fix two bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The cronie packages contain the standard UNIX daemon crond that runs specified programs at scheduled times and the anacron tool that enables crond to run jobs also on machines that are not continuously switched on. Bug Fixes BZ# 1031383 Previously, the anacron process could terminate unexpectedly in cases when the anacrontab file contained incorrect configuration settings. To fix this bug, the configuration settings format check has been amended, and the anacron process no longer crashes. BZ# 1082232 Prior to this update, the crond pid file could be erroneously removed in case a crond sub-process terminated unexpectedly. With this update, handling of the crond sub-processes termination has been corrected, and the removal no longer occurs. Enhancements BZ# 1108384 The crond daemon now logs shutdowns. Its proper terminations are therefore distinguishable from abnormal ones. BZ# 1123984 The crond daemon now logs errors when jobs are skipped due to getpwnam() call failures. Users of cronie are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 4. Tools and components Learn more about the Red Hat Ansible Automation Platform tools and components you will use in creating automation execution environments. 4.1. About Ansible Builder Ansible Builder is a command line tool that automates the process of building automation execution environments by using the metadata defined in various Ansible Collections or by the user. Before Ansible Builder was developed, Red Hat Ansible Automation Platform users could run into dependency issues and errors when creating custom virtual environments or containers that included all of the required dependencies installed. Now, with Ansible Builder, you can easily create a customizable automation execution environments definition file that specifies the content you want to be included in your automation execution environments such as collections, third-party Python requirements, and system-level packages. This allows you to fulfill all of the necessary requirements and dependencies to get jobs running. Note Red Hat currently does not support users who choose to provide their own container images when building automation automation execution environments. 4.2. Uses for Automation content navigator Automation content navigator is a command line, content-creator-focused tool with a text-based user interface. You can use Automation content navigator to: Launch and watch jobs and playbooks. Share stored, completed playbook and job run artifacts in JSON format. Browse and introspect automation execution environments. Browse your file-based inventory. Render Ansible module documentation and extract examples you can use in your playbooks. View a detailed command output on the user interface. 4.3. About automation hub Automation hub provides a place for Red Hat subscribers to quickly find and use content that is supported by Red Hat and our technology partners to deliver additional reassurance for the most demanding environments. At a high level, automation hub provides an overview of all partners participating and providing certified, supported content. From a central view, users can dive deeper into each partner and check out the collections. Additionally, a searchable overview of all available collections is available. 4.4. About the Ansible command line interface Using Ansible on the command line is a useful way to run tasks that you do not repeat very often. The recommended way to handle repeated tasks is to write a playbook. An ad hoc command for Ansible on the command line follows this structure: USD ansible [pattern] -m [module] -a "[module options]" 4.5. Additional resources For more information on how to use Ansible as a command line tool, refer to working with command line tools in the Ansible User Guide . To upload content to automation hub, see Uploading content to automation hub in the Ansible Automation Platform product documentation.

Commands:
ansible [pattern] -m [module] -a "[module options]"
3.17. Starting a Virtual Machine with Cloud-Init This Ruby example starts a virtual machine using the Cloud-Init tool to set the root password and network configuration. # Find the virtual machine: vms_service = connection.system_service.vms_service vm = vms_service.list(search: 'name=myvm')[0] # Find the service that manages the virtual machine: vm_service = vms_service.vm_service(vm.id) # Create a cloud-init script to execute in the # deployed virtual machine. The script must be correctly # formatted and indented because it uses YAML. my_script = " write_files: - content: | Hello, world! path: /tmp/greeting.txt permissions: '0644' " # Start the virtual machine, enabling cloud-init and providing the # password for the `root` user and the network configuration: vm_service.start( use_cloud_init: true, vm: { initialization: { user_name: 'root', root_password: 'redhat123', host_name: 'myvm.example.com', nic_configurations: [ { name: 'eth0', on_boot: true, boot_protocol: OvirtSDK4::BootProtocol::STATIC, ip: { version: OvirtSDK4::IpVersion::V4, address: '192.168.0.100', netmask: '255.255.255.0', gateway: '192.168.0.1' } } ], dns_servers: '192.168.0.1 192.168.0.2 192.168.0.3', dns_search: 'example.com', custom_script: my_script } } ) For more information, see VmService:start .

Commands:
Find the virtual machine: vms_service = connection.system_service.vms_service vm = vms_service.list(search: 'name=myvm')[0] Find the service that manages the virtual machine: vm_service = vms_service.vm_service(vm.id) Create a cloud-init script to execute in the deployed virtual machine. The script must be correctly formatted and indented because it uses YAML. my_script = " write_files: - content: | Hello, world! path: /tmp/greeting.txt permissions: '0644' " Start the virtual machine, enabling cloud-init and providing the password for the `root` user and the network configuration: vm_service.start( use_cloud_init: true, vm: { initialization: { user_name: 'root', root_password: 'redhat123', host_name: 'myvm.example.com', nic_configurations: [ { name: 'eth0', on_boot: true, boot_protocol: OvirtSDK4::BootProtocol::STATIC, ip: { version: OvirtSDK4::IpVersion::V4, address: '192.168.0.100', netmask: '255.255.255.0', gateway: '192.168.0.1' } } ], dns_servers: '192.168.0.1 192.168.0.2 192.168.0.3', dns_search: 'example.com', custom_script: my_script } } )
8.197. seabios 8.197.1. RHBA-2013:1655 - seabios bug fix and enhancement update Updated seabios packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The seabios packages contain an open-source legacy BIOS implementation which can be used as a coreboot payload. It implements the standard BIOS calling interfaces that a typical x86 proprietary BIOS implements. Bug Fixes BZ# 846519 Due to a bug in the Advanced Configuration and Power Interface (ACPI) description table, a stop error (known as Blue Screen of Death, or BSoD) could occur on certain Windows guests. The problem was observed on the guests using the virtio-win small computer system interface (SCSI) drivers during heavy S3 and S4 power state transitions, for example when running the CrystalDiskMark benchmark. A patch has been applied to fix this bug, and a stop error no longer occurs in the described scenario. BZ# 846912 The multiple ACPI description table (MADT) previously contained an incorrect definition. Consequently, after switching to the S3 or S4 power state, the SCSI driver could not have been disabled and was always attached to the Global System Interrupt (GSI) number 9. The incorrect MADT definition has been fixed and the SCSI driver can now be disabled and enabled in this situation as expected. BZ# 888633 The SeaBIOS utility previously allowed booting even from deselected devices when no bootable device was found. This problem has been fixed by adding support for the HALT instruction, which prevents SeaBIOS from default boot attempts if no bootable device is available. Enhancements BZ#876250 With this update, the SMBIOS GUID number (the same number as the system's UUID) is now displayed on the BIOS Power-on self-test (POST) screen. BZ#963312 This update modifies the virsh management user interface so the "virsh dump" command now supports automatic core dumps. With appropriate kdump mechanism settings, the vmcore file is automatically captured and the subsequent actions are executed automatically. Users of seabios are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
11.3. Date Specifications Date specifications are used to create cron-like expressions relating to time. Each field can contain a single number or a single range. Instead of defaulting to zero, any field not supplied is ignored. For example, monthdays="1" matches the first day of every month and hours="09-17" matches the hours between 9 am and 5 pm (inclusive). However, you cannot specify weekdays="1,2" or weekdays="1-2,5-6" since they contain multiple ranges. Table 11.5. Properties of a Date Specification Field Description id A unique name for the date hours Allowed values: 0-23 monthdays Allowed values: 0-31 (depending on month and year) weekdays Allowed values: 1-7 (1=Monday, 7=Sunday) yeardays Allowed values: 1-366 (depending on the year) months Allowed values: 1-12 weeks Allowed values: 1-53 (depending on weekyear ) years Year according the Gregorian calendar weekyears May differ from Gregorian years; for example, 2005-001 Ordinal is also 2005-01-01 Gregorian is also 2004-W53-6 Weekly moon Allowed values: 0-7 (0 is new, 4 is full moon).

Commands:
Chapter 1. Overview AMQ .NET is a lightweight AMQP 1.0 library for the .NET platform. It enables you to write .NET applications that send and receive AMQP messages. AMQ .NET is part of AMQ Clients, a suite of messaging libraries supporting multiple languages and platforms. For an overview of the clients, see AMQ Clients Overview . For information about this release, see AMQ Clients 2.10 Release Notes . AMQ .NET is based on AMQP.Net Lite . For detailed API documentation, see the AMQ .NET API reference . 1.1. Key features SSL/TLS for secure communication Flexible SASL authentication Seamless conversion between AMQP and native data types Access to all the features and capabilities of AMQP 1.0 An integrated development environment with full IntelliSense API documentation 1.2. Supported standards and protocols AMQ .NET supports the following industry-recognized standards and network protocols: Version 1.0 of the Advanced Message Queueing Protocol (AMQP) Versions 1.0, 1.1, 1.2, and 1.3 of the Transport Layer Security (TLS) protocol, the successor to SSL Simple Authentication and Security Layer (SASL) mechanisms ANONYMOUS, PLAIN, and EXTERNAL Modern TCP with IPv6 1.3. Supported configurations Refer to Red Hat AMQ 7 Supported Configurations on the Red Hat Customer Portal for current information regarding AMQ .NET supported configurations. 1.4. Terms and concepts This section introduces the core API entities and describes how they operate together. Table 1.1. API terms Entity Description Connection A channel for communication between two peers on a network Session A context for sending and receiving messages Sender link A channel for sending messages to a target Receiver link A channel for receiving messages from a source Source A named point of origin for messages Target A named destination for messages Message A mutable holder of application data AMQ .NET sends and receives messages . Messages are transferred between connected peers over links . Links are established over sessions . Sessions are established over connections . A sending peer creates a sender link to send messages. The sender link has a target that identifies a queue or topic at the remote peer. A receiving client creates a receiver link to receive messages. The receiver link has a source that identifies a queue or topic at the remote peer. 1.5. Document conventions The sudo command In this document, sudo is used for any command that requires root privileges. Exercise caution when using sudo because any changes can affect the entire system. For more information about sudo , see Using the sudo command . File paths In this document, all file paths are valid for Linux, UNIX, and similar operating systems (for example, /home/andrea ). On Microsoft Windows, you must use the equivalent Windows paths (for example, C:\Users\andrea ). Variable text This document contains code blocks with variables that you must replace with values specific to your environment. Variable text is enclosed in arrow braces and styled as italic monospace. For example, in the following command, replace <project-dir> with the value for your environment: USD cd <project-dir>

Commands:
cd <project-dir>
3.4. Guest CPU Models CPU models define which host CPU features are exposed to the guest operating system. KVM and libvirt contain definitions for several current processor models, allowing users to enable CPU features that are available only in newer CPU models. The set of CPU features that can be exposed to guests depends on support in the host CPU, the kernel, and KVM code. To ensure safe migration of virtual machines between hosts with different sets of CPU features, KVM does not expose all features of the host CPU to guest operating systems by default. Instead, CPU features are based on the selected CPU model. If a virtual machine has a given CPU feature enabled, it cannot be migrated to a host that does not support exposing that feature to guests. Note For more information on guest CPU models, refer to the Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide .

Commands: