mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 8. MBean counter types The MBean counter types that you can specify as part of a custom trigger definition are standard MBean metrics that are generally available in the JDK by default. These MBean counters cover a range of runtime, memory, thread, and operating system metrics. The following is a full list of the MBean counter types that you can specify in a custom trigger definition: Note The name of each MBean counter that you specify as part of a custom trigger definition must exactly match the spelling and capitalization of the MBean counter names in the following list. Operating system metrics Arch AvailableProcessors Name SystemLoadAverage Version CommittedVirtualMemorySize FreePhysicalMemorySize FreeSwapSpaceSize ProcessCpuLoad ProcessCpuTime SystemCpuLoad TotalPhysicalMemorySize TotalSwapSpaceSize Thread metrics AllThreadIds CurrentThreadCpuTime CurrentThreadUserTime DaemonThreadCount PeakThreadCount ThreadCount TotalStartedThreadCount CurrentThreadCpuTimeSupported ObjectMonitorUsageSupported SynchronizerUsageSupported ThreadContentionMonitoringEnabled ThreadContentionMonitoringSupported ThreadCpuTimeEnabled ThreadCpuTimeSupported Runtime metrics BootClassPathSupported BootClassPath ClassPath InputArguments LibraryPath ManagementSpecVersion Name SpecName SpecVersion SystemProperties StartTime Uptime VmName VmVendor VmVersion Memory metrics HeapMemoryUsage NonHeapMemoryUsage ObjectPendingFinalizationCount FreeHeapMemory FreeNonHeapMemory HeapMemoryUsagePercent Verbose Revised on 2023-12-08 09:01:56 UTC

Commands:
Chapter 8. Deleting functions You can delete a function. You can do it using the kn func tool. 8.1. Deleting a function You can delete a function by using the kn func delete command. This is useful when a function is no longer required, and can help to save resources on your cluster. Procedure Delete a function: USD kn func delete [<function_name> -n <namespace> -p <path>] If the name or path of the function to delete is not specified, the current directory is searched for a func.yaml file that is used to determine the function to delete. If the namespace is not specified, it defaults to the namespace value in the func.yaml file.

Commands:
kn func delete [<function_name> -n <namespace> -p <path>]
Chapter 3. Editing a model registry You can edit the details of existing model registries, such as the model registry name, description, and database connection details. Prerequisites You have logged in to OpenShift AI as a user with OpenShift AI administrator privileges. A cluster administrator has configured and enabled the model registry component in your OpenShift AI deployment. For more information, see Configuring the model registry component . The model registry component is enabled for your OpenShift AI deployment, and contains at least 1 model registry. Procedure From the OpenShift AI dashboard, click Settings Model registry settings . Click the action menu ( ... ) beside the model registry that you want to edit, and then click Edit model registry . The Edit model registry dialog opens. Optional: In the Name field, edit the name of the model registry. Optional: In the Description field, edit the description of the model registry. Optional: In the Connect to external MySQL database section, edit the information for the external database where model data for the registry is stored. In the Host field, enter the database's host name. If the database is running in the rhoai-model-registries namespace, enter only the hostname for the database. If the database is running in a different namespace from rhoai-model-registries , enter the database hostname details in <host name>.<namespace>.svc.cluster.local format. In the Port field, enter the port number for the database. In the Username field, enter the default user name that is connected to the database. In the Password field, enter the password for the default user account. In the Database field, enter the database name. Optional: Select the Add CA certificate to secure database connection to use a certificate with your database connection. Click Use cluster-wide CA bundle to use the ca-bundle.crt bundle in the odh-trusted-ca-bundle ConfigMap. Click Use Red Hat OpenShift AI CA bundle to use the odh-ca-bundle.crt bundle in the odh-trusted-ca-bundle ConfigMap. Click Choose from existing certificates to select an existing certificate. You can select the key of any ConfigMap or secret in the rhoai-model-registries namespace. From the Resource list, select a ConfigMap or secret. From the Key list, select a key. Click Upload new certificate to upload a new certificate as a ConfigMap. Drag and drop the PEM file for your certificate into the Certificate field, or click Upload to select a file from your local machine's file system. Note Uploading a certificate creates the db-credential ConfigMap with the ca.crt key. To upload a certificate as a secret, you must create a secret in the OpenShift rhoai-model-registries namespace, and then select it as an existing certificate when you create your model registry. For more information about creating secrets in OpenShift, see Providing sensitive data to pods by using secrets . Click Update . Verification The model registry appears with updated details on the Model Registry Settings page.

Commands:
8.238. xorg-x11-drv-intel 8.238.1. RHBA-2013:1589 - xorg-x11-drv-intel bug fix and enhancement update Updated xorg-x11-drv-intel packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-intel package contains an Intel integrated graphics video driver for the X.Org implementation of the X Window System. Note Within the xorg-x11 package, intel-gpu-tools has been upgraded to upstream version 2.21.12, which provides a number of bug fixes and enhancements over the version. (BZ# 906036 ) Bug Fixes BZ# 886191 Previously, when Red Hat Enterprise Linux 6 was installed on some workstations, Anaconda chose the fbdev driver instead of the i915 Intel driver. With this update, the Intel driver is selected, thus fixing the bug. BZ# 999334 When building rpms from src rpms, the spec definition and sources produced files, which were not packaged in the last phase of the rpmbuild procedure. Consequently, rpmbuild did not create rpm(s) even if everything else was built successfully, and the following error message was returned: Installed (but unpackaged) file(s) found This bug has been fixed and all files are now packaged as expected. Users of xorg-x11-drv-intel are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
B.10.5. RHBA-2011:1363 - corosync bug fix update Updated corosync packages that fix several bugs are now available for Red Hat Enterprise Linux 6 Extended Update Support. The corosync packages provide the Corosync Cluster Engine and C Application Programming Interfaces (APIs) for Red Hat Enterprise Linux cluster software. Bug Fixes BZ# 726607 Previously, under heavy traffic, receive buffers sometimes overflowed, causing loss of packets. Consequently, retransmit list error messages appeared in the log files. This bug has been fixed, incoming messages are now processed more frequently, and the retransmit list error messages no longer appear in the described scenario. BZ# 727960 Previously, when a combination of a lossy network and a large number of configuration changes was used with corosync, corosync sometimes terminated unexpectedly. This bug has been fixed, and corosync no longer crashes in the described scenario. BZ# 734996 Prior to this update, when corosync ran the "cman_tool join" and "cman_tool leave" commands in a loop, corosync sometimes terminated unexpectedly. This bug has been fixed, and corosync no longer crashes in the described scenario. All users of corosync are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 1. Installation overview Red Hat Enterprise Linux AI is distributed and installable as a bootable image. This bootable image includes a container that hold various software and tools for RHEL AI. Each image is compiled to support specific hardware vendors. Each RHEL AI image includes: Red Hat Enterprise Linux 9.4: A RHEL version 9.4 operating system (OS) for your machine. The InstructLab container: Contains InstructLab and various other tools required for RHEL AI. This includes: Python version 3.11: A Python 3.11 installation used internally by InstructLab. The InstructLab tools: The InstructLab command line interface (CLI). The LAB enhanced method of synthetic data generation (SDG). The LAB enhanced method of single and multi-phase training. InstructLab with vLLM: A high-input inference and serving engine for Large Language models (LLMs). InstructLab with DeepSpeed: A learning optimization software that speeds up the training and inferencing process. Red Hat Enterprise Linux AI version 1.1 also includes a sample taxonomy tree with example skills and knowledge that you can download and use for training a model. For general availability, there are three options for installing and deploying Red Hat Enterprise Linux AI. Installing on bare metal Installing on AWS Installing on IBM Cloud After installation with Red Hat Enterprise Linux AI general availability, you can manually download open source Granite LLMs that you can chat and interact with. For more information about downloading these models, see Downloading additional models . Important For Red Hat Enterprise Linux AI general availability, Red Hat only provides bootable images compiled to NVIDIA hardware. For more information about supported hardware, see "Red Hat Enterprise Linux AI hardware requirements" in the "Getting Started" documentation.

Commands:
10.4.3. Discontinued Kernel Components NBD - Network Block Device supplanted by iSCSI in Red Hat Enterprise Linux 6. HFS - Apple filesystem support discontinued in Red Hat Enterprise Linux 6. Tux - Web Server accelerator discontinued in Red Hat Enterprise Linux 6. Non-PAE x86 kernel - versions of Red Hat Enterprise Linux contained multiple kernels for the i686 architecture: a kernel with, and a kernel without PAE. It has been many years since non-PAE hardware was sold in volume. Hence in Red Hat Enterprise Linux 6, there is only a single kernel, one that includes PAE. The Anticipatory I/O scheduler is deprecated and is not present in Red Hat Enterprise Linux 6. It is replaced by the CFQ (Completely Fair Queueing) I/O scheduler, which has been the default I/O scheduler in the Linux kernel since 2006. Customers using the Anticipatory I/O scheduler are encouraged to test their workload using CFQ and file bugs for any performance issues observed. While the goal is to make CFQ perform on par with the Anticipatory I/O scheduler in all tested workloads, Red Hat cannot guarantee that there will be no outliers.

Commands:
Managing configurations by using Puppet integration Red Hat Satellite 6.16 Configure Puppet integration in Satellite and use Puppet classes to configure your hosts Red Hat Satellite Documentation Team satellite-doc-list@redhat.com

Commands:
satellite-installer --enable-foreman-cli-puppet --enable-foreman-plugin-puppet --enable-puppet --foreman-proxy-puppet true --foreman-proxy-puppetca true --puppet-server true
satellite-installer --enable-puppet --foreman-proxy-puppet true --foreman-proxy-puppetca true --puppet-server true
<%= snippet 'puppet_setup' %>
dnf install puppet-agent
yum install puppet-agent
. /etc/profile.d/puppet-agent.sh
puppet config set server satellite.example.com --section agent puppet config set environment My_Puppet_Environment --section agent
puppet resource service puppet ensure=running enable=true
puppet ssl bootstrap
puppet ssl bootstrap
satellite-maintain plugin purge-puppet --remove-all-data
satellite-maintain plugin purge-puppet --remove-all-data
puppet module install puppetlabs-ntp -i /etc/puppetlabs/code/environments/production/modules
Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules Notice: Created target directory /etc/puppetlabs/code/environments/production/modules Notice: Downloading from https://forgeapi.puppet.com Notice: Installing -- do not interrupt /etc/puppetlabs/code/environments/production/modules |-| puppetlabs-ntp (v8.3.0) |-- puppetlabs-stdlib (v4.25.1) [/etc/puppetlabs/code/environments/production/modules]
puppet config print modulepath
/etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/environments/common:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules:/usr/share/puppet/modules
puppet module upgrade module name
Successfully updated environments and Puppet classes from the on-disk Puppet installation
0.de.pool.ntp.org, 1.de.pool.ntp.org, 2.de.pool.ntp.org, 3.de.pool.ntp.org
- 0.de.pool.ntp.org - 1.de.pool.ntp.org - 2.de.pool.ntp.org - 3.de.pool.ntp.org
--- parameters: // shortened YAML output classes: ntp: servers: '["0.de.pool.ntp.org","1.de.pool.ntp.org","2.de.pool.ntp.org","3.de.pool.ntp.org"]' environment: production
puppet agent -t
cat /etc/ntp.conf
ntp.conf: Managed by puppet. server 0.de.pool.ntp.org server 1.de.pool.ntp.org server 2.de.pool.ntp.org server 3.de.pool.ntp.org
12.5.4. IP version 6 BIND version 9 supports name service in IP version 6 (IPv6) environments through the use of A6 zone records. If the network environment includes both IPv4 and IPv6 hosts, use the lwresd lightweight resolver daemon on all network clients. This daemon is a very efficient, caching-only nameserver which understands the new A6 and DNAME records used under IPv6. Refer to the lwresd man page for more information.

Commands:
19.4. ntsysv The ntsysv utility provides a simple interface for activating or deactivating services. You can use ntsysv to turn an xinetd -managed service on or off. You can also use ntsysv to configure runlevels. By default, only the current runlevel is configured. To configure a different runlevel, specify one or more runlevels with the --level option. For example, the command ntsysv --level 345 configures runlevels 3, 4, and 5. The ntsysv interface works like the text mode installation program. Use the up and down arrows to navigate up and down the list. The space bar selects/unselects services and is also used to "press" the Ok and Cancel buttons. To move between the list of services and the Ok and Cancel buttons, use the Tab key. A * signifies that a service is set to on. Pressing the F1 key displays a short description of the selected service. Warning Services managed by xinetd are immediately affected by ntsysv . For all other services, changes do not take effect immediately. You must stop or start the individual service with the command service daemon stop . In the example, replace daemon with the name of the service you want to stop; for example, httpd . Replace stop with start or restart to start or restart the service.

Commands:
Virtualization Security Guide Red Hat Enterprise Linux 7 Securing hosts, guests, and shared infrastructure in virtualized environments on RHEL Jiri Herrmann Red Hat Customer Content Services jherrman@redhat.com Yehuda Zimmerman Red Hat Customer Content Services yzimmerm@redhat.com Scott Radvan Red Hat Customer Content Services Tahlia Richardson Red Hat Customer Content Services Thanks go to the following people for enabling the creation of this guide: Paul Moore Red Hat Engineering Kurt Seifried Red Hat Engineering David Jorm Red Hat Engineering

Commands:
Chapter 8. Errata Table 8.1. Errata Subcommand Description and tasks erratum List errata: Find erratum by CVE: Inspect erratum: host List errata applicable to a host: Apply errata to a host:

Commands:
hammer erratum list
hammer erratum list --cve CVE
hammer erratum info --id err_ID
hammer host errata list --host host_name
hammer host errata apply --host host_name --errata-ids err_ID1,err_ID2,
4.245. python-meh 4.245.1. RHBA-2011:1763 - python-meh bug fix update An updated python-meh package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The python-meh package provides a python library for handling exceptions. Bug Fixes BZ# 728871 Prior to this update, bug reports filed with python-meh were missing information. With this update, these bug reports now include more useful information on system architecture and versions of packages related to the bug. BZ# 730924 Prior to this update, the report packages which python-meh depended on were named "report-gtk" and "report-newt". The packages have been renamed "libreport-gtk" and "libreport-newt". This update changes the python-meh spec file to require these new report packages. All users of python-meh are advised to upgrade to this updated package, which fixes these bugs.

Commands:
21.2. Enabling NIS in Identity Management To enable NIS in Identity Management: Enable the NIS listener and compatibility plug-ins: Optional : Set a fixed port for the NIS remote procedure calls (RPC). When using NIS, the client must know to which port on the IdM server to use to establish the connection. Using the default settings, IdM binds to an unused random port when the server starts. This port is sent to the port mapper service the client uses to request the port number. For a more strict firewall configuration, you can set a fixed port. For example, to set the port to 514 : Note You can set any unused port number below 1024 for the setting. Enable and start the port mapper service: Restart Directory Server:

Commands:
ipa-nis-manage enable ipa-compat-manage enable
ldapmodify -x -D 'cn=directory manager' -W dn: cn=NIS Server,cn=plugins,cn=config changetype: modify add: nsslapd-pluginarg0 nsslapd-pluginarg0: 514
systemctl enable rpcbind.service systemctl start rpcbind.service
systemctl restart dirsrv.target
Chapter 7. Uploading files to your bucket To upload files to your bucket from your workbench, use the upload_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. You have imported the files that you want to upload to your object store to your workbench. Procedure In the notebook, locate the instructions to upload files to a bucket. Replace <file_name> , <bucket_name> and <object_name> with your own values, as shown in the example, and then run the code cell. Verification Locate the following instructions to list files in a bucket: Replace <bucket_name> with the name of your bucket, as shown in the example, and then run the code cell. The file that you uploaded is displayed in the output.

Commands:
#Upload file to bucket #Replace <file_name>, <bucket_name>, and <object_name> with your values. #<file_name>: Name of the file to upload. This must include the full local path to the file on your notebook. #<bucket_name>: The name of the bucket to upload the file to. #<object_name>: The full key to use to save the file to the bucket. s3_client.upload_file('<file_name>', '<bucket_name>', '<object_name>')
s3_client.upload_file('image-973-series123.csv', 'aqs973-image-registry', '/tmp/image-973-series124.csv')
#Upload Verification for key in s3_client.list_objects_v2(Bucket='<bucket_name>')['Contents']: print(key['Key'])
#Upload Verification for key in s3_client.list_objects_v2(Bucket='aqs973-image-registry')['Contents']: print(key['Key'])
20.2. Configuring an OpenSSH Server To run an OpenSSH server, you must first make sure that you have the proper RPM packages installed. The openssh-server package is required and depends on the openssh package. The OpenSSH daemon uses the configuration file /etc/ssh/sshd_config . The default configuration file should be sufficient for most purposes. If you want to configure the daemon in ways not provided by the default sshd_config , read the sshd man page for a list of the keywords that can be defined in the configuration file. To start the OpenSSH service, use the command /sbin/service sshd start . To stop the OpenSSH server, use the command /sbin/service sshd stop . If you want the daemon to start automatically at boot time, refer to Chapter 19, Controlling Access to Services for information on how to manage services. If you reinstall, the reinstalled system creates a new set of identification keys. Any clients who had connected to the system with any of the OpenSSH tools before the reinstall will see the following message: If you want to keep the host keys generated for the system, backup the /etc/ssh/ssh_host*key* files and restore them after the reinstall. This process retains the system's identity, and when clients try to connect to the system after the reinstall, they will not receive the warning message.

Commands:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed.
34.2.2. Choose Service Use the Choose Service screen to choose what kind of subscription service to register the system with. Click Proxy Setup to configure a proxy server if necessary. More information about subscription management with a proxy server can be found in the Red Hat Subscription Management guide. Red Hat Subscription Management Any subscription service which uses the proper X.509 certificates to identify the system, installed products, and attached subscriptions is part of Red Hat Subscription Management . This includes Customer Portal Subscription Management (hosted services), Subscription Asset Manager (on-premise subscription service and proxied content delivery), and CloudForms System Engine (on-premise subscription and content delivery services). This option is the default. Red Hat Subscription Management is strongly recommended for organizations that do not run a local Satellite server. Red Hat Network (RHN) Classic Select the Red Hat Network (RHN) Classic option to use the legacy systems-management features of Red Hat Network. While RHN Classic can be used with Red Hat Enterprise Linux 6.x systems, it is intended primarily for existing, legacy systems. It is recommended that new installations use Red Hat Subscription Management. An RHN Satellite or RHN Proxy Use this option in environments with access to a local mirror of the Red Hat Network content. Figure 34.4. Choose Service

Commands:
Appendix A. Using your subscription AMQ is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. A.1. Accessing your account Procedure Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. A.2. Activating a subscription Procedure Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. A.3. Downloading release files To access .zip, .tar.gz, and other release files, use the customer portal to find the relevant files for download. If you are using RPM packages or the Red Hat Maven repository, this step is not required. Procedure Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ product. The Software Downloads page opens. Click the Download link for your component. A.4. Registering your system for packages To install RPM packages for this product on Red Hat Enterprise Linux, your system must be registered. If you are using downloaded release files, this step is not required. Procedure Go to access.redhat.com . Navigate to Registration Assistant . Select your OS version and continue to the page. Use the listed command in your system terminal to complete the registration. For more information about registering your system, see one of the following resources: Red Hat Enterprise Linux 8 - Registering the system and managing subscriptions Red Hat Enterprise Linux 9 - Registering the system and managing subscriptions

Commands: