mtpti5iD/redhat-docs_dataset huggingface dataset:
B.3. Representing Binary Data Binary data, such as a JPEG image, is represented in LDIF using one of two methods, standard LDIF notation or base-64 encoding. B.3.1. Standard LDIF Notation Standard LDIF notation uses the lesser than (<) symbol to indicate that the data are binary. For example: With this standard notation, it is not necessary to specify the ldapmodify -b parameter. However, standard notation requires that the following line be added to the beginning of the LDIF file or the LDIF update statements: For example: B.3.2. Base-64 Encoding Binary data can be converted to base-64, which can be used in LDIF files, for a variety of data, from images to TLS certificates. Base 64-encoded data are identified by using the :: symbol. For example: In addition to binary data, other values that must be base-64 encoded include the following: Any value that begins with a colon (:) or a space. Any value that contains non-ASCII data, including new lines. Use the ldif command-line utility with the -b parameter to convert binary data to LDIF format: attribute_name is the name of the attribute to which the binary data is supplied. The binary data is read from standard input and the results are written to standard output. Thus, use redirection operators to select input and output files. The ldif command-line utility will take any input and format it with the correct line continuation and appropriate attribute information. The ldif utility also assesses whether the input requires base-64 encoding. For example: This example takes a binary file containing a JPEG-formatted image and converts it into LDIF format for the attribute jpegPhoto . The output is saved to out.ldif . The -b option specifies that the ldif utility should interpret the entire input as a single binary value. If -b is not present, each line is considered to be a separate input value.

Commands:
jpegphoto: < file:/path/to/photo
version: 1
ldapmodify -x -D userDN -W version: 1 dn: cn=Barney Fife,ou=People,dc=example,dc=com changetype: modify add: usercertificate usercertificate;binary: < file: BarneysCert
jpegPhoto:: encoded_data
ldif -b attribute_name
ldif -b jpegPhoto < mark.jpg > out.ldif
Chapter 10. Fixed issues The issues fixed in Streams for Apache Kafka 2.9 on OpenShift. For details of the issues fixed in Kafka 3.9.0, refer to the Kafka 3.9.0 Release Notes. Table 10.1. Streams for Apache Kafka fixed issues Issue Number Description ENTMQST-4324 Make it possible to use Cruise Control to move all data between two JBOD disks ENTMQST-5318 [KAFKA] Improve MirrorMaker logging in case of authorization errors ENTMQST-6234 [BRIDGE] path label in metrics can contain very different values and that makes it hard to work with the metrics ENTMQST-6277 Do not generate empty required arrays in OneOf definition ENTMQST-6278 The namespace.mapper configuration option of Mongodb Sink connector is reported as forbidden ENTMQST-6282 Fix port handling in the Kafka Agent ENTMQST-6283 Improve handling of custom Cruise Control topic configurations ENTMQST-6312 Improve handling of invalid topic configurations ENTMQST-6313 The KafkaTopic.status.topicId is never updated ENTMQST-6331 Use init container for Kafka nodes only when needed ENTMQST-6340 Improve documentation, logging, and automation of certificate renewal activities on OpenShift ENTMQST-6342 Remove-brokers rebalancing seems to get stuck by race condition ENTMQST-6391 CA cert annotations aren't updated during CaReconciler rolling update ENTMQST-6410 Findings in DAST scans results for 2.8.0 ENTMQST-6444 Support for mounting CSI volumes Table 10.2. Streams for Apache Kafka Console fixed issues Issue number Description ASUI-96 Pause and Resume Kafka Reconciliation ASUI-77 Filtering topics by ID not working ASUI-92 Kafka Rebalance Management 10.1. Security updates Check the latest information about Streams for Apache Kafka security updates in the Red Hat Product Advisories portal. 10.2. Erratas Check the latest security and product enhancement advisories for Streams for Apache Kafka.

Commands:
2.2. Starting Cluster Services Start the cluster services on the nodes in the cluster using the following procedure. On both nodes in the cluster, start the ricci service and set a password for user ricci . On the node that will be hosting the web management interface, start the luci service. This will provide the link from which to access luci on this node.

Commands:
service ricci start Starting ricci: [ OK ] passwd ricci New password: Retype new password:
service luci start Starting luci: generating https SSL certificates... done [ OK ] Please, point your web browser to https://example-01:8084 to access luci
Chapter 24. SystemTap SystemTap is a useful instrumentation platform for probing running processes and kernel activity on the Linux system. To execute a probe: Write SystemTap scripts that specify which system events (for example, virtual file system reads, packet transmissions) should trigger specified actions (for example, print, parse, or otherwise manipulate data). SystemTap translates the script into a C program, which it compiles into a kernel module. SystemTap loads the kernel module to perform the actual probe. SystemTap scripts are useful for monitoring system operation and diagnosing system issues with minimal intrusion into the normal operation of the system. You can quickly instrument running system test hypotheses without having to recompile and re-install instrumented code. To compile a SystemTap script that probes kernel-space , SystemTap uses information from three different kernel information packages : kernel- variant -devel- version kernel- variant -debuginfo- version kernel-debuginfo-common- arch-version These kernel information packages must match the kernel to be probed. In addition, to compile SystemTap scripts for multiple kernels, the kernel information packages of each kernel must also be installed. 24.1. Additional Information For more detailed information about SystemTap, see the following Red Hat documentation: SystemTap Beginner's Guide SystemTap Tapset Reference

Commands:
21.7. Virtualization Log Files Each fully virtualized guest log is in the /var/log/libvirt/qemu/ directory. Each guest log is named as GuestName .log and will be periodically compressed once a size limit is reached. If you encounter any errors with the Virtual Machine Manager, you can review the generated data in the virt-manager.log file that resides in the USDHOME/.virt-manager directory.

Commands:
Chapter 4. Knative CLI for use with OpenShift Serverless The Knative ( kn ) CLI enables simple interaction with Knative components on Red Hat OpenShift Service on AWS. 4.1. Key features The Knative ( kn ) CLI is designed to make serverless computing tasks simple and concise. Key features of the Knative CLI include: Deploy serverless applications from the command line. Manage features of Knative Serving, such as services, revisions, and traffic-splitting. Create and manage Knative Eventing components, such as event sources and triggers. Create sink bindings to connect existing Kubernetes applications and Knative services. Extend the Knative CLI with flexible plugin architecture, similar to the kubectl CLI. Configure autoscaling parameters for Knative services. Scripted usage, such as waiting for the results of an operation, or deploying custom rollout and rollback strategies. 4.2. Installing the Knative CLI See Installing the Knative CLI .

Commands:
4.4. Authentication Simultaneous maintaining of TGTs for multiple KDCs Kerberos version 1.10 added a new cache storage type, DIR:, which allows Kerberos to maintain Ticket Granting Tickets (TGTs) for multiple Key Distribution Centers (KDCs) simultaneously and auto-select between them when negotiating with Kerberized resources. Red Hat Enterprise Linux 6.4 and later includes SSSD enhanced to allow the users to select the DIR: cache for users that are logging in via SSSD. This feature is introduced as a Technology Preview. Package: sssd-1.9.2-129

Commands:
12.2. Monitor Red Hat JBoss Data Grid Applications in Red Hat JBoss EAP Ensure that all requirements outlined as prerequisites are met. Follow the listed steps to monitor Red Hat JBoss Data Grid applications in JBoss Enterprise Application Platform using JBoss Operations Network or RHQ. Procedure 12.1. Monitor JBoss Data Grid Applications in JBoss Enterprise Application Platform Configure RHQ/JBoss Operations Network Add an RHQ/JBoss Operations Network specific property (named org.rhq.resourceKey ) to the /bin/ standalone.conf file as follows: This command adds the property to the JBoss Enterprise Application Platform's command line indirectly. Check RHQ/JBoss Operations Network is Running Using a Full JDK Ensure that the RHQ/JBoss Operations Network agent started using a full JDK instead of a JRE. This is because the agent requires access to the JDK's tools.jar file. To configure your RHQ/JBoss Operations Network agent to use the JDK, follow the instructions relevant to your operating system: For Linux users, set the RHQ_AGENT_JAVA_HOME environment variable to the JDK home directory in the agent's rhq-agent-env.sh file. For Windows users, set the RHQ_AGENT_JAVA_HOME environment variable to the JDK home directory in the agent's rhq-agent-env.bat file. Ensure the Agent is Local to the JBoss Enterprise Application Platform Instance Ensure that the RHQ/JBoss Operations Network agent runs locally to and under the same user as the JBoss Application Platform instance. This is required for the Java Attach API to connect to the process. Import Resources to the Agent Inventory RHQ/JBoss Operations Network can now discover resources. These resources can subsequently be imported into the agent inventory. When a JBoss Data Grid user deployment enables JMX statistics to expose JBoss Data Grid Cache Managers or caches, the resources appear as children resources of the JBoss Enterprise Application Platform instance. Report a bug

Commands:
JAVA_OPTS="USDJAVA_OPTS -Dorg.rhq.resourceKey=MyEAP"
B.2. Maven Repository Configuration Example A sample Maven repository file named example-settings.xml is available in the root directory of the Maven repository folder after it is unzipped. The following is an excerpt that contains the relevant parts of the example-settings.xml file: Example B.1. Sample Maven Repository Configuration Report a bug

Commands:
<?xml version="1.0" encoding="UTF-8"?> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <proxies> <!-- proxy Specification for one proxy, to be used in connecting to the network. <proxy> <id>optional</id> <active>true</active> <protocol>http</protocol> <username>proxyuser</</username> <password>proxypass</password> <host>proxy.host.net</host> <port>80</port> <nonProxyHosts>local.net|some.host.com</nonProxyHosts> </proxy> --> </proxies> <profiles> <!-- Configure the JBoss GA Maven repository --> <profile> <id>jboss-ga-repository</id> <repositories> <repository> <id>jboss-ga-repository</id> <url>http://maven.repository.redhat.com/techpreview/all</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>jboss-ga-plugin-repository</id> <url>http://maven.repository.redhat.com/techpreview/all</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> </pluginRepositories> </profile> <!-- Configure the JBoss Early Access Maven repository --> <profile> <id>jboss-earlyaccess-repository</id> <repositories> <repository> <id>jboss-earlyaccess-repository</id> <url>http://maven.repository.redhat.com/earlyaccess/all/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>jboss-earlyaccess-plugin-repository</id> <url>http://maven.repository.redhat.com/earlyaccess/all/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <!-- Optionally, make the repositories active by default --> <activeProfile>jboss-ga-repository</activeProfile> <activeProfile>jboss-earlyaccess-repository</activeProfile> </activeProfiles> </settings>
Installing on OCI OpenShift Container Platform 4.15 Installing OpenShift Container Platform on Oracle Cloud Infrastructure Red Hat OpenShift Documentation Team

Commands:
Error: 400-InvalidParameter, DNS Label oci-demo does not follow Oracle requirements Suggestion: Please update the parameter(s) in the Terraform config as per error message DNS Label oci-demo does not follow Oracle requirements Documentation: https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/core_vcn
./openshift-install version
./openshift-install 4.15.0 built from commit ae7977b7d1ca908674a0d45c5c243c766fa4b2ca release image registry.ci.openshift.org/origin/release:4.15ocp-release@sha256:0da6316466d60a3a4535d5fed3589feb0391989982fba59d47d4c729912d6363 release architecture amd64
install-config.yaml apiVersion: v1 baseDomain: <base_domain> 1 networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 network type: OVNKubernetes machineNetwork: - cidr: <ip_address_from_cidr> 2 serviceNetwork: - 172.30.0.0/16 compute: - architecture: amd64 3 hyperthreading: Enabled name: worker replicas: 0 controlPlane: architecture: amd64 4 hyperthreading: Enabled name: master replicas: 3 platform: external: platformName: oci 5 cloudControllerManager: External sshKey: <public_ssh_key> 6 pullSecret: '<pull_secret>' 7
./openshift-install agent create image --log-level debug
apiVersion: v1alpha1 metadata: name: <cluster_name> 1 namespace: <cluster_namespace> 2 rendezvousIP: <ip_address_from_CIDR> 3 bootArtifactsBaseURL: <server_URL> 4
./openshift-install agent wait-for install-complete --log-level debug
export KUBECONFIG=~/auth/kubeconfig
oc get nodes -A
NAME STATUS ROLES AGE VERSION main-0.private.agenttest.oraclevcn.com Ready control-plane, master 7m v1.27.4+6eeca63 main-1.private.agenttest.oraclevcn.com Ready control-plane, master 15m v1.27.4+d7fa83f main-2.private.agenttest.oraclevcn.com Ready control-plane, master 15m v1.27.4+d7fa83f
oc get co
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE authentication 4.15.0-0 True False False 6m18s baremetal 4.15.0-0 True False False 2m42s network 4.15.0-0 True True False 5m58s Progressing: ... ...
11.6. Reserving Storage on a Volume The POSIX translator is now enhanced with an option that allows user to reserve disk space on the bricks. Some administrative operations, like expanding storage or rebalancing data across nodes, require spare working space on the disk. The storage.reserve option lets users expand disk or cluster when backend bricks are full. When the bricks have free space less than or equal to the reserved space, as declared by the user, new files are not created. This prevents ENOSPC errors on mount points. To enable reserve option, execute the following command: Once this option is enabled, the reserved disk space is not used by the mount points. The storage.reserve option either takes a percentage(%) suffixed value or an unsigned integer value suffixed with absolute units(KB, MB, GB etc). The default value for the option is 1%(1% of the brick size). If set to 0 this option is disabled. Note When the disk space reduces to the size of reserved disk space, only internal operations like rebalance, self-heal and so on can be performed.

Commands:
gluster volume set volname storage.reserve percentage
5.91. gnome-screensaver 5.91.1. RHBA-2012:1393 - gnome-screensaver bug fix update Updated gnome-screensaver packages that fix a bug are now available for Red Hat Enterprise Linux 6. The gnome-screensaver packages contain the GNOME project's official screen saver program. It is designed for improved integration with the GNOME desktop, including themeability, language support, and Human Interface Guidelines (HIG) compliance. It also provides screen-locking and fast user-switching from a locked screen. Bug Fix BZ# 860643 When a Mandatory profile was enabled, the "Lock screen when screen saver is active" option in the Gnome Screensaver Preferences window was not disabled. This bug could lead to security risks for users. With this update, the lock-screen option is disabled as expected in the described scenario, thus preventing this bug. All users of gnome-screensaver are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 10. Default Appearance The appearance and functionality of the GNOME 3 Desktop can be customized both by individual users and by system administrators for all users. System administrators can provide a customized default desktop configuration to all users and even lock down those features to prevent user changes. This chapter describes how to customize the installation program ( Anaconda ), the system boot utilities ( GRUB , Plymouth ), the login screen, fonts, keyboard layouts, the screen shield, and desktop backgrounds. 10.1. Branding Anaconda If you are building your own customized distribution at your company, you can change the brand graphics and product name used in the Red Hat Enterprise Linux 7 installer, Anaconda . For more information on changing the Anaconda graphics and product name, see the Anaconda Customization Guide for Red Hat Enterprise Linux 7.

Commands:
Appendix C. Sample iscsigws.yml file

Commands:
Variables here are applicable to all host groups NOT roles This sample file generated by generate_group_vars_sample.sh Dummy variable to avoid error because ansible does not recognize the file as a good configuration file when no variable in it. dummy: You can override vars by using host or group vars ########### GENERAL # ########### Whether or not to generate secure certificate to iSCSI gateway nodes #generate_crt: False #iscsi_conf_overrides: {} #iscsi_pool_name: rbd #iscsi_pool_size: "{{ osd_pool_default_size }}" #copy_admin_key: True ################## RBD-TARGET-API # ################## Optional settings related to the CLI/API service #api_user: admin #api_password: admin #api_port: 5000 #api_secure: false #loop_delay: 1 #trusted_ip_list: 192.168.122.1 ########## DOCKER # ########## Resource limitation For the whole list of limits you can apply see: docs.docker.com/engine/admin/resource_constraints Default values are based from: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html/red_hat_ceph_storage_hardware_guide/minimum_recommendations These options can be passed using the 'ceph_mds_docker_extra_env' variable. TCMU_RUNNER resource limitation #ceph_tcmu_runner_docker_memory_limit: "{{ ansible_memtotal_mb }}m" #ceph_tcmu_runner_docker_cpu_limit: 1 RBD_TARGET_GW resource limitation #ceph_rbd_target_gw_docker_memory_limit: "{{ ansible_memtotal_mb }}m" #ceph_rbd_target_gw_docker_cpu_limit: 1 RBD_TARGET_API resource limitation #ceph_rbd_target_api_docker_memory_limit: "{{ ansible_memtotal_mb }}m" #ceph_rbd_target_api_docker_cpu_limit: 1
3.2.3. Deleting a Fence Device Note Fence devices that are in use cannot be deleted. To delete a fence device that a node is currently using, first update the node fence configuration for any node using the device and then delete the device. To delete a fence device, follow these steps: From the Fence Devices configuration page, check the box to the left of the fence device or devices to select the devices to delete. Click Delete and wait for the configuration to be updated. A message appears indicating which devices are being deleted. When the configuration has been updated, the deleted fence device no longer appears in the display.

Commands:
10.2. Boot Loader Screen The Red Hat Enterprise Linux 7 boot loader is GRUB 2 . You can change several parts of GRUB 2 's appearance. The following sections show you how to change the distribution name, menu colors, and and the background image. 10.2.1. Distribution Name By default, GRUB 2 displays a title containing the distribution name. You can change the title by customizing the GRUB_DISTRIBUTOR variable in the /etc/default/grub file. Procedure 10.1. Setting the Distribution Name As root, open the /etc/default/grub file. Use the GRUB_DISTRIBUTOR variable to specify your own distribution name. The following is the excerpt of the /etc/default/grub file. Update the second line with the GRUB_DISTRIBUTOR variable: Run the following command as root to ensure the changes take effect: Note You need to update the /etc/default/grub directory after every change you make in there. Also, you can change the colors or the font of the text displayed at the GRUB 2 screen by modifying the /etc/grub.d/40_custom plain text file or by adding another file in the /etc/grub.d/ directory. You can choose from the following directives: set color_normal=foreground/background set color_highlight=foreground/background set menu_color_normal=foreground/background set menu_color_highlight=foreground/background See the grub (8) man page for more information on the semantics and accepted values for these variables. 10.2.2. GRUB 2 Background There is no GRUB background configured in the default setup. Nevertheless, it is possible to add an image to the boot loader screen. Before you configure a background image for GRUB 2 , it is necessary to have a GRUB 2 Unicode font installed for the gfxterm graphical terminal. No font is provided by default, so the prerequisite is to convert an existing TTF or OTF file to the PF2 format used by GRUB 2 : By running the grub2-mkfont command, convert an existing TTF or OTF file to the PF2 format. Name the output file unicode.pf2 to work correctly with the default configuration as written by grub2-mkconfig . Example 10.1. Converting a TTF File to PF2 Format This example demonstrates the conversion from the LiberationSerif-Bold.ttf to the .pf2 format. The new .pf2 format file is called unicode2 so as not to be confused with the existing unicode.pf2 in the /grub2/fonts/ directory. Now, you can configure a background image for GRUB 2 . The image file can reside outside of the boot/ directory. Procedure 10.2. Adding an Image to the Boot Loader Screen Open the /etc/default/grub file as root. Edit the following configuration variables in the file: Supported formats are PNG, JPG, JPEG, and TGA. Create a new configuration file with a background image: Reboot your system. If necessary, the image will be scaled to fit the screen.

Commands:
GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR= Our Corporate Distro V1.2 GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true
grub2-mkconfig -o /boot/grub2/grub.cfg
grub2-mkfont --output=/boot/grub2/fonts/unicode2.pf2 --size=24 /usr/share/fonts/liberation/LiberationSerif-Bold.ttf
GRUB_TERMINAL=gfxterm GRUB_BACKGROUND= path_to_the_image.png
grub2-mkconfig -o /boot/grub2/grub.cfg