mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 15. Idling applications Cluster administrators can idle applications to reduce resource consumption. This is useful when the cluster is deployed on a public cloud where cost is related to resource consumption. If any scalable resources are not in use, OpenShift Container Platform discovers and idles them by scaling their replicas to 0 . The time network traffic is directed to the resources, the resources are unidled by scaling up the replicas, and normal operation continues. Applications are made of services, as well as other scalable resources, such as deployment configs. The action of idling an application involves idling all associated resources. 15.1. Idling applications Idling an application involves finding the scalable resources (deployment configurations, replication controllers, and others) associated with a service. Idling an application finds the service and marks it as idled, scaling down the resources to zero replicas. You can use the oc idle command to idle a single service, or use the --resource-names-file option to idle multiple services. 15.1.1. Idling a single service Procedure To idle a single service, run: USD oc idle <service> 15.1.2. Idling multiple services Idling multiple services is helpful if an application spans across a set of services within a project, or when idling multiple services in conjunction with a script to idle multiple applications in bulk within the same project. Procedure Create a file containing a list of the services, each on their own line. Idle the services using the --resource-names-file option: USD oc idle --resource-names-file <filename> Note The idle command is limited to a single project. For idling applications across a cluster, run the idle command for each project individually. 15.2. Unidling applications Application services become active again when they receive network traffic and are scaled back up their state. This includes both traffic to the services and traffic passing through routes. Applications can also be manually unidled by scaling up the resources. Procedure To scale up a DeploymentConfig, run: USD oc scale --replicas=1 dc <dc_name> Note Automatic unidling by a router is currently only supported by the default HAProxy router.

Commands:
oc idle <service>
oc idle --resource-names-file <filename>
oc scale --replicas=1 dc <dc_name>
Appendix A. Using your subscription Debezium is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing your account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading zip and tar files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Scroll down to INTEGRATION AND AUTOMATION . Click Red Hat Integration to display the Red Hat Integration downloads page. Click the Download link for your component. Revised on 2023-11-17 04:10:54 UTC

Commands:
3.7. Software Collection MANPATH Support To allow the man command on the system to display man pages from the enabled Software Collection, update the MANPATH environment variable with the paths to the man pages that are associated with the Software Collection. To update the MANPATH environment variable, add the following to the %install section of the Software Collection spec file: %install cat >> %{buildroot}%{_scl_scripts}/enable << EOF export MANPATH="%{_mandir}:\USD{MANPATH:-}" EOF This configures the enable scriptlet to update the MANPATH environment variable. The man pages associated with the Software Collection are then not visible as long as the Software Collection is not enabled. The Software Collection can provide a wrapper script that is visible to the system to enable the Software Collection, for example in the /usr/bin/ directory. In this case, ensure that the man pages are visible to the system even if the Software Collection is disabled. To allow the man command on the system to display man pages from the disabled Software Collection, update the MANPATH environment variable with the paths to the man pages associated with the Software Collection. Procedure 3.7. Updating the MANPATH environment variable for the disabled Software Collection To update the MANPATH environment variable, create a custom script /etc/profile.d/ name.sh . The script is preloaded when a shell is started on the system. For example, create the following file: Use the manpage.sh short script that modifies the MANPATH variable to refer to your man path directory: Add the file to your Software Collection package's spec file: SOURCE2: %{?scl_prefix}manpage.sh Install this file into the system /etc/profile.d/ directory by adjusting the %install section of the Software Collection package's spec file: %install install -p -c -m 644 %{SOURCE2} USDRPM_BUILD_ROOT%{?scl:%_root_sysconfdir}%{!?scl:%_sysconfdir}/profile.d/

Commands:
%install cat >> %{buildroot}%{_scl_scripts}/enable << EOF export MANPATH="%{_mandir}:\USD{MANPATH:-}" EOF
%{?scl_prefix}manpage.sh
export MANPATH="/opt/ provider / software_collection/path/to/your/man_pages :USD{MANPATH}"
SOURCE2: %{?scl_prefix}manpage.sh
%install install -p -c -m 644 %{SOURCE2} USDRPM_BUILD_ROOT%{?scl:%_root_sysconfdir}%{!?scl:%_sysconfdir}/profile.d/
4.5. RHEA-2012:0829 - new packages: ipset and libmnl New ipset and libmnl packages are now available for Red Hat Enterprise Linux 6. The ipset packages provide IP sets, a framework inside the Linux 2.4.x and 2.6.x kernel, which can be administered by the ipset utility. Depending on the type, an IP set can currently store IP addresses, TCP/UDP port numbers or IP addresses with MAC addresses in a way that ensures high speed when matching an entry against a set. The libmnl packages required by the ipset packages provide a minimalistic user-space library oriented to Netlink developers. The library provides functions to make socket handling, message building, validating, parsing, and sequence tracking easier. This enhancement update adds the ipset and libmnl packages to Red Hat Enterprise Linux 6. (BZ# 477115 , BZ# 789346 ) All users who require ipset and libmnl are advised to install these new packages.

Commands:
Chapter 19. Determining Certificate System Product Version The Red Hat Certificate System product version is stored in the /usr/share/pki/CS_SERVER_VERSION file. To display the version: To find the product version of a running server, access the following URLs from your browser: http:// host_name : port_number /ca/admin/ca/getStatus http:// host_name : port_number /kra/admin/kra/getStatus http:// host_name : port_number /ocsp/admin/ocsp/getStatus http:// host_name : port_number /tks/admin/tks/getStatus http:// host_name : port_number /tps/admin/tps/getStatus Note Note that each component is a separate package and thus could have a separate version number. The above will show the version number for each currently running component.

Commands:
cat /usr/share/pki/CS_SERVER_VERSION Red Hat Certificate System 10.0 (Batch Update 1)
Chapter 1. Streams for Apache Kafka Proxy overview Streams for Apache Kafka Proxy is an Apache Kafka protocol-aware ("Layer 7") proxy designed to enhance Kafka-based systems. Through its filter mechanism it allows additional behavior to be introduced into a Kafka-based system without requiring changes to either your applications or the Kafka cluster itself. Built-in filters are provided as part of the solution. Functioning as an intermediary, the Streams for Apache Kafka Proxy mediates communication between a Kafka cluster and its clients. It takes on the responsibility of receiving, filtering, and forwarding messages. An API provides a convenient means for implementing custom logic within the proxy. Additional resources Apache Kafka website

Commands:
7.51. evolution-data-server 7.51.1. RHBA-2015:1264 - evolution-data-server bug fix update Updated evolution-data-server packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The evolution-data-server packages provide a unified back end for applications which interact with contacts, tasks and calendar information. Evolution Data Server was originally developed as a back end for the Evolution information management application, but is now used by various other applications. Bug Fixes BZ# 1163375 The Evolution client could not connect to a mail server using the Secure Sockets Layer (SSL) protocol when the server had SSL disabled due to the POODLE vulnerability. With this update, the Evolution Data Server has been modified to also connect using the Transport Layer Security (TLSv1) protocol, thus fixing this bug. BZ# 1141760 Previously, the e-calendar-factory process did not terminate automatically when the user logged out of the graphical desktop environment, and e-calendar-factory thus redundantly consumed system resources. This update fixes the underlying code, which prevents this problem from occurring. Users of evolution-data-server are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 4. Introducing metrics If you want to introduce metrics to your Streams for Apache Kafka Proxy deployment, you can configure an insecure HTTP and Prometheus endpoint (at /metrics ). Add the following to the ConfigMap resource that defines the Streams for Apache Kafka Proxy configuration: Minimal metrics configuration adminHttp: endpoints: prometheus: {} By default, the HTTP endpoint listens on 0.0.0.0:9190 . You can change the hostname and port as follows: Example metrics configuration with hostname and port adminHttp: host: localhost port: 9999 endpoints: prometheus: {} The example files provided with the proxy include a PodMonitor resource. If you have enabled monitoring in OpenShift for user-defined projects, you can use a PodMonitor resource to ingest the proxy metrics. Example PodMonitor resource configuration apiVersion: monitoring.coreos.com/v1 kind: PodMonitor metadata: name: proxy labels: app: proxy spec: selector: matchLabels: app: proxy namespaceSelector: matchNames: - proxy podMetricsEndpoints: - path: /metrics port: metrics

Commands:
adminHttp: endpoints: prometheus: {}
adminHttp: host: localhost port: 9999 endpoints: prometheus: {}
apiVersion: monitoring.coreos.com/v1 kind: PodMonitor metadata: name: proxy labels: app: proxy spec: selector: matchLabels: app: proxy namespaceSelector: matchNames: - proxy podMetricsEndpoints: - path: /metrics port: metrics
Chapter 10. Related information You can refer to the following instructional materials: Upgrade your Red Hat Enterprise Linux Infrastructure Red Hat Enterprise Linux technology capabilities and limits Supported in-place upgrade paths for Red Hat Enterprise Linux In-place upgrade Support Policy Considerations in adopting RHEL 9 Customizing your Red Hat Enterprise Linux in-place upgrade Automating your Red Hat Enterprise Linux pre-upgrade report workflow Using configuration management systems to automate parts of the Leapp pre-upgrade and upgrade process on Red Hat Enterprise Linux Upgrading from RHEL 7 to RHEL 8 Converting from a Linux distribution to RHEL using the Convert2RHEL utility Upgrading SAP environments from RHEL 8 to RHEL 9 Red Hat Insights Documentation Upgrades-related Knowledgebase articles and solutions (Red Hat Knowledgebase) The best practices and recommendations for performing RHEL Upgrade using Leapp Leapp upgrade FAQ (Frequently Asked Questions)

Commands:
Chapter 2. About Red Hat OpenShift Pipelines Red Hat OpenShift Pipelines is a cloud-native, continuous integration and continuous delivery (CI/CD) solution based on Kubernetes resources. It uses Tekton building blocks to automate deployments across multiple platforms by abstracting away the underlying implementation details. Tekton introduces a number of standard custom resource definitions (CRDs) for defining CI/CD pipelines that are portable across Kubernetes distributions. Note Because Red Hat OpenShift Pipelines releases on a different cadence from OpenShift Container Platform, the Red Hat OpenShift Pipelines documentation is now available as separate documentation sets for each minor version of the product. The Red Hat OpenShift Pipelines documentation is available at https://docs.openshift.com/pipelines/ . Documentation for specific versions is available using the version selector drop-down list, or directly by adding the version to the URL, for example, https://docs.openshift.com/pipelines/1.15 . In addition, the Red Hat OpenShift Pipelines documentation is also available on the Red Hat Customer Portal at https://access.redhat.com/documentation/en-us/red_hat_openshift_pipelines/ . For additional information about the Red Hat OpenShift Pipelines life cycle and supported platforms, refer to the Platform Life Cycle Policy .

Commands:
Chapter 1. Creating a software bill of materials manifest file Red Hat Trusted Profile Analyzer can analyze both CycloneDX and Software Package Data Exchange (SPDX) SBOM formats by using the JSON file format. Many open source tools are available to you for creating Software Bill of Materials (SBOM) manifest files from container images, or for your application. For this procedure we are going to use the Syft tool. Important Currently, Trusted Profile Analyzer only supports CycloneDX version 1.3, 1.4, and 1.5, along with SPDX version 2.2, and 2.3. Prerequisites Install Syft for your workstation platform: Red Hat Ecosystem Catalog GitHub Procedure To create an SBOM by using a container image. CycloneDX format: Syntax syft IMAGE_PATH -o cyclonedx-json@1.5 Example USD syft registry:example.io/hello-world:latest -o cyclonedx-json@1.5 SPDX format: Syntax syft IMAGE_PATH -o spdx-json@2.3 Example USD syft registry:example.io/hello-world:latest -o spdx-json@2.3 Note Syft supports many types of container image sources. See the official supported source list on Syft's GitHub site . To create an SBOM by scanning the local file system. CycloneDX format: Syntax syft dir: DIRECTORY_PATH -o cyclonedx-json@1.5 syft file: FILE_PATH -o cyclonedx-json@1.5 Example USD syft dir:. -o cyclonedx-json@1.5 USD syft file:/example-binary -o cyclonedx-json@1.5 SPDX format: Syntax syft dir: DIRECTORY_PATH -o spdx-json@2.3 syft file: FILE_PATH -o spdx-json@2.3 Example USD syft dir:. -o spdx-json@2.3 USD syft file:/example-binary -o spdx-json@2.3 Additional resources Scanning an SBOM manifest file by using the Red Hat Trusted Profile Analyzer managed service. National Telecommunications and Information Administration's (NTIA) How-to Guide on SBOM generation .

Commands:
syft IMAGE_PATH -o cyclonedx-json@1.5
syft registry:example.io/hello-world:latest -o cyclonedx-json@1.5
syft IMAGE_PATH -o spdx-json@2.3
syft registry:example.io/hello-world:latest -o spdx-json@2.3
syft dir: DIRECTORY_PATH -o cyclonedx-json@1.5 syft file: FILE_PATH -o cyclonedx-json@1.5
syft dir:. -o cyclonedx-json@1.5 syft file:/example-binary -o cyclonedx-json@1.5
syft dir: DIRECTORY_PATH -o spdx-json@2.3 syft file: FILE_PATH -o spdx-json@2.3
syft dir:. -o spdx-json@2.3 syft file:/example-binary -o spdx-json@2.3
3.16. Port Mirroring Port mirroring copies layer 3 network traffic on a given logical network and host to a virtual interface on a virtual machine. This virtual machine can be used for network debugging and tuning, intrusion detection, and monitoring the behavior of other virtual machines on the same host and logical network. The only traffic copied is internal to one logical network on one host. There is no increase in traffic on the network external to the host. However, a virtual machine with port mirroring enabled uses more host CPU and RAM than other virtual machines. Port mirroring is enabled or disabled in the vNIC profiles of logical networks, and has the following limitations: Hot linking vNICs with a profile that has port mirroring enabled is not supported. Port mirroring cannot be altered when the vNIC profile is attached to a virtual machine. Given the above limitations, it is recommended that you enable port mirroring on an additional, dedicated vNIC profile. Important Enabling port mirroring reduces the privacy of other network users.

Commands:
Chapter 12. Accessing the RADOS Object Gateway S3 endpoint Users can access the RADOS Object Gateway (RGW) endpoint directly. Prerequisites A running OpenShift Data Foundation Platform Procedure Run oc get service command to get the RGW service name. Run oc expose command to expose the RGW service. Replace <RGW-service name> with the RGW service name from the step. Replace <route name> with a route you want to create for the RGW service. For example: Run oc get route command to confirm oc expose is successful and there is an RGW route. Example output: Verification To verify the ENDPOINT , run the following command: Replace <ENDPOINT> with the route that you get from the command in step 3. For example: Important To get the access key and secret of the default user ocs-storagecluster-cephobjectstoreuser , run the following commands: Access key: Secret key:

Commands:
oc get service -n openshift-storage NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE (...) rook-ceph-rgw-ocs-storagecluster-cephobjectstore ClusterIP 172.30.145.254 <none> 80/TCP,443/TCP 5d7h (...)
oc expose svc/<RGW service name> --hostname=<route name>
oc expose svc/rook-ceph-rgw-ocs-storagecluster-cephobjectstore --hostname=rook-ceph-rgw-ocs.ocp.host.example.com
oc get route -n openshift-storage
NAME HOST/PORT PATH rook-ceph-rgw-ocs-storagecluster-cephobjectstore rook-ceph-rgw-ocs.ocp.host.example.com SERVICES PORT TERMINATION WILDCARD rook-ceph-rgw-ocs-storagecluster-cephobjectstore http <none>
aws s3 --no-verify-ssl --endpoint <ENDPOINT> ls
aws s3 --no-verify-ssl --endpoint http://rook-ceph-rgw-ocs.ocp.host.example.com ls
oc get secret rook-ceph-object-user-ocs-storagecluster-cephobjectstore-ocs-storagecluster-cephobjectstoreuser -n openshift-storage -o yaml | grep -w "AccessKey:" | head -n1 | awk '{print USD2}' | base64 --decode
oc get secret rook-ceph-object-user-ocs-storagecluster-cephobjectstore-ocs-storagecluster-cephobjectstoreuser -n openshift-storage -o yaml | grep -w "SecretKey:" | head -n1 | awk '{print USD2}' | base64 --decode
14.5.9. Setting Network Interface Bandwidth Parameters domiftune sets the guest virtual machine's network interface bandwidth parameters. The following format should be used: The only required parameter is the domain name and interface device of the guest virtual machine, the --config , --live , and --current functions the same as in Section 14.19, "Setting Schedule Parameters" . If no limit is specified, it will query current network interface setting. Otherwise, alter the limits with the following options: <interface-device> This is mandatory and it will set or query the domain's network interface's bandwidth parameters. interface-device can be the interface's target name (<target dev='name'/>), or the MAC address. If no --inbound or --outbound is specified, this command will query and show the bandwidth settings. Otherwise, it will set the inbound or outbound bandwidth. average,peak,burst is the same as in attach-interface command. Refer to Section 14.3, "Attaching Interface Devices"

Commands:
virsh domiftune domain interface-device [[--config] [--live] | [--current]] [--inbound average,peak,burst] [--outbound average,peak,burst]
B.96.5. RHSA-2011:0475 - Critical: thunderbird security update An updated thunderbird package that fixes several security issues is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Mozilla Thunderbird is a standalone mail and newsgroup client. CVE-2011-0080 , CVE-2011-0081 Several flaws were found in the processing of malformed HTML content. An HTML mail message containing malicious content could possibly lead to arbitrary code execution with the privileges of the user running Thunderbird. CVE-2011-0078 An arbitrary memory write flaw was found in the way Thunderbird handled out-of-memory conditions. If all memory was consumed when a user viewed a malicious HTML mail message, it could possibly lead to arbitrary code execution with the privileges of the user running Thunderbird. CVE-2011-0077 An integer overflow flaw was found in the way Thunderbird handled the HTML frameset tag. An HTML mail message with a frameset tag containing large values for the "rows" and "cols" attributes could trigger this flaw, possibly leading to arbitrary code execution with the privileges of the user running Thunderbird. CVE-2011-0075 A flaw was found in the way Thunderbird handled the HTML iframe tag. An HTML mail message with an iframe tag containing a specially-crafted source address could trigger this flaw, possibly leading to arbitrary code execution with the privileges of the user running Thunderbird. CVE-2011-0074 A flaw was found in the way Thunderbird displayed multiple marquee elements. A malformed HTML mail message could cause Thunderbird to execute arbitrary code with the privileges of the user running Thunderbird. CVE-2011-0073 A flaw was found in the way Thunderbird handled the nsTreeSelection element. Malformed content could cause Thunderbird to execute arbitrary code with the privileges of the user running Thunderbird. CVE-2011-0071 A directory traversal flaw was found in the Thunderbird resource:// protocol handler. Malicious content could cause Thunderbird to access arbitrary files accessible to the user running Thunderbird. CVE-2011-0070 A double free flaw was found in the way Thunderbird handled "application/http-index-format" documents. A malformed HTTP response could cause Thunderbird to execute arbitrary code with the privileges of the user running Thunderbird. All Thunderbird users should upgrade to this updated package, which resolves these issues. All running instances of Thunderbird must be restarted for the update to take effect.

Commands:
Technology preview The Streams for Apache Kafka Console is a technology preview. Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete; therefore, Red Hat does not recommend implementing any Technology Preview features in production environments. This Technology Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about the support scope, see Technology Preview Features Support Scope .

Commands: