mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Labels Labels make it possible to embed commands in to container images instead of adding them as options to the command line. These are usually docker commands with multiple options that are required to run a particular container, and they often include running the container as privileged. The options are handled on a container-by-container basis and can make the command very long and hard to remember. Labels are another way to provide this information to docker. Labels build on the metadata that is already available in Docker. This metadata is stored in a .json file that defines the container. Docker has a feature that lets you put name-value pairs into containers and labels build on the feature that permits name-value pairs to be inserted into containers. 3.1. Labels Example Labels simplify running long docker commands on the command-line. The example below will help you understand labels. Here, we create "run labels" that have a semantic meaning. Suppose that you want to run the Chrome browser with GPU acceleration and pulse audio. To do this, your container needs access to the GPU. That would be easy enough, but we must consider "composition". X11 and Window Manager work together: that is composition. The most efficient way for these two programs to work together is to create one big frame buffer to which all compositing programs write. This is handled with a very long command, for example: Let's break this down: -v /dev/dri:/dev/dri video card component -v /dev/snd:/dev/snd sound card component -v /dev/shm:/dev/shm shared memory shm shared memory -\u00adipc inter-process communication container:foo_bar means that this label refers to another running container called foo_bar . This links the running container foo_bar to the running container fedora_chrome . This argument shares the interprocess communication namespaces of the two containers and ensures that the two containers refer to the same objects and that each of the two containers uses the same names to refer to those objects. This is important because they will be communicating over /dev/shm . Shared memory is one way of providing inter-process communication. -e 'DISPLAY=:0' which X11 display the output should go to -u username this specifies the username rhel_chrome the name of the container google-chrome the command that the container will run

Commands:
sudo docker run -v /dev/dri:/dev/dri -v /dev/snd:/dev/snd -v /dev/shm:/shm -\u00adipc=container:foo_bar -\u00adprivileged -e 'DISPLAY=:0' -u username rhel_chrome google-chrome
Chapter 3. Introduction to the Identity Service (keystone) As a cloud administrator, you can manage projects, users, and roles. Projects within the Red Hat OpenStack Services on OpenShift (RHOSO) data plane are organizational units containing a collection of resources. You can assign OpenStack users to roles within those projects. Roles define the actions that those users can perform on the resources within a given project. Users can be assigned roles in multiple projects. Each RHOSO data plane deployment must include at least one user assigned to a role within a project. As a cloud administrator, a user can perform the following actions within OpenStack: Add, update, and delete projects and users. Assign users to one or more roles, and change or remove these assignments. Manage projects and users independently from each other. You can also configure user authentication with the Identity service (keystone)to control access to services and endpoints. 3.1. Authenticate with clouds.yaml Prerequisites The administrator has created a project for you and they have provided you with a clouds.yaml file for you to access the cloud. You have installed the python-openstackclient package. Note To execute openstack client commands on the cloud you must specify the name of the cloud detailed in your clouds.yaml file. You can specify the name of the cloud in one of two ways: Use the --os-cloud option with each command: Use this option if you access more than one cloud. Create an environment variable for the cloud name in your bashrc file:

Commands:
openstack flavor list --os-cloud <cloud_name>
`export OS_CLOUD=<cloud_name>`
Chapter 9. Asterisk Component Available as of Camel version 2.18 The asterisk: component allows you to work easily with an Asterisk PBX Server http://www.asterisk.org/ using asterisk-java This component help to interface with Asterisk Manager Interface Maven users will need to add the following dependency to their pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-asterisk</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> 9.1. URI format asterisk:name[?options] 9.2. Options The Asterisk component has no options. The Asterisk endpoint is configured using URI syntax: with the following path and query parameters: 9.2.1. Path Parameters (1 parameters): Name Description Default Type name Required Logical name String 9.2.2. Query Parameters (8 parameters): Name Description Default Type hostname (common) Required The hostname of the asterisk server String password (common) Required Login password String username (common) Required Login username String bridgeErrorHandler (consumer) Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. false boolean exceptionHandler (consumer) To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. ExceptionHandler exchangePattern (consumer) Sets the exchange pattern when the consumer creates an exchange. ExchangePattern action (producer) What action to perform such as getting queue status, sip peers or extension state. AsteriskAction synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean 9.3. Spring Boot Auto-Configuration The component supports 2 options, which are listed below. Name Description Default Type camel.component.asterisk.enabled Enable asterisk component true Boolean camel.component.asterisk.resolve-property-placeholders Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. true Boolean 9.4. Action Supported actions are: QUEUE_STATUS, Queue Status SIP_PEERS, List SIP Peers EXTENSION_STATE, Check Extension Status

Commands:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-asterisk</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
asterisk:name[?options]
asterisk:name
Appendix A. Appendix A.1. mallopt mallopt is a library call that allows a program to change the behavior of the malloc memory allocator. Example A.1. Allocator heuristics An allocator has heuristics to determine long versus short lived objects. For the former, it attempts to allocate with mmap . For the later, it attempts to allocate with sbrk . In order to override these heuristics, set M_MMAP_THRESHOLD . In multi-threaded applications, the allocator creates multiple arenas in response to lock contention in existing arenas. This can improve the performance significantly for some multi-threaded applications at the cost of an increase in memory usage. To keep this under control, limit the number of arenas that can be created by using the mallopt interface. The allocator has limits on the number of arenas it can create. For 32bit targets, it will create 2 * # core arenas; for 64bit targets, it will create 8 * # core arenas. mallopt allows the developer to override those limits. Example A.2. mallopt To ensure no more than eight arenas are created, issue the following library call: The first argument for mallopt can be: M_MXFAST M_TRIM_THRESHOLD M_TOP_PAD M_MMAP_THRESHOLD M_MMAP_MAX M_CHECK_ACTION M_PERTURB M_ARENA_TEST M_ARENA_MAX Specific definitions for the above can be found at http://www.makelinux.net/man/3/M/mallopt . malloc_trim malloc_trim is a library call that requests the allocator return any unused memory back to the operating system. This is normally automatic when an object is freed. However, in some cases when freeing small objects, glibc might not immediately release the memory back to the operating system. It does this so that the free memory can be used to satisfy upcoming memory allocation requests as it is expensive to allocate from and release memory back to the operating system. malloc_stats malloc_stats is used to dump information about the allocator's internal state to stderr . Using mallinfo is similar to this, but it places the state into a structure instead. Further Information More information on mallopt can be found at http://www.makelinux.net/man/3/M/mallopt and http://www.gnu.org/software/libc/manual/html_node/Malloc-Tunable-Parameters.html .

Commands:
mallopt (M_ARENA_MAX, 8);
Chapter 5. Fixed issues The issues fixed in AMQ Streams 1.7 are shown in the following table. For details of the issues fixed in Kafka 2.7.0, refer to the Kafka 2.7.0 Release Notes . Issue Number Description ENTMQST-1561 OpenSSL tasks should be executed on separate worker executor and not on the main thread ENTMQST-1607 Check the log.message.format.version and inter.broker.protocol.version from the brokers during upgrade ENTMQST-1631 Topic Operator sometimes renames KafkaTopics ENTMQST-1676 Simplify Kafka upgrades and downgrades ENTMQST-1914 Move to Java 11 language level ENTMQST-2030 If the bin/kafka-acls.sh utility is used to add or remove an ACL, the operation is successful but a warning is generated ENTMQST-2085 All KafkaTopic custom resources are deleted and recreated when restarting kafka and zookeeper at the same time ENTMQST-2184 Metrics reporter not able to produce metrics when Kafka min.insync.replicas is greater than 1 ENTMQST-2188 MirrorMaker: Enable synchronization of offsets to the consumer group on the target cluster ENTMQST-2269 kafka-configs.sh is deprecating --zookeeper option but does not provide alternative functionality to list configs for users ENTMQST-2295 Watching the wrong reconciliations for metrics in the Topic Operator ENTMQST-2311 Improve configuration of network policies ENTMQST-2335 Run the ConnectS2I deployment with tini init ENTMQST-2386 Adding or removing JBOD volumes not working as expected ENTMQST-2472 Replacing namespace in Prometheus operator bundle file produces invalid YAML ENTMQST-2480 Inconsistent use of CPU metric in Grafana dashboards ENTMQST-2483 KafkaConnect Build: Declarative management of connector plugins in Kafka Connect custom resource ENTMQST-2525 Add annotations to perform connector/task restart operations ENTMQST-2529 Kafka Exporter dashboard does not auto-select namespace and cluster name ENTMQST-2547 Network policies not properly configured when metrics ConfigMap is used ENTMQST-2548 User-certificate renewal never triggered when it expires independently on the CA ENTMQST-2550 Cruise Control Grafana dashboard presentation is affected when Cruise Control pod is rolled or deleted ENTMQST-2595 Topic Operator fails to create a topic when replica or partition count is decreased ENTMQST-2625 JMX configuration issues cause port already in use error ENTMQST-2636 OAuth NullPointerException when using 'keycloak' authorization with 'resource' permissions ENTMQST-2643 Use the ISO-8601 timestamp standard for Kafka resource status Table 5.1. Fixed common vulnerabilities and exposures (CVEs) Issue Number Title Description ENTMQST-2334 CVE-2020-25649 jackson-databind: FasterXML DOMDeserializer insecure entity expansion is vulnerable to XML external entity (XXE) [amq-st-1] A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. This flaw allows vulnerability to XML external entity (XXE) attacks. The highest threat from this vulnerability is data integrity.

Commands:
Chapter 3. Shenandoah garbage collector modes You can run Shenandoah in three different modes. Select a specific mode with the -XX:ShenandoahGCMode=<name> . The following list describes each Shenandoah mode: normal/satb (product, default) This mode runs a concurrent garbage collector (GC) with Snapshot-At-The-Beginning (SATB) marking. This marking mode does the similar work as G1, the default garbage collector for Red Hat build of OpenJDK 17. iu (experimental) This mode runs a concurrent GC with Incremental Update (IU) marking. It can reclaim unreachably memory more aggressively. This marking mode mirrors the SATB mode. This may make marking less conservative, especially around accessing weak references. passive (diagnostic) This mode runs Stop the World Event GCs. This mode is used for functional testing, but sometimes it is useful for bisecting performance anomalies with GC barriers, or to ascertain the actual live data size in the application.

Commands:
Appendix C. Revision History Revision History Revision 1-18 Tue 14 Mar 2017 Mirek Jahoda Version for 6.9 GA publication. Revision 1-14 Wed 4 May 2016 Robert Kratky Release of the Security Guide for Red Hat Enterprise Linux 6.8 Revision 1-12.4 Tue Dec 16 2014 Robert Kratky Update to sort order on the Red Hat Customer Portal. Revision 1-12.3 Mon Dec 01 2014 Robert Kratky Updates reflecting the POODLE vuln. Revision 1-12.0 Mon Oct 13 2014 Miroslav Svoboda Release of the Security Guide for Red Hat Enterprise Linux 6.6 Revision 1-9.9 Feb 21 2013 Martin Prpic Release of the Security Guide for Red Hat Enterprise Linux 6.4 Revision 1-8.25 Jun 20 2012 Martin Prpic Release of the Security Guide for Red Hat Enterprise Linux 6.3 Revision 1-7 Dec 6 2011 Martin Prpic Release of the Security Guide for Red Hat Enterprise Linux 6.2

Commands:
5.203. mysql-connector-java 5.203.1. RHBA-2012:0992 - mysql-connector-java bug fix and enhancement update An updated mysql-connector-java package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The mysql-connector-java package provides a native Java driver that converts JDBC (Java Database Connectivity) calls into the network protocol used by the MySQL database. It lets developers working with the Java programming language easily build programs and applets that interact with MySQL. The mysql-connector-java package has been upgraded to the latest upstream version, which provides a number of bug fixes and enhancements over the version. For a list of changes, refer to the MySQL Connector/J documentation . This update also adds "stub" implementations of methods required by the JDBC 4.1 API specification. Currently, these methods throw exceptions when called, but their presence is necessary for the driver to function properly in JDK 7 and later. This update also converts the driver from a GCJ build to a pure jar (noarch) build. (BZ# 816696 ) Users are advised to upgrade to this updated mysql-connector-java package, which resolves these issues and adds these enhancements.

Commands:
Chapter 4. Application Properties Configure your project with application.properties or application.yaml . # # Embedded Properties - Uncomment properties to use them. # # Enables embedded capabilities in your application. # Values are true (default) or false. #infinispan.embedded.enabled = # Sets the Spring state machine ID. #infinispan.embedded.machineId = # Sets the name of the embedded cluster. #infinispan.embedded.clusterName = # Specifies a XML configuration file that takes priority over the global # configuration bean or any configuration customizer. #infinispan.embedded.configXml = # # Server Properties - Uncomment properties to use them. # # Specifies a custom filename for Hot Rod client properties. #infinispan.remote.clientProperties = # Enables remote server connections. # Values are true (default) or false. #infinispan.remote.enabled = # Defines a comma-separated list of servers in this format: # `host1[:port],host2[:port]`. #infinispan.remote.server-list= # Sets a timeout value, in milliseconds, for socket connections. #infinispan.remote.socketTimeout = # Sets a timeout value for initializing connections with servers. #infinispan.remote.connectTimeout = # Sets the maximum number of attempts to connect to servers. #infinispan.remote.maxRetries = # Specifies the marshaller to use. #infinispan.remote.marshaller = # Adds your classes to the serialization allow list. #infinispan.remote.java-serial-allowlist=

Commands:
# Embedded Properties - Uncomment properties to use them. # Enables embedded capabilities in your application. Values are true (default) or false. #infinispan.embedded.enabled = Sets the Spring state machine ID. #infinispan.embedded.machineId = Sets the name of the embedded cluster. #infinispan.embedded.clusterName = Specifies a XML configuration file that takes priority over the global configuration bean or any configuration customizer. #infinispan.embedded.configXml = # Server Properties - Uncomment properties to use them. # Specifies a custom filename for Hot Rod client properties. #infinispan.remote.clientProperties = Enables remote server connections. Values are true (default) or false. #infinispan.remote.enabled = Defines a comma-separated list of servers in this format: `host1[:port],host2[:port]`. #infinispan.remote.server-list= Sets a timeout value, in milliseconds, for socket connections. #infinispan.remote.socketTimeout = Sets a timeout value for initializing connections with servers. #infinispan.remote.connectTimeout = Sets the maximum number of attempts to connect to servers. #infinispan.remote.maxRetries = Specifies the marshaller to use. #infinispan.remote.marshaller = Adds your classes to the serialization allow list. #infinispan.remote.java-serial-allowlist=
1.2.6. Committing Changes To share your changes with others and commit them to a Subversion repository, change to the directory with its working copy and run the following command: svn commit [ -m " commit message " ] Note that unless you specify the commit message on the command line, Subversion opens an external text editor for you to write it. For information on how to determine which editor to start, see Section 1.2.1, "Installing and Configuring Subversion" . Example 1.12. Committing changes to a Subversion repository Imagine that the directory with your working copy of a Subversion repository has the following contents: In this working copy, ChangeLog is scheduled for addition to the Subversion repository, Makefile already is under revision control and contains local changes, and the TODO file, which is also under revision control, has been scheduled for removal and is no longer present in the working copy. Additionally, the LICENSE file has been renamed to COPYING . To commit these changes to the Subversion repository, type:

Commands:
project]USD ls AUTHORS ChangeLog COPYING doc INSTALL Makefile README src
project]USD svn commit -m "Updated the makefile." Adding COPYING Adding ChangeLog Deleting LICENSE Sending Makefile Deleting TODO Transmitting file data .. Committed revision 2.
8.38. cryptsetup-luks 8.38.1. RHEA-2014:1593 - cryptsetup-luks enhancement update Updated cryptsetup-luks packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The cryptsetup-luks packages provide a utility which allows users to set up encrypted devices with the Device Mapper and the dm-crypt target. Enhancement BZ# 1009707 FIPS products are now defined by the presence of the dracut-fips package in the system. During the initialization of a library, a cryptographic module is supposed to determine if the library is a FIPS product to reduce the amount of required integrity tests. For this purpose, a new constructor function has been added to the cryptsetup-libs library. The constructor detects if the /etc/system-fips file, which is a part of dracut-fips, exists in the system, and determines if a FIPS integrity test is needed. Users of cryptsetup-luks are advised to upgrade to these updated packages, which add this enhancement.

Commands:
Appendix B. Applying custom configuration to Red Hat Satellite When you install and configure Satellite for the first time by using satellite-installer , you can specify that the DNS and DHCP configuration files are not to be managed by Puppet by using the installer flags --foreman-proxy-dns-managed=false and --foreman-proxy-dhcp-managed=false . If these flags are not specified during the initial installer run, rerunning of the installer overwrites all manual changes, for example, rerun for upgrade purposes. If changes are overwritten, you must run the restore procedure to restore the manual changes. For more information, see Restoring Manual Changes Overwritten by a Puppet Run . To view all installer flags available for custom configuration, run satellite-installer --scenario satellite --full-help . Some Puppet classes are not exposed to the Satellite installer. To manage them manually and prevent the installer from overwriting their values, specify the configuration values by adding entries to configuration file /etc/foreman-installer/custom-hiera.yaml . This configuration file is in YAML format, consisting of one entry per line in the format of <puppet class>::<parameter name>: <value> . Configuration values specified in this file persist across installer reruns. Common examples include: For Apache, to set the ServerTokens directive to return only the product name: To turn off the Apache server signature entirely: The Puppet modules for the Satellite installer are stored under /usr/share/foreman-installer/modules . Check the .pp files (for example: moduleName /manifests/ example .pp) to look up the classes, parameters, and values. Alternatively, use the grep command to do keyword searches. Setting some values may have unintended consequences that affect the performance or functionality of Red Hat Satellite. Consider the impact of the changes before you apply them, and test the changes in a non-production environment first. If you do not have a non-production Satellite environment, run the Satellite installer with the --noop and --verbose options. If your changes cause problems, remove the offending lines from custom-hiera.yaml and rerun the Satellite installer. If you have any specific questions about whether a particular value is safe to alter, contact Red Hat support.

Commands:
apache::server_tokens: Prod
apache::server_signature: Off