mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix J. OSD Ansible settings These are the most common configurable OSD Ansible parameters. osd_auto_discovery Automatically find empty devices to use as OSDs. Value false Required No Notes Cannot be used with devices . Cannot be used with purge-docker-cluster.yml or purge-cluster.yml . To use those playbooks, comment out osd_auto_discovery and declare the OSD devices using devices . devices List of devices where Ceph's data is stored. Value User-defined Required Yes, if specifying a list of devices. Notes Cannot be used when osd_auto_discovery setting is used. When using the devices option, ceph-volume lvm batch mode creates the optimized OSD configuration. dmcrypt To encrypt the OSDs. Value true Required No Notes The default value is false . lvm_volumes A list of FileStore or BlueStore dictionaries. Value User-defined Required Yes, if storage devices are not defined using the devices parameter. Notes Each dictionary must contain a data , journal and data_vg keys. Any logical volume or volume group must be the name and not the full path. The data , and journal keys can be a logical volume (LV) or partition, but do not use one journal for multiple data LVs. The data_vg key must be the volume group containing the data LV. Optionally, the journal_vg key can be used to specify the volume group containing the journal LV, if applicable. osds_per_device The number of OSDs to create per device. Value User-defined Required No Notes The default value is 1 . osd_objectstore The Ceph object store type for the OSDs. Value bluestore or filestore Required No Notes The default value is bluestore . Required for upgrades.

Commands:
22.16.5. Adding a Broadcast or Multicast Server Address To add a broadcast or multicast address for sending, that is to say, the address to broadcast or multicast NTP packets to, make use of the broadcast command in the ntp.conf file. The broadcast and multicast modes require authentication by default. See Section 22.6, "Authentication Options for NTP" . The broadcast command takes the following form: broadcast address where address is an IP broadcast or multicast address to which packets are sent. This command configures a system to act as an NTP broadcast server. The address used must be a broadcast or a multicast address. Broadcast address implies the IPv4 address 255.255.255.255 . By default, routers do not pass broadcast messages. The multicast address can be an IPv4 Class D address, or an IPv6 address. The IANA has assigned IPv4 multicast address 224.0.1.1 and IPv6 address FF05::101 (site local) to NTP . Administratively scoped IPv4 multicast addresses can also be used, as described in RFC 2365 Administratively Scoped IP Multicast .

Commands:
Chapter 66. Condition schema reference Used in: KafkaBridgeStatus , KafkaConnectorStatus , KafkaConnectStatus , KafkaMirrorMaker2Status , KafkaMirrorMakerStatus , KafkaNodePoolStatus , KafkaRebalanceStatus , KafkaStatus , KafkaTopicStatus , KafkaUserStatus , StrimziPodSetStatus Property Property type Description type string The unique identifier of a condition, used to distinguish between other conditions in the resource. status string The status of the condition, either True, False or Unknown. lastTransitionTime string Last time the condition of a type changed from one status to another. The required format is 'yyyy-MM-ddTHH:mm:ssZ', in the UTC time zone. reason string The reason for the condition's last transition (a single word in CamelCase). message string Human-readable message indicating details about the condition's last transition.

Commands:
A.4. JBoss Data Grid JGroups Configuration Files The following configuration files are included with JBoss Data Grid and contain the recommended values for JGroups. All of the following files are included in infinispan-embedded-USD{infinispan.version}.jar found with the Library mode distribution. default-configs/default-jgroups-ec2.xml default-configs/default-jgroups-google.xml default-configs/default-jgroups-tcp.xml default-configs/default-jgroups-udp.xml Report a bug

Commands:
4.20. RHEA-2012:0965 - new package: virt-p2v A new virt-p2v package is now available for Red Hat Enterprise Linux 6. Virt-P2V is a tool for conversion of a physical server to a virtual guest. This enhancement update adds the virt-p2v package to Red Hat Enterprise Linux 6, which contains a bootable ISO image for Virt-P2V conversion. The ISO image is also available on Red Hat Network in the Downloads section of the following channels: RHEL AUS Server (v. 6.2 for 64-bit x86_64) RHEL EUS Server (v. 6.2.z for 64-bit x86_64) Red Hat Enterprise Linux Client (v. 6 for 64-bit x86_64) Red Hat Enterprise Linux Compute Node (v. 6 for x86_64) Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64) Red Hat Enterprise Linux Workstation (v. 6 for x86_64) The bootable image is needed to use the tool as the disks must be unmounted and not in use at the time of conversion. It allows you to convert servers running Microsoft Windows or Red Hat Enterprise Linux into virtual guests on Red Hat Enterprise Virtualization or libvirt hosts. For further information, refer to the V2V Guide . (BZ# 807445 ) All users who require virt-p2v should install this new package.

Commands:
Appendix A. Using your subscription Apicurio Registry is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing your account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading ZIP and TAR files To access ZIP or TAR files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat Integration entries in the Integration and Automation category. Select the desired Apicurio Registry product. The Software Downloads page opens. Click the Download link for your component. Revised on 2024-12-20 16:57:50 UTC

Commands:
9.5. Configuring Rules with pcs To configure a rule, use the following command. If score is omitted, it defaults to INFINITY. If id is omitted, one is generated from the constraint_id . The rule_type should be expression or date_expression . To remove a rule, use the following. If the rule that you are removing is the last rule in its constraint, the constraint will be removed.

Commands:
pcs constraint rule add constraint_id [ rule_type ] [score= score [id= rule_id ] expression|date_expression|date_spec options
pcs constraint rule remove rule_id
Chapter 6. Bug fixes The following describes bugs fixed in Red Hat Enterprise Linux that have a significant impact on users. 6.1. Red Hat Enterprise Linux 8.1 for SAP Solutions RHBA-2020:2206 Fixes issue in sap_cluster_connector where nodenames contain hyphens. RHBA-2021:3175 SAPHana: check_for_primary() uses mode instead of actual mode in global.ini as fallback. RHBA-2021:5221 The HANA_CALL_TIMEOUT parameter can't be used because the value is hardcoded, therefore the description should be removed. 6.2. Red Hat Enterprise Linux 8.2 for SAP Solutions RHBA-2021:3374 SAPHana: check_for_primary() uses mode instead of actual mode in global.ini as fallback. 6.3. Red Hat Enterprise Linux 8.4 for SAP Solutions RHBA-2021:3087 SAPHana: check_for_primary() uses mode instead of actual mode in global.ini as fallback. RHBA-2021:5115 The HANA_CALL_TIMEOUT parameter can't be used because the value is hardcoded, therefore the description should be removed. 6.4. Red Hat Enterprise Linux 8.6 for SAP Solutions RHBA-2022:2106 Users could not provide their custom ansible_managed header because of a hard-coded value in the tuned.conf file. RHBA-2022:1983 SAPHANAController: Integrating systemd-based SAP Start-Up Framework for HA solutions for SAP HANA Scale-Out. RHBA-2022:1979 System roles need to be ansible-lint clean. This update prepares rhel-system-roles-sap for Ansible Collections. RHBA-2022:1981 SAPHana: Integrating systemd based SAP Start-Up Framework for HA solutions for SAP HANA.

Commands:
Chapter 55. Starting an IT Orders case in the Showcase application You can start a new case instance for the IT Orders sample case management project in the Showcase application. The IT Orders sample case management project includes the following roles: owner : The employee who is making the hardware order request. There can be only one of these roles. manager : The employee's manager; the person who will approve or deny the requested hardware. There is only one manager in the IT Orders project. supplier : The available suppliers of IT hardware in the system. There is usually more than one supplier. These roles are configured at the case definition level: Figure 55.1. ITOrders Case Roles Assign users or groups to these roles when starting a new case file instance. Prerequisites You have imported and deployed the IT Orders sample project in Business Central. You have installed and logged in to the Showcase application as instructed in Chapter 52, Installing and logging in to the Showcase application . Procedure In the Showcase application, start a new case instance by clicking the Start Case button. Select the Order for IT hardware case name from the list and complete the role information as shown: In this example, Aimee is the case owner , Katy is the manager , and the supplier group is supplier . Click Start to start the case instance. Select the case from the Case List . The Overview page opens. From the Overview page, you can monitor the case progress, add comments, start new dynamic tasks and processes, and complete and close cases. Note Cases can be started and closed using the Showcase application, but they cannot be reopened using this application. You can only reopen a case using a JMS or REST API call.

Commands:
Chapter 23. Smart-card Authentication in Identity Management Authentication based on smart cards is an alternative to passwords. User credentials are stored on the smart card, and special software and hardware is used to access them. The user places the smart card into a reader and supplies the PIN code for the smart card. This chapter describes how an administrator can configure smart card-based authentication in Identity Management and how users can use smart cards to authenticate to Identity Management. 23.1. Exporting a Certificate From a Smart Card To export the certificate: Place the smart card into the reader. Use the following command to list the certificates on the smart card. In the output, locate the certificate to use for authentication, and note its nickname: Extract the certificate to a file using the certificate nickname. For example, to extract the certificate in the Base64 format to a file named user.crt : The base64 utility is part of the coreutils package.

Commands:
certutil -L -d /etc/pki/nssdb/ -h all Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI my_certificate CT,C,C
certutil -L -d /etc/pki/nssdb/ -n ' my_certificate ' -r | base64 -w 0 > user.crt
4.15. Using MACsec Media Access Control Security ( MACsec , IEEE 802.1AE) encrypts and authenticates all traffic in LANs with the GCM-AES-128 algorithm. MACsec can protect not only IP but also Address Resolution Protocol (ARP), Neighbor Discovery (ND), or DHCP . While IPsec operates on the network layer (layer 3) and SSL or TLS on the application layer (layer 7), MACsec operates in the data link layer (layer 2). Combine MACsec with security protocols for other networking layers to take advantage of different security features that these standards provide. See the MACsec: a different solution to encrypt network traffic article for more information about the architecture of a MACsec network, use case scenarios, and configuration examples. For examples how to configure MACsec using wpa_supplicant and NetworkManager , see the Red Hat Enterprise Linux 7 Networking Guide .

Commands:
probe::ipmib.FragOKs Name probe::ipmib.FragOKs - Count datagram fragmented successfully Synopsis ipmib.FragOKs Values skb pointer to the struct sk_buff being acted on op value to be added to the counter (default value of 1) Description The packet pointed to by skb is filtered by the function ipmib_filter_key . If the packet passes the filter is is counted in the global FragOKs (equivalent to SNMP's MIB IPSTATS_MIB_FRAGOKS)

Commands:
probe::ioblock.end Name probe::ioblock.end - Fires whenever a block I/O transfer is complete. Synopsis Values None Description name - name of the probe point devname - block device name ino - i-node number of the mapped file bytes_done - number of bytes transferred sector - beginning sector for the entire bio flags - see below BIO_UPTODATE 0 ok after I/O completion BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block BIO_EOF 2 out-out-bounds error BIO_SEG_VALID 3 nr_hw_seg valid BIO_CLONED 4 doesn't own data BIO_BOUNCED 5 bio is a bounce bio BIO_USER_MAPPED 6 contains user pages BIO_EOPNOTSUPP 7 not supported error - 0 on success rw - binary trace for read/write request vcnt - bio vector count which represents number of array element (page, offset, length) which makes up this I/O request idx - offset into the bio vector array phys_segments - number of segments in this bio after physical address coalescing is performed. hw_segments - number of segments after physical and DMA remapping hardware coalescing is performed size - total size in bytes Context The process signals the transfer is done.

Commands:
ioblock.end
Chapter 74. Condition schema reference Used in: KafkaBridgeStatus , KafkaConnectorStatus , KafkaConnectStatus , KafkaMirrorMaker2Status , KafkaMirrorMakerStatus , KafkaNodePoolStatus , KafkaRebalanceStatus , KafkaStatus , KafkaTopicStatus , KafkaUserStatus , StrimziPodSetStatus Property Property type Description type string The unique identifier of a condition, used to distinguish between other conditions in the resource. status string The status of the condition, either True, False or Unknown. lastTransitionTime string Last time the condition of a type changed from one status to another. The required format is 'yyyy-MM-ddTHH:mm:ssZ', in the UTC time zone. reason string The reason for the condition's last transition (a single word in CamelCase). message string Human-readable message indicating details about the condition's last transition.

Commands:
5.251. ppc64-utils 5.251.1. RHEA-2012:0815 - ppc64-utils enhancement update An updated ppc64-utils package that adds one enhancement is now available for Red Hat Enterprise Linux 6. The ppc64-utils package is a collection of utilities for Linux running on 64-bit PowerPC platforms. Enhancement BZ# 739123 By adding the ppc64-diag package into Red Hat Enterprise Linux 6, the ppc64-utils package became dependent on ppc64-diag. This update modifies the spec file of ppc64-utils so that ppc64-diag is now included as a prerequisite of ppc64-utils. All users of ppc64-utils are advised to upgrade to this updated package, which adds this enhancement.

Commands:
Chapter 5. Fixed issues The issues fixed in AMQ Streams 1.7 on RHEL are shown in the following table. For details of the issues fixed in Kafka 2.7.0, refer to the Kafka 2.7.0 Release Notes . Issue Number Description ENTMQST-2030 If the bin/kafka-acls.sh utility is used to add or remove an ACL, the operation is successful but a warning is generated ENTMQST-2188 MirrorMaker: Enable synchronization of offsets to the consumer group on the target cluster ENTMQST-2269 kafka-configs.sh is deprecating --zookeeper option but does not provide alternative functionality to list configs for users

Commands:
3.6. Listing ISO Files in the ISO Storage Domain This Ruby example lists the ISO files in the ISO storage domain, myiso . # Get the reference to the root of the services tree: system_service = connection.system_service # Find the service that manages the collection of storage domains: sds_service = system_service.storage_domains_service # Find the ISO storage domain: sd = sds_service.list(search: 'name=myiso').first # Find the service that manages the ISO storage domain: sd_service = sds_service.storage_domain_service(sd.id) # Find the service that manages the collection of files available in the storage domain: files_service = sd_service.files_service # List the names of the files. Note that the name of the .iso file is contained # in the `id` attribute. files = files_service.list files.each do |file| puts file.id end For more information, see http://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4%2FFilesService:list . If you do not know the name of the ISO storage domain, this Ruby example retrieves all the ISO storage domains. # Find the ISO storage domain: iso_sds = sds_service.list.select { |sd| sd.type == OvirtSDK4::StorageDomainType::ISO } For more information, see http://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4/StorageDomainsService:list .

Commands:
Get the reference to the root of the services tree: system_service = connection.system_service Find the service that manages the collection of storage domains: sds_service = system_service.storage_domains_service Find the ISO storage domain: sd = sds_service.list(search: 'name=myiso').first Find the service that manages the ISO storage domain: sd_service = sds_service.storage_domain_service(sd.id) Find the service that manages the collection of files available in the storage domain: files_service = sd_service.files_service List the names of the files. Note that the name of the .iso file is contained in the `id` attribute. files = files_service.list files.each do |file| puts file.id end
Find the ISO storage domain: iso_sds = sds_service.list.select { |sd| sd.type == OvirtSDK4::StorageDomainType::ISO }
17.2.2.3. Shell Commands Option fields allow access rules to launch shell commands through the following two directives: spawn - Launches a shell command as a child process. This option directive can perform tasks like using /usr/sbin/safe_finger to get more information about the requesting client or create special log files using the echo command. In the following example, clients attempting to access Telnet services from the example.com domain are quietly logged to a special file: twist - Replaces the requested service with the specified command. This directive is often used to set up traps for intruders (also called "honey pots"). It can also be used to send messages to connecting clients. The twist directive must occur at the end of the rule line. In the following example, clients attempting to access FTP services from the example.com domain are sent a message via the echo command: For more information about shell command options, refer to the hosts_options man page.

Commands:
in.telnetd : .example.com : spawn /bin/echo `/bin/date` from %h>>/var/log/telnet.log : allow
vsftpd : .example.com : twist /bin/echo "421 Bad hacker, go away!"
Appendix A. Revision History Revision History Revision 3.2-7 Wed Dec 20 2023 Lenka Spackova Fixed broken links and anchors. Revision 3.2-6 Fri Nov 12 2021 Lenka Spackova Updated Section 4.7, "Database Connectors" . Revision 3.2-5 Wed May 01 2019 Lenka Spackova Fixed typos. Revision 3.2-4 Wed Mar 13 2019 Lenka Spackova Added information on the new rh-jmc Software Collection, available with RHEA-2019:0543 . Revision 3.2-3 Thu Dec 20 2018 Lenka Spackova Updated EOL components. Revision 3.2-2 Tue Dec 18 2018 Lenka Spackova Fixed syntax of a command in the PostgreSQL migration chapter. Revision 3.2-1 Tue Nov 13 2018 Lenka Spackova Release of Red Hat Software Collections 3.2 Release Notes. Revision 3.2-0 Tue Oct 23 2018 Lenka Spackova Release of Red Hat Software Collections 3.2 Beta Release Notes.

Commands:
4.4.4. Changing the Parameters of a Logical Volume Group To change the parameters of a logical volume, use the lvchange command. For a listing of the parameters you can change, see the lvchange (8) man page. You can use the lvchange command to activate and deactivate logical volumes. To activate and deactivate all the logical volumes in a volume group at the same time, use the vgchange command, as described in Section 4.3.6, "Changing the Parameters of a Volume Group" . The following command changes the permission on volume lvol1 in volume group vg00 to be read-only.

Commands:
lvchange -pr vg00/lvol1
Chapter 33. Red Hat Enterprise Linux Atomic Host 7.3.3 33.1. Atomic Host OStree update : New Tree Version: 7.3.3 (hash: bfc591ba1a4395c6b8e54d34964b05df4a61e0d82d20cc1a2fd817855c7e2da5) Changes since Tree Version 7.3.2-1 (hash: 69a74a4ed6954492a7c82279f6efe59bffb8952e95577f8359a6717d57a36774) Updated packages : cockpit-ostree-131-3.el7 rpm-ostree-client-2017.1-6.atomic.el7 New packages (rhel-atomic container only) : librhsm-0.0.1-1.el7 libdnf-0.7.4-2.el7 microdnf-2-2.el7.1.1 33.2. Extras Updated packages : atomic-1.15.3-1.el7 cockpit-131-3.el7 docker-latest-1.12.6-11.el7 docker-distribution-2.6.0-1.el7 * flannel-0.7.0-1.el7 kubernetes-1.5.2-0.2.gitc55cf2b.el7 etcd-3.1.0-2.el7 openscap-docker-7.3.3-2 python-docker-py-1.10.6-1.el7 gomtree-0.3.1-1.el7 runc-1.0.0-2.rc2.el7 skopeo-0.1.18-1.el7 New packages : container-selinux-2.9-4.el7 ostree-2017.1-3.atomic.el7 ostree-fuse-2017.1-3.atomic.el7 The asterisk (*) marks packages which are available for Red Hat Enterprise Linux only. 33.2.1. Container Images New Red Hat Enterprise Linux Atomic Image (rhel7/rhel-atomic) Updated : Red Hat Enterprise Linux 7.3.3 Container Image (rhel7/rhel) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic openscap (rhel7/openscap) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux Atomic Kubernetes-apiserver Container Image (rhel7/kubernetes-apiserver) Red Hat Enterprise Linux Atomic Kubernetes-scheduler Container Image (rhel7/kubernetes-scheduler) Red Hat Enterprise Linux Atomic Kubernetes-controller Container Image (rhel7/kubernetes-controller-mgr) 33.3. New Features MicroDNF The microdnf package ( microdnf-2-2.el7.1.1 ) contains a limited functionality package manager written in C. This minimal subscription-manager plugin implementation for microdnf does not enable any repositories by default. As a consequence, all repositories managed by subscription-manager are disabled in container. To enable the necessary repositories, use the --enablerepo option. For example: This way, you can install packages from repositories managed by subscription-manager by enabling them manually. The microdnf package is added to the rhel-atomic minimal base image to replace the yum facility. It has a limited number of features from the dnf command that only allow you to enable or disable repositories, install and remove packages, and clean out cache. Run microdnf --help from inside of the rhel-atomic container to see all available options.

Commands:
microdnf install --enablerepo rhel-7-server-rpms httpd