On Thu, Jul 13, 2023 at 12:14:14PM +0200, Hannes Reinecke wrote: > > Exposing the subsystem is from the target configuration side. > > Additionally, the --context (which is in the initiator/host side), > > according to Daniel, is there to distinguish between different > > invocations. I proposed that blktests subsystem will not be part of > > discoverable fabric or protected somehow by access list. Therefore, no > > additional invocation will happen. I am confused. This is exactly what the whole --context thing is. > Hmm. Maybe we can tweak blktest to use it's own HostNQN, and always pass > that for any nvme-cli call. This is what the current code already does.
