mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 111. ReplicasChangeStatus schema reference Used in: KafkaTopicStatus Property Property type Description targetReplicas integer The target replicas value requested by the user. This may be different from .spec.replicas when a change is ongoing. state string (one of [ongoing, pending]) Current state of the replicas change operation. This can be pending , when the change has been requested, or ongoing , when the change has been successfully submitted to Cruise Control. message string Message for the user related to the replicas change request. This may contain transient error messages that would disappear on periodic reconciliations. sessionId string The session identifier for replicas change requests pertaining to this KafkaTopic resource. This is used by the Topic Operator to track the status of ongoing replicas change operations.

Commands:
Chapter 5. Uninstalling Server and Replica Containers This chapter describes how you can uninstall an Identity Management server or replica container. 5.1. Uninstalling a Server or Replica Container This procedure shows how to uninstall an Identity Management server or replica container and make sure the server or replica is properly removed from the topology. Procedure To ensure that a replica container belonging to an existing topology is properly removed from that topology, use the ipa server-del <container-host-name> command on any enrolled host. This step is necessary because the atomic uninstall command does not: Perform checks to prevent disconnected domain level 1 topology or the removal of the last certificate authority (CA), key recovery authority (KRA), or DNS server Remove the replica container from the existing topology Use the atomic uninstall command, and include the container name and image name: 5.2. Steps After Uninstalling You can find a backup of the container's mounted data directory under /var/lib/<container_name>.backup.<timestamp> . If you need to create a new container, the backup enables you to reuse the persistent data stored in the volume.

Commands:
atomic uninstall --name <container_name> rhel7/ipa-server
Chapter 3. Deploying applications with OpenShift Client You can use OpenShift Client (oc) for application deployment. You can deploy applications from source or from binary artifacts. 3.1. Deploying applications from source using oc The following example demonstrates how to deploy the example-app application using oc , which is in the app folder on the dotnet-8.0 branch of the redhat-developer/s2i-dotnetcore-ex GitHub repository: Procedure Create a new OpenShift project: Add the ASP.NET Core application: Track the progress of the build: View the deployed application once the build is finished: The application is now accessible within the project. Optional : Make the project accessible externally: Obtain the shareable URL: 3.2. Deploying applications from binary artifacts using oc You can use .NET Source-to-Image (S2I) builder image to build applications using binary artifacts that you provide. Prerequisites Published application. For more information, see Procedure Create a new binary build: Start the build and specify the path to the binary artifacts on your local machine: Create a new application:

Commands:
oc new-project sample-project
oc new-app --name= example-app 'dotnet:8.0-ubi8~https://github.com/redhat-developer/s2i-dotnetcore-ex#dotnet-8.0' --build-env DOTNET_STARTUP_PROJECT=app
oc logs -f bc/ example-app
oc logs -f dc/ example-app
oc expose svc/ example-app
oc get routes
oc new-build --name= my-web-app dotnet:8.0-ubi8 --binary=true
oc start-build my-web-app --from-dir= bin/Release/net8.0/publish
oc new-app my-web-app
Chapter 13. Logging in to the Directory Server by using the web console The web console is a browser-based graphical user interface (GUI) that you can use for performing administrative tasks. The Directory Server package automatically installs the Directory Server user interface for the web console. Prerequisites You have permissions to access the web console. Procedure Access the web console by using the following URL in your browser: Log in as a user with sudo privileges. Select the Red Hat Directory Server entry. Additional resources Logging in to the RHEL web console .

Commands:
https://<directory_server_host>:9090
Chapter 24. Providing a custom class to your business application in Business Central To interact with Red Hat AMQ Streams, your business application requires a custom class in the following cases: You want to use a custom message format for sending or receiving messages using message events. You want to use a custom serializer class for the KafkaPublishMessages custom task. To use a custom class in your business application, use Business Central to upload the source code and configure the class. Alternatively, if you deploy your application on SpringBoot, you can compile the classes separately and include them in the class path. In this case, do not complete this procedure. Prerequisites You are logged in to Business Central and have permission to edit business processes. You created a project for your business process. Procedure Prepare Java source files with the required custom classes, for example, MyCustomSerializer . Use the package name for your space and project, for example, com.myspace.test . In Business Central, enter your project and click the Settings Dependencies tab. In the Dependencies field, add dependencies that your custom classes require, for example, org.apache.kafka.kafka-clients , as a comma-separated list. Click the Assets tab. For each of the class source files, complete the following steps: Click Import Asset . In the Please select a file to upload field, select the location of the Java source file for the custom serializer class. Click Ok .

Commands:
Chapter 1. Prerequisites Red Hat Enterprise Linux (RHEL) 9 To obtain the latest version of Red Hat Enterprise Linux (RHEL) 9, see Download Red Hat Enterprise Linux . For installation instructions, see the Product Documentation for Red Hat Enterprise Linux 9 . An active subscription to Red Hat Two or more virtual CPUs 4 GB or more of RAM Approximately 30 GB of disk space on your test system, which can be broken down as follows: Approximately 10 GB of disk space for the Red Hat Enterprise Linux (RHEL) operating system. Approximately 10 GB of disk space for Docker storage for running three containers. Approximately 10 GB of disk space for Red Hat Quay local storage. Note CEPH or other local storage might require more memory. More information on sizing can be found at Quay 3.x Sizing Guidelines . The following architectures are supported for Red Hat Quay: amd64/x86_64 s390x ppc64le 1.1. Installing Podman This document uses Podman for creating and deploying containers. For more information on Podman and related technologies, see Building, running, and managing Linux containers on Red Hat Enterprise Linux 9 . Important If you do not have Podman installed on your system, the use of equivalent Docker commands might be possible, however this is not recommended. Docker has not been tested with Red Hat Quay 3, and will be deprecated in a future release. Podman is recommended for highly available, production quality deployments of Red Hat Quay 3. Use the following procedure to install Podman. Procedure Enter the following command to install Podman: USD sudo yum install -y podman Alternatively, you can install the container-tools module, which pulls in the full set of container software packages: USD sudo yum module install -y container-tools

Commands:
sudo yum install -y podman
sudo yum module install -y container-tools
7.101. lftp 7.101.1. RHBA-2015:0793 - lftp bug fix update Updated lftp packages that fix several bugs are now available for Red Hat Enterprise Linux 6. LFTP is a file transfer utility for File Transfer Protocol (FTP), Secure Shell File Transfer Protocol (SFTP), Hypertext Transfer Protocol (HTTP), and other commonly used protocols. It uses the readline library for input, and provides support for bookmarks, built-in monitoring, job control, and parallel transfer of multiple files at the same time. Bug Fixes BZ# 619777 Previously, downloaded files with duplicated names were not renamed even when the "xfer:auto-rename" and "xfer:clobber" options were enabled. To fix this bug, the condition for renaming downloaded files has been modified and they are now renamed as expected. BZ# 674875 Prior to this update, the lftp manual page did not contain information on the "xfer:auto-rename" option. The option has been documented and added to the page, where it is now available to users. BZ# 732863 Due to a bug in error checking code, lftp could fail to connect to a remote host with an IPv6 address if the local host had only IPv4 connectivity, but the remote host domain name was resolved also to IPv6 addresses. With this update, the code has been amended, and the connectivity problems no longer occur in this situation. BZ# 842322 Due to an incorrect evaluation of the length of an uploaded file, the lftp tool became unresponsive after a file transfer in ASCII mode. With this update, the volume of transferred data is recognized correctly and the lftp program no longer hangs in this scenario. BZ# 928307 When running lftp in mirror mode on a website, lftp terminated with an error in cases of HTTP 302 redirection. To fix this bug, lftp has been amended and now successfully proceeds to the new location in such situations. BZ# 1193617 With the "cmd:fail-exit" option enabled, lftp could terminate unexpectedly when any command was executed after the "help" command. With this update, the "help" command has been amended to return correct return code, and lftp no longer exits in this scenario. Users of lftp are advised to upgrade to these updated packages, which fix these bugs.

Commands:
4.271. rhnlib 4.271.1. RHBA-2011:1665 - rhnlib bug fix update An updated rhnlib package that fixes various bugs is now available for Red Hat Enterprise Linux 6. The rhnlib package consists of a collection of Python modules used by the Red Hat Network (RHN) software. Bug Fixes BZ# 688095 Due to an error in the rhnlib code, network operations would have become unresponsive when an HTTP connection to Red Hat Network (RHN) or RHN Satellite became idle. The code has been modified to use timeout for HTTP connections. Network operations are now terminated after predefined time interval and can be restarted. BZ# 730744 Prior to this update, programs that used rhnlib were not able to connect to RHN or RHN Satellite using an IPv6 address. The code has been modified to correct this issue, and rhnlib-based applications are now able to connect to RHN or RHN Satellite without any problems with IPv6 address resolution. All users of rhnlib are advised to upgrade to this updated package, which resolves these issues.

Commands:
Chapter 13. Customizing GNOME Desktop Features This chapter mentions three key desktop features. After reading, you will know how to quickly terminate the X server by default for all users, how to enable the Compose key or how to disable command line access for the users. To make sure the changes you have made take effect, you need to update the dconf utility. The users will experience the difference when they log out and log in again. 13.1. Allowing and Disallowing Online Accounts The GNOME Online Accounts (GOA) are used for setting personal network accounts which are then automatically integrated with the GNOME Desktop and applications. The user can add their online accounts, such as Google, Facebook, Flickr, ownCloud, and others using the Online Accounts application. As a system administrator, you can enable all online accounts; selectively enable a few online accounts; disable all online accounts. Procedure 13.1. Configuring Online Accounts If you do not have the gnome-online-accounts package on your system, install it by running the following command as root: Create a keyfile for the local database in /etc/dconf/db/local.d/ goa , which contains the following configuration: For selectively enabling a few providers only: For disabling all providers: For allowing all available providers: Lock down the settings to prevent users from overriding them. If it does not exist, create a new directory named /etc/dconf/db/local.d/locks/ . Create a new file in /etc/dconf/db/local.d/locks/goa with the following contents: Update the system databases for the changes to take effect: Users must log out and back in again before the system-wide settings take effect.

Commands:
yum install gnome-online-accounts
[org/gnome/online-accounts] whitelisted-providers= ['google', 'facebook']
[org/gnome/online-accounts] whitelisted-providers= ['']
[org/gnome/online-accounts] whitelisted-providers= ['all']
Prevent users from changing values for the following key: /org/gnome/online-accounts
dconf update
16.17.4. Create LVM Logical Volume Important LVM initial set up is not available during text-mode installation. If you need to create an LVM configuration from scratch, press Alt + F2 to use a different virtual console, and run the lvm command. To return to the text-mode installation, press Alt + F1 . Logical Volume Management (LVM) presents a simple logical view of underlying physical storage space, such as a hard drives or LUNs. Partitions on physical storage are represented as physical volumes that can be grouped together into volume groups . Each volume group can be divided into multiple logical volumes , each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions that can span multiple physical disks. To read more about LVM, refer to the Red Hat Enterprise Linux Deployment Guide . Note, LVM is only available in the graphical installation program. LVM Physical Volume Choose this option to configure a partition or device as an LVM physical volume. This option is the only choice available if your storage does not already contain LVM Volume Groups. This is the same dialog that appears when you add a standard partition - refer to Section 16.17.2, "Adding Partitions" for a description of the available options. Note, however, that File System Type must be set to physical volume (LVM) Figure 16.43. Create an LVM Physical Volume Make LVM Volume Group Choose this option to create LVM volume groups from the available LVM physical volumes, or to add existing logical volumes to a volume group. Figure 16.44. Make LVM Volume Group To assign one or more physical volumes to a volume group, first name the volume group. Then select the physical volumes to be used in the volume group. Finally, configure logical volumes on any volume groups using the Add , Edit and Delete options. You may not remove a physical volume from a volume group if doing so would leave insufficient space for that group's logical volumes. Take for example a volume group made up of two 5 GB LVM physical volume partitions, which contains an 8 GB logical volume. The installer would not allow you to remove either of the component physical volumes, since that would leave only 5 GB in the group for an 8 GB logical volume. If you reduce the total size of any logical volumes appropriately, you may then remove a physical volume from the volume group. In the example, reducing the size of the logical volume to 4 GB would allow you to remove one of the 5 GB physical volumes. Make Logical Volume Choose this option to create an LVM logical volume. Select a mount point, file system type, and size (in MB) just as if it were a standard disk partition. You can also choose a name for the logical volume and specify the volume group to which it will belong. Figure 16.45. Make Logical Volume

Commands:
9.14. Choosing a Disk Encryption Passphrase If you selected the Encrypt System option, the installer prompts you for a passphrase with which to encrypt the partitions on the system. Partitions are encrypted using the Linux Unified Key Setup - refer to Appendix C, Disk Encryption for more information. Figure 9.38. Enter passphrase for encrypted partition Choose a passphrase and type it into each of the two fields in the dialog box. You must provide this passphrase every time that the system boots. Warning If you lose this passphrase, any encrypted partitions and the data on them will become completely inaccessible. There is no way to recover a lost passphrase. Note that if you perform a kickstart installation of Red Hat Enterprise Linux, you can save encryption passphrases and create backup encryption passphrases during installation. Refer to Section C.3.2, "Saving Passphrases" and Section C.3.3, "Creating and Saving Backup Passphrases" .

Commands:
2.41. RHEA-2011:0585 - new package: spice-protocol A new spice-protocol package is now available for Red Hat Enterprise Linux 6. The spice-protocol package contains header files that describe the SPICE protocol and the QXL para-virtualized graphics card. Spice-protocol is needed to build newer versions of the spice-client and spice-server packages. This enhancement update adds the spice-protocol package to Red Hat Enterprise Linux 6. (BZ# 662992 ) Users who wish to build SPICE from source are advised to install this new package.

Commands:
function::cmdline_args Name function::cmdline_args - Fetch command line arguments from current process Synopsis Arguments n First argument to get (zero is the command itself) m Last argument to get (or minus one for all arguments after n) delim String to use to delimit arguments when more than one. General Syntax cmdline_args:string(n:long, m:long, delim:string) Description Returns arguments from the current process starting with argument number n, up to argument m. If there are less than n arguments, or the arguments cannot be retrieved from the current process, the empty string is returned. If m is smaller than n then all arguments starting from argument n are returned. Argument zero is traditionally the command itself.

Commands:
function cmdline_args:string(n:long,m:long,delim:string)
Chapter 10. Hardware Enablement Support added for the CAPI flash block adapter The Coherent Accelerator Processor Interface (CAPI) is a technology that enables I/O adapters to coherently access host memory, and thus ensures improved performance. This update adds the cxlflash driver, which provides support for IBM's CAPI flash block adapter. (BZ#1182021) MMC kernel rebased to version 4.5 With this update, the Multimedia Card (MMC) kernel subsystem has been upgraded to upstream version 4.5, which fixes multiple bugs and also enables the Red Hat Enterprise Linux 7 kernel to use the embedded MMC (eMMC) interface version 5.0. In addition, the update improves the suspend and resume functionality of MMC devices, as well as their general stability. (BZ#1297039) iWarp mapper service added This update adds support for the internet Wide Area RDMA Protocol (iWARP) mapper to Red Hat Enterprise Linux 7. The iWARP mapper is a user-space service that enables the following iWARP drivers to claim TCP ports using the standard socket interface: Intel i40iw NES Chelsio cxgb4 Note that both the iw_cm and ib_core kernel modules need to be loaded for the iWarp mapper service (iwpmd) to start successfully. (BZ#1331651) New package: memkind This update adds the memkind package, which provides a user-extensible heap manager library, built as an extension of the jemalloc memory allocator. This library enables partitioning of the memory heap located between memory types that are defined when the operating system policies are applied to virtual address ranges. In addition, memkind enables the user to control memory partition features and allocate memory with a specified set of memory features selected. (BZ#1210910) Per-port MSI-X support for the AHCI driver The driver for the Advanced Host Controlled Interface (AHCI) has been updated for per-port message-signaled interrupt (MSI-X) vectors. Note that this applies only to controllers that support the feature. (BZ#1286946) Runtime Instrumentation for IBM z Systems is now fully supported The Runtime Instrumentation feature, previously available as a Technology Preview, is now fully supported in Red Hat Enterprise Linux 7 on IBM z Systems. Runtime Instrumentation enables advanced analysis and execution for a number of user-space applications available with the IBM zEnterprise EC12 system. (BZ#1115947)

Commands:
Chapter 7. Hardware Enablement cpuid is now available With this update, the cpuid utility is available in Red Hat Enterprise Linux. This utility dumps detailed information about the CPU(s) gathered from the CPUID instruction, and also determines the exact model of CPU(s). It supports Intel, AMD, and VIA CPUs. (BZ#1316998) Support for RealTek RTS5250S SD4.0 Controllers The Realtek RTS5205 card reader controllers have been added to the kernel. (BZ#1167938)

Commands:
Chapter 1. Overview of AMQ Interconnect AMQ Interconnect is a lightweight AMQP message router for building scalable, available, and performant messaging networks. 1.1. Key features You can use AMQ Interconnect to flexibly route messages between any AMQP-enabled endpoints, including clients, servers, and message brokers. AMQ Interconnect provides the following benefits: Connects clients and message brokers into an internet-scale messaging network with uniform addressing Supports high-performance direct messaging Uses redundant network paths to route around failures Streamlines the management of large deployments 1.2. Supported standards and protocols AMQ Interconnect supports the following industry-recognized standards and network protocols: Version 1.0 of the Advanced Message Queueing Protocol (AMQP) Modern TCP with IPv6 Note The details of distributed transactions (XA) within AMQP are not provided in the 1.0 version of the specification. AMQ Interconnect does not support XA transactions. Additional resources OASIS AMQP 1.0 Specification . 1.3. Supported configurations AMQ Interconnect is supported on Red Hat Enterprise Linux 6, 7, and 8. See Red Hat AMQ 7 Supported Configurations for more information. 1.4. Document conventions In this document, sudo is used for any command that requires root privileges. You should always exercise caution when using sudo , as any changes can affect the entire system. For more information about using sudo , see The sudo Command .

Commands:
Introduction to OpenShift Dedicated OpenShift Dedicated 4 An overview of OpenShift Dedicated architecture Red Hat OpenShift Documentation Team

Commands:
oc run ip-lookup --image=busybox -i -t --restart=Never --rm -- /bin/sh -c "/bin/nslookup -type=a myip.opendns.com resolver1.opendns.com | grep -E 'Address: [0-9.]+'"
spec: nodeSelector: role: worker
oc adm policy remove-cluster-role-from-group self-provisioner system:authenticated:oauth
oc adm policy add-cluster-role-to-group self-provisioner system:authenticated:oauth