mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 14. Idling applications Cluster administrators can idle applications to reduce resource consumption. This is useful when the cluster is deployed on a public cloud where cost is related to resource consumption. If any scalable resources are not in use, OpenShift Container Platform discovers and idles them by scaling their replicas to 0 . The time network traffic is directed to the resources, the resources are unidled by scaling up the replicas, and normal operation continues. Applications are made of services, as well as other scalable resources, such as deployment configs. The action of idling an application involves idling all associated resources. 14.1. Idling applications Idling an application involves finding the scalable resources (deployment configurations, replication controllers, and others) associated with a service. Idling an application finds the service and marks it as idled, scaling down the resources to zero replicas. You can use the oc idle command to idle a single service, or use the --resource-names-file option to idle multiple services. 14.1.1. Idling a single service Procedure To idle a single service, run: USD oc idle <service> 14.1.2. Idling multiple services Idling multiple services is helpful if an application spans across a set of services within a project, or when idling multiple services in conjunction with a script to idle multiple applications in bulk within the same project. Procedure Create a file containing a list of the services, each on their own line. Idle the services using the --resource-names-file option: USD oc idle --resource-names-file <filename> Note The idle command is limited to a single project. For idling applications across a cluster, run the idle command for each project individually. 14.2. Unidling applications Application services become active again when they receive network traffic and are scaled back up their state. This includes both traffic to the services and traffic passing through routes. Applications can also be manually unidled by scaling up the resources. Procedure To scale up a DeploymentConfig, run: USD oc scale --replicas=1 dc <dc_name> Note Automatic unidling by a router is currently only supported by the default HAProxy router.

Commands:
oc idle <service>
oc idle --resource-names-file <filename>
oc scale --replicas=1 dc <dc_name>
Chapter 7. Backing Up and Restoring Data Grid Clusters Create archives of Data Grid resources that include cached entries, cache configurations, Protobuf schemas, and server scripts. You can then use the backup archives to restore Data Grid Server clusters after a restart or migration. Prerequisites Start the Data Grid CLI. Connect to a running Data Grid cluster. 7.1. Backing Up Data Grid Clusters Create backup archives in .zip format that you can download or store on Data Grid Server. Prerequisites Backup archives should reflect the most recent cluster state. For this reason you should ensure the cluster is no longer accepting write requests before you create backup archives. Procedure Create a CLI connection to Data Grid. Run the backup create command with the appropriate options, for example: Back up all resources with an automatically generated name. Back up all resources in a backup archive named example-backup . Back up all resources to the /some/server/dir path on the server. Back up only caches and cache templates. Back up named Protobuf schemas only. List available backup archives on the server. Download the example-backup archive from the server. If the backup operation is still in progress, the command waits for it to complete. Optionally delete the example-backup archive from the server. 7.2. Restoring Data Grid Clusters from Backup Archives Apply the content of backup archives to Data Grid clusters to restore them to the backed up state. Prerequisites Create a backup archive that is either local to the Data Grid CLI or stored on Data Grid Server. Ensure that the target container matches the container name in the backup archive. You cannot restore backups if the container names do not match. Procedure Create a CLI connection to Data Grid. Run the backup restore command with the appropriate options. Restore all content from a backup archive accessible on the server. Restore all content from a local backup archive. Restore only cache content from a backup archive on the server.

Commands:
backup create
backup create -n example-backup
backup create -d /some/server/dir
backup create --caches=* --templates=*
backup create --proto-schemas=schema1,schema2
backup ls
backup get example-backup
backup delete example-backup
backup restore /some/path/on/the/server
backup restore -u /some/local/path
backup restore /some/path/on/the/server --caches=*
20.5. Language-Specific Changes Arabic New Arabic fonts from Paktype are available in Red Hat Enterprise Linux 7: paktype-ajrak, paktype-basic-naskh-farsi, paktype-basic-naskh-sindhi, paktype-basic-naskh-urdu, and paktype-basic-naskh-sa. Chinese The WQY Zenhei font is now the default font for Simplified Chinese. The default engine for Simplified Chinese has been changed to ibus-libpinyin from ibus-pinyin that Red Hat Enterprise Linux 6 uses. Indic The new Lohit Devanagari font replaces the separate Lohit fonts for Hindi, Kashmiri, Konkani, Maithili, Marathi, and Nepali. Any distinct glyphs for these languages needed in the future can be handled in Lohit Devanagari with the Open Type Font locl tags. New font packages gubbi-fonts and navilu-fonts have been added for Kannada language. Japanese IPA fonts are no longer installed by default ibus-kkc, the Kana Kanji Conversion, is the new default Japanese input method engine using the new libkkc back end. It replaces ibus-anthy, anthy, and kasumi. Korean The Nanum font is used by default now. New Locales Red Hat Enterprise Linux 7 supports new locales, Konkani (kok_IN) and Pushto (ps_AF).

Commands:
9.2.2. Finding Packages with Filters Once the software sources have been updated, it is often beneficial to apply some filters so that PackageKit retrieves the results of our Find queries faster. This is especially helpful when performing many package searches. Four of the filters in the Filters drop-down menu are used to split results by matching or not matching a single criterion. By default when PackageKit starts, these filters are all unapplied ( No filter ), but once you do filter by one of them, that filter remains set until you either change it or close PackageKit. Because you are usually searching for available packages that are not installed on the system, click Filters Installed and select the Only available radio button. Figure 9.5. Filtering out already-installed packages Also, unless you require development files such as C header files, click Filters Development and select the Only end user files radio button. This filters out all of the <package_name> -devel packages we are not interested in. Figure 9.6. Filtering out development packages from the list of Find results The two remaining filters with submenus are: Graphical Narrows the search to either applications which provide a GUI interface ( Only graphical ) or those that do not. This filter is useful when browsing for GUI applications that perform a specific function. Free Search for packages which are considered to be free software. See the Fedora Licensing List for details on approved licenses. The remaining filters can be enabled by selecting the check boxes to them: Hide subpackages Checking the Hide subpackages check box filters out generally-uninteresting packages that are typically only dependencies of other packages that we want. For example, checking Hide subpackages and searching for <package> would cause the following related packages to be filtered out of the Find results (if it exists): <package> -devel <package> -libs <package> -libs-devel <package> -debuginfo Only newest packages Checking Only newest packages filters out all older versions of the same package from the list of results, which is generally what we want. Note that this filter is often combined with the Only available filter to search for the latest available versions of new (not installed) packages. Only native packages Checking the Only native packages box on a multilib system causes PackageKit to omit listing results for packages compiled for the architecture that runs in compatibility mode . For example, enabling this filter on a 64-bit system with an AMD64 CPU would cause all packages built for the 32-bit x86 CPU architecture not to be shown in the list of results, even though those packages are able to run on an AMD64 machine. Packages which are architecture-agnostic (i.e. noarch packages such as crontabs-1.10-32.1.el6.noarch.rpm ) are never filtered out by checking Only native packages . This filter has no affect on non-multilib systems, such as x86 machines.

Commands:
20.9. Removing and Deleting a Virtual Machine 20.9.1. Undefining a Virtual Machine The virsh undefine domain [--managed-save] [ storage ] [--remove-all-storage] [--wipe-storage] [--snapshots-metadata] [--nvram] command undefines a domain. If domain is inactive, the configuration is removed completely. If the domain is active (running), it is converted to a transient domain. When the guest virtual machine becomes inactive, the configuration is removed completely. This command can take the following arguments: --managed-save - this argument guarantees that any managed save image is also cleaned up. Without using this argument, attempts to undefine a guest virtual machine with a managed save will fail. --snapshots-metadata - this argument guarantees that any snapshots (as shown with snapshot-list ) are also cleaned up when undefining an inactive guest virtual machine. Note that any attempts to undefine an inactive guest virtual machine with snapshot metadata will fail. If this argument is used and the guest virtual machine is active, it is ignored. --storage - using this argument requires a comma separated list of volume target names or source paths of storage volumes to be removed along with the undefined domain. This action will undefine the storage volume before it is removed. Note that this can only be done with inactive guest virtual machines and that this will only work with storage volumes that are managed by libvirt . --remove-all-storage - in addition to undefining the guest virtual machine, all associated storage volumes are deleted. If you want to delete the virtual machine, choose this option only if there are no other virtual machines using the same associated storage. An alternative way is with the virsh vol-delete . See Section 20.31, "Deleting Storage Volumes" for more information. --wipe-storage - in addition to deleting the storage volume, the contents are wiped. Example 20.17. How to delete a guest virtual machine and delete its storage volumes The following example undefines the guest1 virtual machine and remove all associated storage volumes. An undefined guest becomes transient and thus is deleted after it shuts down: # virsh undefine guest1 --remove-all-storage 20.9.2. Forcing a Guest Virtual Machine to Stop Note This command should only be used when you cannot shut down the virtual guest machine by any other method. The virsh destroy command initiates an immediate ungraceful shutdown and stops the specified guest virtual machine. Using virsh destroy can corrupt guest virtual machine file systems. Use the virsh destroy command only when the guest virtual machine is unresponsive. The virsh destroy command with the --graceful option attempts to flush the cache for the disk image file before powering off the virtual machine. Example 20.18. How to immediately shutdown a guest virtual machine with a hard shutdown The following example immediately shuts down the guest1 virtual machine, probably because it is unresponsive: # virsh destroy guest1 You may want to follow this with the virsh undefine command. See Example 20.17, "How to delete a guest virtual machine and delete its storage volumes"

Commands:
Chapter 14. Session Management 14.1. What Is GDM? The GNOME Display Manager ( GDM ) is a graphical login program running in the background that runs and manages the X servers for both local and remote logins. GDM is a replacement for XDM , the X Display Manager. However, GDM is not derived from XDM and does not contain any original XDM code. In addition, there is no support for a graphical configuration tool in GDM , so editing the /etc/gdm/custom.conf configuration file is necessary to change the GDM settings. 14.1.1. Restarting GDM When you make changes to the system configuration such as setting up the login screen banner message, login screen logo, or login screen background, you need to restart GDM for your changes to take effect. Warning Keep in mind that restarting the service forcibly interrupts any currently running GNOME session of any desktop user who is logged in. This can result in users losing unsaved data. To restart the GDM service, run the following command: For more information about managing services on Red Hat Enterprise Linux 7, see the System Administrator's Guide . 14.1.2. Displaying results of GDM configuration To display results of the GDM configuration, run the following command:

Commands:
systemctl restart gdm.service
DCONF_PROFILE=gdm gsettings list-recursively org.gnome.login-screen
2.17. RHEA-2011:0669 - new package: matahari New matahari packages are now available for Red Hat Enterprise Linux 6. A new mingw32-matahari package, which accompanies matahari, is also now available for Red Hat Enterprise Linux 6. The matahari packages provide a set of APIs for operating system management that are exposed for remote access over the Qpid Management Framework (QMF). The mingw32-matahari package provides the Windows variant of matahari, compiled with the mingw32 compiler toolchain. This enhancement update adds new matahari and mingw32-matahari packages to Red Hat Enterprise Linux 6. (BZ# 658828 , BZ# 658840 ) All users requiring matahari and mingw32-matahari should install these newly-released packages, which add these enhancements.

Commands:
Chapter 5. Upgrading sites This release of Red Hat Service Interconnect is compatible with versions, however Red Hat recommends upgrading all sites to version 1.8. Note Update all sites to ensure the same version of Service Interconnect is running across your service network. You can expect some minimal downtime during the update process. To upgrade a site: This command is not suitable for sites created using the Operator. See the Installation for instructions about upgrading Operator based sites. Note If you enabled the console using a release before 1.4, which was the default, the upgraded site will also have the console enabled. The default for Service Interconnect 1.4 and later is that the console is not enabled. To upgrade a gateway, delete the gateway and recreate it. Port negotiation limitation If your protocol negotiates the communication port, for example active FTP, you cannot use that protocol to communicate across a service network.

Commands:
skupper update
6.2. Enabling Infinispan Query DSL-based Queries In library mode, running Infinispan Query DSL-based queries is almost identical to running Lucene-based API queries. Prerequisites are: All libraries required for Infinispan Query (see Section 2.1.1, "Infinispan Query Dependencies in Library Mode" for details) on the classpath. Indexing enabled and configured for caches (optional). See Section 2.4, "Configure Indexing" for details. Annotated POJO cache values (optional). If indexing is not enabled, POJO annotations are also not required and are ignored if set. If indexing is not enabled, all fields that follow JavaBeans conventions are searchable instead of only the fields with Hibernate Search annotations. Report a bug

Commands:
Chapter 2. Enabling file system access for containers on Red Hat Enterprise Linux based nodes Deploying OpenShift Data Foundation on an OpenShift Container Platform with worker nodes on a Red Hat Enterprise Linux base in a user provisioned infrastructure (UPI) does not automatically provide container access to the underlying Ceph file system. Note Skip this step for hosts based on Red Hat Enterprise Linux CoreOS (RHCOS). Procedure Log in to the Red Hat Enterprise Linux based node and open a terminal. For each node in your cluster: Verify that the node has access to the rhel-7-server-extras-rpms repository. If you do not see both rhel-7-server-rpms and rhel-7-server-extras-rpms in the output, or if there is no output, run the following commands to enable each repository: Install the required packages. Persistently enable container use of the Ceph file system in SELinux.

Commands:
subscription-manager repos --list-enabled | grep rhel-7-server
subscription-manager repos --enable=rhel-7-server-rpms
subscription-manager repos --enable=rhel-7-server-extras-rpms
yum install -y policycoreutils container-selinux
setsebool -P container_use_cephfs on
7.75. grub 7.75.1. RHBA-2013:0428 - grub bug fix and enhancement update Updated grub packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The GRUB utility is a powerful boot loader, which can load a wide variety of operating systems. Bug Fixes BZ#783169 When the BIOS was set to Unified Extensible Firmware Interface (UEFI) mode, all legacy option ROMs in the setup were disabled, and the grub.efi utility was loaded, an attempt to access the network with the NET0 protocol was not successful and the "nd" root command did not work. This bug has been fixed and GRUB works correctly in this situation. BZ#814014 Previously, the GRUB utility did not scan for KVM virtio disks when creating a device map. Consequently, these disks were not added to this map. This bug has been fixed and GRUB now scans for vd* devices located in the /dev/ directory, so virtio disks are added to a device map as expected. BZ#825054 The GRUB utility did not pass high order address bits for the Extensible Firmware Interface (EFI) memory map and system table high order bits. As a consequence, the EFI system map and memory map did not work correctly on computers with RAM bigger then 4 GB. This bug has been fixed by passing high order address bits, so that grub works properly in the described scenario. BZ#870420 When symbolic links in the /dev/mapper/ directory were resolved to the original file, this file did not match proper file entry in the device.map file. Consequently, the grub-install package failed and an error message was returned. With this update, symbolic links are now prevented to resolve in the /dev/mapper/ directory. As a result, grub-install proceeds as expected. BZ#876519 Due to an error in the underlying source code, an incorrect attempt to dereference a NULL pointer could previously cause GRUB to terminate unexpectedly. This update corrects the underlying source code to prevent this error so that GRUB no longer crashes. Enhancements BZ#642396 This enhancement includes support for IPV6 UEFI 2.3.1 netboot, which was previously missing. BZ#737732 With this update, the users can use EFI boot partition as a root partition, which can be specified in the grub.conf file. As a consequence, the users do not have to specify particular drive, but can use the one specified in the EFI boot manager. All users of GRUB are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 1. Introduction to OpenShift Data Foundation Red Hat OpenShift Data Foundation is a highly integrated collection of cloud storage and data services for Red Hat OpenShift Container Platform. It is available as part of the Red Hat OpenShift Container Platform Service Catalog, packaged as an operator to facilitate simple deployment and management. Red Hat OpenShift Data Foundation services are primarily made available to applications by way of storage classes that represent the following components: Block storage devices, catering primarily to database workloads. Prime examples include Red Hat OpenShift Container Platform logging and monitoring, and PostgreSQL. Important Block storage should be used for any worklaod only when it does not require sharing the data across multiple containers. Shared and distributed file system, catering primarily to software development, messaging, and data aggregation workloads. Examples include Jenkins build sources and artifacts, Wordpress uploaded content, Red Hat OpenShift Container Platform registry, and messaging using JBoss AMQ. Multicloud object storage, featuring a lightweight S3 API endpoint that can abstract the storage and retrieval of data from multiple cloud object stores. On premises object storage, featuring a robust S3 API endpoint that scales to tens of petabytes and billions of objects, primarily targeting data intensive applications. Examples include the storage and access of row, columnar, and semi-structured data with applications like Spark, Presto, Red Hat AMQ Streams (Kafka), and even machine learning frameworks like TensorFlow and Pytorch. Note Running PostgresSQL workload on CephFS persistent volume is not supported and it is recommended to use RADOS Block Device (RBD) volume. For more information, see the knowledgebase solution ODF Database Workloads Must Not Use CephFS PVs/PVCs . Red Hat OpenShift Data Foundation version 4.x integrates a collection of software projects, including: Ceph, providing block storage, a shared and distributed file system, and on-premises object storage Ceph CSI, to manage provisioning and lifecycle of persistent volumes and claims NooBaa, providing a Multicloud Object Gateway OpenShift Data Foundation, Rook-Ceph, and NooBaa operators to initialize and manage OpenShift Data Foundation services.

Commands:
15.3. Live Migration and Red Hat Enterprise Linux Version Compatibility Live Migration is supported as shown in Table 15.1, "Live Migration Compatibility" : Table 15.1. Live Migration Compatibility Migration Method Release Type Example Live Migration Support Notes Forward Major release 6.5+ 7.x Fully supported Any issues should be reported Backward Major release 7.x 6.y Not supported Forward Minor release 7.x 7.y (7.0 7.1) Fully supported Any issues should be reported Backward Minor release 7.y 7.x (7.1 7.0) Fully supported Any issues should be reported Troubleshooting problems with migration Issues with the migration protocol - If backward migration ends with "unknown section error", repeating the migration process can repair the issue as it may be a transient error. If not, report the problem. Issues with audio devices - When migrating from Red Hat Enterprise Linux 6.x to Red Hat Enterprise Linux 7.y, note that the es1370 audio card is no longer supported. Use the ac97 audio card instead. Issues with network cards - When migrating from Red Hat Enterprise Linux 6.x to Red Hat Enterprise Linux 7.y, note that the pcnet and ne2k_pci network cards are no longer supported. Use the virtio-net network device instead. Configuring Network Storage Configure shared storage and install a guest virtual machine on the shared storage. Alternatively, use the NFS example in Section 15.4, "Shared Storage Example: NFS for a Simple Migration"

Commands: