Skip to content

Commit 3cfe17f

Browse files
committed
Deployed 56a517c with MkDocs version: 1.6.0
1 parent ea5b24c commit 3cfe17f

File tree

8 files changed

+83
-984
lines changed

8 files changed

+83
-984
lines changed

en/admin/virtnest/vm/clone.html

+26-29
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@
2626
<input autocomplete="off" class="md-toggle" data-md-toggle="search" id="__search" type="checkbox"/>
2727
<label class="md-overlay" for="__drawer"></label>
2828
<div data-md-component="skip">
29-
<a class="md-skip" href="#_1">
29+
<a class="md-skip" href="#cloning-a-cloud-host">
3030
Skip to content
3131
</a>
3232
</div>
@@ -330,16 +330,16 @@
330330
</label>
331331
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix="">
332332
<li class="md-nav__item">
333-
<a class="md-nav__link" href="#_2">
333+
<a class="md-nav__link" href="#prerequisites">
334334
<span class="md-ellipsis">
335-
前提条件
335+
Prerequisites
336336
</span>
337337
</a>
338338
</li>
339339
<li class="md-nav__item">
340-
<a class="md-nav__link" href="#_3">
340+
<a class="md-nav__link" href="#cloning-a-cloud-host_1">
341341
<span class="md-ellipsis">
342-
克隆云主机
342+
Cloning a Cloud Host
343343
</span>
344344
</a>
345345
</li>
@@ -524,16 +524,16 @@
524524
</label>
525525
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix="">
526526
<li class="md-nav__item">
527-
<a class="md-nav__link" href="#_2">
527+
<a class="md-nav__link" href="#prerequisites">
528528
<span class="md-ellipsis">
529-
前提条件
529+
Prerequisites
530530
</span>
531531
</a>
532532
</li>
533533
<li class="md-nav__item">
534-
<a class="md-nav__link" href="#_3">
534+
<a class="md-nav__link" href="#cloning-a-cloud-host_1">
535535
<span class="md-ellipsis">
536-
克隆云主机
536+
Cloning a Cloud Host
537537
</span>
538538
</a>
539539
</li>
@@ -544,38 +544,35 @@
544544
</div>
545545
<div class="md-content" data-md-component="content">
546546
<article class="md-content__inner md-typeset">
547-
<h1 id="_1">克隆云主机<a class="headerlink" href="#_1" title="Permanent link"></a></h1>
548-
<p>本文将介绍如何克隆一台新的云主机。</p>
549-
<p>用户可以克隆一台新的云主机,克隆后的云主机将具有与原始云主机相同的操作系统和系统配置,能够实现快速部署和扩展,快速创建相似配置的新云主机,而无需从头开始安装。</p>
550-
<h2 id="_2">前提条件<a class="headerlink" href="#_2" title="Permanent link"></a></h2>
551-
<p>使用克隆功能之前,需要满足以下前提条件(和快照功能的前提条件一致):</p>
547+
<h1 id="cloning-a-cloud-host">Cloning a Cloud Host<a class="headerlink" href="#cloning-a-cloud-host" title="Permanent link"></a></h1>
548+
<p>This article will introduce how to clone a new cloud host.</p>
549+
<p>Users can clone a new cloud host, which will have the same operating system and system configuration as the original cloud host. This enables quick deployment and scaling, allowing for the rapid creation of new cloud hosts with similar configurations without the need to install from scratch.</p>
550+
<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link"></a></h2>
551+
<p>Before using the cloning feature, the following prerequisites must be met (which are the same as those for the snapshot feature):</p>
552552
<ul>
553-
<li>只有非错误状态下的云主机才能使用克隆功能。</li>
554-
<li>安装 Snapshot CRDsSnapshot ControllerCSI Driver
555-
具体安装步骤可参考 <a href="https://github.com/kubernetes-csi/external-snapshotter?tab=readme-ov-file#usage">CSI Snapshotter</a></li>
556-
<li>等待 snapshot-controller 组件准备就绪, 该组件会监控 VolumeSnapshot VolumeSnapshotContent 相关事件,并触发相关操作。</li>
557-
<li>等待 CSI Driver 准备就绪, 确保 csi-snapshotter sidecar 跑在 CSI Driver 里,csi-snapshotter sidecar 会监控 VolumeSnapshotContent 相关事件,并触发相关操作。<ul>
558-
<li>如存储是 Rook-Ceph,可参考 <a href="https://rook.io/docs/rook/latest-release/Storage-Configuration/Ceph-CSI/ceph-csi-snapshot/">ceph-csi-snapshot</a></li>
559-
<li>如存储是 HwameiStor,可参考 <a href="https://hwameistor.io/cn/docs/volumes/volume_snapshot">huameistor-snapshot</a></li>
553+
<li>Only cloud hosts that are not in an error state can use the cloning feature.</li>
554+
<li>Install Snapshot CRDs, Snapshot Controller, and CSI Driver.
555+
For specific installation steps, refer to <a href="https://github.com/kubernetes-csi/external-snapshotter?tab=readme-ov-file#usage">CSI Snapshotter</a>.</li>
556+
<li>Wait for the snapshot-controller component to be ready. This component will monitor events related to VolumeSnapshot and VolumeSnapshotContent and trigger related operations.</li>
557+
<li>Wait for the CSI Driver to be ready, ensuring that the csi-snapshotter sidecar is running in the CSI Driver. The csi-snapshotter sidecar will monitor events related to VolumeSnapshotContent and trigger related operations.<ul>
558+
<li>If the storage is Rook-Ceph, refer to <a href="https://rook.io/docs/rook/latest-release/Storage-Configuration/Ceph-CSI/ceph-csi-snapshot/">ceph-csi-snapshot</a></li>
559+
<li>If the storage is HwameiStor, refer to <a href="https://hwameistor.io/cn/docs/volumes/volume_snapshot">huameistor-snapshot</a></li>
560560
</ul>
561561
</li>
562562
</ul>
563-
<h2 id="_3">克隆云主机<a class="headerlink" href="#_3" title="Permanent link"></a></h2>
563+
<h2 id="cloning-a-cloud-host_1">Cloning a Cloud Host<a class="headerlink" href="#cloning-a-cloud-host_1" title="Permanent link"></a></h2>
564564
<ol>
565565
<li>
566-
<p>点击左侧导航栏上的 <strong>容器管理</strong> ,然后点击 <strong>云主机</strong> ,进入列表页面,点击列表右侧的 <strong></strong> ,可以对非错误状态下的云主机执行快照操作。</p>
567-
<p><img alt="克隆云主机" src="../../../../admin/virtnest/images/clone01.png"/></p>
566+
<p>Click on <strong>Container Management</strong> in the left navigation bar, then click on <strong>Cloud Hosts</strong> to enter the list page. Click on the <strong></strong> on the right side of the list to perform snapshot operations on cloud hosts that are not in an error state.</p>
568567
</li>
569568
<li>
570-
<p>弹出弹框,需要填写克隆新的云主机的名称和描述,克隆操作可能需要一些时间,具体取决于云主机的大小和存储性能。</p>
571-
<p><img alt="克隆过程" src="../../../../admin/virtnest/images/clone02.png"/></p>
569+
<p>A popup will appear, requiring you to fill in the name and description for the new cloud host being cloned. The cloning operation may take some time, depending on the size of the cloud host and storage performance.</p>
572570
</li>
573571
<li>
574-
<p>克隆成功后可以在云主机列表内查看到新的云主机,新创建出来的云主机处于关机状态,若需要开机需要手动操作。</p>
575-
<p><img alt="新的云主机" src="../../../../admin/virtnest/images/clone03.png"/></p>
572+
<p>After a successful clone, you can view the new cloud host in the cloud host list. The newly created cloud host will be in a powered-off state and will need to be manually powered on if required.</p>
576573
</li>
577574
<li>
578-
<p>克隆前建议对原有云主机进行快照,如果克隆过程中遇到问题,请检查先决条件是否满足,并尝试重新执行克隆操作。</p>
575+
<p>It is recommended to take a snapshot of the original cloud host before cloning. If you encounter issues during the cloning process, please check whether the prerequisites are met and try to execute the cloning operation again.</p>
579576
</li>
580577
</ol>
581578
</article>

en/admin/virtnest/vm/health-check.html

+36-36
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@
2626
<input autocomplete="off" class="md-toggle" data-md-toggle="search" id="__search" type="checkbox"/>
2727
<label class="md-overlay" for="__drawer"></label>
2828
<div data-md-component="skip">
29-
<a class="md-skip" href="#_1">
29+
<a class="md-skip" href="#health-check">
3030
Skip to content
3131
</a>
3232
</div>
@@ -400,23 +400,23 @@
400400
</label>
401401
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix="">
402402
<li class="md-nav__item">
403-
<a class="md-nav__link" href="#http-liveness-probe">
403+
<a class="md-nav__link" href="#configuring-http-liveness-probe">
404404
<span class="md-ellipsis">
405-
配置 HTTP Liveness Probe
405+
Configuring HTTP Liveness Probe
406406
</span>
407407
</a>
408408
</li>
409409
<li class="md-nav__item">
410-
<a class="md-nav__link" href="#tcp-liveness-probe">
410+
<a class="md-nav__link" href="#configuring-tcp-liveness-probe">
411411
<span class="md-ellipsis">
412-
配置 TCP Liveness Probe
412+
Configuring TCP Liveness Probe
413413
</span>
414414
</a>
415415
</li>
416416
<li class="md-nav__item">
417-
<a class="md-nav__link" href="#readiness-probes">
417+
<a class="md-nav__link" href="#configuring-readiness-probes">
418418
<span class="md-ellipsis">
419-
配置 Readiness Probes
419+
Configuring Readiness Probes
420420
</span>
421421
</a>
422422
</li>
@@ -531,23 +531,23 @@
531531
</label>
532532
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix="">
533533
<li class="md-nav__item">
534-
<a class="md-nav__link" href="#http-liveness-probe">
534+
<a class="md-nav__link" href="#configuring-http-liveness-probe">
535535
<span class="md-ellipsis">
536-
配置 HTTP Liveness Probe
536+
Configuring HTTP Liveness Probe
537537
</span>
538538
</a>
539539
</li>
540540
<li class="md-nav__item">
541-
<a class="md-nav__link" href="#tcp-liveness-probe">
541+
<a class="md-nav__link" href="#configuring-tcp-liveness-probe">
542542
<span class="md-ellipsis">
543-
配置 TCP Liveness Probe
543+
Configuring TCP Liveness Probe
544544
</span>
545545
</a>
546546
</li>
547547
<li class="md-nav__item">
548-
<a class="md-nav__link" href="#readiness-probes">
548+
<a class="md-nav__link" href="#configuring-readiness-probes">
549549
<span class="md-ellipsis">
550-
配置 Readiness Probes
550+
Configuring Readiness Probes
551551
</span>
552552
</a>
553553
</li>
@@ -558,16 +558,16 @@
558558
</div>
559559
<div class="md-content" data-md-component="content">
560560
<article class="md-content__inner md-typeset">
561-
<h1 id="_1">健康检查<a class="headerlink" href="#_1" title="Permanent link"></a></h1>
562-
<p>当配置云主机的存活(Liveness)和就绪(Readiness)探针时,与 Kubernetes 的配置过程相似。本文将介绍如何通过 YAML 为云主机配置健康检查参数。</p>
563-
<p>但是需要注意:需要在云主机创建成功并且处于关机状态下,修改 YAML 进行配置。</p>
564-
<h2 id="http-liveness-probe">配置 HTTP Liveness Probe<a class="headerlink" href="#http-liveness-probe" title="Permanent link"></a></h2>
561+
<h1 id="health-check">Health Check<a class="headerlink" href="#health-check" title="Permanent link"></a></h1>
562+
<p>When configuring the liveness and readiness probes for a cloud host, the process is similar to that of Kubernetes configuration. This article will introduce how to configure health check parameters for a cloud host using YAML.</p>
563+
<p>However, it is important to note that the configuration must be done when the cloud host has been successfully created and is in a powered-off state.</p>
564+
<h2 id="configuring-http-liveness-probe">Configuring HTTP Liveness Probe<a class="headerlink" href="#configuring-http-liveness-probe" title="Permanent link"></a></h2>
565565
<ol>
566-
<li>spec.template.spec 中配置 livenessProbe.httpGet。</li>
566+
<li>Configure <code>livenessProbe.httpGet</code> in <code>spec.template.spec</code>.</li>
567567
<li>
568-
<p>修改 cloudInitNoCloud 以启动一个 HTTP 服务器。</p>
568+
<p>Modify <code>cloudInitNoCloud</code> to start an HTTP server.</p>
569569
<details class="note">
570-
<summary>点击查看 YAML 示例配置</summary>
570+
<summary>Click to view YAML example</summary>
571571
<div class="highlight"><pre><span></span><code><a href="#__codelineno-0-1" id="__codelineno-0-1" name="__codelineno-0-1"></a><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">kubevirt.io/v1</span>
572572
<a href="#__codelineno-0-2" id="__codelineno-0-2" name="__codelineno-0-2"></a><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">VirtualMachine</span>
573573
<a href="#__codelineno-0-3" id="__codelineno-0-3" name="__codelineno-0-3"></a><span class="nt">metadata</span><span class="p">:</span>
@@ -667,30 +667,30 @@ <h2 id="http-liveness-probe">配置 HTTP Liveness Probe<a class="headerlink" hre
667667
</details>
668668
</li>
669669
<li>
670-
<p>根据操作系统(如 Ubuntu/Debian CentOS),userData 的配置可能有所不同。主要区别:</p>
670+
<p>The configuration of <code>userData</code> may vary depending on the operating system (such as Ubuntu/Debian or CentOS). The main differences are:</p>
671671
<ul>
672672
<li>
673-
<p>包管理器:</p>
674-
<p>Ubuntu/Debian 使用 apt-get 作为包管理器。
675-
CentOS 使用 yum 作为包管理器。</p>
673+
<p>Package manager:</p>
674+
<p>Ubuntu/Debian uses <code>apt-get</code> as the package manager.
675+
CentOS uses <code>yum</code> as the package manager.</p>
676676
</li>
677677
<li>
678-
<p>SSH 服务重启命令: </p>
679-
<p>Ubuntu/Debian 使用 systemctl restart ssh.service
680-
CentOS 使用 systemctl restart sshd.service(注意 CentOS 7 及之前版本使用 service sshd restart)。</p>
678+
<p>SSH service restart command:</p>
679+
<p>Ubuntu/Debian uses <code>systemctl restart ssh.service</code>.
680+
CentOS uses <code>systemctl restart sshd.service</code> (note that for CentOS 7 and earlier versions, it uses <code>service sshd restart</code>).</p>
681681
</li>
682682
<li>
683-
<p>安装的软件包:</p>
684-
<p>Ubuntu/Debian 安装 ncat
685-
CentOS 安装 nmap-ncat(因为 ncat 在 CentOS 的默认仓库中可能不可用)。</p>
683+
<p>Installed packages:</p>
684+
<p>Ubuntu/Debian installs <code>ncat</code>.
685+
CentOS installs <code>nmap-ncat</code> (because <code>ncat</code> may not be available in the default repository for CentOS).</p>
686686
</li>
687687
</ul>
688688
</li>
689689
</ol>
690-
<h2 id="tcp-liveness-probe">配置 TCP Liveness Probe<a class="headerlink" href="#tcp-liveness-probe" title="Permanent link"></a></h2>
691-
<p>spec.template.spec 中配置 livenessProbe.tcpSocket。</p>
690+
<h2 id="configuring-tcp-liveness-probe">Configuring TCP Liveness Probe<a class="headerlink" href="#configuring-tcp-liveness-probe" title="Permanent link"></a></h2>
691+
<p>Configure <code>livenessProbe.tcpSocket</code> in <code>spec.template.spec</code>.</p>
692692
<details class="note">
693-
<summary>点击查看 YAML 示例配置</summary>
693+
<summary>Click to view YAML example configuration</summary>
694694
<div class="highlight"><pre><span></span><code><a href="#__codelineno-1-1" id="__codelineno-1-1" name="__codelineno-1-1"></a><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">kubevirt.io/v1</span>
695695
<a href="#__codelineno-1-2" id="__codelineno-1-2" name="__codelineno-1-2"></a><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">VirtualMachine</span>
696696
<a href="#__codelineno-1-3" id="__codelineno-1-3" name="__codelineno-1-3"></a><span class="nt">metadata</span><span class="p">:</span>
@@ -788,10 +788,10 @@ <h2 id="tcp-liveness-probe">配置 TCP Liveness Probe<a class="headerlink" href=
788788
<a href="#__codelineno-1-95" id="__codelineno-1-95" name="__codelineno-1-95"></a><span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">cloudinitdisk</span>
789789
</code></pre></div>
790790
</details>
791-
<h2 id="readiness-probes">配置 Readiness Probes<a class="headerlink" href="#readiness-probes" title="Permanent link"></a></h2>
792-
<p>spec.template.spec 中配置 readiness。</p>
791+
<h2 id="configuring-readiness-probes">Configuring Readiness Probes<a class="headerlink" href="#configuring-readiness-probes" title="Permanent link"></a></h2>
792+
<p>Configure <code>readiness</code> in <code>spec.template.spec</code>.</p>
793793
<details class="note">
794-
<summary>点击查看 YAML 示例配置</summary>
794+
<summary>Click to view YAML example configuration</summary>
795795
<div class="highlight"><pre><span></span><code><a href="#__codelineno-2-1" id="__codelineno-2-1" name="__codelineno-2-1"></a><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">kubevirt.io/v1</span>
796796
<a href="#__codelineno-2-2" id="__codelineno-2-2" name="__codelineno-2-2"></a><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">VirtualMachine</span>
797797
<a href="#__codelineno-2-3" id="__codelineno-2-3" name="__codelineno-2-3"></a><span class="nt">metadata</span><span class="p">:</span>

0 commit comments

Comments
 (0)