mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 17. Integrating with cloud management platforms You can integrate Red Hat Advanced Cluster Security for Kubernetes (RHACS) with different cloud management platforms to discover potential clusters to secure. The cluster discovery aims to gain a detailed overview of the cluster assets already or not yet secured by RHACS. The clusters discovered from a cloud management platform are accessible from the Platform Configuration Clusters Discovered clusters page. RHACS matches the discovered clusters against already secured clusters. Based on the result of the matching, a discovered cluster has one of the following statuses: Secured : The cluster is secured by RHACS. Unsecured : The cluster is not secured by RHACS. Undetermined : The metadata collected from secured clusters is not enough for a unique match. The cluster is either secured or unsecured. For successful cluster matching, ensure that the following conditions are met: Sensors running on secured clusters have been updated to the latest version. Access to instance tags via the metadata service has been granted for secured clusters running on AWS. Sensors require access to the AWS EC2 instance tags to determine the cluster status. You can integrate RHACS with the following cloud management platforms: Paladin Cloud OpenShift Cluster Manager 17.1. Configuring Paladin Cloud integration To discover cluster assets from Paladin Cloud, create a new integration in Red Hat Advanced Cluster Security for Kubernetes. Prerequisites A Paladin Cloud account. A Paladin Cloud API token. Procedure In the RHACS portal, go to Platform Configuration Integrations . Scroll down to the Cloud source integrations section and select Paladin Cloud . Click New integration . Enter a name for Integration name . Enter the Paladin Cloud API endpoint for Paladin Cloud endpoint . The default is https://api.paladincloud.io . Enter the Paladin Cloud API token for Paladin Cloud token . Select Test to confirm that authentication is working. Select Create to generate the configuration. Once configured, Red Hat Advanced Cluster Security for Kubernetes discovers cluster assets from your connected Paladin Cloud account. 17.2. Configuring Red Hat OpenShift Cluster Manager integration To discover cluster assets from Red Hat OpenShift Cluster Manager, create a new integration in Red Hat Advanced Cluster Security for Kubernetes. Prerequisites A Red Hat account. An Red Hat OpenShift Cluster Manager API token . Procedure In the RHACS portal, go to Platform Configuration Integrations . Scroll down to the Cloud source integrations section and select Red Hat OpenShift Cluster Manager . Click New integration . Enter a name for Integration name . Enter the Red Hat OpenShift Cluster Manager API endpoint for Endpoint . The default is https://api.openshift.com . Enter the Red Hat OpenShift Cluster Manager API token for API token . Select Test to confirm that authentication is working. Select Create to generate the configuration. Once configured, Red Hat Advanced Cluster Security for Kubernetes discovers cluster assets from your connected Red Hat account.

Commands:
Chapter 25. Why is a RHEL server appearing in an unexpected place in the subscriptions service usage? For some Red Hat products, Red Hat Enterprise Linux is included with and is installed to support that product. This inclusion is sometimes also referred to as being "bundled with" another product. For example, RHEL is included with Red Hat Satellite and is tracked separately in a Satellite page view on the RHEL page in the subscriptions service, but does not appear with the main RHEL usage. In addition, RHEL is included with all Red Hat OpenShift subscriptions, but that RHEL does not appear in the usage results on the RHEL page. Bundled RHEL is not tracked or counted against the total RHEL usage or capacity that is intended for production workloads or similar purposes. In some cases, these bundled RHEL packages might be inadvertently installed in isolation, without the full set of packages included in the bundled subscription. However, these bundled RHEL packages are still associated with the complete set of certificates contained in the bundled subscription. Because the subscriptions service is aware of the associated certificates and uses them to help identify the subscription, RHEL packages that are installed in isolation from their complete bundle could report usage in unexpected places and result in inaccurate usage, capacity, and subscription threshold reporting. For example, installing a RHEL package from a bundled Red Hat OpenShift Container Platform subscription without the rest of the packages from that bundled subscription could result in a RHEL server appearing as a cluster in the usage results for the Red Hat OpenShift page in the subscriptions service, even if there are no Red Hat OpenShift Container Platform nodes or clusters on that server. For best results, Red Hat subscriptions and their associated packages should be installed for the purposes for which they were intended. Installing isolated packages from bundled subscriptions is not a best practice, and will lead to poor quality usage results in the subscriptions service.

Commands:
Chapter 16. Searching 16.1. Searching Designer provides multiple search actions located via Teiid Designer submenu in Eclipses Search menu. The individual actions in the Teiid Designer submenu are described below: Transformations... - Launches the Transformation Search dialog. User can search models in the workspace for matching SQL text. Search results appear in the dialog and user can select and view SQL as well as open desired transformations for editing. Metadata... - Launches the Search dialog. User can search for models in the workspace by specifying an Object Type, and/or a Data Type, and/or a property value. Search results appear in the Search Results view, and double clicking a result will open that model in the appropriate editor. Find Model Object - Launches the Find Model Object dialog, which can be used to find an object in the workspace by specifying all or part of its name. Selecting the object will open it in the appropriate editor.

Commands:
Chapter 18. configuration This chapter describes the commands under the configuration command. 18.1. configuration show Display configuration details Usage: Table 18.1. Command arguments Value Summary -h, --help Show this help message and exit --mask Attempt to mask passwords (default) --unmask Show password in clear text Table 18.2. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 18.3. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 18.4. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 18.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack configuration show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] [--mask | --unmask]
A.11. VDSM Hook Execution before_vm_start scripts can edit the domain XML in order to change VDSM's definition of a virtual machine before it reaches libvirt. Caution must be exercised in doing so. Hook scripts have the potential to disrupt the operation of VDSM, and buggy scripts can result in outages to the Red Hat Virtualization environment. In particular, ensure you never change the UUID of the domain, and do not attempt to remove a device from the domain without sufficient background knowledge. Both before_vdsm_start and after_vdsm_stop hook scripts are run as the root user. Other hook scripts that require root access to the system must be written to use the sudo command for privilege escalation. To support this the /etc/sudoers must be updated to allow the vdsm user to use sudo without reentering a password. This is required as hook scripts are executed non-interactively. Example A.4. Configuring sudo for VDSM Hooks In this example the sudo command will be configured to allow the vdsm user to run the /bin/chown command as root . Log into the virtualization host as root . Open the /etc/sudoers file in a text editor. Add this line to the file: This specifies that the vdsm user has the ability to run the /bin/chown command as the root user. The NOPASSWD parameter indicates that the user will not be prompted to enter their password when calling sudo . Once this configuration change has been made VDSM hooks are able to use the sudo command to run /bin/chown as root . This Python code uses sudo to execute /bin/chown as root on the file /my_file . The standard error stream of hook scripts is collected in VDSM's log. This information is used to debug hook scripts.

Commands:
vdsm ALL=(ALL) NOPASSWD: /bin/chown
retcode = subprocess.call( ["/usr/bin/sudo", "/bin/chown", "root", "/my_file"] )
8.162. python-ethtool 8.162.1. RHBA-2013:1662 - python-ethtool bug fix update Updated python-ethtool packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The python-ethtool packages make the ethtool kernel interface available within the Python programming environment to allow querying and changing of Ethernet card settings, such as speed, port, auto-negotiation, and PCI locations. Bug Fixes BZ# 855920 Previously, the _haveNetwork() routine from the firstboot.loader module returned "False" when set up exclusively for IPv6. As a consequence, there was no network connection. A patch that detects IPv6-only active devices has been applied, and the _haveNetwork() routine now returns "True" as expected. BZ# 876211 Prior to this update, if more IPv4 addresses were bound to one interface, the pifconfig script, which displays information about a network interface, failed to produce the correct output. As a result, two interfaces with the same IPv4 address were reported. A patch has been applied, and the pifconfig script now reports multiple IPv4 addresses correctly. Users of python-ethtool are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 27. Monitoring Stratis file systems As a Stratis user, you can view information about Stratis volumes on your system to monitor their state and free space. 27.1. Displaying information about Stratis volumes You can lists statistics about your Stratis volumes, such as the total, used, and free size or file systems and block devices belonging to a pool, by using the stratis utility. Standard Linux utilities such as df report the size of the XFS file system layer on Stratis, which is 1 TiB. This is not useful information, because the actual storage usage of Stratis is less due to thin provisioning, and also because Stratis automatically grows the file system when the XFS layer is close to full. Important Regularly monitor the amount of data written to your Stratis file systems, which is reported as the Total Physical Used value. Make sure it does not exceed the Total Physical Size value. Prerequisites Stratis is installed. See Installing Stratis . The stratisd service is running. Procedure To display information about all block devices used for Stratis on your system: To display information about all Stratis pools on your system: To display information about all Stratis file systems on your system: Additional resources stratis(8) man page on your system 27.2. Viewing a Stratis pool by using the web console You can use the web console to view an existing Stratis pool and the file systems it contains. Prerequisites You have installed the RHEL 9 web console. You have enabled the cockpit service. Your user account is allowed to log in to the web console. For instructions, see Installing and enabling the web console . The stratisd service is running. You have an existing Stratis pool. Procedure Log in to the RHEL 9 web console. Click Storage . In the Storage table, click the Stratis pool you want to view. The Stratis pool page displays all the information about the pool and the file systems that you created in the pool.

Commands:
stratis blockdev Pool Name Device Node Physical Size State Tier my-pool /dev/sdb 9.10 TiB In-use Data
stratis pool Name Total Physical Size Total Physical Used my-pool 9.10 TiB 598 MiB
stratis filesystem Pool Name Name Used Created Device my-pool my-fs 546 MiB Nov 08 2018 08:03 /dev/stratis/ my-pool/my-fs
Chapter 2. Architectures Red Hat Enterprise Linux 9.4 is distributed with the kernel version 5.14.0-427.13.1, which provides support for the following architectures at the minimum required version (stated in parentheses): AMD and Intel 64-bit architectures (x86-64-v2) The 64-bit ARM architecture (ARMv8.0-A) IBM Power Systems, Little Endian (POWER9) 64-bit IBM Z (z14) Make sure you purchase the appropriate subscription for each architecture.

Commands:
2.2.4.5. NFS Firewall Configuration The ports used for NFS are assigned dynamically by rpcbind, which can cause problems when creating firewall rules. To simplify this process, use the /etc/sysconfig/nfs file to specify which ports are to be used: MOUNTD_PORT - TCP and UDP port for mountd (rpc.mountd) STATD_PORT - TCP and UDP port for status (rpc.statd) LOCKD_TCPPORT - TCP port for nlockmgr (rpc.lockd) LOCKD_UDPPORT - UDP port nlockmgr (rpc.lockd) Port numbers specified must not be used by any other service. Configure your firewall to allow the port numbers specified, as well as TCP and UDP port 2049 (NFS). Run the rpcinfo -p command on the NFS server to see which ports and RPC programs are being used.

Commands:
5.2. Sed The sed command with the -i option lets you delete the contents of a read-only file and lets you delete other protected files. The permissions on a file define what actions can take place to that file, while the permissions on a directory define what actions can be taken to the list of files in that directory. For this reason, sed does not let you use -i on a write-enabled file in a read-only directory, and will break symbolic or hard links when the -i option is used on such a file.

Commands:
25.3.4. Global Directives Global directives are configuration options that apply to the rsyslogd daemon. They usually specify a value for a specific predefined variable that affects the behavior of the rsyslogd daemon or a rule that follows. All of the global directives must start with a dollar sign ( USD ). Only one directive can be specified per line. The following is an example of a global directive that specifies the maximum size of the syslog message queue: The default size defined for this directive ( 10,000 messages) can be overridden by specifying a different value (as shown in the example above). You can define multiple directives in your /etc/rsyslog.conf configuration file. A directive affects the behavior of all configuration options until another occurrence of that same directive is detected. Global directives can be used to configure actions, queues and for debugging. A comprehensive list of all available configuration directives can be found in the section called "Online Documentation" . Currently, a new configuration format has been developed that replaces the USD-based syntax (see Section 25.4, "Using the New Configuration Format" ). However, classic global directives remain supported as a legacy format.

Commands:
USDMainMsgQueueSize 50000
Preface Red Hat Enterprise Linux minor releases are an aggregation of individual security, enhancement, and bug fix errata. The Red Hat Enterprise Linux 7.4 Release Notes document describes the major changes made to the Red Hat Enterprise Linux 7 operating system and its accompanying applications for this minor release, as well as known problems and a complete list of all currently available Technology Previews. Capabilities and limits of Red Hat Enterprise Linux 7 as compared to other versions of the system are available in the Red Hat Knowledgebase article available at https://access.redhat.com/articles/rhel-limits . Packages distributed with this release are listed in Red Hat Enterprise Linux 7 Package Manifest . Migration from Red Hat Enterprise Linux 6 is documented in the Migration Planning Guide. For information regarding the Red Hat Enterprise Linux life cycle, refer to https://access.redhat.com/support/policy/updates/errata/ .

Commands:
Chapter 3. Additional Resources For more information about Red Hat Developer Toolset 12.0 and Red Hat Enterprise Linux, see the resources listed below. 3.1. Red Hat Product Documentation The Red Hat Documentation portal located at https://access.redhat.com/documentation/ serves as a central source of all product documentation. It is translated in 22 languages and for each product, it provides different kinds of books from release and technical notes to installation, user, and reference guides in HTML, PDF, and EPUB formats. The following is a brief list of documents that are directly or indirectly relevant to this book: Red Hat Developer Toolset 12.0 User Guide - The User Guide for Red Hat Developer Toolset contains more information about installing and using this content set. Red Hat Software Collections 3.8 Packaging Guide - The Packaging Guide for Red Hat Software Collections explains the concept of Software Collections, documents the scl utility, and provides a detailed explanation of how to create a custom Software Collection or extend an existing one. Red Hat Software Collections 3.8 Release Notes - The Release Notes for Red Hat Software Collections document known problems, possible issues, and other important information available at the time of release of the content set. They also contain useful information on installing, rebuilding, migrating etc. Using Red Hat Software Collections Container Images - This book provides information on how to use container images based on Red Hat Software Collections. The available container images include applications, daemons, databases, as well as the Red Hat Developer Toolset container images. The images can be run on Red Hat Enterprise Linux 7 Server and Red Hat Enterprise Linux Atomic Host. Red Hat Enterprise Linux 7 Developer Guide - The Developer Guide for Red Hat Enterprise Linux 7 provides an introduction to application development tools in Red Hat Enterprise Linux 7. Red Hat Developer Tools documentation - The Red Hat Developer Tools provides the Eclipse Integrated Development Environment and the following compiler toolsets: Clang and LLVM Toolset, Rust Toolset, and Go Toolset. 3.2. Red Hat Developers Red Hat Developer Program - The Red Hat Developers community portal. Overview of Red Hat Developer Toolset on Red Hat Developers - The Red Hat Developers portal provides a number of tutorials to get you started with developing code using different development technologies. This includes the Node.js, Perl, PHP, Python, and Ruby Software Collections. Red Hat Developer Blog - The Red Hat Developer Blog contains up-to-date information, best practices, opinion, product and program announcements as well as pointers to sample code and other resources for those who are designing and developing applications based on Red Hat technologies.

Commands:
5.372. zsh 5.372.1. RHBA-2012:0937 - zsh bug fix and enhancement update Updated zsh packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The zsh shell is a command interpreter which can be used as an interactive login shell and as a shell script command processor. Zsh resembles the ksh shell (the Korn shell), but includes many enhancements. Zsh supports command line editing, built-in spelling correction, programmable command completion, shell functions (with autoloading), a history mechanism, and more. Bug Fix BZ# 657300 Prior to this update, the zsh shell attempted to execute mathematical expressions in the "-n" option when running in ksh mode. As a consequence, zsh emitted errors when running a syntax only check. This update modifies the source code so that mathematical expressions are now handled like any other command when using the "-n" option. Enhancement BZ# 612685 Prior to this update, a script whose location was listed in "USDPATH" could not be run with the zsh shell. With this update, users can call a script from "USDPATH" with the "-o pathscript" option to search path when zsh is invoked directly. All users are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
Chapter 25. Monitoring Stratis file systems As a Stratis user, you can view information about Stratis volumes on your system to monitor their state and free space. 25.1. Displaying information about Stratis volumes You can lists statistics about your Stratis volumes, such as the total, used, and free size or file systems and block devices belonging to a pool, by using the stratis utility. Standard Linux utilities such as df report the size of the XFS file system layer on Stratis, which is 1 TiB. This is not useful information, because the actual storage usage of Stratis is less due to thin provisioning, and also because Stratis automatically grows the file system when the XFS layer is close to full. Important Regularly monitor the amount of data written to your Stratis file systems, which is reported as the Total Physical Used value. Make sure it does not exceed the Total Physical Size value. Prerequisites Stratis is installed. See Installing Stratis . The stratisd service is running. Procedure To display information about all block devices used for Stratis on your system: To display information about all Stratis pools on your system: To display information about all Stratis file systems on your system: Additional resources stratis(8) man page on your system 25.2. Viewing a Stratis pool by using the web console You can use the web console to view an existing Stratis pool and the file systems it contains. Prerequisites You have installed the RHEL 9 web console. You have enabled the cockpit service. Your user account is allowed to log in to the web console. For instructions, see Installing and enabling the web console . The stratisd service is running. You have an existing Stratis pool. Procedure Log in to the RHEL 9 web console. Click Storage . In the Storage table, click the Stratis pool you want to view. The Stratis pool page displays all the information about the pool and the file systems that you created in the pool.

Commands:
stratis blockdev Pool Name Device Node Physical Size State Tier my-pool /dev/sdb 9.10 TiB In-use Data
stratis pool Name Total Physical Size Total Physical Used my-pool 9.10 TiB 598 MiB
stratis filesystem Pool Name Name Used Created Device my-pool my-fs 546 MiB Nov 08 2018 08:03 /dev/stratis/ my-pool/my-fs
Chapter 17. tags Optional. An operator-defined list of tags placed on each log by the collector or normalizer. The payload can be a string with whitespace-delimited string tokens or a JSON list of string tokens. Data type text file The path to the log file from which the collector reads this log entry. Normally, this is a path in the /var/log file system of a cluster node. Data type text offset The offset value. Can represent bytes to the start of the log line in the file (zero- or one-based), or log line numbers (zero- or one-based), so long as the values are strictly monotonically increasing in the context of a single log file. The values are allowed to wrap, representing a new version of the log file (rotation). Data type long

Commands:
32.2.3. Adding a Group To add a group to the system, use the command groupadd : Command line options for groupadd are detailed in Table 32.2, " groupadd Command Line Options" . Table 32.2. groupadd Command Line Options Option Description -g <gid> Group ID for the group, which must be unique and greater than 499 -r Create a system group with a GID less than 500 -f When used with -g <gid> and <gid> already exists, groupadd will choose another unique <gid> for the group.

Commands:
groupadd <group-name>