|
|
|
@ -1,7 +1,7 @@
|
|
|
|
|
msgid ""
|
|
|
|
|
msgstr ""
|
|
|
|
|
"Project-Id-Version: PACKAGE VERSION\n"
|
|
|
|
|
"POT-Creation-Date: 2014-05-16 06:34+0000\n"
|
|
|
|
|
"POT-Creation-Date: 2014-05-29 06:09+0000\n"
|
|
|
|
|
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
|
|
|
|
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
|
|
|
|
"Language-Team: LANGUAGE <LL@li.org>\n"
|
|
|
|
@ -2266,7 +2266,7 @@ msgstr ""
|
|
|
|
|
msgid "vmware_disktype property"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:317(th) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:52(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:317(th) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:53(title)
|
|
|
|
|
msgid "VMDK disk type"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
@ -2278,7 +2278,7 @@ msgstr ""
|
|
|
|
|
msgid "Monolithic Sparse"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:328(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:73(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:75(td)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:328(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:74(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:76(td)
|
|
|
|
|
msgid "thin"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
@ -4306,327 +4306,327 @@ msgstr ""
|
|
|
|
|
msgid "VMware VMDK driver"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:7(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:8(para)
|
|
|
|
|
msgid "Use the VMware VMDK driver to enable management of the OpenStack Block Storage volumes on vCenter-managed data stores. Volumes are backed by VMDK files on data stores that use any VMware-compatible storage technology such as NFS, iSCSI, FiberChannel, and vSAN."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:13(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:14(para)
|
|
|
|
|
msgid "The VMware ESX VMDK driver is deprecated as of the Icehouse release and might be removed in Juno or a subsequent release. The VMware vCenter VMDK driver continues to be fully supported."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:19(title)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:20(title)
|
|
|
|
|
msgid "Functional context"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:20(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:21(para)
|
|
|
|
|
msgid "The VMware VMDK driver connects to vCenter, through which it can dynamically access all the data stores visible from the ESX hosts in the managed cluster."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:23(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:24(para)
|
|
|
|
|
msgid "When you create a volume, the VMDK driver creates a VMDK file on demand. The VMDK file creation completes only when the volume is subsequently attached to an instance, because the set of data stores visible to the instance determines where to place the volume."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:28(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:29(para)
|
|
|
|
|
msgid "The running vSphere VM is automatically reconfigured to attach the VMDK file as an extra disk. Once attached, you can log in to the running vSphere VM to rescan and discover this extra disk."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:34(title) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:134(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:66(title)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:35(title) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:134(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:66(title)
|
|
|
|
|
msgid "Configuration"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:35(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:36(para)
|
|
|
|
|
msgid "The recommended volume driver for OpenStack Block Storage is the VMware vCenter VMDK driver. When you configure the driver, you must match it with the appropriate OpenStack Compute driver from VMware and both drivers must point to the same server."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:40(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:41(para)
|
|
|
|
|
msgid "In the <filename>nova.conf</filename> file, use this option to define the Compute driver:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:43(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:44(para)
|
|
|
|
|
msgid "In the <filename>cinder.conf</filename> file, use this option to define the volume driver:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:46(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:47(para)
|
|
|
|
|
msgid "The following table lists various options that the drivers support for the OpenStack Block Storage configuration (<filename>cinder.conf</filename>):"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:53(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:54(para)
|
|
|
|
|
msgid "The VMware VMDK drivers support the creation of VMDK disk files of type <literal>thin</literal>, <literal>thick</literal>, or <literal>eagerZeroedThick</literal>. Use the <code>vmware:vmdk_type</code> extra spec key with the appropriate value to specify the VMDK disk file type. The following table captures the mapping between the extra spec entry and the VMDK disk file type:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:62(caption)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:63(caption)
|
|
|
|
|
msgid "Extra spec entry to VMDK disk file type mapping"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:66(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:67(td)
|
|
|
|
|
msgid "Disk file type"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:67(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:113(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:68(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:114(td)
|
|
|
|
|
msgid "Extra spec key"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:68(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:114(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:69(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:115(td)
|
|
|
|
|
msgid "Extra spec value"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:74(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:79(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:84(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:75(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:80(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:85(td)
|
|
|
|
|
msgid "vmware:vmdk_type"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:78(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:80(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:79(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:81(td)
|
|
|
|
|
msgid "thick"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:83(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:85(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:84(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:86(td)
|
|
|
|
|
msgid "eagerZeroedThick"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:89(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:90(para)
|
|
|
|
|
msgid "If you do not specify a <code>vmdk_type</code> extra spec entry, the default disk file type is <literal>thin</literal>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:92(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:93(para)
|
|
|
|
|
msgid "The following example shows how to create a <code>thick</code> VMDK volume by using the appropriate <code>vmdk_type</code>:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:100(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:112(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:101(title) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:113(td)
|
|
|
|
|
msgid "Clone type"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:101(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:102(para)
|
|
|
|
|
msgid "With the VMware VMDK drivers, you can create a volume from another source volume or a snapshot point. The VMware vCenter VMDK driver supports the <literal>full</literal> and <literal>linked/fast</literal> clone types. Use the <code>vmware:clone_type</code> extra spec key to specify the clone type. The following table captures the mapping for clone types:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:109(caption)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:110(caption)
|
|
|
|
|
msgid "Extra spec entry to clone type mapping"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:119(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:121(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:120(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:122(td)
|
|
|
|
|
msgid "full"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:120(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:125(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:121(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:126(td)
|
|
|
|
|
msgid "vmware:clone_type"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:124(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:125(td)
|
|
|
|
|
msgid "linked/fast"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:126(td)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:127(td)
|
|
|
|
|
msgid "linked"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:130(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:131(para)
|
|
|
|
|
msgid "If you do not specify the clone type, the default is <literal>full</literal>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:132(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:133(para)
|
|
|
|
|
msgid "The following example shows linked cloning from another source volume:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:138(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:139(para)
|
|
|
|
|
msgid "The VMware ESX VMDK driver ignores the extra spec entry and always creates a <literal>full</literal> clone."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:144(title)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:145(title)
|
|
|
|
|
msgid "Use vCenter storage policies to specify back-end data stores"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:147(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:148(para)
|
|
|
|
|
msgid "This section describes how to configure back-end data stores using storage policies. In vCenter, you can create one or more storage policies and expose them as a Block Storage volume-type to a vmdk volume. The storage policies are exposed to the vmdk driver through the extra spec property with the <literal>vmware:storage_profile</literal> key."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:154(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:155(para)
|
|
|
|
|
msgid "For example, assume a storage policy in vCenter named <literal>gold_policy.</literal> and a Block Storage volume type named <literal>vol1</literal> with the extra spec key <literal>vmware:storage_profile</literal> set to the value <literal>gold_policy</literal>. Any Block Storage volume creation that uses the <literal>vol1</literal> volume type places the volume only in data stores that match the <literal>gold_policy</literal> storage policy."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:163(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:164(para)
|
|
|
|
|
msgid "The Block Storage back-end configuration for vSphere data stores is automatically determined based on the vCenter configuration. If you configure a connection to connect to vCenter version 5.5 or later in the <filename>cinder.conf</filename> file, the use of storage policies to configure back-end data stores is automatically supported."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:171(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:172(para)
|
|
|
|
|
msgid "You must configure any data stores that you configure for the Block Storage service for the Compute service."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:176(title)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:177(title)
|
|
|
|
|
msgid "To configure back-end data stores by using storage policies"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:179(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:125(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:180(para)
|
|
|
|
|
msgid "In vCenter, tag the data stores to be used for the back end."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:181(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:182(para)
|
|
|
|
|
msgid "OpenStack also supports policies that are created by using vendor-specific capabilities; for example vSAN-specific storage policies."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:185(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:186(para)
|
|
|
|
|
msgid "The tag value serves as the policy. For details, see <xref linkend=\"vmware-spbm\"/>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:191(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:192(para)
|
|
|
|
|
msgid "Set the extra spec key <literal>vmware:storage_profile</literal> in the desired Block Storage volume types to the policy name that you created in the previous step."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:198(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:199(para)
|
|
|
|
|
msgid "Optionally, for the <parameter>vmware_host_version</parameter> parameter, enter the version number of your vSphere platform. For example, <placeholder-1/>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:203(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:204(para)
|
|
|
|
|
msgid "This setting overrides the default location for the corresponding WSDL file. Among other scenarios, you can use this setting to prevent WSDL error messages during the development phase or to work with a newer version of vCenter."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:210(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:117(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:162(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:211(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:117(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:180(para)
|
|
|
|
|
msgid "Complete the other vCenter configuration parameters as appropriate."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:215(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:216(para)
|
|
|
|
|
msgid "The following considerations apply to configuring SPBM for the Block Storage service:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:219(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:220(para)
|
|
|
|
|
msgid "Any volume that is created without an associated policy (that is to say, without an associated volume type that specifies <literal>vmware:storage_profile</literal> extra spec), there is no policy-based placement for that volume."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:230(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:24(title) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:11(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:34(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:42(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:325(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:33(title)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:231(title) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:24(title) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:11(title) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:34(title) ./doc/config-reference/block-storage/drivers/hp-3par-driver.xml:42(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:66(title) ./doc/config-reference/block-storage/drivers/hp-lefthand-driver.xml:325(title) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:33(title)
|
|
|
|
|
msgid "Supported operations"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:231(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:232(para)
|
|
|
|
|
msgid "The VMware vCenter and ESX VMDK drivers support these operations:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:235(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:28(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:15(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:46(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:72(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:91(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:38(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:36(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:236(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:28(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:15(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:46(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:72(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:91(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:38(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:36(para)
|
|
|
|
|
msgid "Create volume"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:238(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:239(para)
|
|
|
|
|
msgid "Create volume from another source volume. (Supported only if source volume is not attached to an instance.)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:243(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:58(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:33(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:109(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:68(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:54(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:244(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:58(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:33(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:109(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:68(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:54(para)
|
|
|
|
|
msgid "Create volume from snapshot"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:246(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:247(para)
|
|
|
|
|
msgid "Create volume from glance image"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:249(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:250(para)
|
|
|
|
|
msgid "Attach volume (When a volume is attached to an instance, a reconfigure operation is performed on the instance to add the volume's VMDK to it. The user must manually rescan and mount the device from within the guest operating system.)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:256(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:37(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:24(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:55(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:81(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:100(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:47(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:45(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:257(para) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:37(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:24(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:55(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:81(para) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:100(para) ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:47(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:45(para)
|
|
|
|
|
msgid "Detach volume"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:259(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:260(para)
|
|
|
|
|
msgid "Create snapshot (Allowed only if volume is not attached to an instance.)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:263(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:264(para)
|
|
|
|
|
msgid "Delete snapshot (Allowed only if volume is not attached to an instance.)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:267(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:268(para)
|
|
|
|
|
msgid "Upload as image to glance (Allowed only if volume is not attached to an instance.)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:272(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:273(para)
|
|
|
|
|
msgid "Although the VMware ESX VMDK driver supports these operations, it has not been extensively tested."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:278(title)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:279(title)
|
|
|
|
|
msgid "Storage policy-based configuration in vCenter"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:279(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:280(para)
|
|
|
|
|
msgid "You can configure Storage Policy-Based Management (SPBM) profiles for vCenter data stores supporting the Compute, Image Service, and Block Storage components of an OpenStack implementation."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:283(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:284(para)
|
|
|
|
|
msgid "In a vSphere OpenStack deployment, SPBM enables you to delegate several data stores for storage, which reduces the risk of running out of storage space. The policy logic selects the data store based on accessibility and available storage space."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:290(title) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:117(title)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:291(title) ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:117(title)
|
|
|
|
|
msgid "Prerequisites"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:293(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:294(para)
|
|
|
|
|
msgid "Determine the data stores to be used by the SPBM policy."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:297(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:298(para)
|
|
|
|
|
msgid "Determine the tag that identifies the data stores in the OpenStack component configuration."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:302(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:303(para)
|
|
|
|
|
msgid "Create separate policies or sets of data stores for separate OpenStack components."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:308(title)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:309(title)
|
|
|
|
|
msgid "Create storage policies in vCenter"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:310(title)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:311(title)
|
|
|
|
|
msgid "To create storage policies in vCenter"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:312(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:313(para)
|
|
|
|
|
msgid "In vCenter, create the tag that identifies the data stores:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:316(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:317(para)
|
|
|
|
|
msgid "From the Home screen, click <guimenuitem>Tags</guimenuitem>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:320(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:321(para)
|
|
|
|
|
msgid "Specify a name for the tag."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:323(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:324(para)
|
|
|
|
|
msgid "Specify a tag category. For example, <filename>spbm-cinder</filename>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:329(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:330(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:132(para)
|
|
|
|
|
msgid "Apply the tag to the data stores to be used by the SPBM policy."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:332(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:333(para) ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:142(para)
|
|
|
|
|
msgid "For details about creating tags in vSphere, see the <link href=\"http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.vcenterhost.doc/GUID-379F40D3-8CD6-449E-89CB-79C4E2683221.html\">vSphere documentation</link>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:339(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:340(para)
|
|
|
|
|
msgid "In vCenter, create a tag-based storage policy that uses one or more tags to identify a set of data stores."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:343(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:344(para)
|
|
|
|
|
msgid "You use this tag name and category when you configure the <filename>*.conf</filename> file for the OpenStack component. For details about creating tags in vSphere, see the <link href=\"http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.storage.doc/GUID-89091D59-D844-46B2-94C2-35A3961D23E7.html\">vSphere documentation</link>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:354(title)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:355(title)
|
|
|
|
|
msgid "Data store selection"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:355(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:356(para)
|
|
|
|
|
msgid "If storage policy is enabled, the driver initially selects all the data stores that match the associated storage policy."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:358(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:359(para)
|
|
|
|
|
msgid "If two or more data stores match the storage policy, the driver chooses a data store that is connected to the maximum number of hosts."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:361(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:362(para)
|
|
|
|
|
msgid "In case of ties, the driver chooses the data store with lowest space utilization, where space utilization is defined by the <literal>(1-freespace/totalspace)</literal> metric."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:366(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:367(para)
|
|
|
|
|
msgid "These actions reduce the number of volume migrations while attaching the volume to instances."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:368(para)
|
|
|
|
|
#: ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:369(para)
|
|
|
|
|
msgid "The volume must be migrated if the ESX host for the instance cannot access the data store that contains the volume."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
@ -9335,27 +9335,39 @@ msgstr ""
|
|
|
|
|
msgid "To configure multiple data stores using SPBM"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:128(para)
|
|
|
|
|
msgid "For details about creating tags in vSphere, see the <link href=\"http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.storage.doc/GUID-ECAF0ABF-20CC-47D3-A037-8B32F3389F9E.html\">vSphere documentation</link>."
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:125(para)
|
|
|
|
|
msgid "In vCenter, use tagging to identify the data stores and define a storage policy:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:135(para)
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:129(para)
|
|
|
|
|
msgid "Create the tag."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:136(para)
|
|
|
|
|
msgid "Create a tag-based storage policy that uses one or more tags to identify a set of data stores."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:146(para)
|
|
|
|
|
msgid "For details about storage policies in vSphere, see the <link href=\"http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.storage.doc/GUID-A8BA9141-31F1-4555-A554-4B5B04D75E54.html\">vSphere documentation</link>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:153(para)
|
|
|
|
|
msgid "Return to the <filename>glance-api.conf</filename> file."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:140(para)
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:158(para)
|
|
|
|
|
msgid "Comment or delete the <parameter>vmware_datastore_name</parameter> parameter."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:145(para)
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:163(para)
|
|
|
|
|
msgid "Uncomment and define the <parameter>vmware_pbm_policy</parameter> parameter by entering the same value as the tag you defined and applied to the data stores in vCenter."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:152(para)
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:170(para)
|
|
|
|
|
msgid "Uncomment and define the <parameter>vmware_pbm_wsdl_location</parameter> parameter by entering the location of the PBM service WSDL file. For example, <filename>file:///opt/SDK/spbm/wsdl/pbmService.wsdl</filename>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:158(para)
|
|
|
|
|
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:176(para)
|
|
|
|
|
msgid "If you do not set this parameter, the storage policy cannot be used to place images in the data store."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|