mtpti5iD/redhat-docs_dataset huggingface dataset:
C.4. Specifying Time Values When specifying time values for LVM selection, you can use either a standardized time specification format or a more free-form specification, as described in Section C.4.1, "Standard time selection format" and Section C.4.2, "Freeform time selection format" . You can specify the way time values are displayed with the report/time format configuration option in the /etc/lvm/lvm.conf configuration file. Information on specifying this option is provided in the lvm.conf file. When specifying time values, you can use the comparison operator aliases since , after , until , and before , as described in Table C.3, "Selection Criteria Comparison Operators" . C.4.1. Standard time selection format You can specify time values for LVM selection in the following format. Table C.15, "Time Specification Formats" summarizes the formats you can use when specifying these time values. Table C.15. Time Specification Formats Field Field Value date YYYY-MM-DD YYYY-MM, auto DD=1 YYYY, auto MM=01 and DD=01 time hh:mm:ss hh:mm, auto ss=0 hh, auto mm=0, auto ss=0 timezone (always with + or - sign) +hh:mm or -hh:mm +hh or -hh The full date/time specification is YYYY-MM-DD hh:mm:ss. Users are able to leave date/time parts from right to left. Whenever these parts are left out, a range is assumed automatically with second granularity. For example: "2015-07-07 9:51" means range of "2015-07-07 9:51:00" - "2015-07-07 9:51:59" "2015-07" means range of "2015-07-01 0:00:00" - "2015-07-31 23:59:59" "2015" means range of "2015-01-01 0:00:00" - "2015-12-31 23:59:59" The following examples show the date/time specification as used in selection criteria. C.4.2. Freeform time selection format You can specify the date/time specification in LVM selection criteria using the following entitles. weekday names ("Sunday" - "Saturday" or abbreviated as "Sun" - "Sat") labels for points in time ("noon", "midnight") labels for a day relative to current day ("today", "yesterday") points back in time with relative offset from today (N is a number) ( "N" "seconds"/"minutes"/"hours"/"days"/"weeks"/"years" "ago") ( "N" "secs"/"mins"/"hrs" ... "ago") ( "N" "s"/"m"/"h" ... "ago") time specification either in hh:mm:ss format or with AM/PM suffixes month names ("January" - "December" or abbreviated as "Jan" - "Dec") The following examples the show the freeform date/time specification as used in selection criteria.

Commands:
date time timezone
lvs -S 'time since "2015-07-07 9:51"' lvs -S 'time = "2015-07"" lvs -S 'time = "2015"'
lvs -S 'time since "yesterday 9AM"' lvs -S 'time since "Feb 3 years 2 months ago"' lvs -S 'time = "February 2015"' lvs -S 'time since "Jan 15 2015" && time until yesterday' lvs -S 'time since "today 6AM"'
Chapter 1. All-in-one Red Hat OpenStack Platform installation The all-in-one installation method uses TripleO to deploy Red Hat OpenStack Platform and related services with a simple, single-node environment. Use this installation to enable proof-of-concept, development, and test deployments on a single node with limited or no follow-up operations. 1.1. Prerequisites Your system must have two network interfaces and a base operating system installed. Example network configuration Interface eth0 assigned to the default network 192.168.122.0/24 Interface eth1 assigned to the management network 192.168.25.0/24

Commands:
12.2. Support for Non-Serializable Objects A common user concern is whether Red Hat JBoss Data Grid supports the storage of non-serializable objects. In JBoss Data Grid, marshalling is supported for non-serializable key-value objects; users can provide externalizer implementations for non-serializable objects. If you are unable to retrofit Serializable or Externalizable support into your classes, you could (as an example) use XStream to convert the non-serializable objects into a String that can be stored in JBoss Data Grid. Note XStream slows down the process of storing key-value objects due to the required XML transformations. Report a bug

Commands:
20.2. Kernel Configuration Changes Hardware Enablement DEVFREQ_GOV_SIMPLE_ONDEMAND (enabled) GPIO IRQCHIP (enabled) HID plantronic (disabled) I2C sensors JC42 (disabled) NTC thermostat (enabled) I2C MUX (enabled) Networking Driver Support Broadcom B44 driver (disabled) Brocade BNA driver (disabled) Calxeda driver(disabled) IBM ethernet driver [ehea] (disabled) Intel E1000 driver (disabled) Mellanox driver [mlxsw] (disabled) Netronoma driver [NFP] (disabled) Qlogic [qla3xxx] driver (disabled) SFC falcon driver (disabled) Wireless (disabled) WLAN (disabled) Ath driver (disabled) Ath10k driver (disabled) Ath 9k driver (disabled) Ath wil6210 (disabled) Broadcom WLAN (disabled) Broadcom brcm80211 (disabled) Intel WLAN (disabled) Intel iwlegacy (disabled) Intel iwlwifi (disabled) Marvell driver (disabled) Marvell mwiflex (disabled) Ralink WLAN driver (disabled) Ralink rt2x00 driver (disabled) Realtek driver (disabled) Realtek rt1818x driver (disabled) Realtek rtiwifi driver (disabled) NVME driver + target driver (enabled) ptp 1588 driver (disabled) s390 HMC driver (disabled) RTL8192e driver (disabled) RTL8712u driver (disabled) Serial UARTLITE driver (enabled) USB LED trigger USBPORT (disabled) USBIP driver (disabled) Power Mgt Deubg + Adv Debug + Sleep Debug (enabled) Core Kernel Support Sched Imbalance patchset (enabled) OPTprobes, kprobe on ftrace (enabled) 64bit Aligned Access (disabled) Arch Soft Dirty (enabled) Arch MMAP Rnd Compat (disabled) SWIOTLB (disabled) Crypto: akcipher, rsa (enabled) Compression: Kernel gzip support (enabled) Kernel XZ support (enabled) Locking: Mutex spin on owner (enabled in debugging kernel) Function Tracer (enabled) Dynamic Ftrace (enabled) Ftrace mcount record (enabled) Common kernel Libaries Rational (enabled) Btree (enabled) libfdt (enabled) parman (disabled) MM NO_BOOTMEM (enabled) MOVABLE NODE (enabled) HMM (Hetrogenous Memory Management) (enabled) HMM Mirrored (enabled) Coherent Device Memory (CDM) (enabled) Zone Device (enabled) IMA (enabled) YAMA (disabled) Networking Stack Support Compact Netlink Msg (disabled) BPF_JIT (enabled) DCCP (disabled) CCIDS (disabled) IPv6 NF target NPT (disabled) Mac80211 (disabled) Desktop, Graphic, and GPU Support DRM_DP_AUX_CHARDEV (enabled) STK1160 video usb driver (disabled) V412 BUF2_DMA_SG (enabled) Storage Support DAX (disabled) NVDIMM + PFN + DAX (enabled) SCSI 3Ware 9xxx driver (disabled) 3Ware sAS driver (disabled) ARCMSR driver (disabled) AIC79xx driver (disabled) Broadcom Bnx2x driver (enabled) Broadcom Bnx2 driver (disabled) QED driver (disabled) QEDI driver (disabled) File Systems BTRFS (disabled) DLM (disabled) GFS2 DLM locking support (disabled) Virtualization and KVM Support vhost [vsock] (disabled) VMWare vsock (disabled)

Commands:
4.4.4. Disabling/Enabling Quota Enforcement Enforcement of quotas can be disabled for a file system without clearing the limits set for all users and groups. Enforcement can also be enabled. Disabling and enabling of quota enforcement is done by changing a tunable parameter, quota_enforce , with the gfs_tool command. The quota_enforce parameter must be disabled or enabled on each node where quota enforcement should be disabled/enabled. Each time the file system is mounted, enforcement is enabled by default. (Disabling is not persistent across unmounts.) Usage MountPoint Specifies the GFS file system to which the actions apply. quota_enforce {0|1} 0 = disabled 1 = enabled Comments A value of 0 disables enforcement. Enforcement can be enabled by running the command with a value of 1 (instead of 0) as the final command line parameter. Even when GFS is not enforcing quotas, it still keeps track of the file-system usage for all users and groups so that quota-usage information does not require rebuilding after re-enabling quotas. Examples This example disables quota enforcement on file system /gfs . This example enables quota enforcement on file system /gfs .

Commands:
gfs_tool settune MountPoint quota_enforce {0|1}
gfs_tool settune /gfs quota_enforce 0
gfs_tool settune /gfs quota_enforce 1
Chapter 8. Installing Using Anaconda This chapter provides step-by-step instructions for installing Red Hat Enterprise Linux using the Anaconda installer. The bulk of this chapter describes installation using the graphical user interface. A text mode is also available for systems with no graphical display, but this mode is limited in certain aspects (for example, custom partitioning is not possible in text mode). If your system does not have the ability to use the graphical mode, you can: Use Kickstart to automate the installation as described in Chapter 27, Kickstart Installations Perform the graphical installation remotely by connecting to the installation system from another computer with a graphical display using the VNC (Virtual Network Computing) protocol - see Chapter 25, Using VNC 8.1. Introduction to Anaconda The Red Hat Enterprise Linux installer, Anaconda , is different from most other operating system installation programs due to its parallel nature. Most installers follow a fixed path: you must choose your language first, then you configure network, then installation type, then partitioning, and so on. There is usually only one way to proceed at any given time. In Anaconda you are only required to select your language and locale first, and then you are presented with a central screen, where you can configure most aspects of the installation in any order you like. This does not apply to all parts of the installation process, however - for example, when installing from a network location, you must configure the network before you can select which packages to install. Some screens will be automatically configured depending on your hardware and the type of media you used to start the installation. You can still change the detected settings in any screen. Screens which have not been automatically configured, and therefore require your attention before you begin the installation, are marked by an exclamation mark. You cannot start the actual installation process before you finish configuring these settings. Additional differences appear in certain screens; notably the custom partitioning process is very different from other Linux distributions. These differences are described in each screen's subsection.

Commands:
Chapter 1. Creating custom repositories Define your repository with third party information to be able to add packages from the third party repository to your customized images. Prerequisites You have administrator access to the Red Hat Hybrid Cloud Console web user interface. You have an account on Red Hat Customer Portal with an Insights subscription. You must have the URL link to your custom repository. Procedure Access the Red Hat Hybrid Cloud Console platform and log in. Click the Settings icon (⚙) in the top right and select Settings . Optionally, access the direct link Repositories . Select Repositories in the left side menu. Click the Add repositories button. The Add repositories wizard opens. Enter the following information: Mandatory - Name. Mandatory - URL. From the drop-down menu, choose the Restrict architecture. You can enable all the architectures or select one. From the dropdown menu, choose the Restrict OS version. You can enable all the OS versions or select one. GPG key - Drag or upload your file with the GPG key. You can also paste the URL or value of the existing GPG key. Optional: If you want to add another repository, click ⊕ Add another repository and repeat the step 5. Click Save . The system validates the repository status. If your repository is marked as Invalid , check the repository URL you added. The Custom Repositories window opens, listing all the custom repositories you added, the architecture you chose, versions, how many packages you added, and the repository status. Verification Open the list of custom repositories and verify that the repository you added is listed.

Commands:
3.3. CPU Monitors cpupower features a selection of monitors that provide idle and sleep state statistics and frequency information and report on processor topology. Some monitors are processor-specific, while others are compatible with any processor. Refer to the cpupower-monitor(1) man page for details on what each monitor measures and which systems they are compatible with. Use the following options with the cpupower monitor command: -l - list all monitors available on your system. -m <monitor1> , <monitor2> - display specific monitors. Their identifiers can be found by running -l . command - display the idle statistics and CPU demands of a specific command.

Commands:
3.19. RHEA-2011:1610 - new packages: spice-gtk New spice-gtk packages are now available for Red Hat Enterprise Linux 6. spice-gtk is a GTK2 widget for SPICE clients. Both virt-manager and virt-viewer can make use of this widget to access virtual machines using the SPICE protocol. This enhancement update adds spice-gtk to Red Hat Enterprise Linux 6. (BZ# 708417 ) All users of SPICE clients such as virt-manager or virt-viewer are advised to install these new packages.

Commands:
Chapter 2. Monitoring architecture Monitoring tools use a client-server model with the client deployed onto the Red Hat OpenStack Platform overcloud nodes. The Rsyslog service provides client-side centralized logging (CL) and collectd with enabled sensubility plugin provides client-side availability monitoring (AM). 2.1. Centralized logging In your Red Hat OpenStack Platform environment, collect the logs from all services in one central location to simplify debugging and administration. These logs come from the operating system, such as syslog and audit log files, infrastructure components such as RabbitMQ and MariaDB, and OpenStack services such as Identity, Compute, and others. The centralized logging toolchain consists of the following components: Log Collection Agent (Rsyslog) Data Store (Elasticsearch) API/Presentation Layer (Kibana) Note Red Hat OpenStack Platform director does not deploy the server-side components for centralized logging. Red Hat does not support the server-side components, including the Elasticsearch database and Kibana. 2.2. Availability monitoring With availability monitoring, you have one central place to monitor the high-level functionality of all components across your entire OpenStack environment. The availability monitoring toolchain consists of several components: Monitoring Agent (collectd with enabled sensubility plugin) Monitoring Relay/Proxy (RabbitMQ) Monitoring Controller/Server (Sensu server) API/Presentation Layer (Uchiwa) Note Red Hat OpenStack Platform director does not deploy the server-side components for availability monitoring. Red Hat does not support the server-side components, including Uchiwa, Sensu Server, the Sensu API plus RabbitMQ, and a Redis instance running on a monitoring node. The availability monitoring components and their interactions are laid out in the following diagrams: Note Items shown in blue denote Red Hat-supported components. Figure 2.1. Availability monitoring architecture at a high level Figure 2.2. Single-node deployment for Red Hat OpenStack Platform Figure 2.3. HA deployment for Red Hat OpenStack Platform

Commands:
2.2. GNOME System Monitor The GNOME desktop environment includes a graphical tool, System Monitor, to assist you in monitoring and modifying the behavior of your system. System Monitor displays basic system information and allows you to monitor system processes and resource or file system usage. System Monitor has four tabs, each of which displays different information about the system. System This tab displays basic information about the system's hardware and software. Processes This tab displays detailed information about active processes and the relationships between those processes. The processes displayed can be filtered to make certain processes easier to find. This tab also lets you perform some actions on the processes displayed, such as start, stop, kill, and change priority. Resources This tab displays the current CPU time usage, memory and swap space usage, and network usage. File Systems This tab lists all mounted file systems, and provides some basic information about each, such as the file system type, mount point, and memory usage. To start System Monitor, press the Super key to enter the Activities Overview, type System Monitor , and then press Enter. For more information about System Monitor, see either the Help menu in the application, or the Red Hat Enterprise Linux 7 System Administrator's Guide .

Commands:
Chapter 28. Red Hat Enterprise Linux Atomic Host 7.4.1 28.1. Atomic Host OStree update : New Tree Version: 7.4.1 (hash: e83c16780259c5272684221e2a6007300d94bbfdc5432f9ab6025300f447145b) Changes since Tree Version 7.4.0 (hash: 846fb0e18e65bd9a62fc9d952627413c6467c33c2d726449a1d7ad7690bbb93a) Updated packages : cockpit-ostree-148-1.el7 rpm-ostree-client-2017.6-6.atomic.el7 28.2. Extras Updated packages : ansible-2.3.2.0-1.el7 * atomic-1.18.1-4.git64843d3.el7 cockpit-148-1.el7 container-selinux-2.21-2.gitba103ac.el7 container-storage-setup-0.6.0-1.gite67c964.el7 docker-1.12.6-54.gitc4618fb.el7 docker-distribution-2.6.2-1.git48294d9.el7 docker-latest-1.13.1-23.git28ae36d.el7 etcd-3.2.5-1.el7 gomtree-0.4.0-1.1.el7 oci-systemd-hook-0.1.12-1.git1e84754.el7 rhel-system-roles-0.3-2.el7 * skopeo-0.1.23-1.git1bbd87f.el7 storaged-2.5.2-4.el7 * The asterisk (*) marks packages which are available for Red Hat Enterprise Linux only. 28.2.1. Container Images Updated : Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux 7.4 Container Image (rhel7.4, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic openscap Container Image (rhel7/openscap) Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) 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 Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic Kubernetes scheduler Container Image (rhel7/kubernetes-scheduler) 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 Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel)

Commands:
17.6. Distributed Execution and Locality In a Distributed Environment ownership, in regards to the DistributionManager and ConsistentHash , is theoretical; neither of these classes have any knowledge if data is actively in the cache. Instead, these classes are used to determine which node should store the specified key. To examine the locality of a given key use either of the following options: Option 1: Confirm that the key is both found in the cache and the DistributionManager indicates it is local, as seen in the following example: Option 2: Query the DataContainer directly: Note If the entry is passivated then the DataContainer will return False , regardless of the key's presence. Report a bug

Commands:
(cache.getAdvancedCache().withFlags(SKIP_REMOTE_LOOKUP).containsKey(key) && cache.getAdvancedCache().getDistributionManager().getLocality(key).isLocal())
cache.getAdvancedCache().getDataContainer().containsKey(key)
Chapter 6. Berkeley Internet Name Domain BIND performs name resolution services via the named daemon. BIND lets users locate computer resources and services by name instead of numerical addresses. In Red Hat Enterprise Linux, the bind package provides a DNS server. Run the rpm -q bind command to see if the bind package is installed. If it is not installed, run the following command as the root user to install it: 6.1. BIND and SELinux The default permissions on the /var/named/slaves/ , /var/named/dynamic/ and /var/named/data/ directories allow zone files to be updated via zone transfers and dynamic DNS updates. Files in /var/named/ are labeled with the named_zone_t type, which is used for master zone files. For a slave server, configure /etc/named.conf to place slave zones in /var/named/slaves/ . The following is an example of a domain entry in /etc/named.conf for a slave DNS server that stores the zone file for testdomain.com in /var/named/slaves/ : If a zone file is labeled named_zone_t , the named_write_master_zones Boolean must be enabled to allow zone transfers and dynamic DNS to update the zone file. Also, the mode of the parent directory has to be changed to allow the named user or group read, write and execute access. If zone files in /var/named/ are labeled with the named_cache_t type, a file system relabel or running restorecon -R /var/ will change their type to named_zone_t .

Commands:
~]# yum install bind
zone "testdomain.com" { type slave; masters { IP-address; }; file "/var/named/slaves/db.testdomain.com"; };
Chapter 8. Monitoring You can use the OpenShift Container Platform web console to monitor metrics related to the health status of your sandboxed workloads and nodes. OpenShift sandboxed containers has a pre-configured dashboard available in the OpenShift Container Platform web console. Administrators can also access and query raw metrics through Prometheus. 8.1. About metrics OpenShift sandboxed containers metrics enable administrators to monitor how their sandboxed containers are running. You can query for these metrics in Metrics UI In the OpenShift Container Platform web console. OpenShift sandboxed containers metrics are collected for the following categories: Kata agent metrics Kata agent metrics display information about the kata agent process running in the VM embedded in your sandboxed containers. These metrics include data from /proc/<pid>/[io, stat, status] . Kata guest operating system metrics Kata guest operating system metrics display data from the guest operating system running in your sandboxed containers. These metrics include data from /proc/[stats, diskstats, meminfo, vmstats] and /proc/net/dev . Hypervisor metrics Hypervisor metrics display data regarding the hypervisor running the VM embedded in your sandboxed containers. These metrics mainly include data from /proc/<pid>/[io, stat, status] . Kata monitor metrics Kata monitor is the process that gathers metric data and makes it available to Prometheus. The kata monitor metrics display detailed information about the resource usage of the kata-monitor process itself. These metrics also include counters from Prometheus data collection. Kata containerd shim v2 metrics Kata containerd shim v2 metrics display detailed information about the kata shim process. These metrics include data from /proc/<pid>/[io, stat, status] and detailed resource usage metrics. 8.2. Viewing metrics You can access the metrics for OpenShift sandboxed containers in the Metrics page In the OpenShift Container Platform web console. Prerequisites You have access to the cluster as a user with the cluster-admin role or with view permissions for all projects. Procedure In the OpenShift Container Platform web console, navigate to Observe Metrics . In the input field, enter the query for the metric you want to observe. All kata-related metrics begin with kata . Typing kata displays a list of all available kata metrics. The metrics from your query are visualized on the page. Additional resources Querying metrics . Gathering data about your cluster .

Commands: