mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 78. versions This chapter describes the commands under the versions command. 78.1. versions show Show available versions of services Usage: Table 78.1. Command arguments Value Summary -h, --help Show this help message and exit --all-interfaces Show values for all interfaces --interface <interface> Show versions for a specific interface. --region-name <region_name> Show versions for a specific region. --service <service> Show versions for a specific service. the argument should be either an exact match to what is in the catalog or a known official value or alias from service-types-authority ( https://service- types.openstack.org/) --status <status> Show versions for a specific status. valid values are: - SUPPORTED - CURRENT - DEPRECATED - EXPERIMENTAL Table 78.2. Output formatter options Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated --sort-ascending Sort the column(s) in ascending order --sort-descending Sort the column(s) in descending order Table 78.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 78.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 78.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 versions show [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--sort-ascending | --sort-descending] [--all-interfaces | --interface <interface>] [--region-name <region_name>] [--service <service>] [--status <status>]
5.2. Global Settings The global settings configure parameters that apply to all servers running HAProxy. A typical global section may look like the following: In the above configuration, the administrator has configured the service to log all entries to the local syslog server. By default, this could be /var/log/syslog or some user-designated location. The maxconn parameter specifies the maximum number of concurrent connections for the service. By default, the maximum is 2000. The user and group parameters specifies the user name and group name for which the haproxy process belongs. Finally, the daemon parameter specifies that haproxy run as a background process.

Commands:
global log 127.0.0.1 local2 maxconn 4000 user haproxy group haproxy daemon
5.78. gdb 5.78.1. RHBA-2012:0930 - gdb bug fix update Updated gdb packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. The GNU Debugger (GDB) is the standard debugger for Linux. With GDB, users can debug programs written in C, C++, and other languages by executing them in a controlled fashion and printing out their data. Bug Fixes BZ# 739685 To load a core file, GDB requires the binaries that were used to produce the core file. GDB uses a built-in detection to load the matching binaries automatically. However, you can specify arbitrary binaries manually and override the detection. Previously, loading other binaries that did not match the invoked core file could cause GDB to terminate unexpectedly. With this update, the underlying code has been modified and GDB no longer crashes under these circumstances. BZ# 750341 Previously, GDB could terminate unexpectedly when loading symbols for a C++ program compiled with early GCC compilers due to errors in the cp_scan_for_anonymous_namespaces() function. With this update, an upstream patch that fixes this bug has been adopted and GDB now loads any known executables without crashing. BZ# 781571 If GDB failed to find the associated debuginfo rpm symbol files, GDB displayed the following message suggesting installation of the symbol files using the yum utility: Missing separate debuginfo for the main executable file Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/47/830504b69d8312361b1ed465ba86c9e815b800 However, the suggested "--enablerepo='*-debuginfo'" option failed to work with RHN (Red Hat Network) debug repositories. This update corrects the option in the message to "--enablerepo='*-debug*'" and the suggested command works as expected. BZ# 806920 On PowerPC platforms, DWARF information created by the IBM XL Fortran compiler does not contain the DW_AT_type attribute for DW_TAG_subrange_type; however, DW_TAG_subrange_type in the DWARF information generated by GCC always contains the DW_AT_type attribute. Previously, GDB could interpret arrays from IBM XL Fortran compiler incorrectly as it was missing the DW_AT_type attribute, even though this is in accordance with the DWARF standard. This updated GDB now correctly provides a stub index type if DW_AT_type is missing for any DW_TAG_subrange_type, and processes debug info from both IBM XL Fortran and GCC compilers correctly. All users of gdb are advised to upgrade to these updated packages, which fix these bugs.

Commands:
1.2. What Are Software Collections? With Software Collections, you can build and concurrently install multiple versions of the same software components on your system. Software Collections have no impact on the system versions of the packages installed by any of the conventional RPM package management utilities. Software Collections: Do not overwrite system files Software Collections are distributed as a set of several components, which provide their full functionality without overwriting system files. Are designed to avoid conflicts with system files Software Collections make use of a special file system hierarchy to avoid possible conflicts between a single Software Collection and the base system installation. Require no changes to the RPM package manager Software Collections require no changes to the RPM package manager present on the host system. Need only minor changes to the spec file To convert a conventional package to a single Software Collection, you only need to make minor changes to the package spec file. Allow you to build a conventional package and a Software Collection package with a single spec file With a single spec file, you can build both the conventional package and the Software Collection package. Uniquely name all included packages With Software Collection's namespace, all packages included in the Software Collection are uniquely named. Do not conflict with updated packages Software Collection's namespace ensures that updating packages on your system causes no conflicts. Can depend on other Software Collections Because one Software Collection can depend on another, you can define multiple levels of dependencies.

Commands:
Chapter 143. KafkaConnectorSpec schema reference Used in: KafkaConnector Property Property type Description class string The Class for the Kafka Connector. tasksMax integer The maximum number of tasks for the Kafka Connector. autoRestart AutoRestart Automatic restart of connector and tasks configuration. config map The Kafka Connector configuration. The following properties cannot be set: name, connector.class, tasks.max. pause boolean The pause property has been deprecated. Deprecated in Streams for Apache Kafka 2.6, use state instead. Whether the connector should be paused. Defaults to false. state string (one of [running, paused, stopped]) The state the connector should be in. Defaults to running. listOffsets ListOffsets Configuration for listing offsets. alterOffsets AlterOffsets Configuration for altering offsets.

Commands:
Chapter 1. About Red Hat OpenShift GitOps Red Hat OpenShift GitOps is an Operator that uses Argo CD as the declarative GitOps engine. It enables GitOps workflows across multicluster OpenShift and Kubernetes infrastructure. Using Red Hat OpenShift GitOps, administrators can consistently configure and deploy Kubernetes-based infrastructure and applications across clusters and development lifecycles. Red Hat OpenShift GitOps is based on the open source project Argo CD and provides a similar set of features to what the upstream offers, with additional automation, integration into Red Hat {OCP} and the benefits of Red Hat's enterprise support, quality assurance and focus on enterprise security. Note Because Red Hat OpenShift GitOps releases on a different cadence from OpenShift Dedicated, the Red Hat OpenShift GitOps documentation is now available as a separate documentation set at Red Hat OpenShift GitOps .

Commands:
Chapter 6. New Packages 6.1. RHEA-2015:1420 - new packages: clufter New clufter packages are now available for Red Hat Enterprise Linux 6. The clufter packages contain a tool for transforming and analyzing cluster configuration formats. Notably, clufter can be used to assist with migration from an older stack configuration to a newer one that leverages Pacemaker. The packages can be used either as a separate command-line tool or as a Python library. This enhancement update adds the clufter packages to Red Hat Enterprise Linux 6. (BZ# 1182358 ) All users who require clufter are advised to install these new packages.

Commands:
25.7.2. Exporting Messages to a Database Processing of log data can be faster and more convenient when performed in a database rather than with text files. Based on the type of DBMS used, choose from various output modules such as ommysql , ompgsql , omoracle , or ommongodb . As an alternative, use the generic omlibdbi output module that relies on the libdbi library. The omlibdbi module supports database systems Firebird/Interbase, MS SQL, Sybase, SQLite, Ingres, Oracle, mSQL, MySQL, and PostgreSQL. Example 25.16. Exporting Rsyslog Messages to a Database To store the rsyslog messages in a MySQL database, add the following into /etc/rsyslog.conf : First, the output module is loaded, then the communication port is specified. Additional information, such as name of the server and the database, and authentication data, is specified on the last line of the above example.

Commands:
USDModLoad ommysql USDActionOmmysqlServerPort 1234 *.* :ommysql:database-server,database-name,database-userid,database-password
Chapter 3. Getting started with OpenShift Virtualization You can explore the features and functionalities of OpenShift Virtualization by installing and configuring a basic environment. Note Cluster configuration procedures require cluster-admin privileges. 3.1. Planning and installing OpenShift Virtualization Plan and install OpenShift Virtualization on an OpenShift Container Platform cluster: Plan your bare metal cluster for OpenShift Virtualization . Prepare your cluster for OpenShift Virtualization . Install the OpenShift Virtualization Operator . Install the virtctl command line interface (CLI) tool . Planning and installation resources Using a CSI-enabled storage provider . Configuring local storage for virtual machines . Installing the Kubernetes NMState Operator . Specifying nodes for virtual machines . Virtctl commands . 3.2. Creating and managing virtual machines Create virtual machines (VMs) by using the web console: Quick create a VM . Customize a template to create a VM . Connect to the VMs: Connect to the serial console or VNC console of a VM by using the web console. Connect to a VM by using SSH . Connect to a Windows VM by using RDP . Manage the VMs: Stop, start, pause, and restart a VM by using the web console . Manage a VM, expose a port, or connect to the serial console by using the virtctl CLI tool . 3.3. steps Connect the VMs to secondary networks: Connect a VM to a Linux bridge network . Connect a VM to an SR-IOV network . Note VMs are connected to the pod network by default. You must configure a secondary network, such as Linux bridge or SR-IOV, and then add the network to the VM configuration. Monitor resources, details, status, and top consumers by using the web console . View high-level information about VM workloads by using the web console . View OpenShift Virtualization logs by using the CLI . Automate Windows VM deployments with sysprep . Live migrate VMs . Back up and restore VMs .

Commands:
4.8. Data Journaling Ordinarily, GFS writes only metadata to its journal. File contents are subsequently written to disk by the kernel's periodic sync that flushes file-system buffers. An fsync() call on a file causes the file's data to be written to disk immediately. The call returns when the disk reports that all data is safely written. Data journaling can result in a reduced fsync() time, especially for small files, because the file data is written to the journal in addition to the metadata. An fsync() returns as soon as the data is written to the journal, which can be substantially faster than the time it takes to write the file data to the main file system. Applications that rely on fsync() to sync file data may see improved performance by using data journaling. Data journaling can be enabled automatically for any GFS files created in a flagged directory (and all its subdirectories). Existing files with zero length can also have data journaling turned on or off. Using the gfs_tool command, data journaling is enabled on a directory (and all its subdirectories) or on a zero-length file by setting the inherit_jdata or jdata attribute flags to the directory or file, respectively. The directory and file attribute flags can also be cleared. Usage Setting and Clearing the inherit_jdata Flag Setting and Clearing the jdata Flag Directory Specifies the directory where the flag is set or cleared. File Specifies the zero-length file where the flag is set or cleared. Examples This example shows setting the inherit_jdata flag on a directory. All files created in the directory or any of its subdirectories will have the jdata flag assigned automatically. Any data written to the files will be journaled. This example shows setting the jdata flag on a file. The file must be zero size. Any data written to the file will be journaled.

Commands:
gfs_tool setflag inherit_jdata Directory gfs_tool clearflag inherit_jdata Directory
gfs_tool setflag jdata File gfs_tool clearflag jdata File
gfs_tool setflag inherit_jdata /gfs1/data/
gfs_tool setflag jdata /gfs1/datafile
4.318. tcp_wrappers 4.318.1. RHEA-2011:1676 - tcp_wrappers enhancement update Enhanced tcp_wrappers packages are now available for Red Hat Enterprise Linux 6. The tcp_wrappers packages provide small daemon programs which can monitor and filter incoming requests for systat, finger, FTP, telnet, rlogin, rsh, exec, tftp, talk and other network services. These packages also contain the libwrap library, which adds the same filtering capabilities to programs linked against it, such as to sshd among others. Enhancement BZ# 727287 Previously, the tcp_wrappers packages were compiled without the RELRO (read-only relocations) flag. Programs provided by this package and also programs built against the tcp_wrappers libraries were thus vulnerable to various attacks based on overwriting the ELF section of a program. To increase the security of tcp_wrappers programs and libraries, the tcp_wrappers spec file has been modified to use the "-Wl,-z,relro" flags when compiling the packages. As a result, the tcp_wrappers packages are now provided with partial RELRO protection. Users of tcp_wrappers are advised to upgrade to these updated packages, which add this enhancement.

Commands:
Preface You can integrate some public clouds and third-party applications with the Hybrid Cloud Console. For information about integrating public clouds, see Configuring cloud integrations for Red Hat services . You can integrate the Red Hat Hybrid Cloud Console with Splunk, ServiceNow, Slack, Event-Driven Ansible, Microsoft Teams, Google Chat, and more applications to route event-triggered notifications to those third-party applications. Integrating third-party applications expands the scope of notifications beyond emails and messages, so that you can view and manage Hybrid Cloud Console events from your preferred platform dashboard or communications tool. To learn more about notifications, see Configuring notifications on the Red Hat Hybrid Cloud Console . Prerequisites You have Organization Administrator or Notifications administrator permissions for the Hybrid Cloud Console. You have the required configuration permissions for each third-party application that you want to integrate with the Hybrid Cloud Console.

Commands:
12.3. Restrictions and Limitations It is strongly recommended to run Red Hat Enterprise Linux 7.2 or later in the L0 host and the L1 guests. L2 guests can contain any guest system supported by Red Hat. It is not supported to migrate L1 or L2 guests. Use of L2 guests as hypervisors and creating L3 guests is not supported. Not all features available on the host are available to be utilized by the L1 hypervisor. For instance, IOMMU/VT-d or APICv cannot be used by the L1 hypervisor. To use nested virtualization, the host CPU must have the necessary feature flags. To determine if the L0 and L1 hypervisors are set up correctly, use the cat /proc/cpuinfo command on both L0 and L1, and make sure that the following flags are listed for the respective CPUs on both hypervisors: For Intel - vmx (Hardware Virtualization) and ept (Extended Page Tables) For AMD - svm (equivalent to vmx) and npt (equivalent to ept)

Commands:
24.3. Viewing CPU Usage 24.3.1. Using the System Monitor Tool The Resources tab of the System Monitor tool allows you to view the current CPU usage on the system. To start the System Monitor tool, either select Applications System Tools System Monitor from the panel, or type gnome-system-monitor at a shell prompt. Then click the Resources tab to view the system's CPU usage. Figure 24.3. System Monitor - Resources In the CPU History section, the System Monitor tool displays a graphical representation of the CPU usage history and shows the percentage of how much CPU is currently in use.

Commands:
7.135. netcf 7.135.1. RHBA-2015:1307 - netcf bug fix update Updated netcf packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The netcf packages contain a library for modifying the network configuration of a system. Network configuration is expressed in a platform-independent XML format, which netcf translates into changes to the system's "native" network configuration files. Bug Fixes BZ# 1113978 Previously, when the XML configuration for an interface enabled dynamic host configuration protocol (DHCP) for IPv6, the netcf library erroneously set the variable named "DHCPV6" in the ifcfg configuration file instead of "DHCPV6C". The underlying source code has been patched, and netcf now passes the correct "DHCPV6C" option to ifcfg. BZ# 1116314 Prior to this update, when requested to configure an interface with an IPv4 netmask of 255.255.255.255, the netcf library logged an error as the interface configuration was rejected. This update fixes the netmask for the 32-bit interface prefix, and netcf now configures IPv4 interfaces successfully. BZ# 1208897 Due to a parsing error, the ifcfg files with comments starting anywhere beyond column 1 or multiple variables on a single line caused the netcf library to generate errors when attempting to list host interfaces. The parsing error has been fixed, and any tool using netcf now lists active interfaces as expected. BZ# 1208894 When multiple static IPv6 addresses were specified in an interface configuration, an extra set of quotes appeared in the IPV6ADDR_SECONDARIES entry in the generated configuration file. This update removes extraneous single quotes from IPV6ADDR_SECONDARIES, thus fixing this bug. BZ# 1165966 Due to a denial of a service flaw in the netcf library, a specially crafted interface name previously caused applications using netcf, such as the libvirt daemon, to terminate unexpectedly. An upstream patch has been applied to fix this bug, and applications using netcf no longer crash in the aforementioned situation. Users of netcf are advised to upgrade to these updated packages, which fix these bugs.

Commands:
4.4. aide 4.4.1. RHBA-2012:0512 - aide bug fix update Updated aide packages that fix one bug are now available for Red Hat Enterprise Linux 6. Advanced Intrusion Detection Environment (AIDE) is a program that creates a database of files on a system, and then uses that database to ensure file integrity and detect system intrusions. Bug Fix BZ# 811936 Previously, the aide utility incorrectly initialized the gcrypt library. This consequently prevented aide to initialize its database if the system was running in FIPS-compliant mode. The initialization routine has been corrected, and along with an extension to the libgcrypt's API introduced in the RHEA-2012:0486 advisory, aide now initializes its database as expected if run in a FIPS-compliant way. All users of aide are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 2. Certification prerequisites for Red Hat OpenStack Platform Application Companies must be Partners in Red Hat Connect for Technology Partners . This program enables an ecosystem for commercial OpenStack deployments and includes numerous technology companies. You must have a support relationship with Red Hat. This can be fulfilled through the multi-vendor support network of TSANet, or through a custom support agreement. You must have a good working knowledge of Red Hat OpenStack Platform (RHOSP) including installation and configuration of the product. You must have a tested application on a supported RHOSP release. Note The RHOSP application certification does not verify if your application's intended behavior matches the application's actual behavior. This responsibility remains under your full control. Additional resources For more information about the product, see detailed product documentation on Red Hat Customer Portal To undertake the product training or certification, see Red Hat Training Page

Commands: