From faf1e3a3be523bbf86ce8a06275d7a32ff0b7a67 Mon Sep 17 00:00:00 2001 From: Joseph Robinson Date: Tue, 19 May 2015 13:18:04 +1000 Subject: [PATCH] VMware - adding a note on NFS 4.1 support Adding a note to the OpenStack configuration reference on VMware support for version 4.1 or NFS. In addition, improve the clarity of two sentences in the chapter. Change-Id: I500473e89fd1d5931f92eabd7c8963cac6b167b4 backport: none Closes-Bug: #1455532 --- .../block-storage/drivers/vmware-vmdk-driver.xml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml b/doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml index ffc160ef54..2b6339c268 100644 --- a/doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml +++ b/doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml @@ -23,13 +23,17 @@ visible from the ESX hosts in the managed cluster. 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. + the volume is subsequently attached to an instance. The + reason for this requirement is that data stores visible + to the instance determine where to place + the volume. Before the service creates the VMDK file, + attach a volume to the target instance. 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. + With the update to ESX version 6.0, the VMDK driver + now supports NFS version 4.1.
Configuration