mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. What changed in this release? 1.1. Major changes in version 1.8 Be aware of the following differences between Red Hat Hyperconverged Infrastructure for Virtualization 1.8 and versions: Changed behavior Red Hat Hyperconverged Infrastructure for Virtualization 1.8 and Red Hat Virtualization 4.4 are based on Red Hat Enterprise Linux 8. Read about the key differences in Red Hat Enterprise Linux 8 in Considerations in adopting RHEL 8 . Cluster upgrades now require at least 10 percent free space on gluster disks in order to reduce the risk of running out of space mid-upgrade. This is available post the upgrade to Red Hat Hyperconverged Infrastructure for Virtualization 1.8. ( BZ#1783750 ) "Hosts" and "Additional Hosts" tabs in the Web Console have been combined into a new "Hosts" tab that shows information previously shown on both. ( BZ#1762804 ) Readcache and readcachesize options have been removed from VDO volumes, as they are not supported on Red Hat Enterprise Linux 8 based operating systems. ( BZ#1808081 ) The Quartz scheduler is replaced with the standard Java scheduler to match support with Red Hat Virtualization. ( BZ#1797487 ) Enhancements The Administrator Portal can now upgrade all hosts in a cluster with one click. This is available post the upgrade to Red Hat Hyperconverged Infrastructure for Virtualization 1.8. ( BZ#1721366 ) At-rest encryption using Network-Bound Disk Encryption (NBDE) is now supported on new Red Hat Hyperconverged Infrastructure for Virtualization deployments. ( BZ#1821248 , BZ#1781184 ) Added support for IPv6 networking. Environments with both IPv4 and IPv6 addresses are not supported. ( BZ#1721383 ) New roles, playbooks, and inventory examples are available to simplify and automate the following tasks: Upgrading ( BZ#1500728 , BZ#1832654 ) Backing up and restoring configuration ( BZ#1850488 ) Replacing hosts ( BZ#1840123 ) Blacklisting multipath devices ( BZ#1807808 ) Creating the gluster logical network ( BZ#1832966 ) Deploying on IPv6 networks. ( BZ#1688217 ) Added an option to select IPv4 or IPv6 based deployment in the web console. ( BZ#1688798 ) fsync in the replication module now uses eager-lock functionality which improves the performance of small-block of size approximately equal to 4k write-heavy workloads by more than 50 percent on Red Hat Hyperconverged Infrastructure for Virtualization 1.8. ( BZ#1836164 ) The web console now supports blacklisting multipath devices. ( BZ#1814120 ) New fencing policies skip_fencing_if_gluster_bricks_up and skip_fencing_if_gluster_quorum_not_met are now added and enabled by default. ( BZ#1775552 ) Red Hat Hyperconverged Infrastructure for Virtualization now ensures that the "performance.strict-o-direct" option in Red Hat Gluster Storage is enabled before creating a storage domain. ( BZ#1807400 ) Red Hat Gluster Storage volume options can now be set for all volumes in the Administrator Portal by using "all" as the volume name. ( BZ#1775586 ) Read-only fields are no longer included in the web console user interface, making the interface simpler and easier to read. ( BZ#1814553 )

Commands:
Chapter 4. Upgrading Red Hat Single Sign-On adapters It is important that you upgrade Red Hat Single Sign-On server first, and then upgrade the adapters. Earlier versions of the adapter might work with later versions of Red Hat Single Sign-On server, but earlier versions of Red Hat Single Sign-On server might not work with later versions of the adapter. 4.1. Compatibility with older adapters As mentioned above, we try to support newer release versions of Red Hat Single Sign-On server working with older release versions of the adapters. However, in some cases we need to include fixes on the Red Hat Single Sign-On server side which may break compatibility with older versions of the adapters. For example, when we implement new aspects of the OpenID Connect specification, which older client adapter versions were not aware of. In those cases, we added Compatibility modes. For OpenId Connect clients, there is a section named OpenID Connect Compatibility Modes in the Red Hat Single Sign-On admin console, on the page with client details. Here, you can disable some new aspects of the Red Hat Single Sign-On server to preserve compatibility with older client adapters. More details are available in the tool tips of individual switches. 4.2. Upgrading the EAP adapter Procedure If you originally installed the adapter using a downloaded archive, to upgrade the JBoss EAP adapter, perform the following procedure. Download the new adapter archive. Remove the adapter modules by deleting the EAP_HOME/modules/system/add-ons/keycloak/ directory. Unzip the downloaded archive into EAP_HOME . Procedure If you originally installed the adapter using RPM, to upgrade the adapter, complete the following steps, which are different depending on whether you are performing a minor or a micro upgrade: For minor upgrades, use Yum to uninstall any adapters you currently have installed and then use Yum to install the new version of the adapters. For micro upgrades, use Yum to upgrade the adapter. This is the only step for micro upgrades. yum update 4.3. Upgrading the JavaScript adapter To upgrade a JavaScript adapter that has been copied to your web application, perform the following procedure. Procedure Download the new adapter archive. Overwrite the keycloak.js file in your application with the keycloak.js file from the downloaded archive. 4.4. Upgrading the Node.js adapter To upgrade a Node.js adapter that has been copied to your web application, perform the following procedure. Procedure Download the new adapter archive. Remove the existing Node.js adapter directory Unzip the updated file into its place Change the dependency for keycloak-connect in the package.json of your application

Commands:
update
Chapter 57. BrokerCapacity schema reference Used in: CruiseControlSpec Property Property type Description disk string The disk property has been deprecated. The Cruise Control disk capacity setting has been deprecated, is ignored, and will be removed in the future Broker capacity for disk in bytes. Use a number value with either standard OpenShift byte units (K, M, G, or T), their bibyte (power of two) equivalents (Ki, Mi, Gi, or Ti), or a byte value with or without E notation. For example, 100000M, 100000Mi, 104857600000, or 1e+11. cpuUtilization integer The cpuUtilization property has been deprecated. The Cruise Control CPU capacity setting has been deprecated, is ignored, and will be removed in the future Broker capacity for CPU resource utilization as a percentage (0 - 100). cpu string Broker capacity for CPU resource in cores or millicores. For example, 1, 1.500, 1500m. For more information on valid CPU resource units see https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-cpu . inboundNetwork string Broker capacity for inbound network throughput in bytes per second. Use an integer value with standard OpenShift byte units (K, M, G) or their bibyte (power of two) equivalents (Ki, Mi, Gi) per second. For example, 10000KiB/s. outboundNetwork string Broker capacity for outbound network throughput in bytes per second. Use an integer value with standard OpenShift byte units (K, M, G) or their bibyte (power of two) equivalents (Ki, Mi, Gi) per second. For example, 10000KiB/s. overrides BrokerCapacityOverride array Overrides for individual brokers. The overrides property lets you specify a different capacity configuration for different brokers.

Commands:
3.2. Installing Samba Using ISO During the installation of Red Hat Gluster Storage, select the RH-Gluster-Samba-Server component, in the Customizing the Software Selection screen. If you want to integrate with Active Directory, select both RH-Gluster-Samba-Server and RH-Gluster-AD-Integration components. Figure 3.1. Customize Packages For more information about installing Red Hat Gluster Storage using an ISO, see Section 2.2, "Installing from an ISO Image"

Commands:
8.81. gzip 8.81.1. RHBA-2014:0297 - gzip bug fix update Updated gzip packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The gzip packages provide the GNU gzip data compression program. Bug Fixes BZ# 949820 Previously, the "-h" option of the zgrep command was absent from the source code of the gzip utility. As a consequence, the output of running the "zgrep -h" command was not parsed, and the file name was printed. With this update, the possibility to use the short "-h" option besides the "--no-filename" option has been added. As a result, running the zgrep command with the "-h" option now prints the correct lines and suppresses the prefixing of the file names on output when multiple files are searched. BZ# 961810 Prior to this update, the time stamp of an archive was set by the futimesat() or utime() system calls when using the gzip utility. Consequently, the archived file had a lower time stamp than expected because only microsecond resolution was enabled, and a nanosecond time stamp was not provided. The underlying source code has been modified to attempt to use the utimensat() or futimens() system calls for nanosecond resolution. As a result, the archived file has exactly the same time stamp as the original file. Users of gzip are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 16. Verifying access to the subscriptions service User access to Hybrid Cloud Console services, including the subscriptions service, is controlled through a role-based access control (RBAC) system. User management capabilities for this RBAC system are granted to the Red Hat Organization Administrator (sometimes also referred to as org admin) for your Red Hat organization, and might also be granted to other members of the organization through the User Access administrator RBAC role. These user access administrators then manage the Hybrid Cloud Console RBAC groups, roles, and permissions for the other members in the organization by using the Settings > User Access option at console.redhat.com. The predefined role Subscriptions viewer controls the ability to activate and access the subscriptions service. By default, every user in the organization has this role. However, if your Organization Administrator has made changes to user access roles and groups, you might not be able to access the subscriptions service. Note The RBAC system for the console.redhat.com contains two roles for the subscriptions service. The Subscriptions administrator role contains every available permission for the subscriptions service. The Subscriptions viewer role contains a subset of the permissions in the Subscriptions administrator role. An example of this type of user is one who only needs to view high-level report data, but does not need to view more detailed information about individual subscriptions and systems. By default, all users are assigned the Subscriptions viewer role through the RBAC Default access group. However, the default behavior for role assignments is affected by how an organization is using RBAC groups to manage user access. If custom groups are in use instead of the Default access group, the Organization Administrator or another user with the User Access administrator RBAC role must manually update these groups to contain the new roles and manage any default assignment of them to the users in the organization. Procedure If you cannot activate or access the subscriptions service, contact your Organization Administrator. Your Organization Administrator can provide information about the status of the subscriptions service for your organization. Additional resources For more information about console.redhat.com user access, see the User Access Configuration Guide for Role-Based Access Control .

Commands:
Chapter 7. Logging 7.1. Enabling protocol logging The client can log AMQP protocol frames to the console. This data is often critical when diagnosing problems. To enable protocol logging, set the PN_TRACE_FRM environment variable to 1 : Example: Enabling protocol logging USD export PN_TRACE_FRM=1 USD <your-client-program> To disable protocol logging, unset the PN_TRACE_FRM environment variable.

Commands:
export PN_TRACE_FRM=1 <your-client-program>
Chapter 1. Overview Troubleshooting OpenShift Data Foundation is written to help administrators understand how to troubleshoot and fix their Red Hat OpenShift Data Foundation cluster. Most troubleshooting tasks focus on either a fix or a workaround. This document is divided into chapters based on the errors that an administrator may encounter: Chapter 2, Downloading log files and diagnostic information using must-gather shows you how to use the must-gather utility in OpenShift Data Foundation. Chapter 3, Commonly required logs for troubleshooting shows you how to obtain commonly required log files for OpenShift Data Foundation. Chapter 6, Troubleshooting alerts and errors in OpenShift Data Foundation shows you how to identify the encountered error and perform required actions. Warning Red Hat does not support running Ceph commands in OpenShift Data Foundation clusters (unless indicated by Red Hat support or Red Hat documentation) as it can cause data loss if you run the wrong commands. In that case, the Red Hat support team is only able to provide commercially reasonable effort and may not be able to restore all the data in case of any data loss.

Commands:
8.2. On Hyper-V Red Hat Enterprise Linux 6.4 and onward include Microsoft's Linux Integration Services, a set of drivers that enable synthetic device support in supported virtualized operating systems. Further details about the drivers provided are available from http://technet.microsoft.com/en-us/library/dn531030.aspx . Important Note that the built-in Red Hat Enterprise Linux Integration Service drivers for Hyper-V are sufficient for Red Hat Enterprise Linux guests to run using the high performance synthetic devices on Hyper-V hosts. These built-in drivers are certified by Red Hat for this use, and certified configurations can be viewed on the Red Hat Customer Portal . Therefore, it is not necessary to download and install Linux Integration Services (LIS) packages, and doing so may limit your Red Hat support, as described in the related Knowledgebase article . The following enhancements have been made to allow for easier deployment and management of Red Hat Enterprise Linux guest virtual machines: Upgraded VMBUS protocols - VMBUS protocols have been upgraded to Windows 8 level. As part of this work, now VMBUS interrupts can be processed on all available virtual CPUs in the guest. Furthermore, the signaling protocol between the Red Hat Enterprise Linux guest virtual machine and the Windows host physical machine has been optimized. Synthetic frame buffer driver - Provides enhanced graphics performance and superior resolution for Red Hat Enterprise Linux desktop users. Live Virtual Machine Backup support - Provisions uninterrupted backup support for live Red Hat Enterprise Linux guest virtual machines. Dynamic expansion of fixed size Linux VHDXs - Allows expansion of live mounted fixed size Red Hat Enterprise Linux VHDXs. Boot using UEFI - Allows virtual machines to boot using Unified Extensible Firmware Interface (UEFI) on a Hyper-V 2012 R2 host. For more information and features, refer to Red Hat Enterprise Linux - Virtualization Administration Guide and to the following article:" Enabling Linux Support on Windows Server 2012 R2 Hyper-V ".

Commands:
6.5. Internal Registration Note See the TPS Profiles section of the Red Hat Certificate System Planning, Installation and Deployment Guide for general information. In case of Internal Registration , the TPS profile (token type) is determined by the Mapping Resolver . In contrast with External Registration , authentication information is defined within the profile itself. For example: Another difference from External Registration is that the CA and KRA connector information is defined under each key type of each profile. For example: TKS connector information, however, is defined per profile: Note Switching registration types between Internal and External Registration means you have to format all previously registered tokens before you can continue using them.

Commands:
op.enroll.userKey.auth.enable=true op.enroll.userKey.auth.id=ldap1
op.enroll.userKey.keyGen.encryption.ca.conn=ca1 op.enroll.userKey.keyGen.encryption.serverKeygen.drm.conn=kra1
op.enroll.userKey.tks.conn=tks1
Chapter 8. Disabling the LVMS CSI provider or CSI snapshot You can configure MicroShift to disable the built-in logical volume manager storage (LVMS) Container Storage Interface (CSI) provider or the CSI snapshot capabilities to reduce the use of runtime resources such as RAM, CPU, and storage. 8.1. Disabling deployments that run CSI snapshot implementations Use the following procedure to disable installation of the CSI implementation pods. Important This procedure is for users who are defining the configuration file before installing and running MicroShift. If MicroShift is already started then CSI snapshot implementation will be running. Users must manually remove it by following the uninstallation instructions. Note MicroShift will not delete CSI snapshot implementation pods. You must configure MicroShift to disable installation of the CSI snapshot implementation pods during the startup process. Procedure Disable installation of the CSI snapshot controller by entering the optionalCsiComponents value under the storage section of the MicroShift configuration file in /etc/microshift/config.yaml : # ... storage: {} 1 # ... 1 Accepted values are: Not defining optionalCsiComponents . Specifying optionalCsiComponents field with an empty value ( [] ) or a single empty string element ( [""] ). Specifying optionalCsiComponents with one of the accepted values which are snapshot-controller , or none . A value of none is mutually exclusive with all other values. Note If the optionalCsiComponents value is empty or null, MicroShift defaults to deploying snapshot-controller. After the optionalCsiComponents field is specified with a supported value in the config.yaml , start MicroShift by running the following command: USD sudo systemctl start microshift Note MicroShift does not redeploy the disabled components after a restart. 8.2. Disabling deployments that run the CSI driver implementations Use the following procedure to disable installation of the CSI implementation pods. Important This procedure is for users who are defining the configuration file before installing and running MicroShift. If MicroShift is already started then CSI driver implementation will be running. Users must manually remove it by following the uninstallation instructions. Note MicroShift will not delete CSI driver implementation pods. You must configure MicroShift to disable installation of the CSI driver implementation pods during the startup process. Procedure Disable installation of the CSI driver by entering the driver value under the storage section of the MicroShift configuration file in /etc/microshift/config.yaml : # ... storage driver: - "none" 1 # ... 1 Valid values are none or lvms . Note By default, the driver value is empty or null and LVMS is deployed. Start MicroShift after the driver field is specified with a supported value in the /etc/microshift/config.yaml file by running the following command: USD sudo systemctl enable --now microshift Note MicroShift does not redeploy the disabled components after a restart operation.

Commands:
storage: {} 1
sudo systemctl start microshift
storage driver: - "none" 1
sudo systemctl enable --now microshift
Chapter 20. Unlocking assets By default, whenever you open and modify an asset in Business Central, that asset is automatically locked for your exclusive use in order to avoid conflicts in a multiuser setup. This lock is automatically released when your session ends or when you save or close the asset. This lock feature ensures that users do not overwrite each other's changes. However, you can force unlock an asset if you need to edit a file that is locked by another user. Procedure In Business Central, go to Menu Design Projects and click the project name. Select the asset from the list to open the asset designer. Go to Overview Metadata and view the Lock Status . Figure 20.1. Unlock metadata view If the asset is already being edited by another user, the following will be displayed in the Lock status field: Locked by <user_name> Click Force unlock asset to unlock. The following confirmation pop-up message is displayed: Are you sure you want to release the lock of this asset? This might cause <user_name> to lose unsaved changes! Click Yes to confirm. The asset returns to an unlocked state and the lock icon option will appear to the asset.

Commands:
8.76. grep 8.76.1. RHBA-2014:0622 - grep bug fix update Updated grep packages that fix one bug are now available for Red Hat Enterprise Linux 6. The grep utility searches through textual input for lines which contain a match to a specified pattern and then prints the matching lines. GNU grep utilities include grep, egrep and fgrep. Bug Fix BZ# 683753 Previously, the grep utility did not request processing of UTF-8 from the Perl-compatible regular expressions (PCRE) library if a UTF-8 locale was in effect. As a consequence, Unicode symbols were not correctly matched if a Perl regular expression (the "-P" option) was used with a UTF-8 locale. This update adds a request for UTF-8 processing to the PCRE library, and grep now correctly handles Unicode symbols in the described situation. Users of grep are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 147. KafkaConnectorStatus schema reference Used in: KafkaConnector Property Property type Description conditions Condition array List of status conditions. observedGeneration integer The generation of the CRD that was last reconciled by the operator. autoRestart AutoRestartStatus The auto restart status. connectorStatus map The connector status, as reported by the Kafka Connect REST API. tasksMax integer The maximum number of tasks for the Kafka Connector. topics string array The list of topics used by the Kafka Connector.

Commands:
2.8.3. Using IPTables The first step in using iptables is to start the iptables service. Use the following command as the root user to start the iptables service: Note The ip6tables service can be turned off if you intend to use the iptables service only. If you deactivate the ip6tables service, remember to deactivate the IPv6 network also. Never leave a network device active without the matching firewall. To force iptables to start by default when the system is booted, use the following command as the root user: This forces iptables to start whenever the system is booted into runlevel 3, 4, or 5. 2.8.3.1. IPTables Command Syntax The following sample iptables command illustrates the basic command syntax: iptables -A <chain> -j <target> The -A option specifies that the rule be appended to <chain> . Each chain is comprised of one or more rules , and is therefore also known as a ruleset . The three built-in chains are INPUT, OUTPUT, and FORWARD. These chains are permanent and cannot be deleted. The chain specifies the point at which a packet is manipulated. The -j <target> option specifies the target of the rule; i.e., what to do if the packet matches the rule. Examples of built-in targets are ACCEPT, DROP, and REJECT. Refer to the iptables man page for more information on the available chains, options, and targets.

Commands:
~]# service iptables restart iptables: Applying firewall rules: [ OK ]
~]# chkconfig --level 345 iptables on