mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Securing the Fuse Console To secure the Fuse Console on Spring Boot: Disable the Fuse Console's proxy servlet when deploying to AWS If you want to deploy a standalone Fuse application to Amazon Web Services (AWS), you should disable the Fuse Console's proxy servlet by setting the hawtio.disableProxy system property to true . Note When you disable the Fuse Console proxy servlet, the Fuse Console's Connect tab is disabled and you cannot connect to other JVMs from the Fuse Console. If you want to deploy more than one Fuse application on AWS, you must deploy the Fuse Console for each application. Set HTTPS as the required protocol You can use the hawtio.http.strictTransportSecurity property to require web browsers to use the secure HTTPS protocol to access the Fuse Console. This property specifies that web browsers that try to use HTTP to access the Fuse Console must automatically convert the request to use HTTPS. Use public keys to secure responses You can use the hawtio.http.publicKeyPins property to secure the HTTPS protocol by telling the web browser to associate a specific cryptographic public key with the Fuse Console to decrease the risk of "man-in-the-middle" attacks with forged certificates. Procedure Set the hawtio.http.strictTransportSecurity and hawtio.http.publicKeyPins properties as shown in the following example: (For deploying on AWS only) To disable the Fuse Console's proxy servlet, set the hawtio.disableProxy property as shown in the following example: Additional resources For a description of the hawtio.http.strictTransportSecurity property's syntax, see the description page for the HTTP Strict Transport Security (HSTS) response header. For a description of the hawtio.http.publicKeyPins property's syntax, including instructions on how to extract the Base64 encoded public key, see the description page for the HTTP Public Key Pinning response header.

Commands:
public static void main(String[] args) { System.setProperty("hawtio.http.strictTransportSecurity", "max-age=31536000; includeSubDomains; preload"); System.setProperty("hawtio.http.publicKeyPins", "pin-sha256=cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs"; max-age=5184000; includeSubDomains"); SpringApplication.run(YourSpringBootApplication.class, args); }
public static void main(String[] args) { System.setProperty("hawtio.disableProxy", "true"); }
1.2. Red Hat Virtualization REST API Prerequisites Red Hat Virtualization REST API Prerequisites A networked installation of Red Hat Virtualization Manager, which includes the REST API. A client or programming library that initiates and receives HTTP requests from the REST API. For example: Python software development kit (SDK) Java software development kit (SDK) cURL command line tool RESTClient , a debugger for RESTful web services Knowledge of Hypertext Transfer Protocol (HTTP), which is the protocol used for REST API interactions. The Internet Engineering Task Force provides a Request for Comments (RFC) explaining the Hypertext Transfer Protocol at http://www.ietf.org/rfc/rfc2616.txt . Knowledge of Extensible Markup Language (XML) or JavaScript Object Notation (JSON), which the API uses to construct resource representations. The W3C provides a full specification on XML at http://www.w3.org/TR/xml/ . ECMA International provide a free publication on JSON at http://www.ecma-international.org .

Commands:
8.207. s390utils 8.207.1. RHBA-2014:1546 - s390utils bug fix and enhancement update Updated s390utils packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The s390utils packages contain a set of user space utilities that should be used together with the zSeries (s390) Linux kernel and device drivers. Bug Fixes BZ# 1009897 Due to incorrect order of initialization, Anaconda failed to detect the presence of the zSeries Linux fibre-channel adapter (zFCP) disks. To fix this bug, the cio_settle kernel interface has been implemented, which waits for the zFCP devices to become online. Now, Anaconda detects the zFCp devices as intended. BZ# 1016181 For each possible CPU, the zfcpdump kernel consumed all memory for the per-CPU data structures. Because only 32 MB are available for zfcpdump, zfcpdump could run out of memory. This update adds a new kernel parameter "possible_cpus=1", and the zfcpdump system no longer runs out of memory. BZ# 1020364 Previously, when the "fdasd -c" command was called with a configuration file that contained only one parameter for a partition, the fdasd daemon terminated unexpectedly with a segmentation fault during configuration file parsing. This update adds a new function to parse configuration file lines, and fdasd no longer crashes in the described situation. BZ# 1094376 Previously, removing a device that was currently offline resulted in an error. The znetconf protocol has been fixed to handle removal of an offline ccwgroup devices correctly, and the "znetconf -r" command now removes a currently offline device as intended. BZ# 1107779 The output of the lsqeth command depends on the presence of a file named "?". Due to a bug in the grep command regular expression (regex), the system qeth devices failed to be detected when a file named "?" was present in the current working directory. To fix this bug, the regex argument of grep has been put in single quotes, and the system qeth devices are now detected successfully. BZ# 1109898 Due to incomplete dependencies specified in the s390utils packages, various command-line tools did not work when invoked or gathered incomplete data. This update adds the missing dependencies to the tools, which now work as expected. In addition, this update adds the following Enhancements BZ# 1017854 , BZ# 1031143 , BZ# 1032061 , BZ# 1088328 With this update, various information gathered by the dbginfo.sh utility has been expanded, along with the relevant manual page. BZ# 1053832 This update introduces a new interface that enables Linux applications such as Data Stage to access and process read-only data in physical sequential data sets owned by IBM System z without interfering with System z. By avoiding FTP or NFS transfer of data from System z, the turnaround time for batch processing is significantly reduced. Users of s390utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 1. Rust Toolset Rust Toolset is a Red Hat offering for developers on Red Hat Enterprise Linux (RHEL). It provides the rustc compiler for the Rust programming language, the Rust package manager Cargo, the rustfmt formatting tool, and required libraries. For Red Hat Enterprise Linux 8, Rust Toolset is available as a module. Rust Toolset is available as packages for Red Hat Enterprise Linux 9. 1.1. Rust Toolset components The following components are available as part of Rust Toolset: Name Version Description rust 1.75.0 The Rust compiler front-end for LLVM. cargo 1.75.0 A build system and dependency manager for Rust. rustfmt 1.75.0 A tool for automatic formatting of Rust code. 1.2. Rust Toolset compatibility Rust Toolset is available for Red Hat Enterprise Linux 8 and Red Hat Enterprise Linux 9 on the following architectures: AMD and Intel 64-bit 64-bit ARM IBM Power Systems, Little Endian 64-bit IBM Z 1.3. Installing Rust Toolset Complete the following steps to install Rust Toolset including all development and debugging tools as well as dependent packages. Note that Rust Toolset has a dependency on LLVM Toolset. Prerequisites All available Red Hat Enterprise Linux updates are installed. Procedure On Red Hat Enterprise Linux 8, install the rust-toolset module by running: On Red Hat Enterprise Linux 9, install the rust-toolset package by running: 1.4. Installing Rust documentation The The Rust Programming Language book is available as installable documentation. Prerequisites Rust Toolset is installed. For more information, see Installing Rust Toolset . Procedure To install the rust-doc package, run the following command: On Red Hat Enterprise Linux 8: You can find the The Rust Programming Language book under the following path: /usr/share/doc/rust/html/index.html . You can find the API documentation for all Rust code packages under the following path: /usr/share/doc/rust/html/std/index.html . On Red Hat Enterprise Linux 9: You can find the The Rust Programming Language book under the following path: /usr/share/doc/rust/html/index.html . You can find the API documentation for all Rust code packages under the following path: /usr/share/doc/rust/html/std/index.html . 1.5. Installing Cargo documentation The Cargo, Rust's Package Manager book is available as installable documentation for Cargo. Note From Rust Toolset 1.66.1, the cargo-doc package is included in the rust-doc package. Prerequisites Rust Toolset is installed. For more information, see Installing Rust Toolset . Procedure To install the cargo-doc package, run: On Red Hat Enterprise Linux 8: You can find the Cargo, Rust's Package Manager book under the following path: /usr/share/doc/cargo/html/index.html . On Red Hat Enterprise Linux 9: You can find the Cargo, Rust's Package Manager book under the following path: /usr/share/doc/cargo/html/index.html . 1.6. Additional resources For more information on the Rust programming language, see the official Rust documentation .

Commands:
yum module install rust-toolset
dnf install rust-toolset
yum install rust-doc
dnf install rust-doc
yum install cargo-doc
dnf install cargo-doc
Chapter 52. Updated Drivers Storage Driver Updates The QLogic Fibre Channel HBA driver (qla2xxx.ko.xz) has been updated to version 9.00.00.00.07.5-k1. The Cisco FCoE HBA Driver driver (fnic.ko.xz) has been updated to version 1.6.0.34. The Emulex OneConnectOpen-iSCSI driver (be2iscsi.ko.xz) has been updated to version 11.4.0.1. The QLogic FCoE driver (bnx2fc.ko.xz) has been updated to version 2.11.8. The Microsemi Smart Family Controller driver (smartpqi.ko.xz) has been updated to version 1.1.2-126. The Emulex LightPulse Fibre Channel SCSI driver (lpfc.ko.xz) has been updated to version 0:11.4.0.4. The LSI MPT Fusion SAS 3.0 Device driver (mpt3sas.ko.xz) has been updated to version 16.100.00.00. The QLogic QEDF 25/40/50/100Gb FCoE driver (qedf.ko.xz) has been updated to version 8.20.5.0. The Avago MegaRAID SAS driver (megaraid_sas.ko.xz) has been updated to version 07.702.06.00-rh2. The HP Smart Array Controller driver (hpsa.ko.xz) has been updated to version 3.4.20-0-RH2. Network Driver Updates The Realtek RTL8152/RTL8153 Based USB Ethernet Adapters driver (r8152.ko.xz) has been updated to version v1.08.9. The Intel(R) 10 Gigabit PCI Express Network driver (ixgbe.ko.xz) has been updated to version 5.1.0-k-rh7.5. The Intel(R) Ethernet Switch Host Interface driver (fm10k.ko.xz) has been updated to version 0.21.7-k. The Intel(R) Ethernet Connection XL710 Network driver (i40e.ko.xz) has been updated to version 2.1.14-k. The Intel(R) 10 Gigabit Virtual Function Network driver (ixgbevf.ko.xz) has been updated to version 4.1.0-k-rh7.5. The Intel(R) XL710 X710 Virtual Function Network driver (i40evf.ko.xz) has been updated to version 3.0.1-k. The Elastic Network Adapter (ENA) driver (ena.ko.xz) has been updated to version 1.2.0k. The Cisco VIC Ethernet NIC driver (enic.ko.xz) has been updated to version 2.3.0.42. The Broadcom BCM573xx network driver (bnxt_en.ko.xz) has been updated to version 1.8.0. The QLogic FastLinQ 4xxxx Core Module driver (qed.ko.xz) has been updated to version 8.10.11.21. The QLogic 1/10 GbE Converged/Intelligent Ethernet driver (qlcnic.ko.xz) has been updated to version 5.3.66. The Mellanox ConnectX HCA Ethernet driver (mlx4_en.ko.xz) has been updated to version 4.0-0. The Mellanox ConnectX HCA low-level driver (mlx4_core.ko.xz) has been updated to version 4.0-0. The Mellanox Connect-IB, ConnectX-4 core driver (mlx5_core.ko.xz) has been updated to version 5.0-0. Graphics Driver and Miscellaneous Driver Updates The standalone VMware SVGA device drm driver (vmwgfx.ko.xz) has been updated to version 2.14.0.0.

Commands:
Chapter 1. Introduction to VDO on LVM The Virtual Data Optimizer (VDO) feature provides inline block-level deduplication, compression, and thin provisioning for storage. You can manage VDO as a type of Logical Volume Manager (LVM) Logical Volumes (LVs), similar to LVM thin-provisioned volumes. VDO volumes on LVM (LVM-VDO) contain the following components: VDO pool LV This is the backing physical device that stores, deduplicates, and compresses data for the VDO LV. The VDO pool LV sets the physical size of the VDO volume, which is the amount of data that VDO can store on the disk. Currently, each VDO pool LV can hold only one VDO LV. As a result, VDO deduplicates and compresses each VDO LV separately. Duplicate data that is stored on separate LVs do not benefit from data optimization of the same VDO volume. VDO LV This is the virtual, provisioned device on top of the VDO pool LV. The VDO LV sets the provisioned, logical size of the VDO volume, which is the amount of data that applications can write to the volume before deduplication and compression occurs. If you are already familiar with the structure of an LVM thin-provisioned implementation, see the following table to understand how the different aspects of VDO are presented to the system. Table 1.1. A comparison of components in VDO on LVM and LVM thin provisioning Physical device Provisioned device VDO on LVM VDO pool LV VDO LV LVM thin provisioning Thin pool Thin volume Since the VDO is thin-provisioned, the file system and applications only see the logical space in use and not the actual available physical space. Use scripting to monitor the available physical space and generate an alert if use exceeds a threshold. For information about monitoring the available VDO space see the Monitoring VDO section. Additional resources Deduplicating and compressing storage Creating a thin logical volume

Commands:
Chapter 1. Customizing sample software templates Learn how to customize ready-to-use software templates for your on-prem environment. Cluster administrators have full control over this process, including modifying metadata and specifications. Prerequisites You have used the forked repository URL from tssc-sample-templates during the RHTAP install process. Procedure Clone your forked repository, and then open it in your preferred text editor, such as Visual Studio Code. Locate the properties file within your project directory. This file stores the default values that can customize. Open it for editing and update the following key-value pairs according to your environment. Key Description export GITHUB_DEFAULT_HOST Set this to your on-prem GitHub host fully qualified domain name. That is, the URL without the HTTP protocol and without the .git extension. For example github-github.apps.cluster-ljg9z.sandbox219.opentlc.com. Default is github.com . export GITLAB_DEFAULT_HOST Set this to your on-prem GitLab host host fully qualified domain name. That is, the URL without the HTTP protocol and without the .git extension. For example gitlab-gitlab.apps.cluster-ljg9z.sandbox219.opentlc.com. Default is gitlab.com . export QUAY_DEFAULT_HOST The default Quay URL correspond to your specific on-prem image registry URL without the HTTP protocol. For example, quay-tv2pb.apps.cluster-tv2pb.sandbox1194.opentlc.com. The default quay host is quay.io . export DEFAULT_DEPLOYMENT_NAMESPACE_PREFIX The namespace prefix for deployments within RHTAP. Default is rhtap-app . Note Update this if you have modified the default trusted-application-pipeline: namespace during the RHTAP installation process. Figure 1.1. The properties file Run the generate.sh script in your terminal. This action adjusts the software templates, replacing default host values with your specified inputs. ./generate.sh Figure 1.2. The generate.sh script Commit and push the changes to your repository. This automatically updates the template in RHDH. Alternatively, you can import and refresh a single or all customized templates directly in RHDH. Go to your forked sample template repository on your Git provider. For a single template, from the templates directory, select select template.yaml . Copy its URL from the browser address bar. For example, https://github.com/<username>/tssc-sample-templates/blob/main/templates/devfile-sample-code-with-quarkus-dance/template.yaml . Otherwise, for all the templates, select all.yaml and copy its URL from the browser address bar. For example, https://github.com/<username>/tssc-sample-templates/blob/main/all.yaml . Switch back to RHDH platform. Select Create > Register Existing Component . In the Select URL field, paste the appropriate URL that you copied in Step 4b. Select Analyze and then select Import to update the templates in RHDH. Verification Consider creating an application to explore the impact of your template customization. Additional resources To customize pipelines, see Customizing sample pipeline templates

Commands:
./generate.sh
Chapter 1. Introducing V2V Warning The Red Hat Enterprise Linux 6 version of the virt-v2v utility has been deprecated. Users of Red Hat Enterprise Linux 6 are advised to create a Red Hat Enterprise 7 virtual machine, and install virt-v2v in that virtual machine. The Red Hat Enterprise Linux 7 version is fully supported and documented in virt-v2v Knowledgebase articles . V2V is an acronym for virtual to virtual, referring to the process of importing virtual machines from one virtualization platform to another. Red Hat Enterprise Virtualization and Red Hat Enterprise Linux are capable of performing V2V operations using the virt-v2v command. 1.1. What is virt-v2v? The virt-v2v command converts virtual machines from a foreign hypervisor to run on KVM, managed by Red Hat Enterprise Virtualization or libvirt. virt-v2v can currently convert virtual machines running Red Hat Enterprise Linux and Windows on Xen, KVM and VMware ESX / ESX(i) hypervisors. virt-v2v enables paravirtualized ( virtio ) drivers in the converted virtual machine if possible. The following guest operating systems are supported by virt-v2v : Supported guest operating systems: Red Hat Enterprise Linux 3.9 Red Hat Enterprise Linux 4 Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 All minor releases of the above guest operating systems are supported by virt-v2v . The following source hypervisors are supported by virt-v2v : Supported source hypervisors: Unless otherwise specified, all minor releases of the following source hypervisors are supported by virt-v2v : Xen - all versions released by Red Hat KVM - all versions released by Red Hat VMware ESX / ESX(i) - versions 3.5, 4.0, 4.1, 5.0, 5.1

Commands:
3.13. Attaching an ISO Image to a Virtual Machine This Ruby example attaches a CD-ROM to a virtual machine and changes it to an ISO image in order to install the guest operating system. # Get the reference to the "vms" service: vms_service = connection.system_service.vms_service # Find the virtual machine: vm = vms_service.list(search: 'name=myvm')[0] # Locate the service that manages the virtual machine: vm_service = vms_service.vm_service(vm.id) # Locate the service that manages the CDROM devices of the VM: cdroms_service = vm_service.cdroms_service # List the first CDROM device: cdrom = cdroms_service.list[0] # Locate the service that manages the CDROM device you just found: cdrom_service = cdroms_service.cdrom_service(cdrom.id) # Change the CD of the VM to 'my_iso_file.iso'. By default this # operation permanently changes the disk that is visible to the # virtual machine after the boot, but it does not have any effect # on the currently running virtual machine. If you want to change the # disk that is visible to the current running virtual machine, change # the `current` parameter's value to `true`. cdrom_service.update( OvirtSDK4::Cdrom.new( file: { id: 'CentOS-7-x86_64-DVD-1511.iso' } ), current: false ) For more information, see http://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4%2FVmService:cdroms_service .

Commands:
Get the reference to the "vms" service: vms_service = connection.system_service.vms_service Find the virtual machine: vm = vms_service.list(search: 'name=myvm')[0] Locate the service that manages the virtual machine: vm_service = vms_service.vm_service(vm.id) Locate the service that manages the CDROM devices of the VM: cdroms_service = vm_service.cdroms_service List the first CDROM device: cdrom = cdroms_service.list[0] Locate the service that manages the CDROM device you just found: cdrom_service = cdroms_service.cdrom_service(cdrom.id) Change the CD of the VM to 'my_iso_file.iso'. By default this operation permanently changes the disk that is visible to the virtual machine after the next boot, but it does not have any effect on the currently running virtual machine. If you want to change the disk that is visible to the current running virtual machine, change the `current` parameter's value to `true`. cdrom_service.update( OvirtSDK4::Cdrom.new( file: { id: 'CentOS-7-x86_64-DVD-1511.iso' } ), current: false )
5.4.11. Renaming Logical Volumes To rename an existing logical volume, use the lvrename command. Either of the following commands renames logical volume lvold in volume group vg02 to lvnew . Renaming the root logical volume requires additional reconfiguration. For information on renaming a root volume, see How to rename root volume group or logical volume in Red Hat Enterprise Linux . For more information on activating logical volumes on individual nodes in a cluster, see Section 5.7, "Activating Logical Volumes on Individual Nodes in a Cluster" .

Commands:
lvrename /dev/vg02/lvold /dev/vg02/lvnew
lvrename vg02 lvold lvnew
Chapter 9. Set Up Invalidation Mode 9.1. About Invalidation Mode Invalidation is a clustered mode that does not share any data, but instead removes potentially obsolete data from remote caches. Using this cache mode requires another, more permanent store for the data such as a database. Red Hat JBoss Data Grid, in such a situation, is used as an optimization for a system that performs many read operations and prevents database usage each time a state is needed. When invalidation mode is in use, data changes in a cache prompts other caches in the cluster to evict their outdated data from memory. 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands: