mtpti5iD/redhat-docs_dataset huggingface dataset:
5.278. redhat-rpm-config 5.278.1. RHBA-2012:0911 - redhat-rpm-config bug fix and enhancement update An updated redhat-rpm-config package that fixes several bugs and adds an enhancement is now available for Red Hat Enterprise Linux 6. The redhat-rpm-config package is used during building of RPM packages to apply various default distribution options determined by Red Hat. It also provides a few Red Hat RPM macro customizations, such as those used during the building of Driver Update packages. Bug Fixes BZ# 680029 Previously, the %kernel_module_package macro did not handle the "-v" and "-r" optional version and release override parameters correctly. Consequently, the specified version and release number were not used when the RPM package was built. This bug has been fixed and these parameters are now handled properly. BZ# 713638 Previously, a script, which generates "modalias"-style dependencies for Driver Update packages in Red Hat Enterprise Linux 6, was not executable and thus could not function properly. This bug has been fixed and these dependencies are now generated as expected. BZ# 713992 When the kabi-whitelists package is installed, the %kernel_module_package macro did not automatically perform a check against the Red Hat kernel ABI interface (kABI). Consequently, when a package was being built, the macro did not warn when the resulting modules used kernel symbols that were exported but not part of the kABI. With this update, the abi_check.py script has been added to perform the check and return a warning during the build process if kabi-whitelists is not installed, thus fixing this bug. BZ# 767738 In certain cases, the dependency-generation scripts that produce information about automatic kernel symbol during the build process of a Driver Update package generated incorrect dependencies. This bug has been fixed and dependencies are now generated correctly. Enhancement BZ# 652084 The path of the autoconf configuration script invoked by the %configure macro can now be customized by overriding the %_configure macro. In addition, this can be of use when building out-of-tree packages. Users of redhat-rpm-config are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
3.4. Deploy a VDB via Management Console Prerequisites Red Hat JBoss Data Virtualization must be installed. The JBoss Enterprise Application Platform (EAP) server must be running. You must have a JBoss EAP Management User registered. Procedure 3.2. Deploy a VDB via Management Console Launch the console in a Web browser Open http://localhost:9990/console/ in a web browser. Authenticate to the console Enter your JBoss EAP administrator username and password when prompted. Open the Deployments panel In the Runtime view, select Server Manage Deployments . Add the virtual database Select the Add button. Select Choose File and choose the VDB file you want to deploy. Select to review the deployment names then select Save . Select En/Disable to enable the VDB.

Commands:
Appendix A. Troubleshooting This section provides the multiple troubleshooting scenarios while using the dashboard. A.1. Dashboard response is slow If the dashboard response is slow, clear the browser cache and reload the dashboard. A.2. Dashboard shows a service is down Dashboard is only a replica of the cluster. If the service is down, check the service status on the node as dashboard displays information collected via node-exporter running on the node. The issue may be in the cluster, configuration, or network. A.3. Task failure on Dashboard While performing any task on the dashboard, if there is any failure, check the respective Ceph daemons. For more information refer to the Troubleshooting Guide A.4. Images cannot be viewed An image can only be viewed under Block > Images if the pool it is in has the RBD application enabled on it. Additional resources For more information, refer to the Troubleshooting Guide

Commands:
11.10. Additional Resources The following are resources which explain more about network interfaces. Installed Documentation /usr/share/doc/initscripts- version /sysconfig.txt - A guide to available options for network configuration files, including IPv6 options not covered in this chapter. Online Resources http://linux-ip.net/gl/ip-cref/ - This document contains a wealth of information about the ip command, which can be used to manipulate routing tables, among other things. Red Hat Access Labs - The Red Hat Access Labs includes a " Network Bonding Helper " . See Also Appendix E, The proc File System - Describes the sysctl utility and the virtual files within the /proc/ directory, which contain networking parameters and statistics among other things.

Commands:
Chapter 9. Security SSH connections using libica AES-GCM now work correctly Previously, unmodified data could be tagged as modified when using decryption with the AES-GCM cipher suite. As a consequence, SSH connections could not be established when using AES-GCM , and with some applications, data encrypted using AES-GCM could not be decrypted. With this update, the tag is computed from the ciphertext when decrypting and from the plaintext when encrypting. As a result, SSH connections using AES-GCM are now successfully established, and it is possible to decrypt data encrypted with AES-GCM . (BZ#1490894)

Commands:
Chapter 1. Red Hat Process Automation Manager components The product is made up of Business Central and KIE Server. Business Central is the graphical user interface where you create and manage business rules. You can install Business Central in a Red Hat JBoss EAP instance or on the Red Hat OpenShift Container Platform (OpenShift). Business Central is also available as a standalone JAR file. You can use the Business Central standalone JAR file to run Business Central without deploying it to an application server. KIE Server is the server where rules and other artifacts are executed. It is used to instantiate and execute rules and solve planning problems. You can install KIE Server in a Red Hat JBoss EAP instance, in a Red Hat JBoss EAP cluster, on OpenShift, in an Oracle WebLogic server instance, in an IBM WebSphere Application Server instance, or as a part of Spring Boot application. You can configure KIE Server to run in managed or unmanaged mode. If KIE Server is unmanaged, you must manually create and maintain KIE containers (deployment units). A KIE container is a specific version of a project. If KIE Server is managed, the Process Automation Manager controller manages the KIE Server configuration and you interact with the Process Automation Manager controller to create and maintain KIE containers.

Commands:
Chapter 113. KafkaUserTemplate schema reference Used in: KafkaUserSpec Full list of KafkaUserTemplate schema properties Specify additional labels and annotations for the secret created by the User Operator. An example showing the KafkaUserTemplate apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaUser metadata: name: my-user labels: strimzi.io/cluster: my-cluster spec: authentication: type: tls template: secret: metadata: labels: label1: value1 annotations: anno1: value1 # ... 113.1. KafkaUserTemplate schema properties Property Description secret Template for KafkaUser resources. The template allows users to specify how the Secret with password or TLS certificates is generated. ResourceTemplate

Commands:
apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaUser metadata: name: my-user labels: strimzi.io/cluster: my-cluster spec: authentication: type: tls template: secret: metadata: labels: label1: value1 annotations: anno1: value1 #
23.11. Initializing the Hard Disk If no readable partition tables are found on existing hard disks, the installation program asks to initialize the hard disk. This operation makes any existing data on the hard disk unreadable. If your system has a brand new hard disk with no operating system installed, or you have removed all partitions on the hard disk, click Re-initialize drive . The installation program presents you with a separate dialog for each disk on which it cannot read a valid partition table. Click the Ignore all button or Re-initialize all button to apply the same answer to all devices. Figure 23.33. Warning screen - initializing DASD Figure 23.34. Warning screen - initializing FCP LUN Certain RAID systems or other nonstandard configurations may be unreadable to the installation program and the prompt to initialize the hard disk may appear. The installation program responds to the physical disk structures it is able to detect. To enable automatic initializing of hard disks for which it turns out to be necessary, use the kickstart command zerombr (refer to Chapter 32, Kickstart Installations ). This command is required when performing an unattended installation on a system with previously initialized disks. Warning If you have a nonstandard disk configuration that can be detached during installation and detected and configured afterward, power off the system, detach it, and restart the installation.

Commands:
3.13. Software Collection Configuration Files Support By default, configuration files in a Software Collection are stored within the /opt/ provider /%{scl} file system hierarchy. To make configuration files more accessible and easier to manage, you are advised to use the nfsmountable macro that redefines the _sysconfdir macro. This results in configuration files being created underneath the /etc/opt/ provider /%{scl}/ directory, outside of the /opt/ provider /%{scl} file system hierarchy. For example, a configuration file example.conf is normally stored in the /etc directory in the base system installation. If the configuration file is a part of a software_collection Software Collection and the nfsmountable macro is defined, the path to the configuration file in software_collection is as follows: For more information about using the nfsmountable macro, see Section 3.1, "Using Software Collections over NFS" .

Commands:
/etc/opt/ provider / software_collection / example.conf
Chapter 6. Managing DNS using Capsule Satellite can manage DNS records using your Capsule. DNS management contains updating and removing DNS records from existing DNS zones. A Capsule has multiple DNS providers that you can use to integrate Satellite with your existing DNS infrastructure or deploy a new one. After you have enabled DNS, your Capsule can manipulate any DNS server that complies with RFC 2136 using the dns_nsupdate provider. Other providers provide more direct integration, such as dns_infoblox for Infoblox . Available DNS providers dns_infoblox - For more information, see Using Infoblox as DHCP and DNS Providers in Provisioning hosts . dns_nsupdate - Dynamic DNS update using nsupdate. For more information, see Using Infoblox as DHCP and DNS Providers in Provisioning hosts . dns_nsupdate_gss - Dynamic DNS update with GSS-TSIG. For more information, see Section 4.4.1, "Configuring dynamic DNS update with GSS-TSIG authentication" .

Commands:
Upgrading connected Red Hat Satellite to 6.16 Red Hat Satellite 6.16 Upgrade Satellite Server and Capsule Red Hat Satellite Documentation Team satellite-doc-list@redhat.com

Commands:
satellite-maintain service stop
satellite-maintain service start
satellite-installer --foreman-proxy-dhcp-managed=false --foreman-proxy-dns-managed=false
satellite-maintain self-upgrade
satellite-maintain upgrade check
satellite-maintain upgrade run
reboot
yum clean metadata
satellite-maintain self-upgrade
grep foreman_url /etc/foreman-proxy/settings.yml
satellite-maintain upgrade check
satellite-maintain upgrade run
reboot
runuser -l postgres -c "psql -d foreman -c \"UPDATE pg_extension SET extowner = (SELECT oid FROM pg_authid WHERE rolname='foreman') WHERE extname='evr';\""
satellite-installer --foreman-db-host newpostgres.example.com --katello-candlepin-db-host newpostgres.example.com --foreman-proxy-content-pulpcore-postgresql-host newpostgres.example.com
satellite-maintain packages install leapp leapp-upgrade-el8toel9
leapp preupgrade
leapp upgrade
journalctl -u leapp_resume -f
satellite-maintain packages unlock
satellite-maintain packages lock
subscription-manager release --unset
2024-01-29T20:50:09 [W|app|] Could not create role 'Ansible Roles Manager': ERF73-0602 [Foreman::PermissionMissingException]: some permissions were not found:
satellite-maintain health check --label duplicate_permissions
foreman-rake db:seed
satellite-maintain health check --label duplicate_permissions
Chapter 1. Preparing to deploy OpenShift Data Foundation When you deploy OpenShift Data Foundation on OpenShift Container Platform using the local storage devices on any platform, you can create internal cluster resources. This approach internally provisions base services so that all the applications can access additional storage classes. You can also deploy OpenShift Data Foundation to use an external Red Hat Ceph Storage cluster and IBM FlashSystem. For instructions, see Deploying OpenShift Data Foundation in external mode . External mode deployment works on clusters that are detected as non-cloud. If your cluster is not detected correctly, open up a bug in Bugzilla . Before you begin the deployment of Red Hat OpenShift Data Foundation using a local storage, ensure that you meet the resource requirements. See Requirements for installing OpenShift Data Foundation using local storage devices . After completing the preparatory steps, perform the following procedures: Install the Local Storage Operator . Install the Red Hat OpenShift Data Foundation Operator . Create the OpenShift Data Foundation cluster on any platform . 1.1. Requirements for installing OpenShift Data Foundation using local storage devices Node requirements The cluster must consist of at least three OpenShift Container Platform worker or infrastructure nodes with locally attached-storage devices on each of them. Each of the three selected nodes must have at least one raw block device available. OpenShift Data Foundation uses the one or more available raw block devices. The devices you use must be empty, the disks must not include Physical Volumes (PVs), Volume Groups (VGs), or Logical Volumes (LVs) remaining on the disk. For more information, see the Resource requirements section in the Planning guide . Disaster recovery requirements Disaster Recovery features supported by Red Hat OpenShift Data Foundation require all of the following prerequisites to successfully implement a disaster recovery solution: A valid Red Hat OpenShift Data Foundation Advanced subscription. A valid Red Hat Advanced Cluster Management (RHACM) for Kubernetes subscription. To know in detail how subscriptions for OpenShift Data Foundation work, see knowledgebase article on OpenShift Data Foundation subscriptions . For detailed disaster recovery solution requirements, see Configuring OpenShift Data Foundation Disaster Recovery for OpenShift Workloads guide, and Requirements and recommendations section of the Install guide in Red Hat Advanced Cluster Management for Kubernetes documentation. Minimum starting node requirements An OpenShift Data Foundation cluster is deployed with a minimum configuration when the resource requirement for a standard deployment is not met. For more information, see the Resource requirements section in the Planning guide .

Commands:
Chapter 1. Red Hat OpenStack Platform identity providers You can deploy one of two methods to authenticate for a user to authenticate to an identity provider (IdP): You can connect the Red Hat OpenStack Platform (RHOSP) Identity service (keystone) to an IdP using LDAP (Lightweight Directory Access Protocol) You can use federation, in which the IdP sends an assertion to the Identity service granting the user access to the cloud. While LDAP is used as a central authority for identity management and authentication, federation can be used to build single sign-on solutions. For information on connecting RHOSP services to an LDAP directory service by using either Active Directory (AD) or Red Hat Identity Manager (IdM), see the following resources: Integrating OpenStack Identity (keystone) with Active Directory Integrating OpenStack Identity (keystone) with Red Hat Identity Manager (IdM) For information on connecting RHOSP to IdM using Red Hat Single Sign-On for a federated solution, see the following resources: Federation using Red Hat OpenStack Platform and Red Hat Single Sign-On Federation using Red Hat OpenStack Platform and Active Directory Federation Services

Commands:
4.3. Clustering and High Availability clufter The clufter package, available as a Technology Preview in Red Hat Enterprise Linux 6, provides a tool for transforming and analyzing cluster configuration formats. It can be used to assist with migration from an older stack configuration to a newer configuration that leverages Pacemaker. For information on the capabilities of clufter , see the clufter(1) man page or the output of the clufter -h command. Package: clufter-0.11.2-1 luci support for fence_sanlock The luci tool now supports the sanlock fence agent as a Technology Preview. The agent is available in the luci's list of agents. Package: luci-0.26.0-67 Recovering a node via a hardware watchdog device New fence_sanlock agent and checkquorum.wdmd, included in Red Hat Enterprise Linux 6.4 as a Technology Preview, provide new mechanisms to trigger the recovery of a node via a hardware watchdog device. Tutorials on how to enable this Technology Preview will be available at https://fedorahosted.org/cluster/wiki/HomePage Note that SELinux in enforcing mode is currently not supported. Package: cluster-3.0.12.1-73

Commands:
9.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: allow_user_mysql_connect When enabled, this Boolean allows users to connect to MySQL. exim_can_connect_db When enabled, this Boolean allows the exim mailer to initiate connections to a database server. ftpd_connect_db When enabled, this Boolean allows ftp daemons to initiate connections to a database server. httpd_can_network_connect_db Enabling this Boolean is required for a web server to communicate with a database server. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, run the following command as root:

Commands:
~]# semanage boolean -l | grep service_name
Chapter 3. Customizing the Cryostat dashboard The Cryostat Dashboard displays information about target Java Virtual Machines (JVMs) in the form of cards on the user interface. You can configure the cards and customize different dashboard layouts according to your requirements. 3.1. Creating a custom dashboard layout Create customized layouts to organize the display of dashboard cards, according to your requirements. You can organize the cards in different configurations and create custom views to display the data and specific metrics that are most relevant to your current requirements. You can add, remove, and arrange the cards and switch between different layouts. You can also create layout templates that you can download, reuse, or share with other users so that they can access the same information and metrics. By using dashboard layouts, you do not need to modify your dashboard manually each time you want to view different information. Prerequisites Created a Cryostat instance in your project. Logged in to your Cryostat web console. Created a target JVM to monitor. Procedure On the Cryostat web console, click Dashboard . On the toolbar, click the layout selector dropdown menu. Click New Layout . Figure 3.1. Creating a new dashboard layout The new layout is assigned a default name. To specify a different name, click the pencil icon beside the name. (Optional): To select an existing template or upload a new one, click the expandable menu on the New Layout button. Figure 3.2. Creating a new dashboard layout by using a template (Optional): To set or download a layout as a template or to clear the layout, click the more options icon ( ... ): Figure 3.3. Setting or downloading a layout as a template or clearing the layout To set the current layout as a template, select Set as template . To download the current layout as a template, select Download as template . The template is downloaded as a .json file. To clear the current layout, select Clear layout . A confirmation dialog then opens. To confirm that you want to permanently clear the current dashboard layout, click Clear . Figure 3.4. Clearing a dashboard layout 3.2. Adding cards to a dashboard layout You can select and configure the cards you want to add to the Cryostat Dashboard . Each card displays a different set of information or metrics about the target JVM you select. Prerequisites Created a Cryostat instance in your project. Logged in to your Cryostat web console. Created a target JVM to monitor. Procedure On the Cryostat web console, click Dashboard . From the Target dropdown menu, select the target JVM whose information you want to view. To add a dashboard card, click the Add card icon. The Dashboard card catalog window opens. From the available cards types, select a card to add to your dashboard layout and click Finish . Repeat this step for each card that you want to add. Note Some cards require additional configuration, for example, the MBeans Metrics Chart card. In this instance, click to access the configuration wizard, specify the values you require, then click Finish . Revised on 2023-12-12 18:03:30 UTC

Commands:
Chapter 10. Predictive Model Markup Language (PMML) Predictive Model Markup Language (PMML) is an XML-based standard established by the Data Mining Group (DMG) for defining statistical and data-mining models. PMML models can be shared between PMML-compliant platforms and across organizations so that business analysts and developers are unified in designing, analyzing, and implementing PMML-based assets and services. For more information about the background and applications of PMML, see the DMG PMML specification . 10.1. PMML conformance levels The PMML specification defines producer and consumer conformance levels in a software implementation to ensure that PMML models are created and integrated reliably. For the formal definitions of each conformance level, see the DMG PMML conformance page. The following list summarizes the PMML conformance levels: Producer conformance A tool or application is producer conforming if it generates valid PMML documents for at least one type of model. Satisfying PMML producer conformance requirements ensures that a model definition document is syntactically correct and defines a model instance that is consistent with semantic criteria that are defined in model specifications. Consumer conformance An application is consumer conforming if it accepts valid PMML documents for at least one type of model. Satisfying consumer conformance requirements ensures that a PMML model created according to producer conformance can be integrated and used as defined. For example, if an application is consumer conforming for Regression model types, then valid PMML documents defining models of this type produced by different conforming producers would be interchangeable in the application. Red Hat Decision Manager includes consumer conformance support for the following PMML model types: Regression models Scorecard models Tree models Mining models (with sub-types modelChain , selectAll , and selectFirst ) Clustering models For a list of all PMML model types, including those not supported in Red Hat Decision Manager, see the DMG PMML specification .

Commands: