mtpti5iD/redhat-docs_dataset huggingface dataset:
2.7. Kernel Thin-provisioning and scalable snapshot capabilities The dm-thinp targets, thin and thin-pool , provide a device mapper device with thin-provisioning and scalable snapshot capabilities. This feature is available as a Technology Preview. Package: kernel-2.6.32-279 kdump/kexec kernel dumping mechanism for IBM System z In Red Hat Enterprise Linux 6.3, the kdump/kexec kernel dumping mechanism is enabled for IBM System z systems as a Technology Preview, in addition to the IBM System z stand-alone and hypervisor dumping mechanism. The auto-reserve threshold is set at 4 GB; therefore, any IBM System z system with more than 4 GB of memory has the kexec/kdump mechanism enabled. Sufficient memory must be available because kdump reserves approximately 128 MB as default. This is especially important when performing an upgrade to Red Hat Enterprise Linux 6.3. Sufficient disk space must also be available for storing the dump in case of a system crash. Kdump is limited to DASD or QETH networks as dump devices until kdump on SCSI disk is supported. The following warning message may appear when kdump is initialized: This message does not impact the dump functionality and can be ignored. You can configure or disable kdump via /etc/kdump.conf , system-config-kdump , or firstboot . Kernel Media support The following features are presented as Technology Previews: The latest upstream video4linux Digital video broadcasting Primarily infrared remote control device support Various webcam support fixes and improvements Package: kernel-2.6.32-279 Remote audit logging The audit package contains the user space utilities for storing and searching the audit records generated by the audit subsystem in the Linux 2.6 kernel. Within the audispd-plugins sub-package is a utility that allows for the transmission of audit events to a remote aggregating machine. This remote audit logging application, audisp-remote , is considered a Technology Preview in Red Hat Enterprise Linux 6. Package: audispd-plugins-2.2-2 Linux (NameSpace) Container [LXC] Linux containers provide a flexible approach to application runtime containment on bare-metal systems without the need to fully virtualize the workload. Red Hat Enterprise Linux 6 provides application level containers to separate and control the application resource usage policies via cgroups and namespaces. This release includes basic management of container life-cycle by allowing creation, editing and deletion of containers via the libvirt API and the virt-manager GUI. Linux Containers are a Technology Preview. Packages: libvirt-0.9.10-21 , virt-manager-0.9.0-14 Diagnostic pulse for the fence_ipmilan agent, BZ# 655764 A diagnostic pulse can now be issued on the IPMI interface using the fence_ipmilan agent. This new Technology Preview is used to force a kernel dump of a host if the host is configured to do so. Note that this feature is not a substitute for the off operation in a production cluster. Package: fence-agents-3.1.5-17

Commands:
..no such file or directory
Appendix C. Understanding the gluster_network_inventory.yml file C.1. Configuration parameters for creation of gluster network vars he_fqdn FQDN of the hosted engine VM he_admin_password Password for RHV Manager Administration Portal. datacenter_name RHV datacenter name. Usually Red Hat Hyperconverged Infrastructure for Virtualization deployment adds all 3 hosts to Default cluster in Default datacenter. cluster_name RHV cluster name. boot_protocol Whether to use DHCP or static networking. . version (optional) Whether to use IPv4 or IPv6 networking. v4 is the default, and is assumed if this parameter is omitted. The other valid value is v6. Mixed networks are not supported. mtu_value (optional) Specifies the Maximum Transmission Unit for the network, the largest packet or frame size that can be sent in a single transaction. The default value is 1500 . Increasing this to 9000 on networks that support Jumbo frames greatly improves throughput. cluster_nodes host Host's public network FQDN, which is mentioned in Red Hat Virtualization Administration Portal. interface Network interface or the bond, corresponding to storage or backend network. C.2. Example gluster_network_inventory.yml

Commands:
all: hosts: localhost: vars: he_fqdn: rhv-manager.example.com he_admin_password: xxxxxxxxxx datacenter_name: Default cluster_name: Default boot_protocol: dhcp version: v4 mtu_value: 9000 # For dhcp boot_protocol cluster_nodes: - {host: host1-frontend.example.com , interface: eth1 } - {host: host2-frontend.example.com , interface: eth1 } - {host: host3-frontend.example.com , interface: eth1 }
1.2.3.3. Converged Networks Communication over the network is normally done through Ethernet, with storage traffic using a dedicated Fibre Channel SAN environment. It is common to have a dedicated network or serial link for system management, and perhaps even heartbeat [2] . As a result, a single server is typically on multiple networks. Providing multiple connections on each server is expensive, bulky, and complex to manage. This gave rise to the need for a way to consolidate all connections into one. Fibre Channel over Ethernet (FCoE) and Internet SCSI (iSCSI) address this need. FCoE With FCoE, standard fibre channel commands and data packets are transported over a 10GbE physical infrastructure via a single converged network adapter (CNA). Standard TCP/IP ethernet traffic and fibre channel storage operations can be transported via the same link. FCoE uses one physical network interface card (and one cable) for multiple logical network/storage connections. FCoE offers the following advantages: Reduced number of connections FCoE reduces the number of network connections to a server by half. You can still choose to have multiple connections for performance or availability; however, a single connection provides both storage and network connectivity. This is especially helpful for pizza box servers and blade servers, since they both have very limited space for components. Lower cost Reduced number of connections immediately means reduced number of cables, switches, and other networking equipment. Ethernet's history also features great economies of scale; the cost of networks drops dramatically as the number of devices in the market goes from millions to billions, as was seen in the decline in the price of 100Mb Ethernet and gigabit Ethernet devices. Similarly, 10GbE will also become cheaper as more businesses adapt to its use. Also, as CNA hardware is integrated into a single chip, widespread use will also increase its volume in the market, which will result in a significant price drop over time. iSCSI Internet SCSI (iSCSI) is another type of converged network protocol; it is an alternative to FCoE. Like fibre channel, iSCSI provides block-level storage over a network. However, iSCSI does not provide a complete management environment. The main advantage of iSCSI over FCoE is that iSCSI provides much of the capability and flexibility of fibre channel, but at a lower cost. [2] Heartbeat is the exchange of messages between systems to ensure that each system is still functioning. If a system "loses heartbeat" it is assumed to have failed and is shut down, with another system taking over for it.

Commands:
7.3. Creating a Red Hat Enterprise Linux 6 Guest with PXE Procedure 7.3. Creating a Red Hat Enterprise Linux 6 guest with virt-manager Optional: Preparation Prepare the storage environment for the virtual machine. For more information on preparing storage, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide . Important Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage. Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide. Open virt-manager and start the wizard Open virt-manager by executing the virt-manager command as root or opening Applications System Tools Virtual Machine Manager . Figure 7.15. The main virt-manager window Click on the Create new virtualized guest button to start the new virtualized guest wizard. Figure 7.16. The create new virtualized guest button The New VM window opens. Name the virtual machine Virtual machine names can contain letters, numbers and the following characters: ' _ ', ' . ' and ' - '. Virtual machine names must be unique for migration and cannot consist only of numbers. Choose the installation method from the list of radio buttons. Figure 7.17. The New VM window - Step 1 Click Forward to continue. The remaining steps are the same as the ISO installation procedure. Continue from Step 5 of the ISO installation procedure. From this point, the only difference in this PXE procedure is on the final New VM screen, which shows the Install: PXE Install field. Figure 7.18. The New VM window - Step 5 - PXE Install

Commands:
4.2. Set the VDB Version You can set the version in one of two ways: through the vdb.xml file, (which is useful for dynamic VDBs), or by specifying a naming convention in the deployment file (such as VDBNAME.VERSION .vdb ). The deployer is responsible for choosing an appropriate version number. If there is already a VDB name and version combination that matches the current deployment, then connections to the VDB will be terminated and its cache entries will be flushed. Any new connections will then be made to the new VDB.

Commands:
14.3. Comparing Images Compare the contents of two specified image files ( imgname1 and imgname2 ) with the qemu-img compare command. Optionally, specify the files' format types ( fmt ). The images can have different formats and settings. By default, images with different sizes are considered identical if the larger image contains only unallocated or zeroed sectors in the area after the end of the other image. In addition, if any sector is not allocated in one image and contains only zero bytes in the other one, it is evaluated as equal. If you specify the -s option, the images are not considered identical if the image sizes differ or a sector is allocated in one image and is not allocated in the second one. The qemu-img compare command exits with one of the following exit codes: 0 - The images are identical 1 - The images are different 2 - There was an error opening one of the images 3 - There was an error checking a sector allocation 4 - There was an error reading the data

Commands:
qemu-img compare [-f fmt ] [-F fmt ] [-p] [-s] [-q] imgname1 imgname2
4.289. sed 4.289.1. RHBA-2011:1116 - sed bug fix update An updated sed package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The sed package provides is a stream or batch (non-interactive) editor that takes text as input, performs an operation or a set of operations on the text, and outputs the modified text. Bug Fixes BZ# 721349 Prior to this update, the is_selinux_disabled() function was not correctly checked. With this update, this check returns the correct value and now the check works as expected. BZ# 679921 Prior to this update, the behavior of the i/--in-place option for symlinks and hardlinks was not clearly documented. With this update, the manpage and the user documentation has been improved and this problem is resolved. All sed users are advised to upgrade to this updated package, which fixes these bugs.

Commands:
2.8.5.3. DMZs and IPTables You can create iptables rules to route traffic to certain machines, such as a dedicated HTTP or FTP server, in a demilitarized zone ( DMZ ). A DMZ is a special local subnetwork dedicated to providing services on a public carrier, such as the Internet. For example, to set a rule for routing incoming HTTP requests to a dedicated HTTP server at 10.0.4.2 (outside of the 192.168.1.0/24 range of the LAN), NAT uses the PREROUTING table to forward the packets to the appropriate destination: With this command, all HTTP connections to port 80 from outside of the LAN are routed to the HTTP server on a network separate from the rest of the internal network. This form of network segmentation can prove safer than allowing HTTP connections to a machine on the network. If the HTTP server is configured to accept secure connections, then port 443 must be forwarded as well.

Commands:
~]# iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 10.0.4.2:80
Chapter 12. Tagging virtual devices In Red Hat OpenStack Platform (RHOSP), if you attach multiple network interfaces or block devices to an instance, you can use device tagging to communicate the intended role of each device to the instance operating system. Tags are assigned to devices at instance boot time, and are available to the instance operating system through the metadata API and the configuration drive, if enabled. You can also tag virtual devices to a running instance. For more information, see the following procedures: Attaching a network to an instance Attaching a volume to an instance Note To execute openstack client commands on the cloud, you must specify the name of the cloud detailed in your clouds.yaml file. You can specify the name of the cloud by using one of the following methods: Use the --os-cloud option with each command, for example: Use this option if you access more than one cloud. Create an environment variable for the cloud name in your bashrc file: Prerequisites The administrator has created a project for you and they have provided you with a clouds.yaml file for you to access the cloud. You have installed the python-openstackclient package. Procedure Create your instance with a virtual block device tag and a virtual network device tag: Replace <myNicTag> with the name of the tag for the virtual NIC device. You can add as many tagged virtual devices as you require. Replace <myVolumeTag> with the name of the tag for the virtual storage device. You can add as many tagged virtual devices as you require. Verify that the virtual device tags have been added to the instance metadata by using one of the following methods: Retrieve the device tag metadata from the metadata API by using GET /openstack/latest/meta_data.json . If the configuration drive is enabled and mounted under /configdrive on the instance operating system, view the /configdrive/openstack/latest/meta_data.json file. Example meta_data.json file:

Commands:
openstack flavor list --os-cloud <cloud_name>
`export OS_CLOUD=<cloud_name>`
openstack server create --flavor m1.tiny --image cirros --network <network_UUID> --nic net-id=<network_UUID>,tag=<myNicTag> --block-device id=<volume_ID>,bus=virtio,tag=<myVolumeTag> myTaggedDevicesInstance
{ "devices": [ { "type": "nic", "bus": "pci", "address": "0030:00:02.0", "mac": "aa:00:00:00:01", "tags": ["myNicTag"] }, { "type": "disk", "bus": "pci", "address": "0030:00:07.0", "serial": "disk-vol-227", "tags": ["myVolumeTag"] } ] }
5.140. latencytop 5.140.1. RHBA-2012:0864 - latencytop bug fix and enhancement update Updated latencytop packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. LatencyTOP is a tool to monitor system latencies. Bug Fix BZ# 633698 When running LatencyTOP as a normal user, LatencyTOP attempted and failed to mount the debug file system. A misleading error message was displayed, suggesting that kernel-debug be installed even though this was already the running kernel. LatencyTOP has been improved to exit and display "Permission denied" when run as a normal user. In addition, fsync view has been removed from the "latencytop" package because it depended on a non-standard kernel tracer that was never present in Red Hat Enterprise Linux kernels or upstream kernels. As a result, LatencyTOP no longer attempts to mount the debugfs file system. Enhancement BZ# 726476 The "latencytop" package requires GTK libraries. Having GTK libraries installed on servers may be undesirable. A build of LatencyTOP without dependencies on GTK libraries is now available under the package name "latencytop-tui". Users are advised to upgrade to these updated latencytop packages, which fix this bug and add this enhancement.

Commands:
7.102. libcgroup 7.102.1. RHBA-2015:1263 - libcgroup bug fix update Updated libcgroup packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The libcgroup packages provide tools and libraries to control and monitor control groups. Bug Fixes BZ# 1036355 Previously, the cgconfigparser utility wrote the whole multi-line value in a single write() function call, while the 'devices' kernel subsystem expected only one line per write(). Consequently, cgconfigparser did not properly set the multi-line variables. The underlying source code has been fixed, and cgconfigparser now parses all variables as intended. BZ# 1139205 Prior to this update, if '/etc/cgfconfig.conf' or a configuration file in the '/etc/cgconfig.d/' directory contained the cgroup name 'default' that was not enclosed in double quotation marks, backwards compatibility was broken and cgconfigparser failed to parse the file. With this update, 'default' without double quotation marks is again considered a valid cgroup name, and configuration files are now parsed correctly. Users of libcgroup are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 23. Security A runtime version of OpenSSL is masked and SSL_OP_NO_TLSv1_1 must not be used when an application runs with OpenSSL 1.0.0 Because certain applications perform incorrect version check of the OpenSSL version, the actual runtime version of OpenSSL is masked and the build-time version is reported instead. Consequently, it is impossible to detect the currently running OpenSSL version using the SSLeay() function. Additionally, passing the value equivalent to the SSL_OP_NO_TLSv1_1 option as present on OpenSSL 1.0.1 to the SSL_CTX_set_options() function when running with OpenSSL 1.0.0 breaks the SSL/TLS support completely. To work around this problem, use another way to detect the currently running OpenSSL version. For example, it is possible to obtain a list of enabled ciphers with the SSL_get_ciphers() function and search a TLS 1.2 cipher by parsing the list using the SSL_CIPHER_description() function. This indicates an application that runs with the OpenSSL version later than 1.0.0 because TLS 1.2 support is present since version 1.0.1. (BZ# 1497859 )

Commands:
9.10. The Security Audit Logger Red Hat JBoss Data Grid includes a logger to audit security logs for the cache, specifically whether a cache or a cache manager operation was allowed or denied for various operations. The default audit logger is org.infinispan.security.impl.DefaultAuditLogger . This logger outputs audit logs using the available logging framework (for example, JBoss Logging) and provides results at the TRACE level and the AUDIT category. To send the AUDIT category to either a log file, a JMS queue, or a database, use the appropriate log appender. Report a bug 9.10.1. Configure the Security Audit Logger (Library Mode) Use the following to declaratively configure the audit logger in Red Hat JBoss Data Grid: Use the following to programatically configure the audit logger in JBoss Data Grid: Report a bug 9.10.2. Configure the Security Audit Logger (Remote Client-Server Mode) Use the following code to configure the audit logger in Red Hat JBoss Data Grid Remote Client-Server Mode. To use a different audit logger, specify it in the <authorization> element. The <authorization> element must be within the <cache-container> element in the Infinispan subsystem (in the standalone.xml configuration file). Note The default audit logger for server mode is org.jboss.as.clustering.infinispan.subsystem.ServerAuditLogger which sends the log messages to the server audit log. See the Management Interface Audit Logging chapter in the JBoss Enterprise Application Platform Administration and Configuration Guide for more information. Report a bug 9.10.3. Custom Audit Loggers Users can implement custom audit loggers in Red Hat JBoss Data Grid Library and Remote Client-Server Mode. The custom logger must implement the org.infinispan.security.AuditLogger interface. If no custom logger is provided, the default logger ( DefaultAuditLogger ) is used. Report a bug

Commands:
<infinispan> <global-security> <authorization audit-logger = "org.infinispan.security.impl.DefaultAuditLogger"> </authorization> </global-security> </infinispan>
GlobalConfigurationBuilder global = new GlobalConfigurationBuilder(); global.security() .authorization() .auditLogger(new DefaultAuditLogger());
<cache-container name="local" default-cache="default"> <security> <authorization audit-logger="org.infinispan.security.impl.DefaultAuditLogger"> <identity-role-mapper/> <role name="admin" permissions="ALL"/> <role name="reader" permissions="READ"/> <role name="writer" permissions="WRITE"/> <role name="supervisor" permissions="ALL_READ ALL_WRITE"/> </authorization> </security> <local-cache name="default" start="EAGER"> <locking isolation="NONE" acquire-timeout="30000" concurrency-level="1000" striping="false"/> <transaction mode="NONE"/> <security> <authorization roles="admin reader writer supervisor"/> </security> </local-cache>
Chapter 4. Exploring a service network Skupper includes a command to allow you report all the sites and the services available on a service network. Prerequisites A service network with more than one site Procedure Set your Kubernetes context to a namespace on the service network. Use the following command to report the status of the service network: USD skupper network status For example: 1 The unique identifier of the site associated with the current context, that is, the west namespace 2 The site name. By default, skupper uses the name of the current namespace. If you want to specify a site name, use skupper init --site-name <site-name> . 3 The version of Skupper running the site. The site version can be different from the current skupper CLI version. To update a site to the version of the CLI, use skupper update . 4 The unique identifier of a remote site on the service network. 5 The sites that the remote site is linked to. 6 The unique identifier of a remote podman site. Podman sites do not have an associated context.

Commands:
skupper network status
Sites: ├─ [local] a960b766-20bd-42c8-886d-741f3a9f6aa2(west) 1 │ │ namespace: west │ │ site name: west 2 │ │ version: 1.8.1 3 │ ╰─ Linked sites: │ ├─ 496ca1de-0c80-4e70-bbb4-d0d6ec2a09c0(east) │ │ direction: outgoing │ ╰─ 484cccc3-401c-4c30-a6ed-73382701b18a() │ direction: incoming ├─ [remote] 496ca1de-0c80-4e70-bbb4-d0d6ec2a09c0(east) 4 │ │ namespace: east │ │ site name: east │ │ version: 1.8.1 │ ╰─ Linked sites: │ ╰─ a960b766-20bd-42c8-886d-741f3a9f6aa2(west) 5 │ direction: incoming ╰─ [remote] 484cccc3-401c-4c30-a6ed-73382701b18a() 6 │ site name: vm-user-c3d98 │ version: 1.8.1 ╰─ Linked sites: ╰─ a960b766-20bd-42c8-886d-741f3a9f6aa2(west) direction: outgoing