mtpti5iD/redhat-docs_dataset huggingface dataset:
Providing feedback on Red Hat documentation We appreciate your feedback on our technical content and encourage you to tell us what you think. If you'd like to add comments, provide insights, correct a typo, or even ask a question, you can do so directly in the documentation. Note You must have a Red Hat account and be logged in to the customer portal. To submit documentation feedback from the customer portal, do the following: Select the HTML format. Click the Feedback button at the top-right of the document. Highlight the section of text where you want to provide feedback. Click the Add Feedback dialog to your highlighted text. Enter your feedback in the text box on the right of the page and then click Submit . We automatically create a tracking issue each time you submit feedback. Open the link that is displayed after you click Submit and start watching the issue or add more comments. Thank you for the valuable feedback.

Commands:
Chapter 19. Shared File Service (manila) Parameters You can modify the manila service with shared file service parameters. Parameter Description ApacheCertificateKeySize Override the private key size used when creating the certificate for this service. CephClusterName The Ceph cluster name. The default value is ceph . CertificateKeySize Specifies the private key size used when creating the certificate. The default value is 2048 . ManilaCephClientUserName Ceph client username for manila integration. The default value is manila . ManilaCephFSCephFSProtocolHelperType Protocol type ( CEPHFS or NFS ) when cephfs back end is enabled. Set via manila cephfs environment files. The default value is CEPHFS . ManilaEnabledShareProtocols List of protocols to be allowed for share creation in manila. When not set, the list is inferred via the storage back end/s enabled. ManilaIPv6 Set to True to enable IPv6 access in manila. The default value is False . ManilaPassword The password for the shared file service account. ManilaWorkers Set the number of workers for manila::wsgi::apache. The default value is equal to the number of vCPU cores on the physical node. MemcacheUseAdvancedPool Use the advanced (eventlet safe) memcached client pool. The default value is True . NotificationDriver Driver or drivers to handle sending notifications. The default value is noop .

Commands:
Chapter 10. Uninstalling a cluster on vSphere that uses installer-provisioned infrastructure You can remove a cluster that you deployed in your VMware vSphere instance by using installer-provisioned infrastructure. Note When you run the openshift-install destroy cluster command to uninstall OpenShift Container Platform, vSphere volumes are not automatically deleted. The cluster administrator must manually find the vSphere volumes and delete them. 10.1. Removing a cluster that uses installer-provisioned infrastructure You can remove a cluster that uses installer-provisioned infrastructure from your cloud. Note After uninstallation, check your cloud provider for any resources not removed properly, especially with user-provisioned infrastructure clusters. There might be resources that the installation program did not create or that the installation program is unable to access. Prerequisites You have a copy of the installation program that you used to deploy the cluster. You have the files that the installation program generated when you created your cluster. Procedure On the computer that you used to install the cluster, go to the directory that contains the installation program, and run the following command: USD ./openshift-install destroy cluster \ --dir <installation_directory> --log-level info 1 2 1 For <installation_directory> , specify the path to the directory that you stored the installation files in. 2 To view different details, specify warn , debug , or error instead of info . Note You must specify the directory that contains the cluster definition files for your cluster. The installation program requires the metadata.json file in this directory to delete the cluster. Optional: Delete the <installation_directory> directory and the OpenShift Container Platform installation program.

Commands:
./openshift-install destroy cluster --dir <installation_directory> --log-level info 1 2
Chapter 4. Install additional software You need to perform some additional configuration for access to software and updates. Ensure you have access to software updates: Configure software repository access using the web console . If your hyperconverged hosts use disk encryption, Install disk encryption software . 4.1. Configuring software access 4.1.1. Configuring software repository access using the Web Console Prerequisites This process is for hyperconverged hosts based on Red Hat Virtualization 4. Procedure On each hyperconverged host: Log in to the Web Console. Use the management FQDN and port 9090, for example, https://server1.example.com:9090/ . Click Subscriptions . Click Register System . Enter your Customer Portal user name and password. Click Done . The Red Hat Virtualization Host subscription is automatically attached to the system. Enable the Red Hat Virtualization 4 repository to allow later updates to the Red Hat Virtualization Host: (Optional) If you use disk encryption, execute the following on each Network-Bound Disk Encryption (NBDE) key server: Log in to the NBDE key server. Register the NBDE key server with Red Hat. Attach the subscription pool: Enable the repositories required for disk encryption software: For NBDE key servers based on Red Hat Enterprise Linux 8: For NBDE key servers based on Red Hat Enterprise Linux 7: 4.2. Installing software 4.2.1. Installing disk encryption software The Network-Bound Disk Encryption key server requires an additional package to support disk encryption. Prerequisites Configuring software repository access using the web console . Procedure On each Network-Bound Disk Encryption (NBDE) key server, install the server-side packages.

Commands:
subscription-manager repos --enable=rhvh-4-for-rhel-8-x86_64-rpms
subscription-manager register --username= username --password= password
subscription-manager attach --pool= pool_id
subscription-manager repos --enable="rhel-8-for-x86_64-baseos-rpms" --enable="rhel-8-for-x86_64-appstream-rpms"
subscription-manager repos --enable="rhel-7-server-rpms"
yum install tang -y
Infinispan Query Guide Red Hat JBoss Data Grid 6.6 Using the Infinispan Query Module in Red Hat JBoss Data Grid 6.6.1 Misha Husnain Ali Red Hat Engineering Content Services mhusnain@redhat.com Gemma Sheldon Red Hat Engineering Content Services gsheldon@redhat.com Christian Huffman Red Hat Engineering Content Services chuffman@redhat.com

Commands:
B.100. util-linux-ng B.100.1. RHBA-2011:0201 - util-linux-ng bug fix update Updated util-linux-ng packages that fix a bug in the mount utility are now available for Red Hat Enterprise Linux 6. The util-linux-ng package contains a large variety of low-level system utilities that are necessary for a Linux system to function. Bug Fix BZ# 659612 To address problems with iSCSI root devices not being checked with the fsck utility, Red Hat Enterprise Linux 5.2 introduced the "_rnetdev" mount option. However, this functionality was missing in the package for Red Hat Enterprise Linux 6. With this update, the mount utility has been updated to support this option. Users of util-linux-ng should upgrade to these updated packages, which resolve this issue.

Commands:
5.6. Configuring PPP (Point-to-Point) Settings Authentication Methods In most cases, the provider's PPP servers supports all the allowed authentication methods. If a connection fails, the user should disable support for some methods, depending on the PPP server configuration. Use point-to-point encryption (MPPE) Microsoft Point-To-Point Encryption protocol ( RFC 3078 ). Allow BSD data compression PPP BSD Compression Protocol ( RFC 1977 ). Allow Deflate data compression PPP Deflate Protocol ( RFC 1979 ). Use TCP header compression Compressing TCP/IP Headers for Low-Speed Serial Links ( RFC 1144 ). Send PPP echo packets LCP Echo-Request and Echo-Reply Codes for loopback tests ( RFC 1661 ). Note Since the PPP support in NetworkManager is optional, to configure PPP settings, make sure that the NetworkManager-ppp package is already installed.

Commands:
16.5. Actions 16.5.1. Copying a Floating Disk When copying a floating disk, the API requires the storage_domain element. The optional name element specifies an alias for the disk. Example 16.4. Copying a Floating Disk

Commands:
POST /ovirt-engine/api/disks/54a81464-b758-495a-824b-1e7937116ae5/copy HTTP/1.1 Accept: application/xml Content-type: application/xml <action> <storage_domain id="c8e108f7-c049-40d2-ad3d-620e4638828e"/> <disk> <name>rhel_disk2</name> </disk> </action>
7.2. Advantages of Using Docker Docker brings in an API for container management, an image format and a possibility to use a remote registry for sharing containers. This scheme benefits both developers and system administrators with advantages such as: Rapid application deployment - containers include the minimal runtime requirements of the application, reducing their size and allowing them to be deployed quickly. Portability across machines - an application and all its dependencies can be bundled into a single container that is independent from the host version of Linux kernel, platform distribution, or deployment model. This container can be transfered to another machine that runs Docker , and executed there without compatibility issues. Version control and component reuse - you can track successive versions of a container, inspect differences, or roll-back to versions. Containers reuse components from the preceding layers, which makes them noticeably lightweight. Sharing - you can use a remote repository to share your container with others. Red Hat provides a registry for this purpose, and it is also possible to configure your own private repository. Lightweight footprint and minimal overhead - Docker images are typically very small, which facilitates rapid delivery and reduces the time to deploy new application containers. Simplified maintenance - Docker reduces effort and risk of problems with application dependencies.

Commands:
17.4.2. Booting into a Graphical Environment If you have installed the X Window System but are not seeing a graphical desktop environment once you log into your system, you can start the X Window System graphical interface using the command startx . Once you enter this command and press Enter , the graphical desktop environment is displayed. Note, however, that this is just a one-time fix and does not change the log in process for future log ins. To set up your system so that you can log in at a graphical login screen, you must edit one file, /etc/inittab , by changing just one number in the runlevel section. When you are finished, reboot the computer. The time you log in, you are presented with a graphical login prompt. Open a shell prompt. If you are in your user account, become root by typing the su command. Now, type the following to edit the file with gedit . The file /etc/inittab opens. Within the first screen, a section of the file which looks like the following appears: To change from a console to a graphical login, you should change the number in the line id:3:initdefault: from a 3 to a 5 . Warning Change only the number of the default runlevel from 3 to 5 . Your changed line should look like the following: When you are satisfied with your change, save and exit the file using the Ctrl + Q keys. A window appears and asks if you would like to save the changes. Click Save . The time you log in after rebooting your system, you are presented with a graphical login prompt.

Commands:
gedit /etc/inittab
Default runlevel. The runlevels used are: 0 - halt (Do NOT set initdefault to this) 1 - Single user mode 2 - Multiuser, without NFS (The same as 3, if you do not have networking) 3 - Full multiuser mode 4 - unused 5 - X11 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault:
id:5:initdefault:
1.3. keepalived and haproxy Administrators can use both Keepalived and HAProxy together for a more robust and scalable high availability environment. Using the speed and scalability of HAProxy to perform load balancing for HTTP and other TCP-based services in conjunction with Keepalived failover services, administrators can increase availability by distributing load across real servers as well as ensuring continuity in the event of router unavailability by performing failover to backup routers.

Commands:
Chapter 2. Managing your cluster resources You can apply global configuration options in OpenShift Dedicated. Operators apply these configuration settings across the cluster. 2.1. Interacting with your cluster resources You can interact with cluster resources by using the OpenShift CLI ( oc ) tool in OpenShift Dedicated. The cluster resources that you see after running the oc api-resources command can be edited. Prerequisites You have access to the cluster as a user with the dedicated-admin role. You have access to the web console or you have installed the oc CLI tool. Procedure To see which configuration Operators have been applied, run the following command: USD oc api-resources -o name | grep config.openshift.io To see what cluster resources you can configure, run the following command: USD oc explain <resource_name>.config.openshift.io To see the configuration of custom resource definition (CRD) objects in the cluster, run the following command: USD oc get <resource_name>.config -o yaml To edit the cluster resource configuration, run the following command: USD oc edit <resource_name>.config -o yaml

Commands:
oc api-resources -o name | grep config.openshift.io
oc explain <resource_name>.config.openshift.io
oc get <resource_name>.config -o yaml
oc edit <resource_name>.config -o yaml
probe::irq_handler.exit Name probe::irq_handler.exit - Execution of interrupt handler completed Synopsis irq_handler.exit Values flags_str symbolic string representation of IRQ flags dev_name name of device ret return value of the handler action struct irqaction* thread_fn interrupt handler function for threaded interrupts next_irqaction pointer to irqaction for shared interrupts thread thread pointer for threaded interrupts thread_flags Flags related to thread irq interrupt number handler interrupt handler function that was executed flags flags for IRQ handler dir pointer to the proc/irq/NN/name entry dev_id Cookie to identify device

Commands:
14. Interoperability 14.1. Samba Samba is a suite of programs which use NetBIOS over TCP/IP (NetBT) to enable the sharing of files, printers and other information (such as directories of available files and printers). This package provides a Server Message Block or SMB server (also known as a Common Internet File System or CIFS server) which can provide network services to SMB/CIFS clients. Red Hat Enterprise Linux 6 provides the following significant enhancements to Samba: Internet Protocol version 6 support (IPv6) Support for Windows 2008 (R2) trust relationships. Support for Windows 7 domain members. Support for Active Directory LDAP signing/sealing policy. Improvements for libsmbclient Better support for Windows management tools (mmc and User Manager) Automatic machine password changes as domain member New registry based configuration layer Encrypted SMB transport between Samba client and server Full support for Windows cross-forest, transitive trusts and one-way domain trusts New NetApi remote management and winbind client C libraries A new graphical user interface for joining Windows Domains Note Refer to the Deployment Guide for futher information on Samba configuration on Red Hat Enterprise Linux 6.

Commands:
Chapter 1. Introduction 1.1. About the MTA plugin for IntelliJ IDEA You can migrate and modernize applications by using the Migration Toolkit for Applications (MTA) plugin for IntelliJ IDEA. The MTA plugin analyzes your projects using customizable rulesets, marks issues in the source code, provides guidance to fix the issues, and offers automatic code replacement, if possible. The plugin supports both the Community Edition and the Ultimate version of IntelliJ IDEA. 1.2. About the Migration Toolkit for Applications What is the Migration Toolkit for Applications? Migration Toolkit for Applications (MTA) accelerates large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. This solution provides insight throughout the adoption process, at both the portfolio and application levels: inventory, assess, analyze, and manage applications for faster migration to OpenShift via the user interface. In MTA 7.1 and later, when you add an application to the Application Inventory , MTA automatically creates and executes language and technology discovery tasks. Language discovery identifies the programming languages used in the application. Technology discovery identifies technologies, such as Enterprise Java Beans (EJB), Spring, etc. Then, each task assigns appropriate tags to the application, reducing the time and effort you spend manually tagging the application. MTA uses an extensive default questionnaire as the basis for assessing your applications, or you can create your own custom questionnaire, enabling you to estimate the difficulty, time, and other resources needed to prepare an application for containerization. You can use the results of an assessment as the basis for discussions between stakeholders to determine which applications are good candidates for containerization, which require significant work first, and which are not suitable for containerization. MTA analyzes applications by applying one or more rulesets to each application considered to determine which specific lines of that application must be modified before it can be modernized. MTA examines application artifacts, including project source directories and application archives, and then produces an HTML report highlighting areas needing changes. How does the Migration Toolkit for Applications simplify migration? The Migration Toolkit for Applications looks for common resources and known trouble spots when migrating applications. It provides a high-level view of the technologies used by the application. MTA generates a detailed report evaluating a migration or modernization path. This report can help you to estimate the effort required for large-scale projects and to reduce the work involved.

Commands:
8.8. Selecting Network Team Configuration Methods To configure a network team using NetworkManager 's text user interface tool, nmtui , proceed to Section 8.9, "Configure a Network Team Using the Text User Interface, nmtui" To create a network team using the command-line tool , nmcli , proceed to Section 8.10.1, "Configure Network Teaming Using nmcli" . To create a network team using the Team daemon , teamd , proceed to Section 8.10.2, "Creating a Network Team Using teamd" . To create a network team using configuration files , proceed to Section 8.10.3, "Creating a Network Team Using ifcfg Files" . To configure a network team using a graphical user interface , see Section 8.14, "Creating a Network Team Using a GUI"

Commands:
Chapter 2. Accessing the web console The OpenShift Container Platform web console is a user interface accessible from a web browser. Developers can use the web console to visualize, browse, and manage the contents of projects. 2.1. Prerequisites JavaScript must be enabled to use the web console. For the best experience, use a web browser that supports WebSockets . Review the OpenShift Container Platform 4.x Tested Integrations page before you create the supporting infrastructure for your cluster. 2.2. Understanding and accessing the web console The web console runs as a pod on the master. The static assets required to run the web console are served by the pod. After OpenShift Container Platform is successfully installed using openshift-install create cluster , find the URL for the web console and login credentials for your installed cluster in the CLI output of the installation program. For example: Example output INFO Install complete! INFO Run 'export KUBECONFIG=<your working directory>/auth/kubeconfig' to manage the cluster with 'oc', the OpenShift CLI. INFO The cluster is ready when 'oc login -u kubeadmin -p <provided>' succeeds (wait a few minutes). INFO Access the OpenShift web-console here: https://console-openshift-console.apps.demo1.openshift4-beta-abcorp.com INFO Login to the console with user: kubeadmin, password: <provided> Use those details to log in and access the web console. For existing clusters that you did not install, you can use oc whoami --show-console to see the web console URL.

Commands:
INFO Install complete! INFO Run 'export KUBECONFIG=<your working directory>/auth/kubeconfig' to manage the cluster with 'oc', the OpenShift CLI. INFO The cluster is ready when 'oc login -u kubeadmin -p <provided>' succeeds (wait a few minutes). INFO Access the OpenShift web-console here: https://console-openshift-console.apps.demo1.openshift4-beta-abcorp.com INFO Login to the console with user: kubeadmin, password: <provided>
21.5. Deactivating a group configuration Use this procedure to deactivate group configurations like metadata-cache , nl-cache , or samba . Use this procedure to reset volume options set up by a group configuration in order to deactivate the group. Navigate to the groups folder: View the contents of the group profile: Reset each volume option present in the group profile:

Commands:
cd /var/lib/glusterd/groups
cat PROFILE_NAME
gluster volume reset VOLNAME OPTION_NAME
2.6. UPower In Red Hat Enterprise Linux 6 DeviceKit-power assumed the power management functions that were part of HAL and some of the functions that were part of GNOME Power Manager in releases of Red Hat Enterprise Linux (refer also to Section 2.7, "GNOME Power Manager" . Red Hat Enterprise Linux 7, DeviceKit-power was renamed to UPower . UPower provides a daemon, an API, and a set of command-line tools. Each power source on the system is represented as a device, whether it is a physical device or not. For example, a laptop battery and an AC power source are both represented as devices. You can access the command-line tools with the upower command and the following options: --enumerate , -e displays an object path for each power devices on the system, for example: --dump , -d displays the parameters for all power devices on the system. --wakeups , -w displays the CPU wakeups on the system. --monitor , -m monitors the system for changes to power devices, for example, the connection or disconnection of a source of AC power, or the depletion of a battery. Press Ctrl + C to stop monitoring the system. --monitor-detail monitors the system for changes to power devices, for example, the connection or disconnection of a source of AC power, or the depletion of a battery. The --monitor-detail option presents more detail than the --monitor option. Press Ctrl + C to stop monitoring the system. --show-info object_path , -i object_path displays all information available for a particular object path. For example, to obtain information about a battery on your system represented by the object path /org/freedesktop/UPower/devices/battery_BAT0 , run:

Commands:
/org/freedesktop/UPower/devices/line_power_AC /org/freedesktop/UPower/devices/battery_BAT0
~]USD upower -i /org/freedesktop/UPower/devices/battery_BAT0