mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 5. Using the API For more information, see the AMQ Python API reference and AMQ Python example suite . 5.1. Handling messaging events AMQ Python is an asynchronous event-driven API. To define how an application handles events, the user implements callback methods on the MessagingHandler class. These methods are then called as network activity or timers trigger new events. Example: Handling messaging events class ExampleHandler(MessagingHandler): def on_start(self, event): print("The container event loop has started") def on_sendable(self, event): print("A message can be sent") def on_message(self, event): print("A message is received") These are only a few common-case events. The full set is documented in the API reference . 5.2. Accessing event-related objects The event argument has attributes for accessing the object the event is regarding. For example, the on_connection_opened event sets the event connection attribute. In addition to the primary object for the event, all objects that form the context for the event are set as well. Attributes with no relevance to a particular event are null. Example: Accessing event-related objects event. container event. connection event. session event. sender event. receiver event. delivery event. message 5.3. Creating a container The container is the top-level API object. It is the entry point for creating connections, and it is responsible for running the main event loop. It is often constructed with a global event handler. Example: Creating a container handler = ExampleHandler() container = Container(handler) container.run() 5.4. Setting the container identity Each container instance has a unique identity called the container ID. When AMQ Python makes a connection, it sends the container ID to the remote peer. To set the container ID, pass it to the Container constructor. Example: Setting the container identity container = Container(handler) container.container_id = "job-processor-3" If the user does not set the ID, the library will generate a UUID when the container is constucted.

Commands:
class ExampleHandler(MessagingHandler): def on_start(self, event): print("The container event loop has started") def on_sendable(self, event): print("A message can be sent") def on_message(self, event): print("A message is received")
event. container event. connection event. session event. sender event. receiver event. delivery event. message
handler = ExampleHandler() container = Container(handler) container.run()
container = Container(handler) container.container_id = "job-processor-3"
Chapter 4. Downloading a manifest for a disconnected Satellite Server Only users on a disconnected Satellite Server download a subscription manifest from the Customer Portal. Users on a connected Satellite Server download subscription manifests in the Manifests section of the Red Hat Hybrid Cloud Console. For information about how to export and download a manifest for a connected Satellite Server, see Exporting and downloading a manifest for connected Satellite servers . Procedure To download a subscription manifest for a disconnected Satellite Server, complete the following steps: From the Subscription Allocations page, click the allocation that you want to add subscriptions to. Click the Subscriptions tab. Click Export Manifest . Note The file saves to your default downloads folder. After you download the manifest, you can import it into your Satellite Server. You can then use the Satellite web UI to update the manifest and refresh it to reflect the changes. Alternatively, you can import an updated manifest that contains the changes. For more information, see Importing a Subscription Manifest into Satellite Server in the Red Hat Satellite Content Management Guide.

Commands:
4.2.2. Blacklisting By Device Name You can blacklist device types by device name so that they will not be grouped into a multipath device by specifying a devnode entry in the blacklist section of the configuration file. The following example shows the lines in the configuration file that would blacklist all SCSI devices, since it blacklists all sd* devices. You can use a devnode entry in the blacklist section of the configuration file to specify individual devices to blacklist rather than all devices of a specific type. This is not recommended, however, since unless it is statically mapped by udev rules, there is no guarantee that a specific device will have the same name on reboot. For example, a device name could change from /dev/sda to /dev/sdb on reboot. By default, the following devnode entries are compiled in the default blacklist; the devices that these entries blacklist do not generally support DM-Multipath. To enable multipathing on any of these devices, you would need to specify them in the blacklist_exceptions section of the configuration file, as described in Section 4.2.4, "Blacklist Exceptions" .

Commands:
blacklist { devnode "^sd[a-z]" }
blacklist { devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^(td|hd)[a-z]" }
Chapter 112. AclRuleGroupResource schema reference Used in: AclRule The type property is a discriminator that distinguishes use of the AclRuleGroupResource type from AclRuleTopicResource , AclRuleClusterResource , AclRuleTransactionalIdResource . It must have the value group for the type AclRuleGroupResource . Property Property type Description type string Must be group . name string Name of resource for which given ACL rule applies. Can be combined with patternType field to use prefix pattern. patternType string (one of [prefix, literal]) 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 topic name. With prefix pattern type, the resource name will be used only as a prefix. Default value is literal .

Commands:
Preface Open Java Development Kit (OpenJDK) is a free and open source implementation of the Java Platform, Standard Edition (Java SE). The Red Hat build of OpenJDK is available in two versions, Red Hat build of OpenJDK 8u and Red Hat build of OpenJDK 11u. Packages for the Red Hat build of OpenJDK are made available on Red Hat Enterprise Linux and Microsoft Windows and shipped as a JDK and JRE in the Red Hat Container Catalog.

Commands:
Chapter 79. JaegerTracing schema reference The type JaegerTracing has been deprecated. Used in: KafkaBridgeSpec , KafkaConnectSpec , KafkaMirrorMaker2Spec , KafkaMirrorMakerSpec The type property is a discriminator that distinguishes use of the JaegerTracing type from OpenTelemetryTracing . It must have the value jaeger for the type JaegerTracing . Property Property type Description type string Must be jaeger .

Commands:
Chapter 10. Troubleshooting and deleting remaining resources during Uninstall Occasionally some of the custom resources managed by an operator may remain in "Terminating" status waiting on the finalizer to complete, although you have performed all the required cleanup tasks. In such an event you need to force the removal of such resources. If you do not do so, the resources remain in the Terminating state even after you have performed all the uninstall steps. Check if the openshift-storage namespace is stuck in the Terminating state upon deletion. Output: Check for the NamespaceFinalizersRemaining and NamespaceContentRemaining messages in the STATUS section of the command output and perform the step for each of the listed resources. Example output : Delete all the remaining resources listed in the step. For each of the resources to be deleted, do the following: Get the object kind of the resource which needs to be removed. See the message in the above output. Example : message: Some content in the namespace has finalizers remaining: cephobjectstoreuser.ceph.rook.io Here cephobjectstoreuser.ceph.rook.io is the object kind. Get the Object name corresponding to the object kind. Example : Example output: Patch the resources. Example: Output: Verify that the openshift-storage project is deleted. Output: If the issue persists, reach out to Red Hat Support .

Commands:
oc get project -n <namespace>
NAME DISPLAY NAME STATUS openshift-storage Terminating
oc get project openshift-storage -o yaml
status: conditions: - lastTransitionTime: "2020-07-26T12:32:56Z" message: All resources successfully discovered reason: ResourcesDiscovered status: "False" type: NamespaceDeletionDiscoveryFailure - lastTransitionTime: "2020-07-26T12:32:56Z" message: All legacy kube types successfully parsed reason: ParsedGroupVersions status: "False" type: NamespaceDeletionGroupVersionParsingFailure - lastTransitionTime: "2020-07-26T12:32:56Z" message: All content successfully deleted, may be waiting on finalization reason: ContentDeleted status: "False" type: NamespaceDeletionContentFailure - lastTransitionTime: "2020-07-26T12:32:56Z" message: 'Some resources are remaining: cephobjectstoreusers.ceph.rook.io has 1 resource instances' reason: SomeResourcesRemain status: "True" type: NamespaceContentRemaining - lastTransitionTime: "2020-07-26T12:32:56Z" message: 'Some content in the namespace has finalizers remaining: cephobjectstoreuser.ceph.rook.io in 1 resource instances' reason: SomeFinalizersRemain status: "True" type: NamespaceFinalizersRemaining
oc get <Object-kind> -n <project-name>
oc get cephobjectstoreusers.ceph.rook.io -n openshift-storage
NAME AGE noobaa-ceph-objectstore-user 26h
oc patch -n <project-name> <object-kind>/<object-name> --type=merge -p '{"metadata": {"finalizers":null}}'
oc patch -n openshift-storage cephobjectstoreusers.ceph.rook.io/noobaa-ceph-objectstore-user --type=merge -p '{"metadata": {"finalizers":null}}'
cephobjectstoreuser.ceph.rook.io/noobaa-ceph-objectstore-user patched
oc get project openshift-storage
Error from server (NotFound): namespaces "openshift-storage" not found
Chapter 4. Deploy the Configured Back End The Director installation uses a non-root user to execute commands, which includes orchestrating the deployment of the Block Storage back end. In Creating a Director Installation User , a user named stack is created for this purpose. This user is configured with elevated privileges. To deploy the lone back end configured in Chapter 3, Define a Single Back End , first log in as the stack user to the Undercloud. Then, deploy the back end (defined in the edited ~/templates/cinder-dellps-config.yaml ) by running the following: Important If you passed any extra environment files when you created the overcloud, pass them again here using the -e option to avoid making undesired changes to the overcloud. For more information, see Modifying the overcloud environment in the Director Installation and Usage guide.

Commands:
openstack overcloud deploy --templates -e ~/templates/cinder-dellps-config.yaml
Integrating Microsoft Azure data into cost management Cost Management Service 1-latest Learn how to add your Microsoft Azure integration and RHEL metering Red Hat Customer Content Services

Commands:
az account show --query "{subscription_id: id }"
{ "subscription_id": 00000000-0000-0000-000000000000 }
client_id: 00000000-0000-0000-000000000000
secret: 00000000-0000-0000-000000000000
tenant: 00000000-0000-0000-000000000000
az account show --query "{subscription_id: id }"
{ "subscription_id": 00000000-0000-0000-000000000000 }
client_id: 00000000-0000-0000-000000000000
secret: 00000000-0000-0000-000000000000
tenant: 00000000-0000-0000-000000000000
azure-functions pandas requests azure-identity azure-storage-blob
'additionalinfo', 'billingaccountid', 'billingaccountname', 'billingcurrencycode', 'billingperiodenddate', 'billingperiodstartdate', 'chargetype', 'consumedservice', 'costinbillingcurrency', 'date', 'effectiveprice', 'metercategory', 'meterid', 'metername', 'meterregion', 'metersubcategory', 'offerid', 'productname', 'publishername', 'publishertype', 'quantity', 'reservationid', 'reservationname', 'resourcegroup', 'resourceid', 'resourcelocation', 'resourcename', 'servicefamily', 'serviceinfo1', 'serviceinfo2', 'subscriptionid', 'tags', 'unitofmeasure', 'unitprice'
column_translation = {"billingcurrency": "billingcurrencycode", "currency": "billingcurrencycode", "instanceid": "resourceid", "instancename": "resourceid", "pretaxcost": "costinbillingcurrency", "product": "productname", "resourcegroupname": "resourcegroup", "subscriptionguid": "subscriptionid", "servicename": "metercategory", "usage_quantity": "quantity"}
Chapter 5. Downloading PDF policy reports The Insights for Red Hat Enterprise Linux compliance service enables you to create PDF reports for individual policies to share with stakeholders, such as your compliance team or auditors. Reports include the following information: Policy details: policy type, operation system, compliance threshold, and business objective. Percentage of systems in compliance with the policy. Numbers of non-compliant and compliant systems. Non-compliant system information. You can select to include compliant systems when creating the report. List of top 10 failed rules: the most severe failed rules, along with the greatest number of failed systems for each rule, are ranked at the top. 5.1. Creating a PDF report for a policy Perform the following steps to download a PDF report for a security policy. Prerequisites You must be logged in to the Red Hat Hybrid Cloud Console. Policy reports are point-in-time reporting. Red Hat recommends uploading your latest system data to Insights for Red Hat Enterprise Linux before creating a policy report in the compliance service. Procedure Optionally run insights-client --compliance on your systems to scan them and upload current data to the compliance service. Navigate to Security > Compliance > Reports . Locate the policy for which to create the report. Click the download icon on the far right of the same row as the policy name. Note You can also click on the policy name and click Download PDF in the upper right of the page. In the Compliance report modal dialog, make selections for system data to include. Make selections for rule data to include. Optionally, add user notes. Click Export report .

Commands:
8.12. ca-certificates 8.12.1. RHEA-2013:1596 - ca-certificates enhancement update Updated ca-certificates packages that add various enhancements are now available for Red Hat Enterprise Linux 6. The ca-certificates package contains a set of CA certificates chosen by the Mozilla Foundation for use with the Internet Public Key Infrastructure (PKI). Note The ca-certificates package has been upgraded to upstream version 1.94 as released with NSS version 3.15, which provides an updated set of recent Certificate Authorities according to the Mozilla CA Certificate Policy. Also, the update-ca-trust configuration management tool has been added. (BZ# 973727 , BZ# 1002646 ) Enhancement BZ# 544376 This update provides Shared System Certificate Authority storage, a system-wide trust storage for configuration data, required as an input for certificate trust decisions. This is a functionally compatible replacement for classic Certificate Authority configuration files and for the libnssckbi NSS trust module. This feature must be explicitly enabled by an administrator. Refer to the update-ca-trust man page in the ca-certificates package for a more detailed description of the feature. Users of ca-certificates are advised to upgrade to these updated packages, which add these enhancements.

Commands:
5.5. Making the Storage Usable Once a mass storage device is in place, there is little that it can be used for. True, data can be written to it and read back from it, but without any underlying structure data access is only possible by using sector addresses (either geometrical or logical). What is needed are methods of making the raw storage a hard drive provides more easily usable. The following sections explore some commonly-used techniques for doing just that. 5.5.1. Partitions/Slices The first thing that often strikes a system administrator is that the size of a hard drive may be much larger than necessary for the task at hand. As a result, many operating systems have the capability of dividing a hard drive's space into various partitions or slices . Because they are separate from each other, partitions can have different amounts of space utilized, and that space in no way impacts the space utilized by other partitions. For example, the partition holding the files comprising the operating system is not affected even if the partition holding the users' files becomes full. The operating system still has free space for its own use. Although it is somewhat simplistic, you can think of partitions as being similar to individual disk drives. In fact, some operating systems actually refer to partitions as "drives". However, this viewpoint is not entirely accurate; therefore, it is important that we look at partitions more closely. 5.5.1.1. Partition Attributes Partitions are defined by the following attributes: Partition geometry Partition type Partition type field These attributes are explored in more detail in the following sections. 5.5.1.1.1. Geometry A partition's geometry refers to its physical placement on a disk drive. The geometry can be specified in terms of starting and ending cylinders, heads, and sectors, although most often partitions start and end on cylinder boundaries. A partition's size is then defined as the amount of storage between the starting and ending cylinders. 5.5.1.1.2. Partition Type The partition type refers to the partition's relationship with the other partitions on the disk drive. There are three different partition types: Primary partitions Extended partitions Logical partitions The following sections describe each partition type. 5.5.1.1.2.1. Primary Partitions Primary partitions are partitions that take up one of the four primary partition slots in the disk drive's partition table. 5.5.1.1.2.2. Extended Partitions Extended partitions were developed in response to the need for more than four partitions per disk drive. An extended partition can itself contain multiple partitions, greatly extending the number of partitions possible on a single drive. The introduction of extended partitions was driven by the ever-increasing capacities of new disk drives. 5.5.1.1.2.3. Logical Partitions Logical partitions are those partitions contained within an extended partition; in

Commands:
3.4. Application Settings for the Data Warehouse service in ovirt-engine-dwhd.conf The following is a list of options for configuring application settings for the Data Warehouse service. These options are available in the /usr/share/ovirt-engine-dwh/services/ovirt-engine-dwhd/ovirt-engine-dwhd.conf file. Configure any changes to the default values in an override file under /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/ . Restart the Data Warehouse service after saving the changes. Table 3.1. ovirt-engine-dwhd.conf application settings variables Variable name Default Value Remarks DWH_DELETE_JOB_HOUR 3 The time at which a deletion job is run. Specify a value between 0 and 23 , where 0 is midnight. DWH_SAMPLING 60 The interval, in seconds, at which data is collected into statistical tables. DWH_TABLES_KEEP_SAMPLES 24 The number of hours that data from DWH_SAMPLING is stored. Data more than two hours old is aggregated into hourly data. DWH_TABLES_KEEP_HOURLY 1440 The number of hours that hourly data is stored. The default is 60 days. Hourly data more than two days old is aggregated into daily data. DWH_TABLES_KEEP_DAILY 43800 The number of hours that daily data is stored. The default is five years. DWH_ERROR_EVENT_INTERVAL 300000 The minimum interval, in milliseconds, at which errors are pushed to the Manager's audit.log .

Commands:
19.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: squid_connect_any When enabled, this Boolean permits Squid to initiate a connection to a remote host on any port. squid_use_tproxy When enabled, this Boolean allows Squid to run as a transparent proxy. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, enter the following command: Enter the following command to view description of a particular Boolean: Note that the additional policycoreutils-devel package providing the sepolicy utility is required for this command to work.

Commands:
~]USD getsebool -a | grep service_name
~]USD sepolicy booleans -b boolean_name
25.18. Adding/Removing a Logical Unit Through rescan-scsi-bus.sh The sg3_utils package provides the rescan-scsi-bus.sh script, which can automatically update the logical unit configuration of the host as needed (after a device has been added to the system). The rescan-scsi-bus.sh script can also perform an issue_lip on supported devices. For more information about how to use this script, refer to rescan-scsi-bus.sh --help . To install the sg3_utils package, run yum install sg3_utils . Known Issues with rescan-scsi-bus.sh When using the rescan-scsi-bus.sh script, take note of the following known issues: In order for rescan-scsi-bus.sh to work properly, LUN0 must be the first mapped logical unit. The rescan-scsi-bus.sh can only detect the first mapped logical unit if it is LUN0 . The rescan-scsi-bus.sh will not be able to scan any other logical unit unless it detects the first mapped logical unit even if you use the --nooptscan option. A race condition requires that rescan-scsi-bus.sh be run twice if logical units are mapped for the first time. During the first scan, rescan-scsi-bus.sh only adds LUN0 ; all other logical units are added in the second scan. A bug in the rescan-scsi-bus.sh script incorrectly executes the functionality for recognizing a change in logical unit size when the --remove option is used. The rescan-scsi-bus.sh script does not recognize ISCSI logical unit removals.

Commands:
6.10. RHEA-2013:0340 - new packages: suitesparse New suitesparse packages are now available for Red Hat Enterprise Linux 6. The suitesparse packages are a collection of libraries for computations involving sparse matrices. This enhancement update adds the suitesparse packages to Red Hat Enterprise Linux 6. (BZ# 844974 ) All users who require suitespare should install these new packages.

Commands: