mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 42. Hardware Enablement Trusted Computing Group TPM 2.0 System API library and management utilities available Two new packages have been added to Red Hat Enterprise Linux to support the Trusted Computing Group's Trusted Platform Module (TPM) 2.0 hardware as a Technology Preview: The tpm2-tss package adds the Intel implementation of the TPM 2.0 System API library. This library enables programs to interact with TPM 2.0 devices. The tpm2-tools package adds a set of utilities for management and utilization of TPM 2.0 devices from user space. (BZ# 1275027 , BZ#1275029) New package: tss2 The tss2 package adds IBM implementation of a Trusted Computing Group Software Stack (TSS) 2.0 as a Technology Preview. This package allows users to interact with TPM 2.0 devices. (BZ#1384452) LSI Syncro CS HA-DAS adapters Red Hat Enterprise Linux 7.1 included code in the megaraid_sas driver to enable LSI Syncro CS high-availability direct-attached storage (HA-DAS) adapters. While the megaraid_sas driver is fully supported for previously enabled adapters, the use of this driver for Syncro CS is available as a Technology Preview. Support for this adapter is provided directly by LSI, your system integrator, or system vendor. Users deploying Syncro CS on Red Hat Enterprise Linux 7.2 and later are encouraged to provide feedback to Red Hat and LSI. (BZ#1062759)

Commands:
Appendix A. Revision History Revision History Revision 1-1.37 Thu Jan 21 2016 Lenka Spackova Added information about the removed systemtap-grapher package to the Deprecated Functionality Chapter. Revision 1-1.36 Wed Jun 04 2014 Miroslav Svoboda Republished to include the latest description changes in the RHSA-2014:0634 kernel advisory. Revision 1-1.33 Wed Mar 12 2014 Miroslav Svoboda Republished to include the latest description changes in the RHSA-2014:0284 kernel advisory. Revision 1-1.32 Fri Jan 24 2014 Milan Navratil Republished to include Section 7.103.14, "RHBA-2013:0093 - kernel bug fix update" . Revision 1-1.30 Tue Dec 02 2013 Miroslav Svoboda Republished to include the latest description changes in the RHBA-2013-1770 kernel advisory. Revision 1-1.29 Fri Nov 29 2013 Miroslav Svoboda Republished to include Section 7.103.4, " RHBA-2013:1770 - kernel bug fix and enhancement update " and several other z-stream errata. Revision 1-1.26 Wed Oct 16 2013 Miroslav Svoboda Republished to include Section 7.103.5, " RHSA-2013:1436 - Moderate: kernel security and bug fix update " . Revision 1-1.25 Wed Aug 28 2013 Miroslav Svoboda Republished to include Section 7.103.6, " RHSA-2013:1173 - Important: kernel security and bug fix update " . Revision 1-1.22 Tue Jul 23 2013 Miroslav Svoboda Republished to include Section 7.103.7, " RHSA-2013:1051 - Moderate: kernel security and bug fix update " . Revision 1-1.21 Tue Jun 25 2013 Eliska Slobodova Republished to include a samba4 known issue. Revision 1-1.20 Tue Jun 11 2013 Miroslav Svoboda Republished to include Section 7.103.8, " RHSA-2013:0911 - Important: kernel security, bug fix and enhancement update " . Revision 1-1.17 Fri May 24 2013 Eliska Slobodova Removed the numad package from Technology Previews as it is now fully supported. Revision 1-1.15 Fri Apr 26 2013 Eliska Slobodova Republished the book to include a known issue. Revision 1-1.13 Fri Mar 22 2013 Miroslav Svoboda Republished to include Section 7.103.9, " RHSA-2013:0744 - Important: kernel security and bug fix update " . Revision 1-1.11 Fri Mar 22 2013 Martin Prpic Republished to include Section 7.128.1, " RHBA-2013:0664 - libvirt bug fix and enhancement update " . Revision 1-1.10 Tue Mar 12 2013 Eliska Slobodova Republished the book to include the RHSA-2013:0630 kernel advisory and a new known issue, BZ# 918647 . Revision 1-1.2 Mon Feb 25 2013 Martin Prpic Fixed incorrect lpfc driver version: BZ# 915284 . Revision 1-1.1 Thu Feb 21 2013 Eliska Slobodova Release of the Red Hat Enterprise Linux 6.4 Technical Notes.

Commands:
11.5. Deploying ACME Responder Once you have configured the ACME responder, deploy it using the following command: This creates a deployment descriptor at /etc/pki/pki-tomcat/Catalina/localhost/acme.xml . The PKI server starts the ACME responder automatically after a few seconds, you do not need to restart the server. To verify that the ACME responder is running, use the following command: For more information, see the pki-server-acme manpage.

Commands:
pki-server acme-deploy
curl -s -k https://USDHOSTNAME:8443/acme/directory | python -m json.tool { "meta": { "caaIdentities": [ "example.com" ], "externalAccountRequired": false, "termsOfService": "https://example.com/acme/tos.pdf", "website": "https://www.example.com" }, "newAccount": "https://<hostname>:8443/acme/new-account", "newNonce": "https://<hostname>:8443/acme/new-nonce", "newOrder": "https://<hostname>:8443/acme/new-order", "revokeCert": "https://<hostname>:8443/acme/revoke-cert" }
20.16.9.12. Specifying boot order To specify the boot order, use a management tool to make the following changes to the domain XML: ... <devices> <interface type='network'> <source network='default'/> <target dev='vnet1'/> <boot order='1'/> </interface> </devices> ... Figure 20.49. Specifying boot order For hypervisors which support it, you can set a specific NIC to be used for the network boot. The order of attributes determine the order in which devices will be tried during boot sequence. Note that the per-device boot elements cannot be used together with general boot elements in BIOS boot loader section.

Commands:
<devices> <interface type='network'> <source network='default'/> <target dev='vnet1'/> <boot order='1'/> </interface> </devices>
Chapter 15. Idling applications Cluster administrators can idle applications to reduce resource consumption. This is useful when the cluster is deployed on a public cloud where cost is related to resource consumption. If any scalable resources are not in use, OpenShift Container Platform discovers and idles them by scaling their replicas to 0 . The time network traffic is directed to the resources, the resources are unidled by scaling up the replicas, and normal operation continues. Applications are made of services, as well as other scalable resources, such as deployment configs. The action of idling an application involves idling all associated resources. 15.1. Idling applications Idling an application involves finding the scalable resources (deployment configurations, replication controllers, and others) associated with a service. Idling an application finds the service and marks it as idled, scaling down the resources to zero replicas. You can use the oc idle command to idle a single service, or use the --resource-names-file option to idle multiple services. 15.1.1. Idling a single service Procedure To idle a single service, run: USD oc idle <service> 15.1.2. Idling multiple services Idling multiple services is helpful if an application spans across a set of services within a project, or when idling multiple services in conjunction with a script to idle multiple applications in bulk within the same project. Procedure Create a file containing a list of the services, each on their own line. Idle the services using the --resource-names-file option: USD oc idle --resource-names-file <filename> Note The idle command is limited to a single project. For idling applications across a cluster, run the idle command for each project individually. 15.2. Unidling applications Application services become active again when they receive network traffic and are scaled back up their state. This includes both traffic to the services and traffic passing through routes. Applications can also be manually unidled by scaling up the resources. Procedure To scale up a DeploymentConfig, run: USD oc scale --replicas=1 dc <dc_name> Note Automatic unidling by a router is currently only supported by the default HAProxy router. Note Services do not support automatic unidling if you configure Kuryr-Kubernetes as an SDN.

Commands:
oc idle <service>
oc idle --resource-names-file <filename>
oc scale --replicas=1 dc <dc_name>
14.6.2. Domain Browsing By default, a Windows NT PDC for a domain is also the domain master browser for that domain. A Samba server must be set up as a domain master server in this type of situation. Network browsing may fail if the Samba server is running WINS along with other domain controllers in operation. For subnets that do not include the Windows NT PDC, a Samba server can be implemented as a local master browser. Configuring the smb.conf for a local master browser (or no browsing at all) in a domain controller environment is the same as workgroup configuration.

Commands:
23.11. Additional Resources The following sources of information provide additional resources regarding PTP and the ptp4l tools. 23.11.1. Installed Documentation ptp4l(8) man page - Describes ptp4l options including the format of the configuration file. pmc(8) man page - Describes the PTP management client and its command options. phc2sys(8) man page - Describes a tool for synchronizing the system clock to a PTP hardware clock (PHC).

Commands:
35.3. Configuring the Certificate Server Component To configure Certificate Server (CS) manually, open the /etc/pki/pki-tomcat/server.xml file. Set all occurrences of the sslVersionRangeStream and sslVersionRangeDatagram parameters to the following values: Alternatively, use the following command to replace the values for you: Restart CS:

Commands:
sslVersionRangeStream="tls1_2:tls1_2" sslVersionRangeDatagram="tls1_2:tls1_2"
sed -i 's/tls1_[01]:tls1_2/tls1_2:tls1_2/g' /etc/pki/pki-tomcat/server.xml
systemctl restart pki-tomcatd@pki-tomcat.service
Appendix A. About Service Interconnect documentation Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message . Revised on 2025-02-24 19:05:05 UTC

Commands:
Chapter 17. Inviting users to your RHACS instance By inviting users to Red Hat Advanced Cluster Security for Kubernetes (RHACS), you can ensure that the right users have the appropriate access rights within your cluster. You can invite one or more users by assigning roles and defining the authentication provider. 17.1. Configuring access control and sending invitations By configuring access control in the RHACS portal, you can invite users to your RHACS instance. Procedure In the RHACS portal, go to the Platform Configuration Access Control Auth providers tab, and then click Invite users . In the Invite users dialog box, provide the following information: Emails to invite : Enter one or more email addresses of the users you want to invite. Ensure that they are valid email addresses associated with the intended recipients. Provider : From the drop-down list, select a provider you want to use for each invited user. Important If you have only one authentication provider available, it is selected by default. If multiple authentication providers are available and at least one of them is Red Hat SSO or Default Internal SSO , that provider is selected by default. If multiple authentication providers are available, but none of them is Red Hat SSO or Default Internal SSO , you are prompted to select one manually. If you have not yet set up an authentication provider, a warning message appears and the form is disabled. Click the link, which takes you to the Access Control section to configure an authentication provider. Role : From the drop-down list, select the role to assign to each invited user. Click Invite users . On the confirmation dialog box, you receive a confirmation that the users have been created with the selected role. Copy the one or more email addresses and the message into an email that you create in your own email client, and send it to the users. Click Done . Verification In the RHACS portal, go to the Platform Configuration Access Control Auth providers tab. Select the authentication provider you used to invite users. Scroll down to the Rules section. Verify that the user emails and authentication provider roles have been added to the list.

Commands:
Chapter 2. AMQ Streams deployment of Kafka Apache Kafka components are provided for deployment to OpenShift with the AMQ Streams distribution. The Kafka components are generally run as clusters for availability. A typical deployment incorporating Kafka components might include: Kafka cluster of broker nodes ZooKeeper cluster of replicated ZooKeeper instances Kafka Connect cluster for external data connections Kafka MirrorMaker cluster to mirror the Kafka cluster in a secondary cluster Kafka Exporter to extract additional Kafka metrics data for monitoring Kafka Bridge to make HTTP-based requests to the Kafka cluster Cruise Control to rebalance topic partitions across broker nodes Not all of these components are mandatory, though you need Kafka and ZooKeeper as a minimum. Some components can be deployed without Kafka, such as MirrorMaker or Kafka Connect. 2.1. Kafka component architecture A cluster of Kafka brokers handles delivery of messages. A broker uses Apache ZooKeeper for storing configuration data and for cluster coordination. Before running Apache Kafka, an Apache ZooKeeper cluster has to be ready. Each of the other Kafka components interact with the Kafka cluster to perform specific roles. Kafka component interaction Apache ZooKeeper Apache ZooKeeper is a core dependency for Kafka as it provides a cluster coordination service, storing and tracking the status of brokers and consumers. ZooKeeper is also used for controller election. Kafka Connect Kafka Connect is an integration toolkit for streaming data between Kafka brokers and other systems using Connector plugins. Kafka Connect provides a framework for integrating Kafka with an external data source or target, such as a database, for import or export of data using connectors. Connectors are plugins that provide the connection configuration needed. A source connector pushes external data into Kafka. A sink connector extracts data out of Kafka External data is translated and transformed into the appropriate format. You can deploy Kafka Connect with build configuration that automatically builds a container image with the connector plugins you require for your data connections. Kafka MirrorMaker Kafka MirrorMaker replicates data between two Kafka clusters, within or across data centers. MirrorMaker takes messages from a source Kafka cluster and writes them to a target Kafka cluster. Kafka Bridge Kafka Bridge provides an API for integrating HTTP-based clients with a Kafka cluster. Kafka Exporter Kafka Exporter extracts data for analysis as Prometheus metrics, primarily data relating to offsets, consumer groups, consumer lag and topics. Consumer lag is the delay between the last message written to a partition and the message currently being picked up from that partition by a consumer

Commands:
14.2. ID Range Assignments During Installation During server installation, the ipa-server-install command by default automatically assigns a random current ID range to the installed server. The setup script randomly selects a range of 200,000 IDs from a total of 10,000 possible ranges. Selecting a random range in this way significantly reduces the probability of conflicting IDs in case you decide to merge two separate IdM domains in the future. However, you can define a current ID range manually during server installation by using the following two options with ipa-server-install : --idstart gives the starting value for UID and GID numbers; by default, the value is selected at random, --idmax gives the maximum UID and GID number; by default, the value is the --idstart starting value plus 199,999. If you have a single IdM server installed, a new user or group entry receives a random ID from the whole range. When you install a new replica and the replica requests its own ID range, the initial ID range for the server splits and is distributed between the server and replica: the replica receives half of the remaining ID range that is available on the initial master. The server and replica then use their respective portions of the original ID range for new entries. Also, if less than 100 IDs from the ID range that was assigned to a replica remain, meaning the replica is close to depleting its allocated ID range, the replica contacts the other available servers with a request for a new ID range. A server receives an ID range the first time the DNA plug-in is used; until then, the server has no ID range defined. For example, when you create a replica from a master server, the replica does not receive an ID range immediately. The replica requests an ID range from the initial master only when the first ID is about to be assigned on the replica. Note If the initial master stops functioning before the replica requests an ID range from it, the replica is unable to contact the master with a request for the ID range. An attempt to add a new user on the replica fails. In such situations, you can find out what ID range is assigned to the disabled master and assign an ID range to the replica manually, which is described in Section 14.5, "Manual ID Range Extension and Assigning a New ID Range" .

Commands:
Chapter 1. Support policy Red Hat will support select major versions of Red Hat build of OpenJDK in its products. For consistency, these are the same versions that Oracle designates as long-term support (LTS) for the Oracle JDK. A major version of Red Hat build of OpenJDK will be supported for a minimum of six years from the time that version is first introduced. For more information, see the OpenJDK Life Cycle and Support Policy . Note RHEL 6 reached the end of life in November 2020. Because of this, Red Hat build of OpenJDK is not supporting RHEL 6 as a supported configuration.

Commands:
4.16. Thumbnail Protection The thumbnail icons can potentially allow an attacker to break into a locked machine using removable media, such as USB devices or CDs. When the system detects a removable media, the Nautilus file manager executes the thumbnail driver code to display thumbnail icons in an appropriate file browser even if the machine is locked. This behavior is unsafe because if the thumbnail executables were vulnerable, the attacker could use the thumbnail driver code to bypass the lock screen without entering the password. Therefore, a new SELinux policy is used to prevent such attacks. This policy ensures that all thumbnail drivers are locked when the screen is locked. The thumbnail protection is enabled for both confined users and unconfined users. This policy affects the following applications: /usr/bin/evince-thumbnailer /usr/bin/ffmpegthumbnailer /usr/bin/gnome-exe-thumbnailer.sh /usr/bin/gnome-nds-thumbnailer /usr/bin/gnome-xcf-thumbnailer /usr/bin/gsf-office-thumbnailer /usr/bin/raw-thumbnailer /usr/bin/shotwell-video-thumbnailer /usr/bin/totem-video-thumbnailer /usr/bin/whaaw-thumbnailer /usr/lib/tumbler-1/tumblerd /usr/lib64/tumbler-1/tumblerd

Commands:
4.3.9. Splitting a Volume Group To split the physical volumes of a volume group and create a new volume group, use the vgsplit command. Logical volumes cannot be split between volume groups. Each existing logical volume must be entirely on the physical volumes forming either the old or the new volume group. If necessary, however, you can use the pvmove command to force the split. The following example splits off the new volume group smallvg from the original volume group bigvg .

Commands:
vgsplit bigvg smallvg /dev/ram15 Volume group "smallvg" successfully split from "bigvg"
Chapter 7. Migration from versions of .NET 7.1. Migration from versions of .NET Microsoft provides instructions for migrating from most versions of .NET Core. If you are using a version of .NET that is no longer supported or want to migrate to a newer .NET version to expand functionality, see the following articles: Migrate from ASP.NET Core 7.0 to 8.0 Migrate from ASP.NET Core 6.0 to 7.0 Migrate from ASP.NET Core 5.0 to 6.0 Migrate from ASP.NET Core 3.1 to 5.0 Migrate from ASP.NET Core 3.0 to 3.1 Migrate from ASP.NET Core 2.2 to 3.0 Migrate from ASP.NET Core 2.1 to 2.2 Migrate from .NET Core 2.0 to 2.1 Migrate from ASP.NET to ASP.NET Core Migrating .NET Core projects from project.json Migrate from project.json to .csproj format Note If migrating from .NET Core 1.x to 2.0, see the first few related sections in Migrate from ASP.NET Core 1.x to 2.0 . These sections provide guidance that is appropriate for a .NET Core 1.x to 2.0 migration path. 7.2. Porting from .NET Framework Refer to the following Microsoft articles when migrating from .NET Framework: For general guidelines, see Porting to .NET Core from .NET Framework . For porting libraries, see Porting to .NET Core - Libraries . For migrating to ASP.NET Core, see Migrating to ASP.NET Core . Several technologies and APIs present in the .NET Framework are not available in .NET Core and .NET. If your application or library requires these APIs, consider finding alternatives or continue using the .NET Framework. .NET Core and .NET do not support the following technologies and APIs: Desktop applications, for example, Windows Forms and Windows Presentation Foundation (WPF) Windows Communication Foundation (WCF) servers (WCF clients are supported) .NET remoting Additionally, several .NET APIs can only be used in Microsoft Windows environments. The following list shows examples of these Windows-specific APIs: Microsoft.Win32.Registry System.AppDomains System.Security.Principal.Windows Important Several APIs that are not supported in the default version of .NET may be available from the Microsoft.Windows.Compatibility NuGet package. Be careful when using this NuGet package. Some of the APIs provided (such as Microsoft.Win32.Registry ) only work on Windows, making your application incompatible with Red Hat Enterprise Linux.

Commands:
B.3.2. Web Server Configuration The following procedure configures an Apache HTTP server. Ensure that the Apache HTTP server is installed on each node in the cluster. You also need the wget tool installed on the cluster to be able to check the status of Apache. On each node, execute the following command. In order for the Apache resource agent to get the status of Apache, ensure that the following text is present in the /etc/httpd/conf/httpd.conf file on each node in the cluster, and ensure that it has not been commented out. If this text is not already present, add the text to the end of the file. Create a web page for Apache to serve up. On one node in the cluster, mount the file system you created in Section B.3.1, "Configuring an LVM Volume with an ext4 File System" , create the file index.html on that file system, then unmount the file system.

Commands:
yum install -y httpd wget
<Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from 127.0.0.1 </Location>
mount /dev/my_vg/my_lv /var/www/ mkdir /var/www/html mkdir /var/www/cgi-bin mkdir /var/www/error restorecon -R /var/www cat <<-END >/var/www/html/index.html <html> <body>Hello</body> </html> END umount /var/www
Release notes OpenShift Container Platform 4.18 Highlights of what is new and what has changed with this OpenShift Container Platform release Red Hat OpenShift Documentation Team

Commands:
conditionalGathererEndpoint: https://console.redhat.com/api/gathering/v2/%s/gathering_rules
oc patch featuregates cluster -p '{"spec": {"featureSet": "TechPreviewNoUpgrade"}}' --type=merge
Warning: unknown field "metadata" You don't have any projects. You can try to create a new project, by running oc new-project <projectname>
oc delete pod -l app=ovnkube-node -n openshift-ovn-kubernetes
oc adm release info 4.18.4 --pullspecs
oc adm release info 4.18.3 --pullspecs
oc adm release info 4.18.2 --pullspecs
oc adm release info 4.18.1 --pullspecs