Deployed e3d6c32 with MkDocs version: 1.6.0

admin/kpanda/best-practice/add-worker-node-on-global.html

@@ -700,7 +700,7 @@ <h1 id="_1">为全局服务集群的工作节点扩容<a class="headerlink" href
 </div>
 <h2 id="_2">前提条件<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
 <ul>
-<li>已经通过<a href="../../install/commercial/deploy-arch.md">火种节点</a>完成 AI 算力中心平台的部署，并且火种节点上的 kind 集群运行正常。</li>
+<li>已经完成 AI 算力中心平台的部署，并且火种节点上的 kind 集群运行正常。</li>
 <li>必须使用平台 Admin 权限的用户登录。</li>
 </ul>
 <h2 id="kind-kubeconfig">获取火种节点上 kind 集群的 kubeconfig<a class="headerlink" href="#kind-kubeconfig" title="Permanent link">¶</a></h2>

admin/kpanda/best-practice/create-redhat9.2-on-centos-platform.html

@@ -693,7 +693,7 @@ <h1 id="centos-redhat-92">在 CentOS 管理平台上创建 RedHat 9.2 工作集
 创建集群时不支持异构（AMD 和 ARM 混合）部署，您可以在集群创建完成后，通过接入异构节点的方式进行集群混合部署管理。</p>
 </div>
 <h2 id="_1">前提条件<a class="headerlink" href="#_1" title="Permanent link">¶</a></h2>
-<p>已经部署好一个 AI 算力中心全模式，并且火种节点还存活，部署参考文档<a href="../../install/commercial/start-install.md">离线安装 AI 算力中心商业版</a></p>
+<p>已经部署好一个 AI 算力中心全模式，并且火种节点还存活。</p>
 <h2 id="redhat">下载并导入 RedHat 相关离线包<a class="headerlink" href="#redhat" title="Permanent link">¶</a></h2>
 <p>请确保已经登录到火种节点！并且之前部署 AI 算力中心时使用的 <code>clusterConfig.yaml</code> 文件还在。</p>
 <h3 id="redhat_1">下载 RedHat 相关离线包<a class="headerlink" href="#redhat_1" title="Permanent link">¶</a></h3>

admin/kpanda/best-practice/create-ubuntu-on-centos-platform.html

@@ -680,7 +680,7 @@ <h1 id="centos-ubuntu">在 CentOS 管理平台上创建 Ubuntu 工作集群<a cl
 </div>
 <h2 id="_1">前提条件<a class="headerlink" href="#_1" title="Permanent link">¶</a></h2>
 <ul>
-<li>已经部署好一个 AI 算力中心全模式，并且火种节点还存活，部署参考文档<a href="../../install/commercial/start-install.md">离线安装 AI 算力中心商业版</a></li>
+<li>已经部署好一个 AI 算力中心全模式，并且火种节点还存活。</li>
 </ul>
 <h2 id="ubuntu">下载并导入 Ubuntu 相关离线包<a class="headerlink" href="#ubuntu" title="Permanent link">¶</a></h2>
 <p>请确保已经登录到火种节点！并且之前部署 AI 算力中心时使用的 clusterConfig.yaml 文件还在。</p>

admin/kpanda/best-practice/multi-arch.html

@@ -723,7 +723,7 @@ <h1 id="_1">为工作集群添加异构节点<a class="headerlink" href="#_1" ti
 </div>
 <h2 id="_2">前提条件<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
 <ul>
-<li>已经部署好一个 AI 算力中心全模式，并且火种节点还存活，部署参考文档<a href="../../install/commercial/start-install.md">离线安装 AI 算力中心商业版</a></li>
+<li>已经部署好一个 AI 算力中心全模式，并且火种节点还存活</li>
 <li>已经通过 AI 算力中心平台创建好一个 AMD 架构，操作系统为 CentOS 7.9 的工作集群，创建参考文档<a href="../clusters/create-cluster.html">创建工作集群</a></li>
 </ul>
 <h2 id="_3">操作步骤<a class="headerlink" href="#_3" title="Permanent link">¶</a></h2>

admin/kpanda/best-practice/use-otherlinux-create-custer.html

@@ -650,14 +650,13 @@
 <div class="md-content" data-md-component="content">
 <article class="md-content__inner md-typeset">
 <h1 id="_1">在非主流操作系统上创建集群<a class="headerlink" href="#_1" title="Permanent link">¶</a></h1>
-<p>本文介绍离线模式下如何在 <strong>未声明支持的 OS</strong> 上创建工作集群。AI 算力中心声明支持的 OS 范围请参考
-<a href="../../install/commercial/deploy-requirements.md">AI 算力中心支持的操作系统</a></p>
+<p>本文介绍离线模式下如何在 <strong>未声明支持的 OS</strong> 上创建工作集群。</p>
 <p>离线模式下在未声明支持的 OS 上创建工作集群，主要的流程如下图：</p>
 <p><img alt="流程" src="https://docs.daocloud.io/daocloud-docs-images/docs/zh/docs/kpanda/images/otherlinux.png"/></p>
 <p>接下来，本文将以 openAnolis 操作系统为例，介绍如何在非主流操作系统上创建集群。</p>
 <h2 id="_2">前提条件<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
 <ul>
-<li>已经部署好一个 AI 算力中心全模式，部署参考文档<a href="../../install/commercial/start-install.md">离线安装 AI 算力中心商业版</a></li>
+<li>已经部署好一个 AI 算力中心全模式</li>
 <li>至少拥有一台可以联网的同架构同版本的节点。</li>
 </ul>
 <h2 id="_3">在线节点构建离线包<a class="headerlink" href="#_3" title="Permanent link">¶</a></h2>

admin/kpanda/clusters/create-cluster.html

@@ -631,7 +631,7 @@ <h1 id="_1">创建工作集群<a class="headerlink" href="#_1" title="Permanent
 其中，接入集群只能从第三方厂商接入，参见<a href="integrate-cluster.html">接入集群</a>。</p>
 <p>本页介绍如何创建工作集群，默认情况下，新建工作集群的工作节点 OS 类型和 CPU 架构需要与全局服务集群保持一致。
 如需使用区别于全局服务集群 OS 或架构的节点创建集群，参阅<a href="../../best-practice/create-ubuntu-on-centos-platform.md">在 centos 管理平台上创建 ubuntu 工作集群</a>进行创建。</p>
-<p>推荐使用 <a href="../../../install/commercial/deploy-requirements.md">算丰 AI 算力平台支持的操作系统</a>来创建集群。
+<p>推荐使用 算丰 AI 算力平台支持的操作系统。
 如您本地节点不在上述支持范围，可参考<a href="../../best-practice/use-otherlinux-create-custer.md">在非主流操作系统上创建集群</a>进行创建。</p>
 <h2 id="_2">前提条件<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
 <p>创建集群之前需要满足一定的前提条件：</p>

en/admin/ghippo/access-control/role.html

@@ -638,7 +638,7 @@
 <h1 id="role-and-permission-management">Role and Permission Management<a class="headerlink" href="#role-and-permission-management" title="Permanent link">¶</a></h1>
 <p>A role corresponds to a set of permissions that determine the actions that can be
 performed on resources. Granting a user a role means granting all the permissions included in that role.</p>
-<p>AI platform platform provides three levels of roles, which effectively solve your permission-related issues:</p>
+<p>AI platform provides three levels of roles, which effectively solve your permission-related issues:</p>
 <ul>
 <li><a href="#platform-roles">Platform Roles</a></li>
 <li><a href="#workspace-roles">Workspace Roles</a></li>

en/admin/ghippo/audit/open-audit.html

@@ -391,9 +391,9 @@
 <nav aria-label="Management Cluster Collection of Kubernetes Audit Logs Switch" class="md-nav">
 <ul class="md-nav__list">
 <li class="md-nav__item">
-<a class="md-nav__link" href="#ai-platform-enterprise-installation-environment">
+<a class="md-nav__link" href="#ai-platform-installation-environment">
 <span class="md-ellipsis">
-      AI platform Enterprise Installation Environment
+      AI platform Installation Environment
     </span>
 </a>
 </li>
@@ -554,9 +554,9 @@
 <nav aria-label="Management Cluster Collection of Kubernetes Audit Logs Switch" class="md-nav">
 <ul class="md-nav__list">
 <li class="md-nav__item">
-<a class="md-nav__link" href="#ai-platform-enterprise-installation-environment">
+<a class="md-nav__link" href="#ai-platform-installation-environment">
 <span class="md-ellipsis">
-      AI platform Enterprise Installation Environment
+      AI platform Installation Environment
     </span>
 </a>
 </li>
@@ -614,7 +614,7 @@ <h2 id="ai-platform-installation-status">AI platform Installation Status<a class
 <ul>
 <li>For AI Community installations, the Kubernetes audit log switch was not operated during the management cluster
   installation process.</li>
-<li>For AI platform Enterprise installations, the Kubernetes audit log switch is enabled by default.<ul>
+<li>For AI platform installations, the Kubernetes audit log switch is enabled by default.<ul>
 <li>To set it to default off, you can modify the installer's <strong>clusterConfig.yaml</strong> file 
   (set <strong>logPath</strong> to empty "").</li>
 </ul>
@@ -625,7 +625,7 @@ <h2 id="ai-platform-installation-status">AI platform Installation Status<a class
 </li>
 </ul>
 <h2 id="management-cluster-collection-of-kubernetes-audit-logs-switch">Management Cluster Collection of Kubernetes Audit Logs Switch<a class="headerlink" href="#management-cluster-collection-of-kubernetes-audit-logs-switch" title="Permanent link">¶</a></h2>
-<h3 id="ai-platform-enterprise-installation-environment">AI platform Enterprise Installation Environment<a class="headerlink" href="#ai-platform-enterprise-installation-environment" title="Permanent link">¶</a></h3>
+<h3 id="ai-platform-installation-environment">AI platform Installation Environment<a class="headerlink" href="#ai-platform-installation-environment" title="Permanent link">¶</a></h3>
 <h4 id="confirm-enabling-kubernetes-audit-logs">Confirm Enabling Kubernetes Audit Logs<a class="headerlink" href="#confirm-enabling-kubernetes-audit-logs" title="Permanent link">¶</a></h4>
 <p>Run the following command to check if audit logs are generated under the <strong>/var/log/kubernetes/audit</strong> directory. 
 If they exist, it means that Kubernetes audit logs are successfully enabled.</p>

en/admin/ghippo/best-practice/oem/oem-in.html

@@ -809,8 +809,8 @@ <h2 id="unify-domain-name-and-port">Unify Domain Name and Port<a class="headerli
 </li>
 </ol>
 <h2 id="integrate-user-systems">Integrate User Systems<a class="headerlink" href="#integrate-user-systems" title="Permanent link">¶</a></h2>
-<p>Integrate the customer system with the AI platform platform through protocols like OIDC/OAUTH,
-allowing users to enter the customer system without logging in again after logging into the AI platform platform.</p>
+<p>Integrate the customer system with the AI platform through protocols like OIDC/OAUTH,
+allowing users to enter the customer system without logging in again after logging into the AI platform.</p>
 <ol>
 <li>
 <p>In the scenario of two AI platform, you can create SSO access through <strong>Global Management</strong> -&gt; <strong>Access Control</strong> -&gt; <strong>Docking Portal</strong>.</p>
@@ -825,7 +825,7 @@ <h2 id="integrate-user-systems">Integrate User Systems<a class="headerlink" href
 </li>
 <li>
 <p>After integration, the customer system login page will display the OIDC (Custom) option.
-   Select to log in via OIDC the first time entering the customer system from the AI platform platform,
+   Select to log in via OIDC the first time entering the customer system from the AI platform,
    and subsequently, you will directly enter the customer system without selecting again.</p>
 <!-- add image later -->
 </li>

en/admin/ghippo/personal-center/ssh-key.html

@@ -435,9 +435,9 @@
 </a>
 </li>
 <li class="md-nav__item">
-<a class="md-nav__link" href="#step-4-set-the-public-key-on-ai-platform-platform">
+<a class="md-nav__link" href="#step-4-set-the-public-key-on-ai-platform">
 <span class="md-ellipsis">
-      Step 4. Set the Public Key on AI platform Platform
+      Step 4. Set the Public Key on AI platform
     </span>
 </a>
 </li>
@@ -523,9 +523,9 @@
 </a>
 </li>
 <li class="md-nav__item">
-<a class="md-nav__link" href="#step-4-set-the-public-key-on-ai-platform-platform">
+<a class="md-nav__link" href="#step-4-set-the-public-key-on-ai-platform">
 <span class="md-ellipsis">
-      Step 4. Set the Public Key on AI platform Platform
+      Step 4. Set the Public Key on AI platform
     </span>
 </a>
 </li>
@@ -619,7 +619,7 @@ <h2 id="step-3-copy-the-public-key">Step 3. Copy the Public Key<a class="headerl
 </code></pre></div>
 </li>
 </ul>
-<h2 id="step-4-set-the-public-key-on-ai-platform-platform">Step 4. Set the Public Key on AI platform Platform<a class="headerlink" href="#step-4-set-the-public-key-on-ai-platform-platform" title="Permanent link">¶</a></h2>
+<h2 id="step-4-set-the-public-key-on-ai-platform">Step 4. Set the Public Key on AI platform<a class="headerlink" href="#step-4-set-the-public-key-on-ai-platform" title="Permanent link">¶</a></h2>
 <ol>
 <li>
 <p>Log in to the AI platform UI page and select <strong>Profile</strong> -&gt; <strong>SSH Public Key</strong> in the upper right corner of the page.</p>

en/admin/insight/best-practice/debug-log.html

@@ -549,7 +549,7 @@ <h1 id="log-collection-troubleshooting-guide">Log Collection Troubleshooting Gui
 <p>After installing the <strong>insight-agent</strong> in the cluster, <strong>Fluent Bit</strong> in <strong>insight-agent</strong> will collect logs in the cluster by default, including Kubernetes event logs, node logs, and container logs. <strong>Fluent Bit</strong> has already configured various log collection plugins, related filter plugins, and log output plugins. The working status of these plugins determines whether log collection is normal. Below is a dashboard for <strong>Fluent Bit</strong> that monitors the working conditions of each <strong>Fluent Bit</strong> in the cluster and the collection, processing, and export of plugin logs.</p>
 <ol>
 <li>
-<p>Use AI platform platform, enter <strong>Insight</strong> , and select the <strong>Dashboard</strong> in the left navigation bar.</p>
+<p>Use AI platform, enter <strong>Insight</strong> , and select the <strong>Dashboard</strong> in the left navigation bar.</p>
 <p><img alt="nav" src="images/insight01.png"/></p>
 </li>
 <li>

en/admin/insight/best-practice/debug-trace.html

@@ -564,7 +564,7 @@ <h1 id="trace-collection-troubleshooting-guide">Trace Collection Troubleshooting
 If you find that there is no trace data after completing the application trace enhancement, please perform the following steps:</p>
 <ol>
 <li>
-<p>Use AI platform platform, enter <strong>Insight</strong> , and select the <strong>Dashboard</strong> in the left navigation bar.</p>
+<p>Use AI platform, enter <strong>Insight</strong> , and select the <strong>Dashboard</strong> in the left navigation bar.</p>
 <p><img alt="nav" src="https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/insight/images/insight01.png"/></p>
 </li>
 <li>

en/admin/insight/dashboard/import-dashboard.html

@@ -536,7 +536,7 @@ <h1 id="import-custom-dashboards">Import Custom Dashboards<a class="headerlink"
 <h2 id="steps">Steps<a class="headerlink" href="#steps" title="Permanent link">¶</a></h2>
 <ol>
 <li>
-<p>Log in to the AI platform platform and go to <strong>Container Management</strong> . Select the <strong>kpanda-global-cluster</strong> from the cluster list.</p>
+<p>Log in to the AI platform and go to <strong>Container Management</strong> . Select the <strong>kpanda-global-cluster</strong> from the cluster list.</p>
 </li>
 <li>
 <p>Choose <strong>Custom Resources</strong> from the left navigation bar. Look for the <strong>grafanadashboards.integreatly.org</strong> 

en/admin/insight/quickstart/install/index.html

@@ -253,7 +253,7 @@
 <div class="md-content" data-md-component="content">
 <article class="md-content__inner md-typeset">
 <h1 id="start-observing">Start Observing<a class="headerlink" href="#start-observing" title="Permanent link">¶</a></h1>
-<p>AI platform platform enables the management and creation of multicloud and multiple clusters.
+<p>AI platform enables the management and creation of multicloud and multiple clusters.
 Building upon this capability, Insight serves as a unified observability solution for
 multiple clusters. It collects observability data from multiple clusters by deploying the insight-agent
 plugin and allows querying of metrics, logs, and trace data through the AI platform Insight.</p>
@@ -274,7 +274,7 @@ <h1 id="start-observing">Start Observing<a class="headerlink" href="#start-obser
    <a href="../res-plan/prometheus-res.html">Prometheus resource planning</a>.</p>
 </li>
 <li>
-<p>As the metric data from multiple clusters is stored centrally, AI platform platform administrators
+<p>As the metric data from multiple clusters is stored centrally, AI platform administrators
    need to adjust the disk space of <strong>vmstorage</strong> based on the cluster size.
    Please refer to <a href="../res-plan/vms-res-plan.html">vmstorage disk capacity planning</a>.</p>
 </li>

en/admin/insight/quickstart/res-plan/modify-vms-disk.html

@@ -612,7 +612,7 @@ <h2 id="procedure">Procedure<a class="headerlink" href="#procedure" title="Perma
 <h3 id="enable-storageclass-expansion">Enable StorageClass expansion<a class="headerlink" href="#enable-storageclass-expansion" title="Permanent link">¶</a></h3>
 <ol>
 <li>
-<p>Log in to the AI platform platform as a global service cluster administrator. Click <strong>Container Management</strong> -&gt; <strong>Clusters</strong> and go to the details of the <strong>kpanda-global-cluster</strong> cluster.</p>
+<p>Log in to the AI platform as a global service cluster administrator. Click <strong>Container Management</strong> -&gt; <strong>Clusters</strong> and go to the details of the <strong>kpanda-global-cluster</strong> cluster.</p>
 </li>
 <li>
 <p>Select the left navigation menu <strong>Container Storage</strong> -&gt; <strong>PVCs</strong> and find the PVC bound to the vmstorage.</p>
@@ -634,7 +634,7 @@ <h3 id="enable-storageclass-expansion">Enable StorageClass expansion<a class="he
 <h3 id="modify-the-disk-capacity-of-vmstorage">Modify the disk capacity of vmstorage<a class="headerlink" href="#modify-the-disk-capacity-of-vmstorage" title="Permanent link">¶</a></h3>
 <ol>
 <li>
-<p>Log in to the AI platform platform as a global service cluster administrator and go to the details of the <strong>kpanda-global-cluster</strong> cluster.</p>
+<p>Log in to the AI platform as a global service cluster administrator and go to the details of the <strong>kpanda-global-cluster</strong> cluster.</p>
 </li>
 <li>
 <p>Select the left navigation menu <strong>CRDs</strong> and find the custom resource for <strong>vmcluster</strong> .</p>
@@ -665,7 +665,7 @@ <h3 id="clone-the-storage-volume">Clone the storage volume<a class="headerlink"
 <p>If the storage volume expansion fails, you can refer to the following method to clone the storage volume.</p>
 <ol>
 <li>
-<p>Log in to the AI platform platform as a global service cluster administrator and go to the details of the <strong>kpanda-global-cluster</strong> cluster.</p>
+<p>Log in to the AI platform as a global service cluster administrator and go to the details of the <strong>kpanda-global-cluster</strong> cluster.</p>
 </li>
 <li>
 <p>Select the left navigation menu <strong>Workloads</strong> -&gt; <strong>StatefulSets</strong> and find the statefulset for <strong>vmstorage</strong> . Click the <strong>┇</strong> on the right side of the target and select <strong>Status</strong> -&gt; <strong>Stop</strong> -&gt; <strong>OK</strong> in the popup menu.</p>
@@ -677,7 +677,7 @@ <h3 id="clone-the-storage-volume">Clone the storage volume<a class="headerlink"
 </code></pre></div>
 </li>
 <li>
-<p>Log in to the AI platform platform and go to the details of the <strong>kpanda-global-cluster</strong> cluster. Select the left navigation menu <strong>Container Storage</strong> -&gt; <strong>PVs</strong> , click <strong>Clone</strong> in the upper right corner, and modify the capacity of the volume.</p>
+<p>Log in to the AI platform and go to the details of the <strong>kpanda-global-cluster</strong> cluster. Select the left navigation menu <strong>Container Storage</strong> -&gt; <strong>PVs</strong> , click <strong>Clone</strong> in the upper right corner, and modify the capacity of the volume.</p>
 <p><img alt="Clone" src="https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/insight/quickstart/images/vmdisk12.png"/></p>
 <p><img alt="Edit Storage" src="https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/insight/quickstart/images/vmdisk13.png"/></p>
 </li>

en/admin/insight/quickstart/res-plan/vms-res-plan.html

@@ -783,7 +783,7 @@ <h3 id="when-the-service-mesh-is-enabled">When the service mesh is enabled<a cla
 </tbody>
 </table>
 <h3 id="example">Example<a class="headerlink" href="#example" title="Permanent link">¶</a></h3>
-<p>There are two clusters in the AI platform platform, of which 500 Pods are running in the global management cluster
+<p>There are two clusters in the AI platform, of which 500 Pods are running in the global management cluster
 (service mesh is turned on), and 1000 Pods are running in the worker cluster (service mesh is not turned on), and the expected metrics are stored for 30 days.</p>
 <ul>
 <li>The number of metrics in the global management cluster is 800x500 + 768x500 = 784000</li>