mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. About CI/CD OpenShift Container Platform is an enterprise-ready Kubernetes platform for developers, which enables organizations to automate the application delivery process through DevOps practices, such as continuous integration (CI) and continuous delivery (CD). To meet your organizational needs, the OpenShift Container Platform provides the following CI/CD solutions: OpenShift Builds OpenShift Pipelines OpenShift GitOps 1.1. OpenShift Builds OpenShift Builds provides you the following options to configure and run a build: Builds using Shipwright is an extensible build framework based on the Shipwright project. You can use it to build container images on an OpenShift Container Platform cluster. You can build container images from source code and Dockerfile by using image build tools, such as Source-to-Image (S2I) and Buildah. For more information, see builds for Red Hat OpenShift . Builds using BuildConfig objects is a declarative build process to create cloud-native apps. You can define the build process in a YAML file that you use to create a BuildConfig object. This definition includes attributes such as build triggers, input parameters, and source code. When deployed, the BuildConfig object builds a runnable image and pushes the image to a container image registry. With the BuildConfig object, you can create a Docker, Source-to-image (S2I), or custom build. For more information, see Understanding image builds . 1.2. OpenShift Pipelines OpenShift Pipelines provides a Kubernetes-native CI/CD framework to design and run each step of the CI/CD pipeline in its own container. It can scale independently to meet the on-demand pipelines with predictable outcomes. For more information, see Red Hat OpenShift Pipelines . 1.3. OpenShift GitOps OpenShift GitOps is an Operator that uses Argo CD as the declarative GitOps engine. It enables GitOps workflows across multicluster OpenShift and Kubernetes infrastructure. Using OpenShift GitOps, administrators can consistently configure and deploy Kubernetes-based infrastructure and applications across clusters and development lifecycles. For more information, see Red Hat OpenShift GitOps . 1.4. Jenkins Jenkins automates the process of building, testing, and deploying applications and projects. OpenShift Developer Tools provides a Jenkins image that integrates directly with the OpenShift Container Platform. Jenkins can be deployed on OpenShift by using the Samples Operator templates or certified Helm chart. For more information, see Configuring Jenkins images .

Commands:
1.11.2. Useful Websites http://www.kernel.org/pub/linux/libs/pam/ -- The Linux-PAM project homepage. http://www.usenix.org/ -- The USENIX homepage. A professional organization dedicated to bringing together computer professionals of all types and fostering improved communication and innovation. http://www.sage.org/ -- The System Administrators Guild homepage. A USENIX special technical group that is a good resource for all system administrators responsible for Linux (or Linux-like) operating systems. http://www.python.org/ -- The Python Language Website. An excellent site for learning more about Python. http://www.perl.org/ -- The Perl Mongers Website. A good place to start learning about Perl and connecting with the Perl community. http://www.rpm.org/ -- The RPM Package Manager homepage. The most comprehensive website for learning about RPM.

Commands:
4.165. lohit-telugu-fonts 4.165.1. RHEA-2011:1142 - lohit-telugu-fonts enhancement update An updated lohit-telugu-fonts package which adds one enhancement is now available for Red Hat Enterprise Linux 6. The lohit-telugu-fonts package provides a free Telugu TrueType/OpenType font. Enhancement BZ# 691297 Unicode 6.0, the most recent major version of the Unicode standard, introduces the Indian Rupee Sign (U+20B9), the new official Indian currency symbol. With this update, the lohit-telugu-fonts package now includes a glyph for this new character. All users requiring the Indian rupee sign should install this updated package, which adds this enhancement.

Commands:
5.5. alsa-utils 5.5.1. RHBA-2012:0917 - alsa-utils bug fix and enhancement update Updated alsa-utils packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The alsa-utils packages provide command-line utilities for the Advanced Linux Sound Architecture (ALSA). Bug Fix BZ# 674199 Prior to this update, the alsactl tool tried to initialize all sound cards if the /etc/asound.state file was not present. As a consequence, SElinux could deny access to non-existent devices. This update modifies the underlying code so that alsactl is called only once from udev. Enhancement BZ# 650113 With this update, the alsa-delay and alsaloop utilities have been added to alsa-utils to manage the system audio delay. All users of alsa-utils are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
Deploying and managing OpenShift Data Foundation using Red Hat OpenStack Platform Red Hat OpenShift Data Foundation 4.15 Instructions on deploying and managing OpenShift Data Foundation on Red Hat OpenStack Platform Red Hat Storage Documentation Team Abstract Read this document for instructions about how to install and manage Red Hat OpenShift Data Foundation using Red Hat OpenShift Container Platform on Red Hat OpenStack Platform (RHOSP). Important Deploying and managing OpenShift Data Foundation on Red Hat OpenStack Platform is a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

Commands:
7.285. xorg-x11-drv-vmmouse 7.285.1. RHBA-2013:0300 - xorg-x11-drv-vmmouse bug fix and enhancement update Updated xorg-x11-drv-vmmouse packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-vmmouse packages contain the X.Org X11 input drivers for the VMware vSphere Hypervisor. Note The xorg-x11-drv-vmmouse package has been upgraded to upstream version 12.9.0, which provides a number of bug fixes and enhancements over the version. (BZ#835262) Users of xorg-x11-drv-vmmouse are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 7. Updating multiple systems You can send an update to Edge several systems through the dashboard application. If the image is the same for all the systems you select, you can update them at the same time. For that, you can select the Edge several systems and use the Update button in the dashboard. The action adds the latest package version update to the image. Optionally, you can select one image and use the More options icon (...) to update, to be able to choose the package version for that image. Prerequisites You must have a Red Hat Hybrid Cloud Console account. A system is built from an image and registered with the Red Hat Hybrid Cloud Console. You built an update to that image. Procedure Access Red Hat Hybrid Cloud Console platform and log in. From the console dashboard, navigate to Red Hat Insights > RHEL > Inventory > Systems . Select the systems that you want to update. The Status column for the system will say Update available if your image update was successful. In the Systems toolbar, click Update to apply the update to the systems. Review the information about the update and click Update system . Confirm that the update completed successfully in the image dashboard. Verification From the console dashboard, navigate to Red Hat Insights > RHEL > Inventory > Systems . If the update was successful, the system status is Up to date . If the system status is Error or Unresponsive the system did not update properly. Click the status to learn more about the failure. If the system status is Error , you can try the update again. Click the Error status, then click Retry .

Commands:
Chapter 12. NFV Performance Red Hat OpenStack Platform director configures the Compute nodes to enforce resource partitioning and fine tuning to achieve line rate performance for the guest virtual network functions (VNFs). The key performance factors in the NFV use case are throughput, latency, and jitter. You can enable high-performance packet switching between physical NICs and virtual machines using data plane development kit (DPDK) accelerated virtual machines. OVS 2.10 embeds support for DPDK 17 and includes support for vhost-user multiqueue, allowing scalable performance. OVS-DPDK provides line-rate performance for guest VNFs. Single root I/O virtualization (SR-IOV) networking provides enhanced performance, including improved throughput for specific networks and virtual machines. Other important features for performance tuning include huge pages, NUMA alignment, host isolation, and CPU pinning. VNF flavors require huge pages and emulator thread isolation for better performance. Host isolation and CPU pinning improve NFV performance and prevent spurious packet loss. For a high-level introduction to CPUs and NUMA topology, see: NFV Performance Considerations and Configure Emulator Threads to run on a Dedicated Physical CPU .

Commands:
Appendix E. 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 11.0-1 Tue Nov 05 2019 Marc Muehlfeld Red Hat Directory Server 11.0 release of this guide.

Commands:
8.62. haproxy 8.62.1. RHBA-2013:1619 - haproxy bug fix and enhancement update Updated haproxy packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The haproxy packages provide a reliable, high-performance network load balancer for TCP and HTTP-based applications. It is particularly suited for web sites crawling under very high loads while needing persistence or Layer7 processing. Note The haproxy packages have been upgraded to upstream version 1.4.24, which provides a number of bug fixes and enhancements over the version. (BZ# 947987 ) Bug Fix BZ# 903303 Previously, the setuid() and setgid() functions did not work properly. As a consequence, the HAProxy load balancer failed to drop supplementary groups correctly after attempting to drop root privileges. The behavior of the functions has been modified, and HAProxy now drops all supplementary groups as expected. Enhancement BZ# 921064 With this update, support for TPROXY has been added to the haproxy packages. TPROXY simplifies management tasks of clients behind proxy firewalls. Also, transparent proxying makes the presence of the proxy invisible to the user. Users of haproxy are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
17.3.2. Saving Traceback Messages If anaconda encounters an error during the graphical installation process, it presents you with a crash reporting dialog box: Figure 17.1. The Crash Reporting Dialog Box Details shows you the details of the error: Figure 17.2. Details of the Crash Save saves details of the error locally or remotely: Exit exits the installation process. If you select Save from the main dialog, you can choose from the following options: Figure 17.3. Select reporter Logger saves details of the error as a log file to the local hard drive at a specified location. Red Hat Customer Support submits the crash report to Customer Support for assistance. Report uploader uploads a compressed version of the crash report to Bugzilla or a URL of your choice. Before submitting the report, click Preferences to specify a destination or provide authentication details. Select the reporting method you need to configure and click Configure Event . Figure 17.4. Configure reporter preferences Logger Specify a path and a filename for the log file. Check Append if you are adding to an existing log file. Figure 17.5. Specify local path for log file Red Hat Customer Support Enter your Red Hat Network username and password so your report reaches Customer Support and is linked with your account. The URL is prefilled and Verify SSL is checked by default. Figure 17.6. Enter Red Hat Network authentication details Report uploader Specify a URL for uploading a compressed version of the crash report. Figure 17.7. Enter URL for uploading crash report Bugzilla Enter your Bugzilla username and password to lodge a bug with Red Hat's bug-tracking system using the crash report. The URL is prefilled and Verify SSL is checked by default. Figure 17.8. Enter Bugzilla authentication details Once you have entered your preferences, click OK to return to the report selection dialog. Select how you would like to report the problem and then click Forward . Figure 17.9. Confirm report data You can now customize the report by checking and unchecking the issues that will be included. When finished, click Apply . Figure 17.10. Report in progress This screen displays the outcome of the report, including any errors in sending or saving the log. Click Forward to proceed. Figure 17.11. Reporting done Reporting is now complete. Click Forward to return to the report selection dialog. You can now make another report, or click Close to exit the reporting utility and then Exit to close the installation process. Important This information does not apply to users of headless IBM System p systems.

Commands:
Chapter 41. Spreadsheet decision tables Spreadsheet decision tables are XLS or XLSX spreadsheets that contain business rules defined in a tabular format. You can include spreadsheet decision tables with standalone Red Hat Process Automation Manager projects or upload them to projects in Business Central. Each row in a decision table is a rule, and each column is a condition, an action, or another rule attribute. After you create and upload your spreadsheet decision tables, the rules you defined are compiled into Drools Rule Language (DRL) rules as with all other rule assets. All data objects related to a spreadsheet decision table must be in the same project package as the spreadsheet decision table. Assets in the same package are imported by default. Existing assets in other packages can be imported with the decision table.

Commands:
Appendix C. LVM Object Tags An LVM tag is a word that can be used to group LVM2 objects of the same type together. Tags can be attached to objects such as physical volumes, volume groups, and logical volumes. Tags can be attached to hosts in a cluster configuration. Snapshots cannot be tagged. Tags can be given on the command line in place of PV, VG or LV arguments. Tags should be prefixed with @ to avoid ambiguity. Each tag is expanded by replacing it with all objects possessing that tag which are of the type expected by its position on the command line. LVM tags are strings using [A-Za-z0-9_+.-] of up to 128 characters. They cannot start with a hyphen. Only objects in a volume group can be tagged. Physical volumes lose their tags if they are removed from a volume group; this is because tags are stored as part of the volume group metadata and that is deleted when a physical volume is removed. Snapshots cannot be tagged. The following command lists all the logical volumes with the database tag. C.1. Adding and Removing Object Tags To add or delete tags from physical volumes, use the --addtag or --deltag option of the pvchange command. To add or delete tags from volume groups, use the --addtag or --deltag option of the vgchange or vgcreate commands. To add or delete tags from logical volumes, use the --addtag or --deltag option of the lvchange or lvcreate commands.

Commands:
lvs @database
2.6. Allowing Read-Only Access to the History Database To allow access to the history database without allowing edits, you must create a read-only PostgreSQL user that can log in to and read from the ovirt_engine_history database. This procedure must be executed on the system on which the history database is installed. Allowing Read-Only Access to the History Database Enable psql commands: Create the user to be granted read-only access to the history database: Grant the newly created user permission to connect to the history database: Grant the newly created user usage of the public schema: Generate the rest of the permissions that will be granted to the newly created user and save them to a file: Use the file you created in the step to grant permissions to the newly created user: Remove the file you used to grant permissions to the newly created user: Exit the postgres user shell by pressing Ctrl + d . Add the following lines for the newly created user to /var/opt/rh/rh-postgresql10/lib/pgsql/data/pg_hba.conf preceding the line beginning local all all , as follows: Reload the PostgreSQL service: To test the read-only user's access permissions: To exit the ovirt_engine_history database, enter \q . The read-only user's SELECT statements against tables and views in the ovirt_engine_history database succeed, while modifications fail.

Commands:
su - postgres -c 'scl enable rh-postgresql10 bash'
psql -U postgres -c "CREATE ROLE username WITH LOGIN ENCRYPTED PASSWORD ' password ';" -d ovirt_engine_history
psql -U postgres -c "GRANT CONNECT ON DATABASE ovirt_engine_history TO username ;"
psql -U postgres -c "GRANT USAGE ON SCHEMA public TO username ;" ovirt_engine_history
psql -U postgres -c "SELECT 'GRANT SELECT ON ' || relname || ' TO username ;' FROM pg_class JOIN pg_namespace ON pg_namespace.oid = pg_class.relnamespace WHERE nspname = 'public' AND relkind IN ('r', 'v');" --pset=tuples_only=on ovirt_engine_history > grant.sql
psql -U postgres -f grant.sql ovirt_engine_history
rm grant.sql
TYPE DATABASE USER ADDRESS METHOD host ovirt_engine_history username 0.0.0.0/0 md5 host ovirt_engine_history username ::0/0 md5 local all all peer
systemctl reload rh-postgresql10-postgresql
su - postgres -c 'scl enable rh-postgresql10 -- psql -U username ovirt_engine_history -h localhost' Password for user username: psql (9.2.23) Type "help" for help. ovirt_engine_history=>
Chapter 10. Using the AMQ Interconnect web console to monitor the router network You can use the AMQ Interconnect web console to monitor the status and performance of your router network. By default, when you create a router deployment, the AMQ Interconnect Operator generates the credentials to access the console and stores them in a Secret. Procedure In OpenShift, switch to Networking Routes , and click the console Route. The web console opens in a new tab. To connect to the web console, complete the following fields: Port Enter 443 . User name Enter the user name. To find the user name and password for accessing the web console, navigate to Workloads Secrets . The Secret containing the web console credentials is called < application-name >-users (for example, router-mesh-users ). The syntax for the user name is < user >@< domain > (the domain is the OpenShift application name, which is the name of the Custom Resource that describes the router deployment). For example, guest@router-mesh . Password Enter the password defined in the < application-name >-users Secret. Click Connect . The Routers page is displayed showing all of the routers in the router network. Use the web console tabs to monitor the router network. This tab... Provides... Overview Aggregated information about routers, addresses, links, connections, and logs. Entities Detailed information about each AMQP management entity for each router in the router network. Some of the attributes have charts that you can add to the Charts tab. Topology A graphical view of the router network, including routers, clients, and brokers. The topology shows how the routers are connected, and how messages are flowing through the network. Charts Graphs of the information selected on the Entities tab. Message Flow A chord diagram showing the real-time message flow by address. Schema The management schema that controls each of the routers in the router network.

Commands:
Chapter 13. Define the LDAP login domain When you are setting up Red Hat Decision Manager to use LDAP for authentication and authorization, define the LDAP login domain because the Git SSH authentication may use another security domain. To define the LDAP login domain, use the org.uberfire.domain system property. For example, on Red Hat JBoss Enterprise Application Platform, add this property in the standalone.xml file as shown: Ensure that the authenticated user has appropriate roles ( admin , analyst , reviewer ) associated with it in LDAP.

Commands:
<system-properties> <!-- other system properties --> <property name="org.uberfire.domain" value="LDAPAuth"/> </system-properties>
7.161. numactl 7.161.1. RHBA-2013:0401 - numactl bug fix and enhancement update Updated numactl packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The numactl packages provide a simple Non-Uniform Memory Access (NUMA) policy support and consist of the numactl program to run other programs with a specific NUMA policy and the libnuma library to do allocations in applications using the NUMA policy. Bug Fixes BZ#804480 Previously, the number of CPUs were miscalculated in the "/sys/devices/system/cpu" directory, because the "cpufreq" and "cpuidle" files were counted, so, the additional two CPUs were added erroneously. With this update, the number of CPUs is now counted correctly. BZ# 814294 The global pointer "numa_all_cpus_ptr" was supposed to be set to a bitmask allocated by the library with bits that represent all CPUs on which the calling thread can execute. Consequently, it did not function as documented when the bitmask was only set to CPU0. With this update, the underlying source code is now fixed and the "numa_all_cpus_ptr" contains only specified CPUs, when the taskset option contains CPU0. Enhancement BZ#829896 The existing tool numastat, which was a Perl script, was rewritten to a C program to provide much more NUMA information. The default operation of numastat will remain the same for compatibility with current users' end scripts. Users of numactl are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands: