mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 5. Attesting and validating a container image Before Enterprise Contract can validate your signed container image, you must first create SLSA provenance and associate it with your container image. Provenance is the verifiable information about software artifacts, including where, when, and how a given software "link" in a supply chain was produced. For more information about Supply-chain Levels for Software Artifacts (SLSA) provenance, see SLSA Provenance . Prerequisites A signed container image. Access to the OpenShift web console. A working Red Hat Trusted Artifact Signer installation running on OpenShift version 4.13 or later. A workstation with the cosign and oc binary files installed. Procedure Create a SLSA provenance predicate.json file; for example: Sign and attest the predicate.json file you just created; for example: Keycloak opens to automatically authenticate you based on your login when you signed your container image. Verify the signature and attestation with Enterprise Contract, for example: Important Be as specific as possible when you run the ec validate image command so that each signature matches the expected identity . Verification When Enterprise Contract has validated your container image, a detailed report of all Enterprise Contract verifications and signatures opens. Additional resources For more information about Red Hat Trusted Artifact Signer, and especially about how it works with RHTAP and Enterprise Contract, see Red Hat Trusted Artifact Signer Deployment . For more information about SLSA, see slsa.dev . For more information about Keycloak, see keycloak.org . 5.1. Verifying JSON and YAML definitions When you're considering all of your options for securing your software supply chain, you might choose to apply policies to task or pipeline definitions. For example, maybe you want to use Enterprise Contract to check which tasks are performed in a given pipeline. Perhaps you want to make some pipeline tasks mandatory, allow only certain tasks to be performed, or any other convention you want to enforce before tasks and pipelines run. Prerequisites You've installed the Enterprise Contract CLI. For install instructions, refer to the Installing Enterprise Contract CLI guide. You can find the required files in the ec-cli GitHub repository . Procedure To verify that an Enterprise Contract JSON or YAML definition is valid, perform the following steps: In the Enterprise Contract CLI, enter the ec validate input command.

Commands:
echo '{ "builder": { "id": "https://localhost/dummy-id" }, "buildType": "https://localhost/dummy-type", "invocation": {}, "buildConfig": {}, "metadata": { "buildStartedOn": "2023-09-25T16:26:44Z", "buildFinishedOn": "2023-09-25T16:28:59Z", "completeness": { "parameters": false, "environment": false, "materials": false }, "reproducible": false }, "materials": [] } ' > predicate.json
cosign attest -y --fulcio-url=USDFULCIO_URL --rekor-url=USDREKOR_URL --oidc-issuer=USDOIDC_ISSUER_URL --predicate predicate.json --type slsaprovenance USDIMAGE
ec validate image --image USDIMAGE --certificate-identity-regexp '.*' --certificate-oidc-issuer-regexp '.*' --output yaml --show-successes
Chapter 7. Known issues This section documents known issues found in this release of Red Hat Ceph Storage. 7.1. Ceph Management Dashboard Disk AVG utilization panel shows N/A on the Red Hat Ceph Storage Dashboard The Red Hat Ceph Storage Dashboard displays a value of N/A on the Overall host performance AVG disk utilization panel thereby showing incorrect Grafana queries. 7.2. Ceph Object Gateway Lifecycle processing stuck in "PROCESSING" state for a given bucket If a Ceph Object Gateway server is unexpectedly restarted when the lifecycle processing is in progress for a given bucket, that bucket does not resume processing lifecycle work for at least two scheduling cycles and is stuck in "PROCESSING" state. This is an expected behavior as it is intended to avoid multiple Ceph Object gateway instances or threads from processing the same bucket simultaneously, especially when the debugging is in progress in production. For future releases, the lifecycle processing shall restart on the following day, when debugging is not enabled. (BZ#2072681) 7.3. The Ceph Ansible utility Ceph containers fails during startup The new deployment of Red Hat Ceph Storage-4.3.z1 on Red Hat Enterprise Linux-8.7 (or higher) or Upgrade of Red Hat Ceph Storage-4.3.z1 to 5.X with host OS as Red Hat Enterprise Linux-8.7(or higher) fails at TASK [ceph-mgr : wait for all mgr to be up] . The behavior of podman released with Red Hat Enterprise Linux 8.7 had changed with respect to SELinux relabeling. Due to this, depending on their startup order, some Ceph containers would fail to start as they would not have access to the files they needed. As a workaround, refer to the knowledge base RHCS 4.3 installation fails while executing the command `ceph mgr dump` ( BZ#2235299 )

Commands:
4.7.2. Useful Websites http://people.redhat.com/alikins/system_tuning.html -- System Tuning Info for Linux Servers. A stream-of-consciousness approach to performance tuning and resource monitoring for servers. http://www.linuxjournal.com/article.php?sid=2396 -- Performance Monitoring Tools for Linux. This Linux Journal page is geared more toward the administrator interested in writing a customized performance graphing solution. Written several years ago, some of the details may no longer apply, but the overall concept and execution are sound.

Commands:
E.8. GRUB Menu Configuration File The configuration file ( /boot/grub/grub.conf on BIOS systems and /boot/efi/EFI/redhat/grub.conf on UEFI systems), which is used to create the list of operating systems to boot in GRUB's menu interface, essentially allows the user to select a pre-set group of commands to execute. The commands given in Section E.7, "GRUB Commands" can be used, as well as some special commands that are only available in the configuration file. E.8.1. Configuration File Structure The commands to set the global preferences for the menu interface are placed at the top of the GRUB configuration file, followed by stanzas for each operating kernel or operating system listed in the menu. The following is a very basic GRUB menu configuration file designed to boot either Red Hat Enterprise Linux or Microsoft Windows: This file configures GRUB to build a menu with Red Hat Enterprise Linux as the default operating system and sets it to autoboot after 10 seconds. Two sections are given, one for each operating system entry, with commands specific to the system disk partition table. Note Note that the default is specified as an integer. This refers to the first title line in the GRUB configuration file. For the Windows section to be set as the default in the example, change the default=0 to default=1 . Configuring a GRUB menu configuration file to boot multiple operating systems is beyond the scope of this chapter. Consult Section E.10, "Additional Resources" for a list of additional resources.

Commands:
default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Red Hat Enterprise Linux Server (2.6.32.130.el6.i686) root (hd0,0) kernel /boot/vmlinuz-2.6.32.130.el6.i686 ro root=LABEL=/1 rhgb quiet initrd /boot/initrd-2.6.32.130.el6.i686.img section to load Windows title Windows rootnoverify (hd0,0) chainloader +1
Chapter 4. Unmanaging Cluster The following are the reasons to unmanage a cluster: Import cluster fails Removal of a cluster that is no longer under management and used for monitoring A way to remove orphaned cluster entries Unmanage a cluster from Web Administration To unmanage a cluster: Log in to the Web Administration interface and select the All Clusters view from drop-down. Locate the cluster from the list of imported clusters. At the far right of the cluster row, click the vertical ellipsis and then click Unmanage . A confirmation box appears. Click Unmanage to proceed. The unmanage cluster task is submitted. To view the task progress, click View Task Progress . The status shows Completed after the unmanage task is successfully completed. Note After a cluster is unmanaged, it will not reappear immediately for reimport in the Web Administration environment. When the cluster is unmanaged, the tendrl-node-agent service undergoes synchronization with the nodes in the cluster. Based on the number of nodes in the cluster, expect a delay ranging from 60 seconds to a few minutes for the unmanaged cluster to reappear in the Web Administration environment. 4.1. Graphite and Carbon Data Archival Graphite and Carbon Data Archival When the cluster unmanage process is initiated, a concurrent process of cluster metrics data archival also begins. Once the cluster unmanage operation is successfully concluded, the Graphite and Carbon metrics data is archived to the following path on the Web Administration server: The size of the archived data will depend on the size of the cluster that is unmanaged. You can either store the archived data or delete it to free some disk space. 4.2. Graphite Database Metrics Retention The Graphite web service is a repository of telemetry data collected using collectd. Changing metrics retention period By default, Graphite retains the cluster metrics for a period of 180 days. To change the default metrics retention period for a given cluster, follow these steps: Unmanage the cluster by following the Unmanage Cluster procedure outlined in the Red Hat Gluster Storage Web Administration Monitoring Guide. After the cluster is unmanaged, stop the carbon-cache service on the Web Administration server: Access the storage-schemas.conf file at: Change the retention period in the retentions parameter under [tendrl] section and save the changes. Example : If you want to change the retention value to 90 days, set the value in the retentions parameter: Where: retentions = Each datapoint represents 60 seconds, and we want to keep enough datapoints so that they add up to 90 days of data. Start the carbon-cache service on the Web Administration server: Import the cluster again. For instructions, see the Import Cluster chapter in the Red Hat Gluster Storage Web Administration Monitoring Guide.

Commands:
/var/lib/carbon/whisper/tendrl/archive/clusters
systemctl stop carbon-cache
/etc/tendrl/monitoring-integration/storage-schemas.conf
[tendrl] pattern = ^tendrl\. retentions = 60s:90d
systemctl start carbon-cache
7.24. cim-schema 7.24.1. RHBA-2015:1267 - cim-schema bug fix and enhancement update An updated cim-schema package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The cim-schema package contains Common Information Model (CIM), a model for describing overall management information in a network or enterprise environment. Note The cim-schema package has been upgraded to upstream version 2.33, which provides a number of model changes and enhancements over the version of the Final schema. This update also contains Experimental schema. (BZ# 1087888 ) Users of cim-schema are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
40.8. Graphical Interface Some OProfile preferences can be set with a graphical interface. To start it, execute the oprof_start command as root at a shell prompt. After changing any of the options, save them by clicking the Save and quit button. The preferences are written to /root/.oprofile/daemonrc , and the application exits. Exiting the application does not stop OProfile from sampling. On the Setup tab, to set events for the processor counters as discussed in Section 40.2.2, "Setting Events to Monitor" , select the counter from the pulldown menu and select the event from the list. A brief description of the event appears in the text box below the list. Only events available for the specific counter and the specific architecture are displayed. The interface also displays whether the profiler is running and some brief statistics about it. Figure 40.1. OProfile Setup On the right side of the tab, select the Profile kernel option to count events in kernel mode for the currently selected event, as discussed in Section 40.2.3, "Separating Kernel and User-space Profiles" . If this option is unselected, no samples are collected for the kernel. Select the Profile user binaries option to count events in user mode for the currently selected event, as discussed in Section 40.2.3, "Separating Kernel and User-space Profiles" . If this option is unselected, no samples are collected for user applications. Use the Count text field to set the sampling rate for the currently selected event as discussed in Section 40.2.2.1, "Sampling Rate" . If any unit masks are available for the currently selected event, as discussed in Section 40.2.2.2, "Unit Masks" , they are displayed in the Unit Masks area on the right side of the Setup tab. Select the checkbox beside the unit mask to enable it for the event. On the Configuration tab, to profile the kernel, enter the name and location of the vmlinux file for the kernel to monitor in the Kernel image file text field. To configure OProfile not to monitor the kernel, select No kernel image . Figure 40.2. OProfile Configuration If the Verbose option is selected, the oprofiled daemon log includes more information. If Per-application kernel samples files is selected, OProfile generates per-application profiles for the kernel and kernel modules as discussed in Section 40.2.3, "Separating Kernel and User-space Profiles" . This is equivalent to the opcontrol --separate=kernel command. If Per-application shared libs samples files is selected, OProfile generates per-application profiles for libraries. This is equivalent to the opcontrol --separate=library command. To force data to be written to samples files as discussed in Section 40.5, "Analyzing the Data" , click the Flush profiler data button. This is equivalent to the opcontrol --dump command. To start OProfile from the graphical interface, click Start profiler . To stop the profiler, click Stop profiler . Exiting the application does not stop OProfile from sampling.

Commands:
D.7. Server View The Server View provides a means to display and manage server instances and their contents within the JBoss Developer Studio environment. Since Teiid Designer is installed as part of a JBoss Data Virtualization server, its contents is displayed as part of its JBoss parent. To show the Server View click Window > Show View > Other... to display the Show View dialog. Click Server > Servers view and click OK . Figure D.9. Server View To create your Teiid instance: Right-click and then select New > Server to launch the JBoss Data Virtualization Server wizard. Configuring the JBoss Data Virtualization Server instance (with Teiid installed) will enable connection to the Teiid Server. In the New Server wizard, select the Red Hat JBoss Enterprise Application Platform server type under the Red Hat JBoss Middleware category and click > . Figure D.10. New Server Dialog On the JBoss Runtime page, click the top Browse... button to select the installation folder of your JBoss Enterprise Application Platform server. Figure D.11. JBoss Runtime Definition Then click the bottom Browse... button to select the standalone.xml configuration file located under the EAP_HOME /standalone/configuration/ folder on your file system. Then click Finish . Figure D.12. Teiid Configuration File Selection Your new JBoss Data Virtualization server configuration will be opened in the JBoss / Teiid Editor for viewing. In this editor you can test both Teiid admin and JDBC connections. Figure D.13. Teiid Editor Actions available in this view include: Teiid Server Properties - View and edit properties of an existing Teiid instance. Reconnect - Reconnect and refresh contents of the selected Teiid instance. Execute VDB - Creates a JDBC Teiid connection profile and opens the Data Tools Database Development perspective. Undeploy VDB - Removes the selected VDB from the Teiid instance. Create Data Source - Launches the New Data Source wizard. Delete Data Source - Removes the selected Data Source from the Teiid instance. Note Once the server is started, the Server view will now display the data source, translator and VDB content for your running Teiid server. Figure D.14. Teiid Contents in Server View

Commands:
Chapter 25. Reducing TCP performance spikes Generating TCP timestamps can result in TCP performance spikes. The sysctl command controls the values of TCP related entries, setting the timestamps kernel parameter found at /proc/sys/net/ipv4/tcp_timestamps . Prerequisites You have administrator privileges. 25.1. Turning off TCP timestamps Turning off TCP timestamps can reduce TCP performance spikes. Procedure Turn off TCP timestamps: The output shows that the value of net.ip4.tcp_timestamps options is 0 . That is, TCP timestamps are disabled. 25.2. Turning on TCP timestamps Generating timestamps can cause TCP performance spikes. You can reduce TCP performance spikes by disabling TCP timestamps. If you find that generating TCP timestamps is not causing TCP performance spikes, you can enable them. Procedure Enable TCP timestamps. The output shows that the value of net.ip4.tcp_timestamps is 1 . That is, TCP timestamps are enabled. 25.3. Displaying the TCP timestamp status You can view the status of TCP timestamp generation. Procedure Display the TCP timestamp generation status: The value 1 indicates that timestamps are being generated. The value 0 indicates timestamps are being not generated.

Commands:
sysctl -w net.ipv4.tcp_timestamps=0 net.ipv4.tcp_timestamps = 0
sysctl -w net.ipv4.tcp_timestamps=1 net.ipv4.tcp_timestamps = 1
sysctl net.ipv4.tcp_timestamps net.ipv4.tcp_timestamps = 0
Chapter 5. Managing DHCP Using Capsule Satellite can integrate with a DHCP service using your Capsule. A Capsule has multiple DHCP providers that you can use to integrate Satellite with your existing DHCP infrastructure or deploy a new one. You can use the DHCP module of Capsule to query for available IP addresses, add new, and delete existing reservations. Note that your Capsule cannot manage subnet declarations. Available DHCP providers dhcp_infoblox - For more information, see Using Infoblox as DHCP and DNS Providers in Provisioning Hosts . dhcp_isc - ISC DHCP server over OMAPI. For more information, see Configuring DNS, DHCP, and TFTP on Capsule Server in Installing Capsule Server . dhcp_remote_isc - ISC DHCP server over OMAPI with leases mounted through networking. For more information, see Configuring an External DHCP Server to Use with Capsule Server in Installing Capsule Server . 5.1. Securing the dhcpd API Capsule interacts with DHCP daemon using the dhcpd API to manage DHCP. By default, the dhcpd API listens to any host without access control. You can add an omapi_key to provide basic security. Procedure Install the required packages: Generate a key: Use satellite-installer to secure the dhcpd API:

Commands:
yum install bind-utils
dnssec-keygen -r /dev/urandom -a HMAC-MD5 -b 512 -n HOST omapi_key cat Komapi_key.+*.private | grep ^Key|cut -d ' ' -f2-
satellite-installer --foreman-proxy-dhcp-key-name " My_Name " --foreman-proxy-dhcp-key-secret " My_Secret "
4.4. Deploy Web Applications on WebLogic Server (Library Mode) Red Hat JBoss Data Grid supports the WebLogic 12c application server in Library mode. The following procedure describes how to deploy web applications on a WebLogic server. Prerequisites The prerequisites to deploy the web applications are as follows: WebLogic Server 12c. JBoss Data Grid Library (Embedded) mode. Procedure 4.1. Deploying Web Applications on a WebLogic Server Create Web Applications Create a web application and add the libraries in the WEB-INF folder. Create a weblogic.xml Deployment Descriptor Create a weblogic.xml deployment descriptor with the following elements in it: Note The prefer-web-inf-classes class indicates that the libraries and the classes in the WEB-INF/lib folder is preferred over the default libraries bundled in the WebLogic server. For example, the commons-pool.jar file in the WebLogic server has version 1.4 and is automatically loaded by the classloader, but the Hot Rod client uses a newer version of this library. Pack the Web Application into a Web Archive File Create a web application archive (WAR) file of the web application and verify that the JBoss Data Grid libraries are in the WEB-INF folder along with the WebLogic deployment descriptor file. Deploy the Application onto WebLogic Server To deploy the web application using the Infinispan CDI module, stop the WebLogic server if it is running, apply the patch on it (Patch file p17424706_121200_Generic.zip ) and restart the WebLogic server. If the Infinispan CDI module is not being used, deploy the web application normally. For more information about applying patch to the WebLogic Server, see the Oracle patch database on the Oracle website. Report a bug

Commands:
<?xml version="1.0" encoding="UTF-8"?> <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd"> <container-descriptor> <prefer-web-inf-classes>true</prefer-web-inf-classes> </container-descriptor> </weblogic-web-app>
Chapter 20. Containers A set of container images is available for Red Hat Enterprise Linux 8. Notable changes include: Docker is not included in RHEL 8.0. For working with containers, use the podman , buildah , skopeo , and runc tools. For information about these tools and on using containers in RHEL 8, see Building, running, and managing containers . The podman tool has been released as a fully supported feature. The podman tool manages pods, container images, and containers on a single node. It is built on the libpod library, which enables management of containers and groups of containers, called pods. To learn how to use podman , see Building, running, and managing containers . In RHEL 8 GA, Red Hat Universal Base Images (UBI) are newly available. UBIs replace some of the images Red Hat previously provided, such as the standard and the minimal RHEL base images. Unlike older Red Hat images, UBIs are freely redistributable. This means they can be used in any environment and shared anywhere. You can use them even if you are not a Red Hat customer. For UBI documentation, see Building, running, and managing containers . In RHEL 8 GA, additional container images are available that provide AppStream components, for which container images are distributed with Red Hat Software Collections in RHEL 7. All of these RHEL 8 images are based on the ubi8 base image. Container images ARM for the 64-bit ARM architecture are fully supported in RHEL 8. The rhel-tools container has been removed in RHEL 8. The sos and redhat-support-tool tools are provided in the support-tools container. System administrators can also use this image as a base for building system tools container image. The support for rootless containers is available as a technology preview in RHEL 8. Rootless containers are containers that are created and managed by regular system users without administrative permissions.

Commands:
Providing feedback on Red Hat documentation We appreciate your feedback on our documentation. Let us know how we can improve it. Submitting comments on specific passages View the documentation in the HTML format and ensure that you see the Feedback button in the upper right corner after the page fully loads. Use your cursor to highlight the part of the text that you want to comment on. Click the Add Feedback button that appears near the highlighted text. Add your feedback and click Submit . Submitting feedback through Jira (account required) Log in to the Jira website. Click Create in the top navigation bar Enter a descriptive title in the Summary field. Enter your suggestion for improvement in the Description field. Include links to the relevant parts of the documentation. Click Create at the bottom of the dialogue.

Commands: