mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Analyzing your projects with the MTR extension You can analyze your projects with the MTR extension by creating a run configuration and running an analysis. 3.1. MTR extension interface The interface of the Migration Toolkit for Runtimes (MTR) extension is designed to make it easier for you to find information and perform actions: In the left pane, you can see a directory tree named Analysis Results with a report icon at its top. You can click the icon to open the MTR report in your browser. Beneath the report icon are the other elements of the tree: the applications analyzed by MTR, the rulesets used, and the issues discovered by the analysis. In the upper right pane, you can configure an analysis. In the lower right pane, you can see the settings of the configuration, including source, target, and advanced options. You can view the progress of an analysis in this pane. When the analysis is completed, you can click the Open Report button to open the MTR report, which describes any issues you need to address before you migrate or modernize your application. For more information, see Reviewing the reports in the CLI Guide . Figure 3.1. MTR extension interface 3.2. Configuring a run configuration You can configure multiple run configurations to run against each project you import to VS Code. Prerequisites mta-cli executable installed. You can download the mta-cli executable from mtr download . Procedure In Extensions view, click the Migration Toolkit for Runtimes icon ( ) on the Activity bar. Click the + (plus sign) to Migration Toolkit for Runtimes to add a run configuration. Complete the following configuration fields: Name : Enter a meaningful name for the analysis configuration or accept the default. cli : Enter the path to the cli executable. For example: USDHOME/mta-cli-1.2.7.GA-redhat-00001/bin/mta-cli . Input : Set to the path of the project that you have open within your IDE by clicking Add and doing one of the following: Enter the input file or directory and press Enter. Click Open File Explorer and select the directory. Target : Select one or more target migration paths. Right-click the run configuration and select Run . When the analysis is completed, you can click the Open Report button to open the MTR report, which describes any issues you need to address before you migrate or modernize your application. For more information, see Reviewing the reports in the CLI Guide .

Commands:
Deploying and managing OpenShift Data Foundation using Red Hat OpenStack Platform Red Hat OpenShift Data Foundation 4.17 Instructions on deploying and managing OpenShift Data Foundation on Red Hat OpenStack Platform Red Hat Storage Documentation Team Abstract Read this document for instructions about how to install and manage Red Hat OpenShift Data Foundation using Red Hat OpenShift Container Platform on Red Hat OpenStack Platform (RHOSP). Important Deploying and managing OpenShift Data Foundation on Red Hat OpenStack Platform is a Technology Preview feature. 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.

Commands:
Chapter 1. About Red Hat OpenShift Pipelines Red Hat OpenShift Pipelines is a cloud-native, continuous integration and continuous delivery (CI/CD) solution based on Kubernetes resources. It uses Tekton building blocks to automate deployments across multiple platforms by abstracting away the underlying implementation details. Tekton introduces a number of standard custom resource definitions (CRDs) for defining CI/CD pipelines that are portable across Kubernetes distributions. Note Because Red Hat OpenShift Pipelines releases on a different cadence from OpenShift Dedicated, the Red Hat OpenShift Pipelines documentation is now available as a separate documentation set at Red Hat OpenShift Pipelines .

Commands:
Chapter 11. Using feature gates in a hosted cluster You can use feature gates in a hosted cluster to enable features that are not part of the default set of features. You can enable the TechPreviewNoUpgrade feature set by using feature gates in your hosted cluster. 11.1. Enabling feature sets by using feature gates You can enable the TechPreviewNoUpgrade feature set in a hosted cluster by editing the HostedCluster custom resource (CR) with the OpenShift CLI. Prerequisites You installed the OpenShift CLI ( oc ). Procedure Open the HostedCluster CR for editing on the hosting cluster by running the following command: USD oc edit <hosted_cluster_name> -n <hosted_cluster_namespace> Define the feature set by entering a value in the featureSet field. For example: apiVersion: hypershift.openshift.io/v1beta1 kind: HostedCluster metadata: name: <hosted_cluster_name> 1 namespace: <hosted_cluster_namespace> 2 spec: configuration: featureGate: featureSet: TechPreviewNoUpgrade 3 1 Specifies your hosted cluster name. 2 Specifies your hosted cluster namespace. 3 This feature set is a subset of the current Technology Preview features. Warning Enabling the TechPreviewNoUpgrade feature set on your cluster cannot be undone and prevents minor version updates. This feature set allows you to enable these Technology Preview features on test clusters, where you can fully test them. Do not enable this feature set on production clusters. Save the file to apply the changes. Verification Verify that the TechPreviewNoUpgrade feature gate is enabled in your hosted cluster by running the following command: USD oc get featuregate cluster -o yaml Additional resources FeatureGate [config.openshift.io/v1 ]

Commands:
oc edit <hosted_cluster_name> -n <hosted_cluster_namespace>
apiVersion: hypershift.openshift.io/v1beta1 kind: HostedCluster metadata: name: <hosted_cluster_name> 1 namespace: <hosted_cluster_namespace> 2 spec: configuration: featureGate: featureSet: TechPreviewNoUpgrade 3
oc get featuregate cluster -o yaml
7.191. screen 7.191.1. RHBA-2015:1247 - screen bug fix and enhancement update Updated screen packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The "screen" utility allows users to have multiple logins on a single terminal. Bug Fix BZ# 908221 Previously, starting the "screen" utility in the rxvt-unicode-256color terminal emulator failed with a "USDTERM too long" error. This update fixes the underlying code and "screen" starts on this emulator as expected. Enhancement BZ# 1087517 With this update, the "screen" utility logs both successful and unsuccessful authentication attempts to a text terminal locked by "screen". This provides users with an additional venue of monitoring the operations and security of their system. Users of screen are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
8.2.4. Backup Media We have been very careful to use the term "backup media" throughout the sections. There is a reason for that. Most experienced system administrators usually think about backups in terms of reading and writing tapes, but today there are other options. At one time, tape devices were the only removable media devices that could reasonably be used for backup purposes. However, this has changed. In the following sections we look at the most popular backup media, and review their advantages as well as their disadvantages. 8.2.4.1. Tape Tape was the first widely-used removable data storage medium. It has the benefits of low media cost and reasonably-good storage capacity. However, tape has some disadvantages -- it is subject to wear, and data access on tape is sequential in nature. These factors mean that it is necessary to keep track of tape usage (retiring tapes once they have reached the end of their useful life), and that searching for a specific file on tape can be a lengthy proposition. On the other hand, tape is one of the most inexpensive mass storage media available, and it has a long history of reliability. This means that building a good-sized tape library need not consume a large part of your budget, and you can count on it being usable now and in the future.

Commands:
Chapter 18. Persistently mounting file systems As a system administrator, you can persistently mount file systems to configure non-removable storage. 18.1. The /etc/fstab file Use the /etc/fstab configuration file to control persistent mount points of file systems. Each line in the /etc/fstab file defines a mount point of a file system. It includes six fields separated by white space: The block device identified by a persistent attribute or a path in the /dev directory. The directory where the device will be mounted. The file system on the device. Mount options for the file system, which includes the defaults option to mount the partition at boot time with default options. The mount option field also recognizes the systemd mount unit options in the x-systemd. option format. Backup option for the dump utility. Check order for the fsck utility. Note The systemd-fstab-generator dynamically converts the entries from the /etc/fstab file to the systemd-mount units. The systemd auto mounts LVM volumes from /etc/fstab during manual activation unless the systemd-mount unit is masked. Example 18.1. The /boot file system in /etc/fstab Block device Mount point File system Options Backup Check UUID=ea74bbec-536d-490c-b8d9-5b40bbd7545b /boot xfs defaults 0 0 The systemd service automatically generates mount units from entries in /etc/fstab . Additional resources fstab(5) and systemd.mount(5) man pages on your system 18.2. Adding a file system to /etc/fstab Configure persistent mount point for a file system in the /etc/fstab configuration file. Procedure Find out the UUID attribute of the file system: For example: Example 18.2. Viewing the UUID of a partition If the mount point directory does not exist, create it: As root, edit the /etc/fstab file and add a line for the file system, identified by the UUID. For example: Example 18.3. The /boot mount point in /etc/fstab Regenerate mount units so that your system registers the new configuration: Try mounting the file system to verify that the configuration works: Additional resources Overview of persistent naming attributes

Commands:
lsblk --fs storage-device
lsblk --fs /dev/sda1 NAME FSTYPE LABEL UUID MOUNTPOINT sda1 xfs Boot ea74bbec-536d-490c-b8d9-5b40bbd7545b /boot
mkdir --parents mount-point
UUID=ea74bbec-536d-490c-b8d9-5b40bbd7545b /boot xfs defaults 0 0
systemctl daemon-reload
mount mount-point
4.10. Desktop With newer kernels, such as the kernel shipped in Red Hat Enterprise Linux 6.1, Nouveau has corrected the Transition Minimized Differential Signalling (TMDS) bandwidth limits for pre-G80 nVidia chipsets. Consequently, the resolution auto-detected by X for some monitors may differ from that used in Red Hat Enterprise Linux 6.0. When enabled, fingerprint authentication is the default authentication method to unlock a workstation, even if the fingerprint reader device is not accessible. However, after a 30 second wait, password authentication will become available. Evolution's IMAP backend only refreshes folder contents under the following circumstances: when the user switches into or out of a folder, when the auto-refresh period expires, or when the user manually refreshes a folder (i.e. using the menu item Folder > Refresh ). Consequently, when replying to a message in the Sent folder, the new message does not immediately appear in the Sent folder. To see the message, force a refresh using one of the methods describe above. The clock applet in the GNOME panel has a default location of Boston, USA. Additional locations are added via the applet's preferences dialog. Additionally, to change the default location, left-click the applet, hover over the desired location in the "Locations" section, and click the "Set..." button that appears. In some multi-monitor configurations (e.g. dual monitors with both rotated), the cursor confinement code produces incorrect results. For example, the cursor may be permitted to disappear offscreen when it should not, or be prevented from entering some areas where it should be allowed to go. Currently, the only work around to this issue is to disable monitor rotation. If a Russian keyboard is chosen during system installation, the login screen is configured to use Russian input for user names and passwords by default. However, pressing Left Shift and Right Shift does not cause the input to change to ASCII mode. Consequently, the user cannot log in. To work around this issue, run the following sequence, as root, post installation:

Commands:
. /etc/sysconfig/keyboard; echo USDLAYOUT | grep -q ",us" && gconftool-2 --direct --config-source xml:readwrite:/var/lib/gdm/.gconf --set /apps/gdm/simple-greeter/recent-layouts --type list --list-type string USD(echo USDLAYOUT | awk -F, '{ print "[" USD2 "," USD1 "]"; }') && echo "DONE"
8.4.6.3. OpenSCAP Remediation Review The review mode allows users to store remediation instructions to a file for further review. The remediation content is not executed during this operation. To generate remediation instructions in the form of a shell script, run:

Commands:
~]USD oscap xccdf generate fix --template urn:xccdf:fix:script:sh --profile xccdf_org.ssgproject.content_profile_rht-ccp --output my-remediation-script.sh /usr/share/xml/scap/ssg/content/ssg-rhel6-ds.xml
Getting Started with AMQ Streams on OpenShift Red Hat AMQ Streams 2.1 Get started using AMQ Streams 2.1 on OpenShift Container Platform

Commands:
apiVersion: kafka.strimzi.io/v1beta2 kind: Kafka metadata: name: my-cluster namespace: amq-streams-kafka spec: kafka: # listeners: # - name: listener1 port: 9094 type: route tls: true
get routes my-cluster-kafka-listener1-bootstrap -o=jsonpath='{.status.ingress[0].host}{"\n"}'
extract secret/my-cluster-cluster-ca-cert --keys=ca.crt --to=- > ca.crt
keytool -keystore client.truststore.jks -alias CARoot -import -file ca.crt
run kafka-producer -ti --image=registry.redhat.io/amq7/amq-streams-kafka-31-rhel8:2.1.0 --rm=true --restart=Never -- bin/kafka-console-producer.sh --bootstrap-server my-cluster-kafka-bootstrap:9092 --topic my-topic
run kafka-consumer -ti --image=registry.redhat.io/amq7/amq-streams-kafka-31-rhel8:2.1.0 --rm=true --restart=Never -- bin/kafka-console-consumer.sh --bootstrap-server my-cluster-kafka-bootstrap:9092 --topic my-topic --from-beginning
kafka-console-producer.sh --bootstrap-server my-cluster-kafka-listener1-bootstrap-amq-streams-kafka.apps.ci-ln-50kcyvt-72292.origin-ci-int-gce.dev.rhcloud.com:443 --producer-property security.protocol=SSL --producer-property ssl.truststore.password=password --producer-property ssl.truststore.location=client.truststore.jks --topic my-topic
kafka-console-consumer.sh --bootstrap-server my-cluster-kafka-listener1-bootstrap-amq-streams-kafka.apps.ci-ln-50kcyvt-72292.origin-ci-int-gce.dev.rhcloud.com:443 --consumer-property security.protocol=SSL --consumer-property ssl.truststore.password=password --consumer-property ssl.truststore.location=client.truststore.jks --topic my-topic --from-beginning
5.4.2. I/O Loads and Performance The other thing that controls hard drive performance is the I/O load to which a hard drive is subjected. Some of the specific aspects of the I/O load are: The amount of reads versus writes The number of current readers/writers The locality of reads/writes These are discussed in more detail in the following sections. 5.4.2.1. Reads Versus Writes For the average hard drive using magnetic media for data storage, the number of read I/O operations versus the number of write I/O operations is not of much concern, as reading and writing data take the same amount of time [19] . However, other mass storage technologies take different amounts of time to process reads and writes [20] . The impact of this is that devices that take longer to process write I/O operations (for example) are able to handle fewer write I/Os than read I/Os. Looked at another way, a write I/O consumes more of the device's ability to process I/O requests than does a read I/O. [19] Actually, this is not entirely true. All hard drives include some amount of on-board cache memory that is used to improve read performance. However, any I/O request to read data must eventually be satisfied by physically reading the data from the storage medium. This means that, while cache may alleviate read I/O performance problems, it can never totally eliminate the time required to physically read the data from the storage medium. [20] Some optical disk drives exhibit this behavior, due to the physical constraints of the technologies used to implement optical data storage.

Commands:
21.2. Preparing for Disaster Recovery If at all possible, it is best to prepare for situations where your equipment will be compromised due to weather, or other reasons. It is highly recommended that you perform a backup of the following files and directories on your host physical machine: From the /etc/libvirt directory, all files. From the /var/lib/libvirt directory, back up the following items: The current dnsmasq DHCP leases found in /var/lib/libvirt/dnsmasq The running virtual network configuration files found in /var/lib/libvirt/network Guest virtual machine files created by virt-manager when saving the current state of a guest, if there are any. These can be found in the /var/lib/libvirt/qemu/save/ directory. If the virsh save command was used to create virtual machines, the files can be found in the location specified for virsh save by the user. The guest virtual machine snapshot files, created by the qemu-img create and virsh snapshot-create commands and found in the locations specified for the commands by the user. Guest virtual machine disk images created by virt-manager , if any, which can be found in the /var/lib/libvirt/images/ directory. If the virsh pool-define command was used to create virtual storage, the image file can be found in the location specified for virsh pool-define by the user. For instructions on how to back up the guest image files, use the steps described in Procedure 21.1, "Creating a backup of the guest virtual machine's disk image for disaster recovery purposes" . If you are using bridges, you will also need to back up the files located in /etc/sysconfig/network-scripts/ifcfg-<bridge_name> Optionally, the guest virtual machine core dump files found in /var/lib/libvirt/qemu/dump can also be backed up to be used for analysing the causes of the failure. Note, however, that these files can be very large for some systems. Procedure 21.1. Creating a backup of the guest virtual machine's disk image for disaster recovery purposes This procedure will cover how to back up several different disk image types. To back up only the guest virtual machine disk image, back up the files located in /var/lib/libvirt/images . To back up guest virtual machine disk images with LVM logical volumes, run the following command: This command creates a snapshot volume named snap with a size of 8G as part of a 64G volume. Create a file for the snapshots using a command similar to this one: Mount the directory you created and the snapshot volume using the following command: Use one of the following commands to back up the volume:

Commands:
lvcreate --snapshot --name snap --size 8G /dev/vg0/data
mkdir /mnt/virt.snapshot
mount /dev/vg0/snap /mnt/virt.snapshot
tar -pzc -f /mnt/backup/virt-snapshot-MM-DD-YYYY.tgz /mnt/virt.snapshot++++++++++++
rsync -a /mnt/virt.snapshot/ /mnt/backup/virt-snapshot.MM-DD-YYYY/
5.5.2. Group Stickiness Stickiness, the measure of how much a resource wants to stay where it is, is additive in groups. Every active resource of the group will contribute its stickiness value to the group's total. So if the default resource-stickiness is 100, and a group has seven members, five of which are active, then the group as a whole will prefer its current location with a score of 500.

Commands:
B.13. dapl B.13.1. RHBA-2011:0354 - dapl bug fix and enhancement update Updated dapl packages that fix several bugs and add provider entries to the dat.conf are now available. dapl provides a userspace implementation of the DAT 2.0 API and is built to natively support InfiniBand and iWARP network technology. Bug Fixes BZ# 673989 Under certain error conditions dapl did not allow the cp_ptr entry to be cleaned up correctly in the internal link list. This could cause new connections to fail. With this update, the entry is cleaned up correctly and subsequent connections work as expected. BZ# 673993 Under certain error conditions dapl could fail to free allocated memory. The consequent memory leak could, potentially, result in an out of memory condition for the application. This update frees allocated memory correctly, closing the leak. BZ# 675198 Under certain circumstances, when a thread was waiting on dapls_evd_dto_wait() and the thread received a signal, the function would return an incorrect error code, resulting in the application failing rather than retrying the request. BZ# 675205 On systems with multiple InfiniBand (IB) adapters, especially if some were configured and some not, the dat_ia_open() function could hang when the driver queried the IB devices listed in /etc/dat.conf. This primarily presented as IBM DB2 installations hanging before they completed. With this update, the dat_ia_open() hang has been fixed and IBM DB2 installations, in particular, now succeed as expected. Enhancement BZ# 675202 New provider entries for Mellanox RDMA over Converged Ethernet (RoCE) devices were added to the dat.conf file. Users should upgrade to these updated packages, which fix these issues.

Commands:
2.2. Define a Managed Connection Factory Extend the org.teiid.resource.spi.BasicManagedConnectionFactory class, providing an implementation for the createConnectionFactory() method. This method will create and return an instance of a Connection Factory. Define an attribute for each configuration variable, and then provide both "getter" and "setter" methods for them. This class will define various configuration variables (such as user, password, and URL) used to connect to the datasource. See the following code for an example. public class MyManagedConnectionFactory extends BasicManagedConnectionFactory { @Override public BasicConnectionFactory createConnectionFactory() throws ResourceException { return new MyConnectionFactory(); } // config property name (metadata for these are defined inside the ra.xml) String userName; public String getUserName() { return this.userName; } public void setUserName(String name){ this.userName = name; } // config property count (metadata for these are defined inside the ra.xml) Integer count; public Integer getCount() { return this.count; } public void setCount(Integer value) { this.count = value; } } Important Use only java.lang objects as the attributes. DO NOT use Java primitives for defining and accessing the properties.

Commands:
public class MyManagedConnectionFactory extends BasicManagedConnectionFactory { @Override public BasicConnectionFactory createConnectionFactory() throws ResourceException { return new MyConnectionFactory(); } // config property name (metadata for these are defined inside the ra.xml) String userName; public String getUserName() { return this.userName; } public void setUserName(String name){ this.userName = name; } // config property count (metadata for these are defined inside the ra.xml) Integer count; public Integer getCount() { return this.count; } public void setCount(Integer value) { this.count = value; } }