mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 11. Browsing files on a network share You can connect to a network share provided by a server and browse the files on the server like local files. You can download or upload files using the file browser. 11.1. GVFS URI format for network shares GNOME uses the GVFS URI format to refer to network shares and files on them. When you connect to a network share from GNOME, you provide the address to the network share in the following format. A URL, or uniform resource locator, is a form of address that refers to a location or file on a network. The address is formatted like this: The basic GVFS URI format takes the following syntax: The scheme specifies the protocol or type of server. The example.com portion of the address is called the domain name. If a username is required, it is inserted before the server name: You can also specify the user name or the port number to the network share: Table 11.1. Common network share protocols Protocol GVFS URI example SSH ssh://user@server.example.com/path NFS nfs://server/path Windows SMB smb://server/Share WebDAV dav://example.server.com/path Public FTP ftp://ftp.example.com/path Authenticated FTP ftp://user@ftp.example.com/path Additional resources The GVFS system The format of the GVFS URI string 11.2. Mounting a storage volume in GNOME You can manually mount a local storage volume or a network share in the Files application. Procedure Open the Files application. Click Other Locations in the side bar. The window lists all connected storage volumes and all network shares that are publicly available on your local area network. If you can see the volume or network share in this list, mount it by clicking the item. If you want to connect to a different network share, use the following steps. Enter the GVFS URI string to the network share in the Connect to Server field. Press Connect . If the dialog asks you for login credentials, enter your name and password into the relevant fields. When the mounting process finishes, you can browse the files on the volume or network share. 11.3. Unmounting a storage volume in GNOME You can unmount a storage volume, a network share, or another resource in the Files application. Procedure Open the Files application. In the side bar, click the Unmount (⏏) icon to the chosen mount. Wait until the mount disappears from the side bar or a notification about the safe removal appears. 11.4. Additional resources Managing storage volumes in GNOME Mounting NFS shares Mounting an SMB Share on Red Hat Enterprise Linux

Commands:
protocol :// server.example.com / folder/file
protocol :// user @ server.example.com : port / folder/file
Chapter 13. Editing applications You can edit the configuration and the source code of the application you create using the Topology view. 13.1. Prerequisites You have the appropriate roles and permissions in a project to create and modify applications in OpenShift Container Platform. You have created and deployed an application on OpenShift Container Platform using the Developer perspective . You have logged in to the web console and have switched to the Developer perspective . 13.2. Editing the source code of an application using the Developer perspective You can use the Topology view in the Developer perspective to edit the source code of your application. Procedure In the Topology view, click the Edit Source code icon, displayed at the bottom-right of the deployed application, to access your source code and modify it. Note This feature is available only when you create applications using the From Git , From Catalog , and the From Dockerfile options. If the Eclipse Che Operator is installed in your cluster, a Che workspace ( ) is created and you are directed to the workspace to edit your source code. If it is not installed, you will be directed to the Git repository ( ) your source code is hosted in. 13.3. Editing the application configuration using the Developer perspective You can use the Topology view in the Developer perspective to edit the configuration of your application. Note Currently, only configurations of applications created by using the From Git , Container Image , From Catalog , or From Dockerfile options in the Add workflow of the Developer perspective can be edited. Configurations of applications created by using the CLI or the YAML option from the Add workflow cannot be edited. Prerequisites Ensure that you have created an application using the From Git , Container Image , From Catalog , or From Dockerfile options in the Add workflow. Procedure After you have created an application and it is displayed in the Topology view, right-click the application to see the edit options available. Figure 13.1. Edit application Click Edit application-name to see the Add workflow you used to create the application. The form is pre-populated with the values you had added while creating the application. Edit the necessary values for the application. Note You cannot edit the Name field in the General section, the CI/CD pipelines, or the Create a route to the application field in the Advanced Options section. Click Save to restart the build and deploy a new image. Figure 13.2. Edit and redeploy application

Commands:
Chapter 9. Metrics A metrics endpoint, /api/v2/metrics/ is available in the API that produces instantaneous metrics about automation controller, which can be consumed by system monitoring software such as the open source project Prometheus. The types of data shown at the metrics/ endpoint are Content-type: text/plain and application/json . This endpoint contains useful information, such as counts of how many active user sessions there are, or how many jobs are actively running on each automation controller node. You can configure Prometheus to scrape these metrics from automation controller by hitting the automation controller metrics endpoint and storing this data in a time-series database. Clients can later use Prometheus in conjunction with other software such as Grafana or Metricbeat to visualize that data and set up alerts. 9.1. Setting up Prometheus To set up and use Prometheus, you must install Prometheus on a virtual machine or container. For more information, see the First steps with Prometheus documentation. Procedure In the Prometheus configuration file (typically prometheus.yml ), specify a <token_value> , a valid username and password for an automation controller user that you have created, and a <controller_host> . Note Alternatively, you can provide an OAuth2 token (which can be generated at /api/v2/users/N/personal_tokens/ ). By default, the configuration assumes a user with username= admin and password= password . Using an OAuth2 Token, created at the /api/v2/tokens endpoint to authenticate Prometheus with automation controller, the following example provides a valid scrape configuration if the URL for your automation controller's metrics endpoint is /https://controller_host:443/metrics . scrape_configs - job_name: 'controller' tls_config: insecure_skip_verify: True metrics_path: /api/v2/metrics scrape_interval: 5s scheme: https bearer_token: <token_value> # basic_auth: # username: admin # password: password static_configs: - targets: - <controller_host> For help configuring other aspects of Prometheus, such as alerts and service discovery configurations, see the Prometheus configuration documentation. If Prometheus is already running, you must restart it to apply the configuration changes by making a POST to the reload endpoint, or by killing the Prometheus process or service. Use a browser to navigate to your graph in the Prometheus UI at /http://<your_prometheus>:9090/graph and test out some queries. For example, you can query the current number of active automation controller user sessions by executing: awx_sessions_total{type="user"} . Refer to the metrics endpoint in the automation controller API for your instance ( api/v2/metrics ) for more ways to query.

Commands:
scrape_configs - job_name: 'controller' tls_config: insecure_skip_verify: True metrics_path: /api/v2/metrics scrape_interval: 5s scheme: https bearer_token: <token_value> # basic_auth: # username: admin # password: password static_configs: - targets: - <controller_host>
4.3. Creating a Virtual Machine with Virtual Machine Manager The Virtual Machine Manager , also known as virt-manager , is a graphical tool for quick deployment of virtual machines in Red Hat Enterprise Linux. In this tutorial, you will become familiar with its basic functions and will be able to use Virtual Machine Manager to create a virtual machine. 4.3.1. Introduction to Virtual Machine Manager To open the Virtual Machine Manager , click Applications System Tools Virtual Machine Manager ; or open the terminal and run the virt-manager command. The following image shows the Virtual Machine Manager interface. This interface enables you to control all of your virtual machines from one central location. Figure 4.1. The Virtual Machine Manager interface Commonly used interface elements include: Create new virtual machine : Click here to create a new virtual machine. Virtual machines : A list of configured connections and all guest virtual machines associated with them. When a virtual machine is created, it will be listed here. When a guest is running, an animated graph shows the guest's CPU usage in the CPU usage column. After selecting a virtual machine from this list, use the following buttons to control the selected virtual machine's state: Open : Opens the guest virtual machine console and details in a new window. Run : Turns on the virtual machine. Pause : Pauses the virtual machine. Shut down : Shuts down the virtual machine. Clicking on the arrow displays a drop-down menu with several options for turning off the virtual machine, including Reboot, Shut Down, Force Reset, Force Off, and Save. Right-clicking on a virtual machine shows a menu with more functions, including: Clone : Clones the virtual machine. Migrate : Migrates the virtual machine to another host. Delete : Deletes the virtual machine.

Commands:
Chapter 1. Overview Read this document to understand how to create, configure, and allocate storage to core services or hosted applications in Red Hat OpenShift Data Foundation. Chapter 2, Storage classes shows you how to create custom storage classes. Chapter 3, Block pools provides you with information on how to create, update and delete block pools. Chapter 4, Configure storage for OpenShift Container Platform services shows you how to use OpenShift Data Foundation for core OpenShift Container Platform services. Chapter 6, Backing OpenShift Container Platform applications with OpenShift Data Foundation provides information about how to configure OpenShift Container Platform applications to use OpenShift Data Foundation. Adding file and object storage to an existing external OpenShift Data Foundation cluster Chapter 8, How to use dedicated worker nodes for Red Hat OpenShift Data Foundation provides information about how to use dedicated worker nodes for Red Hat OpenShift Data Foundation. Chapter 9, Managing Persistent Volume Claims provides information about managing Persistent Volume Claim requests, and automating the fulfillment of those requests. Chapter 10, Reclaiming space on target volumes shows you how to reclaim the actual available storage space. Chapter 12, Volume Snapshots shows you how to create, restore, and delete volume snapshots. Chapter 13, Volume cloning shows you how to create volume clones. Chapter 14, Managing container storage interface (CSI) component placements provides information about setting tolerations to bring up container storage interface component on the nodes.

Commands:
7.6. RHEA-2014:1434 - new package: google-crosextra-carlito-fonts A new google-crosextra-carlito-fonts package is now available for Red Hat Enterprise Linux 6. The google-crosextra-carlito-fonts package provides the Carlito font family. Carlito is metric-compatible with Calibri font. Carlito comes in regular, bold, italic, and bold italic faces. The family covers Latin-Greek-Cyrillic (not a complete set, though) with about 2,000 glyphs. It has the same character coverage as Calibri. This font is sans-serif typeface family based on Lato. This enhancement update adds the google-crosextra-carlito-fonts package to Red Hat Enterprise Linux 6. (BZ# 1025628 ) All users who require google-crosextra-carlito-fonts are advised to install this new package.

Commands:
Chapter 1. Benefits of Red Hat Developer Hub Increased developer productivity Eliminates common organizational challenges, enabling seamless collaboration, and providing clear guidelines for creating, developing, and deploying applications. Unified Self-Service Dashboard Provides development teams with a unified dashboard. Your platform engineering team can curate aspects such as: Git Continuous Integration/Continuous Delivery (CI/CD) Static Application Security Testing (SAST)/Dynamic Application Security Testing (DAST) Supply Chain OpenShift/Kubernetes cluster JIRA Monitoring API Documentation Best practices through software templates Automates organizational best practices by encoding common tasks such as: Creating new applications Running Ansible jobs Establishing CI/CD pipelines for production deployment in Git Scalable technical documentation Code and documentation is in the same repository, eliminating dependencies on proprietary document systems. Efficient onboarding for new developers New developers can adapt quickly and become productive within a short time frame. Robust enterprise Role-Based Access Control (RBAC) Empowers administrators to: Create roles Assign users or groups to roles Implement robust security policies for enhanced access control Additional resources For more information about the different features of Red Hat Developer Hub and how to extend it, see Red Hat Developer Hub overview .

Commands:
Chapter 1. Overview of multiple storage cluster deployments Red Hat OpenShift Data Foundation provides the ability to deploy two storage clusters, where one is internal mode and the other is in external mode. This can be achieved only with the first cluster installed as internal in openshift-storage namespace while the second cluster is installed as the external in openshift-storage-extended namespace. Clusters installed conversely is not currently supported. Supported platforms Bare metal VMware VSphere OpenStack OpenShift Virtualization IBM Cloud IBM Power

Commands:
Common object reference OpenShift Container Platform 4.13 Reference guide common API objects Red Hat OpenShift Documentation Team

Commands:
<quantity> ::= <signedNumber><suffix>
(Note that <suffix> may be empty, from the "" case in <decimalSI>.)
(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)
(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)
type MyAPIObject struct { runtime.TypeMeta `json:",inline"` MyPlugin runtime.Object `json:"myPlugin"` }
type PluginA struct { AOption string `json:"aOption"` }
type MyAPIObject struct { runtime.TypeMeta `json:",inline"` MyPlugin runtime.RawExtension `json:"myPlugin"` }
type PluginA struct { AOption string `json:"aOption"` }
{ "kind":"MyAPIObject", "apiVersion":"v1", "myPlugin": { "kind":"PluginA", "aOption":"foo", }, }
Chapter 111. AclRuleTransactionalIdResource schema reference Used in: AclRule The type property is a discriminator that distinguishes use of the AclRuleTransactionalIdResource type from AclRuleTopicResource , AclRuleGroupResource , AclRuleClusterResource . It must have the value transactionalId for the type AclRuleTransactionalIdResource . Property Description type Must be transactionalId . string name Name of resource for which given ACL rule applies. Can be combined with patternType field to use prefix pattern. string patternType Describes the pattern used in the resource field. The supported types are literal and prefix . With literal pattern type, the resource field will be used as a definition of a full name. With prefix pattern type, the resource name will be used only as a prefix. Default value is literal . string (one of [prefix, literal])

Commands:
Chapter 6. Enabling alert data retention Learn how to configure a retention period for Red Hat Advanced Cluster Security for Kubernetes alerts. With Red Hat Advanced Cluster Security for Kubernetes, you can configure the time to keep historical alerts stored. Red Hat Advanced Cluster Security for Kubernetes then deletes the older alerts after the specified time. By automatically deleting alerts that are no longer needed, you can save storage costs. The alerts for which you can configure the retention period include: Runtime alerts, both unresolved (active) and resolved. Stale deploy-time alerts that do not apply to the current deployment. Note Data retention settings are enabled by default. You can change these settings after the installation. When you upgrade Red Hat Advanced Cluster Security for Kubernetes, data retention settings are not applied unless you have enabled them before. You can configure alert retention settings by using the RHACS portal or the API. The deletion process runs every hour. Currently, you cannot change this. 6.1. Configuring alert data retention You can configure alert retention settings by using the RHACS portal. Prerequisites You must have the Administration role with read and write permissions to configure data retention. Procedure In the RHACS portal, go to Platform Configuration System Configuration . On the System Configuration view header, click Edit . Under the Data Retention Configuration section, update the number of days for each type of data: All Runtime Violations Resolved Deploy-Phase Violations Runtime Violations For Deleted Deployments Images No Longer Deployed Note To save a type of data forever, set the retention period to 0 days. Click Save . Note To configure alert data retention by using Red Hat Advanced Cluster Security for Kubernetes API, view the PutConfig API and related APIs in the ConfigService group in the API reference documentation.

Commands:
Chapter 9. Uninstalling a cluster on OpenStack You can remove a cluster that you deployed to Red Hat OpenStack Platform (RHOSP). 9.1. Removing a cluster that uses installer-provisioned infrastructure You can remove a cluster that uses installer-provisioned infrastructure from your cloud. Note If you deployed your cluster to the AWS C2S Secret Region, the installation program does not support destroying the cluster; you must manually remove the cluster resources. Note After uninstallation, check your cloud provider for any resources not removed properly, especially with User Provisioned Infrastructure (UPI) clusters. There might be resources that the installer did not create or that the installer is unable to access. For example, some Google Cloud resources require IAM permissions in shared VPC host projects, or there might be unused health checks that must be deleted . Prerequisites You have a copy of the installation program that you used to deploy the cluster. You have the files that the installation program generated when you created your cluster. Procedure From the directory that contains the installation program on the computer that you used to install the cluster, run the following command: USD ./openshift-install destroy cluster \ --dir <installation_directory> --log-level info 1 2 1 For <installation_directory> , specify the path to the directory that you stored the installation files in. 2 To view different details, specify warn , debug , or error instead of info . Note You must specify the directory that contains the cluster definition files for your cluster. The installation program requires the metadata.json file in this directory to delete the cluster. Optional: Delete the <installation_directory> directory and the OpenShift Container Platform installation program.

Commands:
./openshift-install destroy cluster --dir <installation_directory> --log-level info 1 2
Chapter 7. Technology Previews Technology Preview features included with Streams for Apache Kafka 2.9. Important 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 . 7.1. Streams for Apache Kafka Proxy Streams for Apache Kafka Proxy is an Apache Kafka protocol-aware 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. As part of the technology preview, you can try the Record Encryption filter and Record Validation filter. The Record Encryption filter uses industry-standard cryptographic techniques to apply encryption to Kafka messages, ensuring the confidentiality of data stored in the Kafka Cluster. The Record Validation filter validates records sent by a producer. Only records that pass the validation are sent to the broker. For more information, see the Streams for Apache Kafka Proxy guide .

Commands:
Chapter 11. Installation and Booting Improved logging when network traffic is blocked during installation This update adds improved logging when attempting to connect to a network repository during installation. Now, when there is a connection problem with a network repository during installation, logs include more detailed information about what caused the problem. (BZ#1240379) Support for Memory Address Range Mirroring With this update, it is possible to configure Memory Address Range Mirroring on EFI-based systems on compatible hardware, using the efibootmgr utility with the new --mirror-below-4G and --mirror-above-4G options. (BZ#1271412) Default logging levels increased in Yum and NetworkManager With this update, default logging levels were increased in the Yum and NetworkManager utilities. (BZ#1254368) Driver Update Disks can now replace loaded modules It is now possible to use a Driver Update Disk to replace a module that is already loaded, provided that the original module is not in use. (BZ#1101653)

Commands:
9.2.5. Viewing the Transaction Log PackageKit maintains a log of the transactions that it performs. To view the log, from the Add/Remove Software window, click System Software log , or run the gpk-log command at the shell prompt. The Software Log Viewer shows the following information: Date - the date on which the transaction was performed. Action - the action that was performed during the transaction, for example Updated packages or Installed packages . Details - the transaction type such as Updated , Installed , or Removed , followed by a list of affected packages. Username - the name of the user who performed the action. Application - the front end application that was used to perform the action, for example Update System . Typing the name of a package in the top text entry field filters the list of transactions to those which affected that package. Figure 9.10. Viewing the log of package management transactions with the Software Log Viewer

Commands: