mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. The Cache API The Cache interface provides simple methods for the addition, retrieval and removal of entries, which includes atomic mechanisms exposed by the JDK's ConcurrentMap interface. How entries are stored depends on the cache mode in use. For example, an entry may be replicated to a remote node or an entry may be looked up in a cache store. The Cache API is used in the same manner as the JDK Map API for basic tasks. This simplifies the process of migrating from Map-based, simple in-memory caches to Red Hat JBoss Data Grid's cache. Note This API is not available in JBoss Data Grid's Remote Client-Server Mode Report a bug 1.1. Using the ConfigurationBuilder API to Configure the Cache API Red Hat JBoss Data Grid uses a ConfigurationBuilder API to configure caches. Caches are configured programmatically using the ConfigurationBuilder helper object. The following is an example of a synchronously replicated cache configured programmatically using the ConfigurationBuilder API : Procedure 1.1. Programmatic Cache Configuration In the first line of the configuration, a new cache configuration object (named c ) is created using the ConfigurationBuilder . Configuration c is assigned the default values for all cache configuration options except the cache mode, which is overridden and set to synchronous replication ( REPL_SYNC ). In the second line of the configuration, a new variable (of type String ) is created and assigned the value repl . In the third line of the configuration, the cache manager is used to define a named cache configuration for itself. This named cache configuration is called repl and its configuration is based on the configuration provided for cache configuration c in the first line. In the fourth line of the configuration, the cache manager is used to obtain a reference to the unique instance of the repl that is held by the cache manager. This cache instance is now ready to be used to perform operations to store and retrieve data. Note JBoss EAP includes its own underlying JMX. This can cause a collision when using the sample code with JBoss EAP and display an error such as org.infinispan.jmx.JmxDomainConflictException: Domain already registered org.infinispan . To avoid this, configure global configuration as follows: Report a bug

Commands:
Configuration c = new ConfigurationBuilder().clustering().cacheMode(CacheMode.REPL_SYNC).build(); String newCacheName = "repl"; manager.defineConfiguration(newCacheName, c); Cache<String, String> cache = manager.getCache(newCacheName);
GlobalConfiguration glob = new GlobalConfigurationBuilder() .clusteredDefault() .globalJmxStatistics() .allowDuplicateDomains(true) .enable() .build();
4.88. ibus-anthy 4.88.1. RHBA-2011:1208 - ibus-anthy bug fix update An updated ibus-anthy package that fixes a bug is now available for Red Hat Enterprise Linux 6. The ibus-anthy package contains the Anthy engine, which provides an input method for Japanese based on the IBus (Intelligent Input Bus) platform. Bug Fix BZ# 661597 Previously, when changing the Candidate Window Page Size setting of Other under the General tab, the im-chooser application had to be restarted for the changes to take effect. This problem has been fixed and the changes made to Candidate Window Page Size now apply immediately. All users of ibus-anthy are advised to upgrade to this updated package, which resolves this bug.

Commands:
Chapter 62. KafkaExporterTemplate schema reference Used in: KafkaExporterSpec Property Description deployment Template for Kafka Exporter Deployment . DeploymentTemplate pod Template for Kafka Exporter Pods . PodTemplate service The service property has been deprecated. The Kafka Exporter service has been removed. Template for Kafka Exporter Service . ResourceTemplate container Template for the Kafka Exporter container. ContainerTemplate serviceAccount Template for the Kafka Exporter service account. ResourceTemplate

Commands:
22.8. JBoss Operations Network Plug-in Quickstart For testing or demonstrative purposes with a single JBoss Operations Network agent, upload the plug-in to the server then type "plugins update" at the agent command line to force a retrieval of the latest plugins from the server. 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
Chapter 5. Migrating from synchronization to trust automatically by using ipa-winsync-migrate In RHEL 8, the synchronization approach to integrating RHEL systems into Active Directory (AD) indirectly is deprecated. Red Hat recommends migrating to the approach based on a trust between Identity Management (IdM) and AD instead. This chapter describes how to migrate from synchronization to trust automatically, by using the ipa-winsync-migrate utility. 5.1. Automatic migration from synchronization to trust by using ipa-winsync-migrate The ipa-winsync-migrate utility migrates all synchronized users from an AD forest, while preserving the existing configuration in the Winsync environment and transferring it into the AD trust. For each AD user created by the Winsync agreement, ipa-winsync-migrate creates an ID override in the Default Trust View. After the migration completes: The ID overrides for the AD users have the following attributes copied from the original entry in Winsync: Login name ( uid ) UID number ( uidnumber ) GID number ( gidnumber ) Home directory ( homedirectory ) GECOS entry ( gecos ) The user accounts in the AD trust keep their original configuration in IdM, which includes: POSIX attributes User groups Role-based access control rules Host-based access control rules SELinux membership sudo rules The new AD users are added as members of an external IdM group. The original Winsync replication agreement, the original synchronized user accounts, and all local copies of the user accounts are removed. Additional resources How the Default Trust View works 5.2. Migrating from synchronization to trust by using ipa-winsync-migrate Prerequisites On RHEL 7, you configured synchronisation between RHEL Identity Management (IdM) and AD. Procedure Back up your IdM setup using the ipa-backup utility. See Backing up and restoring IdM . NOTE The migration affects a significant part of the IdM configuration and many user accounts. Creating a backup enables you to restore your original setup if necessary. Create a trust with the synchronized domain. See For details, see Installing trust between IdM and AD . Run ipa-winsync-migrate and specify the AD realm and the host name of the AD domain controller: If a conflict occurs in the overrides created by ipa-winsync-migrate , information about the conflict is displayed, but the migration continues. Uninstall the Password Sync service from the AD server. This removes the synchronization agreement from the AD domain controllers. Additional resources ipa-winsync-migrate (1) Backing up and restoring IdM servers using Ansible playbooks

Commands:
ipa-winsync-migrate --realm example.com --server ad.example.com
7.166. openscap 7.166.1. RHBA-2013:0362 - openscap bug fix and enhancement update Updated openscap packages that fix various bugs and add several enhancements are now available for Red Hat Enterprise Linux 6. The openscap packages provide OpenSCAP, which is a set of open source libraries for the integration of the Security Content Automation Protocol (SCAP). SCAP is a line of standards that provide a standard language for the expression of Computer Network Defense (CND) related information. Note The openscap packages have been upgraded to upstream version 0.9.2, which provides a number of bug fixes and enhancements over the version. (BZ# 829349 ) All users of openscap are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 4. Setting up an authentication method for RHOSP The high availability fence agents and resource agents support three authentication methods for communicating with RHOSP: Authentication with a clouds.yaml configuration file Authentication with an OpenRC environment script Authentication with a username and password through Pacemaker After determining the authentication method to use for the cluster, specify the appropriate authentication parameters when creating a fencing or cluster resource. 4.1. Authenticating with RHOSP by using a clouds.yaml file The procedures in this document that use a a clouds.yaml file for authentication use the clouds.yaml file shown in this procedure. Those procedures specify ha-example for the cloud= parameter , as defined in this file. Procedure On each node that will be part of your cluster, create a clouds.yaml file, as in the following example. For information about creating a clouds.yaml file, see Users and Identity Management Guide . Test whether authentication is successful and you have access to the RHOSP API with the following basic RHOSP command, substituting the name of the cloud you specified in the clouds.yaml file you created for ha-example . If this command does not display a server list, contact your RHOSP administrator. Specify the cloud parameter when creating a cluster resource or a fencing resource. 4.2. Authenticating with RHOSP by using an OpenRC environment script To use an OpenRC environment script to authenticate with RHOSP, perform the following steps. Procedure On each node that will be part of your cluster, configure an OpenRC environment script. For information about creating an OpenRC environment script, see Set environment variables using the OpenStack RC file . Test whether authentication is successful and you have access to the RHOSP API with the following basic RHOSP command. If this command does not display a server list, contact your RHOSP administrator. Specify the openrc parameter when creating a cluster resource or a fencing resource. 4.3. Authenticating with RHOSP by means of a username and password To authenticate with RHOSP by means of a username and password, specify the username , password , and auth_url parameters for a cluster resource or a fencing resource when you create the resource. Additional authentication parameters may be required, depending on the RHOSP configuration. The RHOSP administrator provides the authentication parameters to use.

Commands:
cat .config/openstack/clouds.yaml clouds: ha-example: auth: auth_url: https://<ip_address>:13000/ project_name: rainbow username: unicorns password: <password> user_domain_name: Default project_domain_name: Default <. . . additional options . . .> region_name: regionOne verify: False
openstack --os-cloud=ha-example server list
openstack server list
Chapter 3. User tasks 3.1. Creating applications from installed Operators This guide walks developers through an example of creating applications from an installed Operator using the Red Hat OpenShift Service on AWS web console. 3.1.1. Creating an etcd cluster using an Operator This procedure walks through creating a new etcd cluster using the etcd Operator, managed by Operator Lifecycle Manager (OLM). Prerequisites Access to an Red Hat OpenShift Service on AWS cluster. The etcd Operator already installed cluster-wide by an administrator. Procedure Create a new project in the Red Hat OpenShift Service on AWS web console for this procedure. This example uses a project called my-etcd . Navigate to the Operators Installed Operators page. The Operators that have been installed to the cluster by the dedicated-admin and are available for use are shown here as a list of cluster service versions (CSVs). CSVs are used to launch and manage the software provided by the Operator. Tip You can get this list from the CLI using: USD oc get csv On the Installed Operators page, click the etcd Operator to view more details and available actions. As shown under Provided APIs , this Operator makes available three new resource types, including one for an etcd Cluster (the EtcdCluster resource). These objects work similar to the built-in native Kubernetes ones, such as Deployment or ReplicaSet , but contain logic specific to managing etcd. Create a new etcd cluster: In the etcd Cluster API box, click Create instance . The page allows you to make any modifications to the minimal starting template of an EtcdCluster object, such as the size of the cluster. For now, click Create to finalize. This triggers the Operator to start up the pods, services, and other components of the new etcd cluster. Click the example etcd cluster, then click the Resources tab to see that your project now contains a number of resources created and configured automatically by the Operator. Verify that a Kubernetes service has been created that allows you to access the database from other pods in your project. All users with the edit role in a given project can create, manage, and delete application instances (an etcd cluster, in this example) managed by Operators that have already been created in the project, in a self-service manner, just like a cloud service. If you want to enable additional users with this ability, project administrators can add the role using the following command: USD oc policy add-role-to-user edit <user> -n <target_project> You now have an etcd cluster that will react to failures and rebalance data as pods become unhealthy or are migrated between nodes in the cluster. Most importantly, dedicated-admins or developers with proper access can now easily use the database with their applications.

Commands:
oc get csv
oc policy add-role-to-user edit <user> -n <target_project>
10.3.3. Trouble with Partition Tables If you receive an error after the Disk Partitioning Setup ( Section 9.13, "Disk Partitioning Setup" ) phase of the installation saying something similar to The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive. you may not have a partition table on that drive or the partition table on the drive may not be recognizable by the partitioning software used in the installation program. Users who have used programs such as EZ-BIOS have experienced similar problems, causing data to be lost (assuming the data was not backed up before the installation began) that could not be recovered. No matter what type of installation you are performing, backups of the existing data on your systems should always be made.

Commands:
Chapter 6. Upgrading Hosts to Major Red Hat Enterprise Linux Release You can use a job template to upgrade your Red Hat Enterprise Linux hosts to the major release. Below upgrade paths are possible: Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 Prerequisites Ensure that your Red Hat Enterprise Linux hosts meet the requirements for the upgrade. For Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 upgrade, see Planning an upgrade in Upgrading from RHEL 7 to RHEL 8 . For Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 upgrade, see Planning an upgrade to RHEL 9 in Upgrading from RHEL 8 to RHEL 9 . Prepare your Red Hat Enterprise Linux hosts for the upgrade. For Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 upgrade, see Preparing a RHEL 7 system for the upgrade in Upgrading from RHEL 7 to RHEL 8 . For Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 upgrade, see Preparing a RHEL 8 system for the upgrade in Upgrading from RHEL 8 to RHEL 9 . Enable remote execution feature on Satellite. For more information, see Chapter 12, Configuring and Setting Up Remote Jobs . Distribute Satellite SSH keys to the hosts that you want to upgrade. For more information, see Section 12.8, "Distributing SSH Keys for Remote Execution" . Procedure On Satellite, enable the Leapp plugin: In the Satellite web UI, navigate to Hosts > All Hosts . Select the hosts that you want to upgrade to the major Red Hat Enterprise Linux version. In the upper right of the Hosts window, from the Select Action list, select Preupgrade check with Leapp . Click Submit to start the pre-upgrade check. When the check is finished, click the Leapp preupgrade report tab to see if Leapp has found any issues on your hosts. Issues that have the Inhibitor flag are considered crucial and are likely to break the upgrade procedure. Issues that have the Has Remediation flag contain remediation that can help you fix the issue. Click an issue that is flagged as Has Remediation to expand it. If the issue contains a remediation Command , you can fix it directly from Satellite using remote execution. Select the issue. If the issue contains only a remediation Hint , use the hint to fix the issue on the host manually. Repeat this step for other issues. After you selected any issues with remediation commands, click Fix Selected and submit the job. After the issues are fixed, click the Rerun button, and then click Submit to run the pre-upgrade check again to verify that the hosts you are upgrading do not have any issues and are ready to be upgraded. If the pre-upgrade check verifies that the hosts do not have any issues, click the Run Upgrade button and click Submit to start the upgrade.

Commands:
satellite-installer --enable-foreman-plugin-leapp
Chapter 9. Ceph File System snapshots As a storage administrator, you can take a point-in-time snapshot of a Ceph File System (CephFS) directory. CephFS snapshots are asynchronous, and you can choose which directory snapshots are created in. 9.1. Prerequisites A running, and healthy Red Hat Ceph Storage cluster. Deployment of a Ceph File System. 9.2. Ceph File System snapshots The Ceph File System (CephFS) snapshotting feature is enabled by default on new Ceph File Systems, but must be manually enabled on existing Ceph File Systems. CephFS snapshots create an immutable, point-in-time view of a Ceph File System. CephFS snapshots are asynchronous and are kept in a special hidden directory in the CephFS directory named .snap . You can specify snapshot creation for any directory within a Ceph File System. When specifying a directory, the snapshot also includes all the subdirectories beneath it. Warning Each Ceph Metadata Server (MDS) cluster allocates the snap identifiers independently. Using snapshots for multiple Ceph File Systems that are sharing a single pool causes snapshot collisions, and results in missing file data. Additional Resources See the Creating a snapshot for a Ceph File System section in the Red Hat Ceph Storage File System Guide for more details. See the Creating a snapshot schedule for a Ceph File System section in the Red Hat Ceph Storage File System Guide for more details. 9.3. Creating a snapshot for a Ceph File System You can create an immutable, point-in-time view of a Ceph File System (CephFS) by creating a snapshot. Note For a new Ceph File System, snapshots are enabled by default. Prerequisites A running, and healthy Red Hat Ceph Storage cluster. Deployment of a Ceph File System. Root-level access to a Ceph Metadata Server (MDS) node. Procedure Log into the Cephadm shell: Example For existing Ceph File Systems, enable the snapshotting feature: Syntax Example Create a new snapshot subdirectory under the .snap directory: Syntax Example This example creates the new-snaps subdirectory, and this informs the Ceph Metadata Server (MDS) to start making snapshots. To delete snapshots: Syntax Example Important Attempting to delete root-level snapshots, which might contain underlying snapshots, will fail. Additional Resources See the Ceph File System snapshot schedules section in the Red Hat Ceph Storage File System Guide for more details. See the Ceph File System snapshots section in the Red Hat Ceph Storage File System Guide for more details. 9.4. Additional Resources See the Deployment of the Ceph File System section in the Red Hat Ceph Storage File System Guide .

Commands:
cephadm shell
ceph fs set FILE_SYSTEM_NAME allow_new_snaps true
ceph fs set cephfs01 allow_new_snaps true
mkdir NEW_DIRECTORY_PATH
mkdir /.snap/new-snaps
rmdir NEW_DIRECTORY_PATH
rmdir /.snap/new-snaps
Chapter 33. extension This chapter describes the commands under the extension command. 33.1. extension list List API extensions Usage: Table 33.1. Optional Arguments Value Summary -h, --help Show this help message and exit --compute List extensions for the compute api --identity List extensions for the identity api --network List extensions for the network api --volume List extensions for the block storage api --long List additional fields in output Table 33.2. Output Formatters Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated Table 33.3. CSV Formatter Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 33.4. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 33.5. Table Formatter Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show. 33.2. extension show Show API extension Usage: Table 33.6. Positional Arguments Value Summary <extension> Extension to display. currently, only network extensions are supported. (Name or Alias) Table 33.7. Optional Arguments Value Summary -h, --help Show this help message and exit Table 33.8. Output Formatters Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 33.9. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 33.10. Shell Formatter Value Summary --prefix PREFIX Add a prefix to all variable names Table 33.11. Table Formatter Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack extension list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--compute] [--identity] [--network] [--volume] [--long]
openstack extension show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] <extension>
Chapter 84. ExternalConfigurationEnv schema reference Used in: ExternalConfiguration Property Property type Description name string Name of the environment variable which will be passed to the Kafka Connect pods. The name of the environment variable cannot start with KAFKA_ or STRIMZI_ . valueFrom ExternalConfigurationEnvVarSource Value of the environment variable which will be passed to the Kafka Connect pods. It can be passed either as a reference to Secret or ConfigMap field. The field has to specify exactly one Secret or ConfigMap.

Commands: