mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix B. Updating the deployment configuration of an example application The deployment configuration for an example application contains information related to deploying and running the application in OpenShift, such as route information or readiness probe location. The deployment configuration of an example application is stored in a set of YAML files. For examples that use the OpenShift Maven plugin, the YAML files are located in the src/main/jkube/ directory. For examples using Nodeshift, the YAML files are located in the .nodeshift directory. Important The deployment configuration files used by the OpenShift Maven plugin and Nodeshift do not have to be full OpenShift resource definitions. Both OpenShift Maven plugin and Nodeshift can take the deployment configuration files and add some missing information to create a full OpenShift resource definition. The resource definitions generated by the OpenShift Maven plugin are available in the target/classes/META-INF/jkube/ directory. The resource definitions generated by Nodeshift are available in the tmp/nodeshift/resource/ directory. Prerequisites An existing example project. The oc CLI client installed. Procedure Edit an existing YAML file or create an additional YAML file with your configuration update. For example, if your example already has a YAML file with a readinessProbe configured, you could change the path value to a different available path to check for readiness: spec: template: spec: containers: readinessProbe: httpGet: path: /path/to/probe port: 8080 scheme: HTTP ... If a readinessProbe is not configured in an existing YAML file, you can also create a new YAML file in the same directory with the readinessProbe configuration. Deploy the updated version of your example using Maven or npm. Verify that your configuration updates show in the deployed version of your example. USD oc export all --as-template='my-template' apiVersion: template.openshift.io/v1 kind: Template metadata: creationTimestamp: null name: my-template objects: - apiVersion: template.openshift.io/v1 kind: DeploymentConfig ... spec: ... template: ... spec: containers: ... livenessProbe: failureThreshold: 3 httpGet: path: /path/to/different/probe port: 8080 scheme: HTTP initialDelaySeconds: 60 periodSeconds: 30 successThreshold: 1 timeoutSeconds: 1 ... Additional resources If you updated the configuration of your application directly using the web-based console or the oc CLI client, export and add these changes to your YAML file. Use the oc export all command to show the configuration of your deployed application.

Commands:
spec: template: spec: containers: readinessProbe: httpGet: path: /path/to/probe port: 8080 scheme: HTTP
oc export all --as-template='my-template' apiVersion: template.openshift.io/v1 kind: Template metadata: creationTimestamp: null name: my-template objects: - apiVersion: template.openshift.io/v1 kind: DeploymentConfig spec: template: spec: containers: livenessProbe: failureThreshold: 3 httpGet: path: /path/to/different/probe port: 8080 scheme: HTTP initialDelaySeconds: 60 periodSeconds: 30 successThreshold: 1 timeoutSeconds: 1
Chapter 3. Repositories Red Hat Enterprise Linux 9 is distributed through two main repositories: BaseOS AppStream Both repositories are required for a basic RHEL installation, and are available with all RHEL subscriptions. Content in the BaseOS repository is intended to provide the core set of the underlying OS functionality that provides the foundation for all installations. This content is available in the RPM format and is subject to support terms similar to those in releases of RHEL. For more information, see the Scope of Coverage Details document. Content in the AppStream repository includes additional user-space applications, runtime languages, and databases in support of the varied workloads and use cases. In addition, the CodeReady Linux Builder repository is available with all RHEL subscriptions. It provides additional packages for use by developers. Packages included in the CodeReady Linux Builder repository are unsupported. Additional resources Package manifest

Commands:
10.5.61. ProxyRequests To configure the Apache HTTP Server to function as a proxy server, remove the hash mark ( # ) from the beginning of the <IfModule mod_proxy.c> line, the ProxyRequests, and each line in the <Proxy> stanza. Set the ProxyRequests directive to On , and set which domains are allowed access to the server in the Allow from directive of the <Proxy> stanza.

Commands:
Chapter 56. JSON Gson Gson is a Data Format which uses the Gson Library . from("activemq:My.Queue"). marshal().json(JsonLibrary.Gson). to("mqseries:Another.Queue"); 56.1. Dependencies When using json-gson with Red Hat build of Camel Spring Boot make sure to use the following Maven dependency to have support for auto configuration: <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-gson-starter</artifactId> </dependency> 56.2. Gson Options The JSON Gson dataformat supports 3 options, which are listed below. Name Default Java Type Description prettyPrint Boolean To enable pretty printing output nicely formatted. Is by default false. unmarshalType String Class name of the java type to use when unmarshalling. contentTypeHeader Boolean Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON. 56.3. Spring Boot Auto-Configuration The component supports 4 options, which are listed below. Name Description Default Type camel.dataformat.json-gson.content-type-header Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON. true Boolean camel.dataformat.json-gson.enabled Whether to enable auto configuration of the json-gson data format. This is enabled by default. Boolean camel.dataformat.json-gson.pretty-print To enable pretty printing output nicely formatted. Is by default false. false Boolean camel.dataformat.json-gson.unmarshal-type Class name of the java type to use when unmarshalling. String

Commands:
from("activemq:My.Queue"). marshal().json(JsonLibrary.Gson). to("mqseries:Another.Queue");
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-gson-starter</artifactId> </dependency>
Chapter 17. command This chapter describes the commands under the command command. 17.1. command list List recognized commands by group Usage: Table 17.1. Optional Arguments Value Summary -h, --help Show this help message and exit --group <group-keyword> Show commands filtered by a command group, for example: identity, volume, compute, image, network and other keywords Table 17.2. Output Formatters Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated Table 17.3. CSV Formatter Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 17.4. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 17.5. Table Formatter Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack command list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--group <group-keyword>]
Chapter 6. Configuring Your Maven Repositories 6.1. About The Provided Maven Repositories A set of repositories containing artifacts required to build applications is provided with this release. Maven must be configured to use these repositories and the Maven Central Repository in order to provide correct build functionality. Two interchangeable sets of repositories ensuring the same functionality are provided. The first set is available for download and is stored in a local file system. The second set is hosted online for use as remote repositories. If you provided the location of Maven's settings.xml file during installation, Maven is already configured to use the online repositories. Important Maven repositories are also subject to patching. After a patch is released, it is applied to the remote repositories. Both original and patched artifacts reside there, only the versions of artifacts are incremented. It is user's responsibility to pick the new version of the patched artifact in their dependency management. For more information see https://access.redhat.com/site/maven-repository .

Commands:
7.72. gnome-terminal 7.72.1. RHBA-2012:1311 - gnome-terminal bug fix update Updated gnome-terminal packages that fix one bug are now available for Red Hat Enterprise Linux 6. Gnome-terminal is a terminal emulator for GNOME. It supports translucent backgrounds, opening multiple terminals in a single window (tabs) and clickable URLs. Bug Fix BZ#819796 Prior to this update, gnome-terminal was not completely localized into Asamese. With this update, the Assamese locale has been updated. All gnome-terminal users are advised to upgrade to these updated packages, which fix this bug.

Commands:
5.2.12. /proc/iomem This file shows you the current map of the system's memory for each physical device: The first column displays the memory registers used by each of the different types of memory. The second column lists the kind of memory located within those registers and displays which memory registers are used by the kernel within the system RAM or, if the network interface card has multiple Ethernet ports, the memory registers assigned for each port.

Commands:
00000000-0009fbff : System RAM 0009fc00-0009ffff : reserved 000a0000-000bffff : Video RAM area 000c0000-000c7fff : Video ROM 000f0000-000fffff : System ROM 00100000-07ffffff : System RAM 00100000-00291ba8 : Kernel code 00291ba9-002e09cb : Kernel data e0000000-e3ffffff : VIA Technologies, Inc. VT82C597 [Apollo VP3] e4000000-e7ffffff : PCI Bus #01 e4000000-e4003fff : Matrox Graphics, Inc. MGA G200 AGP e5000000-e57fffff : Matrox Graphics, Inc. MGA G200 AGP e8000000-e8ffffff : PCI Bus #01 e8000000-e8ffffff : Matrox Graphics, Inc. MGA G200 AGP ea000000-ea00007f : Digital Equipment Corporation DECchip 21140 [FasterNet] ea000000-ea00007f : tulip ffff0000-ffffffff : reserved
5.106. imsettings 5.106.1. RHBA-2012:0768 - imsettings bug fix update Updated imsettings packages that fix one bug are now available for Red Hat Enterprise Linux 6. IMSettings provides command line tools and a library to configure and control input-methods settings. Users normally access it through the "im-chooser" GUI tool. Bug Fix BZ# 713433 Prior to this update, the IMSettings daemon unexpectedly invalidated the pointer after obtaining a new pointer. This update modifies IMSettings so that the code is updated after all transactions are finished. All users of imsettings are advised to upgrade to these updated packages, which fix this bug.

Commands:
7.228. vsftpd 7.228.1. RHBA-2015:1408 - vsftpd bug fix update Updated vsftpd packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The vsftpd packages include a Very Secure File Transfer Protocol (FTP) daemon, which is used to serve files over a network. Bug Fixes BZ# 1063401 Prior to this update, the "local_max_rate" option did not work as expected. As a consequence, the transmission speed was significantly lower. This update extends the types of variables for calculating and accumulating the amount of transferred data and postpones the start of evaluation after the tenth evaluation. BZ# 1092877 Previously, vsftpd server could not handle the use of "pam_exec.so" in the "pam.d" configuration file. Consequently, the vsftpd server considered new processes created by the "pam_exe.so" module to be its own and therefore attempted to catch them. When the processes were caught by "pam_exec.so", the vsftpd server became unresponsive. A patch has been applied to fix this bug, and the vsftpd server no longer hangs in the described situation. Users of vsftpd are advised to upgrade to these updated packages, which fix these bugs. The vsftpd daemon must be restarted for this update to take effect.

Commands:
4.166. lsof 4.166.1. RHEA-2011:1753 - lsof enhancement update An updateed lsof package that adds one enhancement is now available for Red Hat Enterprise Linux 6. The lsof package provides the LiSt Open Files (LSOF) tool to list information about files that are open and running on a Linux/UNIX system. Enhancement BZ# 671480 This enhancement update adds the new option +|-e s to lsof which exempts file systems with the path name "s" from being subjected to kernel function calls that might block. Note, that only the first +|-e argument is processed and the rest is ignored. All users of lsof are advised to upgrade to this updated package, which add this enhancement.

Commands:
7.81. hsqldb 7.81.1. RHBA-2013:0334 - hsqldb bug fix update Updated hsqldb packages that fix one bug are now available for Red Hat Enterprise Linux 6. The hsqldb packages provide a relational database management system written in Java. The Hyper Structured Query Language Database (HSQLDB) contains a JDBC driver to support a subset of ANSI-92 SQL. Bug Fix BZ# 827343 Prior to this update, the hsqldb database did not depend on java packages of version 1:1.6.0 or later. As a consequence, the build-classpath command failed on systems without the java-1.6.0-openjdk package installed and the hsqldb packages could be installed incorrectly. This update adds a requirement for java-1.6.0-openjdk. Now, the installation of hsqldb proceeds correctly as expected. All users of hsqldb are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 23. Subscription management The following chapter contains the most notable changes to subscription management between RHEL 8 and RHEL 9. 23.1. Notable changes to subscription management Merged system purpose commands under the subscription-manager syspurpose command Previously, there were two different commands to set system purpose attributes; syspurpose and subscription-manager . To unify all the system purpose attributes under one module, all the addons , role , service-level , and usage commands from subscription-manager have been moved to the new submodule, subscription-manager syspurpose . Existing subscription-manager commands outside the new submodule are deprecated. The separate package ( python3-syspurpose ) that provides the syspurpose command line tool has been removed in RHEL 9. This update provides a consistent way to view, set, and update all system purpose attributes using a single command of subscription-manager. This command replaces all the existing system purpose commands with their equivalent versions available as a new subcommand. For example, subscription-manager role --set SystemRole becomes subscription-manager syspurpose role --set SystemRole and so on. For complete information about the new commands, options, and other attributes, see the SYSPURPOSE OPTIONS section in the subscription-manager man page or Configuring system purpose using the subscription manager command line tool . virt-who now uses /etc/virt-who.conf for global options instead of /etc/sysconfig/virt-who In RHEL 9, the global options for the virt-who utility on your system are stored in the /etc/virt-who.conf file. Therefore, the /etc/sysconfig/virt-who file is not being used any more, and has been removed.

Commands:
B.94. systemtap B.94.1. RHSA-2010:0894 - Important: systemtap security update Updated systemtap packages that fix two security issues are now available for Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this update as having important security impact. 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. SystemTap is an instrumentation system for systems running the Linux kernel, version 2.6. Developers can write scripts to collect data on the operation of the system. staprun, the SystemTap runtime tool, is used for managing SystemTap kernel modules (for example, loading them). CVE-2010-4170 It was discovered that staprun did not properly sanitize the environment before executing the modprobe command to load an additional kernel module. A local, unprivileged user could use this flaw to escalate their privileges. CVE-2010-4171 It was discovered that staprun did not check if the module to be unloaded was previously loaded by SystemTap. A local, unprivileged user could use this flaw to unload an arbitrary kernel module that was not in use. Note Note: After installing this update, users already in the stapdev group must be added to the stapusr group in order to be able to run the staprun tool. Red Hat would like to thank Tavis Ormandy for reporting these issues. SystemTap users should upgrade to these updated packages, which contain backported patches to correct these issues.

Commands:
5.123. java-1.6.0-sun 5.123.1. RHSA-2013:0236 - Critical: java-1.6.0-sun security update Updated java-1.6.0-sun packages that fix several security issues are now available for Red Hat Enterprise Linux 5 and 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. 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. Oracle Java SE version 6 includes the Oracle Java Runtime Environment and the Oracle Java Software Development Kit. Security Fix CVE-2012-1541 , CVE-2012-3213 , CVE-2012-3342 , CVE-2013-0351 , CVE-2013-0409 , CVE-2013-0419 , CVE-2013-0423 , CVE-2013-0424 , CVE-2013-0425 , CVE-2013-0426 , CVE-2013-0427 , CVE-2013-0428 , CVE-2013-0429 , CVE-2013-0430 , CVE-2013-0432 , CVE-2013-0433 , CVE-2013-0434 , CVE-2013-0435 , CVE-2013-0438 , CVE-2013-0440 , CVE-2013-0441 , CVE-2013-0442 , CVE-2013-0443 , CVE-2013-0445 , CVE-2013-0446 , CVE-2013-0450 , CVE-2013-1473 , CVE-2013-1475 , CVE-2013-1476 , CVE-2013-1478 , CVE-2013-1480 , CVE-2013-1481 This update fixes several vulnerabilities in the Oracle Java Runtime Environment and the Oracle Java Software Development Kit. Further information about these flaws can be found on the Oracle Java SE Critical Patch Update Advisory page . All users of java-1.6.0-sun are advised to upgrade to these updated packages, which provide Oracle Java 6 Update 39. All running instances of Oracle Java must be restarted for the update to take effect. 5.123.2. RHSA-2012:1392 - Critical: java-1.6.0-sun security update Updated java-1.6.0-sun packages that fix several security issues are now available for Red Hat Enterprise Linux 5 and 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. 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. Oracle Java SE version 6 includes the Oracle Java Runtime Environment and the Oracle Java Software Development Kit. Security Fix CVE-2012-0547 , CVE-2012-1531 , CVE-2012-1532 , CVE-2012-1533 , CVE-2012-3143 , CVE-2012-3159 , CVE-2012-3216 , CVE-2012-4416 , CVE-2012-5068 , CVE-2012-5069 , CVE-2012-5071 , CVE-2012-5072 , CVE-2012-5073 , CVE-2012-5075 , CVE-2012-5077 , CVE-2012-5079 , CVE-2012-5081 , CVE-2012-5083 , CVE-2012-5084 , CVE-2012-5085 , CVE-2012-5086 , CVE-2012-5089 This update fixes several vulnerabilities in the Oracle Java Runtime Environment and the Oracle Java Software Development Kit. Further information about these flaws can be found on the Oracle Java SE Critical Patch Update Advisory and Oracle Security Alert pages . All users of java-1.6.0-sun are advised to upgrade to these updated packages, which provide Oracle Java 6 Update 37. All running instances of Oracle Java must be restarted for the update to take effect.

Commands:
5.6.3.3. Data Migration Most seasoned system administrators would be impressed by LVM capabilities so far, but they would also be asking themselves this question: What happens if one of the drives making up a logical volume starts to fail? The good news is that most LVM implementations include the ability to migrate data off of a particular physical drive. For this to work, there must be sufficient reserve capacity left to absorb the loss of the failing drive. Once the migration is complete, the failing drive can then be replaced and added back into the available storage pool.

Commands:
4.2. Setting up Google Compute Engine To set up Google Compute engine, perform the following steps: 4.2.1. SSH Keys SSH keys must be generated and registered with the Google Compute Engine project to connect via standard SSH. You can SSH directly to the instance public IP addresses after it is generated. Generate an SSH key pair for use with Google Compute Engine using the following command: In the Google Developers Console, click Computer > Compute Engine > Metadata > SSH Keys > Edit . Enter the output generated from ~/.ssh/google_compute_engine.pub file, and click Save . To enable SSH agent to use this identity file for each new local console session, run the following command on the console: Adding the below line to your ~/.ssh/config file helps you automate this command. You can now connect via standard SSH to the new VM instances created in your Google Compute Engine project. The gcloud compute config-ssh command from the Google Cloud SDK populates your ~/.ssh/config file with aliases that allows simple SSH connections by instance name. 4.2.2. Setting up Quota The minimum persistent disk quotas listed below are required for this deployment. It may be necessary to request a quota increase from Google. Local region (see US-CENTRAL1 illustration in Section 4.1.3, "Primary Storage Pool Configuration" ) Total persistent disk reserved (GB) >= 206,000 CPUs >= 100 Remote region (see EUROPE-WEST1 illustration in Section 4.1.4, "Secondary Storage Pool Configuration" ) Total persistent disk reserved (GB) >= 103,000 CPUs >=40

Commands:
ssh-keygen -t rsa -f ~/.ssh/google_compute_engine
ssh-add ~/.ssh/google_compute_engine
IdentityFile ~/.ssh/google_compute_engine
ssh -i ~/.ssh/google_compute_engine <username>@<instance_external_ip>