mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 11. Allowing JavaScript-based access to the API server from additional hosts 11.1. Allowing JavaScript-based access to the API server from additional hosts The default OpenShift Container Platform configuration only allows the OpenShift web console to send requests to the API server. If you need to access the API server or OAuth server from a JavaScript application using a different hostname, you can configure additional hostnames to allow. Prerequisites Access to the cluster as a user with the cluster-admin role. Procedure Edit the APIServer resource: USD oc edit apiserver.config.openshift.io cluster Add the additionalCORSAllowedOrigins field under the spec section and specify one or more additional hostnames: apiVersion: config.openshift.io/v1 kind: APIServer metadata: annotations: release.openshift.io/create-only: "true" creationTimestamp: "2019-07-11T17:35:37Z" generation: 1 name: cluster resourceVersion: "907" selfLink: /apis/config.openshift.io/v1/apiservers/cluster uid: 4b45a8dd-a402-11e9-91ec-0219944e0696 spec: additionalCORSAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) 1 1 The hostname is specified as a Golang regular expression that matches against CORS headers from HTTP requests against the API server and OAuth server. Note This example uses the following syntax: The (?i) makes it case-insensitive. The // pins to the beginning of the domain and matches the double slash following http: or https: . The \. escapes dots in the domain name. The (:|\z) matches the end of the domain name (\z) or a port separator (:) . Save the file to apply the changes.

Commands:
oc edit apiserver.config.openshift.io cluster
apiVersion: config.openshift.io/v1 kind: APIServer metadata: annotations: release.openshift.io/create-only: "true" creationTimestamp: "2019-07-11T17:35:37Z" generation: 1 name: cluster resourceVersion: "907" selfLink: /apis/config.openshift.io/v1/apiservers/cluster uid: 4b45a8dd-a402-11e9-91ec-0219944e0696 spec: additionalCORSAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) 1
Chapter 1. Planning your ITSM integration with automation services catalog Plan for the updates and modifications required to your Ansible Automation Platform and playbook inventory to integrate with your ITSM system. Some changes will require specific levels of administrative permissions in both Ansible Tower and automation services catalog. This section will detail the exact roles required to perform updates, and the artifacts you will need to modify. Required permissions You will require the following roles to complete the integration workflow: You can write or update the playbooks used for ITSM integration. You are an Ansible Tower administrator and can create job templates and add surveys. You are a Catalog Administrator and can create portfolios, edit surveys, and set order processes. Playbooks Write or update those playbooks used in the job templates and workflows you intend to use for ITSM integration with Automation Services Catalog. Ansible Tower job and workflow template surveys Update surveys attached to job templates running the before and after playbooks to support substitutable values. Automation Services Catalog Update surveys set to products in your ITSM integration workflow to enable substitution.

Commands:
1.11. Create a Connection to a VDB Using the Data Source Class Prerequisites The client application must have the JBoss Data Virtualization EAP_HOME /dataVirtualization/jdbc/teiid- VERSION -redhat- N -jdbc.jar JAR file in its classpath. (If the application is running on the same application server as the JBoss Data Virtualization instance to which the connection is desired, then this will already be the case.) JBoss Data Virtualization must be installed and running, with the relevant virtual databases (VDBs) deployed. Procedure 1.2. Create a Connection to a VDB Using the Data Source Class Create a Connection Object Create a org.teiid.jdbc.TeiidDataSource object, set the required properties, and use the TeiidDataSource.getConnection() method to obtain a Connection object. For example: See Also: Section 1.9, "Connection Properties for the Driver and Data Source Classes" Section 1.12, "Additional Data Source Connection Properties"

Commands:
public class TeiidClient { public Connection getConnection(String user, String password) throws Exception { TeiidDataSource ds = new TeiidDataSource(); ds.setUser(user); ds.setPassword(password); ds.setServerName("localhost"); ds.setPortNumber(31000); ds.setDatabaseName("myVDB"); return ds.getConnection(); } }
Chapter 2. Preparing your environment for Satellite installation in an IPv6 network You can install and use Satellite in an IPv6 network. Before installing Satellite in an IPv6 network, view the limitations and ensure that you meet the requirements. To provision hosts in an IPv6 network, after installing Satellite, you must also configure Satellite for the UEFI HTTP boot provisioning. For more information, see Section 4.5, "Configuring Satellite for UEFI HTTP boot provisioning in an IPv6 network" . 2.1. Limitations of Satellite installation in an IPv6 network Satellite installation in an IPv6 network has the following limitations: You can install Satellite and Capsules in IPv6-only systems, dual-stack installation is not supported. Although Satellite provisioning templates include IPv6 support for PXE and HTTP (iPXE) provisioning, the only tested and certified provisioning workflow is the UEFI HTTP Boot provisioning. This limitation only relates to users who plan to use Satellite to provision hosts. 2.2. Requirements for Satellite installation in an IPv6 network Before installing Satellite in an IPv6 network, ensure that you meet the following requirements: You must deploy an external DHCP IPv6 server as a separate, unmanaged service to bootstrap clients into GRUB2. GRUB2 configures IPv6 networking by using DHCPv6 or by assigning a static IPv6 address. This is required because the DHCP server in Red Hat Enterprise Linux (ISC DHCP) does not provide an integration API for managing IPv6 records, therefore the Capsule DHCP plugin that provides DHCP management is limited to IPv4 subnets. You must deploy an external HTTP proxy server that supports both IPv4 and IPv6. This is required because Red Hat Content Delivery Network distributes content only over IPv4 networks, therefore you must use this proxy to pull content into the Satellite on your IPv6 network. You must configure Satellite to use this dual stack (supporting both IPv4 and IPv6) HTTP proxy server as the default proxy. For more information, see Adding a Default HTTP Proxy to Satellite .

Commands:
6.2. Run JBoss Data Grid (Library Mode) Use the provided instructions to run Red Hat JBoss Data Grid with Maven in Library mode. Note To simplify embedding Red Hat JBoss Data Grid directly in your application, the distribution of JBoss Data Grid contains fewer, consolidated jars. For the list of supported jar files, see the Packaging Revisions in the Release Notes. Infinispan Embedded without Querying Add the following dependencies to the pom.xml file: Add infinispan-embedded dependency: Infinispan Embedded with Querying Add the following dependencies to the pom.xml file: Add infinispan-embedded-query dependency: Warning The Infinispan query API directly exposes the Hibernate Search and the Lucene APIs and cannot be embedded within the infinispan-embedded-query.jar file. Do not include other versions of Hibernate Search and Lucene in the same deployment as infinispan-embedded-query . This action will cause classpath conflicts and result in unexpected behavior. Report a bug

Commands:
<dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-embedded</artifactId> <version>USD{infinispan.version}</version> </dependency>
<dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-embedded-query</artifactId> <version>USD{infinispan.version}</version> </dependency>
4.357. xorg-x11-drv-wacom and wacomcpl 4.357.1. RHBA-2011:1588 - xorg-x11-drv-wacom and wacomcpl bug fix and enhancement update Updated xorg-x11-drv-wacom and wacomcpl packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-wacom package provides an X Window System input device driver that allows the X server to handle Wacom tablets with extended functionality. The wacomcpl package provides a graphical user interface (GUI) for the xorg-x11-drv-wacom X input device driver. The wacomcpl package has been upgraded to upstream version 0.10, which provides a number of bug fixes and enhancements over the version. (BZ# 713864 ) Bug Fixes BZ# 713769 With this update, the new X.Org server is now supported. BZ# 641759 Previously, the xsetwacom(1) manual page contained a typographical error. This update corrects the typographical error. BZ# 675672 Previously, calibration could be inaccurate when using TwinView while the orientation was set to "LeftOf". With this update, the source code is modified and calibration now works as expected. Enhancements BZ# 711618 Prior to this update, the wacomcpl utility supported only a single wacomcplrc file in the user's home directory. All the user settings were restored from this file when logging in. When various users logged into multiple machines with a different setup, a user had to update the wacomcplrc file every time. With this update, wacomcpl is modified to support host-specific wacomcplrc files. If no file exists with a hostname suffix, wacomcpl finally tries to load the wacomcplrc file without the suffix. BZ# 711619 With this update, the eraser automatically updates to the same calibration setting as the stylus when calibrating or binding the stylus to a screen using wacomcpl. All users of xorg-x11-drv-wacom and wacomcpl are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Appendix A. Using your subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the AMQ Streams for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-08-12 11:04:53 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Chapter 12. Compiler and Tools SystemTap SystemTap is a tracing and probing tool that allows users to study and monitor the activities of the operating system (particularly, the kernel) in fine detail. It provides information similar to the output of tools like netstat , ps , top , and iostat ; however, SystemTap is designed to provide more filtering and analysis options for collected information. SystemTap in Red Hat Enterprise Linux 6.2 is updated to version 1.6, providing: Kernel modules with a hyphen (" - ") in their name, such as i2c-core are now handled properly. process.mark now supports USDUSDparms for reading probe parameters. Improved and simplified operation of the SystemTap compile-server and client : compile-server may cache script build results for improved performance. compile-server and client now communicate exchange version information to adjust the communication protocol accordingly and use the newest version of the server possible. Removal of deprecated tools: stap-client , stap-authorize-server-cert , stap-authorize-signing-cert , stap-find-or-start-server , and stap-find-servers . For remote execution, the --remote USER@HOST functionality can now be specified multiple times and will automatically build the script for distinct kernel and architecture configurations, and run it on all named machines at once. The staprun utility now allows multiple instances of the same script to be run at the same time.

Commands:
15.3. RollingUpgradeManager Operations The RollingUpgradeManager Mbean handles the operations that allow data to be migrated from one version of Red Hat JBoss Data Grid to another when performing rolling upgrades. The RollingUpgradeManager operations are: recordKnownGlobalKeyset retrieves the entire keyset from the cluster running on the old version of JBoss Data Grid. synchronizeData performs the migration of data from the Source Cluster to the Target Cluster, which is running the new version of JBoss Data Grid. disconnectSource disables the Source Cluster, the older version of JBoss Data Grid, once data migration to the Target Cluster is complete. Report a bug

Commands:
8.256. vte 8.256.1. RHBA-2014:0638 - vte bug fix update Updated vte packages that fix one bug are now available for Red Hat Enterprise Linux 6. Virtual Terminal Emulator (VTE) is a terminal emulator widget for use in Gtk2 applications. Bug Fix BZ# 1063741 Previously, Virtual Terminal Emulator (VTE) did not correctly determine how many bytes could be read before performing a UI update and proceeding further. As a consequence, running the cat command on a large text file resulted in the GNOME terminal responding slowly. A patch has been applied to address this bug, and the performance of the GNOME terminal is no longer slowed down in the described situation. Users of vte are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 6. Configuring the heap size for Red Hat build of OpenJDK application on RHEL You can configure Red Hat build of OpenJDK to use a customized heap size. Procedure Add the maximum heap size option to the java command when running your application. For example, to set the maximum heap size to 100 megabytes, use the -Xmx100m option: Additional resources For more information about the Xmx option, see -Xmxsize in the Java documentation . Revised on 2024-11-18 12:58:13 UTC

Commands:
java -Xmx100m <your_application_name>
8.95. ipset 8.95.1. RHBA-2014:1543 - ipset bug fix update Updated ipset packages that fix one bug are now available for Red Hat Enterprise Linux 6. The ipset packages provide IP sets, a framework inside the Linux 2.4.x and 2.6.x kernel, which can be administered by the ipset utility. Depending on the type, an IP set can currently store IP addresses, TCP/UDP port numbers or IP addresses with MAC addresses in a way that ensures high speed when matching an entry against a set. Bug Fix BZ# 888571 Prior to this update, ipset initiation script which would load the ipset rules was missing. Consequently, security problems at system initiation could occur. This update provides all the files necessary to add an ipset systemd service, which starts up before iptables and stops afterwards. As a result, ipset rules can be started, stopped, and saved as intended. Users of ipset are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 15. 4.11.1 Release Notes 15.1. Bug Fixes The following bug has been fixed in Red Hat Update Infrastructure 4.11.1. Failure to handle certificate expiration dates after 2049 Prior to this update, the Content Delivery Server (CDS) used a version of the python3.11-rhsm package that failed to handle entitlement certificates expiring after the year 2049. Consequently, requests using such a certificate failed with an HTTP 403 error, and a traceback was logged on the CDS: "String does not contain a date". This update contains an updated python3.11-rhsm package that improves the way the expiration date is parsed. As a result, such a certificate is handled correctly and the CDS provides the requested content. Users of RHUI are advised to upgrade to this updated package, which fixes this bug. Note Neither the rhui-installer nor the rhui-tools version has changed, and remains 4.11.0.X in both cases. Only the release of the python3.11-rhsm package has changed.

Commands:
3.2. Processing Power Often known as CPU power, CPU cycles, and various other names, processing power is the ability of a computer to manipulate data. Processing power varies with the architecture (and clock speed) of the CPU -- usually CPUs with higher clock speeds and those supporting larger word sizes have more processing power than slower CPUs supporting smaller word sizes. 3.2.1. Facts About Processing Power Here are the two main facts about processing power that you should keep in mind: Processing power is fixed Processing power cannot be stored Processing power is fixed, in that the CPU can only go so fast. For example, if you need to add two numbers together (an operation that takes only one machine instruction on most architectures), a particular CPU can do it at one speed, and one speed only. With few exceptions, it is not even possible to slow the rate at which a CPU processes instructions, much less increase it. Processing power is also fixed in another way: it is finite. That is, there are limits to the types of CPUs that can be plugged into any given computer. Some systems are capable of supporting a wide range of CPUs of differing speeds, while others may not be upgradeable at all [10] . Processing power cannot be stored for later use. In other words, if a CPU can process 100 million instructions in one second, one second of idle time equals 100 million instructions worth of processing that have been wasted. If we take these facts and examine them from a slightly different perspective, a CPU "produces" a stream of executed instructions at a fixed rate. And if the CPU "produces" executed instructions, that means that something else must "consume" them. The section defines these consumers. [10] This situation leads to what is humorously termed as a forklift upgrade , which means a complete replacement of a computer.

Commands:
19.6. User Authorization 19.6.1. User Authorization Model Red Hat Virtualization applies authorization controls based on the combination of the three components: The user performing the action The type of action being performed The object on which the action is being performed 19.6.2. User Actions For an action to be successfully performed, the user must have the appropriate permission for the object being acted upon. Each type of action has a corresponding permission . Some actions are performed on more than one object. For example, copying a template to another storage domain will impact both the template and the destination storage domain. The user performing an action must have appropriate permissions for all objects the action impacts.

Commands:
9.14. LDAP Connector Update Capabilities The LDAP connector also provides an update capability. However, additional modeling requirements are imposed beyond those required for read-only access. Here is a list of these additional requirements: Supports Update table property - to enable updates, each source model table must have this property set to 'true'; Updateable column property - to enable updates, each column in the source model table must have this property set to 'true'; You also need these additional columns: DN - for all update types (INSERT, UPDATE, and DELETE), the distinguished name must be modeled as a column, setting the name in source to dn. For UPDATE and DELETE capability, the DN must be specified in the criteria clause while for INSERT, the DN must be one of the column values to be set. objectClass - for INSERT, the objectclass must be modelled as a column, setting the name in source to objectClass. It must also be one of the column values to be set. additional - each entry defined in the LDAP directory's schema may also have one or more additional required columns. This is dependent on the LDAP server implementatation so consult the LDAP documentation accordingly. Here are some sample queries:

Commands:
SELECT * FROM LdapModel.People
INSERT INTO LdapModel.People (dn, sn, objectclass, Name) VALUES ('cn=JoeYoung,ou=people,dc=example,dc=org','Young','person', 'Joe Young')
UPDATE LdapModel.People SET PhoneNumber='(314) 299-2999' WHERE DN='cn=JoeYoung,ou=people,dc=example,dc=org'
DELETE FROM LdapModel.People WHERE DN='cn=JoeYoung,ou=people,dc=example,dc=org'
13.3.3. Use a Boot Option to Specify a Driver Update Disk Important This method only works to introduce completely new drivers, not to update existing drivers. Type linux dd at the boot prompt at the start of the installation process and press Enter . The installer prompts you to confirm that you have a driver disk: Figure 13.6. The driver disk prompt Insert the driver update disk that you created on CD, DVD, or USB flash drive and select Yes . The installer examines the storage devices that it can detect. If there is only one possible location that could hold a driver disk (for example, the installer detects the presence of a DVD drive, but no other storage devices) it will automatically load any driver updates that it finds at this location. If the installer finds more than one location that could hold a driver update, it prompts you to specify the location of the update. See Section 13.4, "Specifying the Location of a Driver Update Image File or a Driver Update Disk" .

Commands:
21.3.3. Starting and Stopping the Server On the server that is exporting NFS file systems, the nfs service must be running. View the status of the NFS daemon with the following command: Start the NFS daemon with the following command: Stop the NFS daemon with the following command: To start the nfs service at boot time, use the command: You can also use chkconfig , ntsysv or the Services Configuration Tool to configure which services start at boot time. Refer to Chapter 19, Controlling Access to Services for details.

Commands:
/sbin/service nfs status
/sbin/service nfs start
/sbin/service nfs stop
/sbin/chkconfig --level 345 nfs on