mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 6. Downloading files from your bucket To download a file from your bucket to your workbench, use the download_file() method. Prerequisites You have cloned the odh-doc-examples repository to your workbench. You have opened the s3client_examples.ipynb file in your workbench. You have installed Boto3 and configured an S3 client. Procedure In the notebook, locate the following instructions to download files from a bucket: Modify the code sample: Replace <bucket_name> with the name of the bucket that the file is located in... Replace <object_name> with the name of the file that you want to download. Replace <file_name> with the name and path that you want the file to be downloaded to, as shown in the example. Run the code cell. Verification The file that you downloaded appears in the path that you specified on your workbench.

Commands:
#Download file from bucket #Replace the following values with your own: #<bucket_name>: The name of the bucket. #<object_name>: The name of the file to download. Must include full path to the file on the bucket. #<file_name>: The name of the file when downloaded. s3_client.download_file('<bucket_name>','<object_name>','<file_name>')
s3_client.download_file('aqs086-image-registry', 'series35-image36-086.csv', '\tmp\series35-image36-086.csv_old')
Chapter 7. References 7.1. Red Hat Configuring RHEL 8 for SAP HANA2 installation Configuring and managing high availability clusters Support Policies for RHEL High Availability Clusters Support Policies for RHEL High Availability Clusters - Fencing/STONITH Support Policies for RHEL High Availability Clusters - Management of SAP HANA in a Cluster Red Hat HA Solutions for SAP HANA, S/4HANA and NetWeaver based SAP Applications Configuring quorum devices The Systemd-Based SAP Startup Framework Why does the stop operation of a SAPHana resource agent fail when the systemd based SAP startup framework is enabled? 7.2. SAP SAP HANA Server Installation and Update Guide SAP HANA System Replication Implementing a HA/DR Provider SAP Note 2057595 - FAQ: SAP HANA High Availability SAP Note 2063657 - SAP HANA System Replication Takeover Decision Guideline SAP Note 2235581 - SAP HANA: Supported Operating Systems SAP Note 2369981 - Required configuration steps for authentication with HANA System Replication SAP Note 2972496 - SAP HANA Filesystem Types SAP Note 3007062 - FAQ: SAP HANA & Third Party Cluster Solutions SAP Note 3115048 - sapstartsrv with native Linux systemd support SAP Note 3139184 - Linux: systemd integration for sapstartsrv and SAP Host Agent SAP Note 3189534 - Linux: systemd integration for sapstartsrv and SAP HANA 7.3. Other Be Prepared for Using Pacemaker Cluster for SAP HANA - Part 1: Basics Be Prepared for Using Pacemaker Cluster for SAP HANA - Part 2: Failure of Both Nodes

Commands:
Chapter 26. The web console The following chapter contains the most notable changes to the web console between RHEL 8 and RHEL 9. 26.1. Changes to the RHEL web console Remote root login disabled on new installations of RHEL 9.2 and later Due to security reasons, on new installations of RHEL 9.2 and newer, it is not possible to connect to the web console from a remote machine as a root user. To enable the remote root login: As a root user, open the /etc/cockpit/disallowed-users file in a text editor. Remove the root user line from the file. Save your changes.

Commands:
17.8. Managing DNS Settings The DNS tab allows you to configure the system's hostname, domain, name servers, and search domain. Name servers are used to look up other hosts on the network. If the DNS server names are retrieved from DHCP or PPPoE (or retrieved from the ISP), do not add primary, secondary, or tertiary DNS servers. If the hostname is retrieved dynamically from DHCP or PPPoE (or retrieved from the ISP), do not change it. Figure 17.14. DNS Configuration Note The name servers section does not configure the system to be a name server. Instead, it configures which name servers to use when resolving IP addresses to hostnames and vice-versa. Warning If the hostname is changed and system-config-network is started on the local host, you may not be able to start another X11 application. As such, you may have to re-login to a new desktop session.

Commands:
Chapter 4. Basic configuration options of Shenandoah garbage collector Shenandoah garbage collector (GC) has the following basic configuration options: -Xlog:gc Print the individual GC timing. -Xlog:gc+ergo Print the heuristics decisions, which might shed light on outliers, if any. -Xlog:gc+stats Print the summary table on Shenandoah internal timings at the end of the run. It is best to run this with logging enabled. This summary table conveys important information about GC performance. Heuristics logs are useful to figure out GC outliers. -XX:+AlwaysPreTouch Commit heap pages into memory and helps to reduce latency hiccups. -Xms and -Xmx Making the heap non-resizeable with -Xms = -Xmx reduces difficulties with heap management. Along with AlwaysPreTouch , the -Xms = -Xmx commit all memory on startup, which avoids difficulties when memory is finally used. -Xms also defines the low boundary for memory uncommit, so with -Xms = -Xmx all memory stays committed. If you want to configure Shenandoah for a lower footprint, then setting lower -Xms is recommended. You need to decide how low to set it to balance the commit/uncommit overhead versus memory footprint. In many cases, you can set -Xms arbitrarily low. -XX:+UseLargePages Enables hugetlbfs Linux support. -XX:+UseTransparentHugePages Enables huge pages transparently. With transparent huge pages, it is recommended to set /sys/kernel/mm/transparent_hugepage/enabled and /sys/kernel/mm/transparent_hugepage/defrag to madvise . When running with AlwaysPreTouch , it will also pay the defrag tool costs upfront at startup. -XX:+UseNUMA While Shenandoah does not support NUMA explicitly yet, it is a good idea to enable NUMA interleaving on multi-socket hosts. Coupled with AlwaysPreTouch , it provides better performance than the default out-of-the-box configuration. -XX:-UseBiasedLocking There is a tradeoff between uncontended (biased) locking throughput, and the safepoints JVM does to enable and disable them. For latency-oriented workloads, turn biased locking off. -XX:+DisableExplicitGC Invoking System.gc() from user code forces Shenandoah to perform additional GC cycle. It usually does not harm, as -XX:+ExplicitGCInvokesConcurrent gets enabled by default, which means the concurrent GC cycle would be invoked, not the STW Full GC. Revised on 2024-05-10 09:08:44 UTC

Commands:
6.6. Additional Resources For more information about users and groups, and tools to manage them, refer to the following resources. 6.6.1. Installed Documentation Related man pages - There are a number of man pages for the various applications and configuration files involved with managing users and groups. Some of the more important man pages have been listed here: User and Group Administrative Applications man chage - A command to modify password aging policies and account expiration. man gpasswd - A command to administer the /etc/group file. man groupadd - A command to add groups. man grpck - A command to verify the /etc/group file. man groupdel - A command to remove groups. man groupmod - A command to modify group membership. man pwck - A command to verify the /etc/passwd and /etc/shadow files. man pwconv - A tool to convert standard passwords to shadow passwords. man pwunconv - A tool to convert shadow passwords to standard passwords. man useradd - A command to add users. man userdel - A command to remove users. man usermod - A command to modify users. Configuration Files man 5 group - The file containing group information for the system. man 5 passwd - The file containing user information for the system. man 5 shadow - The file containing passwords and account expiration information for the system.

Commands:
Chapter 16. Controlling power management transitions You can control power management transitions to improve latency. Prerequisites You have root permissions on the system. 16.1. Power saving states Modern processors actively transition to higher power saving states (C-states) from lower states. Unfortunately, transitioning from a high power saving state back to a running state can consume more time than is optimal for a real-time application. To prevent these transitions, an application can use the Power Management Quality of Service (PM QoS) interface. With the PM QoS interface, the system can emulate the behavior of the idle=poll and processor.max_cstate=1 parameters, but with a more fine-grained control of power saving states. idle=poll prevents the processor from entering the idle state. processor.max_cstate=1 prevents the processor from entering deeper C-states (energy-saving modes). When an application holds the /dev/cpu_dma_latency file open, the PM QoS interface prevents the processor from entering deep sleep states, which cause unexpected latencies when they are being exited. When the file is closed, the system returns to a power-saving state. 16.2. Configuring power management states You can control power management transitions by configuring power management states with one of the following ways: Write a value to the /dev/cpu_dma_latency file to change the maximum response time for processes in microseconds and hold the file descriptor open until low latency is required. Reference the /dev/cpu_dma_latency file in an application or a script. Prerequisites You have administrator privileges. Procedure Specify latency tolerance by writing a 32-bit number that represents a maximum response time in microseconds in /dev/cpu_dma_latency and keep the file descriptor open through the low-latency operation. A value of 0 disables C-state completely. For example: Note The Power Management Quality of Service interface ( pm_qos ) interface is only active while it has an open file descriptor. Therefore, any script or program you use to access /dev/cpu_dma_latency must hold the file open until power-state transitions are allowed.

Commands:
import os import signal import sys if not os.path.exists('/dev/cpu_dma_latency'): print("no PM QOS interface on this system!") sys.exit(1) try: fd = os.open('/dev/cpu_dma_latency', os.O_WRONLY) os.write(fd, b'\0\0\0\0') print("Press ^C to close /dev/cpu_dma_latency and exit") signal.pause() except KeyboardInterrupt: print("closing /dev/cpu_dma_latency") os.close(fd) sys.exit(0)
Deploying and managing OpenShift Data Foundation using Red Hat OpenStack Platform Red Hat OpenShift Data Foundation 4.18 Instructions on deploying and managing OpenShift Data Foundation on Red Hat OpenStack Platform Red Hat Storage Documentation Team Abstract Read this document for instructions about how to install and manage Red Hat OpenShift Data Foundation using Red Hat OpenShift Container Platform on Red Hat OpenStack Platform (RHOSP). Important Deploying and managing OpenShift Data Foundation on Red Hat OpenStack Platform is a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

Commands:
Chapter 13. Verify your deployment After deployment is complete, verify that your deployment has completed successfully. Browse to the Administration Portal, for example, http://engine.example.com/ovirt-engine . Administration Console Login Log in using the administrative credentials added during hosted engine deployment. When login is successful, the Dashboard appears. Administration Console Dashboard Verify that your cluster is available. Administration Console Dashboard - Clusters Verify that at least one host is available. If you provided additional host details during Hosted Engine deployment, 3 hosts are visible here, as shown. Administration Console Dashboard - Hosts Click Compute Hosts . Verify that all hosts are listed with a Status of Up . Administration Console - Hosts Verify that all storage domains are available. Click Storage Domains . Verify that the Active icon is shown in the first column. Administration Console - Storage Domains

Commands:
14.2. Samba Daemons and Related Services The following is a brief introduction to the individual Samba daemons and services, as well as details on how to start and stop them. 14.2.1. Daemon Overview Samba is comprised of three daemons ( smbd , nmbd , and winbindd ). Two services ( smb and windbind ) control how the daemons are started, stopped, and other service-related features. Each daemon is listed in detail, as well as which specific service has control over it. 14.2.1.1. The smbd daemon The smbd server daemon provides file sharing and printing services to Windows clients. In addition, it is responsible for user authentication, resource locking, and data sharing through the SMB protocol. The default ports on which the server listens for SMB traffic are TCP ports 139 and 445. The smbd daemon is controlled by the smb service. 14.2.1.2. The nmbd daemon The nmbd server daemon understands and replies to NetBIOS name service requests such as those produced by SMB/CIFS in Windows-based systems. These systems include Windows 95/98/ME, Windows NT, Windows 2000, Windows XP, and LanManager clients. It also participates in the browsing protocols that make up the Windows Network Neighborhood view. The default port that the server listens to for NMB traffic is UDP port 137. The nmbd daemon is controlled by the smb service. 14.2.1.3. The winbindd daemon The winbind service resolves user and group information on a Windows NT server and makes it understandable by UNIX platforms. This is achieved by using Microsoft RPC calls, Pluggable Authentication Modules (PAM), and the Name Service Switch (NSS). This allows Windows NT domain users to appear and operate as UNIX users on a UNIX machine. Though bundled with the Samba distribution, the winbind service is controlled separately from the smb service. The winbindd daemon is controlled by the winbind service and does not require the smb service to be started in order to operate. Because winbind is a client-side service used to connect to Windows NT based servers, further discussion of winbind is beyond the scope of this manual.

Commands:
Getting ready to install MicroShift Red Hat build of MicroShift 4.18 Plan for your MicroShift installation and learn about important configurations Red Hat OpenShift Documentation Team

Commands:
sudo mkdir -p /etc/systemd/journald.conf.d
cat <<EOF | sudo tee /etc/systemd/journald.conf.d/microshift.conf &>/dev/null [Journal] Storage=persistent SystemMaxUse=1G RuntimeMaxUse=1G EOF
sudo grub2-editenv - list | grep ^boot_success
boot_success=1
sudo journalctl -o cat -u greenboot-healthcheck.service
Running Required Health Check Scripts STARTED GRUB boot variables: boot_success=0 boot_indeterminate=0 boot_counter=2 Waiting 300s for MicroShift service to be active and not failed FAILURE
sudo journalctl -o cat -u redboot-task-runner.service
Running Red Scripts STARTED GRUB boot variables: boot_success=0 boot_indeterminate=0 boot_counter=0 The ostree status: * rhel c0baa75d9b585f3dd989a9cf05f647eb7ca27ee0dbd4b94fe8c93ed3a4b9e4a5.0 Version: 9.1 origin: <unknown origin type> rhel 6869c1347b0e0ba1bbf0be750cdf32da5138a1fcbc5a4c6325ab9eb647b64663.0 (rollback) Version: 9.1 origin refspec: edge:rhel/9/x86_64/edge System rollback imminent - preparing MicroShift for a clean start Stopping MicroShift services Removing MicroShift pods Killing conmon, pause and OVN processes Removing OVN configuration Finished greenboot Failure Scripts Runner. Cleanup succeeded Script '40_microshift_pre_rollback.sh' SUCCESS FINISHED redboot-task-runner.service: Deactivated successfully.
sudo grub2-editenv - list | grep ^boot_success
boot_success=1
8.11. NFS References Administering an NFS server can be a challenge. Many options, including quite a few not mentioned in this chapter, are available for exporting or mounting NFS shares. For more information, see the following sources: Installed Documentation man mount - Contains a comprehensive look at mount options for both NFS server and client configurations. man fstab - Provides detail for the format of the /etc/fstab file used to mount file systems at boot-time. man nfs - Provides details on NFS-specific file system export and mount options. man exports - Shows common options used in the /etc/exports file when exporting NFS file systems. Useful Websites http://linux-nfs.org - The current site for developers where project status updates can be viewed. http://nfs.sourceforge.net/ - The old home for developers which still contains a lot of useful information. http://www.citi.umich.edu/projects/nfsv4/linux/ - An NFSv4 for Linux 2.6 kernel resource. http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.111.4086 - An excellent whitepaper on the features and enhancements of the NFS Version 4 protocol. Related Books Managing NFS and NIS by Hal Stern, Mike Eisler, and Ricardo Labiaga; O'Reilly & Associates - Makes an excellent reference guide for the many different NFS export and mount options available. NFS Illustrated by Brent Callaghan; Addison-Wesley Publishing Company - Provides comparisons of NFS to other network file systems and shows, in detail, how NFS communication occurs.

Commands:
A.14. OProfile OProfile is a low overhead, system-wide performance monitoring tool provided by the oprofile package. It uses the performance monitoring hardware on the processor to retrieve information about the kernel and executables on the system, such as when memory is referenced, the number of second-level cache requests, and the number of hardware interrupts received. OProfile is also able to profile applications that run in a Java Virtual Machine (JVM). OProfile provides the following tools. Note that the legacy opcontrol tool and the new operf tool are mutually exclusive. ophelp Displays available events for the system's processor along with a brief description of each. opimport Converts sample database files from a foreign binary format to the native format for the system. Only use this option when analyzing a sample database from a different architecture. opannotate Creates annotated source for an executable if the application was compiled with debugging symbols. opcontrol Configures which data is collected in a profiling run. operf Intended to replace opcontrol . The operf tool uses the Linux Performance Events subsystem, allowing you to target your profiling more precisely, as a single process or system-wide, and allowing OProfile to co-exist better with other tools using the performance monitoring hardware on your system. Unlike opcontrol , no initial setup is required, and it can be used without the root privileges unless the --system-wide option is in use. opreport Retrieves profile data. oprofiled Runs as a daemon to periodically write sample data to disk. Legacy mode ( opcontrol , oprofiled , and post-processing tools) remains available, but is no longer the recommended profiling method. For further information about any of these commands, see the OProfile man page:

Commands:
man oprofile
9.2. Import DDL You can create source relational models by importing DDL using the steps below. In Model Explorer, right-click and then click Import... or click the File > Import... action. Select the import option Teiid Designer > DDL File (General) >> Source or View Model and click > . Note You can also choose DDL File (Teiid) which import metadata from Teiid DDL file. Select existing DDL from either Choose from file system... or Choose from workspace... . Set the Model folder location, enter or select valid model name, set Model type (Source Model or View Model), set desired options and click > (or Finish if enabled) Figure 9.2. DDL Import Options If you click > , a difference report is presented for viewing or deselecting individual relational entities. Click Finish to complete. Figure 9.3. Import DDL Dialog

Commands:
4.4. GFS Quota Management File-system quotas are used to limit the amount of file-system space a user or group can use. A user or group does not have a quota limit until one is set. GFS keeps track of the space used by each user and group even when there are no limits in place. GFS updates quota information in a transactional way so system crashes do not require quota usages to be reconstructed. To prevent a performance slowdown, a GFS node synchronizes updates to the quota file only periodically. The "fuzzy" quota accounting can allow users or groups to slightly exceed the set limit. To minimize this, GFS dynamically reduces the synchronization period as a "hard" quota limit is approached. GFS uses its gfs_quota command to manage quotas. Other Linux quota facilities cannot be used with GFS. 4.4.1. Setting Quotas Two quota settings are available for each user ID (UID) or group ID (GID): a hard limit and a warn limit . A hard limit is the amount of space that can be used. The file system will not let the user or group use more than that amount of disk space. A hard limit value of zero means that no limit is enforced. A warn limit is usually a value less than the hard limit. The file system will notify the user or group when the warn limit is reached to warn them of the amount of space they are using. A warn limit value of zero means that no limit is enforced. Limits are set using the gfs_quota command. The command only needs to be run on a single node where GFS is mounted. Usage Setting Quotas, Hard Limit Setting Quotas, Warn Limit User A user ID to limit or warn. It can be either a user name from the password file or the UID number. Group A group ID to limit or warn. It can be either a group name from the group file or the GID number. Size Specifies the new value to limit or warn. By default, the value is in units of megabytes. The additional -k , -s and -b flags change the units to kilobytes, sectors, and file-system blocks, respectively. MountPoint Specifies the GFS file system to which the actions apply. Examples This example sets the hard limit for user Bert to 1024 megabytes (1 gigabyte) on file system /gfs . This example sets the warn limit for group ID 21 to 50 kilobytes on file system /gfs .

Commands:
gfs_quota limit -u User -l Size -f MountPoint
gfs_quota limit -g Group -l Size -f MountPoint
gfs_quota warn -u User -l Size -f MountPoint
gfs_quota warn -g Group -l Size -f MountPoint
gfs_quota limit -u Bert -l 1024 -f /gfs
gfs_quota warn -g 21 -l 50 -k -f /gfs
Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message . AMQ Clients is a suite of AMQP 1.0 and JMS clients, adapters, and libraries. It includes JMS 2.0 support and new, event-driven APIs to enable integration into existing applications. AMQ Clients is part of Red Hat AMQ. For more information, see Introducing Red Hat AMQ 7 .

Commands: