mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Container images with Rust Toolset on RHEL 8 On RHEL 8, you can build your own Rust Toolset container images on top of Red Hat Universal Base Images (UBI) containers using Containerfiles. 4.1. Creating a container image of Rust Toolset on RHEL 8 On RHEL 8, Rust Toolset packages are part of the Red Hat Universal Base Images (UBIs) repositories. To keep the container size small, install only individual packages instead of the entire Rust Toolset. Prerequisites An existing Containerfile. For more information on creating Containerfiles, see the Dockerfile reference page. Procedure Visit the Red Hat Container Catalog . Select a UBI. Click Get this image and follow the instructions. To create a container containing Rust Toolset, add the following lines to your Containerfile: To create a container image containing an individual package only, add the following lines to your Containerfile: Replace < package_name > with the name of the package you want to install. 4.2. Additional resources For more information on Red Hat UBI images, see Working with Container Images . For more information on Red Hat UBI repositories, see Universal Base Images (UBI): Images, repositories, packages, and source code .

Commands:
FROM registry.access.redhat.com/ubi8/ubi: latest RUN yum install -y rust-toolset
RUN yum install < package-name >
Chapter 2. Executive reports You can download a high-level executive report summarizing the security exposure of your infrastructure. Executive reports are two to three-page PDF files, designed for an executive audience, and include the following information: On page 1 Number of RHEL systems analyzed Number of individual CVEs to which your systems are currently exposed Number of security rules in your infrastructure List of CVEs that have advisories On page 2 Percentage of CVEs by severity (CVSS base score) range Number of CVEs published by 7, 30, and 90 day time frame Top three CVEs in your infrastructure, including security rules and known exploits On page 3 Security rule breakdown by severity Top 3 security rules, including severity and number of exposed systems 2.1. Downloading an executive report Use the following steps to download an executive report for key stakeholders in your security organization: Procedure Navigate to the Security > Vulnerability > Reports tab and log in if necessary. On the Executive report card, click Download PDF . Click Save File and click OK . Verification Verify that the PDF file is in your Downloads folder or other specified location. 2.2. Downloading an executive report using the vulnerability service API You can download an executive report using the vulnerability service API . Request URL: https://console.redhat.com/api/vulnerability/v1/report/executive Curl: curl -X GET "https://console.redhat.com/api/vulnerability/v1/report/executive" -H "accept: application/vnd.api+json"

Commands:
curl -X GET "https://console.redhat.com/api/vulnerability/v1/report/executive" -H "accept: application/vnd.api+json"
Appendix F. Additional Replication High Availability Configuration Elements The following table lists additional ha-policy configuration elements that are not described in the Configuring replication high availability section. These elements have default settings that are sufficient for most common use cases. Table F.1. Additional configuration elements for replication high availability Name Used in Description check-for-live-server Embedded broker coordination Applies only to brokers configured as master brokers. Specifies whether the original master broker checks the cluster for another live broker using its own server ID when starting up. Set to true to fail back to the original master broker and avoid a "split brain" situation in which two brokers become live at the same time. The default value of this property is false . cluster-name Embedded broker and ZooKeeper coordination Name of the cluster configuration to use for replication. This setting is only necessary if you configure multiple cluster connections. If configured, the cluster configuration with this name will be used when connecting to the cluster. If unset, the first cluster connection defined in the configuration is used. initial-replication-sync-timeout Embedded broker and ZooKeeper coordination The amount of time the replicating broker will wait upon completion of the initial replication process for the replica to acknowledge that it has received all the necessary data. The default value of this property is 30,000 milliseconds. NOTE: During this interval, any other journal-related operations are blocked. max-saved-replicated-journals-size Embedded broker and ZooKeeper coordination Applies to backup brokers only. Specifies how many backup journal files the backup broker retains. Once this value has been reached, the broker makes space for each new backup journal file by deleting the oldest journal file. The default value of this property is 2 .

Commands:
4.368. cluster 4.368.1. RHBA-2013:1054 - cluster and gfs2-utils bug fix update Updated cluster and gfs2-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6 Extended Update Support. The Red Hat Cluster Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Using redundant hardware, shared disk storage, power management, and robust cluster communication and application failover mechanisms, a cluster can meet the needs of the enterprise market. Bug Fix BZ# 982698 Previously, the cman init script did not handle its lock file correctly. During a node reboot, this could have caused the node itself to be evicted from the cluster by other members. With this update, the cman init script now handles the lock file correctly, and no fencing action is taken by other nodes of the cluster. Users of cluster and gfs2-utils are advised to upgrade to these updated packages, which fix this bug.

Commands:
4.131. libcmpiutil 4.131.1. RHEA-2011:1586 - libcmpiutil enhancement update An updated libcmpiutil package that adds one enhancement is now available for Red Hat Enterprise Linux 6. The libcmpiutil library provides an application programming interface (API) for performing common tasks with various Common Manageability Programming Interface (CMPI) providers. Enhancement BZ# 694550 With this update, the performance and the interface of the libcmpiutil library have been enhanced, which is used by the libvirt-cim package. All libcmpiutil users are advised to upgrade to this updated package, which adds this enhancement.

Commands:
Chapter 11. Users and Roles Administration 11.1. User Roles There are three user roles available for Web Administration. Admin : The Admin role gives complete rights to the user to manage all Web Administration operations. Normal User : The Normal User role authorizes the user to perform operations such as importing cluster and enabling or disabling volume profiling but restricts managing users and other administrative operations. Read-only User : Read-only: The Read-only User role authorizes the user to only view and monitor cluster-wide metrics and readable data. The user can launch Grafana dashboards from the Web Administration interface but is restricted to perform any storage operations. This role is suited for users performing monitoring tasks. 11.2. Configuring Roles To add and configure a new user, follow these steps: Log In the Web Administration interface and in navigation pane, click Admin > Users . The users list is displayed. To add a new user, click Add at the right-hand side. Enter the user information in the given fields. To enable or disable email notifications, toggle the ON-OFF button. Select a Role from the available three roles and click Save . The new user is successfully created. 11.2.1. Editing Users To edit an existing user: Navigate to the user view by clicking Admin > Users from the interface navigation. Locate the user to be edited and click Edit at the right-hand side. Edit the required information and click Save . 11.2.2. Disabling Notifications and Deleting User Enabling and Disabling Notifications To enable notifications: Navigate to the user view by clicking Admin > Users from the interface navigation. Click the vertical elipsis to the Edit button and click Disable Email Notification from the callout menu. Email notification is successfuly disabled for the user. Deleting User To delete an existing user: Navigate to the user view by clicking Admin > Users from the interface navigation. Locate the user to be deleted and click the vertical elipsis to the Edit button. A callout menu opens, click Delete User . A confirmation box appears. Click Delete .

Commands:
B.25. gdm B.25.1. RHSA-2011:0395 - Moderate: gdm security update Updated gdm packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The GNOME Display Manager (GDM) provides the graphical login screen, shown shortly after boot up, log out, and when user-switching. CVE-2011-0727 A race condition flaw was found in the way GDM handled the cache directories used to store users' dmrc and face icon files. A local attacker could use this flaw to trick GDM into changing the ownership of an arbitrary file via a symbolic link attack, allowing them to escalate their privileges. Red Hat would like to thank Sebastian Krahmer of the SuSE Security Team for reporting this issue. All users should upgrade to these updated packages, which contain a backported patch to correct this issue. GDM must be restarted for this update to take effect. Rebooting achieves this, but changing the runlevel from 5 to 3 and back to 5 also restarts GDM.

Commands:
Chapter 13. Using TLS certificates for applications accessing RGW Most of the S3 applications require TLS certificate in the forms such as an option included in the Deployment configuration file, passed as a file in the request, or stored in /etc/pki paths. TLS certificates for RADOS Object Gateway (RGW) are stored as Kubernetes secret and you need to fetch the details from the secret. Prerequisites A running OpenShift Data Foundation cluster. Procedure For internal RGW server Get the TLS certificate and key from the kubernetes secret: <secret_name> The default kubernetes secret name is <objectstore_name>-cos-ceph-rgw-tls-cert . Specify the name of the object store. For external RGW server Get the the TLS certificate from the kubernetes secret: <secret_name> The default kubernetes secret name is ceph-rgw-tls-cert and it is an opaque type of secret. The key value for storing the TLS certificates is cert .

Commands:
oc get secrets/<secret_name> -o jsonpath='{.data..tls\.crt}' | base64 -d oc get secrets/<secret_name> -o jsonpath='{.data..tls\.key}' | base64 -d
oc get secrets/<secret_name> -o jsonpath='{.data.cert}' | base64 -d
18.4. RAID Support in the Anaconda Installer The Anaconda installer automatically detects any hardware and firmware RAID sets on a system, making them available for installation. Anaconda also supports software RAID using mdraid , and can recognize existing mdraid sets. Anaconda provides utilities for creating RAID sets during installation; however, these utilities only allow partitions (as opposed to entire disks) to be members of new sets. To use an entire disk for a set, create a partition on it spanning the entire disk, and use that partition as the RAID set member. When the root file system uses a RAID set, Anaconda adds special kernel command-line options to the bootloader configuration telling the initrd which RAID set(s) to activate before searching for the root file system. For instructions on configuring RAID during installation, see the Red Hat Enterprise Linux 7 Installation Guide .

Commands:
function::callers Name function::callers - Return first n elements of kernel stack backtrace Synopsis Arguments n number of levels to descend in the stack (not counting the top level). If n is -1, print the entire stack. Description This function returns a string of the first n hex addresses from the backtrace of the kernel stack. Output may be truncated as per maximum string length (MAXSTRINGLEN).

Commands:
callers:string(n:long)
21.3. Creating virsh Dump Files Executing a virsh dump command sends a request to dump the core of a guest virtual machine to a file so errors in the virtual machine can be diagnosed. Running this command may require you to manually ensure proper permissions on file and path specified by the argument corefilepath . The virsh dump command is similar to a coredump (or the crash utility). To create the virsh dump file, run: While the domain (guest virtual machine domain name) and corefilepath (location of the newly created core dump file) are mandatory, the following arguments are optional: --live creates a dump file on a running machine and does not pause it. --crash stops the guest virtual machine and generates the dump file. The main difference is that the guest virtual machine will not be listed as Stopped, with the reason as Crashed. Note that in virt-manager the status will be listed as Paused. --reset will reset the guest virtual machine following a successful dump. Note, these three switches are mutually exclusive. --bypass-cache uses O_DIRECT to bypass the file system cache. --memory-only the dump file will be saved as an elf file, and will only include domain's memory and cpu common register value. This option is very useful if the domain uses host devices directly. --verbose displays the progress of the dump The entire dump process may be monitored using virsh domjobinfo command and can be canceled by running virsh domjobabort .

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

Commands:
2.4. Partition Information Figure 2.4. Partition Information Select whether or not to clear the Master Boot Record (MBR). Choose to remove all existing partitions, remove all existing Linux partitions, or preserve existing partitions. To initialize the disk label to the default for the architecture of the system (for example, msdos for x86 and gpt for Itanium), select Initialize the disk label if you are installing on a brand new hard drive. 2.4.1. Creating Partitions To create a partition, click the Add button. The Partition Options window shown in Figure 2.5, "Creating Partitions" appears. Choose the mount point, file system type, and partition size for the new partition. Optionally, you can also choose from the following: In the Additional Size Options section, choose to make the partition a fixed size, up to a chosen size, or fill the remaining space on the hard drive. If you selected swap as the file system type, you can select to have the installation program create the swap partition with the recommended size instead of specifying a size. Force the partition to be created as a primary partition. Create the partition on a specific hard drive. For example, to make the partition on the first IDE hard disk ( /dev/hda ), specify hda as the drive. Do not include /dev in the drive name. Use an existing partition. For example, to make the partition on the first partition on the first IDE hard disk ( /dev/hda1 ), specify hda1 as the partition. Do not include /dev in the partition name. Format the partition as the chosen file system type. Figure 2.5. Creating Partitions To edit an existing partition, select the partition from the list and click the Edit button. The same Partition Options window appears as when you chose to add a partition as shown in Figure 2.5, "Creating Partitions" , except it reflects the values for the selected partition. Modify the partition options and click OK . To delete an existing partition, select the partition from the list and click the Delete button. 2.4.1.1. Creating Software RAID Partitions To create a software RAID partition, use the following steps: Click the RAID button. Select Create a software RAID partition . Configure the partitions as previously described, except select Software RAID as the file system type. Also, you must specify a hard drive on which to make the partition or specify an existing partition to use. Figure 2.6. Creating a Software RAID Partition Repeat these steps to create as many partitions as needed for your RAID setup. All of your partitions do not have to be RAID partitions. After creating all the partitions needed to form a RAID device, follow these steps: Click the RAID button. Select Create a RAID device . Select a mount point, file system type, RAID device name, RAID level, RAID members, number of spares for the software RAID device, and whether to format the RAID device. Figure 2.7. Creating a Software RAID Device Click OK to add the device to the list.

Commands:
Chapter 2. Using tags to manage cost data Learn how tags work in cost management and how you can use them to best organize and view your resources to manage your costs. 2.1. Enabling and creating a tag mapping Tag mapping is when you combine multiple tags across your cloud integrations. Tag mapping enables you to group and filter similar tags with one tag key. To map a tag, you must first enable it. Cost management has a limit of 200 tags that you can enable. Complete the following steps: In cost management, click Settings . Click the header tab, Tags and labels . Click the drop-down menu, Enable tags and labels . Select the tags that you want to enable. Clear a tag to disable it. , click the Map tags and labels drop-down menu and click Create a tag mapping . In the wizard that opens, select the tags that you want to make child tags. Then click . Select one tag that you want to be the parent tag. This action will map the parent tag to the children tags that you selected in the step. Click . Review your selections and click Create tag mapping . 2.1.1. Troubleshooting duplicate keys For every resource, each tag key must be unique and have only one value. However, when you map tags, you can unintentionally create scenarios that violate this rule and create multiple values. Ordinarily, having more than one value would duplicate your costs. However, to avoid duplication, cost management prioritizes one key's value. To understand how cost management prioritizes values and plan accordingly, see Section 1.3, "Understanding value precedence in tags" . 2.1.1.1. Troubleshooting example Consider the following example where you are running an EC2 instance on AWS. You tagged this instance with the following key > value pairs: app > cost-management App > Insights In cost management, you mapped app to App . Therefore, the same EC2 instance has the following key > value pairs: App > cost-management App > Insights In this situation, cost management prioritizes the pre-existing value of the key App > Insights . Cost management also removes the association of the key app and its value cost-management from the AWS resource to prevent duplicate costs. App=cost-management is added to the App=insight cost. Because App is set as the parent key, cost management prioritizes its value over the value of app in the tag mapping. Therefore, you should consider your tag mapping strategy before you set parent tags. To troubleshoot issues with duplicate keys, ensure that your tag keys are unique and have only one value. Alternatively, to learn how to prioritize your keys, see Section 1.3, "Understanding value precedence in tags" .

Commands:
probe::signal.sys_tkill Name probe::signal.sys_tkill - Sending a kill signal to a thread Synopsis signal.sys_tkill Values sig_pid The PID of the process receiving the kill signal sig The specific signal sent to the process name Name of the probe point pid_name The name of the signal recipient sig_name A string representation of the signal task A task handle to the signal recipient Description The tkill call is analogous to kill(2), except that it also allows a process within a specific thread group to be targeted. Such processes are targeted through their unique thread IDs (TID).

Commands:
Chapter 5. Load Balancing, Scheduling, and Migration 5.1. Load Balancing, Scheduling, and Migration Individual hosts have finite hardware resources, and are susceptible to failure. To mitigate against failure and resource exhaustion, hosts are grouped into clusters, which are essentially a grouping of shared resources. A Red Hat Virtualization environment responds to changes in demand for host resources using load balancing policy, scheduling, and migration. The Manager is able to ensure that no single host in a cluster is responsible for all of the virtual machines in that cluster. Conversely, the Manager is able to recognize an underutilized host, and migrate all virtual machines off of it, allowing an administrator to shut down that host to save power. Available resources are checked as a result of three events: Virtual machine start - Resources are checked to determine on which host a virtual machine will start. Virtual machine migration - Resources are checked in order to determine an appropriate target host. Time elapses - Resources are checked at a regular interval to determine whether individual host load is in compliance with cluster load balancing policy. The Manager responds to changes in available resources by using the load balancing policy for a cluster to schedule the migration of virtual machines from one host in a cluster to another. The relationship between load balancing policy, scheduling, and virtual machine migration are discussed in the following sections.

Commands: