mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 5. Managing Red Hat High Availability Add-On With Conga This chapter describes various administrative tasks for managing Red Hat High Availability Add-On and consists of the following sections: Section 5.1, "Adding an Existing Cluster to the luci Interface" Section 5.2, "Removing a Cluster from the luci Interface" Section 5.3, "Managing Cluster Nodes" Section 5.4, "Starting, Stopping, Restarting, and Deleting Clusters" Section 5.5, "Managing High-Availability Services" Section 5.6, "Backing Up and Restoring the luci Configuration" 5.1. Adding an Existing Cluster to the luci Interface If you have previously created a High Availability Add-On cluster you can easily add the cluster to the luci interface so that you can manage the cluster with Conga . To add an existing cluster to the luci interface, follow these steps: Click Manage Clusters from the menu on the left side of the luci Homebase page. The Clusters screen appears. Click Add . The Add Existing Cluster screen appears. Enter the node host name for any of the nodes in the existing cluster. After you have entered the node name, the node name is reused as the ricci host name; you can override this if you are communicating with ricci on an address that is different from the address to which the cluster node name resolves. As of Red Hat Enterprise Linux 6.9, after you have entered the node name and ricci host name, the fingerprint of the certificate of the ricci host is displayed for confirmation. If it is legitimate, enter the ricci password Important It is strongly advised that you verify the certificate fingerprint of the ricci server you are going to authenticate against. Providing an unverified entity on the network with the ricci password may constitute a confidentiality breach, and communication with an unverified entity may cause an integrity breach. Since each node in the cluster contains all of the configuration information for the cluster, this should provide enough information to add the cluster to the luci interface. Click Connect . The Add Existing Cluster screen then displays the cluster name and the remaining nodes in the cluster. Enter the individual ricci passwords for each node in the cluster, or enter one password and select Use same password for all nodes . Click Add Cluster . The previously-configured cluster now displays on the Manage Clusters screen.

Commands:
7.214. time 7.214.1. RHBA-2015:0710 - time bug fix update Updated time packages that fix one bug are now available for Red Hat Enterprise Linux 6. The GNU time utility monitors the use of system resources by a program. It does so by running the program, collecting information about the resources it uses while running, and displaying the results. Bug Fix BZ# 703865 Previously, the maximum resident set size (RSS) reported by the GNU time utility was incorrect. To fix this bug, the utility has been amended to reflect the fact that Linux kernel expresses the RSS value in kilobytes, not memory pages. The GNU time utility now reports the maximum RSS value correctly. Users of time are advised to upgrade to these updated packages, which fix this bug.

Commands:
6.4. Creating Guests with PXE This section provides information on creating guests with PXE. Requirements PXE guest installation requires a PXE server running on the same subnet as the guest virtual machines you wish to install. The method of accomplishing this depends on how the virtual machines are connected to the network. Contact Support if you require assistance setting up a PXE server. PXE Installation with virt-install virt-install PXE installations require both the --network=bridge:installation parameter, where installation is the name of your bridge, and the --pxe parameter. By default, if no network is found, the guest virtual machine attempts to boot from alternative bootable devices. If there is no other bootable device found, the guest pauses. You can use the qemu-kvm boot parameter reboot-timeout to allow the guest to retry booting if no bootable device is found, like so: Example 6.2. Fully-virtualized PXE installation with virt-install Note that the command above cannot be executed in a text-only environment. A fully-virtualized ( --hvm ) guest can only be installed in a text-only environment if the --location and --extra-args "console= console_type " are provided instead of the --graphics spice parameter. Procedure 6.2. PXE installation with virt-manager Select PXE Select PXE as the installation method and follow the rest of the steps to configure the OS type, memory, CPU and storage settings. Figure 6.8. Selecting the installation method Figure 6.9. Selecting the installation type Figure 6.10. Specifying virtualized hardware details Figure 6.11. Specifying storage details Start the installation The installation is ready to start. Figure 6.12. Finalizing virtual machine details A DHCP request is sent and if a valid PXE server is found the guest virtual machine's installation processes will start. After the installation completes, you can connect to the guest operating system. For more information, see Section 6.5, "Connecting to Virtual Machines"

Commands:
qemu-kvm -boot reboot-timeout=1000
virt-install --hvm --connect qemu:///system --network=bridge:installation --pxe --graphics spice --name rhel6-machine --ram=756 --vcpus=4 --os-type=linux --os-variant=rhel6 --disk path=/var/lib/libvirt/images/rhel6-machine.img,size=10
1.2. Installing Pacemaker configuration tools You can use the following yum install command to install the Red Hat High Availability Add-On software packages along with all available fence agents from the High Availability channel. Alternately, you can install the Red Hat High Availability Add-On software packages along with only the fence agent that you require with the following command. The following command displays a listing of the available fence agents. The lvm2-cluster and gfs2-utils packages are part of ResilientStorage channel. You can install them, as needed, with the following command. Warning After you install the Red Hat High Availability Add-On packages, you should ensure that your software update preferences are set so that nothing is installed automatically. Installation on a running cluster can cause unexpected behaviors.

Commands:
yum install pcs pacemaker fence-agents-all
yum install pcs pacemaker fence-agents- model
rpm -q -a | grep fence fence-agents-rhevm-4.0.2-3.el7.x86_64 fence-agents-ilo-mp-4.0.2-3.el7.x86_64 fence-agents-ipmilan-4.0.2-3.el7.x86_64
yum install lvm2-cluster gfs2-utils
Chapter 7. Configuring the SSI filter You can configure filter-based Server Side Includes (SSI) support for JBoss Web Server to enable dynamic generation of content in existing HTML pages. Note SSI directives do not work if you try to configure the SSI filter as in versions. Procedure Open the conf/web.xml file. In the web.xml file, uncomment the following block: <mime-mapping> <extension>shtml</extension> <mime-type>text/x-server-parsed-html</mime-type> </mime-mapping>

Commands:
<mime-mapping> <extension>shtml</extension> <mime-type>text/x-server-parsed-html</mime-type> </mime-mapping>
Chapter 3. Creating a data science project To implement a data science workflow, you must create a project. In OpenShift, a project is a Kubernetes namespace with additional annotations, and is the main way that you can manage user access to resources. A project organizes your data science work in one place and also allows you to collaborate with other developers and data scientists in your organization. Within a project, you can add the following functionality: Connections so that you can access data without having to hardcode information like endpoints or credentials. Workbenches for working with and processing data, and for developing models. Deployed models so that you can test them and then integrate them into intelligent applications. Deploying a model makes it available as a service that you can access by using an API. Pipelines for automating your ML workflow. Prerequisites You have logged in to Red Hat OpenShift AI. If you are using OpenShift AI groups, you are part of the user group or admin group (for example, rhoai-users or rhoai-admins ) in OpenShift. You have the appropriate roles and permissions to create projects. Procedure From the OpenShift AI dashboard, select Data Science Projects . The Data Science Projects page shows a list of projects that you can access. For each user-requested project in the list, the Name column shows the project display name, the user who requested the project, and the project description. Click Create project . In the Create project dialog, update the Name field to enter a unique display name for your project. Optional: If you want to change the default resource name for your project, click Edit resource name . The resource name is what your resource is labeled in OpenShift. Valid characters include lowercase letters, numbers, and hyphens (-). The resource name cannot exceed 30 characters, and it must start with a letter and end with a letter or number. Note: You cannot change the resource name after the project is created. You can edit only the display name and the description. Optional: In the Description field, provide a project description. Click Create . Verification A project details page opens. From this page, you can add connections, create workbenches, configure pipelines, and deploy models.

Commands:
Chapter 4. Red Hat Decision Manager supported repositories You can use Git repositories and Apache Maven with Red Hat Decision Manager. 4.1. Git repositories Git repositories are used internally within Business Central to store all processes, rules, and other artifacts that are created in the authoring environment. Git is a distributed version control system. It implements revisions as commit objects. When you commit your changes into a repository, a new commit object in the Git repository is created. When you create a project in Business Central, it is added to the Git repository that is connected to Business Central. If you have projects in other Git repositories, you can import them into Business Central spaces. You can use Git hooks to synchronize the internal Git repositories with external repositories. 4.2. Apache Maven Apache Maven is a distributed build automation tool used in Java application development to build and manage software projects. You can use Maven to build, publish, and deploy your Red Hat Decision Manager projects. Maven provides the following benefits: The build process is easy and a uniform build system is implemented across projects. All of the required JAR files for a project are made available at compile time. A proper project structure is configured. Dependencies and versions are well managed. There is no need for additional build processing because Maven builds output into a number of predefined types, such as JAR and WAR. Maven uses repositories to store Java libraries, plug-ins, and other build artifacts. These repositories can be local or remote. Red Hat Decision Manager maintains local and remote maven repositories that you can add to your project for accessing the rules, processes, events, and other project dependencies. When building projects and archetypes, Maven dynamically retrieves Java libraries and Maven plug-ins from local or remote repositories. Doing this promotes sharing and reuse of dependencies across projects.

Commands:
Chapter 2. Setting up an unbound DNS server The unbound DNS server is a validating, recursive, and caching DNS resolver. Additionally, unbound focuses on security and has, for example, Domain Name System Security Extensions (DNSSEC) enabled by default. 2.1. Configuring Unbound as a caching DNS server By default, the unbound DNS service resolves and caches successful and failed lookups. The service then answers requests to the same records from its cache. Procedure Install the unbound package: Edit the /etc/unbound/unbound.conf file, and make the following changes in the server clause: Add interface parameters to configure on which IP addresses the unbound service listens for queries, for example: With these settings, unbound only listens on the specified IPv4 and IPv6 addresses. Limiting the interfaces to the required ones prevents clients from unauthorized networks, such as the internet, from sending queries to this DNS server. Add access-control parameters to configure from which subnets clients can query the DNS service, for example: Create private keys and certificates for remotely managing the unbound service: If you skip this step, verifying the configuration in the step will report the missing files. However, the unbound service automatically creates the files if they are missing. Verify the configuration file: Update the firewalld rules to allow incoming DNS traffic: Enable and start the unbound service: Verification Query the unbound DNS server listening on the localhost interface to resolve a domain: After querying a record for the first time, unbound adds the entry to its cache. Repeat the query: Because of the cached entry, further requests for the same record are significantly faster until the entry expires. steps Configure clients in your network to use this DNS server. For example, use the nmcli utility to set the IP of the DNS server in a NetworkManager connection profile: Additional resources unbound.conf(5) man page on your system

Commands:
dnf install unbound
interface: 127.0.0.1 interface: 192.0.2.1 interface: 2001:db8:1::1
access-control: 127.0.0.0/8 allow access-control: 192.0.2.0/24 allow access-control: 2001:db8:1::/64 allow
systemctl restart unbound-keygen
unbound-checkconf unbound-checkconf: no errors in /etc/unbound/unbound.conf
firewall-cmd --permanent --add-service=dns firewall-cmd --reload
systemctl enable --now unbound
dig @ localhost www.example.com www.example.com. 86400 IN A 198.51.100.34 ;; Query time: 330 msec
dig @ localhost www.example.com www.example.com. 85332 IN A 198.51.100.34 ;; Query time: 1 msec
nmcli connection modify Example_Connection ipv4.dns 192.0.2.1 nmcli connection modify Example_Connection ipv6.dns 2001:db8:1::1
Chapter 3. HA Solution for S/4HANA based on ABAP Platform 1809 or newer 3.1. Standalone Enqueue Server 2 (ENSA2) Standalone Enqueue Server, a component of Application Server ABAP, is a mechanism to ensure the high availability of the lock table and its entries. Standalone Enqueue Server has evolved into generation 2 since NetWeaver 7.51, known as Standalone Enqueue Server 2, or ENSA2. In ENSA2, if the ASCS fails, it can start on a separate node in the cluster, and copy the lock entries from the enqueue replicator 2. In ABAP platform 1809 or newer, the Standalone Enqueue Server 2 (ENSA2) has become the default installation. 3.2. Supported Scenarios Supported Scenario Description Multi-node cluster Because in ENSA2 ASCS doesn't have to "follow" ERS, that makes a multi-node cluster possible Two-node cluster Upgraded two-node cluster can easily adjust the setup to switch from ENSA1 to ENSA2 Brand new installations can take this chance to design the architecture, choosing between multi-node cluster or two-node cluster. Below is the architecture diagram of a typical 3-node cluster. Of course more nodes can be added upon customer's datacenter requirements or needs. 3.3. Support Policies Please refer to Support Policies for RHEL High Availability Clusters - Management of SAP S/4HANA . 3.4. Configuration Guides On-Premise: Configuring HA clusters to manage SAP NetWeaver or SAP S/4HANA Application server instances using the RHEL HA Add-On AWS: Configure SAP S/4HANA ASCS/ERS ENSA2 on Amazon Web Services (AWS) Azure with GlusterFS: Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux with GlusterFS Azure with NetApp: Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux with Azure NetApp Files for SAP applications Azure with NFS: High availability for SAP NetWeaver on Azure VMs on Red Hat Enterprise Linux with NFS on Azure Files GCP: HA cluster configuration guide for SAP NetWeaver on RHEL IBM Power System Virtual Server: Configuring high availability for SAP S/4HANA (ASCS and ERS) in a RHEL HA Add-On cluster 3.5. Cost-Optimized SAP S/4HANA HA setup (HANA System Replication and ENSA2 combined) With current versions of S/4HANA, it is also possible to run HANA and ABAP Application Server instances on the same system. This makes it possible to have a "cost-optimized" S/4HANA setup where both HANA System Replication and ENSA2 are managed by a single cluster running on the same cluster nodes. For more information, please refer to Configuring a Cost-Optimized SAP S/4HANA HA cluster (HANA System Replication + ENSA2) using the RHEL HA Add-On .

Commands:
8.5. Procedure Metadata SYS.Procedures This table supplies information about the procedures in the virtual database. Column Name Type Description VDBName string VDB name SchemaName string Schema Name Name string Procedure name NameInSource string Procedure name in source system ReturnsResults boolean Returns a result set UID string Procedure UID OID integer Unique ID Description string Description SYS.ProcedureParams This supplies information on procedure parameters. Column Name Type Description VDBName string VDB name SchemaName string Schema Name ProcedureName string Procedure name Name string Parameter name DataType string Data Virtualization runtime data type name Position integer Position in procedure args Type string Parameter direction: "In", "Out", "InOut", "ResultSet", "ReturnValue" Optional boolean Parameter is optional Precision integer Precision of parameter TypeLength integer Length of parameter value Scale integer Scale of parameter Radix integer Radix of parameter NullType string Nullability: "Nullable", "No Nulls", "Unknown" UID string Procedure UID Description string Description OID integer Unique ID Warning The OID column is no longer used on system tables. Use UID instead.

Commands:
Chapter 15. Red Hat Gluster Storage Red Hat Gluster Storage provides flexible and affordable unstructured data storage for the enterprise. GlusterFS , a key building block of Gluster, is based on a stackable user-space design and aggregates various storage servers over a network and interconnects them into one large parallel network file system. The POSIX-compatible GlusterFS servers, which use the XFS file system format to store data on disks, can be accessed using industry standard access protocols including NFS and CIFS. See the Red Hat Gluster Storage collection of guides for more information. The glusterfs package provides Red Hat Gluster Storage. For detailed information about its installation process, see the Installation Guide for Red Hat Gluster Storage. 15.1. Red Hat Gluster Storage and SELinux When enabled, SELinux serves as an additional security layer by providing flexible mandatory access control for the glusterd (GlusterFS Management Service) and glusterfsd (NFS server) processes as a part of Red Hat Gluster Storage. These processes have advanced process isolation unbounded with the glusterd_t SELinux type.

Commands:
30.9. Removing sudo Commands, Command Groups, and Rules Removing sudo Commands, Command Groups, and Rules in the Web UI Under the Policy tab, click Sudo and select Sudo Rules , Sudo Commands , or Sudo Command Groups . Select the command, command group, or rule to delete, and click Delete . Figure 30.16. Deleting a sudo Command Removing sudo Commands, Command Groups, and Rules from the Command Line To delete a command, command group, or rule, use the following commands: ipa sudocmd-del ipa sudocmdgroup-del ipa sudorule-del For more information about these commands and the options they accept, run them with the --help option added.

Commands:
2.4. Cluster Considerations When determining the number of nodes that your system will contain, note that there is a trade-off between high availability and performance. With a larger number of nodes, it becomes increasingly difficult to make workloads scale. For that reason, Red Hat does not support using GFS2 for cluster file system deployments greater than 16 nodes. Deploying a cluster file system is not a "drop in" replacement for a single node deployment. Red Hat recommends that you allow a period of around 8-12 weeks of testing on new installations in order to test the system and ensure that it is working at the required performance level. During this period any performance or functional issues can be worked out and any queries should be directed to the Red Hat support team. Red Hat recommends that customers considering deploying clusters have their configurations reviewed by Red Hat support before deployment to avoid any possible support issues later on.

Commands:
Add-ons Red Hat Advanced Cluster Management for Kubernetes 2.12 Add-ons

Commands:
apiVersion: agent.open-cluster-management.io/v1 kind: KlusterletAddonConfig metadata: name: <cluster_name> namespace: <cluster_name> spec: applicationManager: enabled: true certPolicyController: enabled: true policyController: 1 enabled: true searchCollector: enabled: true
apply -f klusterlet-addon-config.yaml
get managedclusteraddons -n <cluster namespace>
apiVersion: addon.open-cluster-management.io/v1alpha1 kind: AddOnDeploymentConfig metadata: name: config-name 1 namespace: config-name-space 2 spec: nodePlacement: nodeSelector: node-selector 3 tolerations: tolerations 4
apiVersion: addon.open-cluster-management.io/v1alpha1 kind: AddOnDeploymentConfig metadata: name: deploy-config namespace: open-cluster-management-hub spec: nodePlacement: nodeSelector: "node-dedicated": "acm-addon" tolerations: - effect: NoSchedule key: node-dedicated value: acm-addon operator: Equal
apply -f addondeploymentconfig
patch clustermanagementaddons <addon-name> --type='json' -p='[{"op":"add", "path":"/spec/supportedConfigs", "value":[{"group":"addon.open-cluster-management.io","resource":"addondeploymentconfigs", "defaultConfig":{"name":"deploy-config","namespace":"open-cluster-management-hub"}}]}]'
-n <managed-cluster> patch managedclusteraddons <addon-name> --type='json' -p='[{"op":"add", "path":"/spec/configs", "value":[ {"group":"addon.open-cluster-management.io","resource":"addondeploymentconfigs","namespace":"<config-namespace>","name":"<config-name>"} ]}]'
-n <my-cluster-name> edit klusterletaddonconfig <my-cluster-name>
-n <my-cluster-name> edit klusterletaddonconfig
spec proxyConfig: httpProxy: "<proxy_not_secure>" 1 httpsProxy: "<proxy_secure>" 2 noProxy: "<no_proxy>" 3
apiVersion: agent.open-cluster-management.io/v1 kind: KlusterletAddonConfig metadata: name: clusterName namespace: clusterName spec: proxyConfig: httpProxy: http://pxuser:12345@10.0.81.15:3128 httpsProxy: http://pxuser:12345@10.0.81.15:3128 noProxy: .cluster.local,.svc,10.128.0.0/14, example.com applicationManager: enabled: true proxyPolicy: CustomProxy policyController: enabled: true proxyPolicy: OCPGlobalProxy searchCollector: enabled: true proxyPolicy: Disabled certPolicyController: enabled: true proxyPolicy: Disabled
Chapter 44. Viewing process instance logs You can view all the process events of an instance from its Logs tab. The instance logs list all the current and process states. Business Central has two types of logs for process instances, Business and Technical logs. Procedure In Business Central, go to Menu Manage Process Instances . On the Manage Process Instances page, click the process instance whose log you want to view. Select the Logs tab: Click Business to view the business events log. Click Technical to view the technical events log. Click Asc or Desc to change the order of the log files.

Commands:
20.45. Display or Set Block I/O Parameters The blkiotune command sets or displays the I/O parameters for a specified guest virtual machine. The following format should be used: More information on this command can be found in the Virtualization Tuning and Optimization Guide

Commands:
virsh blkiotune domain [--weight weight ] [--device-weights device-weights ] [---device-read-iops-sec -device-read-iops-sec ] [--device-write-iops-sec device-write-iops-sec ] [--device-read-bytes-sec device-read-bytes-sec ] [--device-write-bytes-sec device-write-bytes-sec ] [[--config] [--live] | [--current]]