mtpti5iD/redhat-docs_dataset huggingface dataset:
Technical Notes Red Hat Virtualization 4.3 Technical notes for Red Hat Virtualization 4.3 and associated packages Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract The Technical Notes document provides information about changes made between release 4.2 and release 4.3 of Red Hat Virtualization. This document is intended to supplement the information contained in the text of the relevant errata advisories available through the Content Delivery Network.

Commands:
Chapter 5. Checking DNS records using IdM Healthcheck You can identify issues with DNS records in Identity Management (IdM) using the Healthcheck tool. 5.1. DNS records healthcheck test The Healthcheck tool includes a test for checking that the expected DNS records required for autodiscovery are resolvable. To list all tests, run the ipa-healthcheck with the --list-sources option: You can find the DNS records check test under the ipahealthcheck.ipa.idns source. IPADNSSystemRecordsCheck This test checks the DNS records from the ipa dns-update-system-records --dry-run command using the first resolver specified in the /etc/resolv.conf file. The records are tested on the IPA server. 5.2. Screening DNS records using the healthcheck tool Follow this procedure to run a standalone manual test of DNS records on an Identity Management (IdM) server using the Healthcheck tool. The Healthcheck tool includes many tests. Results can be narrowed down by including only the DNS records tests by adding the --source ipahealthcheck.ipa.idns option. Prerequisites You must perform Healthcheck tests as the root user. Procedure To run the DNS records check, enter: If the record is resolvable, the test returns SUCCESS as a result: The test returns a WARNING when, for example, the number of records does not match the expected number: Additional resources See man ipa-healthcheck .

Commands:
ipa-healthcheck --list-sources
ipa-healthcheck --source ipahealthcheck.ipa.idns
{ "source": "ipahealthcheck.ipa.idns", "check": "IPADNSSystemRecordsCheck", "result": "SUCCESS", "uuid": "eb7a3b68-f6b2-4631-af01-798cac0eb018", "when": "20200415143339Z", "duration": "0.210471", "kw": { "key": "_ldap._tcp.idm.example.com.:server1.idm.example.com." } }
{ "source": "ipahealthcheck.ipa.idns", "check": "IPADNSSystemRecordsCheck", "result": "WARNING", "uuid": "972b7782-1616-48e0-bd5c-49a80c257895", "when": "20200409100614Z", "duration": "0.203049", "kw": { "msg": "Got {count} ipa-ca A records, expected {expected}", "count": 2, "expected": 1 } }
20.16.3. Device Addresses Many devices have an optional <address> sub-element to describe where the device placed on the virtual bus is presented to the guest virtual machine. If an address (or any optional attribute within an address) is omitted on input, libvirt will generate an appropriate address; but an explicit address is required if more control over layout is required. See below for device examples including an address element. Every address has a mandatory attribute type that describes which bus the device is on. The choice of which address to use for a given device is constrained in part by the device and the architecture of the guest virtual machine. For example, a disk device uses type='disk' , while a console device would use type='pci' on the 32-bit AMD and Intel architecture or AMD64 and Intel 64 guest virtual machines, or type='spapr-vio' on PowerPC64 pseries guest virtual machines. Each address <type> has additional optional attributes that control where on the bus the device will be placed. The additional attributes are as follows: type='pci' - PCI addresses have the following additional attributes: domain (a 2-byte hex integer, not currently used by qemu) bus (a hex value between 0 and 0xff, inclusive) slot (a hex value between 0x0 and 0x1f, inclusive) function (a value between 0 and 7, inclusive) Also available is the multifunction attribute, which controls turning on the multifunction bit for a particular slot/function in the PCI control register. This multifunction attribute defaults to 'off' , but should be set to 'on' for function 0 of a slot that will have multiple functions used. type='drive - drive addresses have the following additional attributes: controller - (a 2-digit controller number) bus - (a 2-digit bus number) target - (a 2-digit bus number) unit - (a 2-digit unit number on the bus) type='virtio-serial' - Each virtio-serial address has the following additional attributes: controller - (a 2-digit controller number) bus - (a 2-digit bus number) slot - (a 2-digit slot within the bus) type='ccid' - A CCID address, used for smart-cards, has the following additional attributes: bus - (a 2-digit bus number) slot attribute - (a 2-digit slot within the bus) type='usb' - USB addresses have the following additional attributes: bus - (a hex value between 0 and 0xfff, inclusive) port - (a dotted notation of up to four octets, such as 1.2 or 2.1.3.1) type='spapr-vio - On PowerPC pseries guest virtual machines, devices can be assigned to the SPAPR-VIO bus. It has a flat 64-bit address space; by convention, devices are generally assigned at a non-zero multiple of 0x1000, but other addresses are valid and permitted by libvirt. The additional attribute: reg (the hex value address of the starting register) can be assigned to this attribute.

Commands:
2.2. Failover Post connection failover will be used if you are using an administration connection (such as what is used by AdminShell) or if the autoFailover connection property is set to true. Post connection failover works by sending a ping, at most every second, to test the connection prior to use. If the ping fails, a new instance will be selected prior to the operation being attempted. This is not considered to be true transparent application failover because the client does not restart transactions or queries, nor will it recreate session scoped temporary tables. Warning Extreme caution should be exercised if using this with non-admin connections.

Commands:
Chapter 7. Standalone server vs. servers in a managed domain considerations Setting up identity management with an LDAP server, including Microsoft Active Directory, is essentially the same whether it is used in a standalone server or for servers in a managed domain. In general, this also applies to setting up most identity stores with both security realms and security domains. Just as with any other configuration setting, the standalone configuration resides in the standalone.xml file and the configuration for a managed domain resides in the domain.xml and host.xml files.

Commands:
Chapter 8. Reviewing monitoring dashboards Red Hat OpenShift Service on AWS provides a set of monitoring dashboards that help you understand the state of cluster components and user-defined workloads. 8.1. Monitoring dashboards in the Administrator perspective Use the Administrator perspective to access dashboards for the core Red Hat OpenShift Service on AWS components, including the following items: API performance etcd Kubernetes compute resources Kubernetes network resources Prometheus USE method dashboards relating to cluster and node performance Node performance metrics Figure 8.1. Example dashboard in the Administrator perspective 8.2. Monitoring dashboards in the Developer perspective In the Developer perspective, you can access only the Kubernetes compute resources dashboards: Figure 8.2. Example dashboard in the Developer perspective 8.3. Reviewing monitoring dashboards as a cluster administrator In the Administrator perspective, you can view dashboards relating to core Red Hat OpenShift Service on AWS cluster components. Prerequisites You have access to the cluster as a user with the dedicated-admin role. Procedure In the Administrator perspective of the Red Hat OpenShift Service on AWS web console, go to Observe Dashboards . Choose a dashboard in the Dashboard list. Some dashboards, such as etcd and Prometheus dashboards, produce additional sub-menus when selected. Optional: Select a time range for the graphs in the Time Range list. Select a pre-defined time period. Set a custom time range by clicking Custom time range in the Time Range list. Input or select the From and To dates and times. Click Save to save the custom time range. Optional: Select a Refresh Interval . Hover over each of the graphs within a dashboard to display detailed information about specific items. 8.4. Reviewing monitoring dashboards as a developer In the Developer perspective, you can view dashboards relating to a selected project. Note In the Developer perspective, you can view dashboards for only one project at a time. Prerequisites You have access to the cluster as a developer or as a user. You have view permissions for the project that you are viewing the dashboard for. Procedure In the Developer perspective in the Red Hat OpenShift Service on AWS web console, click Observe and go to the Dashboards tab. Select a project from the Project: drop-down list. Select a dashboard from the Dashboard drop-down list to see the filtered metrics. Note All dashboards produce additional sub-menus when selected, except Kubernetes / Compute Resources / Namespace (Pods) . Optional: Select a time range for the graphs in the Time Range list. Select a pre-defined time period. Set a custom time range by clicking Custom time range in the Time Range list. Input or select the From and To dates and times. Click Save to save the custom time range. Optional: Select a Refresh Interval . Hover over each of the graphs within a dashboard to display detailed information about specific items.

Commands:
15.3.3. Connecting to VNC Server Using SSH VNC is a clear text network protocol with no security against possible attacks on the communication. To make the communication secure, you can encrypt your server-client connection by using the -via option. This will create an SSH tunnel between the VNC server and the client. The format of the command to encrypt a VNC server-client connection is as follows: vncviewer -via user @ host : display_number Example 15.6. Using the -via Option To connect to a VNC server using SSH , enter a command as follows: When you are prompted to, type the password, and confirm by pressing Enter . A window with a remote desktop appears on your screen. For more information on using SSH , see Chapter 14, OpenSSH .

Commands:
vncviewer -via joe@192.168.2.101 127.0.0.1:3
5.7.2. Disk Quota Issues Many times the first thing most people think of when they think about disk quotas is using it to force users to keep their directories clean. While there are sites where this may be the case, it also helps to look at the problem of disk space usage from another perspective. What about applications that, for one reason or another, consume too much disk space? It is not unheard of for applications to fail in ways that cause them to consume all available disk space. In these cases, disk quotas can help limit the damage caused by such errant applications, forcing it to stop before no free space is left on the disk. The hardest part of implementing and managing disk quotas revolves around the limits themselves. What should they be? A simplistic approach would be to divide the disk space by the number of users and/or groups using it, and use the resulting number as the per-user quota. For example, if the system has a 100GB disk drive and 20 users, each user should be given a disk quota of no more than 5GB. That way, each user would be guaranteed 5GB (although the disk would be 100% full at that point). For those operating systems that support it, temporary quotas could be set somewhat higher -- say 7.5GB, with a permanent quota remaining at 5GB. This would have the benefit of allowing users to permanently consume no more than their percentage of the disk, but still permitting some flexibility when a user reaches (and exceeds) their limit. When using disk quotas in this manner, you are actually over-committing the available disk space. The temporary quota is 7.5GB. If all 20 users exceeded their permanent quota at the same time and attempted to approach their temporary quota, that 100GB disk would actually have to be 150GB to allow everyone to reach their temporary quota at the same time. However, in practice not everyone exceeds their permanent quota at the same time, making some amount of overcommitment a reasonable approach. Of course, the selection of permanent and temporary quotas is up to the system administrator, as each site and user community is different.

Commands:
B.51.2. RHBA-2010:0951 - lvm2 bug fix update and enhancement Updated lvm2 packages that fix several bugs and add an enhancement are now available. The lvm2 packages contain support for Logical Volume Management (LVM). Bug Fixes BZ# 651007 Merging of a snapshot volume caused I/O errors to be issued during a reboot. After the reboot the snapshot volume (snapshot of an LV where the root file system resides) was still present and it appeared as if the merge operation was still in progress. With this update, the errors no longer occur and the snapshot merge completes cleanly. BZ# 652185 The optimizer for the regex filter defined in the LVM2 configuration (the 'devices/filter' setting) did not work correctly when using the 'or' operator. This resulted in improper filtering of devices. With this update, the application of the regex filter works as expected. BZ# 652186 Previously, the 'vgchange' command did not allow the '--addtag' and '--deltag' arguments to be used simultaneously. With this update, this restriction is removed. BZ# 652638 Prior to this update, the 'fsadm' script issued an error message about not being able to resize the just unmounted file system because it required the 'force' option to be used. With this update, the 'force' option is not needed anymore and the script proceeds and successfully resizes the file system. Enhancement BZ# 652662 This update adds support for using multiple "--addtag" and "--deltag" arguments within a single command. Users are advised to upgrade to these updated lvm2 packages, which resolve these issues and add this enhancement.

Commands:
12.21. Loopback Translator The Loopback translator, known by the type name loopback, provides a quick testing solution. It supports all SQL constructs and returns default results, with some configurable behaviour. Table 12.16. Registry Properties Name Description Default ThrowError True to always throw an error false RowCount Rows returned for non-update queries. 1 WaitTime True to always throw an error false PollIntervalInMilli if positive results will be "asynchronously" returned - that is a DataNotAvailableException will be thrown initially and the engine will wait the poll interval before polling for the results. -1 DelegateName Set to the name of the translator which is to be mimicked. - You can also use the Loopback translator to mimic how a real source query would be formed for a given translator (although loopback will still return dummy data that may not be useful for your situation). To enable this behavior, set the DelegateName property to the name of the translator you wish to mimic. For example to disable all capabilities, set the DelegateName property to "jdbc-simple". A source connection is not required for this translator.

Commands:
Chapter 4. OVALSTREAMS 4.1. List all OVAL streams Abstract Provides an index to all OVAL stream files from where they can be downloaded. When no parameter is passed, returns a list of all OVAL stream files. JSON XML HTML 4.2. Parameters Name Description Example after Index of OVAL stream files modified after the query date. Expected format: ISO 8601. 2016-02-01 label Index of OVAL stream files for a product version label. jboss-eap-6 isCompressed Return response in compressed 'gzip' format Default: true Note All the above query parameters can be used in combination with each other to retrieve the desired result. 4.3. Retrieve an OVAL stream Abstract Returns the OVAL stream data for a product identified by base name. JSON OVAL stream files are in XML format; the JSON view is a representation of the OVAL data in JSON format. Example: oval/ovalstreams/RHEL7.json Returns a JSON representation of the OVAL streams for Red Hat Enterprise Linux 7. XML Note For more information about the OVAL format see the FAQ . Sample Query URLs https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams.xml https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams.json https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams/RHEL9 https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams/RHEL9.xml https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams/RHEL9.json https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams?label=jboss-eap-8 https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams.xml?label=jboss-eap-8 https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams.json?label=jboss-eap-8 https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams?after=2022-11-30 https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams.xml?after=2022-11-30 https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams.json?after=2022-11-30 https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams?isCompressed=false https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams.json?isCompressed=false https://access.redhat.com/hydra/rest/securitydata/oval/ovalstreams?after=2022-11-30&isCompressed=false

Commands:
GET oval/ovalstreams.json
GET oval/ovalstreams.xml
GET oval/ovalstreams
By default, returned results are ordered by date.
GET oval/ovalstreams/<BASE>.json
GET oval/ovalstreams/<BASE>.xml
Chapter 25. Red Hat Enterprise Linux Atomic Host 7.4.4 25.1. Atomic Host OStree update : New Tree Version: 7.4.4 (hash: 91b59e14c4eef641f388cbc5b2cbbdd4653a89f4053d684217d9c1c9394c3dd3) Changes since Tree Version 7.4.3 (hash: 83350a7fb3a3ebd09c5996eec5ec8307f61bbb463b999bdfece223288927a60f) Updated packages : cockpit-ostree-157-1.el7 rpm-ostree-client-2017.11-1.atomic.el7 25.2. Extras Updated packages : ansible-2.4.2.0-2.el7 * buildah-0.9-1.git04ea079.el7 cockpit-157-1.el7 container-selinux-2.36-1.gitff95335.el7 docker-1.12.6-71.git3e8e77d.el7 docker-latest-1.13.1-37.git9a813fa.el7 etcd-3.2.11-1.el7 gomtree-0.4.2-2.1.el7 oci-register-machine-0-3.14.gitcd1e331.el7 oci-systemd-hook-0.1.14-2.git9b1e622.el7 oci-umount-2.3.1-2.gitbf16163.el7 ostree-2017.14-2.el7 rhel-system-roles-0.5-3.el7 * runc-1.0.0-23.rc4.dev.git1d3ab6d.el7 skopeo-0.1.27-3.dev.git14245f2.el7 The asterisk (*) marks packages which are available for Red Hat Enterprise Linux only. 25.2.1. Container Images Updated : Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux 7.4 Container Image (rhel7.4, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic Kubernetes apiserver Container Image (rhel7/kubernetes-apiserver) Red Hat Enterprise Linux Atomic Kubernetes controller-manager Container (rhel7/kubernetes-controller-mgr) Red Hat Enterprise Linux Atomic Kubernetes scheduler Container Image (rhel7/kubernetes-scheduler) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic OpenSCAP Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) 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 open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) 25.3. New Features Enhanced documentation for buildah Enhanced coverage of the buildah command describes several new features, including how to build containers from scratch. See Building container images with Buildah . The rpm-ostree command now has several new features. The most notable of them: rpm-ostree ex livefs --replace --download-only and --cache-only rpm-ostree refresh-md have been documented in Package Layering . For other new rpm-ostree features, see the upstream rpm-ostree release notes .

Commands:
1.2. Why Virtualization Security Matters Deploying virtualization in your infrastructure provides many benefits but can also introduce new risks. Virtualized resources and services should be deployed with the following security considerations: The host/hypervisor become prime targets; they are often a single point of failure for guests and data. Virtual machines can interfere with each other in undesirable ways. Assuming no access controls were in place to help prevent this, one malicious guest could bypass a vulnerable hypervisor and directly access other resources on the host system, such as the storage of other guests. Resources and services can become difficult to track and maintain; with rapid deployment of virtualized systems comes an increased need for management of resources, including sufficient patching, monitoring and maintenance. Technical staff may lack knowledge, have gaps in skill sets, and have minimal experience in virtual environments. This is often a gateway to vulnerabilities. Resources such as storage can be spread across, and dependent upon, several machines. This can lead to overly complex environments, and poorly-managed and maintained systems. Virtualization does not remove any of the traditional security risks present in your environment; the entire solution stack, not just the virtualization layer, must be secured. This guide aims to assist you in mitigating your security risks by offering a number of virtualization recommended practices for Red Hat Enterprise Linux that will help you secure your virtualized infrastructure.

Commands:
5.2.2. /proc/buddyinfo This file is used primarily for diagnosing memory fragmentation issues. Using the buddy algorithm, each column represents the number of pages of a certain order (a certain size) that are available at any given time. For example, for zone DMA (direct memory access), there are 90 of 2^(0*PAGE_SIZE) chunks of memory. Similarly, there are 6 of 2^(1*PAGE_SIZE) chunks, and 2 of 2^(2*PAGE_SIZE) chunks of memory available. The DMA row references the first 16 MB on a system, the HighMem row references all memory greater than 4 GB on a system, and the Normal row references all memory in between. The following is an example of the output typical of /proc/buddyinfo :

Commands:
Node 0, zone DMA 90 6 2 1 1 Node 0, zone Normal 1650 310 5 0 0 Node 0, zone HighMem 2 0 0 1 1
Chapter 2. Acknowledgments Red Hat Ceph Storage version 8.0 contains many contributions from the Red Hat Ceph Storage team. In addition, the Ceph project is seeing amazing growth in the quality and quantity of contributions from individuals and organizations in the Ceph community. We would like to thank all members of the Red Hat Ceph Storage team, all of the individual contributors in the Ceph community, and additionally, but not limited to, the contributions from organizations such as: Intel(R) Fujitsu (R) UnitedStack Yahoo TM Ubuntu Kylin Mellanox (R) CERN TM Deutsche Telekom Mirantis (R) SanDisk TM SUSE (R)

Commands:
6.2. s390x Architectures Bugzilla #448777 Systems using zFCP for access to SCSI disks on Red Hat Enterprise Linux 4 require a hardware fibre channel switch to be connected between the mainframe and disk storage. This update enables point-to-point connections, which are fibre connections directly from the mainframe to the disk storage. While connection to a fibre channel switch is still supported, it is no longer required.

Commands: