# Data Object - NvdimmNamespaceCreateSpec(vim.host.NvdimmSystem.NamespaceCreateSpec)

Parameter to
  CreateNvdimmNamespace_Task
Extends
  DynamicData
Since
  vSphere API 6.7

## Data Object Description

Deprecated. As of vSphere 6.7u1, use PMemNamespaceCreateReq

Arguments for creating a namespace.

Properties

Name | Type | Description
--- | --- | ---
blockCount | xsd:long | Number of blocks in the namespace. For persistent region type, blockCount is the size of persistent region in bytes. For block region type, block count represent number of bytes per block size.
blockSize | xsd:long | Size of block in the namespace. For persistent region type, block size is one. For block region, block size represents one of the logical block sizes of 512, 4096 etc.
friendlyName* | xsd:string | Friendly name of the namespace to be created. A friendly name can be provided by user to assosiate a name to the created namespace, but such a name is not mandatory and is empty string by default.
locationID | xsd:int | This identifier is the interleave set ID if the namespace is being used in persistent mode. If in block mode, this is a device handle.
type | xsd:string | Type of the namespace to be created - block or persistent. Must be one of the values in NamespaceType
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="NvdimmNamespaceCreateSpec"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="friendlyName" type="xsd:string" minOccurs="0"/> <element name="blockSize" type="xsd:long"/> <element name="blockCount" type="xsd:long"/> <element name="type" type="xsd:string"/> <element name="locationID" type="xsd:int"/> </sequence> </extension> </complexContent> </complexType>