mtpti5iD/redhat-docs_dataset huggingface dataset:
Installing Red Hat Developer Hub on OpenShift Container Platform Red Hat Developer Hub 1.2 Red Hat Customer Content Services

Commands:
global: auth: backend: enabled: true clusterRouterBase: apps.<clusterName>.com # other Red Hat Developer Hub Helm Chart configurations
Loaded config from app-config-from-configmap.yaml, env 2023-07-24T19:44:46.223Z auth info Configuring "database" as KeyStore provider type=plugin Backend failed to start up Error: Missing required config value at 'backend.database.client'
NAMESPACE=<emphasis><rhdh></emphasis> new-project USD{NAMESPACE} || oc project USD{NAMESPACE}
helm upgrade redhat-developer-hub -i https://github.com/openshift-helm-charts/charts/releases/download/redhat-redhat-developer-hub-1.2.6/redhat-developer-hub-1.2.6.tgz
PASSWORD=USD(oc get secret redhat-developer-hub-postgresql -o jsonpath="{.data.password}" | base64 -d) CLUSTER_ROUTER_BASE=USD(oc get route console -n openshift-console -o=jsonpath='{.spec.host}' | sed 's/^[^.]*\.//') helm upgrade redhat-developer-hub -i "https://github.com/openshift-helm-charts/charts/releases/download/redhat-redhat-developer-hub-1.2.6/redhat-developer-hub-1.2.6.tgz" --set global.clusterRouterBase="USDCLUSTER_ROUTER_BASE" --set global.postgresql.auth.password="USDPASSWORD"
echo "https://redhat-developer-hub-USDNAMESPACE.USDCLUSTER_ROUTER_BASE"
Part II. Storage Administration The Storage Administration section starts with storage considerations for Red Hat Enterprise Linux 7. Instructions regarding partitions, logical volume management, and swap partitions follow this. Disk Quotas, RAID systems are , followed by the functions of mount command, volume_key, and acls. SSD tuning, write barriers, I/O limits and diskless systems follow this. The large chapter of Online Storage is , and finally device mapper multipathing and virtual storage to finish.

Commands:
Chapter 1. Red Hat OpenShift support for Windows Containers overview Red Hat OpenShift support for Windows Containers is a feature providing the ability to run Windows compute nodes in an OpenShift Container Platform cluster. This is possible by using the Red Hat Windows Machine Config Operator (WMCO) to install and manage Windows nodes. With a Red Hat subscription, you can get support for running Windows workloads in OpenShift Container Platform. Windows instances deployed by the WMCO are configured with the containerd container runtime. For more information, see the release notes . You can add Windows nodes either by creating a compute machine set or by specifying existing Bring-Your-Own-Host (BYOH) Window instances through a configuration map . Note Compute machine sets are not supported for bare metal or provider agnostic clusters. For workloads including both Linux and Windows, OpenShift Container Platform allows you to deploy Windows workloads running on Windows Server containers while also providing traditional Linux workloads hosted on Red Hat Enterprise Linux CoreOS (RHCOS) or Red Hat Enterprise Linux (RHEL). For more information, see getting started with Windows container workloads . You need the WMCO to run Windows workloads in your cluster. The WMCO orchestrates the process of deploying and managing Windows workloads on a cluster. For more information, see how to enable Windows container workloads . You can create a Windows MachineSet object to create infrastructure Windows machine sets and related machines so that you can move supported Windows workloads to the new Windows machines. You can create a Windows MachineSet object on multiple platforms. You can schedule Windows workloads to Windows compute nodes. You can perform Windows Machine Config Operator upgrades to ensure that your Windows nodes have the latest updates. You can remove a Windows node by deleting a specific machine. You can use Bring-Your-Own-Host (BYOH) Windows instances to repurpose Windows Server VMs and bring them to OpenShift Container Platform. BYOH Windows instances benefit users who are looking to mitigate major disruptions in the event that a Windows server goes offline. You can use BYOH Windows instances as nodes on OpenShift Container Platform 4.8 and later versions. You can disable Windows container workloads by performing the following: Uninstalling the Windows Machine Config Operator Deleting the Windows Machine Config Operator namespace

Commands:
Chapter 2. Preparing your Environment for Satellite Installation in an IPv6 Network You can install and use Satellite in an IPv6 network. Before installing Satellite in an IPv6 network, view the limitations and ensure that you meet the requirements. To provision hosts in an IPv6 network, after installing Satellite, you must also configure Satellite for the UEFI HTTP boot provisioning. For more information, see Section 4.5, "Configuring Satellite for UEFI HTTP Boot Provisioning in an IPv6 Network" . 2.1. Limitations of Satellite Installation in an IPv6 Network Satellite installation in an IPv6 network has the following limitations: You can install Satellite and Capsules in IPv6-only systems, dual-stack installation is not supported. Although Satellite provisioning templates include IPv6 support for PXE and HTTP (iPXE) provisioning, the only tested and certified provisioning workflow is the UEFI HTTP Boot provisioning. This limitation only relates to users who plan to use Satellite to provision hosts. 2.2. Requirements for Satellite Installation in an IPv6 Network Before installing Satellite in an IPv6 network, ensure that you meet the following requirements: If you plan to provision hosts from Satellite or Capsules, you must install Satellite and Capsules on Red Hat Enterprise Linux version 7.9 or higher because these versions include the latest version of the grub2 package. You must deploy an external DHCP IPv6 server as a separate unmanaged service to bootstrap clients into GRUB2, which then configures IPv6 networking either using DHCPv6 or assigning static IPv6 address. This is required because the DHCP server in Red Hat Enterprise Linux (ISC DHCP) does not provide an integration API for managing IPv6 records, therefore the Capsule DHCP plug-in that provides DHCP management is limited to IPv4 subnets. You must deploy an external HTTP proxy server that supports both IPv4 and IPv6. This is required because Red Hat Content Delivery Network distributes content only over IPv4 networks, therefore you must use this proxy to pull content into the Satellite on your IPv6 network. You must configure Satellite to use this dual stack (supporting both IPv4 and IPv6) HTTP proxy server as the default proxy. For more information, see Adding a Default HTTP Proxy to Satellite .

Commands:
5.2. AutoCommitTxn Execution Property Since user level commands may execute multiple source commands, users can specify the AutoCommitTxn execution property to control the transactional behavior of a user command when not in a local or global transaction. Table 5.2. AutoCommitTxn Settings Setting Description OFF Do not wrap each command in a transaction. Individual source commands may commit or rollback regardless of the success or failure of the overall command. ON Wrap each command in a transaction. This mode is the safest, but may introduce performance overhead. DETECT This is the default setting. Will automatically wrap commands in a transaction, but only if the command seems to be transactionally unsafe. The concept of command safety with respect to a transaction is determined by Red Hat JBoss Data Virtualization based upon command type, the transaction isolation level, and available metadata. A wrapping transaction is not needed if any of the following is true: A user command is fully pushed to the source. The user command is a SELECT (including XML) and the transaction isolation is not REPEATABLE_READ nor SERIALIZABLE. The user command is a stored procedure and the transaction isolation is not REPEATABLE_READ nor SERIALIZABLE and the updating model count is zero. The update count may be set on all procedures as part of the procedure metadata in the model.

Commands:
Chapter 3. Prerequisites For the solution to work, the following requirements must be met. All nodes must have the same: number of CPUs and RAM software configuration RHEL release (please note that at least RHEL 8.6 is required) firewall settings SAP HANA release (SAP HANA 2.0 SPS04 or later) The pacemaker packages are only installed on the cluster nodes and must use the same version of resource-agents-sap-hana (0.162.1 or later). To be able to support SAP HANA Multitarget System Replication , refer to Add SAP HANA Multitarget System Replication autoregister support . Also, set the following: use register_secondaries_on_takeover=true use log_mode=normal The initial setup is based on the installation guide, Automating SAP HANA Scale-Up System Replication using the RHEL HA Add-On . The system replication configuration of all SAP HANA instances is based on SAP requirements. For more information, refer to the guidelines from SAP based on the SAP HANA Administration Guide .

Commands:
Appendix A. Using your Red Hat subscription Red Hat Connectivity Link is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Managing your subscriptions Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. In the menu bar, click Subscriptions to view and manage your subscriptions. Revised on 2025-03-12 11:42:29 UTC

Commands:
6.2. Creating Guests with virt-install You can use the virt-install command to create guest virtual machines from the command line. virt-install is used either interactively or as part of a script to automate the creation of virtual machines. Using virt-install with Kickstart files allows for unattended installation of virtual machines. The virt-install tool provides a number of options that can be passed on the command line. To see a complete list of options run the following command: Note that you need root privileges in order for virt-install commands to complete successfully. The virt-install man page also documents each command option and important variables. qemu-img is a related command which may be used before virt-install to configure storage options. An important option is the --graphics option which allows graphical installation of a virtual machine. Example 6.1. Using virt-install to install a Red Hat Enterprise Linux 5 guest virtual machine This example creates a Red Hat Enterprise Linux 5 guest: Ensure that you select the correct os-type for your operating system when running this command. Refer to man virt-install for more examples. Note When installing a Windows guest with virt-install , the --os-type= windows option is recommended. This option prevents the CD-ROM from disconnecting when rebooting during the installation procedure. The --os-variant option further optimizes the configuration for a specific guest operating system. After the installation completes, you can connect to the guest operating system. For more information, see Section 6.5, "Connecting to Virtual Machines"

Commands:
virt-install --help
virt-install --name=guest1-rhel5-64 --file=/var/lib/libvirt/images/guest1-rhel5-64.dsk --file-size=8 --nonsparse --graphics spice --vcpus=2 --ram=2048 --location=http://example1.com/installation_tree/RHEL5.6-Server-x86_64/os --network bridge=br0 --os-type=linux --os-variant=rhel5.4
probe::tcp.setsockopt Name probe::tcp.setsockopt - Call to setsockopt Synopsis Values optstr Resolves optname to a human-readable format level The level at which the socket options will be manipulated optlen Used to access values for setsockopt name Name of this probe optname TCP socket options (e.g. TCP_NODELAY, TCP_MAXSEG, etc) sock Network socket Context The process which calls setsockopt

Commands:
tcp.setsockopt
Chapter 93. OtherArtifact schema reference Used in: Plugin Property Description url URL of the artifact which will be downloaded. AMQ Streams does not do any security scanning of the downloaded artifacts. For security reasons, you should first verify the artifacts manually and configure the checksum verification to make sure the same artifact is used in the automated build. Required for jar , zip , tgz and other artifacts. Not applicable to the maven artifact type. string sha512sum SHA512 checksum of the artifact. Optional. If specified, the checksum will be verified while building the new container. If not specified, the downloaded artifact will not be verified. Not applicable to the maven artifact type. string fileName Name under which the artifact will be stored. string insecure By default, connections using TLS are verified to check they are secure. The server certificate used must be valid, trusted, and contain the server name. By setting this option to true , all TLS verification is disabled and the artifact will be downloaded, even when the server is considered insecure. boolean type Must be other . string

Commands:
3.5. Listing Hosts This Ruby example lists the hosts. # Get the reference to the root of the services tree: system_service = connection.system_service # Get the reference to the service that manages the # collection of hosts: host_service = system_service.hosts_service # Retrieve the list of hosts and for each one # print its name: host = host_service.list host.each do |host| puts host.name end In an environment with only one attached host ( Atlantic ) the example outputs: For more information, see https://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4/HostsService#list-instance_method .

Commands:
Get the reference to the root of the services tree: system_service = connection.system_service Get the reference to the service that manages the collection of hosts: host_service = system_service.hosts_service Retrieve the list of hosts and for each one print its name: host = host_service.list host.each do |host| puts host.name end
Atlantic
2.44. RHEA-2011:0532 - new package: svrcore A new svrcore package is now available for Red Hat Enterprise Linux 6. The svrcore package contains an API library which provides various methods of handling and managing secure Personal Identification Number (PIN) storage. The svrcore library uses the Mozilla NSS cryptographic library. An example of an application which would use svrcore is one that must be restarted without user intervention, but which requires a PIN to unlock a private key and other cryptographic objects. This enhancement update adds a new svrcore package to Red Hat Enterprise Linux 6. (BZ# 643539 ) All users requiring svrcore should install this newly-released package.

Commands:
Chapter 2. Installing Kaoto Important It is recommended to install the Extension Pack for Apache Camel by Red Hat . It will provide a set of tools to manage, edit, run, and debug Camel integrations in various contexts. The following procedure explains how to install VS Code and other essential extensions required to get started with Kaoto. If you do not have Visual Studio Code installed, install it from here . Launch VS Code. Install the Extension Pack for Apache Camel by Red Hat into your Visual Studio Code instance. To run and debug Camel integrations using VS Code UI, install JBang CLI . Optionally, to run Camel integrations from the command line, install Camel CLI . Important Create and select a workspace folder where all the integration will be stored. Selecting a workspace is important to ensure all required commands will be available and behave correctly.

Commands:
16.3.4. Module Arguments PAM uses arguments to pass information to a pluggable module during authentication for some modules. For example, the pam_userdb.so module uses secrets stored in a Berkeley DB file to authenticate the user. Berkeley DB is an open source database system embedded in many applications. The module takes a db argument so that Berkeley DB knows which database to use for the requested service. A typical pam_userdb.so line within a PAM configuration file looks like this: In the example, replace <path-to-file> with the full path to the Berkeley DB database file. Invalid arguments are ignored and do not otherwise affect the success or failure of the PAM module. However, most modules report errors to the /var/log/messages file.

Commands:
auth required pam_userdb.so db= <path-to-file>
4.5.4. Synchronizing Quotas with the quotasync Command GFS2 stores all quota information in its own internal file on disk. A GFS2 node does not update this quota file for every file system write; rather, by default it updates the quota file once every 60 seconds. This is necessary to avoid contention among nodes writing to the quota file, which would cause a slowdown in performance. As a user or group approaches their quota limit, GFS2 dynamically reduces the time between its quota-file updates to prevent the limit from being exceeded. The normal time period between quota synchronizations is a tunable parameter, quota_quantum . You can change this from its default value of 60 seconds using the quota_quantum= mount option, as described in Table 4.2, "GFS2-Specific Mount Options" . The quota_quantum parameter must be set on each node and each time the file system is mounted. Changes to the quota_quantum parameter are not persistent across unmounts. You can update the quota_quantum value with the mount -o remount . You can use the quotasync command to synchronize the quota information from a node to the on-disk quota file between the automatic updates performed by GFS2. Usage Synchronizing Quota Information u Sync the user quota files. g Sync the group quota files a Sync all file systems that are currently quota-enabled and support sync. When -a is absent, a file system mountpoint should be specified. mntpnt Specifies the GFS2 file system to which the actions apply. Tuning the Time Between Synchronizations MountPoint Specifies the GFS2 file system to which the actions apply. secs Specifies the new time period between regular quota-file synchronizations by GFS2. Smaller values may increase contention and slow down performance. Examples This example synchronizes all the cached dirty quotas from the node it is run on to the ondisk quota file for the file system /mnt/mygfs2 . This example changes the default time period between regular quota-file updates to one hour (3600 seconds) for file system /mnt/mygfs2 when remounting that file system on logical volume /dev/volgroup/logical_volume .

Commands:
quotasync [-ug] -a| mntpnt
mount -o quota_quantum= secs ,remount BlockDevice MountPoint
quotasync -ug /mnt/mygfs2
mount -o quota_quantum=3600,remount /dev/volgroup/logical_volume /mnt/mygfs2
5.137. keyutils 5.137.1. RHEA-2012:0963 - keyutils enhancement update Updated keyutils packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The keyutils package provides utilities to control the Linux kernel key management facility and to provide a mechanism by which the kernel calls up to user space to get a key instantiated. Enhancement BZ# 772497 With this update, the request-key utility allows multiple configuration files to be provided. The request-key configuration file and its associated key-type specific variants are used by the request-key utility to determine which program should be run to instantiate a key. All users of keyutils are advised to upgrade to these updated packages, which add this enhancement.

Commands:
Chapter 8. Authentication and Interoperability Better Interoperability with Active Directory Added functionality of System Security Services Daemon ( SSSD ) enables better interoperability of Red Hat Enterprise Linux clients with Active Directory, which makes identity management easier in Linux and Windows environments. The most notable enhancements include resolving users and groups and authenticating users from trusted domains in a single forest, DNS updates, site discovery, and using NetBIOS name for user and group lookups. Apache Modules for IPA A set of Apache modules has been added to Red Hat Enterprise Linux 6.6 as a Technology Preview. The Apache modules can be used by external applications to achieve tighter interaction with Identity Management beyond simple authentication.

Commands:
Chapter 3. Attaching a host-based subscription to hypervisors Use this procedure to attach a host-based subscription, such as Red Hat Enterprise Linux for Virtual Datacenters , to hypervisors that are already registered to Red Hat Satellite. Note This procedure is only valid if you have Simple Content Access (SCA) disabled on Satellite. You are not required to manually attach the subscriptions if you have SCA enabled. Note that SCA is enabled by default for newly created organizations. To learn more about SCA, see Simple Content Access . To register a new hypervisor, ensure your host activation key includes a host-based subscription, then see Registering Hosts to Satellite in Managing Hosts . You must register a hypervisor before configuring virt-who to query it. Prerequisites Import a Subscription Manifest that includes a host-based subscription into Satellite Server. Ensure you have sufficient entitlements for the host-based subscription to cover all of the hypervisors you plan to use. Procedure In the Satellite web UI, navigate to Hosts > Content Hosts . In the Content Hosts list, select the check box to the name of each hypervisor you want to attach the subscription to. From the Select Action list, select Manage Subscriptions . In the Content Host Bulk Subscriptions window, select a host-based subscription, then click Add Selected . For CLI users On Satellite Server, list the available subscriptions to find the host-based subscription's ID: Attach the host-based subscription to a hypervisor: Repeat these steps for each hypervisor you plan to use.

Commands:
hammer subscription list --organization-id organization_id
hammer host subscription attach --host host_name --subscription-id subscription_id
Part II. Managing projects in Business Central As a process administrator, you can use Business Central in Red Hat Process Automation Manager to manage new, sample, and imported projects on a single or multiple branches. Prerequisites Red Hat JBoss Enterprise Application Platform 7.4 is installed. For details, see the Red Hat JBoss Enterprise Application Platform 7.4 Installation Guide . Red Hat Process Automation Manager is installed and configured with KIE Server. For more information, see Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 . Red Hat Process Automation Manager is running and you can log in to Business Central with the developer role. For more information, see Planning a Red Hat Process Automation Manager installation .

Commands:
7.98. kdebase 7.98.1. RHBA-2012:1371 - kdebase bug fix update Updated kdebase packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The K Desktop Environment (KDE) is a graphical desktop environment for the X Window System. The kdebase packages include core applications for KDE. Bug Fixes BZ#608007 Prior to this update, the Konsole context menu item "Show menu bar" was always checked in new windows even if this menu item was disabled before. This update modifies the underlying code to handle the menu item "Show menu bar" as expected. BZ# 729307 Prior to this update, users could not define a default size for xterm windows when using the Konsole terminal in KDE. This update modifies the underlying code and adds the functionality to define a default size. All users of kdebase are advised to upgrade to these updated packages, which fix these bugs.

Commands: