When will NvmeLunsPerNs is removed?

[uchida2016]

When nvme bdev is deleted by rpc.py with delete_lun option, coresponding nvme_device is not deleted.

ex: Nvme3n1p0 is on 0000:02:00.0
# ./scripts/rpc.py delete_lun Nvme3n1p0

Then I try to create bdev again by rpc.py with construct_nvme_bdev. But it fails because the nvme_device already existed.

# ./scripts/rpc.py construct_nvme_bdev 0000:02:00.0
Got JSON-RPC error response
request:
{
  "jsonrpc": "2.0",
  "params": {
    "pci_address": "0000:02:00.0"
  },
  "method": "construct_nvme_bdev",
  "id": 1
}
response:
{
  "message": "Invalid parameters",
  "code": -32602
}

I'd like to make a PR to delete nvme_device in blockdev_nvme_destruct.
Regarding to it, I have a question. Daniel mentioned that NvmeLunsPerNs option will be removed in #85. I want to wait for it, then make a PR. Would you tell me when NvmeLunsPerNs will be removed?

[ghost]

The actual NvmeLunsPerNs removal is fairly trivial, but I am working on a more general replacement for this feature, since we still want to support splitting bdevs (e.g. for testing large numbers of independent LUNs); however, it will now be implemented as a generic "virtual blockdev" that can be layered on top of the NVMe bdev as well as other bdev types. I expect this work to be done within Q1, but I don't have an exact timeline.

Once this cleanup is complete, we should definitely be in a better position to correctly support removal of LUNs and bdevs.

[uchida2016]

Thank you for the information. I need removal of LUNs and bdevs to be supported in next version 17.03.

[ghost]

NvmeLunsPerNs has been removed in commit efccac8.