mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 31. extension This chapter describes the commands under the extension command. 31.1. extension list List API extensions Usage: Table 31.1. Command arguments Value Summary -h, --help Show this help message and exit --compute List extensions for the compute api --identity List extensions for the identity api --network List extensions for the network api --volume List extensions for the block storage api --long List additional fields in output Table 31.2. Output formatter options 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 31.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 31.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 31.5. Table formatter options 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. 31.2. extension show Show API extension Usage: Table 31.6. Positional arguments Value Summary <extension> Extension to display. currently, only network extensions are supported. (Name or Alias) Table 31.7. Command arguments Value Summary -h, --help Show this help message and exit Table 31.8. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 31.9. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 31.10. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 31.11. Table formatter options 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 extension 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] [--compute] [--identity] [--network] [--volume] [--long]
openstack extension show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] <extension>
probe::json_data Name probe::json_data - Fires whenever JSON data is wanted by a reader. Synopsis json_data Values None Context This probe fires when the JSON data is about to be read. This probe must gather up data and then call the following macros to output the data in JSON format. First, @ json_output_data_start must be called. That call is followed by one or more of the following (one call for each data item): @ json_output_string_value , @ json_output_numeric_value , @ json_output_array_string_value , and @ json_output_array_numeric_value . Finally @ json_output_data_end must be called.

Commands:
Chapter 34. Case Management Model and Notation You can use Business Central to import, view, and modify the content of Case Management Model and Notation (CMMN) files. When authoring a project, you can import your case management model and then select it from the asset list to view or modify it in a standard XML editor. The following CMMN constructs are currently available: Tasks (human task, process task, decision task, case task) Discretionary tasks (same as above) Stages Milestones Case file items Sentries (entry and exit) The following tasks are not supported: Required Repeat Manual activation Sentries for individual tasks are limited to entry criteria while entry and exit criteria are supported for stages and milestones. Decision tasks map by default to a DMN decision. Event listeners are not supported. Red Hat Process Automation Manager does not provide any modeling capabilities for CMMN and focuses solely on the execution of the model.

Commands:
Chapter 165. StrimziPodSetStatus schema reference Used in: StrimziPodSet Property Property type Description conditions Condition array List of status conditions. observedGeneration integer The generation of the CRD that was last reconciled by the operator. pods integer Number of pods managed by this StrimziPodSet resource. readyPods integer Number of pods managed by this StrimziPodSet resource that are ready. currentPods integer Number of pods managed by this StrimziPodSet resource that have the current revision.

Commands:
Chapter 7. Installing OpenShift DR Hub Operator on Hub cluster Prerequisites Ensure that the values for the access and secret key are base-64 encoded . The encoded values for the keys were retrieved in the prior section and the resulting Secrets are exactly the same as those created already on the managed clusters. Procedure On the Hub cluster, navigate to OperatorHub and use the search filter for OpenShift DR Hub Operator . Follow the screen instructions to Install the operator into the project openshift-dr-system . Create S3 secrets for the Hub cluster using the following S3 secret YAML format for the Primary managed cluster . Run the following command to create this secret on the Hub cluster. Example output: Create S3 secrets using the following S3 secret YAML format for the Secondary managed cluster . Run the following command to create this secret on the Hub cluster. Example output: Configure ConfigMap for the OpenShift DR Hub Operator. After the operator is successfully created, a new ConfigMap called ramen-hub-operator-config is created. Run the following command to edit the file. Add the following new content starting at s3StoreProfiles to the ConfigMap on the Hub cluster. Note Make sure to replace <primary clusterID> , <secondary clusterID> , baseDomain , odrbucket-<your value1> , and odrbucket-<your value2> variables with exact same values as used for the ramen-cluster-operator-config ConfigMap on the managed clusters.

Commands:
apiVersion: v1 data: AWS_ACCESS_KEY_ID: <primary cluster base-64 encoded access key> AWS_SECRET_ACCESS_KEY: <primary cluster base-64 encoded secret access key> kind: Secret metadata: name: odr-s3secret-primary namespace: openshift-dr-system
oc create -f odr-s3secret-primary.yaml
secret/odr-s3secret-primary created
apiVersion: v1 data: AWS_ACCESS_KEY_ID: <secondary cluster base-64 encoded access key> AWS_SECRET_ACCESS_KEY: <secondary cluster base-64 encoded secret access key> kind: Secret metadata: name: odr-s3secret-secondary namespace: openshift-dr-system
oc create -f odr-s3secret-secondary.yaml
secret/odr-s3secret-secondary created
oc edit configmap ramen-hub-operator-config -n openshift-dr-system
[...] apiVersion: v1 data: ramen_manager_config.yaml: | apiVersion: ramendr.openshift.io/v1alpha1 kind: RamenConfig [...] ramenControllerType: "dr-hub" ### Start of new content to be added s3StoreProfiles: - s3ProfileName: s3-primary s3CompatibleEndpoint: https://s3-openshift-storage.apps.<primary clusterID>.<baseDomain> s3Region: primary s3Bucket: odrbucket-<your value1> s3SecretRef: name: odr-s3secret-primary namespace: openshift-dr-system - s3ProfileName: s3-secondary s3CompatibleEndpoint: https://s3-openshift-storage.apps.<secondary clusterID>.<baseDomain> s3Region: secondary s3Bucket: odrbucket-<your value2> s3SecretRef: name: odr-s3secret-secondary namespace: openshift-dr-system [...]
5.190. microcode_ctl 5.190.1. RHBA-2012:0827 - microcode_ctl bug fix and enhancement update Updated microcode_ctl packages that fix one bug and add two enhancements are now available for Red Hat Enterprise Linux 6. The microcode_ctl packages provide microcode updates for Intel and AMD processors. Bug Fix BZ# 768803 Previously, running the microcode_ctl utility with long arguments for the "-d" or "-f" options led to a buffer overflow. Consequently, microcode_ctl terminated unexpectedly with a segmentation fault and a backtrace was displayed. With this update, microcode_ctl has been modified to handle this situation gracefully. The microcode_ctl utility no longer crashes and displays an error message informing the user that the file name used is too long. Enhancements BZ# 736266 The Intel CPU microcode file has been updated to version 20111110, which is the latest version of the microcode available from Intel. BZ# 787757 The AMD CPU microcode file has been updated to version 20120117, which is the latest version of the microcode available from AMD. All users of microcode_ctl are advised to upgrade to these updated packages, which fix this bug and add these enhancements.

Commands:
3.3. realmd Commands The realmd system has two major task areas: managing system enrollment in a domain setting which domain users are allowed to access the local system resources The central utility in realmd is called realm . Most realm commands require the user to specify the action that the utility should perform, and the entity, such as a domain or user account, for which to perform the action: For example: Table 3.1. realmd Commands Command Description Realm Commands discover Run a discovery scan for domains on the network. join Add the system to the specified domain. leave Remove the system from the specified domain. list List all configured domains for the system or all discovered and configured domains. Login Commands permit Enable access for specified users or for all users within a configured domain to access the local system. deny Restrict access for specified users or for all users within a configured domain to access the local system. For more information about the realm commands, see the realm (8) man page.

Commands:
realm command arguments
realm join ad.example.com realm permit user_name
Appendix B. Revision History Revision History Revision 6-9.3 Thu 25 May 2017 Vladimir Slavik Removal of section on distributed compiling. Revision 6-9.2 Mon 3 April 2017 Robert Kratky Release of the Developer Guide for Red Hat_Enterprise Linux 6.9 Revision 2-60 Wed 4 May 2016 Robert Kratky Release of the Developer Guide for Red Hat_Enterprise Linux 6.8 Revision 2-56 Tue Jul 6 2015 Robert Kratky Release of the Developer Guide for Red Hat_Enterprise Linux 6.7 Revision 2-55 Wed Apr 15 2015 Robert Kratky Release of the Developer Guide for Red Hat_Enterprise Linux 6.7 Beta Revision 2-54 Tue Dec 16 2014 Robert Kratky Update to sort order on the Red Hat Customer Portal. Revision 2-52 Wed Nov 11 2014 Robert Kratky Re-release for RHSCL 1.2 and DTS 3.0. Revision 2-51 Fri Oct 10 2014 Robert Kratky Release of the Developer Guide for Red Hat_Enterprise Linux 6.6

Commands:
F.3. Creating New Logical Volumes for an Existing Cluster To create new volumes, either volumes need to be added to a managed volume group on the node where it is already activated by the service, or the volume_list must be temporarily bypassed or overridden to allow for creation of the volumes until they can be prepared to be configured by a cluster resource. Note New logical volumes can be added only to existing volume groups managed by a cluster lvm resource if lv_name is not specified. The lvm resource agent allows for only a single logical volume within a volume group if that resource is managing volumes individually, rather than at a volume group level. To create a new logical volume when the service containing the volume group where the new volumes will live is already active, use the following procedure. The volume group should already be tagged on the node owning that service, so simply create the volumes with a standard lvcreate command on that node. Determine the current owner of the relevant service. On the node where the service is started, create the logical volume. Add the volume into the service configuration in whatever way is necessary. To create a new volume group entirely, use the following procedure. Create the volume group on one node using that node's name as a tag, which should be included in the volume_list . Specify any desired settings for this volume group as normal and specify --addtag nodename , as in the following example: Create volumes within this volume group as normal, otherwise perform any necessary administration on the volume group. When the volume group activity is complete, deactivate the volume group and remove the tag. Add the volume into the service configuration in whatever way is necessary.

Commands:
clustat
lvcreate -l 100%FREE -n lv2 myVG
vgcreate myNewVG /dev/mapper/mpathb --addtag node1.example.com
vgchange -an myNewVg --deltag node1.example.com
3.3. Creating A Cluster Creating a cluster with luci consists of selecting cluster nodes, entering their passwords, and submitting the request to create a cluster. If the node information and passwords are correct, Conga automatically installs software into the cluster nodes and starts the cluster. Create a cluster as follows: As administrator of luci , select the cluster tab. Click Create a New Cluster . At the Cluster Name text box, enter a cluster name. The cluster name cannot exceed 15 characters. Add the node name and password for each cluster node. Enter the node name for each node in the Node Hostname column; enter the root password for each node in the in the Root Password column. Check the Enable Shared Storage Support checkbox if clustered storage is required. Click Submit . Clicking Submit causes the the Create a new cluster page to be displayed again, showing the parameters entered in the preceding step, and Lock Manager parameters. The Lock Manager parameters consist of the lock manager option buttons, DLM (preferred) and GULM , and Lock Server text boxes in the GULM lock server properties group box. Configure Lock Manager parameters for either DLM or GULM as follows: For DLM - Click DLM (preferred) or confirm that it is set. For GULM - Click GULM or confirm that it is set. At the GULM lock server properties group box, enter the FQDN or the IP address of each lock server in a Lock Server text box. Note You must enter the FQDN or the IP address of one, three, or five GULM lock servers. Re-enter enter the root password for each node in the in the Root Password column. Click Submit . Clicking Submit causes the following actions: Cluster software packages to be downloaded onto each cluster node. Cluster software to be installed onto each cluster node. Cluster configuration file to be created and propagated to each node in the cluster. Starting the cluster. A progress page shows the progress of those actions for each node in the cluster. When the process of creating a new cluster is complete, a page is displayed providing a configuration interface for the newly created cluster.

Commands:
2.2.3.3. Qt Library Documentation The qt-doc package provides HTML manuals and references located in /usr/share/doc/qt4/html/ . This package also provides the Qt Reference Documentation , which is an excellent starting point for development within the Qt framework. You can also install further demos and examples from qt-demos and qt-examples . To get an overview of the capabilities of the Qt framework, see /usr/bin/qtdemo-qt4 (provided by qt-demos ).

Commands:
Chapter 4. Updating your Red Hat account information You use your Red Hat account to log in to the Red Hat Hybrid Cloud Console. The following table lists information that you can update on your Red Hat account: Table 4.1. Red Hat account information Label Description Personal Update personal information including your name, email address, job title, and phone numbers. Login & password Change your password and manage accounts connected to your company's single sign-on (SSO). Note that you cannot change your Red Hat login after it has been created. Postal address Update your mailing address. Language and location Change your preferred language and time zone. Errata notifications Control which errata notifications you receive and when you receive them. Errata notifications are email notifications of security updates, bug fixes, and enhancements. Prerequisites You are logged in to the Hybrid Cloud Console. Procedure To update your Red Hat account information, click your user avatar in the upper right of the Red Hat Hybrid Cloud Console window. A drop-down list appears. Click My profile . Select a label under Your information or Your preferences . Update your information and then click Save .

Commands:
4.143. libsemanage 4.143.1. RHBA-2011:1770 - libsemanage bug fix update Updated libsemanage packages that fix file creation when umask is changed. The libsemanage library provides an API for the manipulation of SELinux binary policies. It is used by checkpolicy (the policy compiler) and similar tools, as well as by programs such as load_policy, which must perform specific transformations on binary policies (for example, customizing policy boolean settings). Bug Fix BZ# 747345 When running semanage commands while umask is set to 027 (or to a similar value that restricts a non-priviledged user from reading files created with such a file-creating mask), semanage changed the permissions of certain files such as the /etc/selinux/mls/contexts/files/file_contexts file. As a consequence, non-priviledged processes were not able to read such files and certain commands such as the restorecon command failed to run on these files. To solve this problem, libsemanage has been modified to save and clear umask before libsemanage creates context files and then restore it after the files are created so the file permissions are readable by non-priviledged processes. Operations on these context files now work as expected. All users of libsemange are advised to upgrade to these updated packages, which fix this bug.

Commands:
probe::sunrpc.clnt.shutdown_client Name probe::sunrpc.clnt.shutdown_client - Shutdown an RPC client Synopsis sunrpc.clnt.shutdown_client Values om_queue the jiffies queued for xmit clones the number of clones vers the RPC program version number om_rtt the RPC RTT jiffies om_execute the RPC execution jiffies rpccnt the count of RPC calls progname the RPC program name authflavor the authentication flavor prot the IP protocol number prog the RPC program number om_bytes_recv the count of bytes in om_bytes_sent the count of bytes out port the port number om_ntrans the count of RPC transmissions netreconn the count of reconnections om_ops the count of operations tasks the number of references servername the server machine name

Commands:
Chapter 1. About CI/CD Red Hat OpenShift Service on AWS is an enterprise-ready Kubernetes platform for developers, which enables organizations to automate the application delivery process through DevOps practices, such as continuous integration (CI) and continuous delivery (CD). To meet your organizational needs, the Red Hat OpenShift Service on AWS provides the following CI/CD solutions: OpenShift Builds OpenShift Pipelines OpenShift GitOps Jenkins 1.1. OpenShift Builds OpenShift Builds provides you the following options to configure and run a build: Builds using Shipwright is an extensible build framework based on the Shipwright project. You can use it to build container images on an Red Hat OpenShift Service on AWS cluster. You can build container images from source code and Dockerfile by using image build tools, such as Source-to-Image (S2I) and Buildah. For more information, see builds for Red Hat OpenShift . Builds using BuildConfig objects is a declarative build process to create cloud-native apps. You can define the build process in a YAML file that you use to create a BuildConfig object. This definition includes attributes such as build triggers, input parameters, and source code. When deployed, the BuildConfig object builds a runnable image and pushes the image to a container image registry. With the BuildConfig object, you can create a Docker, Source-to-image (S2I), or custom build. For more information, see Understanding image builds . 1.2. OpenShift Pipelines OpenShift Pipelines provides a Kubernetes-native CI/CD framework to design and run each step of the CI/CD pipeline in its own container. It can scale independently to meet the on-demand pipelines with predictable outcomes. For more information, see Red Hat OpenShift Pipelines . 1.3. OpenShift GitOps OpenShift GitOps is an Operator that uses Argo CD as the declarative GitOps engine. It enables GitOps workflows across multicluster OpenShift and Kubernetes infrastructure. Using OpenShift GitOps, administrators can consistently configure and deploy Kubernetes-based infrastructure and applications across clusters and development lifecycles. For more information, see Red Hat OpenShift GitOps . 1.4. Jenkins Jenkins automates the process of building, testing, and deploying applications and projects. OpenShift Developer Tools provides a Jenkins image that integrates directly with the Red Hat OpenShift Service on AWS. Jenkins can be deployed on OpenShift by using the Samples Operator templates or certified Helm chart. For more information, see Configuring Jenkins images .

Commands:
Appendix A. Getting involved in the Migration Toolkit for Applications development A.1. Contributing to the project To help the Migration Toolkit for Applications cover most application constructs and server configurations, including yours, you can help with any of the following items: Send an email to jboss-migration-feedback@redhat.com and let us know what MTA migration rules must cover. Provide example applications to test migration rules. Identify application components and problem areas that might be difficult to migrate: Write a short description of the problem migration areas. Write a brief overview describing how to solve the problem in migration areas. Try Migration Toolkit for Applications on your application. Make sure to report any issues you meet. Contribute to the Migration Toolkit for Applications rules repository: Write a Migration Toolkit for Applications rule to identify or automate a migration process. Create a test for the new rule. For more information, see Rule Development Guide . Contribute to the project source code: Create a core rule. Improve MTA performance or efficiency. Any level of involvement is greatly appreciated! A.2. Reporting issues MTA uses Jira as its issue tracking system. If you encounter an issue executing MTA, submit a Jira issue . A.3. Migration Toolkit for Applications development resources Use the following resources to learn and contribute to the Migration Toolkit for Applications development: MTA forums: https://developer.jboss.org/en/windup Jira issue tracker: https://issues.redhat.com/projects/MTA/issues MTA mailing list: jboss-migration-feedback@redhat.com Revised on 2025-02-26 19:47:51 UTC

Commands: