mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Example Script

Commands:
#!/usr/bin/env python from __future__ import print_function import sys import requests from datetime import datetime, timedelta API_HOST = 'https://access.redhat.com/product-life-cycles/api/v1' def get_data(query): full_query = API_HOST + query r = requests.get(full_query) if r.status_code != 200: print('ERROR: Invalid request; returned {} for the following ' 'query:\n{}'.format(r.status_code, full_query)) sys.exit(1) if not r.json(): print('No data returned with the following query:') print(full_query) sys.exit(0) return r.json() Get RHEL and Openshift Container Platform 4 life cycle data endpoint = '/products' params = 'name=Red Hat Enterprise Linux,Openshift Container Platform 4' data = get_data(endpoint + '?' + params) products = data['data'] for product in products: print(product) Get RHEL and Openshift Container Platform 4 life cycle data using legacy JSON endpoint endpoint = '/plccapi/lifecycle.json' params = 'products=Red Hat Enterprise Linux,Openshift Container Platform 4' data = get_data(endpoint + '?' + params) for product in data: print(product) print('-----')
Chapter 2. Viewing subscription status The status tiles on the Subscription Inventory page show the number of subscriptions in your inventory that are active, already expired, expiring soon, or scheduled to become active on a future date. Active The subscription term has started based on the terms of the contract. You can use the subscription. Expired The subscription term has ended based on the terms of the contract. You must renew the subscription to activate it. Expiring soon The subscription is scheduled to expire within 30 days. You must renew the subscription before the end date to keep it active. Future dated The subscription is scheduled to become active within 30 days. You can begin using the subscription on the start date. Subscriptions can have more than one status. For example, an active subscription that is scheduled to expire within 30 days will be counted on both the Active and Expiring soon tiles.

Commands:
7.306. authd 7.306.1. RHBA-2013:1168 - authd bug fix update Updated authd packages that fix one bug are now available for Red Hat Enterprise Linux 6. The authd package contains a small and fast RFC 1413 Ident Protocol daemon with both xinetd server and interactive modes that supports IPv6 and IPv4 as well as the more popular features of pidentd. Bug Fix BZ# 994118 If authd encountered a negative UID when reading a /proc/net/tcp entry then it stopped reading at that point, and failed to identify the connection it was looking for. Consequently, authd returned a "non-existent user" error response. With this update, the handling of negative UID values in authd is modified, and authd correctly reports a valid user. Users of authd are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 11. Compiler and Tools Git cannot be used with HTTP or HTTPS and SSO Git provides the http.delegation configuration variable, which corresponds to the cURL --delegation parameter, for use when delegation of Kerberos tickets is required. However, Git included in Red Hat Enterprise Linux 6 contains irrelevant checks of the version of the libcurl library while required fixes are provided by a different version of libcurl on RHEL 6 systems. As a consqeuence, using Git with Single Sign-On on HTTP or HTTPS connections fails. To work around this problem, use the Git version provided by the rh-git29 Software Collection from Red Hat Software Collections. (BZ# 1430723 )

Commands:
18.12.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6 Protocol ID: igmp-ipv6, esp-ipv6, ah-ipv6, udplite-ipv6, all-ipv6 The chain parameter is ignored for this type of traffic and should either be omitted or set to root. Table 18.14. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv protocol types Attribute Name Datatype Definition srcmacaddr MAC_ADDR MAC address of sender srcipaddr IP_ADDR Source IP address srcipmask IP_MASK Mask applied to source IP address dstipaddr IP_ADDR Destination IP address dstipmask IP_MASK Mask applied to destination IP address srcipfrom IP_ADDR start of range of source IP address scripto IP_ADDR end of range of source IP address dstipfrom IP_ADDR Start of range of destination IP address dstipto IP_ADDR End of range of destination IP address comment STRING text string up to 256 characters state STRING comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE ipset STRING The name of an IPSet managed outside of libvirt ipsetflags IPSETFLAGS flags for the IPSet; requires ipset attribute

Commands:
Chapter 5. Installing the policy system Installing the Skupper policy system on a cluster allows you control how Skupper is used on the cluster. Note Applying the policy system in a cluster without specific policy rules prohibits site linking and service exposure. If you are installing the policy system on a cluster where there are existing sites, you must create policies before installing the policy system to avoid disruption. Prerequisites Access to a Kubernetes cluster with cluster-admin privileges. The Red Hat Service Interconnect Operator is installed Procedure Log into your cluster. Deploy the policy CRD: where the contents of skupper_cluster_policy_crd.yaml is specified in the Appendix A, YAML for the Skupper policy CRD appendix. Additional information See Securing a service network using policies for more information about using policies.

Commands:
kubectl apply -f skupper_cluster_policy_crd.yaml customresourcedefinition.apiextensions.k8s.io/skupperclusterpolicies.skupper.io created clusterrole.rbac.authorization.k8s.io/skupper-service-controller created
8.166. python-weberror 8.166.1. RHBA-2013:1723 - python-weberror bug fix update An updated python-weberror package that fixes one bug is now available for Red Hat Enterprise Linux 6. The python-weberror package provides WebError, a web application's error handing library for use as a Web Server Gateway Interface (WSGI) middleware. Bug Fix BZ# 746118 Previously, the WebError middleware used the MD5 algorithm when assigning an identifier to the handled error. However, this algorithm is not, by default, supported by Python's runtime in FIPS mode. Consequently, when web applications raised an exception in FIPS mode and the exception was handled by WebError, incomplete error diagnostics were provided. With this update, error identification based on MD5 is not generated automatically, thus avoiding the problems when the error identifier is not processed further. Users of python-weberror are advised to upgrade to this updated package, which fixes this bug.

Commands:
7.3. Network Bonding Using the NetworkManager Command Line Tool, nmcli Note See Section 3.3, "Configuring IP Networking with nmcli" for an introduction to nmcli . To create a bond connection with the nmcli tool, issue the following command: Note that as no con-name was given for the bond, the connection name was derived from the interface name by prepending the type. NetworkManager supports most of the bonding options provided by the kernel. For example: To add a port interface: Create a new connection, see Section 3.3.5, "Creating and Modifying a Connection Profile with nmcli" for details. Set the controller property to the bond interface name, or to the name of the controller connection: To add a new port interface, repeat the command with the new interface. For example: To activate the ports, issue a command as follows: When you activate a port, the controller connection also starts. You can see Section 7.1, "Understanding the Default Behavior of Controller and Port Interfaces" for more information. In this case, it is not necessary to manually activate the controller connection. It is possible to change the active_slave option and the primary option of the bond at runtime, without deactivating the connection. For example to change the active_slave option, issue the following command: or to change the primary option: Note The active_slave option sets the currently active port whereas the primary option of the bond specifies the active port to be automatically selected by kernel when a new port is added or a failure of the active port occurs.

Commands:
~]USD nmcli con add type bond ifname mybond0 Connection 'bond-mybond0' (5f739690-47e8-444b-9620-1895316a28ba) successfully added.
~]USD nmcli con add type bond ifname mybond0 bond.options "mode=balance-rr,miimon=100" Connection 'bond-mybond0' (5f739690-47e8-444b-9620-1895316a28ba) successfully added.
~]USD nmcli con add type ethernet ifname ens3 master mybond0 Connection 'bond-slave-ens3' (220f99c6-ee0a-42a1-820e-454cbabc2618) successfully added.
~]USD nmcli con add type ethernet ifname ens7 master mybond0 Connection 'bond-slave-ens7' (ecc24c75-1c89-401f-90c8-9706531e0231) successfully added.
~]USD nmcli con up bond-slave- ens7 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/14)
~]USD nmcli con up bond-slave- ens3 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/15)
~]USD nmcli dev mod bond0 +bond.options "active_slave= ens7 " Connection successfully reapplied to device 'bond0'.
~]USD nmcli dev mod bond0 +bond.options "primary= ens3 " Connection successfully reapplied to device 'bond0'.
18.4. Saving iptables Rules Rules created with the iptables command are stored in memory. If the system is restarted before saving the iptables rule set, all rules are lost. For netfilter rules to persist through system reboot, they need to be saved. To do this, log in as root and type: This executes the iptables initscript, which runs the /sbin/iptables-save program and writes the current iptables configuration to /etc/sysconfig/iptables . The existing /etc/sysconfig/iptables file is saved as /etc/sysconfig/iptables.save . The time the system boots, the iptables init script reapplies the rules saved in /etc/sysconfig/iptables by using the /sbin/iptables-restore command. While it is always a good idea to test a new iptables rule before committing it to the /etc/sysconfig/iptables file, it is possible to copy iptables rules into this file from another system's version of this file. This provides a quick way to distribute sets of iptables rules to multiple machines. Important If distributing the /etc/sysconfig/iptables file to other machines, type /sbin/service iptables restart for the new rules to take effect.

Commands:
/sbin/service iptables save
5.333. tog-pegasus 5.333.1. RHBA-2012:0953 - tog-pegasus bug fix update Updated tog-pegasus packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The tog-pegasus packages provide OpenPegasus Web-Based Enterprise Management (WBEM) services for Linux. WBEM enables management solutions that deliver increased control of enterprise resources. WBEM is a platform and resource independent Distributed Management Task Force (DMTF) standard that defines a common information model (CIM) and communication protocol for monitoring and controlling resources from diverse sources. Bug Fixes BZ# 796191 Previously, with the Single Chunk Memory Objects (SCMO) implementation, empty string values in embedded instances were converted to null values during the embedded CIMInstance to SCMOInstance conversion. This was due to the usage of the _setString() function that set the string size to 0 if the string was empty. This broke functionality of the existing providers. A backported upstream patch uses the _SetBinary() function instead which is already used while setting the string values on the normal SCMOInstance. BZ# 799040 Previously, the tog-pegasus packages did not provide a generic "cim-server", which could be required by packages that do not need a specific implementation of the CIM server as a dependency. With this update, the tog-pegasus packages provide a generic "cim-server" that can be required by such packages. All users of tog-pegasus are advised to upgrade to these updated packages, which fix these bugs.

Commands:
9.2. Run Red Hat JBoss Data Virtualization in a Google Compute Instance Procedure 9.2. Run Red Hat JBoss Data Virtualization in a Google Compute Instance Open the necessary ports: Google Developers Console -> Compute -> Compute Engine -> VM Instance -> [name of your instance] -> Network . Upload your public SSH key: Google Developers Console - Compute -> Compute Engine -> VM Instance -> [name of your instance] -> SSH Keys . Bind the management ports (jboss.bind.address.management) to an external interface. (The default value for management ports is localhost .)

Commands:
4.3. Adding Hosts Each diskless client must have its own snapshot directory on the NFS server that is used as its read/write file system. The Network Booting Tool can be used to create these snapshot directories. After completing the steps in Section 4.2, "Finish Configuring the Diskless Environment" , a window appears to allow hosts to be added for the diskless environment. Click the New button. In the dialog shown in Figure 4.1, "Add Diskless Host" , provide the following information: Hostname or IP Address/Subnet - Specify the hostname or IP address of a system to add it as a host for the diskless environment. Enter a subnet to specify a group of systems. Operating System - Select the diskless environment for the host or subnet of hosts. Serial Console - Select this checkbox to perform a serial installation. Snapshot name - Provide a subdirectory name to be used to store all of the read/write content for the host. Ethernet - Select the Ethernet device on the host to use to mount the diskless environment. If the host only has one Ethernet card, select eth0 . Ignore the Kickstart File option. It is only used for PXE installations. Figure 4.1. Add Diskless Host In the existing snapshot/ directory in the diskless directory, a subdirectory is created with the Snapshot name specified as the file name. Then, all of the files listed in snapshot/files and snapshot/files.custom are copied copy from the root/ directory to this new directory.

