commit
dc7fd533f3
|
@ -668,9 +668,10 @@ OpenStack 的内部驱动程序已经被弃用。请使用 [OpenStack 的外部
|
||||||
diskformat: zeroedthick
|
diskformat: zeroedthick
|
||||||
```
|
```
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
`diskformat`: `thin`, `zeroedthick` and `eagerzeroedthick`. Default: `"thin"`.
|
`diskformat`: `thin`, `zeroedthick` and `eagerzeroedthick`. Default: `"thin"`.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
`diskformat`: `thin`, `zeroedthick` 和 `eagerzeroedthick`。默认值: `"thin"`。
|
`diskformat`: `thin`, `zeroedthick` 和 `eagerzeroedthick`。默认值: `"thin"`。
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
|
@ -689,14 +690,15 @@ OpenStack 的内部驱动程序已经被弃用。请使用 [OpenStack 的外部
|
||||||
datastore: VSANDatastore
|
datastore: VSANDatastore
|
||||||
```
|
```
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
`datastore`: The user can also specify the datastore in the StorageClass.
|
`datastore`: The user can also specify the datastore in the StorageClass.
|
||||||
The volume will be created on the datastore specified in the storage class,
|
The volume will be created on the datastore specified in the storage class,
|
||||||
which in this case is `VSANDatastore`. This field is optional. If the
|
which in this case is `VSANDatastore`. This field is optional. If the
|
||||||
datastore is not specified, then the volume will be created on the datastore
|
datastore is not specified, then the volume will be created on the datastore
|
||||||
specified in the vSphere config file used to initialize the vSphere Cloud
|
specified in the vSphere config file used to initialize the vSphere Cloud
|
||||||
Provider.
|
Provider.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
`datastore`:用户也可以在 StorageClass 中指定数据存储。
|
`datastore`:用户也可以在 StorageClass 中指定数据存储。
|
||||||
卷将在 storage class 中指定的数据存储上创建,在这种情况下是 `VSANDatastore`。
|
卷将在 storage class 中指定的数据存储上创建,在这种情况下是 `VSANDatastore`。
|
||||||
该字段是可选的。
|
该字段是可选的。
|
||||||
|
@ -708,7 +710,7 @@ OpenStack 的内部驱动程序已经被弃用。请使用 [OpenStack 的外部
|
||||||
-->
|
-->
|
||||||
3. Kubernetes 中的存储策略管理
|
3. Kubernetes 中的存储策略管理
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
* Using existing vCenter SPBM policy
|
* Using existing vCenter SPBM policy
|
||||||
|
|
||||||
One of the most important features of vSphere for Storage Management is
|
One of the most important features of vSphere for Storage Management is
|
||||||
|
@ -721,7 +723,8 @@ OpenStack 的内部驱动程序已经被弃用。请使用 [OpenStack 的外部
|
||||||
|
|
||||||
The SPBM policies can be specified in the StorageClass using the
|
The SPBM policies can be specified in the StorageClass using the
|
||||||
`storagePolicyName` parameter.
|
`storagePolicyName` parameter.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
* 使用现有的 vCenter SPBM 策略
|
* 使用现有的 vCenter SPBM 策略
|
||||||
|
|
||||||
vSphere 用于存储管理的最重要特性之一是基于策略的管理。
|
vSphere 用于存储管理的最重要特性之一是基于策略的管理。
|
||||||
|
@ -731,7 +734,7 @@ OpenStack 的内部驱动程序已经被弃用。请使用 [OpenStack 的外部
|
||||||
|
|
||||||
SPBM 策略可以在 StorageClass 中使用 `storagePolicyName` 参数声明。
|
SPBM 策略可以在 StorageClass 中使用 `storagePolicyName` 参数声明。
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
* Virtual SAN policy support inside Kubernetes
|
* Virtual SAN policy support inside Kubernetes
|
||||||
|
|
||||||
Vsphere Infrastructure (VI) Admins will have the ability to specify custom
|
Vsphere Infrastructure (VI) Admins will have the ability to specify custom
|
||||||
|
@ -746,7 +749,8 @@ OpenStack 的内部驱动程序已经被弃用。请使用 [OpenStack 的外部
|
||||||
You can see [Storage Policy Based Management for dynamic provisioning of volumes](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/policy-based-mgmt.html)
|
You can see [Storage Policy Based Management for dynamic provisioning of volumes](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/policy-based-mgmt.html)
|
||||||
for more details on how to use storage policies for persistent volumes
|
for more details on how to use storage policies for persistent volumes
|
||||||
management.
|
management.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
* Kubernetes 内的 Virtual SAN 策略支持
|
* Kubernetes 内的 Virtual SAN 策略支持
|
||||||
|
|
||||||
Vsphere Infrastructure(VI)管理员将能够在动态卷配置期间指定自定义 Virtual SAN
|
Vsphere Infrastructure(VI)管理员将能够在动态卷配置期间指定自定义 Virtual SAN
|
||||||
|
|
Loading…
Reference in New Issue