mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix E. Editors E.1. Editors Editors are the UI components designed to assist editing your models and to maintain the state for a given model or resource in your workspace. When editing a model, the model will be opened in a Model Editor. Editing a property value, for instance, will require an open editor prior to actually changing the property. Any number of editors can be open at once, but only one can be active at a time. The main menu bar and toolbar for Teiid Designer may contain operations that are applicable to the active editor (and removed when editor becomes inactive). Tabs in the editor area indicate the names of models that are currently open for editing. An asterisk (*) indicates that an editor has unsaved changes. Figure E.1. Editor Tabs By default, editors are stacked in the editors area, but you can choose to tile them vertically, and or horizontally in order to view multiple models simultaneously. Figure E.2. Viewing Multiple Editors The Teiid Designer provides main editor views for XMI models and VDBs. The Model Editor contains sub-editors which provide different views of the data or parts of data within an XMI model. These sub-editors, specific to model types are listed below. Diagram Editor - All models except XML Schema models. Table Editor - All models. Simple Datatypes Editor - XML Schema models only. Semantics Editor - XML Schema models only. Source Editor - XML Schema models only. The VDB Editor is a single page editor containing panels for editing description, model contents and data roles. In addition to general Editors for models, there are detailed editors designed for editing specific model object types. These object editors include: Transformation Editor - Manages Transformation SQL for Relational View Base Tables, Procedures and XML Web Service Operations. Choice Editor - Manages properties and criteria for XML choice elements in XML Document View models. Input Editor - Manages Input Set parameters used between Mapping Classes in XML Document View models. Recursion Editor - Manages recursion properties for recursive XML Elements in XML Document View models. Operation Editor - Manages SQL and Input Variables for Web Service Operations.

Commands:
18.12.10.8. ICMP Protocol ID: icmp Note: The chain parameter is ignored for this type of traffic and should either be omitted or set to root. Table 18.10. ICMP protocol types Attribute Name Datatype Definition srcmacaddr MAC_ADDR MAC address of sender srcmacmask MAC_MASK Mask applied to the MAC address of the sender dstmacaddr MAD_ADDR MAC address of the destination dstmacmask MAC_MASK Mask applied to the MAC address of the destination srcipaddr IP_ADDR Source IP address srcipmask IP_MASK Mask applied to source IP address dstipaddr IP_ADDR Destination IP address dstipmask IP_MASK Mask applied to destination IP address srcipfrom IP_ADDR start of range of source IP address scripto IP_ADDR end of range of source IP address dstipfrom IP_ADDR Start of range of destination IP address dstipto IP_ADDR End of range of destination IP address type UNIT16 ICMP type code UNIT16 ICMP code comment STRING text string up to 256 characters state STRING comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE ipset STRING The name of an IPSet managed outside of libvirt ipsetflags IPSETFLAGS flags for the IPSet; requires ipset attribute

Commands:
4.199. nss 4.199.1. RHBA-2011:1838 - nss bug fix update Updated nss packages that fix one bug are now available for Red Hat Enterprise Linux 6. Network Security Services (NSS) is a set of libraries designed to support the cross-platform development of security-enabled client and server applications. Bug Fix BZ# 766056 Recent changes to NSS re-introduced a problem where applications could not use multiple SSL client certificates in the same process. Therefore, any attempt to run commands that worked with multiple SSL client certificates, such as the "yum repolist" command, resulted in a re-negotiation handshake failure. With this update, a revised patch correcting this problem has been applied to NSS, and using multiple SSL client certificates in the same process is now possible again. All users of nss are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 7. Setting the Number of Directory Server Threads The number of threads Directory Server uses to handle simultaneous connections affects the performance of the server. For example, if all threads are busy handling time-consuming tasks (such as add operations), new incoming connections are queued until a free thread can process the request. If the server provides a low number of CPU threads, configuring a higher number of threads can increase the performance. However, on a server with many CPU threads, setting a too high value does not further increase the performance. By default, Directory Server automatically calculates the number of threads automatically. This number is based on the hardware resources of the server when the instance starts. Note Red Hat recommends to use the auto-tuning settings. Do not set the number of threads manually. 7.1. Automatic Thread Tuning If you enable automatic thread tuning, Directory Server will use the following optimized number of threads: Number of CPU Threads Number of Directory Server Threads 1 16 2 16 4 24 8 32 16 48 32 64 64 96 128 192 256 384 512 512 [a] 1024 512 [a] 2048 512 [a] [a] The recommended maximum number of threads is applied. 7.1.1. Enabling Automatic Thread Tuning Using the Command Line Directory Server can automatically set the number of threads based on the available hardware threads. To enable this feature: Enable automatic setting of the number of threads: Restart the Directory Server instance: Important If you enabled the automatic setting of the number of threads, the nsslapd-threadnumber parameter shows the calculated number of threads while Directory Server is running. 7.1.2. Enabling Automatic Thread Tuning Using the Web Console Directory Server can automatically set the number of threads based on the available hardware threads. To enable this feature: Open the Directory Server user interface in the web console. For details, see Logging Into Directory Server Using the Web Console section in the Red Hat Directory Server Administration Guide . Select the instance. Open the Server Settings menu, and select Tuning & Limits . Set the Number Of Worker Threads field to -1 . Click Save . Click the Actions button, and select Restart Instance . Important If you enabled the automatic setting, the Number Of Worker Threads field shows the calculated number of threads while Directory Server is running.

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-threadnumber="-1"
dsctl instance_name restart
8.97. ipvsadm 8.97.1. RHBA-2014:1511 - ipvsadm bug fix update Updated ipvsadm packages that fix one bug are now available for Red Hat Enterprise Linux 6. The ipvsadm packages provide the ipsvadm tool to administer the IP Virtual Server services offered by the Linux kernel. Bug Fix BZ# 1099687 Previously, the ipvsadm tool did not handle printing of existing sync daemons correctly under certain circumstances. Consequently, the "ipvsadm --list --daemon" command did not report the existence of a backup sync daemon when only a backup sync daemon was running on a node. A patch has been applied to address this bug, and "ipvsadm --list --daemon" now correctly shows the backup sync daemon even if it is the only daemon running. Users of ipvsadm are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 2. Power monitoring overview Important Power monitoring is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . 2.1. About power monitoring You can use power monitoring for Red Hat OpenShift to monitor the power usage and identify power-consuming containers running in an OpenShift Container Platform cluster. Power monitoring collects and exports energy-related system statistics from various components, such as CPU and DRAM. It provides granular power consumption data for Kubernetes pods, namespaces, and nodes. Warning Power monitoring Technology Preview works only in bare-metal deployments. Most public cloud vendors do not expose Kernel Power Management Subsystems to virtual machines. 2.2. Power monitoring architecture Power monitoring is made up of the following major components: The Power monitoring Operator For administrators, the Power monitoring Operator streamlines the monitoring of power usage for workloads by simplifying the deployment and management of Kepler in an OpenShift Container Platform cluster. The setup and configuration for the Power monitoring Operator are simplified by adding a Kepler custom resource definition (CRD). The Operator also manages operations, such as upgrading, removing, configuring, and redeploying Kepler. Kepler Kepler is a key component of power monitoring. It is responsible for monitoring the power usage of containers running in OpenShift Container Platform. It generates metrics related to the power usage of both nodes and containers. 2.3. Kepler hardware and virtualization support Kepler is the key component of power monitoring that collects real-time power consumption data from a node through one of the following methods: Kernel Power Management Subsystem (preferred) rapl-sysfs : This requires access to the /sys/class/powercap/intel-rapl host file. rapl-msr : This requires access to the /dev/cpu/*/msr host file. The estimator power source Without access to the kernel's power cap subsystem, Kepler uses a machine learning model to estimate the power usage of the CPU on the node. Warning The estimator feature is experimental, not supported, and should not be relied upon. You can identify the power estimation method for a node by using the Power Monitoring / Overview dashboard. 2.4. Additional resources Power monitoring dashboards overview

Commands:
4.283. sblim-gather 4.283.1. RHBA-2011:1593 - sblim-gather bug fix update Updated sblim-gather packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The sblim-gather package (Standards Based Linux Instrumentation for Manageability Performance Data Gatherer Base) contains agents and control programs for gathering and providing performance data and CIM (Common Information Model) Providers. The sblim-gather package has been upgraded to upstream version 2.2.3, which provides a number of bug fixes over the version. (BZ# 633991 ) Bug Fixes BZ# 712043 Previously, CIM Metrics providers specific to IBM System z were missing from the sblim-gather package, preventing proper functionality of the package on that architecture. This update ensures that the CIM Metrics providers are now properly included in the IBM System z packages, with the result that full functionality is now provided. BZ# 713174 The sblim-gather-provider package is DSP1053 compliant and advertises this via the Linux_MetricRegisteredProfile class under the root/interop namespace. Prior to this update, the registration of this class and provider was missing from the package, preventing communication with the class via CIM object managers. This bug has been fixed, and now the appropriate provider for the Linux_MetricRegisteredProfile class is properly registered under the root/interop namespace. BZ# 626769 Previously, the sblim-gather init script was incorrectly placed in the /etc/init.d directory, causing difficulties during installation of the package. With this update, the init script is correctly placed in the /etc/rc.d/init.d directory, thus fixing this bug. BZ# 627919 Previously, the sblim-gather init script exit status codes were incorrect in two scenarios: when restarting a service as a non-privileged user and when passing an invalid argument. This bug has been fixed, and all exit status codes of the sblim-gather init script are now correct. All users of sblim-gather are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 6. Upgrade Quay Bridge Operator To upgrade the Quay Bridge Operator (QBO), change the Channel Subscription update channel in the Subscription tab to the desired channel. When upgrading QBO from version 3.5 to 3.7, a number of extra steps are required: You need to create a new QuayIntegration custom resource. This can be completed in the Web Console or from the command line. upgrade-quay-integration.yaml - apiVersion: quay.redhat.com/v1 kind: QuayIntegration metadata: name: example-quayintegration-new spec: clusterID: openshift 1 credentialsSecret: name: quay-integration namespace: openshift-operators insecureRegistry: false quayHostname: https://registry-quay-quay35.router-default.apps.cluster.openshift.com 1 Make sure that the clusterID matches the value for the existing QuayIntegration resource. Create the new QuayIntegration custom resource: USD oc create -f upgrade-quay-integration.yaml Delete the old QuayIntegration custom resource. Delete the old mutatingwebhookconfigurations : USD oc delete mutatingwebhookconfigurations.admissionregistration.k8s.io quay-bridge-operator

Commands:
- apiVersion: quay.redhat.com/v1 kind: QuayIntegration metadata: name: example-quayintegration-new spec: clusterID: openshift 1 credentialsSecret: name: quay-integration namespace: openshift-operators insecureRegistry: false quayHostname: https://registry-quay-quay35.router-default.apps.cluster.openshift.com
oc create -f upgrade-quay-integration.yaml
oc delete mutatingwebhookconfigurations.admissionregistration.k8s.io quay-bridge-operator
1.2. A Detailed Look at the Boot Process The beginning of the boot process varies depending on the hardware platform being used. However, once the kernel is found and loaded by the boot loader, the default boot process is identical across all architectures. This chapter focuses primarily on the x86 architecture. 1.2.1. The BIOS When an x86 computer is booted, the processor looks at the end of system memory for the Basic Input/Output System or BIOS program and runs it. The BIOS controls not only the first step of the boot process, but also provides the lowest level interface to peripheral devices. For this reason it is written into read-only, permanent memory and is always available for use. Other platforms use different programs to perform low-level tasks roughly equivalent to those of the BIOS on an x86 system. For instance, Itanium-based computers use the Extensible Firmware Interface ( EFI ) Shell . Once loaded, the BIOS tests the system, looks for and checks peripherals, and then locates a valid device with which to boot the system. Usually, it checks any diskette drives and CD-ROM drives present for bootable media, then, failing that, looks to the system's hard drives. In most cases, the order of the drives searched while booting is controlled with a setting in the BIOS, and it looks on the master IDE device on the primary IDE bus. The BIOS then loads into memory whatever program is residing in the first sector of this device, called the Master Boot Record or MBR . The MBR is only 512 bytes in size and contains machine code instructions for booting the machine, called a boot loader, along with the partition table. Once the BIOS finds and loads the boot loader program into memory, it yields control of the boot process to it.

Commands:
Assessing RHEL Configuration Issues Using the Red Hat Insights Advisor Service with FedRAMP Red Hat Insights 1-latest Assess and monitor the configuration issues impacting your RHEL systems Red Hat Customer Content Services

Commands:
USE [master] GO CREATE LOGIN [assessmentLogin] with PASSWORD= N'<*PASSWORD*>' ALTER SERVER ROLE [sysadmin] ADD MEMBER [assessmentLogin] GO
echo "assessmentLogin" > /var/opt/mssql/secrets/assessment echo "<*PASSWORD*>" >> /var/opt/mssql/secrets/assessment
chmod 0600 /var/opt/mssql/secrets/assessment chown mssql:mssql /var/opt/mssql/secrets/assessment
yum -y install powershell
su mssql -c "/usr/bin/pwsh -Command Install-Module SqlServer"
/bin/curl -LJ0 -o /opt/mssql/bin/runassessment.ps1 https://raw.githubusercontent.com/microsoft/sql-server-samples/master/samples/manage/sql-assessment-api/RHEL/runassessment.ps1 chown mssql:mssql /opt/mssql/bin/runassessment.ps1 chmod 0700 /opt/mssql/bin/runassessment.ps1
mkdir /var/opt/mssql/log/assessments/ chown mssql:mssql /var/opt/mssql/log/assessments/ chmod 0700 /var/opt/mssql/log/assessments/
su mssql -c "pwsh -File /opt/mssql/bin/runassessment.ps1"
insights-client
cp mssql-runassessment.service /etc/systemd/system/ cp mssql-runassessment.timer /etc/systemd/system/ chmod 644 /etc/systemd/system/
systemctl enable --now mssql-runassessment.timer
insights-client --group=<name-you-choose>
tags --- group: eastern-sap name: Jane Example contact: jexample@corporate.com Zone: eastern time zone Location: - gray_rack - basement Application: SAP
tags --- group: eastern-sap location: Boston description: - RHEL8 - SAP key 4: value
insights-client
vi /etc/insights-client/tags.yaml
cat /etc/insights-client/tags.yaml group: redhat location: Brisbane/Australia description: - RHEL8 - SAP security: strict network_performance: latency
insights-client
insights-client --unregister
curl -k --user PORTALUSERNAME https://console.redhat.com/api/inventory/v1/hosts | json_pp > hosts.json
yum install perl-JSON-PP
curl -k --user PORTALUSERNAME https://console.redhat.com/api/inventory/v1/hosts/f59716a6-5d64-4901-b65f-788b1aee25cc
curl -k --user PORTALUSERNAME -X "DELETE" https://console.redhat.com/api/inventory/v1/hosts/f59716a6-5d64-4901-b65f-788b1aee25cc
Chapter 3. Setting Up DM-Multipath This chapter provides step-by-step example procedures for configuring DM-Multipath. It includes the following procedures: Basic DM-Multipath setup Ignoring local disks Adding more devices to the configuration file 3.1. Setting Up DM-Multipath Before setting up DM-Multipath on your system, ensure that your system has been updated and includes the device-mapper-multipath package. Use the following procedure to set up DM-Multipath for a basic failover configuration. Edit the /etc/multipath.conf file by commenting out the following lines at the top of the file. This section of the configuration file, in its initial state, blacklists all devices. You must comment it out to enable multipathing. After commenting out those lines, this section appears as follows. The default settings for DM-Multipath are compiled in to the system and do not need to be explicitly set in the /etc/multipath.conf file. The default value of path_grouping_policy is set to failover , so in this example you do not need to change the default value. For information on changing the values in the configuration file to something other than the defaults, see Chapter 4, The DM-Multipath Configuration File . The initial defaults section of the configuration file configures your system that the names of the multipath devices are are of the form mpath n ; without this setting, the names of the multipath devices would be aliased to the WWID of the device. Save the configuration file and exit the editor. Execute the following commands: The multipath -v2 command prints out multipathed paths that show which devices are multipathed, but only for the devices created by this command. If the command does yield any output, you can check your multipath devices as follows: Run the multipath -ll command. This lists all the multipath devices. If running the multipath -ll command does not show the device, verify that multipath is configured properly by checking the /etc/multipath file and making sure that the SCSI devices you want to be multipathed exist on the system. If the SCSI devices do not appear, ensure that all SAN connections are set up properly. For further information on the multipath command and its output, see Section 5.1, "Multipath Command Output" , see Section 5.2, "Multipath Queries with multipath Command" , and see Section 5.3, "Multipath Command Options" . Execute the following command to ensure sure that the multipath daemon starts on bootup: Since the value of user_friendly_name is set to yes in the configuration filea the multipath devices will be created as /dev/mapper/mpath n . For information on setting the name of the device to an alias of your choosing, see Chapter 4, The DM-Multipath Configuration File .

Commands:
devnode_blacklist { devnode "*" }
devnode_blacklist { devnode "*" }
modprobe dm-multipath service multipathd start multipath -v2
chkconfig multipathd on
Chapter 8. Conclusion In the sections of this guide we walked through the primary workflows necessary to get started using automation services catalog. Following these workflows you have: Created the necessary groups and users to use both Catalog and Approval through the User access, Connected to a source platform, Created portfolios, Added products from the source platform into the portfolio, Created and set approval processes for the portfolio, Shared the portfolio with users, Approved or denied orders created by users, and comment on orders where necessary.

Commands:
C.2. Selection Criteria Operators Table C.2, "Selection Criteria Grouping Operators" describes the selection criteria grouping operators. Table C.2. Selection Criteria Grouping Operators Grouping Operator Description ( ) Used for grouping statements [ ] Used to group strings into a string list (exact match) { } Used to group strings into a string list (subset match) Table C.3, "Selection Criteria Comparison Operators" describes the selection criteria comparison operators and the field types with which they can be used. Table C.3. Selection Criteria Comparison Operators Comparison Operator Description Field Type =~ Matching regular expression regex !~ Not matching regular expression. regex = Equal to number, size, percent, string, string list != Not equal to number, size, percent, string, string list >= Greater than or equal to number, size, percent > Greater than number, size, percent <= Less than or equal to number, size, percent < Less than number, size, percent Table C.4, "Selection Criteria Logical and Grouping Operators" describes the selection criteria logical and grouping operators. Table C.4. Selection Criteria Logical and Grouping Operators Logical and Grouping Operator Description && All fields must match , All fields must match (same as &&) || At least one field must match # At least one field must match (same as ||) ! Logical negation ( Left parenthesis (grouping operator) ) Right parenthesis (grouping operator) [ List start (grouping operator) ] List end (grouping operator) { List subset start (grouping operator) } List subset end (grouping operator)

Commands:
4.205. openmotif 4.205.1. RHBA-2011:1228 - openmotif bug fix update An updated openmotif package that fixes one bug is now available for Red Hat Enterprise Linux 6. The openmotif package includes the Motif shared libraries needed to run applications that are dynamically linked against Motif, as well as the Motif Window Manager (MWM). Bug Fix BZ# 584300 Previously, under certain circumstances, LabelGadget could have drawn over a parent window with the background color and, if using the Xft fonts, also over the text. With this update, the text and background drawing functionality has been fixed so that the aforementioned problems do not occur anymore. All users of openmotif are advised to upgrade to this updated package, which fixes this bug.

Commands: