mtpti5iD/redhat-docs_dataset huggingface dataset:
Workloads APIs OpenShift Container Platform 4.18 Reference guide for workloads APIs Red Hat OpenShift Documentation Team

Commands:
"postCommit": { "script": "rake test --verbose", }
The above is a convenient form which is equivalent to:
"postCommit": { "command": ["/bin/sh", "-ic"], "args": ["rake test --verbose"] }
"postCommit": { "commit": ["rake", "test", "--verbose"] }
Command overrides the image entrypoint in the exec form, as documented in Docker: https://docs.docker.com/engine/reference/builder/#entrypoint.
"postCommit": { "args": ["rake", "test", "--verbose"] }
This form is only useful if the image entrypoint can handle arguments.
"postCommit": { "script": "rake test USD1", "args": ["--verbose"] }
This form is useful if you need to pass arguments that would otherwise be hard to quote properly in the shell script. In the script, USD0 will be "/bin/sh" and USD1, USD2, etc, are the positional arguments from Args.
"postCommit": { "command": ["rake", "test"], "args": ["--verbose"] }
This form is equivalent to appending the arguments to the Command slice.
"postCommit": { "script": "rake test --verbose", }
The above is a convenient form which is equivalent to:
"postCommit": { "command": ["/bin/sh", "-ic"], "args": ["rake test --verbose"] }
"postCommit": { "commit": ["rake", "test", "--verbose"] }
Command overrides the image entrypoint in the exec form, as documented in Docker: https://docs.docker.com/engine/reference/builder/#entrypoint.
"postCommit": { "args": ["rake", "test", "--verbose"] }
This form is only useful if the image entrypoint can handle arguments.
"postCommit": { "script": "rake test USD1", "args": ["--verbose"] }
This form is useful if you need to pass arguments that would otherwise be hard to quote properly in the shell script. In the script, USD0 will be "/bin/sh" and USD1, USD2, etc, are the positional arguments from Args.
"postCommit": { "command": ["rake", "test"], "args": ["--verbose"] }
This form is equivalent to appending the arguments to the Command slice.
Chapter 1. Installing and preparing the Operators You install the Red Hat OpenStack Services on OpenShift (RHOSO) OpenStack Operator ( openstack-operator ) and create the RHOSO control plane on an operational Red Hat OpenShift Container Platform (RHOCP) cluster. You install the OpenStack Operator by using the RHOCP web console. You perform the control plane installation tasks and all data plane creation tasks on a workstation that has access to the RHOCP cluster. 1.1. Prerequisites An operational RHOCP cluster, version 4.16. For the RHOCP system requirements, see Red Hat OpenShift Container Platform cluster requirements in Planning your deployment . The oc command line tool is installed on your workstation. You are logged in to the RHOCP cluster as a user with cluster-admin privileges. 1.2. Installing the OpenStack Operator You use OperatorHub on the Red Hat OpenShift Container Platform (RHOCP) web console to install the OpenStack Operator ( openstack-operator ) on your RHOCP cluster. Procedure Log in to the RHOCP web console as a user with cluster-admin permissions. Select Operators OperatorHub . In the Filter by keyword field, type OpenStack . Click the OpenStack Operator tile with the Red Hat source label. Read the information about the Operator and click Install . On the Install Operator page, select "Operator recommended Namespace: openstack-operators" from the Installed Namespace list. Click Install to make the Operator available to the openstack-operators namespace. The Operators are deployed and ready when the Status of the OpenStack Operator is Succeeded .

Commands:
Chapter 40. Removing Red Hat Enterprise Linux from IBM System z If you want to delete the existing operating system data, first, if any Linux disks contain sensitive data, ensure that you destroy the data according to your security policy. To proceed you can consider these options: Overwrite the disks with a new installation. Start a new installation and use the partitioning dialog (refer to Section 23.13, "Disk Partitioning Setup" ) to format the partitions where Linux was installed. After the Write changes to disk dialog described in Section 23.16, "Write Changes to Disk" , exit the installer. Make the DASD or SCSI disk where Linux was installed visible from another system, then delete the data. However, this might require special privileges. Ask your system administrator for advice. You can use Linux commands such as dasdfmt (DASD only), parted , mke2fs or dd . For more details about the commands, refer to the respective man pages. 40.1. Running a Different Operating System on your z/VM Guest or LPAR If you want to boot from a DASD or SCSI disk different from where the currently installed system resides under a z/VM guest virtual machine or an LPAR, shut down the Red Hat Enterprise Linux installed and use the desired disk, where another Linux instance is installed, to boot from. This leaves the contents of the installed system unchanged.

Commands:
8.4.2.2. cpio The cpio utility is another traditional UNIX program. It is an excellent general-purpose program for moving data from one place to another and, as such, can serve well as a backup program. The behavior of cpio is a bit different from tar . Unlike tar , cpio reads the names of the files it is to process via standard input. A common method of generating a list of files for cpio is to use programs such as find whose output is then piped to cpio : This command creates a cpio archive file (containing the everything in /home/ ) called home-backup.cpio and residing in the /mnt/backup/ directory. Note Because find has a rich set of file selection tests, sophisticated backups can easily be created. For example, the following command performs a backup of only those files that have not been accessed within the past year: There are many other options to cpio (and find ); to learn more about them read the cpio(1) and find(1) man pages.

Commands:
find /home/ | cpio -o > /mnt/backup/home-backup.cpio
find /home/ -atime +365 | cpio -o > /mnt/backup/home-backup.cpio
B.65. pango B.65.1. RHSA-2011:0180 - Moderate: pango security update Updated pango and evolution28-pango packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Pango is a library used for the layout and rendering of internationalized text. CVE-2011-0020 An input sanitization flaw, leading to a heap-based buffer overflow, was found in the way Pango displayed font files when using the FreeType font engine back end. If a user loaded a malformed font file with an application that uses Pango, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. Users of pango and evolution28-pango are advised to upgrade to these updated packages, which contain a backported patch to resolve this issue. After installing the updated packages, you must restart your system or restart your X session for the update to take effect.

Commands:
15.2.6. Querying Use the rpm -q command to query the database of installed packages. The rpm -q foo command displays the package name, version, and release number of the installed package foo : Note To query a package, replace foo with the actual package name. Instead of specifying the package name, use the following options with -q to specify the package(s) you want to query. These are called Package Selection Options . -a queries all currently installed packages. -f <file> queries the package which owns <file> . When specifying a file, you must specify the full path of the file (for example, /bin/ls ). -p <packagefile> queries the package <packagefile> . There are a number of ways to specify what information to display about queried packages. The following options are used to select the type of information for which you are searching. These are called Information Query Options . -i displays package information including name, description, release, size, build date, install date, vendor, and other miscellaneous information. -l displays the list of files that the package contains. -s displays the state of all the files in the package. -d displays a list of files marked as documentation (man pages, info pages, READMEs, etc.). -c displays a list of files marked as configuration files. These are the files you change after installation to adapt the package to your system (for example, sendmail.cf , passwd , inittab , etc.). For the options that display lists of files, add -v to the command to display the lists in a familiar ls -l format.

Commands:
foo-2.0-1
2.2.4.2.2. Review the NFS Client Use the nosuid option to disallow the use of a setuid program. The nosuid option disables the set-user-identifier or set-group-identifier bits. This prevents remote users from gaining higher privileges by running a setuid program. Use this option on the client and the server side. The noexec option disables all executable files on the client. Use this to prevent users from inadvertently executing files placed in the file system being shared. The nosuid and noexec options are standard options for most, if not all, file systems. Use the nodev option to prevent " device-files " from being processed as a hardware device by the client. The resvport option is a client-side mount option and secure is the corresponding server-side export option (see explanation above). It restricts communication to a "reserved port". The reserved or "well known" ports are reserved for privileged users and processes such as the root user. Setting this option causes the client to use a reserved source port to communicate with the server. All versions of NFS now support mounting with Kerberos authentication. The mount option to enable this is: sec=krb5 . NFSv4 supports mounting with Kerberos using krb5i for integrity and krb5p for privacy protection. These are used when mounting with sec=krb5 , but need to be configured on the NFS server. Refer to the man page on exports ( man 5 exports ) for more information. The NFS man page ( man 5 nfs ) has a " SECURITY CONSIDERATIONS " section which explains the security enhancements in NFSv4 and contains all the NFS specific mount options.

Commands:
9.2. Permissions Access to a CacheManager or a Cache is controlled using a set of required permissions. Permissions control the type of action that is performed on the CacheManager or Cache, rather than the type of data being manipulated. Some of these permissions can apply to specifically name entities, such as a named cache. Different types of permissions are available depending on the entity. Table 9.1. CacheManager Permissions Permission Function Description CONFIGURATION defineConfiguration Whether a new cache configuration can be defined. LISTEN addListener Whether listeners can be registered against a cache manager. LIFECYCLE stop, start Whether the cache manager can be stopped or started respectively. ALL A convenience permission which includes all of the above. Table 9.2. Cache Permissions Permission Function Description READ get, contains Whether entries can be retrieved from the cache. WRITE put, putIfAbsent, replace, remove, evict Whether data can be written/replaced/removed/evicted from the cache. EXEC distexec, mapreduce Whether code execution can be run against the cache. LISTEN addListener Whether listeners can be registered against a cache. BULK_READ keySet, values, entrySet,query Whether bulk retrieve operations can be executed. BULK_WRITE clear, putAll Whether bulk write operations can be executed. LIFECYCLE start, stop Whether a cache can be started / stopped. ADMIN getVersion, addInterceptor*, removeInterceptor, getInterceptorChain, getEvictionManager, getComponentRegistry, getDistributionManager, getAuthorizationManager, evict, getRpcManager, getCacheConfiguration, getCacheManager, getInvocationContextContainer, setAvailability, getDataContainer, getStats, getXAResource Whether access to the underlying components/internal structures is allowed. ALL A convenience permission which includes all of the above. ALL_READ Combines READ and BULK_READ. ALL_WRITE Combines WRITE and BULK_WRITE. Note Some permissions may need to be combined with others in order to be useful. For example, EXEC with READ or with WRITE. Report a bug

Commands:
Chapter 11. SNMP Configuration with the Red Hat High Availability Add-On As of the Red Hat Enterprise Linux 6.1 release and later, the Red Hat High Availability Add-On provides support for SNMP traps. This chapter describes how to configure your system for SNMP followed by a summary of the traps that the Red Hat High Availability Add-On emits for specific cluster events. 11.1. SNMP and the Red Hat High Availability Add-On The Red Hat High Availability Add-On SNMP subagent is foghorn , which emits the SNMP traps. The foghorn subagent talks to the snmpd daemon by means of the AgentX Protocol. The foghorn subagent only creates SNMP traps; it does not support other SNMP operations such as get or set . There are currently no config options for the foghorn subagent. It cannot be configured to use a specific socket; only the default AgentX socket is currently supported.

Commands:
Chapter 5. HighAvailability The following table lists all the packages in the High Availability add-on. For more information about core packages, see the Scope of Coverage Details document. Package Core Package? License ccs Yes GPLv2 clufter-cli No GPLv2+ clufter-lib-ccs No GPLv2+ clufter-lib-general No GPLv2+ clufter-lib-pcs No GPLv2+ cluster-cim Yes GPLv2 cluster-glue No GPLv2+ and LGPLv2+ cluster-glue-libs No GPLv2+ and LGPLv2+ cluster-glue-libs-devel Yes GPLv2+ and LGPLv2+ cluster-snmp Yes GPLv2 clusterlib No GPLv2+ and LGPLv2+ clusterlib-devel Yes GPLv2+ and LGPLv2+ cman Yes GPLv2+ and LGPLv2+ corosync No BSD corosynclib No BSD corosynclib-devel Yes BSD fence-virt No GPLv2+ fence-virtd-checkpoint Yes GPLv2+ foghorn Yes GPLv2+ libesmtp-devel Yes LGPLv2+ and GPLv2+ libqb No LGPLv2+ libqb-devel No LGPLv2+ luci Yes GPLv2 and MIT modcluster No GPLv2 omping Yes ISC openais No BSD openaislib No BSD openaislib-devel Yes BSD pacemaker Yes GPLv2+ and LGPLv2+ pacemaker-cli No GPLv2+ and LGPLv2+ pacemaker-cluster-libs No GPLv2+ and LGPLv2+ pacemaker-cts No GPLv2+ and LGPLv2+ pacemaker-doc Yes GPLv2+ and LGPLv2+ pacemaker-libs No GPLv2+ and LGPLv2+ pacemaker-libs-devel Yes GPLv2+ and LGPLv2+ pacemaker-remote No GPLv2+ and LGPLv2+ pcs Yes GPLv2 python-clufter No GPLv2+ and GFDL python-repoze-what-plugins-sql No BSD python-repoze-what-quickstart Yes BSD python-repoze-who-friendlyform No BSD python-repoze-who-plugins-sa No BSD python-tw-forms No MIT and LGPLv2+ resource-agents Yes GPLv2+ and LGPLv2+ resource-agents-sap-hana No GPLv2+ rgmanager Yes GPLv2+ and LGPLv2+ ricci No GPLv2 sbd Yes GPLv2+

Commands:
11.4. Setting Up Mandatory Extensions In GNOME Shell, you can provide a set of extensions that the user has to use. To do so, install the extensions in the /usr/share/gnome-shell/extensions directory and then lock down the org.gnome.shell.enabled-extensions and org.gnome.shell.development-tools keys. Locking down the org.gnome.shell.development-tools key ensures that the user cannot use GNOME Shell's integrated debugger and inspector tool ( Looking Glass ) to disable any mandatory extensions. Procedure 11.4. Setting up mandatory extensions Create a local database file for machine-wide settings in /etc/dconf/db/local.d/00-extensions-mandatory : The enabled-extensions key specifies the enabled extensions using the extensions' uuid ( myextension1@myname.example.com and myextension2@myname.example.com ). The development-tools key is set to false to disable access to Looking Glass . Override the user's setting and prevent the user from changing it in /etc/dconf/db/local.d/locks/extensions-mandatory : Update the system databases: Users must log out and back in again before the system-wide settings take effect.

Commands:
List all mandatory extensions enabled-extensions=[' myextension1@myname.example.com ', ' myextension2@myname.example.com '] Disable access to Looking Glass development-tools=false
Lock the list of mandatory extensions and access to Looking Glass /org/gnome/shell/enabled-extensions /org/gnome/shell/development-tools
dconf update
Chapter 8. ScalableFileSystem The following table lists all the packages in the Scalable FileSystem add-on. For more information about core packages, see the Scope of Coverage Details document. Package Core Package? License xfsdump Yes GPL+ xfsprogs Yes GPL+ and LGPLv2+ xfsprogs-devel Yes GPL+ and LGPLv2+ xfsprogs-qa-devel Yes GPL+ and LGPLv2+

Commands:
Chapter 1. Product overview Red Hat Process Automation Manager is an open-source business automation platform that combines business process management (BPM), case management, business rules management, and resource planning. It enables business and IT users to create, manage, validate, and deploy business processes, cases, and business rules. Red Hat Process Automation Manager uses a centralized repository where all resources are stored. This ensures consistency, transparency, and the ability to audit across the business. Business users can modify business logic and business processes without requiring assistance from IT personnel. Red Hat Process Automation Manager 7.13 provides increased stability, several fixed issues, and new features. Red Hat Process Automation Manager is fully supported on Red Hat OpenShift Container Platform and can be installed on various platforms. For information about the support policy for Red Hat Process Automation Manager, see the Release maintenance plan for Red Hat Decision Manager 7.x and Red Hat Process Automation Manager 7.x .

Commands:
4.353. xorg-x11-drv-intel 4.353.1. RHBA-2011:1619 - xorg-x11-drv-intel bug fix and enhancement update Updated xorg-x11-drv-intel packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-intel packages contain an Intel integrated graphics video driver for the X.Org implementation of the X Window System. The xorg-x11-drv-intel packages have been upgraded to upstream version 2.16, which provides a number of bug fixes and enhancements over the version. (BZ# 713767 ) Bug Fixes BZ# 699933 A black screen could appear when attempting to turn on a Lenovo ThinkPad T500 laptop after suspending it. As a consequence, the laptop could not recover from suspend. The source code has been modified so that Lenovo ThinkPad T500 laptops now recover from suspend successfully. BZ# 720702 Prior to this update, arithmetic rounding in the panel fitting algorithm did not work as expected. As a result, the screen was staggered in a diagonal way when scaling up the 1360x768 mode for the Intel Ironlake driver with Low-voltage differential signaling (LVDS) while the scaling mode was set to "None" or "Full aspect". This update modifies the rounding in the panel fitting algorithm so that the screen resolution can now be changed correctly. Enhancement BZ# 684313 This update adds support for future Intel embedded graphics controllers and enables additional 3D features. All users of xorg-x11-drv-intel are advised to upgrade to these updated xorg-x11-drv-intel packages, which fix these bugs and add this enhancement.

Commands:
Chapter 1. Uninstalling Red Hat OpenShift GitOps Uninstalling the Red Hat OpenShift GitOps Operator is a two-step process: Delete the Argo CD instances that were added under the default namespace of the Red Hat OpenShift GitOps Operator. Uninstall the Red Hat OpenShift GitOps Operator. Uninstalling only the Operator will not remove the Argo CD instances created. 1.1. Deleting the Argo CD instances Delete the Argo CD instances added to the namespace of the GitOps Operator. Procedure In the Terminal type the following command: USD oc delete gitopsservice cluster -n openshift-gitops Note You cannot delete an Argo CD cluster from the web console UI. After the command runs successfully all the Argo CD instances will be deleted from the openshift-gitops namespace. Delete any other Argo CD instances from other namespaces using the same command: USD oc delete gitopsservice cluster -n <namespace> 1.2. Uninstalling the GitOps Operator You can uninstall Red Hat OpenShift GitOps Operator from the OperatorHub by using the web console. Procedure From the Operators OperatorHub page, use the Filter by keyword box to search for Red Hat OpenShift GitOps tile. Click the Red Hat OpenShift GitOps tile. The Operator tile indicates it is installed. In the Red Hat OpenShift GitOps descriptor page, click Uninstall . Additional resources You can learn more about uninstalling Operators on OpenShift Container Platform in the Deleting Operators from a cluster section.

Commands:
oc delete gitopsservice cluster -n openshift-gitops
oc delete gitopsservice cluster -n <namespace>
Chapter 21. Monitoring Server and Database Activity This chapter describes monitoring database and Red Hat Directory Server logs. For information on using SNMP to monitor the Directory Server, see Section 21.10, "Monitoring Directory Server Using SNMP" . 21.1. Types of Directory Server Log Files Directory Server provides the following log types: Access log: Contains information on client connections and connection attempts to the Directory Server instance. This log type is enabled by default. Error log: Contains detailed messages of errors and events the directory experiences during normal operations. This log type is enabled by default. Warning If the Directory Server fails to write to the errors log, the server sends an error message to the Syslog service and exits. This log type is enabled by default. Audit log: Records changes made to each database as well as to server configuration. This log is not enabled by default. Audit fail log: Records failed audit events. This log is not enabled by default.

Commands:
Chapter 17. Adding Variables to the Watch List Overview By adding variables to the watch list, you can focus on particular variables to see whether their values change as expected as they flow through the routing context. Procedure To add a variable to the watch list: If necessary, start the debugger. See Chapter 14, Running the Camel Debugger . In the Variables view, right-click a variable you want to track to open the context menu. Select Watch . A new view, Expressions , opens to the Breakpoints view. The Expressions view displays the name of the variable being watched and its current value, for example: Repeat [watch1] and [watch2] to add additional variables to the watch list. Note The variables you add remain in the watch list until you remove them. To stop watching a variable, right-click it in the list to open the context menu, and then click Remove . With the Expressions view open, step through the routing context to track how the value of each variable in the watch list changes as it reaches each step in the route. Related topics Chapter 16, Changing Variable Values

Commands: