mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Networking Operators overview OpenShift Container Platform supports multiple types of networking Operators. You can manage the cluster networking using these networking Operators. 3.1. Cluster Network Operator The Cluster Network Operator (CNO) deploys and manages the cluster network components in an OpenShift Container Platform cluster. This includes deployment of the Container Network Interface (CNI) default network provider plug-in selected for the cluster during installation. For more information, see Cluster Network Operator in OpenShift Container Platform . 3.2. DNS Operator The DNS Operator deploys and manages CoreDNS to provide a name resolution service to pods. This enables DNS-based Kubernetes Service discovery in OpenShift Container Platform. For more information, see DNS Operator in OpenShift Container Platform . 3.3. Ingress Operator When you create your OpenShift Container Platform cluster, pods and services running on the cluster are each allocated IP addresses. The IP addresses are accessible to other pods and services running nearby but are not accessible to external clients. The Ingress Operator implements the Ingress Controller API and is responsible for enabling external access to OpenShift Container Platform cluster services. For more information, see Ingress Operator in OpenShift Container Platform .

Commands:
A.2. Authentication Methods Anonymous SASL Mechanism ( RFC 4505 ) Not supported. Note that RFC 4512 does not require the ANONYMOUS SASL mechanism. However, Directory Server support LDAP anonymous binds. External SASL Mechanism ( RFC 4422 ) Supported. Plain SASL Mechanism ( RFC 4616 ) Not supported. Note that RFC 4512 does not require the PLAIN SASL mechanism. However, Directory Server support LDAP anonymous binds. SecurID SASL Mechanism ( RFC 2808 ) Not supported. However if a Cyrus SASL plug-in exists, Directory Server is able to use it. Kerberos V5 (GSSAPI) SASL Mechanism ( RFC 4752 ) Supported. CRAM-MD5 SASL Mechanism ( RFC 2195 ) Supported. Digest-MD5 SASL Mechanism ( RFC 2831 ) Supported. One-time Password SASL Mechanism ( RFC 2444 ) Not supported. However if a Cyrus SASL plug-in exists, Directory Server is able to use it.

Commands:
Chapter 8. Sources The updated Red Hat Ceph Storage source code packages are available at the following location: For Red Hat Enterprise Linux 8: http://ftp.redhat.com/redhat/linux/enterprise/8Base/en/RHCEPH/SRPMS/ For Red Hat Enterprise Linux 9: http://ftp.redhat.com/redhat/linux/enterprise/9Base/en/RHCEPH/SRPMS/

Commands:
Chapter 55. Installation and Booting Certain RPM packages are not available on binary DVDs The virt-p2v RPM, syslinux-tftpboot , LibreOffice , and KDE language packages are not available on Red Hat Enterprise Linux binary DVDs due to the limited size of a single-layered DVD. The packages are still consumable by Red Hat Subscription Management and Red Hat Network by enabling the relevant updates after Anaconda installation. The packages can also be downloaded from https://access.redhat.com/downloads . In addition, the syslinux-tftpboot package has been moved from the Optional channel to the Base channel (Server variant) and it is now also available for the IBM POWER, little endian architecture. (BZ# 1611665 , BZ#1592748, BZ#1616396) The content location detection code is not working on Red Hat Virtualization Hosts Red Hat Virtualization Hosts cannot select the hardening profile from locally-installed content. To work around this problem, use the oscap-anaconda-addon package to fetch the Red Hat Enterprise Linux datastream file from a URL. 1. Upload the ssg-rhel7-ds.xml datastream file from the Red Hat Enterprise Linux 7 scap-security-guide package to your network so it can be discovered by Anaconda. To do so: a) Use Python to set up a web server in a directory that contains the ssg-rhel7-ds.xml datastream file and listens on port 8000. Example: python2 -m SimpleHTTPServer, or python3 -m http.server. or, b) Upload the ssg-rhel7-ds.xml datastream file to a HTTPS or FTP Server. 2. In the Security Policy window of Anaconda's Graphical User Interface, click Change Content and enter the URL that points to the ssg-rhel7-ds.xml datastream file, for example: http://gateway:8000/ssg-rhel7-ds.xml or ftp://my-ftp-server/ssg-rhel7-ds.xml. The ssg-rhel7-ds.xml datastream file is now available and Red Hat Virtualization Hosts can select the hardening profile. (BZ# 1636847 ) Composer can not create live ISO system images Because of a dependency resolution issue, tools for building live ISO images are not recognized by Composer at run time. As a consequence, Composer fails to build live ISO images and users can not create this type of system image. Composer is available as a Technology Preview. (BZ#1642156) NVDIMM commands are not added to kickstart script file anaconda-ks.cfg after installation The installer creates a kickstart script equivalent to the configuration used for installation of the system. This script is stored in the file /root/anaconda-ks.cfg . However, when the interactive graphical user interface is used for installation, the recently added nvdimm commands used for configuring Non-Volatile Dual In-line Memory (NVDIMM) devices are not added to this file. To create a kickstart script for reproduction of the installation, users must note the settings for NVDIMM devices and add the missing commands to the file manually. (BZ# 1620109 )

Commands:
8.158. pykickstart 8.158.1. RHBA-2013:1629 - pykickstart bug fix and enhancement update An updated pykickstart package that fixes several bugs and adds one enhancement is now available for Red Hat Enterprise Linux 6. The pykickstart package contains a python library for manipulating kickstart files. Bug Fixes BZ# 886010 When combining the autopart command with other kickstart partitioning commands in one kickstart file, installation proceeded unexpectedly with errors. The underlying source code has been modified so that the user is notified and installation is aborted with a parse error if the kickstart file contains invalid partitioning. BZ# 924579 When a kickstart file specified two logical volumes with the same name, installation failed with this inappropriate error message: AttributeError: 'LogVolData' object has no attribute 'device' With this update, duplicate names are detected correctly and the appropriate error message is displayed. BZ# 966183 When running a kickstart file that contained the "network" command with the "--ipv6" option specified, installation could terminate unexpectedly with the following message: TypeError: not all arguments converted during string formatting This update applies a patch to fix this bug and kickstart files work as expected in the described scenario. Enhancement BZ# 978252 This enhancement adds the ability to specify the "--ipv6gateway" option for the "network" command in kickstart files. As a result, both IPv4 and IPv6 default gateways can be specified for a network device configuration using the "network" command. Users of pykickstart are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
Preface The Red Hat Enterprise Linux 6.7 Technical Notes list and document the changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications between minor release Red Hat Enterprise Linux 6.6 and minor release Red Hat Enterprise Linux 6.7. For system administrators and others planning Red Hat Enterprise Linux 6.7 upgrades and deployments, the Technical Notes provide a single, organized record of the bugs fixed in, features added to, and Technology Previews included with this new release of Red Hat Enterprise Linux. For auditors and compliance officers, the Red Hat Enterprise Linux 6.7 Technical Notes provide a single, organized source for change tracking and compliance testing. For every user, the Red Hat Enterprise Linux 6.7 Technical Notes provide details of what has changed in this new release. Note The Package Manifest is available as a separate document.

Commands:
Part III. Managing and monitoring business processes in Business Central As a process administrator, you can use Business Central in Red Hat Process Automation Manager to manage and monitor process instances and tasks running on a number of projects. From Business Central you can start a new process instance, verify the state of all process instances, and abort processes. You can view the list of jobs and tasks associated with your processes, as well as understand and communicate any process errors. Prerequisites Red Hat JBoss Enterprise Application Platform 7.4 is installed. For more information, see Red Hat JBoss Enterprise Application Platform 7.4 Installation Guide . Red Hat Process Automation Manager is installed. For more information, see Planning a Red Hat Process Automation Manager installation . Red Hat Process Automation Manager is running and you can log in to Business Central with the process-admin role. For more information, see Planning a Red Hat Process Automation Manager installation .

Commands:
7.8. Using NSCD with SSSD SSSD is not designed to be used with the NSCD daemon. Even though SSSD does not directly conflict with NSCD, using both services can result in unexpected behavior, especially with how long entries are cached. The most common evidence of a problem is conflicts with NFS. When using Network Manager to manage network connections, it may take several minutes for the network interface to come up. During this time, various services attempt to start. If these services start before the network is up and the DNS servers are available, these services fail to identify the forward or reverse DNS entries they need. These services will read an incorrect or possibly empty resolv.conf file. This file is typically only read once, and so any changes made to this file are not automatically applied. This can cause NFS locking to fail on the machine where the NSCD service is running, unless that service is manually restarted. To avoid potential conflicts and performance issues, do not run NSCD and SSSD services simultaneously on the same system.

Commands:
Chapter 9. availability This chapter describes the commands under the availability command. 9.1. availability zone list List availability zones and their status Usage: Table 9.1. Command arguments Value Summary -h, --help Show this help message and exit --compute List compute availability zones --network List network availability zones --volume List volume availability zones --long List additional fields in output Table 9.2. Output formatter options 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 to show multiple columns --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 --sort-ascending Sort the column(s) in ascending order --sort-descending Sort the column(s) in descending order Table 9.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 9.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 9.5. Table formatter options 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 availability zone 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] [--sort-ascending | --sort-descending] [--compute] [--network] [--volume] [--long]
Chapter 1. Recommendations for Large Deployments Use the following undercloud and overcloud recommendations, specifications, and configuration for deploying a large Red Hat OpenStack Platform (RHOSP) environment. RHOSP 16.2 deployments that include more than 100 overcloud nodes are considered large environments. Red Hat has tested and validated optimum performance on a large scale environment of 700 overcloud nodes using RHOSP 16.2 without using minion. For DCN-based deployments, the number of nodes from the central and edge sites can be very high. For recommendations about DCN deployments, contact Red Hat Global Support Services.

Commands:
Chapter 2. Admin REST API Red Hat Single Sign-On comes with a fully functional Admin REST API with all features provided by the Admin Console. To invoke the API you need to obtain an access token with the appropriate permissions. The required permissions are described in the Server Administration Guide. You can obtain a token by enabling authentication for your application using Red Hat Single Sign-On; see the Securing Applications and Services Guide. You can also use direct access grant to obtain an access token. 2.1. Examples of using CURL 2.1.1. Authenticating with a username and password Procedure Obtain an access token for the user in the realm master with username admin and password password : curl \ -d "client_id=admin-cli" \ -d "username=admin" \ -d "password=password" \ -d "grant_type=password" \ "http://localhost:8080/auth/realms/master/protocol/openid-connect/token" Note By default this token expires in 1 minute The result will be a JSON document. Invoke the API you need by extracting the value of the access_token property. Invoke the API by including the value in the Authorization header of requests to the API. The following example shows how to get the details of the master realm: curl \ -H "Authorization: bearer eyJhbGciOiJSUz..." \ "http://localhost:8080/auth/admin/realms/master" 2.1.2. Authenticating with a service account To authenticate against the Admin REST API using a client_id and a client_secret , perform this procedure. Procedure Make sure the client is configured as follows: client_id is a confidential client that belongs to the realm master client_id has Service Accounts Enabled option enabled client_id has a custom "Audience" mapper Included Client Audience: security-admin-console Check that client_id has the role 'admin' assigned in the "Service Account Roles" tab. curl \ -d "client_id=<YOUR_CLIENT_ID>" \ -d "client_secret=<YOUR_CLIENT_SECRET>" \ -d "grant_type=client_credentials" \ "http://localhost:8080/auth/realms/master/protocol/openid-connect/token" 2.2. Additional resources Server Administration Guide Securing Applications and Services Guide API Documentation

Commands:
curl -d "client_id=admin-cli" -d "username=admin" -d "password=password" -d "grant_type=password" "http://localhost:8080/auth/realms/master/protocol/openid-connect/token"
curl -H "Authorization: bearer eyJhbGciOiJSUz..." "http://localhost:8080/auth/admin/realms/master"
curl -d "client_id=<YOUR_CLIENT_ID>" -d "client_secret=<YOUR_CLIENT_SECRET>" -d "grant_type=client_credentials" "http://localhost:8080/auth/realms/master/protocol/openid-connect/token"
Chapter 197. Kubernetes ConfigMap Component Available as of Camel version 2.17 The Kubernetes ConfigMap component is one of Kubernetes Components which provides a producer to execute kubernetes ConfigMap operations. 197.1. Component Options The Kubernetes ConfigMap component has no options. 197.2. Endpoint Options The Kubernetes ConfigMap endpoint is configured using URI syntax: with the following path and query parameters: 197.2.1. Path Parameters (1 parameters): Name Description Default Type masterUrl Required Kubernetes API server URL String 197.2.2. Query Parameters (20 parameters): Name Description Default Type apiVersion (producer) The Kubernetes API Version to use String dnsDomain (producer) The dns domain, used for ServiceCall EIP String kubernetesClient (producer) Default KubernetesClient to use if provided KubernetesClient operation (producer) Producer operation to do on Kubernetes String portName (producer) The port name, used for ServiceCall EIP String portProtocol (producer) The port protocol, used for ServiceCall EIP tcp String connectionTimeout (advanced) Connection timeout in milliseconds to use when making requests to the Kubernetes API server. Integer synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean caCertData (security) The CA Cert Data String caCertFile (security) The CA Cert File String clientCertData (security) The Client Cert Data String clientCertFile (security) The Client Cert File String clientKeyAlgo (security) The Key Algorithm used by the client String clientKeyData (security) The Client Key data String clientKeyFile (security) The Client Key file String clientKeyPassphrase (security) The Client Key Passphrase String oauthToken (security) The Auth Token String password (security) Password to connect to Kubernetes String trustCerts (security) Define if the certs we used are trusted anyway or not Boolean username (security) Username to connect to Kubernetes String 197.3. Spring Boot Auto-Configuration The component supports 2 options, which are listed below. Name Description Default Type camel.component.kubernetes-config-maps.enabled Whether to enable auto configuration of the kubernetes-config-maps component. This is enabled by default. Boolean camel.component.kubernetes-config-maps.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

Commands:
kubernetes-config-maps:masterUrl
Chapter 12. Database cleaning Warning The content for this feature is available in this release as a Documentation Preview , and therefore is not fully verified by Red Hat. Use it only for testing, and do not use in a production environment. The Compute service includes an administrative tool, nova-manage , that you can use to perform deployment, upgrade, clean-up, and maintenance-related tasks, such as applying database schemas, performing online data migrations during an upgrade, and managing and cleaning up the database. The following database management tasks are performed by default: Archives deleted instance records by moving the deleted rows from the production tables to shadow tables. Purges deleted rows from the shadow tables after archiving is complete.

Commands:
4.113. kdeaccessibility 4.113.1. RHBA-2011:1173 - kdeaccessibility bug fix update Updated kdeaccessibility packages that fix one bug are now available for Red Hat Enterprise Linux 6. KDE is a graphical desktop environment for the X Window System. Kdeaccessibility contains KDE accessibility utilities, including KMouseTool (to initiate mouse clicks), KMag (to magnify parts of the screen), and KMouth & KTTS (a text-to-speech utility). Bug Fix BZ# 587897 Prior to this update, the icon for the kttsmsg program incorrectly appeared in GNOME Application's Accessories menu. This bug has been fixed in this update so that the icon is now no longer displayed, as expected. All users of kdeaccessibility are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 13. Fixed issues in Red Hat Process Automation Manager 7.13.3 Red Hat Process Automation Manager 7.13.3 provides increased stability and fixed issues listed in this section. 13.1. Business Central Dashbuilder does not support the type MILLISECOND [ RHPAM-4659 ] An exception occurs while using expressions with the USD character in BRL condition in GDST [ RHDM-1938 ] 13.2. Process engine IntermediateThrowingSignal node from subprocess and the subprocess is not getting marked as executed. [ RHPAM-4653 ] With jbpm-kie-services and Servicesorm.xml the incorrect version of orm is used [ RHPAM-4649 ] Error code: 404 on History button for Process Variable of type: org.jbpm.document.DocumentCollection [ RHPAM-4648 ] Unable to abort process instances that encounter the issue reported in RHPAM-4296 [ RHPAM-4625 ] Some events are missed in event emitters (elastic search) [ RHPAM-4584 ] Update Quarkus version in PIM to support Keystore and trustore passwords to be stored on vault [ RHPAM-4423 ] 13.3. Red Hat build of Kogito BPMN files contaning (Java) ServiceTask created using VSCode BPMN Editor causes parser errors in maven build [ RHPAM-4604 ] 13.4. DMN Designer [GSS](7.13.3) DMN extend rule to catch non-normalized named elements [ RHDM-1957 ] 13.5. Red Hat OpenShift Container Platform Red Hat Process Automation Manager Kogito Operator 7.x installation is failing with OOMKilled and CrashLoopBackOff [ RHPAM-4629 ] 13.6. Decision engine NullPointerException in mvel MathProcessor with equality check when null property is on right side [ RHPAM-4642 ] executable-model fails with BigDecimal arithmetic when it's a scope of a method call [ RHDM-1966 ] The str operator with bind variable fails after mvel jitting [ RHDM-1965 ] The executable model build fails when setting negative BigDecimal literal value [ RHDM-1959 ]

Commands:
Chapter 13. Tagging virtual devices In Red Hat OpenStack Platform (RHOSP), if you attach multiple network interfaces or block devices to an instance, you can use device tagging to communicate the intended role of each device to the instance operating system. Tags are assigned to devices at instance boot time, and are available to the instance operating system through the metadata API and the configuration drive, if enabled. You can also tag virtual devices to a running instance. For more information, see the following procedures: Attaching a network to an instance Attaching a volume to an instance Procedure Create your instance with a virtual block device tag and a virtual network device tag: Replace <myNicTag> with the name of the tag for the virtual NIC device. You can add as many tagged virtual devices as you require. Replace <myVolumeTag> with the name of the tag for the virtual storage device. You can add as many tagged virtual devices as you require. Verify that the virtual device tags have been added to the instance metadata by using one of the following methods: Retrieve the device tag metadata from the metadata API by using GET /openstack/latest/meta_data.json . If the configuration drive is enabled and mounted under /configdrive on the instance operating system, view the /configdrive/openstack/latest/meta_data.json file. Example meta_data.json file:

Commands:
openstack server create --flavor m1.tiny --image cirros --network <network_UUID> --nic net-id=<network_UUID>,tag=<myNicTag> --block-device id=<volume_ID>,bus=virtio,tag=<myVolumeTag> myTaggedDevicesInstance
{ "devices": [ { "type": "nic", "bus": "pci", "address": "0030:00:02.0", "mac": "aa:00:00:00:01", "tags": ["myNicTag"] }, { "type": "disk", "bus": "pci", "address": "0030:00:07.0", "serial": "disk-vol-227", "tags": ["myVolumeTag"] } ] }