HostNasVolumeSpec

HostNasVolumeSpec
HostNasVolumeSpec

Specification for creating NAS volume.

When mounting a NAS volume on multiple hosts, the same remoteHost and remotePath values should be used on every host, otherwise it will be treated as different datastores. For example, if one host references the remotePath of a NAS volume as "/mnt/mount1" and another references it as "/mnt/mount1/", it will not be recognized as the same datastore.

AllOf
This class requires all of the following:
JSON Example
{
    "_typeName": "string",
    "remoteHost": "string",
    "remotePath": "string",
    "localPath": "string",
    "accessMode": "string",
    "type": "string",
    "userName": "string",
    "password": "string",
    "remoteHostNames": [
        "string"
    ],
    "securityType": "string",
    "vmknicToBind": "string",
    "vmknicBound": false,
    "connections": 0
}
string
remoteHost
Required

The host that runs the NFS v3 or CIFS server.

For NFS v4.1 and beyond use remoteHostNames defined later. The field remotehost may be deprecated in future for NFS, so clients should plan to use the property remoteHostNames to send in the host name(s) for both NFS v3 and v4.1

string
remotePath
Required

The remote path of the NFS mount point.

string
localPath
Required

The localPath refers to the name of the NAS datastore to be created using this specification.

In the case of ESX Server, the datastore name is a component in the file system path at which the NAS volume can be found. For example, if localPath is set to "nas_volume" the created NAS datastore will be named "nas_volume" and it can be accessed via the file system path "/vmfs/volumes/nas_volume".

In the case of VMware Server, the localPath will also be used as the datastore name, but the datastore name may not necessarily be reflected in the file system path where the NAS volume may be accessed.

string
accessMode
Required

Access mode for the mount point.

Mounting in read-write mode would be successful irregardless on how the mount point is exported or access permissions. For example, mounting a volume that is exported as read-only as readWrite will succeed. Hence, that a readWrite mount succeeds should not be taken as an indication that all files on a mount is writable.

If a file system is mounted readOnly, the system cannot create or modify any files on the file system. This is mostly useful for storing ISO images and templates, since a virtual machine cannot be powered on from a readOnly volume.

The access mode of a mounted NFS volume can be obtained at accessMode.

See also HostMountModeEnum.

string
type
Optional

Specifies the type of the the NAS volume.

Supported types are CIFS, NFS, NFS41 If not specified, defaults to NFS

string
userName
Optional

If type is CIFS, the user name to use when connecting to the CIFS server.

If type is NFS, this field will be ignored.

string As password As password
password
Optional

If type is CIFS, the password to use when connecting to the CIFS server.

If type is NFS, this field will be ignored.

array of string
remoteHostNames
Optional

Hostnames or IP addresses of remote NFS server.

In case of NFS v4.1 this may have multiple entries. For NFS v3 the input should be same in both remoteHost and remoteHostNames. In case of NFS v4.1, if vmknic binding is enabled, then input can be in format {hostip1:vmknic1, hostip2:vmknic2}.

string
securityType
Optional

Provided during mount indicating what security type, if any, to use See HostNasVolumeSecurityTypeEnum

string
vmknicToBind
Optional

Name of the vmknic to be used by this mount.

This field will be updated by a client with vmknic that will be used for NAS volume mount operation for vmknic binding for NFSv3

Since: vSphere API Release 8.0.1.0

boolean
vmknicBound
Optional

Indicates whether a client wants to bind this mount to vmknic.

This field will be set to true by a client if vmknic should bind during NAS volume mount operation for NFSv3 else it will be set to false

Since: vSphere API Release 8.0.1.0

integer As int32 As int32
connections
Optional

Indicates the number of TCP connections for the particular NFSv3 Server during NAS volume mount operation.

If unset or set to 0, it defaults to one connection

Since: vSphere API Release 8.0.1.0