mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix A. Image service (glance) command options You can use the following optional arguments with the glance image-create and glance image-update commands. Table A.1. Command options Specific to Option Description All --architecture <ARCHITECTURE> Operating system architecture as specified in https://docs.openstack.org/glance/latest/user/common-image-properties.html#architecture All --protected [True_False] If true, image will not be deletable. All --name <NAME> Descriptive name for the image All --instance-uuid <INSTANCE_UUID> Metadata that can be used to record which instance this image is associated with. (Informational only, does not create an instance snapshot.) All --min-disk <MIN_DISK> Amount of disk space (in GB) required to boot image. All --visibility <VISIBILITY> Scope of image accessibility. Valid values: public, private, community, shared All --kernel-id <KERNEL_ID> ID of image stored in the Image service (glance) that should be used as the kernel when booting an AMI-style image. All --os-version <OS_VERSION> Operating system version as specified by the distributor All --disk-format <DISK_FORMAT> Format of the disk. Valid values: None, ami, ari, aki, vhd, vhdx, vmdk, raw, qcow2, vdi, iso, ploop All --os-distro <OS_DISTRO> Common name of operating system distribution as specified in https://docs.openstack.org/glance/latest/user/common-image-properties.html#os-distro All --owner <OWNER> Owner of the image All --ramdisk-id <RAMDISK_ID> ID of image stored in the Image service that should be used as the ramdisk when booting an AMI-style image. All --min-ram <MIN_RAM> Amount of RAM (in MB) required to boot image. All --container-format <CONTAINER_FORMAT> Format of the container. Valid values: None, ami, ari, aki, bare, ovf, ova, docker All --property <key=value> Arbitrary property to associate with image. May be used multiple times. glance image-create --tags <TAGS> [<TAGS> ...] List of strings related to the image glance image-create --id <ID> An identifier for the image glance image-update --remove-property Key name of arbitrary property to remove from the image.

Commands:
Chapter 3. Listing available buckets in your object store To list buckets that are available in your object store, use the list_bucket() method. Prerequisites You have cloned the odh-doc-examples repository to your workbench. You have opened the s3client_examples.ipynb file in your workbench. You have installed Boto3 and configured the S3 client. Procedure In the notebook, locate the following instructions that lists available buckets and then run the code cell. A successful response includes an HTTP request status code of 200 and a list of buckets, similar to the following output: Locate the instructions that prints only the names of available buckets and execute the code cell. The output displays the names of the buckets, similar to the following example.

Commands:
#List available buckets s3_client.list_buckets()
'HTTPStatusCode': 200, 'Buckets': [{'Name': 'aqs086-image-registry', 'CreationDate': datetime.datetime(2024, 1, 16, 20, 21, 36, 244000, tzinfo=tzlocal( ))},
#Print only names of available buckets for bucket in s3_client.list_buckets()['Buckets']: print(bucket['Name'])
aqs086-image-registry aqs087-image-registry aqs135-image-registry aqs246-image-registry
3.4. CPU Power Saving Policies cpupower provides ways to regulate your processor's power saving policies. Use the following options with the cpupower set command: --perf-bias <0-15> Allows software on supported Intel processors to more actively contribute to determining the balance between optimum performance and saving power. This does not override other power saving policies. Assigned values range from 0 to 15, where 0 is optimum performance and 15 is optimum power efficiency. By default, this option applies to all cores. To apply it only to individual cores, add the --cpu <cpulist> option. --sched-mc <0|1|2> Restricts the use of power by system processes to the cores in one CPU package before other CPU packages are drawn from. 0 sets no restrictions, 1 initially employs only a single CPU package, and 2 does this in addition to favouring semi-idle CPU packages for handling task wakeups. --sched-smt <0|1|2> Restricts the use of power by system processes to the thread siblings of one CPU core before drawing on other cores. 0 sets no restrictions, 1 initially employs only a single CPU package, and 2 does this in addition to favouring semi-idle CPU packages for handling task wakeups.

Commands:
1.4.3. GFS2 Performance Improvements There are many features of GFS2 file systems that do not result in a difference in the user interface from GFS file systems but which improve file system performance. A GFS2 file system provides improved file system performance in the following ways: Better performance for heavy usage in a single directory Faster synchronous I/O operations Faster cached reads (no locking overhead) Faster direct I/O with preallocated files (provided I/O size is reasonably large, such as 4M blocks) Faster I/O operations in general Faster execution of the df command, because of faster statfs calls Improved atime mode to reduce the number of write I/O operations generated by atime when compared with GFS GFS2 file systems provide broader and more mainstream support in the following ways: GFS2 is part of the upstream kernel (integrated into 2.6.19). GFS2 supports the following features. extended file attributes ( xattr ) the lsattr () and chattr () attribute settings by means of standard ioctl () calls nanosecond timestamps A GFS2 file system provides the following improvements to the internal efficiency of the file system. GFS2 uses less kernel memory. GFS2 requires no metadata generation numbers. Allocating GFS2 metadata does not require reads. Copies of metadata blocks in multiple journals are managed by revoking blocks from the journal before lock release. GFS2 includes a much simpler log manager that knows nothing about unlinked inodes or quota changes. The gfs2_grow and gfs2_jadd commands use locking to prevent multiple instances running at the same time. The ACL code has been simplified for calls like creat () and mkdir (). Unlinked inodes, quota changes, and statfs changes are recovered without remounting the journal.

Commands:
Chapter 5. Exporting applications As a developer, you can export your application in the ZIP file format. Based on your needs, import the exported application to another project in the same cluster or a different cluster by using the Import YAML option in the +Add view. Exporting your application helps you to reuse your application resources and saves your time. 5.1. Prerequisites You have installed the gitops-primer Operator from the OperatorHub. Note The Export application option is disabled in the Topology view even after installing the gitops-primer Operator. You have created an application in the Topology view to enable Export application . 5.2. Procedure In the developer perspective, perform one of the following steps: Navigate to the +Add view and click Export application in the Application portability tile. Navigate to the Topology view and click Export application . Click OK in the Export Application dialog box. A notification opens to confirm that the export of resources from your project has started. Optional steps that you might need to perform in the following scenarios: If you have started exporting an incorrect application, click Export application Cancel Export . If your export is already in progress and you want to start a fresh export, click Export application Restart Export . If you want to view logs associated with exporting an application, click Export application and the View Logs link. After a successful export, click Download in the dialog box to download application resources in ZIP format onto your machine.

Commands:
Appendix C. Removing the standalone Red Hat Virtualization Manager The engine-cleanup command removes all components of the Red Hat Virtualization Manager and automatically backs up the following: the Grafana database, in /var/lib/grafana/ the Manager database in /var/lib/ovirt-engine/backups/ a compressed archive of the PKI keys and configuration in /var/lib/ovirt-engine/backups/ Backup file names include the date and time. Warning You should use this procedure only on a standalone installation of the Red Hat Virtualization Manager. Procedure Run the following command on the Manager machine: # engine-cleanup The Manager service must be stopped before proceeding. You are prompted to confirm. Enter OK to proceed: During execution engine service will be stopped (OK, Cancel) [OK]: You are prompted to confirm that you want to remove all Manager components. Enter OK to remove all components, or Cancel to exit engine-cleanup : All the installed ovirt components are about to be removed, data will be lost (OK, Cancel) [Cancel]: OK engine-cleanup details the components that are removed, and the location of backup files. Remove the Red Hat Virtualization packages: # dnf remove rhvm* vdsm-bootstrap

Commands:
engine-cleanup
During execution engine service will be stopped (OK, Cancel) [OK]:
All the installed ovirt components are about to be removed, data will be lost (OK, Cancel) [Cancel]: OK
dnf remove rhvm* vdsm-bootstrap
Chapter 8. Desktop GNOME rebased to version 3.22.3 The GNOME Desktop has been updated to upstream version 3.22.3, which provides a number of bug fixes and enhancements over the version. Notable changes include: Overhauled desktop notifications Built-in integration with world clocks and media players Automatically adjusting screen brightness (for systems with an integrated light sensor) In many applications, support for a standard dialog to document keyboard shortcuts Improvements to several setting panels (printer, mouse, touchpad, keyboard shortcuts) Option to rename multiple files at once Built-in support for compressed files and for Google Drive Undo support for trash (BZ# 1383353 ) The xorg-x11-drv-libinput driver has been added to the X.Org input drivers The xorg-x11-drv-libinput X.Org driver is a wrapper driver for the low-level libinput library. This update adds the driver to the X.Org input drivers. After you install xorg-x11-drv-libinput , it is possible to remove the xorg-x11-drv-synaptics driver and get access to some of the improved input device handling offered by libinput . (BZ#1413811) Change of default driver for some Intel and nVidia Hardware This change affects: 4th Generation Intel Core Processors and later nVidia GeForce 8 hardware and later The default DDX driver has changed to be xf86-video-modesetting . Previously the defaults were xf86-video-nouveau and xf86-video-intel for nVidia and Intel hardware respectively. (BZ#1404868) dconf-editor is now provided by a separate package The upstream dconf team have split the dconf-editor into its own package. This release reflects that change. In addition, the user interface has been redesigned in version 3.22. The tree view on the left side has been removed. Keys and directories are now shown in the same window. The ability to go back in the hierarchy has moved to the path shown in the header-bar. (BZ#1388931)

Commands:
3.8. Searching for Data Centers The following table describes all search options for Data Centers. Table 3.4. Searching for Data Centers Property (of resource or resource-type) Type Description (Reference) Clusters. clusters-prop Depends on property type The property of the clusters associated with the data center. name String The name of the data center. description String A description of the data center. type String The type of data center. status List The availability of the data center. sortby List Sorts the returned results by one of the resource properties. page Integer The page number of results to display. Example Datacenter: type = nfs and status != up This example returns a list of data centers with a storage type of NFS and status other than up.

Commands:
15.6. Migrating with virt-manager This section covers migrating a KVM guest virtual machine with virt-manager from one host physical machine to another. Connect to the target host physical machine In the virt-manager interface , connect to the target host physical machine by selecting the File menu, then click Add Connection . Add connection The Add Connection window appears. Figure 15.1. Adding a connection to the target host physical machine Enter the following details: Hypervisor : Select QEMU/KVM . Method : Select the connection method. Username : Enter the user name for the remote host physical machine. Hostname : Enter the host name for the remote host physical machine. Note For more information on the connection options, see Section 19.5, "Adding a Remote Connection" . Click Connect . An SSH connection is used in this example, so the specified user's password must be entered in the step. Figure 15.2. Enter password Configure shared storage Ensure that both the source and the target host are sharing storage, for example using NFS . Migrate guest virtual machines Right-click the guest that is to be migrated, and click Migrate . In the New Host field, use the drop-down list to select the host physical machine you wish to migrate the guest virtual machine to and click Migrate . Figure 15.3. Choosing the destination host physical machine and starting the migration process A progress window appears. Figure 15.4. Progress window If the migration finishes without any problems, virt-manager displays the newly migrated guest virtual machine running in the destination host. Figure 15.5. Migrated guest virtual machine running in the destination host physical machine

Commands:
Chapter 1. Introduction SystemTap provides free software (GPL) infrastructure to simplify the gathering of information about the running Linux system. This assists diagnosis of a performance or functional problem. SystemTap eliminates the need for the developer to go through the tedious and disruptive instrument, recompile, install, and reboot sequence that may be otherwise required to collect data. SystemTap provides a simple command line interface and scripting language for writing instrumentation for a live, running kernel. This instrumentation uses probe points and functions provided in the tapset library. Simply put, tapsets are scripts that encapsulate knowledge about a kernel subsystem into pre-written probes and functions that can be used by other scripts. Tapsets are analogous to libraries for C programs. They hide the underlying details of a kernel area while exposing the key information needed to manage and monitor that aspect of the kernel. They are typically developed by kernel subject-matter experts. A tapset exposes the high-level data and state transitions of a subsystem. For the most part, good tapset developers assume that SystemTap users know little to nothing about the kernel subsystem's low-level details. As such, tapset developers write tapsets that help ordinary SystemTap users write meaningful and useful SystemTap scripts. 1.1. Documentation Goals This guide aims to document SystemTap's most useful and common tapset entries; it also contains guidelines on proper tapset development and documentation. The tapset definitions contained in this guide are extracted automatically from properly-formatted comments in the code of each tapset file. As such, any revisions to the definitions in this guide should be applied directly to their respective tapset file.

Commands:
Chapter 27. JvmOptions schema reference Used in: CruiseControlSpec , EntityTopicOperatorSpec , EntityUserOperatorSpec , KafkaBridgeSpec , KafkaClusterSpec , KafkaConnectSpec , KafkaMirrorMaker2Spec , KafkaMirrorMakerSpec , KafkaNodePoolSpec , ZookeeperClusterSpec Property Property type Description -XX map A map of -XX options to the JVM. -Xmx string -Xmx option to to the JVM. -Xms string -Xms option to to the JVM. gcLoggingEnabled boolean Specifies whether the Garbage Collection logging is enabled. The default is false. javaSystemProperties SystemProperty array A map of additional system properties which will be passed using the -D option to the JVM.

Commands:
Chapter 5. Deploying standalone Multicloud Object Gateway Deploying only the Multicloud Object Gateway component with the OpenShift Data Foundation provides the flexibility in deployment and helps to reduce the resource consumption. After deploying the MCG component, you can create and manage buckets using MCG object browser. For more information, see Creating and managing buckets using MCG object browser . Use this section to deploy only the standalone Multicloud Object Gateway component, which involves the following steps: * Installing the Local Storage Operator. * Installing Red Hat OpenShift Data Foundation Operator * Creating standalone Multicloud Object Gateway :leveloffset: +2

Commands:
Chapter 5. About OpenShift Serverless Functions OpenShift Serverless Functions enables developers to create and deploy stateless, event-driven functions as a Knative service on OpenShift Container Platform. The kn func CLI is provided as a plugin for the Knative kn CLI. You can use the kn func CLI to create, build, and deploy the container image as a Knative service on the cluster. 5.1. Included runtimes OpenShift Serverless Functions provides templates that can be used to create basic functions for the following runtimes: Quarkus Node.js TypeScript 5.2. steps Getting started with functions .

Commands:
Chapter 1. Overview of authentication methods in Satellite Red Hat Satellite includes native support for authentication with a username and password. If you require additional methods of authentication, configure your Satellite Server to use an external authentication source. Table 1.1. External authentication sources supported by Satellite and the authentication features they provide Username and password Single sign-on (SSO) One-time password (OTP) Time-based one-time password (TOTP) Additional details Active Directory (direct integration) Yes Yes No No Chapter 5, Configuring Kerberos SSO for Active Directory users in Satellite Identity Management Yes (Linux and Active Directory users) Yes (Linux users only) No No Chapter 3, Configuring Kerberos SSO with Identity Management in Satellite Red Hat Single Sign-On Yes Yes Yes Yes Chapter 4, Configuring SSO and 2FA with Red Hat Single Sign-On in Satellite LDAP Yes No No No Chapter 6, Configuring an LDAP server as an external identity provider for Satellite

Commands:
Chapter 8. Configuring cost models to accurately report costs Now that you configured your integrations to collect cost and usage data in cost management, you can configure cost models to associate prices to metrics and usage. A cost model is a framework that uses raw costs and metrics to define calculations for the costs in cost management. You can record, categorize, and distribute the costs that the cost model generates to specific customers, business units, or projects. In Cost Models , you can complete the following tasks: Classifying your costs as infrastructure or supplementary costs Capturing monthly costs for OpenShift nodes and clusters Applying a markup to account for additional support costs To learn how to configure a cost model, see Using cost models .

Commands:
7.276. xfsprogs 7.276.1. RHBA-2013:0481 - xfsprogs bug fix and enhancement update Updated xfsprogs packages that fix three bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The xfsprogs packages contain a set of commands to use the XFS file system, including the mkfs.xfs command to construct an XFS system. Bug Fixes BZ# 730433 When the manual geometry of the mkfs.xfs utility was specified for striping as well as calculating of the allocation group counts and size, mkfs.xfs could emit confusing error messages on failure. With this update, more standardized and informative error messages are returned. BZ# 836433 When the sector size was not specified by the "-f" option, the mkfs.xfs utility used the 512 byte sector size by default even for drives with 4 Kb physical sectors. With this update, mkfs.xfs correctly recognizes the sector size in the described scenario, which fixes this bug. BZ# 878859 When attempting to set a 32-bit quota project ID on an XFS file system which did not have this feature enabled, the command returned success, but truncated the project ID to the lower 16 bits. With this update, a project ID of more than 16 bits cannot be set unless the 32-bit project ID feature is enabled. Enhancement BZ#827186 With this update, mkfs.xfs can enable 32-bit project quota IDs on a file system with the "-i projid32bit=1" parameter specified. Without this parameter, mkfs.xfs defaults to 16-bit project quota IDs. The 32-bit project quota IDs can be enabled on existing file systems by using the "xfs_admin -p" command. All users who use the XFS file system are advised to upgrade to these updated packages, which fix these bugs and add this enhancement. 7.276.2. RHBA-2013:0987 - xfsprogs bug fix update Updated xfsprogs packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The xfsprogs packages contain a set of commands to use the XFS file system, including the mkfs.xfs command to construct an XFS file system. Bug Fixes BZ# 971698 When stripe geometry was specified manually to the mkfs.xfs utility, mkfs.xfs did not properly select "multidisk mode" as it does when stripe geometry is automatically detected. As a result, a less than optimal number of allocation groups were created. With this update, multidisk mode is selected properly, and a larger number of allocation groups are created. BZ# 976217 Previously, xfs_repair was unable to properly handle fragmented multiblock version 2 directories (Multiblock dir2 is only enabled with the "-n size=" mkfs.xfs option, where the size is greater than the file system block size). With this update, xfs_repair can operate on fragmented dir2 directories without errors. Users of xfsprogs are advised to upgrade to these updated packages, which fix these bugs.

Commands: