OpenShift Dedicated 4 入门OpenShift Dedicated 4 入门 OpenShift Dedicated 入门 Last Updated: 2024-02-23 OpenShift Dedicated 4 入门 OpenShift Dedicated 入门 法律通告 法律通告 Copyright © 2024 Red Hat, Inc. The text of and illustrations in community. All other trademarks are the property of their respective owners. 摘要 摘要 OpenShift Dedicated 集群入门。 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 第 第 1 章 章 了解您的云部署 了解您的云部署选项 选项 1.1. OPENSHIFT DEDICATED 云部署选项概述 1.2. 后续步骤 第 第 2 章 章 OPENSHIFT DEDICATED 入 入门 门 2.1. 先决条件 2.2. 创建 OPENSHIFT DEDICATED 集群 2.3. 配置身份提供程序 2.4. 为用户授予管理员权限 2.5. 访问集群 2.60 码力 | 15 页 | 199.19 KB | 1 年前3
OpenShift Dedicated 4 附加组件服务OpenShift Dedicated 4 附加组件服务 在 OpenShift Dedicated 集群中添加服务 Last Updated: 2024-02-15 OpenShift Dedicated 4 附加组件服务 在 OpenShift Dedicated 集群中添加服务 法律通告 法律通告 Copyright © 2024 Red Hat, Inc. The text property of their respective owners. 摘要 摘要 本文档提供有关使用 OpenShift Cluster Manager 控制台在 OpenShift Dedicated 集群中添加服务的 信息。 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MANAGER 删除附加组件服务 第 第 2 章 章 适用于 适用于 OPENSHIFT DEDICATED 的附加 的附加组 组件服 件服务 务 2.1. RED HAT OPENSHIFT API MANAGEMENT 3 3 3 4 5 5 目 目录 录 1 OpenShift Dedicated 4 附加 附加组 组件服 件服务 务 2 第 1 章 使用 RED HAT OPENSHIFT0 码力 | 9 页 | 100.47 KB | 1 年前3
Get off my thread: Techniques for moving k to background threadsthe current thread?Why do we need to move work off the current thread? Many environments have a dedicated thread for processing events: GUIs Client-Server applications Performing extensive processing to a dedicated background threadHow do we move work off the current thread? Possible ways to move the work off the current thread: Spawn a new thread for each event handler Pass data to a dedicated background move the work off the current thread: Spawn a new thread for each event handler Pass data to a dedicated background thread Submit tasks to a generic thread pool Submit tasks to a special purpose executorSpawning0 码力 | 90 页 | 6.97 MB | 6 月前3
OpenShift Container Platform 4.6 分布式追踪OpenShift Container Platform web 控制台。 您可以使用具有 cluster-admin 角色的用户访问集群。如果使用 Red Hat OpenShift Dedicated,则必须有一个具有 dedicated-admin 角色的帐户。 警告 警告 不要安装 Operators 的 Community 版本。不支持社区 Operator。 注意 注意 如果您已经安装了 OpenShift cluster-admin 角色的用户身份登录到 OpenShift Container Platform web 控制台。如果 使用 Red Hat OpenShift Dedicated,则必须有一个具有 dedicated-admin 角色的帐户。 2. 导航至 Operators → OperatorHub。 3. 在过滤器框中键入 Elasticsearch 以找到 OpenShift OpenShift Container Platform web 控制台。 您可以使用具有 cluster-admin 角色的用户访问集群。如果使用 Red Hat OpenShift Dedicated,则必须有一个具有 dedicated-admin 角色的帐户。 如果需要持久性存储,则必须在安装 Red Hat OpenShift distributed tracing Platform Operator0 码力 | 59 页 | 572.03 KB | 1 年前3
OpenShift Container Platform 4.8 Service Mesh网格中导入的。这些服务 还必须由 peer 的 ExportedServiceMeshSet 资源提供。 在 AWS(ROSA)、Azure Red Hat OpenShift(ARO)或 OpenShift Dedicated(OSD)上的 Red Hat OpenShift Service 上的集群间不支持 Service Mesh Federation。 1.2.2.12.3. OVN-Kubernetes Container Red Hat OpenShift Dedicated 和 和 Microsoft Azure Red Hat OpenShift OpenShift 上 上 的 的 Red Hat OpenShift Service Mesh Red Hat OpenShift Service Mesh 现在通过 Red Hat OpenShift Dedicated 和 Microsoft Azure Red admin 如何自定义它的更多信息,请参阅 OpenShift Container Platform 文档。如果使用 Red Hat OpenShift Dedicated,请参阅 Red Hat OpenShift Dedicated 的 dedicated-admin 角色。 1.5.1.16.2. 子域 支持子域(例如:"*.domain.com")。但是,OpenShift Container0 码力 | 344 页 | 3.04 MB | 1 年前3
OpenShift Container Platform 4.14 分布式追踪OpenShift Container Platform web 控制台。 您可以使用具有 cluster-admin 角色的用户访问集群。如果使用 Red Hat OpenShift Dedicated,则必须有一个具有 dedicated-admin 角色的帐户。 警告 警告 不要安装 Operators 的 Community 版本。不支持社区 Operator。 注意 注意 如果您已经安装了 OpenShift cluster-admin 角色的用户身份登录到 OpenShift Container Platform web 控制台。如果 使用 Red Hat OpenShift Dedicated,则必须有一个具有 dedicated-admin 角色的帐户。 2. 导航至 Operators → OperatorHub。 3. 在过滤器框中键入 Elasticsearch 以找到 OpenShift OpenShift Container Platform web 控制台。 您可以使用具有 cluster-admin 角色的用户访问集群。如果使用 Red Hat OpenShift Dedicated,则必须有一个具有 dedicated-admin 角色的帐户。 如果需要持久性存储,则必须在安装 Red Hat OpenShift distributed tracing Platform (Jaeger)0 码力 | 100 页 | 928.24 KB | 1 年前3
Apache Karaf Cellar 3.x Documentationof Cellar is to synchronize the state of several Karaf instances (named nodes). Cellar provides dedicated shell commands and MBeans to administrate the cluster, and manipulate the resources on the cluster "runtime clustering" by providing dedicated feature like: • HTTP load balancing • HTTP sessions replication • log centralization Please, see the sections dedicated to those features. 1.2. Cross topology cloud blobstore, allowing to use instances located on a cloud provider: Please, see the sections dedicated to these features for details. 4. Core runtime and Hazelcast Cellar uses Hazelcast as cluster0 码力 | 34 页 | 157.07 KB | 1 年前3
Apache Karaf Cellar 4.x - DocumentationCellar is to synchronize the status of several Karaf instances (named nodes). Cellar provides dedicated shell commands and JMX MBeans to manage the cluster, and manipulate the resources on the cluster provides "runtime clustering" by providing dedicated feature like: * HTTP load balancing * HTTP sessions replication * log centralization Please, see the sections dedicated to those features. 1.2. Cross topology cloud blobstore, allowing to use instances located on a cloud provider: Please, see the sections dedicated to these features for details. 4. Core runtime and Hazelcast Cellar uses Hazelcast as cluster0 码力 | 39 页 | 177.09 KB | 1 年前3
Apache OFBiz® Selenium-WebDriver
too long, to be able to run often and so detect new bugs rapidly. Data used for these tests are dedicated for them, load with ext-tests and it’s not necessary they area similar to real business data. is not build to be used by a scenario test, so, if part of code could be used by Scenario Test, dedicated method should be created for that. All methods, like simple action, call by scenario test, should similar to real business data and dedicated to the test, some base data, existing before (like demo data for example) could be checked or updated by a pre-scenario dedicated which is run just before running0 码力 | 38 页 | 1006.03 KB | 1 年前3
MITRE Defense Agile Acquisition Guide - Mar 2014depends on strong commitments at all levels of the acquisition process. First, Agile requires dedicated government involvement throughout the entire process in order to plan and integrate multiple releases demands a technically competent government team in addition to the development contactors. Close, dedicated acquisition teams facilitate this model, but it must be further reinforced at the top. Leadership invaluable linchpin to enable this relationship in a collaborative, flexible business environment. Dedicated onsite contracting support enables this close partnership with the program team. The program manager0 码力 | 74 页 | 3.57 MB | 5 月前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100













