mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Overview of upgrading OpenShift AI Red Hat OpenShift AI is automatically updated as new release or versions become available. Currently, no administrator action is necessary to trigger the process. When an OpenShift AI upgrade occurs, you should complete the Requirements for upgrading OpenShift AI . Notes: Before you can use an accelerator in OpenShift AI, your instance must have the associated accelerator profile. If your OpenShift cluster instance has an accelerator, its accelerator profile is preserved after the upgrade. For more information about accelerators, see Working with accelerators . Notebook images are integrated into the image stream during the upgrade and subsequently appear in the OpenShift AI dashboard. Notebook images are constructed externally; they are prebuilt images that undergo quarterly changes and they do not change with every OpenShift AI upgrade. Important Previously, data science pipelines in OpenShift AI were based on KubeFlow Pipelines v1. Data science pipelines are now based on KubeFlow Pipelines v2, which uses a different workflow engine. Data science pipelines 2.0 is enabled and deployed by default in OpenShift AI. Data science pipelines 1.0 resources are no longer supported or managed by OpenShift AI. After upgrading to OpenShift AI with data science pipelines 2.0, it is no longer possible to deploy, view, or edit the details of pipelines that are based on data science pipelines 1.0 from either the dashboard or the KFP API server. If you are a current data science pipelines user, do not upgrade to OpenShift AI with data science pipelines 2.0 until you are ready to migrate to the new data science pipelines solution. OpenShift AI does not automatically migrate existing data science pipelines 1.0 instances to 2.0. If you are upgrading to OpenShift AI with data science pipelines 2.0, you must manually migrate your existing data science pipelines 1.0 instances and update your workbenches. For more information, see Migrating to data science pipelines 2.0 . Data science pipelines 2.0 contains an installation of Argo Workflows. OpenShift AI does not support direct customer usage of this installation of Argo Workflows. To upgrade to OpenShift AI with data science pipelines 2.0, ensure that no separate installation of Argo Workflows exists on your cluster.

Commands:
Chapter 10. PostgreSQL PostgreSQL is an Object-Relational database management system (DBMS). [8] In Red Hat Enterprise Linux 6, the postgresql-server package provides PostgreSQL. Run the rpm -q postgresql-server command to see if the postgresql-server package is installed. If it is not installed, run the following command as the root user to install it: 10.1. PostgreSQL and SELinux When PostgreSQL is enabled, it runs confined by default. Confined processes run in their own domains, and are separated from other confined processes. If a confined process is compromised by an attacker, depending on SELinux policy configuration, an attacker's access to resources and the possible damage they can do is limited. The following example demonstrates the PostgreSQL processes running in their own domain. This example assumes the postgresql-server package is installed: Run the getenforce command to confirm SELinux is running in enforcing mode: The getenforce command returns Enforcing when SELinux is running in enforcing mode. Run the service postgresql start command as the root user to start postgresql : Run the ps -eZ | grep postgres command to view the postgresql processes: The SELinux context associated with the postgresql processes is unconfined_u:system_r:postgresql_t:s0 . The second last part of the context, postgresql_t , is the type. A type defines a domain for processes and a type for files. In this case, the postgresql processes are running in the postgresql_t domain. [8] Refer to the PostgreSQL project page for more information.

Commands:
~]# yum install postgresql-server
~]USD getenforce Enforcing
~]# service postgresql start Starting postgresql service: [ OK ]
~]USD ps -eZ | grep postgres unconfined_u:system_r:postgresql_t:s0 395 ? 00:00:00 postmaster unconfined_u:system_r:postgresql_t:s0 397 ? 00:00:00 postmaster unconfined_u:system_r:postgresql_t:s0 399 ? 00:00:00 postmaster unconfined_u:system_r:postgresql_t:s0 400 ? 00:00:00 postmaster unconfined_u:system_r:postgresql_t:s0 401 ? 00:00:00 postmaster unconfined_u:system_r:postgresql_t:s0 402 ? 00:00:00 postmaster
Chapter 14. Creating the mortgage-process project A project is a container for assets such as data objects, business processes, guided rules, decision tables, and forms. The project that you are creating is similar to the existing Mortgage_Process sample project in Business Central. Procedure In Business Central, go to Menu Design Projects . Red Hat Process Automation Manager provides a default space called MySpace , as shown in the following image. You can use the default space to create and test example projects. Figure 14.1. Default space Click Add Project . Enter mortgage-process in the Name field. Click Configure Advanced Options and modify the GAV fields with the following values: Group ID : com.myspace Artifact ID : mortgage-process Version : 1.0.0 Click Add . The Assets view of the project opens.

Commands:
Chapter 4. Managing users As an OpenStack administrator, you can add, modify, and delete users in the dashboard. Users can be members of one or more projects. You can manage projects and users independently from each other. 4.1. Creating users with the dashboard You can assign a primary project and role to the user. Users that you create with OpenStack Dashboard (horizon) are Identity service users by default. You can integrate Active Directory users by configuring the LDAP provider included with the Identity service. Procedure Log in to the Dashboard as an admin user. Select Identity > Users . Click Create User . Enter a user name, email, and preliminary password for the user. Select a project from the Primary Project list. Select a role for the user from the Role list. The default role is member . Click Create User . 4.2. Editing users with the dashboard You can update user details, including the primary project. Procedure Log in to the dashboard as an admin user. Select Identity > Users . In the Actions column, click Edit . In the Update User window, you can update the User Name , Email , and Primary Project . Click Update User . 4.3. Enabling or disabling users with the dashboard You can disable a user with the dashboard. This action is reversible, unlike deleting a user. Limitations: You cannot disable or enable more than one user at a time. You cannot set the primary project of a user to active. The result is that the user you have disabled cannot: Log in to the dashboard. Get access to OpenStack services. Do any user-project action in the dashboard. Procedure As an admin user in the dashboard, select Identity > Users . In the Actions column, click the arrow, and select Enable User or Disable User . In the Enabled column, the value then updates to either True or False . 4.4. Deleting a user with the dashboard You must be a user with an administrative role to delete other users. This action cannot be reversed. Procedure As an admin user in the dashboard, select Identity > Users . Select the users you want to delete. Click Delete Users . The Confirm Delete Users window is displayed. Click Delete Users to confirm the action.

Commands:
B.43.2. RHSA-2011:0392 - Important: libtiff security and bug fix update Updated libtiff packages that fix one security issue and one bug are now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. The libtiff packages contain a library of functions for manipulating Tagged Image File Format (TIFF) files. CVE-2011-1167 A heap-based buffer overflow flaw was found in the way libtiff processed certain TIFF files encoded with a 4-bit run-length encoding scheme from ThunderScan. An attacker could use this flaw to create a specially-crafted TIFF file that, when opened, would cause an application linked against libtiff to crash or, possibly, execute arbitrary code. Bug Fix BZ# 688825 The RHSA-2011:0318 libtiff update introduced a regression that prevented certain TIFF Internet Fax image files, compressed with the CCITT Group 4 compression algorithm, from being read. All libtiff users should upgrade to these updated packages, which contain a backported patch to resolve these issues. All running applications linked against libtiff must be restarted for this update to take effect.

Commands:
9.3. Browsing GSettings Values for Desktop Applications There are two tools you can use to view and edit GSettings values: The dconf-editor GUI tool. The gsettings command-line utility. Note You may not have dconf-editor installed on the system by default. To install it, run the following command: Both dconf-editor and the gsettings utility let you browse and change options for system and application preferences. You can even use them to change preferences that do not exist in the graphical user interface. dconf-editor provides a GUI for the browsing and editing of settings. It presents the hierarchy of settings in a tree-view and also displays additional information about each setting, including the description, type and default value. gsettings can be used to display and set dconf values. It also includes Bash completion for commands and settings. gsettings can be used to automate configuration in shell scripts. Note that both dconf-editor and the gsettings utility are intended to browse and modify the current user's GSettings database. This means that you should always run these tools as a normal user. Figure 9.1. dconf-editor showing org.gnome.destop.background GSettings Keys Getting More Information For more information on the dconf-editor tool, see the dconf-editor (1) man page. For more information on the gsettings utility, see the gsettings (1) man page.

Commands:
yum install dconf-editor
Chapter 3. Conclusion During this hour, you have been taken on a tour of Red Hat JBoss Data Virtualization's various features. You have run various quick starts that demonstrate the product's functionality and teach you a little about how it works. You can now go forward and modify these quick starts to build your own solutions to suit your business needs. Use the pre-packaged quick starts as templates to guide you and refer to the full documentation suite to learn more about the product's capabilities.

Commands:
Chapter 4. Subscription Management Red Hat Support Tool Red Hat Enterprise Linux 6.5 includes a new package, redhat-support-tool , which provides the Red Hat Support Tool. This tool facilitates console-based access to Red Hat's subscriber services and gives Red Hat subscribers more venues for accessing both the content and services available to them as Red Hat customers. Further, it enables our customers to integrate and automate their helpdesk services with our subscription services. The capabilities of this package include: Knowledge Base article and solution viewing from the console (formatted as man pages). Viewing, creating, modifying, and commenting on customer cases from the console. Attachment uploading directly to a customer case or to ftp://dropbox.redhat.com/ from the console. Full proxy support (that is, FTP and HTTP proxies). Easy listing and downloading of attachments to customer cases from the console. Knowledge Base searching on query terms, log messages, and other parameters, and viewing search results in a selectable list. Easy uploading of log files, text files, and other sources to the Shadowman automatic problem determination engine for diagnosis. Various other support-related commands. For more information about the Red Hat Support Tool, refer to the installed documentation in the /usr/share/doc/redhat-support-tool- version / directory or the following Knowledge Base article: https://access.redhat.com/site/articles/445443 . Updates of subscription-manager list Among the list of available subscription, the output of the subscription-manager list --available command now contains a new field, Provides . This field shows the names of the products that the system is eligible for. In addition, a new field, Suggested , has been added to facilitate compliance and provide parity with the graphical user interface (GUI).

Commands:
5.329. tboot 5.329.1. RHBA-2012:0771 - tboot bug fix update Updated tboot packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The tboot packages provide Trusted Boot (tboot), an open source pre- kernel/VMM module, that uses Intel Trusted Execution Technology (Intel TXT) to initialize the launch of operating system kernels and virtual machines. The tboot package has been upgraded to upstream version 1.7.0, which provides a number of bug fixes and enhancements over the version and adds support for future Intel chip sets. (BZ# 773406 ) Bug Fixes BZ# 732439 Prior to this update, increasing binary large objects (BLOB) with lcptools or lcputils utilities could cause a null pointer dereferencing. This update modifies the underlying code so that the pointer now refers to an existing value. BZ# 754345 Prior to this update, the tboot module could, under certain circumstances, be enabled on 32-bit platforms. As a consequence, tboot could prevent the kernel from booting. This update restricts tboot to 64-bit platforms. All users of tboot are advised to upgrade to these updated packages, which fix these bugs and adds these enhancements.

Commands:
7.70. gvfs 7.70.1. RHBA-2015:0237 - gvfs bug fix update Updated gvfs packages that fix two bugs are now available for Red Hat Enterprise Linux 6. GVFS is the GNOME Desktop Virtual File System layer that allows users to easily access local and remote data via File Transfer Protocol (FTP), Secure Shell File Transfer Protocol (SFTP), Web Distributed Authoring and Versioning (WebDAV), Common Internet File System (CIFS), Server Message Block (SMB), and other protocols. GVFS integrates with the GNOME I/O (GIO) abstraction layer. Bug Fixes BZ# 998061 Previously, the GNOME Desktop Virtual File System (GVFS) trash implementation did not take access permissions into consideration when creating file monitors for mount points. Consequently, file monitors were polling files without read access permissions, preventing AutoFS mount points from expiring as they normally would when not in use for some time. With this update, the trash implementation no longer creates file monitors to monitor files without read access permissions. As a result, AutoFS mount points can now freely expire. BZ# 1140451 Prior to this update, gvfs‐gdu‐volume‐monitor did not verify whether it received the data when getting the pool of GNOME Disk Utility (GDU) devices. Consequently, the gvfs‐gdu‐volume‐monitor process could terminate unexpectedly if the data was not received. Now, gvfs‐gdu‐volume‐monitor verifies whether the data was received, and no longer crashes. Users of GVFS are advised to upgrade to these updated packages, which fix these bugs. 7.70.2. RHBA-2015:1428 - gvfs bug fix update Updated gvfs packages that fix two bugs are now available for Red Hat Enterprise Linux 6. GVFS is the GNOME Desktop Virtual File System layer that allows users to easily access local and remote data using File Transfer Protocol (FTP), Secure Shell File Transfer Protocol (SFTP), Web Distributed Authoring and Versioning (WebDAV), Common Internet File System (CIFS), Server Message Block (SMB), and other protocols. GVFS integrates with the GNOME I/O (GIO) abstraction layer. Bug Fixes BZ# 1165676 Prior to this update, the gvfsd-gphoto2 utility did not verify whether it received the data when getting information on the camera attached storage. Consequently, gvfsd-gphoto2 could terminate unexpectedly if the data was not received. Now, gvfsd-gphoto2 verifies whether the data was received, and no longer crashes in the described situation. BZ# 1210203 The gvfsd-metadata daemon did not correctly handle the situation when an application tried to save a metadata entry larger than the size of a journal file, that is, larger than 32 kB. The daemon wrote all changes from the journal to the metadata database to make more space for the entry and then created a new journal file. This operation was repeated in an infinite loop unnecessarily, overloading the CPU and disk. With this update, the operation is retried only once. As a result, the metadata entry is not saved if it is too large, and gvfsd-metadata returns a warning instead. Users of GVFS are advised to upgrade to these updated packages, which fix these bugs.

Commands:
23.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 23.36. 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:
6.3. JBoss Data Virtualization Log Categories Within EAP log files, all information specific to JBoss Data Virtualization is prefixed with the org.teiid log category identifier. Logs originating from third-party code and other components not related to JBoss Data Virtualization, including integrated org.jboss components, are prefixed with their own log category identifiers, not org.teiid . The table below summarizes the categories relevant to JBoss Data Virtualization. For a complete listing, see the standalone.xml (or domain.xml for domain mode) file. Table 6.3. JBoss Data Virtualization Log Categories Log Category Description com.arjuna Third-party transaction manager. This will include information about all transactions, not just those for JBoss Data Virtualization. org.teiid Root category identifier for all JBoss Data Virtualization logs. Note: there are potentially more contexts used under org.teiid than those shown in this table. org.teiid.PROCESSOR Query processing logs. Also see org.teiid.PLANNER. org.teiid.PLANNER Query planning logs. org.teiid.SECURITY Session/Authentication events. Also see org.teiid AUDIT_LOG. org.teiid.TRANSPORT Events related to the socket transport. org.teiid.RUNTIME Events related to work management and system start/stop. org.teiid.CONNECTOR Connector logs. org.teiid.BUFFER_MGR Buffer and storage management logs. org.teiid.TXN_LOG Detailed log of all transaction operations. org.teiid.COMMAND_LOG Refer to Section 6.4, "Command Logging" . org.teiid.AUDIT_LOG Refer to Section 6.5, "Audit Logging" . org.teiid.ADMIN_API Admin API logs. org.teiid.ODBC ODBC logs. Note Refer to the JBoss Enterprise Application Platform Administration and Configuration Guide for more information about logging.

Commands:
Chapter 11. Changing the Camel version As you work with a Fuse tooling project, you might want to change the Camel version that it uses. This can be helpful, for example, if you want to use a feature supported in a more recent Camel version or if you want to use a community version. To change the Camel version that a project uses: In Project Explorer , right-click the project for which you want to change the Camel version and select Configure Change Camel Version . In the Change Camel Version window, to the right of the Camel Version field, click the down caret to display available Camel versions. To use a community version of Apache Camel, you enter its version number, for example, 2.19.2 . Select or enter the version you want and click Finish . Fuse Tooling checks whether the version you selected is available and supported by Fuse Tooling. If it is then Fuse Tooling changes the Camel version and saves the project's updated pom.xml file. You receive an error message if the Camel version that you select is not available or not supported. You can check the project's Camel version in its pom.xml file, in the <camel.version> element.

Commands:
Chapter 5. Customizing the Fuse Console branding You can customize the Fuse Console branding information, such as title, logo, and login page information, by using the Fuse Console branding plugin. By default, the Fuse Console branding is defined in the hawtconfig.json that is located in the Fuse Console WAR file ( karaf-install-dir/system/io/hawt/hawtio-war/<version>/hawtio-war-<version>.war ). When you implement the Fuse Console branding plugin, you can override the default branding with your own custom branding. Procedure Download the branding plugin example from https://github.com/hawtio/hawtio/tree/master/examples/branding-plugin to a local directory of your choice. In an editor of your choice, open the Fuse Console branding plugin's src/main/webapp/plugin/brandingPlugin.js file to customize the Fuse Console branding. You can change the values of the configuration properties listed in Table A.1, "Fuse Console Configuration Properties" . Save your changes. In an editor of your choice, open the Fuse Console branding plugin's pom.xml file to its <parent> section: Edit the <parent> section as follows: Change the value of the <version> property to match the version of your Fuse on Karaf installation. For example, if your Fuse on Karaf installation directory name is 2.0.0.fuse-760015 , set the version to 2.0.0.fuse-760015 . Remove the <relativePath>../..</relativePath> line. For example: In a Terminal window, build the branding-plugin project by running the following command: If Fuse is not already running, start it by running the following command: Linux/Unix: bin/fuse Windows: bin\fuse.bat` At the Karaf CLI prompt, type the following command to install the Fuse Console branding plugin (where <version> is the version of your Fuse on Karaf installation): Linux/Unix: install -s mvn:io.hawt/branding-plugin/<version>/war Windows: install -s mvn:io.hawt\branding-plugin\<version>\war In a web browser, open the Fuse Console by using the URL that the start command returned in Step 7 (the default URL is http://localhost:8181/hawtio/ ). Note If you have already run the Fuse Console in a web browser, the branding is stored in the browser's local storage. To use new branding settings, you must clear the browser's local storage.

Commands:
<parent> <groupId>io.hawt</groupId> <artifactId>project</artifactId> <version>2.9-SNAPSHOT</version> <relativePath>../..</relativePath> </parent>
<parent> <groupId>io.hawt</groupId> <artifactId>project</artifactId> <version> 2.0.0.fuse-760015</version> </parent>
mvn clean install
Appendix B. Revision History Note that revision numbers relate to the edition of this manual, not to version numbers of Red Hat Directory Server. Revision History Revision 11.5-1 Tue May 10 2022 Marc Muehlfeld Red Hat Directory Server 11.5 release of this guide. Revision 11.4-1 Tue Nov 09 2021 Marc Muehlfeld Red Hat Directory Server 11.4 release of this guide. Revision 11.3-1 Tue May 11 2021 Marc Muehlfeld Red Hat Directory Server 11.3 release of this guide. Revision 11.2-1 Tue Nov 03 2020 Marc Muehlfeld Red Hat Directory Server 11.2 release of this guide. Revision 11.1-1 Tue Apr 28 2020 Marc Muehlfeld Red Hat Directory Server 11.1 release of this guide. Revision History Revision 11.0-1 Thu Nov 21 2019 Marc Muehlfeld Red Hat Directory Server 11.0 release of this guide.

Commands: