nvmet.namespace.create ====================== Create a NVMe target namespace in a subsystem (`subsys`). This will expose the namespace to any hosts permitted to access the subsystem. .. raw:: html
NVMe-oF namespace configuration data for creation.
No Additional PropertiesNamespace ID (NSID).
Each namespace within a subsystem has an associated NSID, unique within that subsystem.
If not supplied during namespace creation then the next available NSID will be used.
Value must be greater or equal to 1 and strictly lesser than 4294967295
Type of device (or file) used to implement the namespace.
Normalized path to the device or file for the namespace.
Must be at least 1 characters long
When device_type is "FILE" then this will be the size of the file in bytes.
If enabled is False then the namespace will not be accessible.
Some namespace configuration changes are blocked when that namespace is enabled.
ID of the NVMe-oF subsystem to contain this namespace.
The created NVMe-oF namespace configuration.
No Additional PropertiesUnique identifier for the NVMe-oF namespace.
Namespace ID (NSID).
Each namespace within a subsystem has an associated NSID, unique within that subsystem.
If not supplied during namespace creation then the next available NSID will be used.
Value must be greater or equal to 1 and strictly lesser than 4294967295
NVMe-oF subsystem that contains this namespace.
No Additional PropertiesUnique identifier for the NVMe-oF subsystem.
Human readable name for the subsystem.
If subnqn is not provided on creation, then this name will be appended to the basenqn from     nvmet.global.config to generate a subnqn.
Must be at least 1 characters long
NVMe Qualified Name (NQN) for the subsystem.
If not provided during creation, will be auto-generated by appending the name to the basenqn     from nvmet.global.config.
Must be at least 1 characters long
Serial number assigned to the subsystem.
Any host can access the storage associated with this subsystem (i.e. no access control).
Enable Protection Information (PI) for data integrity checking.
Maximum number of queue IDs allowed for this subsystem.
IEEE Organizationally Unique Identifier for the subsystem.
If set to either True or False, then override the global ana setting from nvmet.global.config for this     subsystem only.
If null, then the global ana setting will take effect.
List of host ids which have access to this subsystem.
Only populated on query if extra.options.verbose is set.
List of namespaces ids in this subsystem.
Only populated on query if extra.options.verbose is set.
List of ports ids on which this subsystem is available.
Only populated on query if extra.options.verbose is set.
Type of device (or file) used to implement the namespace.
Path to the device or file being used to implement the namespace.
When device_type is:
device_path is e.g. "zvol/poolname/zvolname"device_path is e.g. "/mnt/poolmnt/path/to/file". The file will be created if necessary.Must be at least 1 characters long
When device_type is "FILE" then this will be the size of the file in bytes.
Unique device identifier for the namespace.
Must be at least 1 characters long
Namespace Globally Unique Identifier for the namespace.
Must be at least 1 characters long
If enabled is False then the namespace will not be accessible.
Some namespace configuration changes are blocked when that namespace is enabled.
Reflect the locked state of the namespace.
The underlying device_path could be an encrypted ZVOL, or a file on an encrypted dataset. In either case     locked will be True if the underlying entity is locked.