|
|
|
|
@@ -1,7 +1,7 @@
|
|
|
|
|
msgid ""
|
|
|
|
|
msgstr ""
|
|
|
|
|
"Project-Id-Version: PACKAGE VERSION\n"
|
|
|
|
|
"POT-Creation-Date: 2014-03-19 06:05+0000\n"
|
|
|
|
|
"POT-Creation-Date: 2014-03-20 06:23+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"
|
|
|
|
|
@@ -2226,343 +2226,347 @@ msgstr ""
|
|
|
|
|
msgid "Injection of SSH keys into compute instances hosted by vCenter is not currently supported."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:182(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:180(para)
|
|
|
|
|
msgid "To use multiple vCenter installations with OpenStack, each vCenter must be assigned to a separate availability zone. This is required as the OpenStack Block Storage VMDK driver does not currently work across multiple vCenter installations."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:190(title)
|
|
|
|
|
msgid "VMware vCenter driver"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:183(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:191(para)
|
|
|
|
|
msgid "Use the VMware vCenter driver (VMwareVCDriver) to connect OpenStack Compute with vCenter. This recommended configuration enables access through vCenter to advanced vSphere features like vMotion, High Availability, and Dynamic Resource Scheduling (DRS)."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:189(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:197(title)
|
|
|
|
|
msgid "VMwareVCDriver configuration options"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:190(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:198(para)
|
|
|
|
|
msgid "When you use the VMwareVCDriver (vCenter versions 5.1 and later) with OpenStack Compute, add the following VMware-specific configuration options to the <filename>nova.conf</filename> file:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:206(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:214(para)
|
|
|
|
|
msgid "vSphere vCenter versions 5.0 and earlier: You must specify the location of the WSDL files by adding the <code>wsdl_location=http://127.0.0.1:8080/vmware/SDK/wsdl/vim25/vimService.wsdl</code> setting to the above configuration. For more information, see <link linkend=\"VMWare_additional_config\">vSphere 5.0 and earlier additional set up</link>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:215(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:223(para)
|
|
|
|
|
msgid "Clusters: The vCenter driver can support multiple clusters. To use more than one cluster, simply add multiple <option>cluster_name</option> lines in <filename>nova.conf</filename> with the appropriate cluster name. Clusters and data stores used by the vCenter driver should not contain any VMs other than those created by the driver."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:224(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:232(para)
|
|
|
|
|
msgid "Data stores: The <option>datastore_regex</option> setting specifies the data stores to use with Compute. For example, <option>datastore_regex=\"nas.*\"</option> selects all the data stores that have a name starting with \"nas\". If this line is omitted, Compute uses the first data store returned by the vSphere API. It is recommended not to use this field and instead remove data stores that are not intended for OpenStack."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:234(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:242(para)
|
|
|
|
|
msgid "Reserved host memory: The <option>reserved_host_memory_mb</option> setting is set to 512 MB by default. However, VMware recommends setting this value to 0 MB because the vCenter driver reports the effective memory available to the virtual machines."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:242(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:250(para)
|
|
|
|
|
msgid "A <systemitem class=\"service\">nova-compute</systemitem> service can control one or more clusters containing multiple ESX hosts, making <systemitem class=\"service\">nova-compute</systemitem> a critical service from a high availability perspective. Because the host that runs <systemitem class=\"service\">nova-compute</systemitem> can fail while the vCenter and ESX still run, you must protect the <systemitem class=\"service\">nova-compute</systemitem> service against host failures."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:252(para) ./doc/config-reference/compute/section_hypervisor_vmware.xml:666(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:260(para) ./doc/config-reference/compute/section_hypervisor_vmware.xml:674(para)
|
|
|
|
|
msgid "Many <filename>nova.conf</filename> options are relevant to libvirt but do not apply to this driver."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:255(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:263(para)
|
|
|
|
|
msgid "You must complete additional configuration for environments that use vSphere 5.0 and earlier. See <xref linkend=\"VMWare_additional_config\"/>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:261(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:269(title)
|
|
|
|
|
msgid "Images with VMware vSphere"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:262(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:270(para)
|
|
|
|
|
msgid "The vCenter driver supports images in the VMDK format. Disks in this format can be obtained from VMware Fusion or from an ESX environment. It is also possible to convert other formats, such as qcow2, to the VMDK format using the <option>qemu-img</option> utility. After a VMDK disk is available, load it into the OpenStack Image Service. Then, you can use it with the VMware vCenter driver. The following sections provide additional details on the supported disks and the commands used for conversion and upload."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:272(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:280(title)
|
|
|
|
|
msgid "Supported image types"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:273(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:281(para)
|
|
|
|
|
msgid "Upload images to the OpenStack Image Service in VMDK format. The following VMDK disk types are supported:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:277(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:285(para)
|
|
|
|
|
msgid "<emphasis role=\"italic\">VMFS Flat Disks</emphasis> (includes thin, thick, zeroedthick, and eagerzeroedthick). Note that once a VMFS thin disk is exported from VMFS to a non-VMFS location, like the OpenStack Image Service, it becomes a preallocated flat disk. This impacts the transfer time from the OpenStack Image Service to the data store when the full preallocated flat disk, rather than the thin disk, must be transferred."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:287(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:295(para)
|
|
|
|
|
msgid "<emphasis role=\"italic\">Monolithic Sparse disks</emphasis>. Sparse disks get imported from the OpenStack Image Service into ESX as thin provisioned disks. Monolithic Sparse disks can be obtained from VMware Fusion or can be created by converting from other virtual disk formats using the <code>qemu-img</code> utility."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:296(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:304(para)
|
|
|
|
|
msgid "The following table shows the <option>vmware_disktype</option> property that applies to each of the supported VMDK disk types:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:300(caption)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:308(caption)
|
|
|
|
|
msgid "OpenStack Image Service disk type settings"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:303(th)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:311(th)
|
|
|
|
|
msgid "vmware_disktype property"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:304(th) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:46(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:312(th) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:46(title)
|
|
|
|
|
msgid "VMDK disk type"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:309(td)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:317(td)
|
|
|
|
|
msgid "sparse"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:311(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:319(para)
|
|
|
|
|
msgid "Monolithic Sparse"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:315(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:66(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:68(td)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:323(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:66(td) ./doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml:68(td)
|
|
|
|
|
msgid "thin"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:317(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:325(para)
|
|
|
|
|
msgid "VMFS flat, thin provisioned"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:321(td)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:329(td)
|
|
|
|
|
msgid "preallocated (default)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:323(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:331(para)
|
|
|
|
|
msgid "VMFS flat, thick/zeroedthick/eagerzeroedthick"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:330(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:338(para)
|
|
|
|
|
msgid "The <option>vmware_disktype</option> property is set when an image is loaded into the OpenStack Image Service. For example, the following command creates a Monolithic Sparse image by setting <option>vmware_disktype</option> to <literal>sparse</literal>:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:339(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:347(para)
|
|
|
|
|
msgid "Note that specifying <literal>thin</literal> does not provide any advantage over <literal>preallocated</literal> with the current version of the driver. Future versions might restore the thin properties of the disk after it is downloaded to a vSphere data store."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:346(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:354(title)
|
|
|
|
|
msgid "Convert and load images"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:347(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:355(para)
|
|
|
|
|
msgid "Using the <code>qemu-img</code> utility, disk images in several formats (such as, qcow2) can be converted to the VMDK format."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:350(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:358(para)
|
|
|
|
|
msgid "For example, the following command can be used to convert a <link href=\"http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img\">qcow2 Ubuntu Precise cloud image</link>:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:356(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:364(para)
|
|
|
|
|
msgid "VMDK disks converted through <code>qemu-img</code> are <emphasis role=\"italic\">always</emphasis> monolithic sparse VMDK disks with an IDE adapter type. Using the previous example of the Precise Ubuntu image after the <code>qemu-img</code> conversion, the command to upload the VMDK disk should be something like:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:367(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:375(para)
|
|
|
|
|
msgid "Note that the <option>vmware_disktype</option> is set to <emphasis role=\"italic\">sparse</emphasis> and the <code>vmware_adaptertype</code> is set to <emphasis role=\"italic\">ide</emphasis> in the previous command."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:371(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:379(para)
|
|
|
|
|
msgid "If the image did not come from the <code>qemu-img</code> utility, the <code>vmware_disktype</code> and <code>vmware_adaptertype</code> might be different. To determine the image adapter type from an image file, use the following command and look for the <option>ddb.adapterType=</option> line:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:378(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:386(para)
|
|
|
|
|
msgid "Assuming a preallocated disk type and an iSCSI lsiLogic adapter type, the following command uploads the VMDK disk:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:386(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:394(para)
|
|
|
|
|
msgid "Currently, OS boot VMDK disks with an IDE adapter type cannot be attached to a virtual SCSI controller and likewise disks with one of the SCSI adapter types (such as, busLogic, lsiLogic) cannot be attached to the IDE controller. Therefore, as the previous examples show, it is important to set the <option>vmware_adaptertype</option> property correctly. The default adapter type is lsiLogic, which is SCSI, so you can omit the <parameter>vmware_adaptertype</parameter> property if you are certain that the image adapter type is lsiLogic."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:398(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:406(title)
|
|
|
|
|
msgid "Tag VMware images"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:399(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:407(para)
|
|
|
|
|
msgid "In a mixed hypervisor environment, OpenStack Compute uses the <option>hypervisor_type</option> tag to match images to the correct hypervisor type. For VMware images, set the hypervisor type to <literal>vmware</literal>. Other valid hypervisor types include: xen, qemu, kvm, lxc, uml, and hyperv."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:412(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:420(title)
|
|
|
|
|
msgid "Optimize images"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:413(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:421(para)
|
|
|
|
|
msgid "Monolithic Sparse disks are considerably faster to download but have the overhead of an additional conversion step. When imported into ESX, sparse disks get converted to VMFS flat thin provisioned disks. The download and conversion steps only affect the first launched instance that uses the sparse disk image. The converted disk image is cached, so subsequent instances that use this disk image can simply use the cached version."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:421(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:429(para)
|
|
|
|
|
msgid "To avoid the conversion step (at the cost of longer download times) consider converting sparse disks to thin provisioned or preallocated disks before loading them into the OpenStack Image Service. Below are some tools that can be used to pre-convert sparse disks."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:428(emphasis)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:436(emphasis)
|
|
|
|
|
msgid "Using vSphere CLI (or sometimes called the remote CLI or rCLI) tools"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:430(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:438(para)
|
|
|
|
|
msgid "Assuming that the sparse disk is made available on a data store accessible by an ESX host, the following command converts it to preallocated format:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:434(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:442(para)
|
|
|
|
|
msgid "(Note that the vifs tool from the same CLI package can be used to upload the disk to be converted. The vifs tool can also be used to download the converted disk if necessary.)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:440(emphasis)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:448(emphasis)
|
|
|
|
|
msgid "Using vmkfstools directly on the ESX host"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:442(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:450(para)
|
|
|
|
|
msgid "If the SSH service is enabled on an ESX host, the sparse disk can be uploaded to the ESX data store via scp and the vmkfstools local to the ESX host can use used to perform the conversion: (After logging in to the host via ssh)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:451(emphasis)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:459(emphasis)
|
|
|
|
|
msgid "vmware-vdiskmanager"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:452(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:460(para)
|
|
|
|
|
msgid "<code>vmware-vdiskmanager</code> is a utility that comes bundled with VMware Fusion and VMware Workstation. Below is an example of converting a sparse disk to preallocated format:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:457(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:465(para)
|
|
|
|
|
msgid "In all of the above cases, the converted vmdk is actually a pair of files: the descriptor file <emphasis role=\"italic\">converted.vmdk</emphasis> and the actual virtual disk data file <emphasis role=\"italic\">converted-flat.vmdk</emphasis>. The file to be uploaded to the OpenStack Image Service is <emphasis role=\"italic\">converted-flat.vmdk</emphasis>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:468(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:476(title)
|
|
|
|
|
msgid "Image handling"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:469(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:477(para)
|
|
|
|
|
msgid "The ESX hypervisor requires a copy of the VMDK file in order to boot up a virtual machine. As a result, the vCenter OpenStack Compute driver must download the VMDK via HTTP from the OpenStack Image Service to a data store that is visible to the hypervisor. To optimize this process, the first time a VMDK file is used, it gets cached in the data store. Subsequent virtual machines that need the VMDK use the cached version and don't have to copy the file again from the OpenStack Image Service."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:478(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:486(para)
|
|
|
|
|
msgid "Even with a cached VMDK, there is still a copy operation from the cache location to the hypervisor file directory in the shared data store. To avoid this copy, boot the image in linked_clone mode. To learn how to enable this mode, see <xref linkend=\"VMWare_config\"/>. Note also that it is possible to override the linked_clone mode on a per-image basis by using the <code>vmware_linked_clone</code> property in the OpenStack Image Service."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:489(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:497(title)
|
|
|
|
|
msgid "Networking with VMware vSphere"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:490(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:498(para)
|
|
|
|
|
msgid "The VMware driver supports networking with the <systemitem class=\"service\">nova-network</systemitem> service or the OpenStack Networking Service. Depending on your installation, complete these configuration steps before you provision VMs:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:497(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:505(para)
|
|
|
|
|
msgid "<emphasis role=\"bold\"> The <systemitem class=\"service\">nova-network</systemitem> service with the FlatManager or FlatDHCPManager</emphasis>. Create a port group with the same name as the <literal>flat_network_bridge</literal> value in the <filename>nova.conf</filename> file. The default value is <literal>br100</literal>. If you specify another value, the new value must be a valid linux bridge identifier that adheres to linux bridge naming conventions."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:506(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:514(para)
|
|
|
|
|
msgid "All VM NICs are attached to this port group."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:507(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:515(para)
|
|
|
|
|
msgid "Ensure that the flat interface of the node that runs the <systemitem class=\"service\">nova-network</systemitem> service has a path to this network."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:512(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:520(para)
|
|
|
|
|
msgid "<emphasis role=\"bold\">The <systemitem class=\"service\">nova-network</systemitem> service with the VlanManager</emphasis>. Set the <literal>vlan_interface</literal> configuration option to match the ESX host interface that handles VLAN-tagged VM traffic."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:518(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:526(para)
|
|
|
|
|
msgid "OpenStack Compute automatically creates the corresponding port groups."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:522(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:530(para)
|
|
|
|
|
msgid "If you are using the OpenStack Networking Service: Before provisioning VMs, create a port group with the same name as the <literal>vmware.integration_bridge</literal> value in <filename>nova.conf</filename> (default is <literal>br-int</literal>). All VM NICs are attached to this port group for management by the OpenStack Networking plug-in."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:533(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:541(title)
|
|
|
|
|
msgid "Volumes with VMware vSphere"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:534(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:542(para)
|
|
|
|
|
msgid "The VMware driver supports attaching volumes from the OpenStack Block Storage service. The VMware VMDK driver for OpenStack Block Storage is recommended and should be used for managing volumes based on vSphere data stores. More information about the VMware VMDK driver can be found at: <link href=\"http://docs.openstack.org/trunk/config-reference/content/vmware-vmdk-driver.html\">VMware VMDK Driver</link>. Also an iscsi volume driver provides limited support and can be used only for attachments."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:545(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:553(title)
|
|
|
|
|
msgid "vSphere 5.0 and earlier additional set up"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:546(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:554(para)
|
|
|
|
|
msgid "Users of vSphere 5.0 or earlier must host their WSDL files locally. These steps are applicable for vCenter 5.0 or ESXi 5.0 and you can either mirror the WSDL from the vCenter or ESXi server that you intend to use or you can download the SDK directly from VMware. These workaround steps fix a <link href=\"http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=2010507\">known issue</link> with the WSDL that was resolved in later versions."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:554(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:562(para)
|
|
|
|
|
msgid "When setting the VMwareVCDriver configuration options, you must include the <code>wsdl_location</code> option. For more information, see <link linkend=\"VMWareVCDriver_configuration_options\">VMwareVCDriver configuration options</link> above."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:560(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:568(title)
|
|
|
|
|
msgid "Mirror WSDL from vCenter (or ESXi)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:562(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:570(para)
|
|
|
|
|
msgid "Set the <code>VMWAREAPI_IP</code> shell variable to the IP address for your vCenter or ESXi host from where you plan to mirror files. For example:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:568(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:576(para)
|
|
|
|
|
msgid "Create a local file system directory to hold the WSDL files:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:573(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:581(para)
|
|
|
|
|
msgid "Change into the new directory. <placeholder-1/>"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:577(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:585(para)
|
|
|
|
|
msgid "Use your OS-specific tools to install a command-line tool that can download files like <placeholder-1/>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:582(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:590(para)
|
|
|
|
|
msgid "Download the files to the local file cache:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:592(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:600(para)
|
|
|
|
|
msgid "Because the <filename>reflect-types.xsd</filename> and <filename>reflect-messagetypes.xsd</filename> files do not fetch properly, you must stub out these files. Use the following XML listing to replace the missing file content. The XML parser underneath Python can be very particular and if you put a space in the wrong place, it can break the parser. Copy the following contents and formatting carefully."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:609(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:617(para)
|
|
|
|
|
msgid "Now that the files are locally present, tell the driver to look for the SOAP service WSDLs in the local file system and not on the remote vSphere server. Add the following setting to the <filename>nova.conf</filename> file for your <systemitem class=\"service\">nova-compute</systemitem> node:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:619(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:627(para)
|
|
|
|
|
msgid "Alternatively, download the version appropriate SDK from <link href=\"http://www.vmware.com/support/developer/vc-sdk/\">http://www.vmware.com/support/developer/vc-sdk/</link> and copy it to the <filename>/opt/stack/vmware</filename> file. Make sure that the WSDL is available, in for example <filename>/opt/stack/vmware/SDK/wsdl/vim25/vimService.wsdl</filename>. You must point <filename>nova.conf</filename> to fetch this WSDL file from the local file system by using a URL."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:628(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:636(para)
|
|
|
|
|
msgid "When using the VMwareVCDriver (vCenter) with OpenStack Compute with vSphere version 5.0 or earlier, <filename>nova.conf</filename> must include the following extra config option:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:636(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:644(title)
|
|
|
|
|
msgid "VMware ESX driver"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:637(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:645(para)
|
|
|
|
|
msgid "This section covers details of using the VMwareESXDriver. The ESX Driver has not been extensively tested and is not recommended. To configure the VMware vCenter driver instead, see <xref linkend=\"VMWareVCDriver_details\"/>."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:642(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:650(para)
|
|
|
|
|
msgid "The VMWare ESX driver has been deprecated in the Icehouse release and will be removed with the Juno release."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:648(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:656(title)
|
|
|
|
|
msgid "VMwareESXDriver configuration options"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:649(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:657(para)
|
|
|
|
|
msgid "When you use the VMwareESXDriver (no vCenter) with OpenStack Compute, add the following VMware-specific configuration options to the <filename>nova.conf</filename> file:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:661(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:669(para)
|
|
|
|
|
msgid "Remember that you will have one <systemitem class=\"service\">nova-compute</systemitem> service for each ESXi host. It is recommended that this host run as a VM on the same ESXi host that it manages."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:671(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:679(title)
|
|
|
|
|
msgid "Requirements and limitations"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:672(para)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:680(para)
|
|
|
|
|
msgid "The ESXDriver cannot use many of the vSphere platform advanced capabilities, namely vMotion, high availability, and DRS."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:678(title) ./doc/config-reference/compute/section_compute-scheduler.xml:515(title)
|
|
|
|
|
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:686(title) ./doc/config-reference/compute/section_compute-scheduler.xml:515(title)
|
|
|
|
|
msgid "Configuration reference"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
|
OpenStack Jenkins