mtpti5iD/redhat-docs_dataset huggingface dataset:
14.4. OpenSSH Clients To connect to an OpenSSH server from a client machine, you must have the openssh-clients and openssh packages installed (see Section 8.2.4, "Installing Packages" for more information on how to install new packages in Red Hat Enterprise Linux). 14.4.1. Using the ssh Utility The ssh utility allows you to log in to a remote machine and execute commands there. It is a secure replacement for the rlogin , rsh , and telnet programs. Similarly to the telnet command, log in to a remote machine by using the following command: ssh hostname For example, to log in to a remote machine named penguin.example.com , type the following at a shell prompt: This will log you in with the same user name you are using on the local machine. If you want to specify a different user name, use a command in the following form: ssh username @ hostname For example, to log in to penguin.example.com as john , type: The first time you initiate a connection, you will be presented with a message similar to this: Type yes to confirm. You will see a notice that the server has been added to the list of known hosts, and a prompt asking for your password: Important Update the host key of an SSH server if the key changes. The client notifies the user that the connection cannot proceed until the server's host key is deleted from the ~/.ssh/known_hosts file. Contact the system administrator of the SSH server to verify the server is not compromised, then remove the line with the name of the remote machine at the beginning. After entering the password, you will be provided with a shell prompt for the remote machine. Alternatively, the ssh program can be used to execute a command on the remote machine without logging in to a shell prompt: ssh [ username @ ] hostname command For example, the /etc/redhat-release file provides information about the Red Hat Enterprise Linux version. To view the contents of this file on penguin.example.com , type: After you enter the correct password, the user name will be displayed, and you will return to your local shell prompt.

Commands:
~]USD ssh penguin.example.com
~]USD ssh john@penguin.example.com
The authenticity of host 'penguin.example.com' can't be established. RSA key fingerprint is 94:68:3a:3a:bc:f3:9a:9b:01:5d:b3:07:38:e2:11:0c. Are you sure you want to continue connecting (yes/no)?
Warning: Permanently added 'penguin.example.com' (RSA) to the list of known hosts. john@penguin.example.com's password:
~]USD ssh john@penguin.example.com cat /etc/redhat-release john@penguin.example.com's password: Red Hat Enterprise Linux Server release 6.2 (Santiago)
Chapter 11. Viewing threads You can view and monitor the state of threads. Procedure Click the Runtime tab and then the Threads subtab. The Threads page lists active threads and stack trace details for each thread. By default, the thread list shows all threads in descending ID order. To sort the list by increasing ID, click the ID column label. Optionally, filter the list by thread state (for example, Blocked ) or by thread name. To drill down to detailed information for a specific thread, such as the lock class name and full stack trace for that thread, in the Actions column, click More .

Commands:
3.2. Procedure Result Caching Cached virtual procedure results are used automatically when a matching set of parameter values is detected for the same procedure execution. Usage of the cached results may be bypassed when used with the OPTION NOCACHE clause. To indicate that a virtual procedure is to be cached, its definition must include a Cache Hint. Results will be cached with the default ttl. The pref_mem and ttl options of the cache hint may also be used for procedure caching. Procedure results cache keys include the input parameter values. To prevent one procedure from filling the cache, at most 256 cache keys may be created per procedure per VDB. A cached procedure will always produce all of its results prior to allowing those results to be consumed and placed in the cache. This differs from normal procedure execution which in some situations allows the returned results to be consumed in a streaming manner.

Commands:
/*+ cache */ BEGIN END
Chapter 7. Common Features 7.1. Element Property Icons Note Throughout this guide, the elements of each resource are detailed in tables. These tables include a properties column, displaying icons depicting element properties. The meaning of these icons is shown in Table 7.1, "Element property icons" . Table 7.1. Element property icons Property Description Icon Required for creation These elements must be included in the client-provided representation of a resource on creation, but are not mandatory for an update of a resource. Non-updatable These elements cannot have their value changed when updating a resource. Include these elements in a client-provided representation on update only if their values are not altered by the API user. If altered, the API reports an error. Read-only These elements are read-only. Values for read-only elements are not created or modified.

Commands:
17.4. RAID Support in the Installer The Anaconda installer will automatically detect any hardware and firmware RAID sets on a system, making them available for installation. Anaconda also supports software RAID using mdraid , and can recognize existing mdraid sets. Anaconda provides utilities for creating RAID sets during installation; however, these utilities only allow partitions (as opposed to entire disks) to be members of new sets. To use an entire disk for a set, simply create a partition on it spanning the entire disk, and use that partition as the RAID set member. When the root file system uses a RAID set, Anaconda will add special kernel command-line options to the bootloader configuration telling the initrd which RAID set(s) to activate before searching for the root file system. For instructions on configuring RAID during installation, refer to the Red Hat Enterprise Linux 6 Installation Guide .

Commands:
Chapter 1. Data Grid Operator Data Grid Operator provides operational intelligence and reduces management complexity for deploying Data Grid on Kubernetes and Red Hat OpenShift. 1.1. Data Grid Operator deployments When you install Data Grid Operator, it extends the Kubernetes API with Custom Resource Definitions (CRDs) for deploying and managing Data Grid clusters on Red Hat OpenShift. To interact with Data Grid Operator, OpenShift users apply Custom Resources (CRs) through the OpenShift Web Console or oc client. Data Grid Operator listens for Infinispan CRs and automatically provisions native resources, such as StatefulSets and Secrets, that your Data Grid deployment requires. Data Grid Operator also configures Data Grid services according to the specifications in Infinispan CRs, including the number of pods for the cluster and backup locations for cross-site replication. Figure 1.1. Custom resources 1.2. Cluster management A single Data Grid Operator installation can manage multiple clusters with different Data Grid versions in separate namespaces. Each time a user applies CRs to modify the deployment, Data Grid Operator applies the changes globally to all Data Grid clusters. Figure 1.2. Operator-managed clusters 1.3. Resource reconciliation Data Grid Operator reconciles custom resources such as the Cache CR with resources on your Data Grid cluster. Bidirectional reconciliation synchronizes your CRs with changes that you make to Data Grid resources through the Data Grid Console, command line interface (CLI), or other client application and vice versa. For example if you create a cache through the Data Grid Console then Data Grid Operator adds a declarative Kubernetes representation. To perform reconciliation Data Grid Operator creates a listener pod for each Data Grid cluster that detects modifications for Infinispan resources. Notes about reconciliation When you create a cache through the Data Grid Console, CLI, or other client application, Data Grid Operator creates a corresponding Cache CR with a unique name that conforms to the Kubernetes naming policy. Declarative Kubernetes representations of Data Grid resources that Data Grid Operator creates with the listener pod are linked to Infinispan CRs. Deleting Infinispan CRs removes any associated resource declarations.

Commands:
Chapter 14. OpenShift by Red Hat OpenShift by Red Hat is a Platform as a Service (PaaS) that enables developers to build and deploy web applications. OpenShift provides a wide selection of programming languages and frameworks including Java, Ruby, and PHP. It also provides integrated developer tools to support the application life cycle, including Eclipse integration, JBoss Developer Studio, and Jenkins. OpenShift uses an open source ecosystem to provide a platform for mobile applications, database services, and more. [13] 14.1. OpenShift and SELinux SELinux provides better security control over applications that use OpenShift because all processes are labeled according to the SELinux policy. Therefore, SELinux protects OpenShift from possible malicious attacks within different gears running on the same node. See the Dan Walsh's presentation for more information about SELinux and OpenShift. [13] To learn more about OpenShift, see OpenShift Enterprise documentation and OpenShift Online documentation .

Commands:
Chapter 2. Start here with OpenShift Virtualization Use the following tables to find content to help you learn about and use OpenShift Virtualization. 2.1. Cluster administrator Learn Plan Deploy Additional resources Learn about OpenShift Virtualization Configuring your cluster for OpenShift Virtualization Updating your node network configuration Getting Support Learn more about OpenShift Container Platform Plan storage for virtual machine disks Configuring CSI volumes Learn about virtual machine live migration Installing OpenShift Virtualization using the OpenShift Virtualization console or CLI Learn about node maintenance 2.2. Virtualization administrator Learn Deploy Manage Use Learn about OpenShift Virtualization Connecting virtual machines to the default pod network for virtual machines and external networks Enabling the virtctl client Importing virtual machines with the Migration Toolkit for containers Learn about storage features for virtual machine disks Customizing the storage profile Using the CLI tools Using live migration Creating boot sources and attaching them to templates Viewing logs and events Updating boot source templates Monitoring virtual machine health 2.3. Virtual machine administrator / developer Learn Use Manage Additional resources Learn about OpenShift Virtualization Enabling the virtctl client Viewing logs and events Getting Support Creating virtual machines Monitoring virtual machine health Managing virtual machines instances Creating and managing virtual machine snapshots Controlling virtual machine states Accessing the virtual machine consoles Pass configuration data to virtual machines using secrets, configuration maps, and service accounts

Commands:
23.10. Assign Storage Devices If you selected more than one storage device on the storage devices selection screen (refer to Section 23.6, "Storage Devices" ), anaconda asks you to select which of these devices should be available for installation of the operating system, and which should only be attached to the file system for data storage. During installation, the devices that you identify here as being for data storage only are mounted as part of the file system, but are not partitioned or formatted. Figure 23.32. Assign storage devices The screen is split into two panes. The left pane contains a list of devices to be used for data storage only. The right pane contains a list of devices that are to be available for installation of the operating system. Each list contains information about the devices to help you to identify them. A small drop-down menu marked with an icon is located to the right of the column headings. This menu allows you to select the types of data presented on each device. Reducing or expanding the amount of information presented might help you to identify particular devices. Move a device from one list to the other by clicking on the device, then clicking either the button labeled with a left-pointing arrow to move it to the list of data storage devices or the button labeled with a right-pointing arrow to move it to the list of devices available for installation of the operating system. The list of devices available as installation targets also includes a radio button beside each device. On platforms other than System z, this radio button is used to specify the device to which you want to install the boot loader. On System z this choice does not have any effect. The zipl boot loader will be installed on the disk that contains the /boot directory, which is determined later on during partitioning. When you have finished identifying devices to be used for installation, click to continue.

Commands:
Chapter 1. Building applications overview Using OpenShift Dedicated, you can create, edit, delete, and manage applications using the web console or command line interface (CLI). 1.1. Working on a project Using projects, you can organize and manage applications in isolation. You can manage the entire project lifecycle, including creating, viewing, and deleting a project in OpenShift Dedicated. After you create the project, you can grant or revoke access to a project and manage cluster roles for the users using the Developer perspective. You can also edit the project configuration resource while creating a project template that is used for automatic provisioning of new projects. As a user with dedicated administrator permissions, you can choose to prevent an authenticated user group from self-provisioning new projects . 1.2. Working on an application 1.2.1. Creating an application To create applications, you must have created a project or have access to a project with the appropriate roles and permissions. You can create an application by using either the Developer perspective in the web console , installed Operators , or the OpenShift CLI ( oc ) . You can source the applications to be added to the project from Git, JAR files, devfiles, or the developer catalog. You can also use components that include source or binary code, images, and templates to create an application by using the OpenShift CLI ( oc ). With the OpenShift Dedicated web console, you can create an application from an Operator installed by a cluster administrator. 1.2.2. Maintaining an application After you create the application, you can use the web console to monitor your project or application metrics . You can also edit or delete the application using the web console. When the application is running, not all applications resources are used. As a cluster administrator, you can choose to idle these scalable resources to reduce resource consumption. 1.2.3. Deploying an application You can deploy your application using Deployment or DeploymentConfig objects and manage them from the web console. You can create deployment strategies that help reduce downtime during a change or an upgrade to the application. You can also use Helm , a software package manager that simplifies deployment of applications and services to OpenShift Dedicated clusters. 1.3. Using the Red Hat Marketplace The Red Hat Marketplace is an open cloud marketplace where you can discover and access certified software for container-based environments that run on public clouds and on-premises.

Commands:
13.2.3. Add to /etc/fstab As root, edit the /etc/fstab file to include the new partition using the partition's UUID. Use the command blkid -o list for a complete list of the partition's UUID, or blkid device for individual device details. The first column should contain UUID= followed by the file system's UUID. The second column should contain the mount point for the new partition, and the column should be the file system type (for example, ext3 or swap). If you need more information about the format, read the man page with the command man fstab . If the fourth column is the word defaults , the partition is mounted at boot time. To mount the partition without rebooting, as root, type the command: mount /work

Commands:
Chapter 50. Guided rules Guided rules are business rules that you create in a UI-based guided rules designer in Business Central that leads you through the rule-creation process. The guided rules designer provides fields and options for acceptable input based on the data objects for the rule being defined. The guided rules that you define are compiled into Drools Rule Language (DRL) rules as with all other rule assets. All data objects related to a guided rule must be in the same project package as the guided rule. Assets in the same package are imported by default. After you create the necessary data objects and the guided rule, you can use the Data Objects tab of the guided rules designer to verify that all required data objects are listed or to import other existing data objects by adding a New item .

Commands:
Chapter 3. Accessing the Red Hat Support If you require help with troubleshooting a problem, you can contact Red Hat Support. Procedure Log in to the Red Hat Support web site and choose one of the following options: Open a new support case. Initiate a live chat with a Red Hat expert. Contact a Red Hat expert by making a call or sending an email. 3.1. Using the sosreport utility to collect daignostic information about a system to attach it to a support ticket The sosreport command collects configuration details, system information and diagnostic information from a Red Hat Enterprise Linux system. The following section describes how to use the sosreport command to produce reports for your support cases. Prerequisites A valid user account on the Red Hat Customer Portal. See Create a Red Hat Login . An active subscription for the RHEL system. A support-case number. Procedure Install the sos package: Generate a report: Optionally, pass the -upload option to the command to automatically upload and attach the report to a support case. This requires internet access and your Customer Portal credentials. Optional: Manually attach the report to your support case. See the Red Hat Knowledgebase solution How can I attach a file to a Red Hat support case? for more information. Additional resources What is an sosreport and how to create one in Red Hat Enterprise Linux? (Red Hat Knowledgebase)

Commands:
dnf install sos
sosreport
5.5. Managing High-Availability Services In addition to adding and modifying a service, as described in Section 4.10, "Adding a Cluster Service to the Cluster" , you can perform the following management functions for high-availability services through the luci server component of Conga : Start a service Restart a service Disable a service Delete a service Relocate a service From the cluster-specific page, you can manage services for that cluster by clicking on Service Groups along the top of the cluster display. This displays the services that have been configured for that cluster. Starting a service - To start any services that are not currently running, select any services you want to start by clicking the check box for that service and clicking Start . Restarting a service - To restart any services that are currently running, select any services you want to restart by clicking the check box for that service and clicking Restart . Disabling a service - To disable any service that is currently running, select any services you want to disable by clicking the check box for that service and clicking Disable . Deleting a service - To delete any services that are not currently running, select any services you want to disable by clicking the check box for that service and clicking Delete . Relocating a service - To relocate a running service, click on the name of the service in the services display. This causes the services configuration page for the service to be displayed, with a display indicating on which node the service is currently running. From the Start on node... drop-down box, select the node on which you want to relocate the service, and click on the Start icon. A message appears at the top of the screen indicating that the service is being started. You may need to refresh the screen to see the new display indicating that the service is running on the node you have selected. Note If the running service you have selected is a vm service, the drop-down box will show a migrate option instead of a relocate option. Note You can also start, restart, disable or delete an individual service by clicking on the name of the service on the Services page. This displays the service configuration page. At the top right corner of the service configuration page are the same icons for Start , Restart , Disable , and Delete .

Commands:
7.207. system-config-kickstart 7.207.1. RHBA-2015:1356 - system-config-kickstart bug fix update An updated system-config-kickstart package that fixes one bug is now available for Red Hat Enterprise Linux 6. The system-config-kickstart package contains Kickstart Configurator, a graphical tool for creating kickstart files. Bug Fix BZ# 1022372 Previously, system-config-kickstart tried to display the user manual by executing /usr/bin/htmlview even though this program did not exist, and the underlying code did not handle this situation properly. Consequently, system-config-kickstart terminated. With this update, the user manual, which was in fact outdated and not translated like the rest of the user interface, has been removed from the system-config-kickstart package, and the corresponding menu item has also been removed from the user interface. As a result, system-config-kickstart no longer terminates unexpectedly. Users of system-config-kickstart are advised to upgrade to this updated package, which fixes this bug.

Commands: