mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 6. Connecting to external services You can connect a router to an external service such as a message broker. The services may be running in the same OpenShift cluster as the router network, or running outside of OpenShift. Prerequisites You must have access to a message broker. Procedure This procedure describes how to connect a router to a broker and configure a link route to connect messaging clients to it. Start editing the Interconnect Custom Resource YAML file that describes the router deployment that you want to connect to a broker. In the spec section, configure the connection and link route. Sample router-mesh.yaml file apiVersion: interconnectedcloud.github.io/v1alpha1 kind: Interconnect metadata: name: router-mesh spec: ... connectors: 1 - name: my-broker host: broker port: 5672 routeContainer: true linkRoutes: 2 - prefix: q1 direction: in connection: my-broker - prefix: q1 direction: out connection: my-broker 1 The connection to be used to connect this router to the message broker. The Operator will configure this connection from every router defined in this router deployment to the broker. If you only want a single connection between the router network and the broker, then configure a listener instead of a connector and have the broker establish the connection. 2 The link route configuration. It defines the incoming and outgoing links and connection to be used to connect messaging applications to the message broker. Verify that the router has established the link route to the message broker. Additional resources For more information about link routes, see Creating link routes .

Commands:
oc edit -f router-mesh.yaml
apiVersion: interconnectedcloud.github.io/v1alpha1 kind: Interconnect metadata: name: router-mesh spec: connectors: 1 - name: my-broker host: broker port: 5672 routeContainer: true linkRoutes: 2 - prefix: q1 direction: in connection: my-broker - prefix: q1 direction: out connection: my-broker
oc exec router-mesh-fb6bc5797-crvb6 -it -- qdstat --linkroutes Link Routes address dir distrib status ==================================== q1 in linkBalanced active q1 out linkBalanced active
1.7. Removing a Directory Server Instance If you run multiple instances on a server, you can remove individual instances of them. When you remove an instance, the content of the /var/lib/dirsrv/slapd- instance_name / and /etc/dirsrv/slapd- instance_name / directories are removed. Important The /var/lib/dirsrv/slapd- instance_name / directory contains the database, as well as the backup and export directory. The /etc/dirsrv/slapd- instance_name / directory contains the instance configuration and the network security services (NSS) database. Before you remove an instance, backup this data. 1.7.1. Removing an Instance Using the Command Line To remove an instance using the command line: 1.7.2. Removing an Instance Using the Web Console To remove an instance using the web console: Open the Directory Server user interface in the web console. See Section 1.4, "Logging Into Directory Server Using the Web Console" . Select the instance. Click the Actions button, and select Remove instance .

Commands:
dsctl instance_name remove --do-it Removing instance Completed instance removal
Chapter 9. Pacemaker Rules Rules can be used to make your configuration more dynamic. One common example is to set one value for resource-stickiness during working hours, to prevent resources from being moved back to their most preferred location, and another on weekends when no one is around to notice an outage. Another use of rules might be to assign machines to different processing groups (using a node attribute) based on time and to then use that attribute when creating location constraints. Each rule can contain a number of expressions, date-expressions and even other rules. The results of the expressions are combined based on the rule's boolean-op field to determine if the rule ultimately evaluates to true or false . What happens depends on the context in which the rule is being used. Table 9.1. Properties of a Rule Field Description role Limits the rule to apply only when the resource is in that role. Allowed values: Started , Slave, and Master . NOTE: A rule with role="Master" cannot determine the initial location of a clone instance. It will only affect which of the active instances will be promoted. score The score to apply if the rule evaluates to true . Limited to use in rules that are part of location constraints. score-attribute The node attribute to look up and use as a score if the rule evaluates to true . Limited to use in rules that are part of location constraints. boolean-op How to combine the result of multiple expression objects. Allowed values: and and or . The default value is and . 9.1. Node Attribute Expressions Node attribute expressions are used to control a resource based on the attributes defined by a node or nodes. Table 9.2. Properties of an Expression Field Description value User supplied value for comparison attribute The node attribute to test type Determines how the value(s) should be tested. Allowed values: string , integer , version operation The comparison to perform. Allowed values: * lt - True if the node attribute's value is less than value * gt - True if the node attribute's value is greater than value * lte - True if the node attribute's value is less than or equal to value * gte - True if the node attribute's value is greater than or equal to value * eq - True if the node attribute's value is equal to value * ne - True if the node attribute's value is not equal to value * defined - True if the node has the named attribute * not_defined - True if the node does not have the named attribute

Commands:
7.2. Guide View In this section, we introduce the Guides View by walking through a simple example. For this example, we will follow the Model JDBC Source Action Set. The actions appear in the following order: Define Teiid Model Project Create JDBC connection Create source model for JDBC data source Preview Data Define VDB Edit VDB Execute VDB The action names are self explanatory. We will create a new Model Project in the workspace, then define our connection properties to a MySQL database. We will then connect to the database and import the metadata, creating a source model in Teiid Designer . we will preview the database contents. Finally we will define a VDB and then deploy it to a running JBoss Data Virtualization Server to execute.

Commands:
Chapter 245. OGNL Language Available as of Camel version 1.1 Camel allows OGNL to be used as an Expression or Predicate the DSL or Xml Configuration. You could use OGNL to create an Predicate in a Message Filter or as an Expression for a Recipient List You can use OGNL dot notation to invoke operations. If you for instance have a body that contains a POJO that has a getFamilyName method then you can construct the syntax as follows: "request.body.familyName" // or "getRequest().getBody().getFamilyName()" 245.1. OGNL Options The OGNL language supports 1 options, which are listed below. Name Default Java Type Description trim true Boolean Whether to trim the value to remove leading and trailing whitespaces and line breaks 245.2. Spring Boot Auto-Configuration The component supports 2 options, which are listed below. Name Description Default Type camel.language.ognl.enabled Enable ognl language true Boolean camel.language.ognl.trim Whether to trim the value to remove leading and trailing whitespaces and line breaks true Boolean 245.3. Variables Variable Type Description this Exchange the Exchange is the root object exchange Exchange the Exchange object exception Throwable the Exchange exception (if any) exchangeId String the exchange id fault Message the Fault message (if any) request Message the exchange.in message response Message the exchange.out message (if any) properties Map the exchange properties property(name) Object the property by the given name property(name, type) Type the property by the given name as the given type 245.4. Samples For example you could use OGNL inside a Message Filter in XML <route> <from uri="seda:foo"/> <filter> <ognl>request.headers.foo == 'bar'</ognl> <to uri="seda:bar"/> </filter> </route> And the sample using Java DSL: from("seda:foo").filter().ognl("request.headers.foo == 'bar'").to("seda:bar"); 245.5. Loading script from external resource Available as of Camel 2.11 You can externalize the script and have Camel load it from a resource such as "classpath:" , "file:" , or "http:" . This is done using the following syntax: "resource:scheme:location" , eg to refer to a file on the classpath you can do: .setHeader("myHeader").ognl("resource:classpath:myognl.txt") 245.6. Dependencies To use OGNL in your camel routes you need to add the a dependency on camel-ognl which implements the OGNL language. If you use maven you could just add the following to your pom.xml, substituting the version number for the latest & greatest release (see the download page for the latest versions). <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-ognl</artifactId> <version>x.x.x</version> </dependency> Otherwise, you'll also need OGNL

Commands:
"request.body.familyName" // or "getRequest().getBody().getFamilyName()"
<route> <from uri="seda:foo"/> <filter> <ognl>request.headers.foo == 'bar'</ognl> <to uri="seda:bar"/> </filter> </route>
from("seda:foo").filter().ognl("request.headers.foo == 'bar'").to("seda:bar");
.setHeader("myHeader").ognl("resource:classpath:myognl.txt")
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-ognl</artifactId> <version>x.x.x</version> </dependency>
20.16.9.14. Quality of service This section of the domain XML provides setting quality of service. Incoming and outgoing traffic can be shaped independently. The bandwidth element can have at most one inbound and at most one outbound child elements. Leaving any of these children element out results in no QoS being applied on that traffic direction. Therefore, when you want to shape only domain's incoming traffic, use inbound only, and vice versa. Each of these elements has one mandatory attribute average (or floor as described below). average specifies average bit rate on the interface being shaped. Then there are two optional attributes: peak , which specifies maximum rate at which interface can send data, and burst , which specifies the amount of bytes that can be burst at peak speed. Accepted values for attributes are integer numbers. The units for average and peak attributes are kilobytes per second, whereas burst is only set in kilobytes. In addition, inbound traffic can optionally have a floor attribute. This guarantees minimal throughput for shaped interfaces. Using the floor requires that all traffic goes through one point where QoS decisions can take place. As such it may only be used in cases where the interface type='network'/ with a forward type of route , nat , or no forward at all). It should be noted that within a virtual network, all connected interfaces are required to have at least the inbound QoS set ( average at least) but the floor attribute does not require specifying average . However, peak and burst attributes still require average . At the present time, ingress qdiscs may not have any classes, and therefore floor may only be applied only on inbound and not outbound traffic. To specify the QoS configuration settings, use a management tool to make the following changes to the domain XML: ... <devices> <interface type='network'> <source network='default'/> <target dev='vnet0'/> <bandwidth> <inbound average='1000' peak='5000' floor='200' burst='1024'/> <outbound average='128' peak='256' burst='256'/> </bandwidth> </interface> <devices> ... Figure 20.51. Quality of service

Commands:
<devices> <interface type='network'> <source network='default'/> <target dev='vnet0'/> <bandwidth> <inbound average='1000' peak='5000' floor='200' burst='1024'/> <outbound average='128' peak='256' burst='256'/> </bandwidth> </interface> <devices>
7.185. plymouth 7.185.1. RHBA-2013:0321 - plymouth bug fix and enhancement update Updated plymouth packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The plymouth packages provide a graphical boot animation in place of the text messages that are normally displayed. Text messages are instead redirected to a log file for viewing after boot. Note The plymouth packages have been upgraded to upstream version 0.8.3, which provides a number of bug fixes and enhancements over the version. (BZ#853207) All users of plymouth are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
20.5. Archiving File Systems With ACLs By default, the dump command now preserves ACLs during a backup operation. When archiving a file or file system with tar , use the --acls option to preserve ACLs. Similarly, when using cp to copy files with ACLs, include the --preserve=mode option to ensure that ACLs are copied across too. In addition, the -a option (equivalent to -dR --preserve=all ) of cp also preserves ACLs during a backup along with other information such as timestamps, SELinux contexts, and the like. For more information about dump , tar , or cp , refer to their respective man pages. The star utility is similar to the tar utility in that it can be used to generate archives of files; however, some of its options are different. Refer to Table 20.1, "Command Line Options for star " for a listing of more commonly used options. For all available options, refer to man star . The star package is required to use this utility. Table 20.1. Command Line Options for star Option Description -c Creates an archive file. -n Do not extract the files; use in conjunction with -x to show what extracting the files does. -r Replaces files in the archive. The files are written to the end of the archive file, replacing any files with the same path and file name. -t Displays the contents of the archive file. -u Updates the archive file. The files are written to the end of the archive provided the following are true: They do not already exist in the archive. The files to be updated are newer than the files of the same name already in the archive. This option only works if the archive is a file or an unblocked tape which can go in reverse (as opposed to only going back to 0). -x Extracts the files from the archive. If used with -U and a file in the archive is older than the corresponding file on the file system, the file is not extracted. -help Displays the most important options. -xhelp Displays the least important options. -/ Do not strip leading slashes from file names when extracting the files from an archive. By default, they are stripped when files are extracted. -acl When creating or extracting, archives or restores any ACLs associated with the files and directories.

Commands:
Chapter 1. Red Hat OpenShift support for Windows Containers overview Red Hat OpenShift support for Windows Containers is a feature providing the ability to run Windows compute nodes in an OpenShift Container Platform cluster. This is possible by using the Red Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes. With a Red Hat subscription, you can get support for running Windows workloads in OpenShift Container Platform. Windows instances deployed by the WMCO are configured with the containerd container runtime. For more information, see the release notes . You can add Windows nodes either by creating a machine set or by specifying existing Bring-Your-Own-Host (BYOH) Window instances through a configuration map . Note Machine sets are not supported for bare metal or provider agnostic clusters. For workloads including both Linux and Windows, OpenShift Container Platform allows you to deploy Windows workloads running on Windows Server containers while also providing traditional Linux workloads hosted on Red Hat Enterprise Linux CoreOS (RHCOS) or Red Hat Enterprise Linux (RHEL). For more information, see getting started with Windows container workloads . You need the WMCO to run Windows workloads in your cluster. The WMCO orchestrates the process of deploying and managing Windows workloads on a cluster. For more information, see how to enable Windows container workloads . You can create a Windows MachineSet object to create infrastructure Windows machine sets and related machines so that you can move supported Windows workloads to the new Windows machines. You can create a Windows MachineSet object on multiple platforms. You can schedule Windows workloads to Windows compute nodes. You can perform Windows Machine Config Operator upgrades to ensure that your Windows nodes have the latest updates. You can remove a Windows node by deleting a specific machine. You can use Bring-Your-Own-Host (BYOH) Windows instances to repurpose Windows Server VMs and bring them to OpenShift Container Platform. BYOH Windows instances benefit users who are looking to mitigate major disruptions in the event that a Windows server goes offline. You can use BYOH Windows instances as nodes on OpenShift Container Platform 4.8 and later versions. You can disable Windows container workloads by performing the following: Uninstalling the Windows Machine Config Operator Deleting the Windows Machine Config Operator namespace

Commands:
4.280. sblim-cmpi-base 4.280.1. RHBA-2011:1548 - sblim-cmpi-base bug fix update An updated sblim-cmpi-base package that fixes several bugs is now available for Red Hat Enterprise Linux 6. The sblim-cmpi-base package provides Standards Based Linux Instrumentation for Manageability (SBLIM) Common Manageability Programming Interface (CMPI) Base Providers for System-Related Common Information Model (CIM) classes. The sblim-cmpi-base package has been upgraded to upstream version 1.6.1, which provides a number of bug fixes over the version. (BZ# 694514 ) All users of sblim-cmpi-base are advised to upgrade to this updated package, which fixes these bugs.

Commands:
9.2. Installing AIDE To install the aide package, enter the following command as root : To generate an initial database, enter the following command as root : Note In the default configuration, the aide --init command checks just a set of directories and files defined in the /etc/aide.conf file. To include additional directories or files in the AIDE database, and to change their watched parameters, edit /etc/aide.conf accordingly. To start using the database, remove the .new substring from the initial database file name: To change the location of the AIDE database, edit the /etc/aide.conf file and modify the DBDIR value. For additional security, store the database, configuration, and the /usr/sbin/aide binary file in a secure location such as a read-only media. Important To avoid SELinux denials after the AIDE database location change, update your SELinux policy accordingly. See the SELinux User's and Administrator's Guide for more information.

Commands:
~]# yum install aide
~]# aide --init AIDE, version 0.14 ### AIDE database at /var/lib/aide/aide.db.new.gz initialized.
~]# mv /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz
4.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. By default, anonymous users have read access to files in /var/ftp/ when they log in via FTP. This directory is labeled with the public_content_t type, allowing only read access, even if write access is configured in /etc/vsftpd/vsftpd.conf . The public_content_t type is accessible to other services, such as Apache HTTP Server, Samba, and NFS. Use one of the following types to share files through FTP: public_content_t Label files and directories you have created with the public_content_t type to share them read-only through vsftpd. Other services, such as Apache HTTP Server, Samba, and NFS, also have access to files labeled with this type. Files labeled with the public_content_t type cannot be written to, even if Linux permissions allow write access. If you require write access, use the public_content_rw_t type. public_content_rw_t Label files and directories you have created with the public_content_rw_t type to share them with read and write permissions through vsftpd . Other services, such as Apache HTTP Server, Samba, and NFS, also have access to files labeled with this type. Remember that Booleans for each service must be enabled before they can write to files labeled with this type.

Commands:
Chapter 20. Kernel Kernel Media support The following features are presented as Technology Previews: The latest upstream video4linux Digital video broadcasting Primarily infrared remote control device support Various webcam support fixes and improvements Package: kernel-2.6.32-696 Linux (NameSpace) Container [LXC] Linux containers provide a flexible approach to application runtime containment on bare-metal systems without the need to fully virtualize the workload. Red Hat Enterprise Linux 6 provides application level containers to separate and control the application resource usage policies through cgroups and namespaces. This release includes basic management of container life-cycle by allowing creation, editing and deletion of containers using the libvirt API and the virt-manager GUI. Linux Containers are a Technology Preview. Packages: libvirt-0.10.2-62 , virt-manager-0.9.0-33 Diagnostic pulse for the fence_ipmilan agent, BZ# 655764 A diagnostic pulse can now be issued on the IPMI interface using the fence_ipmilan agent. This new Technology Preview is used to force a kernel dump of a host if the host is configured to do so. Note that this feature is not a substitute for the off operation in a production cluster. Package: fence-agents-4.0.15-13

Commands:
Preface Welcome to the Red Hat JBoss Core Services version 2.4.57 Service Pack 6 release. Red Hat JBoss Core Services Apache HTTP Server is an open source web server developed by the Apache Software Foundation . The Apache HTTP Server includes the following features: Implements the current HTTP standards, including HTTP/1.1 and HTTP/2. Supports Transport Layer Security (TLS) encryption through OpenSSL , which provides secure connections between the web server and web clients. Supports extensible functionality through the use of modules, some of which are included with the Red Hat JBoss Core Services Apache HTTP Server. This release of Red Hat JBoss Core Services includes some important security updates.

Commands:
Chapter 1. Creating a system group to manage multiple systems In the Insights Workspaces application, you can consolidate multiple systems into groups, simplifying their management. For example, you can easily mitigate vulnerabilities and update systems that are alike. Prerequisites You have a Red Hat Hybrid Cloud Console account. You have registered the systems you plan to group with the Insights Inventory application. Procedure Access Red Hat Hybrid Cloud Console platform and log in. From the console dashboard, navigate to Red Hat Insights > RHEL > Inventory . In the dashboard menu, click Inventory > Groups . On the Groups page, click Create group . In the Create Group dialog, add a group name that describes your group, for example retail-north-america . Click Create . On the Inventory > Groups page, use the search box to find the group you just created and click the group name, for example retail-north-america , from the group list. Verification If the group creation was successful, you can see the group name on the page for your group.

Commands: