mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Onboarding certification partners Use the Red Hat Customer Portal to create a new account if you are a new partner, or use your existing Red Hat account if you are a current partner to onboard with Red Hat for certifying your products. 2.1. Onboarding existing certification partners Prerequisites You have an existing Red Hat account. Procedure Access Red Hat Customer Portal and click Log in . Enter your Red Hat login or email address and click . Then, use either of the following options: Log in with company single sign-on Log in with Red Hat account From the menu bar on the header, click your avatar to view the account details. If an account number is associated with your account, then you can proceed with the certification process. If an account number is not associated with your account, then first contact the Red Hat global customer service team to raise a request for creating a new account number. After you get an account number, contact the certification team to proceed with the certification process. 2.2. Onboarding new certification partners Creating a new Red Hat account is the first step for onboarding new certification partners. Procedure Access Red Hat Customer Portal and click Register . Enter the following details to create a new Red Hat account: Select Corporate in the Account Type field. If you have created a Corporate type account and require an account number, contact the Red Hat global customer service team . Note Ensure that you create a company account and not a personal account. The account created during this step is also used to sign in to the Red Hat Ecosystem Catalog when working with certification requests. Choose a Red Hat login and password. Important If your login ID is associated with multiple accounts, then do not use your contact email as the login ID as this can cause issues during login. Also, you cannot change your login ID once created. Enter your Personal information and Company information . Click Create My Account . A new Red Hat account is created. Contact your Ecosystem Partner Management (EPM) representative, if available. Else contact the certification team to proceed with the certification process. 2.3. Exploring the Partner landing page After logging in to Red Hat Partner Connect , the partner landing page opens. This page serves as a centralized hub, offering access to various partner services and capabilities that enable you to start working on opportunities. The Partner landing page offers the following services: Software certification Red Hat Demo platform Red Hat Partner Training Portal Access library of marketing, sales & technical content Partner support Email preference center Partner subscriptions User account As part of the Red Hat partnership, partners receive access to various Red Hat systems and services that enable them to create shared value with Red Hat for our joint customers. Go to the Software certification tile and click Certify your software to begin your product certification journey. The personalized Product certification dashboard opens.

Commands:
5.96. grep 5.96.1. RHBA-2012:0352 - grep bug fix update An updated grep package that fixes one bug is now available for Red Hat Enterprise Linux 6. The grep utility searches through textual input for lines which contain a match to a specified pattern and then prints the matching lines. GNU grep utilities include grep, egrep and fgrep. Bug Fix BZ# 741452 Previously, the grep utility was not able to handle the EPIPE error. If a SIGPIPE signal was blocked by the shell, grep kept continuously printing error messages. An upstream patch has been applied to address this problem, so that grep exits on the first EPIPE error and prints only one error message. All users of grep are advised to upgrade to this updated package, which fixes this bug.

Commands:
28.2.2. Connecting the Installation System to a VNC Listener To have the installation system automatically connect to a VNC client, first start the client in listening mode. On Red Hat Enterprise Linux systems, use the -listen option to run vncviewer as a listener. In a terminal window, enter the command: Note By default, vncviewer uses TCP port 5500 when in listening mode. The firewall must be configured to permit connections to this port from other systems. Choose System Administration Firewall . Select Other ports , and Add . Enter 5500 in the Port(s) field, and specify tcp as the Protocol . Once the listening client is active, start the installation system and set the VNC options at the boot: prompt. In addition to vnc and vncpassword options, use the vncconnect option to specify the name or IP address of the system that has the listening client. To specify the TCP port for the listener, add a colon and the port number to the name of the system. For example, to connect to a VNC client on the system desktop.mydomain.com on the port 5500, enter the following at the boot: prompt:

Commands:
vncviewer -listen
linux vnc vncpassword= qwerty vncconnect= desktop.mydomain.com:5500
probe::scsi.iodispatching Name probe::scsi.iodispatching - SCSI mid-layer dispatched low-level SCSI command Synopsis Values device_state_str The current state of the device, as a string dev_id The scsi device id channel The channel number data_direction The data_direction specifies whether this command is from/to the device 0 (DMA_BIDIRECTIONAL), 1 (DMA_TO_DEVICE), 2 (DMA_FROM_DEVICE), 3 (DMA_NONE) lun The lun number request_bufflen The request buffer length host_no The host number device_state The current state of the device data_direction_str Data direction, as a string req_addr The current struct request pointer, as a number request_buffer The request buffer address

Commands:
scsi.iodispatching
Chapter 3. Updating Red Hat build of OpenJDK 11 for Microsoft Windows using the archive Red Hat build of OpenJDK 11 for Microsoft Windows can be manually update using the archive. Procedure Download the archive of Red Hat build of OpenJDK 11. Extract the contents of an archive to a directory of your choice. Note Extracting the contents of an archive to a directory path that does not contain spaces is recommended. On Command Prompt, update JAVA_HOME environment variable as follows: Open Command Prompt as an administrator. Set the value of the environment variable to your Red Hat build of OpenJDK 11 for Microsoft Windows installation path: If the path contains spaces, use the shortened path name. Restart Command Prompt to reload the environment variables. Set the value of PATH variable if it is not set already: Restart Command Prompt to reload the environment variables. Verify that java -version works without supplying the full path.

Commands:
C:\> setx /m JAVA_HOME "C:\Progra~1\RedHat\java-11-openjdk-11.0.1.13-1"
C:\> setx -m PATH "%PATH%;%JAVA_HOME%\bin";
C:\> java -version openjdk version "11.0.3" 2019-04-16 LTS OpenJDK Runtime Environment (build 11.0.3+7-LTS) OpenJDK 64-bit Server VM (build 11.0.3+7-LTS, mixed mode)
3.11. Cluster Networking Cluster level networking objects include: Clusters Logical Networks Figure 3.1. Networking within a cluster A data center is a logical grouping of multiple clusters and each cluster is a logical group of multiple hosts. Figure 3.1, "Networking within a cluster" depicts the contents of a single cluster. Hosts in a cluster all have access to the same storage domains. Hosts in a cluster also have logical networks applied at the cluster level. For a virtual machine logical network to become operational for use with virtual machines, the network must be defined and implemented for each host in the cluster using the Red Hat Virtualization Manager. Other logical network types can be implemented on only the hosts that use them. Multi-host network configuration automatically applies any updated network settings to all of the hosts within the data center to which the network is assigned.

Commands:
33.8. Defining DNS Query Policy To resolve host names within the DNS domain, a DNS client issues a query to the DNS name server. For some security contexts or for performance, it might be advisable to restrict what clients can query DNS records in the zone. DNS queries can be configured when the zone is created or when it is modified by using the --allow-query option with the ipa dnszone-mod command to set a list of clients which are allowed to issue queries. For example: The default --allow-query value is any , which allows the zone to be queried by any client.

Commands:
[user@server ~]USD ipa dnszone-mod --allow-query=192.0.2.0/24;2001:DB8::/32;203.0.113.1 example.com
Chapter 5. Configuring OAuth authorization This section describes how to connect Red Hat CodeReady Workspaces as an OAuth application to supported OAuth providers. Configuring GitHub OAuth Configuring OpenShift OAuth 5.1. Configuring GitHub OAuth OAuth for GitHub allows for automatic SSH key upload to GitHub. Procedure Set up the GitHub OAuth client . The Authorization callback URL is filled in the steps. Go to the RH-SSO administration console and select the Identity Providers tab. Select the GitHub identity provider in the drop-down list. Paste the Redirect URI to the Authorization callback URL of the GitHub OAuth application. Fill the Client ID and Client Secret from the GitHub oauth app. Enable Store Tokens . Save the changes of the Github Identity provider and click Register application in the GitHub oauth app page. 5.2. Configuring OpenShift OAuth For users to interact with OpenShift, they must first authenticate to the OpenShift cluster. OpenShift OAuth is a process in which users prove themselves to a cluster through an API with obtained OAuth access tokens. Authentication with the OpenShift connector plugin is a possible way for CodeReady Workspaces users to authenticate with an OpenShift cluster. The following section describes the OpenShift OAuth configuration options and its use with a CodeReady Workspaces. Prerequisites The OpenShift command-line tool, oc is installed. Procedure To enable OpenShift OAuth automatically, deployed CodeReady Workspaces using the crwctl with the --os-oauth option. See the crwctl server:start specification chapter. For CodeReady Workspaces deployed in single-user mode: Register CodeReady Workspaces OAuth client in OpenShift. See the Register an OAuth client in OpenShift chapter. Add the OpenShift SSL certificate to the CodeReady Workspaces Java trust store. See Adding self-signed SSL certificates to CodeReady Workspaces . Update the OpenShift deployment configuration. <client-ID> a name specified in the OpenShift OAuthClient. <openshift-secret> a secret specified in the OpenShift OAuthClient. <oauth-endpoint> the URL of the OpenShift OAuth service: For OpenShift 3 specify the OpenShift master URL. For OpenShift 4 specify the oauth-openshift route. <verify-token-url> request URL that is used to verify the token. <OpenShift master url>/api can be used for OpenShift 3 and 4. See CodeReady Workspaces configMaps and their behavior .

Commands:
oc create -f <(echo ' kind: OAuthClient apiVersion: oauth.openshift.io/v1 metadata: name: che secret: "<random set of symbols>" redirectURIs: - "<CodeReady Workspaces api url>/oauth/callback" grantMethod: prompt ')
CHE_OAUTH_OPENSHIFT_CLIENTID: <client-ID> CHE_OAUTH_OPENSHIFT_CLIENTSECRET: <openshift-secret> CHE_OAUTH_OPENSHIFT_OAUTH__ENDPOINT: <oauth-endpoint> CHE_OAUTH_OPENSHIFT_VERIFY__TOKEN__URL: <verify-token-url>
Chapter 1. Installing dynamic plugins with the Red Hat Developer Hub Operator You can store the configuration for dynamic plugins in a ConfigMap object that your Backstage custom resource (CR) can reference. Note If the pluginConfig field references environment variables, you must define the variables in your secrets-rhdh secret. Procedure From the OpenShift Container Platform web console, select the ConfigMaps tab. Click Create ConfigMap . From the Create ConfigMap page, select the YAML view option in Configure via and edit the file, if needed. Example ConfigMap object using the GitHub dynamic plugin kind: ConfigMap apiVersion: v1 metadata: name: dynamic-plugins-rhdh data: dynamic-plugins.yaml: | includes: - dynamic-plugins.default.yaml plugins: - package: './dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-dynamic' disabled: false pluginConfig: catalog: providers: github: organization: "USD{GITHUB_ORG}" schedule: frequency: { minutes: 1 } timeout: { minutes: 1 } initialDelay: { seconds: 100 } Click Create . Go to the Topology view. Click on the overflow menu for the Red Hat Developer Hub instance that you want to use and select Edit Backstage to load the YAML view of the Red Hat Developer Hub instance. Add the dynamicPluginsConfigMapName field to your Backstage CR. For example: apiVersion: rhdh.redhat.com/v1alpha1 kind: Backstage metadata: name: my-rhdh spec: application: # ... dynamicPluginsConfigMapName: dynamic-plugins-rhdh # ... Click Save . Navigate back to the Topology view and wait for the Red Hat Developer Hub pod to start. Click the Open URL icon to start using the Red Hat Developer Hub platform with the new configuration changes. Verification Ensure that the dynamic plugins configuration has been loaded, by appending /api/dynamic-plugins-info/loaded-plugins to your Red Hat Developer Hub root URL and checking the list of plugins: Example list of plugins [ { "name": "backstage-plugin-catalog-backend-module-github-dynamic", "version": "0.5.2", "platform": "node", "role": "backend-plugin-module" }, { "name": "backstage-plugin-techdocs", "version": "1.10.0", "role": "frontend-plugin", "platform": "web" }, { "name": "backstage-plugin-techdocs-backend-dynamic", "version": "1.9.5", "platform": "node", "role": "backend-plugin" }, ]

Commands:
kind: ConfigMap apiVersion: v1 metadata: name: dynamic-plugins-rhdh data: dynamic-plugins.yaml: | includes: - dynamic-plugins.default.yaml plugins: - package: './dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-dynamic' disabled: false pluginConfig: catalog: providers: github: organization: "USD{GITHUB_ORG}" schedule: frequency: { minutes: 1 } timeout: { minutes: 1 } initialDelay: { seconds: 100 }
apiVersion: rhdh.redhat.com/v1alpha1 kind: Backstage metadata: name: my-rhdh spec: application: dynamicPluginsConfigMapName: dynamic-plugins-rhdh
name: backstage-plugin-catalog-backend-module-github-dynamic
version: 0.5.2
platform: node
role: backend-plugin-module
name: backstage-plugin-techdocs
version: 1.10.0
role: frontend-plugin
platform: web
name: backstage-plugin-techdocs-backend-dynamic
version: 1.9.5
platform: node
role: backend-plugin
F.6. About Runnable Interfaces A Runnable Interface (also known as a Runnable) declares a single run() method, which executes the active part of the class' code. The Runnable object can be executed in its own thread after it is passed to a thread constructor. 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
4.222. perl-Net-DNS 4.222.1. RHBA-2011:1271 - perl-Net-DNS bug fix update An updated perl-Net-DNS package that fixes one bug is now available for Red Hat Enterprise Linux 6. The perl-Net-DNS package contains a collection of Perl modules that act as a Domain Name System (DNS) resolver. It allows the programmer to perform DNS queries that are beyond the capabilities of the gethostbyname and gethostbyaddr routines. Bug Fix BZ# 688211 Prior to this update, perl-Net-DNS lacked a complete IPv6 functionality. This update adds the dependencies related to IPv6 and, in addition, prevents the possibility of interactive (re)build. All users of perl-Net-DNS should upgrade to this updated package, which fixes this bug.

Commands:
Chapter 1. Installing Ansible plug-ins for Red Hat Developer Hub Ansible plug-ins for Red Hat Developer Hub deliver an Ansible-specific portal experience with curated learning paths, push-button content creation, integrated development tools, and other opinionated resources. Important The Ansible plug-ins are a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information on Red Hat Technology Preview features, see Technology Preview Features Scope . Additional detail on how Red Hat provides support for bundled community dynamic plugins is available on the Red Hat Developer Support Policy page. To install and configure the Ansible plugins, see Installing Ansible plug-ins for Red Hat Developer Hub .

Commands:
Chapter 24. system 24.1. system:framework 24.1.1. Description OSGi Framework options. 24.1.2. Syntax system:framework [options] [framework] 24.1.3. Arguments Name Description framework Name of the OSGi framework to use 24.1.4. Options Name Description -nodebug, --disable-debug Disable debug for the OSGi framework --help Display this help message -debug, --enable-debug Enable debug for the OSGi framework 24.2. system:name 24.2.1. Description Show or change Karaf instance name. 24.2.2. Syntax system:name [options] [name] 24.2.3. Arguments Name Description name New name for the instance 24.2.4. Options Name Description --help Display this help message 24.3. system:property 24.3.1. Description Get or set a system property. 24.3.2. Syntax system:property [options] [key] [value] 24.3.3. Arguments Name Description key The system property name value New value for the system property 24.3.4. Options Name Description --help Display this help message -f, --file-dump Dump all system properties in a file (in data folder) -p, --persistent Persist the new value to the etc/system.properties file -u, --unset Show unset know properties with value unset 24.4. system:shutdown 24.4.1. Description Shutdown the Karaf container. 24.4.2. Syntax system:shutdown [options] [time] 24.4.3. Arguments Name Description time Shutdown after a specified delay. The time argument can have different formats. First, it can be an absolute time in the format hh:mm, in which hh is the hour (1 or 2 digits) and mm is the minute of the hour (in two digits). Second, it can be in the format m (or +m), in which m is the number of minutes to wait. The word now is an alias for 0 (or +0). 24.4.4. Options Name Description -c, --clean, --clean-all, -ca Force a clean restart by deleting the data directory --help Display this help message -h, --halt Halt the Karaf container. -cc, --clean-cache, -cc Force a clean restart by deleting the cache directory -f, --force Force the shutdown without confirmation message. -r, --reboot Reboot the Karaf container. 24.5. system:start-level 24.5.1. Description Gets or sets the system start level. 24.5.2. Syntax system:start-level [options] [level] 24.5.3. Arguments Name Description level The new system start level to set 24.5.4. Options Name Description --help Display this help message 24.6. system:version 24.6.1. Description Display the instance version 24.6.2. Syntax system:version [options] 24.6.3. Options Name Description --help Display this help message

Commands:
19.7.2. Useful Websites http://web.mit.edu/kerberos/www/ - Kerberos: The Network Authentication Protocol webpage from MIT. http://www.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html - The Kerberos Frequently Asked Questions (FAQ). ftp://athena-dist.mit.edu/pub/kerberos/doc/usenix.PS - The PostScript version of Kerberos: An Authentication Service for Open Network Systems by Jennifer G. Steiner, Clifford Neuman, and Jeffrey I. Schiller. This document is the original paper describing Kerberos. http://web.mit.edu/kerberos/www/dialogue.html - Designing an Authentication System: a Dialogue in Four Scenes originally by Bill Bryant in 1988, modified by Theodore Ts'o in 1997. This document is a conversation between two developers who are thinking through the creation of a Kerberos-style authentication system. The conversational style of the discussion make this a good starting place for people who are completely unfamiliar with Kerberos. http://www.ornl.gov/~jar/HowToKerb.html - How to Kerberize your site is a good reference for kerberizing a network. http://www.networkcomputing.com/netdesign/kerb1.html - Kerberos Network Design Manual is a thorough overview of the Kerberos system.

Commands:
5.2.3. Define a target profile in virt-v2v.conf Now that you are able to connect to the conversion server as root, it must be pre-configured with details about what to do with the virtual machine it creates. These details are given as a target profile in the /etc/virt-v2v.conf file on the conversion server. Define a target profile in virt-v2v.conf : As root, edit /etc/virt-v2v.conf : Scroll to the end of the file. Before the final </virt-v2v> , add the following: Where: Profile Name is an arbitrary, descriptive target profile name. Method is the destination hypervisor type (rhev or libvirt). Storage Format is the output storage format, either raw or qcow2. Allocation is the output allocation policy, either preallocated or sparse. Network type specifies the network to which a network interface should be connected when imported into Red Hat Enterprise Virtualization. The first network type entry contains details about network configuration before conversion, the second network type entry maps to an after conversion configuration. In the given example, any detected network card is to be mapped to the managed network called rhevm. Important The value associated with the <storage format> tag (in the above example "nfs.share.com:/export1") must match the value associated with the <method> tag. In this example, since the output method is "rhev", the value associated with storage must be an initialized NFS share. For the libvirt method, the storage format value must be an initialized storage domain that exists locally on the conversion server, for example "default". You have created a target profile that defines what will happen to the virtual machine that results from this P2V conversion.

Commands:
nano /etc/virt-v2v.conf
<profile name="myrhev"> <method>rhev</method> <storage format="raw" allocation="preallocated"> nfs.share.com:/export1 </storage> <network type="default"> <network type="network" name="rhevm"/> </network> </profile>