Commands:
A.2. VDSM Hooks VDSM is extensible via hooks. Hooks are scripts executed on the host when key events occur. When a supported event occurs VDSM runs any executable hook scripts in /usr/libexec/vdsm/hooks/ nn_event-name / on the host in alphanumeric order. By convention each hook script is assigned a two digit number, included at the front of the file name, to ensure that the order in which the scripts will be run in is clear. You are able to create hook scripts in any programming language, Python will however be used for the examples contained in this chapter. Note that all scripts defined on the host for the event are executed. If you require that a given hook is only executed for a subset of the virtual machines which run on the host then you must ensure that the hook script itself handles this requirement by evaluating the Custom Properties associated with the virtual machine. Warning VDSM hooks can interfere with the operation of Red Hat Virtualization. A bug in a VDSM hook has the potential to cause virtual machine crashes and loss of data. VDSM hooks should be implemented with caution and tested rigorously. The Hooks API is new and subject to significant change in the future.

Commands:
Chapter 150. XML Tokenize The XML Tokenize language is a built-in language in camel-xml-jaxp , which is a truly XML-aware tokenizer that can be used with the Split EIP as the conventional Tokenize to efficiently and effectively tokenize XML documents.. XML Tokenize is capable of not only recognizing XML namespaces and hierarchical structures of the document but also more efficiently tokenizing XML documents than the conventional Tokenize language. 150.1. Dependencies When using xtokenize with Red Hat build of Camel Spring Boot make sure to use the following Maven dependency to have support for auto configuration: <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-xml-jaxp-starter</artifactId> </dependency> Additional dependency In order to use this component, an additional dependency is required as follows: <dependency> <groupId>org.codehaus.woodstox</groupId> <artifactId>woodstox-core-asl</artifactId> <version>4.4.1</version> </dependency> or <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-stax-starter</artifactId> </dependency> 150.2. XML Tokenizer Options The XML Tokenize language supports 4 options, which are listed below. Name Default Java Type Description headerName String Name of header to tokenize instead of using the message body. mode Enum The extraction mode. The available extraction modes are: i - injecting the contextual namespace bindings into the extracted token (default) w - wrapping the extracted token in its ancestor context u - unwrapping the extracted token to its child content t - extracting the text content of the specified element. Enum values: i w u t group Integer To group N parts together. trim Boolean Whether to trim the value to remove leading and trailing whitespaces and line breaks. 150.3. Example See Split EIP which has examples using the XML Tokenize language. 150.4. Spring Boot Auto-Configuration The component supports 3 options, which are listed below. Name Description Default Type camel.language.xtokenize.enabled Whether to enable auto configuration of the xtokenize language. This is enabled by default. Boolean camel.language.xtokenize.mode The extraction mode. The available extraction modes are: i - injecting the contextual namespace bindings into the extracted token (default) w - wrapping the extracted token in its ancestor context u - unwrapping the extracted token to its child content t - extracting the text content of the specified element. String camel.language.xtokenize.trim Whether to trim the value to remove leading and trailing whitespaces and line breaks. true Boolean

Commands:
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-xml-jaxp-starter</artifactId> </dependency>
<dependency> <groupId>org.codehaus.woodstox</groupId> <artifactId>woodstox-core-asl</artifactId> <version>4.4.1</version> </dependency>
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-stax-starter</artifactId> </dependency>
20.16.9.15. Setting VLAN tag (on supported network types only) To specify the VLAN tag configuration settings, use a management tool to make the following changes to the domain XML: ... <devices> <interface type='bridge'> <vlan> <tag id='42'/> </vlan> <source bridge='ovsbr0'/> <virtualport type='openvswitch'> <parameters interfaceid='09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'/> </virtualport> </interface> <devices> ... Figure 20.52. Setting VLAN tag (on supported network types only) If (and only if) the network connection used by the guest virtual machine supports vlan tagging transparent to the guest virtual machine, an optional vlan element can specify one or more vlan tags to apply to the guest virtual machine's network traffic (openvswitch and type='hostdev' SR-IOV interfaces do support transparent vlan tagging of guest virtual machine traffic; everything else, including standard Linux bridges and libvirt's own virtual networks, do not support it. 802.1Qbh (vn-link) and 802.1Qbg (VEPA) switches provide their own way (outside of libvirt) to tag guest virtual machine traffic onto specific vlans.) To allow for specification of multiple tags (in the case of vlan trunking), a subelement, tag , specifies which vlan tag to use (for example: tag id='42'/ . If an interface has more than one vlan element defined, it is assumed that the user wants to do VLAN trunking using all the specified tags. In the case that vlan trunking with a single tag is desired, the optional attribute trunk='yes' can be added to the toplevel vlan element.

Commands:
<devices> <interface type='bridge'> <vlan> <tag id='42'/> </vlan> <source bridge='ovsbr0'/> <virtualport type='openvswitch'> <parameters interfaceid='09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'/> </virtualport> </interface> <devices>
Appendix C. Revision History Revision History Revision 1-502 Mon Mar 08 2017 Jiri Herrmann Updates for the 6.9 GA release Revision 1-501 Mon May 02 2016 Jiri Herrmann Updates for the 6.8 GA release Revision 1-500 Thu Mar 01 2016 Jiri Herrmann Multiple updates for the 6.8 beta release Revision 1-449 Thu Oct 08 2015 Jiri Herrmann Cleaned up the Revision History Revision 1-447 Fri Jul 10 2015 Dayle Parker Updates for the 6.7 GA release.

Commands:
Chapter 10. Dashboard (horizon) Parameters You can modify the horizon service with dashboard parameters. Parameter Description HorizonAllowedHosts A list of IP/Hostname for the server OpenStack Dashboard (horizon) is running on. Used for header checks. The default value is * . HorizonCustomizationModule OpenStack Dashboard (horizon) has a global overrides mechanism available to perform customizations. HorizonHelpURL On top of dashboard there is a Help button. This button could be used to re-direct user to vendor documentation or dedicated help portal. The default value is https://access.redhat.com/documentation/en-us/red_hat_openstack_platform . HorizonPasswordValidator Regex for password validation. HorizonPasswordValidatorHelp Help text for password validation. HorizonSecret Secret key for the webserver. HorizonSecureCookies Set CSRF_COOKIE_SECURE / SESSION_COOKIE_SECURE in OpenStack Dashboard (horizon). The default value is False . HorizonVhostExtraParams Extra parameters for OpenStack Dashboard (horizon) vhost configuration. The default value is {'add_listen': True, 'priority': 10, 'access_log_format': '%a %l %u %t \\"%r\\" %>s %b \\"%%{}{Referer}i\\" \\"%%{}{User-Agent}i\\"', 'options': ['FollowSymLinks', 'MultiViews']} . MemcachedIPv6 Enable IPv6 features in Memcached. The default value is False . TimeZone The timezone to be set on the overcloud. The default value is UTC . WebSSOChoices Specifies the list of SSO authentication choices to present. Each item is a list of an SSO choice identifier and a display message. The default value is [['OIDC', 'OpenID Connect']] . WebSSOEnable Enable support for Web Single Sign-On. The default value is False . WebSSOIDPMapping Specifies a mapping from SSO authentication choice to identity provider and protocol. The identity provider and protocol names must match the resources defined in keystone. The default value is {'OIDC': ['myidp', 'openid']} . WebSSOInitialChoice The initial authentication choice to select by default. The default value is OIDC .

Commands: