mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 56. Kamelet Main Since Camel 3.11 A main class that is opinionated to boostrap and run Camel standalone with Kamelets (or plain YAML routes) for development and demo purposes. 56.1. Initial configuration The KameletMain is pre-configured with the following properties: camel.component.kamelet.location = classpath:/kamelets,github:apache:camel-kamelets/kamelets camel.component.rest.consumerComponentName = platform-http camel.component.rest.producerComponentName = vertx-http You can override these settings by updating the configuration in application.properties . 56.2. Automatic dependencies downloading The Kamelet Main can automatically download Kamelet YAML files from a remote location over http/https, and from github as well. The official Kamelets from the Apache Camel Kamelet Catalog is stored on github and they can be used out of the box as-is. For example a Camel route can be coded in YAML which uses the Earthquake Kamelet from the catalog, as shown below: - route: from: "kamelet:earthquake-source" steps: - unmarshal: json: {} - log: "Earthquake with magnitude USD{body[properties][mag]} at USD{body[properties][place]}" In the above example, the earthquake kamelet will be downloaded from github, and as well its required dependencies. For more information, see Kamelet Main example

Commands:
camel.component.kamelet.location = classpath:/kamelets,github:apache:camel-kamelets/kamelets camel.component.rest.consumerComponentName = platform-http camel.component.rest.producerComponentName = vertx-http
- route: from: "kamelet:earthquake-source" steps: - unmarshal: json: {} - log: "Earthquake with magnitude USD{body[properties][mag]} at USD{body[properties][place]}"
5.231. pcre 5.231.1. RHBA-2012:1240 - pcre bug fix release Updated pcre packages that fix four bugs are now available for Red Hat Enterprise Linux 6. The pcre packages provide the Perl-compatible regular expression (PCRE) library. Bug Fixes BZ# 756105 Prior to this update, matching patterns with repeated forward reference failed to match if the first character was not repeated at the start of the matching text. This update modifies the matching algorithm not to expect the first character again. Now, patterns with repeated forward references match as expected. BZ# 759475 Prior to this update, case-less patterns in UTF-8 mode did not match characters at the end of input text with encoding length that was shorter than the encoding length of character in the pattern, for example "/a/8i".This update modifies the pcre library to count the length of matched characters correctly. Now, case-less patterns match characters with different encoding length correctly even at the end of an input string. BZ# 799003 Prior to this update, manual pages for the pcre library contained misprints. This update modifies the manual pages. BZ# 842000 Prior to this update, applications that were compiled with the libpcrecpp library from the pcre version 6 could not been executed against libpcrecpp library from the pcre version 7 because the application binary interface (ABI) was mismatched. This update adds the compat RE::Init() function for the pcre version 6 to the pcre version 7 libpcrecpp library. Applications that were compiled on Red Hat Enterprise Linux 5 and use the RE::Init function can now be executed on Red Hat Enterprise Linux 6. All users of pcre are advised to upgrade to these updated packages, which fix these bugs. 5.231.2. RHBA-2012:0445 - pcre bug fix update Updated pcre packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The pcre packages provide the Perl-compatible regular expression (PCRE) library. Bug Fixes BZ# 613690 Prior to this update, the PCRE license file was missing from the pcre-static subpackage. This update adds the license file. BZ# 676636 Prior to this update, the pcretest(1) manual page contained various misprints. This update corrects these misprints. BZ# 676643 Prior to this update, the pcregrep(1) manual page contained various misprints. This update corrects these misprints. All users of pcre are advised to upgrade to these updated packages, which fix these bugs.

Commands:
4.3. VDB Content and Structure In Teiid Designer, the VDB file names use a .vdb file extension. VDBs are structurally just ZIP archive files containing 3 folders: META-INF - contains vdb.xml definition file. runtime-inf - contains a binary INDEX file for each model included in your VDB. project folder - contains of the models you will be adding in the VDB Editor (that is, *.xmi and *.xsd files) When deployed, the metadata is consumed by JBoss Data Virtualization in order to create the necessary runtime metadata for your model definitions. The vdb.xml file contains: VDB name, version, properties contained model information (name, translator name, connection info) translator info data role definitions for the referenced models import VDB references Fortunately, Teiid Designer simplifies the management of your VDBs by providing a dedicated VDB Editor which maintains a consistent, valid vdb.xml file for you and assists in synchronizing your workspace models with any related models in your VDB. (See Section E.8.1, "VDB Editor" )

Commands:
Part IV. Advanced Installation Options This part of the Red Hat Enterprise Linux Installation Guide covers more advanced or uncommon methods of installing Red Hat Enterprise Linux, including: customizing the installation program's behavior by specifying boot options setting up a PXE server to boot the installation program over a network installing with remote access through VNC using a Kickstart file to automate the installation process installing into a disk image instead of a physical drive upgrading a release of Red Hat Enterprise Linux to the current version

Commands:
Chapter 30. Deprecated Functionality in Red Hat Enterprise Linux 7 Symbols from libraries linked as dependencies no longer resolved by ld Previously, the ld linker resolved any symbols present in any linked library, even if some libraries were linked only implicitly as dependencies of other libraries. This allowed developers to use symbols from the implicitly linked libraries in application code and omit explicitly specifying these libraries for linking. For security reasons, ld has been changed to not resolve references to symbols in libraries linked implicitly as dependencies. As a result, linking with ld fails when application code attempts to use symbols from libraries not declared for linking and linked only implicitly as dependencies. To use symbols from libraries linked as dependencies, developers must explicitly link against these libraries as well. To restore the behavior of ld , use the -copy-dt-needed-entries command-line option. (BZ# 1292230 ) Windows guest virtual machine support limited As of Red Hat Enterprise Linux 7, Windows guest virtual machines are supported only under specific subscription programs, such as Advanced Mission Critical (AMC).

Commands:
Preface HawtIO provides enterprise monitoring tools for viewing and managing Red Hat HawtIO-enabled applications. It is a web-based console accessed from a browser to monitor and manage a running HawtIO-enabled container. HawtIO is based on the open source HawtIO software ( https://hawt.io/ ). HawtIO Diagnostic Console Guide describes how to manage applications with HawtIO. The audience for this guide are Apache Camel eco-system developers and administrators. This guide assumes familiarity with Apache Camel and the processing requirements for your organization. Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message .

Commands:
Chapter 17. EphemeralStorage schema reference Used in: JbodStorage , KafkaClusterSpec , KafkaNodePoolSpec , ZookeeperClusterSpec The type property is a discriminator that distinguishes use of the EphemeralStorage type from PersistentClaimStorage . It must have the value ephemeral for the type EphemeralStorage . Property Property type Description id integer Storage identification number. It is mandatory only for storage volumes defined in a storage of type 'jbod'. sizeLimit string When type=ephemeral, defines the total amount of local storage required for this EmptyDir volume (for example 1Gi). type string Must be ephemeral . kraftMetadata string (one of [shared]) Specifies whether this volume should be used for storing KRaft metadata. This property is optional. When set, the only currently supported value is shared . At most one volume can have this property set.

Commands:
20.2. XML Representation of a Group Resource Example 20.1. An XML representation of a group resource

Commands:
<group id="85bf8d97-273c-4a5c-b801-b17d58330dab" href="/ovirt-engine/api/groups/85bf8d97-273c-4a5c-b801-b17d58330dab"> <name>Everyone</name> <link rel="tags" href="/ovirt-engine/api/groups/85bf8d97-273c-4a5c-b801-b17d58330dab/tags"/> <link rel="permissions" href="/ovirt-engine/api/groups/85bf8d97-273c-4a5c-b801-b17d58330dab/permissions"/> <link rel="roles" href="/ovirt-engine/api/groups/85bf8d97-273c-4a5c-b801-b17d58330dab/roles"/> <domain_entry_id> 65656530303030302D303030302D303030302D303030 </domain_entry_id> <namespace>*</namespace> </group>
Configuring OpenShift Data Foundation Disaster Recovery for OpenShift Workloads Red Hat OpenShift Data Foundation 4.15 The OpenShift Data Foundation Disaster Recovery capabilities for Metropolitan and Regional regions is now General Available which also includes Disaster Recovery with stretch cluster. Red Hat Storage Documentation Team Abstract The intent of this solution guide is to detail the steps necessary to deploy OpenShift Data Foundation for disaster recovery with Advanced Cluster Management and stretch cluster to achieve a highly available storage infrastructure.

Commands:
9.2.4. Installing and Removing Package Groups PackageKit also has the ability to install Yum package groups, which it calls Package collections . Clicking on Package collections in the top-left list of categories in the Software Updates window allows us to scroll through and find the package group we want to install. In this case, we want to install Czech language support (the Czech Support group). Checking the box and clicking apply informs us how many additional packages must be installed in order to fulfill the dependencies of the package group. Figure 9.9. Installing the Czech Support package group Similarly, installed package groups can be uninstalled by selecting Package collections , unchecking the appropriate check box, and applying.

Commands:
Appendix C. Configuring a Jenkins freestyle project to deploy your application with the OpenShift Maven plugin Similar to using Maven and the OpenShift Maven plugin from your local host to deploy an application, you can configure Jenkins to use Maven and the OpenShift Maven plugin to deploy an application. Prerequisites Access to an OpenShift cluster. The Jenkins container image running on same OpenShift cluster. A JDK and Maven installed and configured on your Jenkins server. An application configured to use Maven, the OpenShift Maven plugin in the pom.xml , and built using a RHEL base image. Note For building and deploying your applications to OpenShift, Eclipse Vert.x 4.3 only supports builder images based on OpenJDK 8 and OpenJDK 11. Oracle JDK and OpenJDK 9 builder images are not supported. Example pom.xml <properties> ... <jkube.generator.from>registry.access.redhat.com/redhat-openjdk-18/openjdk18-openshift:latest</jkube.generator.from> </properties> The source of the application available in GitHub. Procedure Create a new OpenShift project for your application: Open the OpenShift Web console and log in. Click Create Project to create a new OpenShift project. Enter the project information and click Create . Ensure Jenkins has access to that project. For example, if you configured a service account for Jenkins, ensure that account has edit access to the project of your application. Create a new freestyle Jenkins project on your Jenkins server: Click New Item . Enter a name, choose Freestyle project , and click OK . Under Source Code Management , choose Git and add the GitHub url of your application. Under Build , choose Add build step and select Invoke top-level Maven targets . Add the following to Goals : clean oc:deploy -Popenshift -Djkube.namespace=MY_PROJECT Substitute MY_PROJECT with the name of the OpenShift project for your application. Click Save . Click Build Now from the main page of the Jenkins project to verify your application builds and deploys to the OpenShift project for your application. You can also verify that your application is deployed by opening the route in the OpenShift project of the application. steps Consider adding GITSCM polling or using the Poll SCM build trigger . These options enable builds to run every time a new commit is pushed to the GitHub repository. Consider adding a build step that executes tests before deploying.

Commands:
<properties> <jkube.generator.from>registry.access.redhat.com/redhat-openjdk-18/openjdk18-openshift:latest</jkube.generator.from> </properties>
clean oc:deploy -Popenshift -Djkube.namespace=MY_PROJECT
Chapter 1. Configuring Argo CD RBAC By default, any type of user, except the kube:admin user, logged into the default Argo CD instance does not have access to any services. But a user logged into a custom Argo CD instance is a read-only user by default. Note In Red Hat OpenShift GitOps v1.9.0 or earlier versions, any type of user, except the kube:admin user, logged into Argo CD using Red Hat SSO (RH SSO) is a read-only user by default. 1.1. Configuring user level access To manage and modify the user level access, configure the role-based access control (RBAC) section in the Argo CD custom resource (CR). Procedure Edit the argocd CR: USD oc edit argocd [argocd-instance-name] -n [namespace] Output metadata ... ... rbac: policy: 'g, rbacsystem:cluster-admins, role:admin' scopes: '[groups]' Add the policy configuration to the rbac section and add the name and the desired role to be applied to the user: metadata ... ... rbac: policy: g, <name>, role:<admin> scopes: '[groups]' Note Currently, RHSSO cannot read the group information of Red Hat OpenShift GitOps users. Therefore, configure the RBAC at the user level.

Commands:
oc edit argocd [argocd-instance-name] -n [namespace]
metadata rbac: policy: 'g, rbacsystem:cluster-admins, role:admin' scopes: '[groups]'
metadata rbac: policy: g, <name>, role:<admin> scopes: '[groups]'
4.15. Hewlett-Packard iLO The fence agents for HP iLO devices fence_ilo and HP iLO2 devices fence_ilo2 . share the same implementation. Table 4.16, "HP iLO (Integrated Lights Out) and HP iLO2" lists the fence device parameters used by these agents. Table 4.16. HP iLO (Integrated Lights Out) and HP iLO2 luci Field cluster.conf Attribute Description Name name A name for the server with HP iLO support. IP Address or Hostname ipaddr The IP address or host name assigned to the device. IP Port (optional) ipport TCP port to use for connection with the device. The default value is 443. Login login The login name used to access the device. Password passwd The password used to authenticate the connection to the device. Password Script (optional) passwd_script The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. Power Wait (seconds) power_wait Number of seconds to wait after issuing a power off or power on command. Delay (seconds) delay The number of seconds to wait before fencing is started. The default value is 0. Power Timeout (seconds) power_timeout Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. Shell Timeout (seconds) shell_timeout Number of seconds to wait for a command prompt after issuing a command. The default value is 3. Login Timeout (seconds) login_timeout Number of seconds to wait for a command prompt after login. The default value is 5. Times to Retry Power On Operation retry_on Number of attempts to retry a power on operation. The default value is 1. Figure 4.12, "HP iLO" shows the configuration screen for adding an HP iLO fence device. Figure 4.12. HP iLO The following command creates a fence device instance for a HP iLO device: The following is the cluster.conf entry for the fence_ilo device:

Commands:
ccs -f cluster.conf --addfencedev hpilotest1 agent=fence_hpilo ipaddr=192.168.0.1 login=root passwd=password123 power_wait=60
<fencedevices> <fencedevice agent="fence_ilo" ipaddr="192.168.0.1" login="root" name="hpilotest1" passwd="password123" power_wait="60"/> </fencedevices>
Chapter 3. Ruby Examples 3.1. Connecting to the Red Hat Virtualization Manager The Connection class is the entry point of the software development kit. It provides access to the services of the Red Hat Virtualization Manager's REST API. The parameters of the Connection class are: url - Base URL of the Red Hat Virtualization Manager API username password ca_file - PEM file containing the trusted CA certificates. The ca.pem file is required when connecting to a server protected by TLS. If you do not specify the ca_file , the system-wide CA certificate store is used. Connecting to the Red Hat Virtualization Manager connection = OvirtSDK4::Connection.new( url: 'https://engine.example.com/ovirt-engine/api', username: 'admin@internal', password: '...', ca_file: 'ca.pem', ) Important The connection holds critical resources, including a pool of HTTP connections to the server and an authentication token. You must free these resources when they are no longer in use: The connection, and all the services obtained from it, cannot be used after the connection has been closed. If the connection fails, the software development kit will raise an Error exception, containing details of the failure. For more information, see http://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4/Connection:initialize .

Commands:
connection = OvirtSDK4::Connection.new( url: 'https://engine.example.com/ovirt-engine/api', username: 'admin@internal', password: '...', ca_file: 'ca.pem', )
connection.close
Comments and Feedback In the spirit of open source, we invite anyone to provide feedback and comments on any reference architecture. Although we review our papers internally, sometimes issues or typographical errors are encountered. Feedback allows us to not only improve the quality of the papers we produce, but allows the reader to provide their thoughts on potential improvements and topic expansion to the papers. Feedback on the papers can be provided by emailing ansible-feedback@redhat.com . Please refer to the title within the email.

Commands:
Chapter 17. Authentication and Interoperability Apache Modules for External Authentication A set of Apache modules was added to Red Hat Enterprise Linux 6.6 as a Technology Preview. The mod_authnz_pam , mod_intercept_form_submit , and mod_lookup_identity Apache modules in the respective packages can be used by Web applications to achieve tighter interaction with external authentication and identity sources, such as Identity Management in Red Hat Enterprise Linux. Simultaneous maintaining of TGTs for multiple KDCs Kerberos version 1.10 added a new cache storage type, DIR:, which allows Kerberos to maintain Ticket Granting Tickets (TGTs) for multiple Key Distribution Centers (KDCs) simultaneously and auto-select between them when negotiating with Kerberized resources. Red Hat Enterprise Linux 6.4 and later includes SSSD enhanced to allow the users to select the DIR: cache for users that are logging in using SSSD. This feature is introduced as a Technology Preview. Package: sssd-1.13.3 Cross-Forest Kerberos Trust Functionality in Identity Management The Cross-Forest Kerberos Trust functionality provided by Identity Management (IdM) is included as a Technology Preview. This feature allows to create a trust relationship between an IdM and an Active Directory (AD) domain. This means that users from the AD domain can access resources and services from the IdM domain with their AD credentials. No data needs to be synchronized between the IdM and AD domain controllers; AD user are always authenticated against the AD domain controller and information about users is looked up without the need for synchronization. This feature is provided by the optional ipa-server-trust-ad package. This package depends on features which are only available in samba4 . Because samba4-* packages conflicts with the corresponding samba-* packages, all samba-* packages must be removed before ipa-server-trust-ad can be installed. When the ipa-server-trust-ad package is installed, the ipa-adtrust-install utility must be run on all IdM servers and replicas to enable IdM to handle trusts. When this is done, a trust can be established from the command line using the ipa trust-add command or the IdM web UI. For more information, see the Identity Management Guide for Red Hat Enterprise Linux . Note that Red Hat recommends to connect Red Hat Enterprise Linux 6 IdM clients to a Red Hat Enterprise Linux 7 IdM server for cross-forest trust capability. Trusts are fully supported on servers running Red Hat Enterprise Linux 7. Configuration with Red Hat Enterprise Linux 6 clients connected to a Red Hat Enterprise Linux 7 server for cross-forest trust is fully supported as well. In such setups, it is recommended to use the latest version of Red Hat Enterprise Linux 6 on the client side and the latest version of Red Hat Enterprise Linux 7 on the server side. Packages: ipa-3.0.0 and samba-3.6.23

Commands:
Appendix F. Revision History Revision History Revision 2-42 Thu August 9 2019 Jiri Herrmann Version for 7.7 GA publication Revision 2-40 Thu May 23 2019 Jiri Herrmann Version for 7.7 Beta publication Revision 2-39 Thu Oct 25 2018 Jiri Herrmann Version for 7.6 GA publication Revision 2-37 Thu Aug 14 2018 Jiri Herrmann Version for 7.6 Beta publication Revision 2-36 Thu Aug 14 2018 Jiri Herrmann Added a rework of the virtual storage chapters Revision 2-35 Thu Apr 5 2018 Jiri Herrmann Version for 7.5 GA publication Revision 2-32 Thu Jul 27 2017 Jiri Herrmann Version for 7.4 GA publication Revision 2-32 Thu Jul 27 2017 Jiri Herrmann Version for 7.4 GA publication Revision 2-29 Mon Oct 17 2016 Jiri Herrmann Version for 7.3 GA publication Revision 2-24 Thu Dec 17 2015 Laura Novich Republished guide and fixed multiple issues Revision 2-23 Sun Nov 22 2015 Laura Novich Republished guide Revision 2-21 Thu Nov 12 2015 Laura Novich Multiple content updates for 7.2 Revision 2-19 Thu Oct 08 2015 Jiri Herrmann Cleaned up the Revision History Revision 2-17 Thu Aug 27 2015 Dayle Parker Updates for the 7.2 beta release

Commands:
C.2. Cache org.infinispan.CacheImpl The Cache component represents an individual cache instance. Table C.3. Attributes Name Description Type Writable cacheName Returns the cache name. String No cacheStatus Returns the cache status. String No configurationAsProperties Returns the cache configuration in form of properties. Properties No version Returns the version of Infinispan String No cacheAvailability Returns the cache availability String Yes Table C.4. Operations Name Description Signature start Starts the cache. void start() stop Stops the cache. void stop() clear Clears the cache. void clear() 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands: