mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. IdM server performance recommendations The following table shows the maximum number of users and clients that you can add or enroll to the IdM environment at the same time that ensure a stable performance of your IdM server. Table 3.1. Maximum number per IdM server Action Description Number Client enrollments The maximum number of the IdM clients that you can enroll with an IdM server at the same time before enrollment starts failing. 130 Adding users The maximum number of users you can add at the same time using the ipa user-add[] command from different IdM clients before failing to add a user. You can add more users over the same amount of time by using the IdM API batch command. We recommend adding users in batches of 100 users. For more details about batch command, see Using batches for executing IdM API commands . 325 Client authentications The maximum number of the IdM clients that can authenticate at the same time before authentications start to fail. 800 Adding a member to a user group The recommended number of members in a group that you can add without exceeding time for adding a new member to a group. IdM has a two-seconds rule as a normal time frame for adding a member to a group. You can add more members, but the time of the action will progressively extend. 1500

Commands:
B.3. How to Set Up Red Hat Virtualization Manager to Use FCoE You can configure Fibre Channel over Ethernet (FCoE) properties for host network interface cards from the Administration Portal. The fcoe key is not available by default and needs to be added to the Manager using the engine configuration tool. You can check whether fcoe has already been enabled by running the following command: # engine-config -g UserDefinedNetworkCustomProperties You also need to install the required VDSM hook package on the hosts. Depending on the FCoE card on the hosts, special configuration may also be needed; see Configuring Fibre Channel over Ethernet in Red Hat Enterprise Linux Managing storage devices . Procedure On the Manager, run the following command to add the key: # engine-config -s UserDefinedNetworkCustomProperties='fcoe=^((enable|dcb|auto_vlan)=(yes|no),?)*USD' Restart the ovirt-engine service: # systemctl restart ovirt-engine.service Install the VDSM hook package on each of the Red Hat Enterprise Linux hosts on which you want to configure FCoE properties. The package is available by default on Red Hat Virtualization Host (RHVH). # dnf install vdsm-hook-fcoe The fcoe key is now available in the Administration Portal. See Editing Host Network Interfaces and Assigning Logical Networks to Hosts to apply FCoE properties to logical networks.

Commands:
engine-config -g UserDefinedNetworkCustomProperties
engine-config -s UserDefinedNetworkCustomProperties='fcoe=^((enable|dcb|auto_vlan)=(yes|no),?)*USD'
systemctl restart ovirt-engine.service
dnf install vdsm-hook-fcoe
10.4.4. Problems with the X Server Crashing and Non-Root Users If you are having trouble with the X server crashing when anyone logs in, you may have a full file system (or, a lack of available hard drive space). To verify that this is the problem you are experiencing, run the following command: The df command should help you diagnose which partition is full. For additional information about df and an explanation of the options available (such as the -h option used in this example), refer to the df man page by typing man df at a shell prompt. A key indicator is 100% full or a percentage above 90% or 95% on a partition. The /home/ and /tmp/ partitions can sometimes fill up quickly with user files. You can make some room on that partition by removing old files. After you free up some disk space, try running X as the user that was unsuccessful before.

Commands:
df -h
Release notes Red Hat OpenShift AI Cloud Service 1 Features, enhancements, resolved issues, and known issues associated with this release

Commands:
Bad value for --endpoint-url "cp": scheme is missing. Must be of the form http://<hostname>/ or https://<hostname>/
the object provided is unrecognized (must be of type Secret): couldn't get version/kind; json parse error: unexpected end of JSON input ({"apiVersion":"v1","kind":"Sec ...)
oc get kfdefs.kfdef.apps.kubeflow.org -A NAMESPACE NAME AGE redhat-ods-applications rhods-anaconda 3h6m redhat-ods-applications rhods-dashboard 3h6m redhat-ods-applications rhods-data-science-pipelines-operator 3h6m redhat-ods-applications rhods-model-mesh 3h6m redhat-ods-applications rhods-nbc 3h6m redhat-ods-applications rhods-osd-config 3h6m redhat-ods-monitoring modelmesh-monitoring 3h6m redhat-ods-monitoring monitoring 3h6m rhods-notebooks rhods-notebooks 3h6m rhods-notebooks rhods-osd-config 3h5m
Connecting to cache endpoint ds-pipeline-dspa.project-name.svc.cluster.local:8887 panic: runtime error: invalid memory address or nil pointer dereference
get ValidatingWebhookConfiguration,MutatingWebhookConfiguration | grep -i knative
get ValidatingWebhookConfiguration,MutatingWebhookConfiguration | grep -i knative
As of transformers v4.44, default chat template is no longer allowed, so you must provide a chat template if the tokenizer does not define one
containers: - args: - --chat-template=<CHAT_TEMPLATE>
ReconcileCompletedWithComponentErrors DataScienceCluster resource reconciled with component errors: 1 error occurred: * CustomResourceDefinition.apiextensions.k8s.io "appwrappers.workload.codeflare.dev" is invalid: status.storedVersions[0]: Invalid value: "v1beta1": must appear in spec.versions
oc delete crd appwrappers.workload.codeflare.dev
oc get crd appwrappers.workload.codeflare.dev NAME CREATED AT appwrappers.workload.codeflare.dev 2024-11-22T18:35:04Z
apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: allow-ingress-to-myapp spec: podSelector: matchLabels: app: myapp ingress: - {}
Failed to get endpoint for this deployed model. routes.rout.openshift.io"<model_name>" not found
oc patch OdhDashboardConfig odh-dashboard-config -n redhat-ods-applications --type=merge -p '{"spec": {"dashboardConfig": {"notebookController.enabled": true}}}'
runc create failed: unable to start container process: unable to init seccomp: error loading seccomp filter into kernel: error loading seccomp filter: errno 524
Error creating workbench Operation cannot be fulfilled on notebooks.kubeflow.org "workbench-name": the object has been modified; please apply your changes to the latest version and try again
Request invalid against a username that does not exist.
import os os.environ["TENSORBOARD_PROXY_URL"]= os.environ["NB_PREFIX"]+"/proxy/6006/"
16.2. PAM Configuration Files The directory /etc/pam.d/ contains the PAM configuration files for each PAM-aware application. In earlier versions of PAM, the file /etc/pam.conf was used, but this file is now deprecated and is only used if the /etc/pam.d/ directory does not exist. 16.2.1. PAM Service Files Each PAM-aware application or service has a file within the /etc/pam.d/ directory. Each file within this directory bears the name of the service for which it controls access. It is up to the PAM-aware program to define its service name and install its own PAM configuration file in the /etc/pam.d/ directory. For example, the login program defines its service name as login and installs the /etc/pam.d/login PAM configuration file.

Commands:
Chapter 10. Auditing listening endpoints Red Hat Advanced Cluster Security for Kubernetes (RHACS) provides the ability to audit the processes that are listening on ports in your secured clusters and filter this data by deployment, namespace, or cluster. You can view information about processes and ports that they are listening on by using the following methods: In the RHACS web portal, go to Network Listening Endpoints . Connect to the ListeningEndpointsService object in the API. For more information on the API, go to Help API reference in the RHACS web portal. The page provides a list of processes by deployment, with the following information displayed for each process on the list: Deployment name Cluster Namespace Count, or the number of processes listening on the ports in the deployment You can further filter the information displayed on the page by using the filter field and entering individual deployments, namespaces, and clusters. Click the expand icon at the top of the list to expand all sections for all deployments listed, or click the expand icon on a single deployment line to view additional information about that deployment. The following information is provided: Exec file path: Location of the process PID: System ID of the process Port: Port on which the process is listening Protocol: Protocol in use by the process Pod ID: Name of the pod where the process is contained Container name: Name of the container in which the process that is listening is located Clicking on a deployment name brings you to the Risk page in the RHACS web portal, where you can view information about the deployment, including risk indicators such as policy violations and additional deployment details.

Commands:
Chapter 64. KafkaExporterTemplate schema reference Used in: KafkaExporterSpec Property Property type Description deployment DeploymentTemplate Template for Kafka Exporter Deployment . pod PodTemplate Template for Kafka Exporter Pods . service ResourceTemplate The service property has been deprecated. The Kafka Exporter service has been removed. Template for Kafka Exporter Service . container ContainerTemplate Template for the Kafka Exporter container. serviceAccount ResourceTemplate Template for the Kafka Exporter service account.

Commands:
Appendix A. Revision History Revision History Revision 1.1.0- Tue Aug 06 2019 Eliane Pereira Revision 1.0.0- Thu Jul 11 2019 Eliane Pereira Composer has been splitted to its own guide and it is now available. Revision 0.0-0 Sun Jun 2 2019 Eliane Pereira Preparing document for 7.7 GA publication.

Commands:
2.10. What are Models? A model is a representation of a set of information constructs. A familiar model is the relational model, which defines tables composed of columns and containing records of data. Another familiar model is the XML model, which defines hierarchical data sets. In Teiid Designer , models are used to define the entities, and relationships between those entities, required to fully define the integration of information sets so that they may be accessed in a uniform manner, using a single API and access protocol. The file extension used for these models is .xmi (for example, NorthwindOracle.xmi ) which adheres to the XMI syntax defined by the OMG. Below is an example of the partial contents of a model file. Figure 2.1. Sample Model File Note Model files should never be modified by hand. While it is possible to do so, there is the possibility that you may corrupt the file such that it cannot be used within Teiid Designer system. The fundamental models in Teiid Designer define the structural and data characteristics of the information contained in data sources. These are referred to as source models. Teiid Designer uses the information in source models to federate the information in multiple sources, so that from a user's viewpoint these all appear to be in a single source. Figure 2.2. Model Internals In addition to source models, Teiid Designer provides the ability to define a variety of view models. These can be used to define a layer of abstraction above the physical (or source) layer, so that information can be presented to end users and consuming applications in business terms rather than as it is physically stored. Views are mapped to sources using transformations between models. These business views can be in a variety of forms: Relational Tables and Views XML Web services Functions A third model type, logical, provides the ability to define models from a logical or structural perspective.

Commands:
Preface In Red Hat OpenShift AI, when you create a workbench, you select a workbench image that includes an integrated development environment (IDE) for developing your machine learning (ML) models. OpenShift AI supports the following data science IDEs for developing ML models: JupyterLab code-server RStudio Server (Technology Preview feature) Note The RStudio workbench images are currently unavailable for disconnected environments. For information about RStudio Server, see the Release Notes .

Commands:
Chapter 11. Networking ethtool -P now returns correct output for virtual devices The permanent address of virtual devices such as bridge or veth was incorrectly set to their link layer address, instead of being all zeroes. This update restores the original behavior for devices that do not have a permanent address so that the ethtool -P command now returns an all-zero address once again. (BZ#1318500) Clients using IEEE802.1x-port-based authentication no longer lose connectivity Previously, the wpa_supplicant service stopped responding to Extensible Authentication Protocol (EAP) Identity Request packets after wpa_supplicant was reloaded. As a consequence, clients using IEEE802.1x-port-based authentication lost connectivity until wpa_supplicant was restarted. With this update, the client is deauthenticated after reconfiguration. As a result, clients using IEEE802.1x-port-based authentication no longer lose connectivity in the described situation. (BZ#1359044) UDP iperf over IPv6 ESP no longer causes kernel panic Previously, a transform (XFRM) lookup could be performed on an already transformed destination cache entry (dst_entry) using UDP over IPv6 with a connected socket in conjunction with IPsec in Encapsulating Security Payload (ESP) transport mode. As a consequence, invalid IPv6 fragments were transmitted from the host or the kernel could terminate unexpectedly due to a socket buffer (SKB) underrun. With this update, XFRM lookup on already transformed dst_entry is not possible. Using UDP iperf over IPv6 ESP no longer causes invalid IPv6 fragments transmissions or a kernel panic. (BZ#1327680) tty_ldisc_flush() no longer causes ISDN crashes When providing certain services and using the Integrated Services Digital Network (ISDN), the system could terminate unexpectedly due to the call of the tty_ldisc_flush() function. The provided patch removes this call and the system no longer hangs in the described scenario. (BZ#1328115)

Commands:
Appendix A. API response codes The Red Hat Satellite 6 API provides HTTP response status codes for API calls. The following codes are common for all resources in the Satellite API. Table A.1. API response codes Response Explanation 200 OK For a successful request action: show, index, update, or delete (GET, PUT, DELETE requests). 201 Created For a successful create action (POST request). 301 Moved Permanently Redirect when Satellite is restricted to use HTTPS and HTTP is attempted. 400 Bad Request A required parameter is missing or the search query has invalid syntax. 401 Unauthorized Failed to authorize the user, for example, due to incorrect credentials. 403 Forbidden The user has insufficient permissions to perform the action or read the resource, or the action is unsupported in general. 404 Not Found The record with the given ID does not exist. It can appear in show and delete actions when the requested record does not exist; or in create, update and delete actions when one of the associated records does not exist. 409 Conflict Could not delete the record due to existing dependencies, for example, host groups that still contain hosts. 415 Unsupported Media Type The content type of the HTTP request is not JSON. 422 Unprocessable Entity Failed to create an entity due to some validation errors. Applies to create or update actions only. 500 Internal Server Error Unexpected internal server error. 503 Service Unavailable The server is not running.

Commands:
2.6. Stopping and Restarting the Red Hat Gluster Storage Instance Important When you stop and restart a Red Hat Gluster Storage instance, Amazon Web Services assigns the instance a new IP address and hostname. This results in the instance losing its association with the virtual hardware, causing disruptions to the trusted storage pool. To prevent errors, add the restarted Red Hat Gluster Storage instance to the trusted storage pool. See section Adding Servers to the Trusted Storage Pool in the Red Hat Gluster Storage Administration Guide . Rebooting the Red Hat Gluster Storage instance preserves the IP address and hostname and does not lose its association with the virtual hardware. This does not cause any disruptions to the trusted storage pool.

Commands:
12.13. Cassandra Translator The Cassandra Translator, known by the type name cassandra, exposes querying functionality to Cassandra Data Sources. The translator translates Teiid push down commands into Cassandra CQL. The Cassandra Translator currently has no import or execution properties. The Cassandra Translator supports only SELECT statements with a restrictive set of capabilities including: count(*), comparison predicates, IN predicates, and LIMIT. Consider a custom extension or create an enhancement request should your usage require additional capabilities. The Teiid-specific Cassandra Resource Adapter should be used with this translator. Cassandra source procedures may be created using the teiid_rel:native-query extension. The procedure will invoke the native-query similar to a direct procedure call with the benefits that the query is predetermined and that result column types are known, rather than requiring the use of ARRAYTABLE or similar functionality. Warning The direct query procedure feature is turned off by default because of the security risk this exposes to execute any command against the source. To enable this feature, override the execution property called SupportsDirectQueryProcedure to true. By default the name of the procedure that executes the queries directly is called native. Override the execution property DirectQueryProcedureName to change it to another name. The Cassandra translator provides a procedure to execute any ad-hoc CQL query directly against the source without Teiid parsing or resolving. Since the metadata of this procedure's results are not known to Teiid, they are returned as an object array. ARRAYTABLE can be used construct tabular output for consumption by client applications.

Commands:
SELECT X.* FROM cassandra_source.native('SELECT firstname, lastname FROM users WHERE birth_year = USD1 AND country = USD2 ALLOW FILTERING', 1981, 'US') n, ARRAYTABLE(n.tuple COLUMNS firstname string, lastname string) AS X
function::text_strn Name function::text_strn - Escape any non-printable chars in a string. Synopsis Arguments input The string to escape. len Maximum length of string to return. 0 means MAXSTRINGLEN. quoted Put double quotes around the string. If input string is truncated it will have " ... " after the second quote. General Syntax text_strn:string (input:string, len:long, quoted:long) Description This function accepts a string of designated length, and any ASCII characters that are not printable are replaced by the corresponding escape sequence in the returned string.

Commands:
function text_strn:string(input:string,len:long,quoted:long)
8.4.6. Creating a Yum Repository To set up a Yum repository, follow these steps: Install the createrepo package. To do so, type the following at a shell prompt as root : Copy all packages that you want to have in your repository into one directory, such as /mnt/local_repo/ . Change to this directory and run the following command: This creates the necessary metadata for your Yum repository, as well as the sqlite database for speeding up yum operations. Important Compared to Red Hat Enterprise Linux 5, RPM packages for Red Hat Enterprise Linux 6 are compressed with the XZ lossless data compression format and can be signed with newer hash algorithms like SHA-256. Consequently, it is not recommended to use the createrepo command on Red Hat Enterprise Linux 5 to create the package metadata for Red Hat Enterprise Linux 6.

Commands:
install createrepo
createrepo --database /mnt/local_repo
Chapter 7. Downgrading Red Hat Quay Red Hat Quay only supports rolling back, or downgrading, to z-stream versions, for example, 3.12.3 3.12.2. Rolling back to y-stream versions (3.13 3.12) is not supported. This is because Red Hat Quay updates might contain database schema upgrades that are applied when upgrading to a new version of Red Hat Quay. Database schema upgrades are not considered backwards compatible. Important Downgrading to z-streams is neither recommended nor supported by either Operator based deployments or virtual machine based deployments. Downgrading should only be done in extreme circumstances. The decision to rollback your Red Hat Quay deployment must be made in conjunction with the Red Hat Quay support and development teams. For more information, contact Red Hat Quay support.

Commands:
Chapter 1. Getting started with Red Hat Quay configuration Red Hat Quay can be deployed by an independent, standalone configuration, or by using the Red Hat Quay Operator on OpenShift Container Platform. How you create, retrieve, update, and validate the Red Hat Quay configuration varies depending on the type of deployment you are using. However, the core configuration options are the same for either deployment type. Core configuration is primarily set through a config.yaml file, but can also be set by using the configuration API. For standalone deployments of Red Hat Quay, you must supply the minimum required configuration parameters before the registry can be started. The minimum requirements to start a Red Hat Quay registry can be found in the "Retrieving the current configuration" section. If you install Red Hat Quay on OpenShift Container Platform using the Red Hat Quay Operator, you do not need to supply configuration parameters because the Red Hat Quay Operator supplies default information to deploy the registry. After you have deployed Red Hat Quay with the desired configuration, you should retrieve, and save, the full configuration from your deployment. The full configuration contains additional generated values that you might need when restarting or upgrading your system.

Commands:
6.8. Modifying Resource Parameters To modify the parameters of a configured resource, use the following command. The following sequence of commands show the initial values of the configured parameters for resource VirtualIP , the command to change the value of the ip parameter, and the values following the update command.

Commands:
pcs resource update resource_id [ resource_options ]
pcs resource show VirtualIP Resource: VirtualIP (type=IPaddr2 class=ocf provider=heartbeat) Attributes: ip=192.168.0.120 cidr_netmask=24 Operations: monitor interval=30s pcs resource update VirtualIP ip=192.169.0.120 pcs resource show VirtualIP Resource: VirtualIP (type=IPaddr2 class=ocf provider=heartbeat) Attributes: ip=192.169.0.120 cidr_netmask=24 Operations: monitor interval=30s