mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Installation environment options for Red Hat Process Automation Manager With Red Hat Process Automation Manager, you can set up a development environment to develop business applications, a runtime environment to run those applications to support decisions, or both. Development environment : Typically consists of one Business Central installation and at least one KIE Server installation. You can use Business Central to design decisions and other artifacts, and you can use KIE Server to execute and test the artifacts that you created. Runtime environment : Consists of one or more KIE Server instances with or without Business Central. Business Central has an embedded Process Automation Manager controller. If you install Business Central, use the Menu Deploy Execution servers page to create and maintain containers. If you want to automate KIE Server management without Business Central, you can use the headless Process Automation Manager controller. You can also cluster both development and runtime environments. A clustered development or runtime environment consists of a unified group or cluster of two or more servers. The primary benefit of clustering Red Hat Process Automation Manager development environments is high availability and enhanced collaboration, while the primary benefit of clustering Red Hat Process Automation Manager runtime environments is high availability and load balancing. High availability decreases the chance of data loss when a single server fails. When a server fails, another server fills the gap by providing a copy of the data that was on the failed server. When the failed server comes online again, it resumes its place in the cluster. Note Clustering of the runtime environment is currently supported on Red Hat JBoss EAP 7.4 and Red Hat OpenShift Container Platform only. Additional resources Planning a Red Hat Process Automation Manager installation Red Hat Process Automation Manager 7 Supported Configurations Red Hat Process Automation Manager 7 Component Details

Commands:
2.2.3.4. Assign Static Ports and Use iptables Rules All of the servers related to NIS can be assigned specific ports except for rpc.yppasswdd - the daemon that allows users to change their login passwords. Assigning ports to the other two NIS server daemons, rpc.ypxfrd and ypserv , allows for the creation of firewall rules to further protect the NIS server daemons from intruders. To do this, add the following lines to /etc/sysconfig/network : The following iptables rules can then be used to enforce which network the server listens to for these ports: This means that the server only allows connections to ports 834 and 835 if the requests come from the 192.168.0.0/24 network, regardless of the protocol. Note Refer to Section 2.8, "Firewalls" for more information about implementing firewalls with iptables commands.

Commands:
YPSERV_ARGS="-p 834" YPXFRD_ARGS="-p 835"
~]# iptables -A INPUT -p ALL -s ! 192.168.0.0/24 --dport 834 -j DROP ~]# iptables -A INPUT -p ALL -s ! 192.168.0.0/24 --dport 835 -j DROP
Appendix E. Proxies E.1. SPICE Proxy E.1.1. SPICE Proxy Overview The SPICE Proxy is a tool used to connect SPICE Clients to virtual machines when the SPICE Clients are outside the network that connects the hypervisors. Setting up a SPICE Proxy consists of installing Squid on a machine and configuring the firewall to allow proxy traffic. Turning a SPICE Proxy on consists of using engine-config on the Manager to set the key SpiceProxyDefault to a value consisting of the name and port of the proxy. Turning a SPICE Proxy off consists of using engine-config on the Manager to remove the value to which the key SpiceProxyDefault has been set. Important The SPICE Proxy can only be used in conjunction with the standalone SPICE client, and cannot be used to connect to virtual machines using noVNC. E.1.2. SPICE Proxy Machine Setup This procedure explains how to set up a machine as a SPICE Proxy. A SPICE Proxy makes it possible to connect to the Red Hat Virtualization network from outside the network. We use Squid in this procedure to provide proxy services. Installing Squid on Red Hat Enterprise Linux Install Squid on the Proxy machine: Open /etc/squid/squid.conf . Change: to: Start the squid service and enable it to run automatically after reboot: Enable incoming requests to the squid service in the default firewalld zone: Make this firewall rule persistent in the runtime configuration: Confirm that the squid service appears in the list of firewall services: You have now set up a machine as a SPICE proxy. Before connecting to the Red Hat Virtualization network from outside the network, activate the SPICE proxy. E.1.3. Turning On a SPICE Proxy This procedure explains how to activate (or turn on) the SPICE proxy. Activating SPICE Proxy On the Manager, use the engine-config tool to set a proxy: Restart the ovirt-engine service: The proxy must have this form: Note Only SPICE clients shipped with Red Hat Enterprise Linux 6.7, Red Hat Enterprise Linux 7.2, or later, support HTTPS proxies. Earlier clients only support HTTP. If HTTPS is specified for earlier clients, the client will ignore the proxy setting and attempt a direct connection to the host. SPICE Proxy is now activated (turned on). It is now possible to connect to the Red Hat Virtualization network through the SPICE proxy. E.1.4. Turning Off a SPICE Proxy This procedure explains how to turn off (deactivate) a SPICE proxy. Turning Off a SPICE Proxy Log in to the Manager: Run the following command to clear the SPICE proxy: Restart the Manager: SPICE proxy is now deactivated (turned off). It is no longer possible to connect to the Red Hat Virtualization network through the SPICE proxy.

Commands:
yum install squid
http_access deny CONNECT !SSL_ports
http_access deny CONNECT !Safe_ports
systemctl enable squid.service --now
firewall-cmd --permanent --add-service=squid
firewall-cmd --reload
firewall-cmd --list-services ssh dhcpv6-client squid
engine-config -s SpiceProxyDefault=someProxy
systemctl restart ovirt-engine.service
protocol://[host]:[port]
ssh root@ [IP of Manager]
engine-config -s SpiceProxyDefault=""
systemctl restart ovirt-engine.service
8.211. suitesparse 8.211.1. RHBA-2013:0988 - suitesparse bug fix update Updated suitesparse packages that fix one bug are now available for Red Hat Enterprise Linux 6. The suitesparse packages are a collection of libraries for computations involving sparse matrices. Bug Fix BZ#902854 The suitesparse base package was missing a copy of the General Public License (GPL). The license was included in the suitesparse-doc subpackage, but it was possible to install suitesparse without the suitesparse-doc subpackage. With this update, a copy of the license is now included also in the base package. Users of suitesparse are advised to upgrade to these updated packages, which fix this bug.

Commands:
probe::vm.kmem_cache_alloc Name probe::vm.kmem_cache_alloc - Fires when \ Synopsis Values ptr Pointer to the kmemory allocated caller_function Name of the caller function. call_site Address of the function calling this kmemory function. gfp_flag_name Type of kmemory to allocate(in string format) name Name of the probe point bytes_req Requested Bytes bytes_alloc Allocated Bytes gfp_flags type of kmemory to allocate Description kmem_cache_alloc is requested.

Commands:
vm.kmem_cache_alloc
Chapter 2. Server Initialization After performing all the installation and configuration tasks defined in the Server Installation and Configuration Guide , you will need to create an initial admin account. Red Hat Single Sign-On does not have any configured admin account out of the box. This account will allow you to create an admin that can log into the master realm's administration console so that you can start creating realms, users and registering applications to be secured by Red Hat Single Sign-On. If your server is accessible from localhost , you can boot it up and create this admin user by going to the http://localhost:8080/auth URL. Welcome Page Simply specify the username and password you want for this initial admin. If you cannot access the server via a localhost address, or just want to provision Red Hat Single Sign-On from the command line you can do this with the ... /bin/add-user-keycloak script. add-user-keycloak script The parameters are a little different depending if you are using the standalone operation mode or domain operation mode. For standalone mode, here is how you use the script. Linux/Unix Windows For domain mode, you have to point the script to one of your server hosts using the -sc switch. Linux/Unix Windows

Commands:
.../bin/add-user-keycloak.sh -r master -u <username> -p <password>
> ...\bin\add-user-keycloak.bat -r master -u <username> -p <password>
.../bin/add-user-keycloak.sh --sc domain/servers/server-one/configuration -r master -u <username> -p <password>
> ...\bin\add-user-keycloak.bat --sc domain/servers/server-one/configuration -r master -u <username> -p <password>
23.4. Configure the Install Terminal If you logged in with ssh and X11 forwarding, anaconda starts immediately with its graphical user interface. If you did not set the display= variable and do not use X11 forwarding, anaconda gives you the choice of starting VNC or text mode. Figure 23.1. Choosing VNC or text mode If you choose VNC, you will be asked for a password or you can choose to use VNC without a password. If you use a password, make a note of the password for future reference. The VNC server then starts. Figure 23.2. The VNC server starts Now open a connection to the IP address of your z/VM guest virtual machine using a VNC client. Authenticate to the VNC server with the previously entered password.

Commands:
8.218. shared-mime-info 8.218.1. RHBA-2014:0555 - shared-mime-info bug fix update Updated shared-mime-info packages that fix one bug are now available for Red Hat Enterprise Linux 6. The shared-mime-info packages contain the core database of common types. Programs and desktops consult the MIME database to determine the correct MIME type for a file. Bug Fix BZ# 974505 Due to optimizations performed by the Anaconda installer, the glib2 packages, which the shared-mime-info packages depend on, were not yet installed when the shared-mime-info's post-installation script was run. As a consequence, a harmless error message was reported. This update adds an explicit dependency on glib2 for the post-installation script to only run after the glib2 packages have been installed, and the errors no longer occur in the described situation. Users of shared-mime-info are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 31. Best practices for automation controller The following describes best practice for the use of automation controller: 31.1. Use Source Control Automation controller supports playbooks stored directly on the server. Therefore, you must store your playbooks, roles, and any associated details in source control. This way you have an audit trail describing when and why you changed the rules that are automating your infrastructure. Additionally, it permits sharing of playbooks with other parts of your infrastructure or team. 31.2. Ansible file and directory structure If you are creating a common set of roles to use across projects, these should be accessed through source control submodules, or a common location such as /opt . Projects should not expect to import roles or content from other projects. For more information, see the link General tips from the Ansible documentation. Note Avoid using the playbooks vars_prompt feature, as automation controller does not interactively permit vars_prompt questions. If you cannot avoid using vars_prompt , see the Surveys functionality. Avoid using the playbooks pause feature without a timeout, as automation controller does not permit canceling a pause interactively. If you cannot avoid using pause , you must set a timeout. Jobs use the playbook directory as the current working directory, although jobs must be coded to use the playbook_dir variable rather than relying on this. 31.3. Use Dynamic Inventory Sources If you have an external source of truth for your infrastructure, whether it is a cloud provider or a local CMDB, it is best to define an inventory sync process and use the support for dynamic inventory (including cloud inventory sources). This ensures your inventory is always up to date. Note Edits and additions to Inventory host variables persist beyond an inventory synchronization as long as --overwrite_vars is not set. 31.4. Variable Management for Inventory Keep variable data with the hosts and groups definitions (see the inventory editor), rather than using group_vars/ and host_vars/ . If you use dynamic inventory sources, automation controller can synchronize such variables with the database as long as the Overwrite Variables option is not set. 31.5. Autoscaling Use the "callback" feature to permit newly booting instances to request configuration for auto-scaling scenarios or provisioning integration. 31.6. Larger Host Counts Set "forks" on a job template to larger values to increase parallelism of execution runs. For more information on tuning Ansible, see the Ansible blog . 31.7. Continuous integration / Continuous Deployment For a Continuous Integration system, such as Jenkins, to spawn a job, it must make a curl request to a job template. The credentials to the job template must not require prompting for any particular passwords. For configuration and use instructions, see Installation in the Ansible documentation.

Commands:
2.2.2. Minimal USB Boot Media for UEFI-based Systems Warning When you perform this procedure any data on the USB flash drive is destroyed with no warning. Make sure that you specify the correct USB flash drive, and make sure that this flash drive does not contain any data that you want to keep. To creater minimal USB boot media for Red Hat Enterprise Linux, use the efidisk.img file in the images/ directory on the Red Hat Enterprise Linux 6.9 installation DVD: Download an ISO image file of the Red Hat Enterprise Linux 6.9 installation DVD as described in Chapter 1, Obtaining Red Hat Enterprise Linux . Become root: Create a mount point for the ISO image file: Mount the image file: Where DVD.iso is the name of the ISO image file, for example RHEL6.9-Server-x86_64-DVD.iso . Transfer efidisk.img from the ISO image file to your USB flash drive: For example: Note Use the dd command to write the image file directly to the device. Using cp to copy the file or transferring the file using a file manager will make the device unbootable. Unmount the ISO image file:

Commands:
su -
mkdir /mnt/dvdiso
mount DVD.iso /mnt/dvdiso -o loop
dd if=/mnt/dvdiso/images/efidisk.img of=/dev/ device_name
dd if=/mnt/dvdiso/images/efidisk.img of=/dev/sdc
umount /mnt/dvdiso
Chapter 60. request This chapter describes the commands under the request command. 60.1. request token authorize Authorize a request token Usage: Table 60.1. Command arguments Value Summary -h, --help Show this help message and exit --request-key <request-key> Request token to authorize (id only) (required) --role <role> Roles to authorize (name or id) (repeat option to set multiple values) (required) Table 60.2. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns Table 60.3. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 60.4. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 60.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show. 60.2. request token create Create a request token Usage: Table 60.6. Command arguments Value Summary -h, --help Show this help message and exit --consumer-key <consumer-key> Consumer key (required) --consumer-secret <consumer-secret> Consumer secret (required) --project <project> Project that consumer wants to access (name or id) (required) --domain <domain> Domain owning <project> (name or id) Table 60.7. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns Table 60.8. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 60.9. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 60.10. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack request token authorize [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] --request-key <request-key> --role <role>
openstack request token create [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] --consumer-key <consumer-key> --consumer-secret <consumer-secret> --project <project> [--domain <domain>]
5.149. libgweather 5.149.1. RHBA-2012:0381 - libgweather bug fix update An updated libgweather package that fixes one bug is now available for Red Hat Enterprise Linux 6. The libgweather library is used by applications to access weather information from online services for numerous locations. Bug Fix BZ# 704105 Previously, the libgweather library did not contain information for the city of Jerusalem, making it impossible to search for the city or select the city from the list of cities offered by the weather panel applet. This update adds the missing information to the libgweather database, so that users can now select Jerusalem as a valid option. All users of libgweather are advised to upgrade to this updated package, which fixes this bug.

Commands:
4.369. db4 4.369.1. RHBA-2013:1443 - db4 bug fix update Updated db4 packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Berkeley Database (Berkeley DB) is a programmatic toolkit that provides embedded database support for both traditional and client/server applications. The Berkeley DB includes B+tree, Extended Linear Hashing, Fixed and Variable-length record access methods, transactions, locking, logging, shared memory caching, and database recovery. The Berkeley DB supports C, C++, Java, and Perl APIs. It is used by many applications, including Python and Perl, so this should be installed on all systems. Bug Fix BZ# 1012585 Due to an incorrect order of the mutex initialization calls, the rpm utility became unresponsive under certain circumstances, until it was terminated. With this update, the order of the mutex initialization calls has been revised. As a result, the rpm utility no longer becomes unresponsive. Users of db4 are advised to upgrade to these updated packages, which fix this bug.

Commands:
Part I. Managing and monitoring KIE Server As a system administrator, you can install, configure, and upgrade Red Hat Decision Manager for production environments, quickly and easily troubleshoot system failures, and ensure that systems are running optimally. Prerequisites Red Hat JBoss Enterprise Application Platform 7.4 is installed. For more information, see Red Hat JBoss Enterprise Application Platform 7.4 Installation Guide . Red Hat Decision Manager is installed. For more information, see Planning a Red Hat Decision Manager installation . Red Hat Decision Manager is running and you can log in to Business Central with the admin role. For more information, see Planning a Red Hat Decision Manager installation .

Commands:
7.147. mod_nss 7.147.1. RHBA-2013:0513 - mod_nss bug fix and enhancement update Updated mod_nss packages that fix one bug and add two enhancements are now available for Red Hat Enterprise Linux 6. The mod_nss module provides strong cryptography for the Apache HTTP Server via the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, using the Network Security Services (NSS) security library. Bug Fix BZ#769906 The mod_nss module reported 'Required value NSSCipherSuite not set.' even though a value for NSSCipherSuite was present in the virtual host. This bug was a configuration issue which was exacerbated by a couple of confusing log messages. As a result, several log messages were changed to help clarify what values were actually missing. Enhancements BZ#816394 Added support for TLSv1.1 to mod_nss module. BZ#835071 Added the ability to share mod_proxy with other SSL providers. Users of mod_nss are advised to upgrade to these updated packages, which fix this bug and add these enhancements.

Commands:
Chapter 17. Red Hat Enterprise Linux Atomic Host 7.6.1 17.1. Atomic Host OStree update : New Tree Version: 7.6.1 (hash: 0092a3e37c7d42296dab2d4b2a131e513b45d984a2ea2a8f2a38b394c6a9f81d) Changes since Tree Version 7.6.0 (hash: 4330ddfb4b9f84c63edcea17928cd5cf1f8688e3e3297a63c18097defebf97a4) 17.2. Extras Updated packages : buildah-1.4-3.gitc8ed967.el7 cockpit-176-4.el7 libssh-0.7.1-7.el7 python-docker-py-1.10.6-7.el7 lorax-composer-19.7.27-1.el7 docker-1.13.1-84.git07f3374.el7 podman-0.11.1.1-3.git594495d.el7 driverctl-0.101-1.el7 dpdk-17.11-15.el7 oci-umount-2.3.4-2.git87f9237.el7 runc-1.0.0-54.dev.git2abd837.el7 skopeo-0.1.31-7.gitb0b750d.el7 oci-systemd-hook-0.1.18-2.git3efe246.el7 container-selinux-2.74-1.el7 atomic-1.22.1-26.gitb507039.el7 rhel-system-roles-1.0-5.el7 dnf-2.7.5-19.el7_6 17.2.1. Container Images Updated : Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux 7.6 Container Image (rhel7.6, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux 7.6 Container Image for aarch64 (rhel7.6, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic OpenSCAP Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel)

Commands: