mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix B. Revision History Revision History Revision 7.1-1 Wed Aug 7 2019 Steven Levine Preparing document for 7.7 GA publication. Revision 6.1-2 Thu Oct 4 2018 Steven Levine Preparing document for 7.6 GA publication. Revision 5.1-2 Wed Mar 14 2018 Steven Levine Preparing document for 7.5 GA publication. Revision 5.1-1 Wed Dec 13 2017 Steven Levine Preparing document for 7.5 Beta publication. Revision 4.1-3 Tue Aug 1 2017 Steven Levine Document version for 7.4 GA publication. Revision 4.1-1 Wed May 10 2017 Steven Levine Preparing document for 7.4 Beta publication. Revision 3.1-2 Mon Oct 17 2016 Steven Levine Version for 7.3 GA publication. Revision 3.1-1 Wed Aug 17 2016 Steven Levine Preparing document for 7.3 Beta publication. Revision 2.1-5 Mon Nov 9 2015 Steven Levine Preparing document for 7.2 GA publication. Revision 2.1-1 Tue Aug 18 2015 Steven Levine Preparing document for 7.2 Beta publication. Revision 1.1-3 Tue Feb 17 2015 Steven Levine Version for 7.1 GA Revision 1.1-1 Thu Dec 04 2014 Steven Levine Version for 7.1 Beta Release Revision 0.1-9 Tue Jun 03 2014 John Ha Version for 7.0 GA Release Revision 0.1-4 Wed Nov 27 2013 John Ha Build for Beta of Red Hat Enterprise Linux 7 Revision 0.1-1 Wed Jan 16 2013 Steven Levine First version for Red Hat Enterprise Linux 7

Commands:
Chapter 1. Overview Version 4 of the Python software development kit is a collection of classes that allows you to interact with the Red Hat Virtualization Manager in Python-based projects. By downloading these classes and adding them to your project, you can access a range of functionality for high-level automation of administrative tasks. Note Version 3 of the SDK is no longer supported. For more information, consult the RHV 4.3 version of this guide . Python 3.7 and async In Python 3.7 and later versions, async is a reserved keyword. You cannot use the async parameter in methods of services that previously supported it, as in the following example, because async=True will cause an error: dc = dc_service.update( types.DataCenter( description='Updated description', ), async=True, ) The solution is to add an underscore to the parameter ( async_ ): dc = dc_service.update( types.DataCenter( description='Updated description', ), async_=True, ) Note This limitation applies only to Python 3.7 and later. Earlier versions of Python do not require this modification. 1.1. Prerequisites To install the Python software development kit, you must have: A system where Red Hat Enterprise Linux 8 is installed. Both the Server and Workstation variants are supported. A subscription to Red Hat Virtualization entitlements. Important The software development kit is an interface for the Red Hat Virtualization REST API. Use the version of the software development kit that corresponds to the version of your Red Hat Virtualization environment. For example, if you are using Red Hat Virtualization 4.3, use V4 Python software development kit. 1.2. Installing the Python Software Development Kit To install the Python software development kit: Enable the repositories that are appropriate for your hardware platform . For example, for x86-64 hardware, enable: # subscription-manager repos \ --enable=rhel-8-for-x86_64-baseos-rpms \ --enable=rhel-8-for-x86_64-appstream-rpms \ --enable=rhv-4.4-manager-for-rhel-8-x86_64-rpms # subscription-manager repos \ --enable=rhel-8-for-x86_64-baseos-eus-rpms \ --enable=rhel-8-for-x86_64-appstream-eus-rpms # subscription-manager release --set=8.6 Install the required packages: # dnf install python3-ovirt-engine-sdk4 The Python software development kit is installed into the Python 3 site-packages directory, and the accompanying documentation and example are installed to /usr/share/doc/python3-ovirt-engine-sdk4 .

Commands:
dc = dc_service.update( types.DataCenter( description='Updated description', ), async=True, )
dc = dc_service.update( types.DataCenter( description='Updated description', ), async_=True, )
subscription-manager repos --enable=rhel-8-for-x86_64-baseos-rpms --enable=rhel-8-for-x86_64-appstream-rpms --enable=rhv-4.4-manager-for-rhel-8-x86_64-rpms subscription-manager repos --enable=rhel-8-for-x86_64-baseos-eus-rpms --enable=rhel-8-for-x86_64-appstream-eus-rpms subscription-manager release --set=8.6
dnf install python3-ovirt-engine-sdk4
Chapter 20. JbodStorage schema reference Used in: KafkaClusterSpec , KafkaNodePoolSpec The type property is a discriminator that distinguishes use of the JbodStorage type from EphemeralStorage , PersistentClaimStorage . It must have the value jbod for the type JbodStorage . Property Description type Must be jbod . string volumes List of volumes as Storage objects representing the JBOD disks array. EphemeralStorage , PersistentClaimStorage array

Commands:
Chapter 7. Developing collections Collections are a distribution format for Ansible content that can include playbooks, roles, modules, and plugins. Red Hat provides Ansible Content Collections on Ansible automation hub that contain both Red Hat Ansible Certified Content and Ansible validated content. If you have installed private automation hub, you can create collections for your organization and push them to private automation hub so that you can use them in job templates in Ansible Automation Platform. You can use collections to package and distribute plug-ins. These plug-ins are written in Python. You can also create collections to package and distribute Ansible roles, which are expressed in YAML. You can also include playbooks and custom plug-ins that are required for these roles in the collection. Typically, collections of roles are distributed for use within your organization.

Commands:
Chapter 2. Differences from upstream OpenJDK 17 Red Hat build of OpenJDK in Red Hat Enterprise Linux contains a number of structural changes from the upstream distribution of OpenJDK. The Microsoft Windows version of Red Hat build of OpenJDK attempts to follow Red Hat Enterprise Linux updates as closely as possible. The following list details the most notable Red Hat build of OpenJDK 17 changes: FIPS support. Red Hat build of OpenJDK 17 automatically detects whether RHEL is in FIPS mode and automatically configures Red Hat build of OpenJDK 17 to operate in that mode. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows. Cryptographic policy support. Red Hat build of OpenJDK 17 obtains the list of enabled cryptographic algorithms and key size constraints from the RHEL system configuration. These configuration components are used by the Transport Layer Security (TLS) encryption protocol, the certificate path validation, and any signed JARs. You can set different security profiles to balance safety and compatibility. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows. Red Hat build of OpenJDK on RHEL dynamically links against native libraries such as zlib for archive format support and libjpeg-turbo , libpng , and giflib for image support. RHEL also dynamically links against Harfbuzz and Freetype for font rendering and management. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows. The src.zip file includes the source for all of the JAR libraries shipped with Red Hat build of OpenJDK. Red Hat build of OpenJDK on RHEL uses system-wide timezone data files as a source for timezone information. Red Hat build of OpenJDK on RHEL uses system-wide CA certificates. Red Hat build of OpenJDK on Microsoft Windows includes the latest available timezone data from RHEL. Red Hat build of OpenJDK on Microsoft Windows uses the latest available CA certificate from RHEL. Additional resources See, Improve system FIPS detection (RHEL Planning Jira) See, Using system-wide cryptographic policies (RHEL documentation)

Commands:
2.4. Configuring max_luns If RAID storage in your cluster presents multiple LUNs (Logical Unit Numbers), each cluster node must be able to access those LUNs. To enable access to all LUNs presented, configure max_luns in the /etc/modprobe.conf file of each node as follows: Open /etc/modprobe.conf with a text editor. Append the following line to /etc/modprobe.conf . Set N to the highest numbered LUN that is presented by RAID storage. For example, with the following line appended to the /etc/modprobe.conf file, a node can access LUNs numbered as high as 255: Save /etc/modprobe.conf . Run mkinitrd to rebuild initrd for the currently running kernel as follows. Set the kernel variable to the currently running kernel: For example, the currently running kernel in the following mkinitrd command is 2.6.9-34.0.2.EL: Note You can determine the currently running kernel by running uname -r . Restart the node.

Commands:
options scsi_mod max_luns= N
options scsi_mod max_luns=255
cd /boot mkinitrd -f -v initrd- kernel .img kernel
mkinitrd -f -v initrd-2.6.9-34.0.2.EL.img 2.6.9-34.0.2.EL
2.2. Support Limits and Removals Read this section to understand which technologies are no longer supported, or support reduced functionality, in Red Hat Gluster Storage 3.5. gluster-swift (Object Store) Using Red Hat Gluster Storage as an object store for Red Hat OpenStack Platform is no longer supported. gstatus Red Hat Gluster Storage 3.5 does not support gstatus. Heketi for standalone Red Hat Gluster Storage Heketi is supported only for use with OpenShift Container Storage. It is not supported for general use with Red Hat Gluster Storage. Nagios Monitoring Red Hat Gluster Storage 3.5 does not support monitoring using Nagios. Red Hat Gluster Storage Web Administration is now the recommended monitoring tool for Red Hat Storage Gluster clusters. Red Hat Atomic Host Red Hat Atomic Host is not supported for use with Red Hat Gluster Storage 3.5. Red Hat Gluster Storage Console Red Hat Gluster Storage Console is not supported for use with Red Hat Gluster Storage 3.5. Red Hat Gluster Storage Web Administration is now the recommended monitoring tool for Red Hat Storage Gluster clusters. Virtual Disk Optimizer (VDO) Virtual Disk Optimizer (VDO) volumes are only supported as part of a Red Hat Hyperconverged Infrastructure for Virtualization 2.0 deployment. VDO is not supported with other Red Hat Gluster Storage deployments.

Commands:
20.2.4. Using a Prepared FCP-attached SCSI Disk Double-click Load . In the dialog box that follows, select SCSI as the Load type . As Load address fill in the device number of the FCP channel connected with the SCSI disk. As World wide port name fill in the WWPN of the storage system containing the disk as a 16-digit hexadecimal number. As Logical unit number fill in the LUN of the disk as a 16-digit hexadecimal number. As Boot program selector fill in the number corresponding the zipl boot menu entry that you prepared for booting the Red Hat Enterprise Linux installer. Leave the Boot record logical block address as 0 and the Operating system specific load parameters empty. Click the OK button.

Commands:
7.7. Importing Templates 7.7.1. Importing a Template into a Data Center Note The export storage domain is deprecated. Storage data domains can be unattached from a data center and imported to another data center in the same environment, or in a different environment. Virtual machines, floating virtual disks, and templates can then be uploaded from the imported storage domain to the attached data center. See the Importing Existing Storage Domains section in the Red Hat Virtualization Administration Guide for information on importing storage domains. Import templates from a newly attached export domain. This procedure requires access to the Administration Portal. Importing a Template into a Data Center Click Storage Domains and select the newly attached export domain. Click the domain name to go to the details view. Click the Template Import tab and select a template. Click Import . Use the drop-down lists to select the Target Cluster and CPU Profile . Select the template to view its details, then click the Disks tab and select the Storage Domain to import the template into. Click OK . If the Import Template Conflict window appears, enter a New Name for the template, or select the Apply to all check box and enter a Suffix to add to the cloned Templates . Click OK . Click Close . The template is imported into the destination data center. This can take up to an hour, depending on your storage hardware. You can view the import progress in the Events tab. Once the importing process is complete, the templates will be visible in Compute Templates . The templates can create new virtual machines, or run existing imported virtual machines based on that template. 7.7.2. Importing a Virtual Disk from an OpenStack Image Service as a Template Virtual disks managed by an OpenStack Image Service can be imported into the Red Hat Virtualization Manager if that OpenStack Image Service has been added to the Manager as an external provider. This procedure requires access to the Administration Portal. Click Storage Domains and select the OpenStack Image Service domain. Click the storage domain name to go to the details view. Click the Images tab and select the image to import. Click Import . Note If you are importing an image from a Glance storage domain, you have the option of specifying the template name. OpenStack Glance is now deprecated. This functionality will be removed in a later release. Select the Data Center into which the virtual disk will be imported. Select the storage domain in which the virtual disk will be stored from the Domain Name drop-down list. Optionally, select a Quota to apply to the virtual disk. Select the Import as Template check box. Select the Cluster in which the virtual disk will be made available as a template. Click OK . The image is imported as a template and is displayed in the Templates tab. You can now create virtual machines based on the template.

Commands:
4.5. One-Time Passwords One-time password (OTP) is a password that is valid for only one authentication session; it becomes invalid after use. Unlike traditional static passwords that stay the same for a longer period of time, OTPs keep changing. OTPs are used as part of two-factor authentication: the first step requires the user to authenticate with a traditional static password, and the second step prompts for an OTP issued by a recognized authentication token. Authentication using an OTP combined with a static password is considered safer than authentication using a static password alone. Because an OTP can only be used for successful authentication once, even if a potential intruder intercepts the OTP during login, the intercepted OTP will already be invalid by that point. One-Time Passwords in Red Hat Enterprise Linux Red Hat Identity Management supports OTP authentication for IdM users. For more information, see the One-Time Passwords section in the Linux Domain Identity, Authentication, and Policy Guide .

Commands:
Chapter 4. Deploying functions You can deploy your functions to the cluster by using the kn func tool. 4.1. Deploying a function You can deploy a function to your cluster as a Knative service by using the kn func deploy command. If the targeted function is already deployed, it is updated with a new container image that is pushed to a container image registry, and the Knative service is updated. Prerequisites The OpenShift Serverless Operator and Knative Serving are installed on the cluster. You have installed the Knative ( kn ) CLI. You have created a project or have access to a project with the appropriate roles and permissions to create applications and other workloads in OpenShift Container Platform. You must have already created and initialized the function that you want to deploy. Procedure Deploy a function: USD kn func deploy [-n <namespace> -p <path> -i <image>] Example output Function deployed at: http://func.example.com If no namespace is specified, the function is deployed in the current namespace. The function is deployed from the current directory, unless a path is specified. The Knative service name is derived from the project name, and cannot be changed using this command. Note You can create a serverless function with a Git repository URL by using Import from Git or Create Serverless Function in the +Add view of the Developer perspective.

Commands:
kn func deploy [-n <namespace> -p <path> -i <image>]
Function deployed at: http://func.example.com
Chapter 3. Deprecated functionalities This section lists deprecated functionalities in Red Hat Developer Hub 1.3. 3.1. spec.application.image , spec.application.replicas and spec.application.imagePullSecrets fields are deprecated spec.application.image , spec.application.replicas and spec.application.imagePullSecrets fields are deprecated in v1alpha2 in favour of spec.deployment . Procedure To update your Developer Hub Operation configuration: Remove the spec.application.image , spec.application.replicas and spec.application.imagePullSecrets fields from the Operator configuration. For example: spec: application: replicas: 2 # &lt;1&gt; imagePullSecrets: # &lt;2&gt; - my-secret-name image: quay.io/my/my-rhdh:latest # &lt;3&gt; <1> Replica count. <2> Array of image pull secrets names. <3> Image name. Replace the removed fields with new spec.deployment fields. For example: spec: deployment: patch: spec: replicas: 2 # &lt;1&gt; imagePullSecrets: # &lt;2&gt; - name: my-secret-name template: metadata: labels: my: true spec: containers: - name: backstage-backend image: quay.io/my/my-rhdh:latest # &lt;3&gt; <1> Replica count. <2> Array of image pull secrets names. <3> Image name. Additional resources RHIDP-1138

Commands:
spec: application: replicas: 2 # &lt;1&gt; imagePullSecrets: # &lt;2&gt; - my-secret-name image: quay.io/my/my-rhdh:latest # &lt;3&gt;
spec: deployment: patch: spec: replicas: 2 # &lt;1&gt; imagePullSecrets: # &lt;2&gt; - name: my-secret-name template: metadata: labels: my: true spec: containers: - name: backstage-backend image: quay.io/my/my-rhdh:latest # &lt;3&gt;
Chapter 1. 2023.Q4 release notes Release scope This release includes the following new clients: Red Hat build of Apache Qpid Proton DotNet Red Hat build of Apache Qpid ProtonJ2 View all the clients from the Product Documentation for Red Hat AMQ Clients page. This release does not include a C++ or Python client. If you require these clients, see: Using the AMQ C++ Client 2.11 Using the AMQ Python Client 2.11 Documentation structure Starting in 2023.Q4, documentation for each Red Hat AMQ client is versioned and published independently. For example, if you navigate to Red Hat build of Rhea page, all versions of that client are available to browse. Removed AMQ Clients The following clients are no longer available: AMQ Ruby Client Use the 2.11 Client as a workaround. AMQ OpenWire JMS client Migrate to AMQ JMS or AMQ Core Protocol JMS. The CMS and NMS APIs Users of the CMS API can migrate to AMQ C++, and users of the NMS API can migrate to AMQ .NET. The CMS and NMS APIs might have reduced functionality in AMQ 7. Fixed Issues For a complete list of issues that have been fixed in this release, see the following link for each client. If the client is not listed, then no issues were fixed for that particular client. Alternatively, see AMQ Clients Resolved Issues Component URL Red Hat build of Rhea Red Hat build of Rhea 2023.Q4 Fixed Issues Red Hat build of Apache Qpid JMS Red Hat build of Apache Qpid JMS 2023.Q4 Fixed Issues AMQ Spring Boot Starter AMQ Spring Boot Starter 2023.Q4 Fixed Issues

Commands:
14.7.6. Suspending the Host Physical Machine The nodesuspend command puts the host physical machine into a system-wide sleep state similar to that of Suspend-to-RAM (s3), Suspend-to-Disk (s4), or Hybrid-Suspend and sets up a Real-Time-Clock to wake up the node after the duration that is set has past. The --target option can be set to either mem , disk , or hybrid . These options indicate to set the memory, disk, or combination of the two to suspend. Setting the --duration instructs the host physical machine to wake up after the set duration time has run out. It is set in seconds. It is recommended that the duration time be longer than 60 seconds.

Commands:
virsh nodesuspend disk 60
Chapter 4. Customer Portal Labs Relevant For Migration Red Hat Customer Portal Labs are tools designed to help you improve performance, troubleshoot issues, identify security problems, and optimize configuration. This appendix provides an overview of Red Hat Customer Portal Labs relevant to migration. All Red Hat Customer Portal Labs are available at http://access.redhat.com/labs/ . Red Hat Enterprise Linux Upgrade Helper The Red Hat Enterprise Linux Update Helper is a tool that helps you upgrade your Red Hat Enterprise Linux from version 6.5/6.6/6.7/6.8/6.9 to version 7.x. The only information that you need to provide is your upgrade path. This application shows you: the basic steps to upgrade Red Hat Enterprise Linux extra steps that prevent known issues specific to your upgrade scenario This application supports the following upgrade paths: 6.5 to 7.4 6.6 to 7.4 6.7 to 7.4 6.8 to 7.4 6.9 to 7.4 Product Life Cycle Checker The Product Life Cycle Checker is a tool for viewing Red Hat products' life-cycle information, including General Availability, End of Support, and End of Life. With this tool, it is possible to choose multiple products and view their dates.

Commands: