nvmet.host_subsys.query ======================= .. raw:: html
List of filters for query results. See API documentation for "Query Methods" for more guidance.
No Additional Items[
[
"name",
"=",
"bob"
]
]
[
[
"OR",
[
[
[
"name",
"=",
"bob"
]
],
[
[
"name",
"=",
"larry"
]
]
]
]
]
Query options customize the results returned by a query method. More complete documentation with examples
are covered in the "Query methods" section of the TrueNAS API documentation.
Extra options are defined on a per-endpoint basis and are described in the documentation for the associated
query method.
An array of field names describing the manner in which query results should be ordered. The field names may
also have one of more of the following special prefixes: -
(reverse sort direction), nulls_first:
(place
any null values at the head of the results list), nulls_last:
(place any null values at the tail of the
results list).
[
"size",
"-devname",
"nulls_first:-expiretime"
]
An array of field names specifying the exact fields to include in the query return. The dot character .
may be used to explicitly select only subkeys of the query result.
[
"username",
"Authentication.status"
]
Return a numeric value representing the number of items that match the specified query-filters
.
Return the JSON object of the first result matching the specified query-filters
. The query fails
if there specified query-filters
return no results.
This specifies the beginning offset of the results array. When combined with the limit
query-option
it may be used to implement pagination of large results arrays. WARNING: some query methods provide
volatile results and the onus is on the developer to understand whether pagination is appropriate
for a particular query API method.
This specifies the maximum number of results matching the specified query-filters
to return. When
combined wtih the offset
query-option it may be used to implement pagination of large results arrays.
WARNING: some query methods provide volatile results and the onus is on the developer to understand whether
pagination is appropriate for a particular query API method.
NQN of the host that will connect to this TrueNAS.
Must be at least 1
characters long
If set, the secret that the host must present when connecting.
A suitable secret can be generated using nvme gen-dhchap-key
, or by using the nvmet.host.generate_key
API.
Must be at least 1
characters long
If set, the secret that this TrueNAS will present to the host when the host is connecting (Bi-Directional Authentication).
A suitable secret can be generated using nvme gen-dhchap-key
, or by using the nvmet.host.generate_key
API.
Must be at least 1
characters long
If selected, the DH (Diffie-Hellman) key exchange built on top of CHAP to be used for authentication.
HMAC (Hashed Message Authentication Code) to be used in conjunction if a dhchap_dhgroup
is selected.
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
Must be at least 1
characters long
Must be at most 223
characters long
If True
then any host can access the storage associated with this subsystem (i.e. no access control).
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.