mtpti5iD/redhat-docs_dataset huggingface dataset:
8.2. Create New Relational Source Model 8.2.1. Create a New Relational Source Model To create a new empty relational source model: Launch the New Model Wizard . Specify a unique model name. Select Relational option from Model Class drop-down menu. Select Source Model from Model Type drop-down menu. Click Finish . Note You can change the target location (i.e. project or folder) by selecting the Browse... button and selecting a project or folder within your workspace. In addition to creating a new empty relational source model, you can also copy from existing model of the same model class. 8.2.2. Generate File Translator Procedures This builder option allows construction of a relational model containing one or more of the procedures required for accessing file based data via a file translator. To create a new relational model containing file translator procedures, complete first 4 steps from the Create a New Relational Source Model section and continue with these additional steps: Select the model builder labeled Generate File Translator Procedures and click > . The Generate File Translator Procedures dialog will be displayed. Select one or more of the Available File Translator Procedures , then click Finish . 8.2.3. Generate Web Service Translator Procedures This builder option allows construction of a relational model containing one or more of the procedures required for accessing web-service-based XML data via a web service translator. To create a new relational model containing web-service-based translator procedures, complete first 4 steps from the Create a New Relational Source Model section and continue with these additional steps: Select the model builder labeled Generate Web Service Translator Procedures and click > . The Generate Web Service Translator Procedures dialog will be displayed. Select one or more of the Available Web Services Translator Procedures , then click Finish . 8.2.4. Copy from an Existing Relational Source Model This builder option performs a structural copy of the contents of an existing model to a newly defined model. You can choose a full copy or select individual model components for copy. To create a new relational model by copying contents from another relational source model, complete first 4 steps from the Create a New Relational Source Model section and continue with these additional steps: Select the model builder labeled Copy from existing model of the same model class and click > . The Copy Existing Model dialog will be displayed. Select an existing relational model from the workspace using the browse button. Note An existing model will be preselected if a relational model in the workspace is selected in the model-explorer-view prior to starting the new model wizard. Select the Copy all descriptions option if desired. Click Finish .

Commands:
8.3.4. Customizing Security Profiles After selecting the security profile that suits your security policy, you can further adjust it by clicking the Customize button. This will open the new Customization window that allows you to modify the currently selected XCCDF profile without actually changing the respective XCCDF file. Figure 8.4. Customizing the Selected Security Profile The Customization window contains a complete set of XCCDF elements relevant to the selected security profile with detailed information about each element and its functionality. You can enable or disable these elements by selecting or de-selecting the respective check boxes in the main field of this window. The Customization window also supports undo and redo functionality; you can undo or redo your selections by clicking the respective arrow icon in the top left corner of the window. You can also change variables that will later be used for evaluation. Find the desired item in the Customization window, navigate to the right part and use the Modify value field. Figure 8.5. Setting a value for the selected item in the Customization window After you have finished your profile customizations, confirm the changes by clicking the Confirm Customization button. Your changes are now in the memory and do not persist if SCAP Workbench is closed or certain changes, such as selecting a new SCAP content or choosing another customization option, are made. To store your changes, click the Save Customization button in the SCAP Workbench window. This action allows you to save your changes to the security profile as an XCCDF customization file in the chosen directory. Note that this customization file can be further selected with other profiles.

Commands:
7.111. libdvdread 7.111.1. RHBA-2012:1247 - libdvdread bug fix update Updated libdvdread packages that fix one bug is now available for Red Hat Enterprise Linux 6. The libdvdread packages contain a simple foundation to read DVD video disks. This provides the functionality that is required to access many DVDs. Bug Fix BZ# 842016 Prior to this update, the dvd_stat_t structure was not public. As a consequence, source code that required such structures could not be compiled. This update makes the dvd_stat_t structure public, to allow compiling code with of this type. All users of libdvdread are advised to upgrade to these updated packages, which fix this bug.

Commands:
19.3. Security Security Guide The Security Guide is designed to assist users and administrators in learning the processes and practices of securing workstations and servers against local and remote intrusion, exploitation, and malicious activity. SELinux User's and Administrator's Guide The SELinux User's and Administrator's Guide covers the management and use of Security-Enhanced Linux. Note that managing confined services, which was documented in a stand-alone book in Red Hat Enterprise Linux 6, is now part of the SELinux User's and Administrator's Guide.

Commands:
1.4. Pacemaker Architecture Components A cluster configured with Pacemaker comprises separate component daemons that monitor cluster membership, scripts that manage the services, and resource management subsystems that monitor the disparate resources. The following components form the Pacemaker architecture: Cluster Information Base (CIB) The Pacemaker information daemon, which uses XML internally to distribute and synchronize current configuration and status information from the Designated Coordinator (DC) - a node assigned by Pacemaker to store and distribute cluster state and actions by means of the CIB - to all other cluster nodes. Cluster Resource Management Daemon (CRMd) Pacemaker cluster resource actions are routed through this daemon. Resources managed by CRMd can be queried by client systems, moved, instantiated, and changed when needed. Each cluster node also includes a local resource manager daemon (LRMd) that acts as an interface between CRMd and resources. LRMd passes commands from CRMd to agents, such as starting and stopping and relaying status information. Shoot the Other Node in the Head (STONITH) Often deployed in conjunction with a power switch, STONITH acts as a cluster resource in Pacemaker that processes fence requests, forcefully powering down nodes and removing them from the cluster to ensure data integrity. STONITH is configured in CIB and can be monitored as a normal cluster resource. corosync corosync is the component - and a daemon of the same name - that serves the core membership and member-communication needs for high availability clusters. It is required for the High Availability Add-On to function. In addition to those membership and messaging functions, corosync also: Manages quorum rules and determination. Provides messaging capabilities for applications that coordinate or operate across multiple members of the cluster and thus must communicate stateful or other information between instances.

Commands:
Chapter 11. steps To start deploying your OpenShift Data Foundation, you can use the internal mode within OpenShift Container Platform or use external mode to make available services from a cluster running outside of OpenShift Container Platform. Depending on your requirement, go to the respective deployment guides. Internal mode Deploying OpenShift Data Foundation using Amazon web services Deploying OpenShift Data Foundation using Bare Metal Deploying OpenShift Data Foundation using VMWare vSphere Deploying OpenShift Data Foundation using Microsoft Azure Deploying OpenShift Data Foundation using Google Cloud [Technology Preview] Deploying OpenShift Data Foundation using Red Hat OpenStack Platform [Technology Preview] Deploying OpenShift Data Foundation using Red Hat Virtualization Platform Deploying OpenShift Data Foundation on IBM Power Deploying OpenShift Data Foundation on IBM Z Infrastructure External mode Deploying OpenShift Data Foundation in external mode

Commands:
14.7.2. Setting NUMA Parameters The virsh numatune can either set or retrieve the NUMA parameters for a specified domain. Within the Domain XML file these parameters are nested within the <numatune> element. Without using options, only the current settings are displayed. The numatune domain command requires a specified domain and can take the following options: --mode - The mode can be set to either strict , interleave , or preferred . Running domains cannot have their mode changed while live unless the domain was started within strict mode. --nodeset contains a list of NUMA nodes that are used by the host physical machine for running the domain. The list contains nodes, each separated by a comma, with a dash - used for node ranges and a caret ^ used for excluding a node. Only one of the following three options can be used per instance: --config will take effect on the boot of a persistent guest virtual machine. --live will set the scheduler information of a running guest virtual machine. --current will affect the current state of the guest virtual machine.

Commands:
D.19. Guides View To open Teiid Designer's Guides View , click the main menu's Window > Show View > Other... and then click the Teiid Designer > Guides view in the dialog. The Guides view provides assistance for many common modeling tasks. The view includes categorized Modeling Actions and also links to Cheat Sheets for common processes. Cheat Sheets are an eclipse concept for which Teiid Designer has provided contributions (see Cheat Sheets view). The Guides view is shown below: Figure D.31. Guides View The upper Action Sets section provides categorized sets of actions. Select the desired category in the drop-down, then the related actions for the selected category are displayed in the list below it. Execute an action by clicking the Execute selected action link or double-clicking the action. The lower Cheat Sheets section provides a list of available Cheat Sheet links, which will launch the appropriate Cheat Sheet to guide you step-by-step through the selected process.

Commands:
Chapter 2. Load Balancing Considerations Distributing load between several Capsule Servers prevents any one Capsule from becoming a single point of failure. Configuring Capsules to use a load balancer can provide resilience against planned and unplanned outages. This improves availability and responsiveness. Consider the following guidelines when configuring load balancing: If you use Puppet, Puppet certificate signing is assigned to the first Capsule that you configure. If the first Capsule is down, clients cannot obtain Puppet content. This solution does not use Pacemaker or other similar HA tools to maintain one state across all Capsules. To troubleshoot issues, reproduce the issue on each Capsule, bypassing the load balancer. Additional Maintenance Required for Load Balancing Configuring Capsules to use a load balancer results in a more complex environment and requires additional maintenance. The following additional steps are required for load balancing: You must ensure that all Capsules have the same Content Views and synchronize all Capsules to the same Content View versions You must upgrade each Capsule in sequence You must backup each Capsule that you configure regularly Upgrading Capsule Servers in a Load Balancing Configuration To upgrade Capsule Servers from 6.10 to 6.11, complete the Upgrading Capsule Servers procedure in Upgrading and Updating Red Hat Satellite . There are no additional steps required for Capsule Servers in a load balancing configuration.

Commands:
Chapter 6. Configuring tagging for your integrations The cost management application tracks cloud and infrastructure costs with tags. Tags are also known as labels in OpenShift. You can refine tags in cost management to filter and attribute resources, organize your resources by cost, and allocate costs to different parts of your cloud infrastructure. Important You can only configure tags and labels directly on an integration. You can choose the tags that you activate in cost management, however, you cannot edit tags and labels in the cost management application. To learn more about the following topics, see Managing cost data using tagging : Planning your tagging strategy to organize your view of cost data Understanding how cost management associates tags Configuring tags and labels on your integrations

Commands:
Chapter 33. Preparing your environment for managing IdM using Ansible playbooks As a system administrator managing Identity Management (IdM), when working with Red Hat Ansible Engine, it is good practice to do the following: Create a subdirectory dedicated to Ansible playbooks in your home directory, for example ~/MyPlaybooks . Copy and adapt sample Ansible playbooks from the /usr/share/doc/ansible-freeipa/* and /usr/share/doc/rhel-system-roles/* directories and subdirectories into your ~/MyPlaybooks directory. Include your inventory file in your ~/MyPlaybooks directory. Using this practice, you can find all your playbooks in one place and you can run your playbooks without invoking root privileges. Note You only need root privileges on the managed nodes to execute the ipaserver , ipareplica , ipaclient and ipabackup ansible-freeipa roles. These roles require privileged access to directories and the dnf software package manager. Follow this procedure to create the ~/MyPlaybooks directory and configure it so that you can use it to store and run Ansible playbooks. Prerequisites You have installed an IdM server on your managed nodes, server.idm.example.com and replica.idm.example.com . You have configured DNS and networking so you can log in to the managed nodes, server.idm.example.com and replica.idm.example.com , directly from the control node. You know the IdM admin password. Procedure Create a directory for your Ansible configuration and playbooks in your home directory: Change into the ~/MyPlaybooks/ directory: Create the ~/MyPlaybooks/ansible.cfg file with the following content: Create the ~/MyPlaybooks/inventory file with the following content: This configuration defines two host groups, eu and us , for hosts in these locations. Additionally, this configuration defines the ipaserver host group, which contains all hosts from the eu and us groups. Optional: Create an SSH public and private key. To simplify access in your test environment, do not set a password on the private key: Copy the SSH public key to the IdM admin account on each managed node: These commands require that you enter the IdM admin password. Additional resources Installing an Identity Management server using an Ansible playbook How to build your inventory

Commands:
mkdir ~/MyPlaybooks/
cd ~/MyPlaybooks
[defaults] inventory = /home/ your_username /MyPlaybooks/inventory [privilege_escalation] become=True
[eu] server.idm.example.com [us] replica.idm.example.com [ipaserver:children] eu us
ssh-keygen
ssh-copy-id admin@server.idm.example.com ssh-copy-id admin@replica.idm.example.com
8.213. system-config-date 8.213.1. RHBA-2013:1098 - system-config-date bug fix update An updated system-config-date package that fixes one bug is now available for Red Hat Enterprise Linux 6. The system-config-date package provides a graphical interface for changing the system date and time, configuring the system time zone, and setting up the NTP daemon to synchronize the time of the system with an NTP time server. Bug Fix BZ#760977 When using unsupported locale settings during system installation, the firstboot utility previously failed with a stack trace after the initial phase of installation. Consequently, the user was not able to configure peripherals, users, kdump, and other settings. With this update, the underlying code has been modified to catch exceptions caused by incorrect locale values and firstboot now warns the users to change their locale instead of failing. Users of system-config-date are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 1. About CI/CD OpenShift Container Platform is an enterprise-ready Kubernetes platform for developers, which enables organizations to automate the application delivery process through DevOps practices, such as continuous integration (CI) and continuous delivery (CD). To meet your organizational needs, the OpenShift Container Platform provides the following CI/CD solutions: OpenShift Builds OpenShift Pipelines OpenShift GitOps Jenkins 1.1. OpenShift Builds OpenShift Builds provides you the following options to configure and run a build: Builds using Shipwright is an extensible build framework based on the Shipwright project. You can use it to build container images on an OpenShift Container Platform cluster. You can build container images from source code and Dockerfile by using image build tools, such as Source-to-Image (S2I) and Buildah. For more information, see builds for Red Hat OpenShift . Builds using BuildConfig objects is a declarative build process to create cloud-native apps. You can define the build process in a YAML file that you use to create a BuildConfig object. This definition includes attributes such as build triggers, input parameters, and source code. When deployed, the BuildConfig object builds a runnable image and pushes the image to a container image registry. With the BuildConfig object, you can create a Docker, Source-to-image (S2I), or custom build. For more information, see Understanding image builds . 1.2. OpenShift Pipelines OpenShift Pipelines provides a Kubernetes-native CI/CD framework to design and run each step of the CI/CD pipeline in its own container. It can scale independently to meet the on-demand pipelines with predictable outcomes. For more information, see Red Hat OpenShift Pipelines . 1.3. OpenShift GitOps OpenShift GitOps is an Operator that uses Argo CD as the declarative GitOps engine. It enables GitOps workflows across multicluster OpenShift and Kubernetes infrastructure. Using OpenShift GitOps, administrators can consistently configure and deploy Kubernetes-based infrastructure and applications across clusters and development lifecycles. For more information, see Red Hat OpenShift GitOps . 1.4. Jenkins Jenkins automates the process of building, testing, and deploying applications and projects. OpenShift Developer Tools provides a Jenkins image that integrates directly with the OpenShift Container Platform. Jenkins can be deployed on OpenShift by using the Samples Operator templates or certified Helm chart. For more information, see Configuring Jenkins images .

Commands:
18.4. Installing in Text Mode Text mode installation offers an interactive, non-graphical interface for installing Red Hat Enterprise Linux. This can be useful on systems with no graphical capabilities; however, you should always consider the available alternatives (an automated Kickstart installation or using the graphical user interface over VNC) before starting a text-based installation. Text mode is limited in the amount of choices you can make during the installation. Figure 18.1. Text Mode Installation Installation in text mode follows a pattern similar to the graphical installation: There is no single fixed progression; you can configure many settings in any order you want using the main status screen. Screens which have already been configured, either automatically or by you, are marked as [x] , and screens which require your attention before the installation can begin are marked with [!] . Available commands are displayed below the list of available options. Note When related background tasks are being run, certain menu items can be temporarily unavailable or display the Processing... label. To refresh to the current status of text menu items, use the r option at the text mode prompt. At the bottom of the screen in text mode, a green bar is displayed showing five menu options. These options represent different screens in the tmux terminal multiplexer; by default you start in screen 1, and you can use keyboard shortcuts to switch to other screens which contain logs and an interactive command prompt. For information about available screens and shortcuts to switch to them, see Section 18.2.1, "Accessing Consoles" . Limits of interactive text mode installation include: The installer will always use the English language and the US English keyboard layout. You can configure your language and keyboard settings, but these settings will only apply to the installed system, not to the installation. You cannot configure any advanced storage methods (LVM, software RAID, FCoE, zFCP and iSCSI). It is not possible to configure custom partitioning; you must use one of the automatic partitioning settings. You also cannot configure where the boot loader will be installed. You cannot select any package add-ons to be installed; they must be added after the installation finishes using the Yum package manager. To start a text mode installation, boot the installation with the inst.text boot option used in the parameter file ( generic.prm ). See Chapter 21, Parameter and Configuration Files on IBM Z for information about the parameter file.

Commands:
Chapter 23. subsystem 23.1. subsystem:info 23.1.1. Description Display information about subsystems 23.1.2. Syntax subsystem:info [options] [id] 23.1.3. Arguments Name Description id Subsystem names or ids 23.1.4. Options Name Description --help Display this help message --indent Indentation method 23.2. subsystem:install 23.2.1. Description Install a new subsystem 23.2.2. Syntax subsystem:install [options] [Subsystem to install the new subsystem into] [New subsystem url] 23.2.3. Arguments Name Description Subsystem to install the new subsystem into New subsystem url 23.2.4. Options Name Description --help Display this help message 23.3. subsystem:list 23.3.1. Description List all subsystems 23.3.2. Syntax subsystem:list [options] 23.3.3. Options Name Description --help Display this help message 23.4. subsystem:start 23.4.1. Description Start the specified subsystems 23.4.2. Syntax subsystem:start [options] [id] 23.4.3. Arguments Name Description id Subsystem names or ids 23.4.4. Options Name Description --help Display this help message 23.5. subsystem:stop 23.5.1. Description Stop the specified subsystems 23.5.2. Syntax subsystem:stop [options] [id] 23.5.3. Arguments Name Description id Subsystem names or ids 23.5.4. Options Name Description --help Display this help message 23.6. subsystem:uninstall 23.6.1. Description Uninstall the specified subsystems 23.6.2. Syntax subsystem:uninstall [options] [id] 23.6.3. Arguments Name Description id Subsystem names or ids 23.6.4. Options Name Description --help Display this help message

Commands: