We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NVMfRemoteControllerConnect
also can't get them via
docker run --network=opi-spdk-bridge_opi --rm -it namely/grpc-cli call --json_input --json_output opi-spdk-server:50051 NVMfRemoteControllerList "{}" connecting to opi-spdk-server:50051 { "ctrl": [ { "subnqn": "OpiNvme12" } ] } Rpc succeeded with OK status
so I have no idea how to call
docker run --network=host --rm -it namely/grpc-cli call --json_input --json_output 127.0.0.1:50051 NVMeNamespaceCreate "{'namespace' : {'subsystem_id' : 'nqn.2016-06.io.spdk:cnode1' , 'bdev' : 'OpiNvme12n7981' } }"
since n7981 is unknown...
n7981
The text was updated successfully, but these errors were encountered:
temp workaround is to use
docker run --network=opi-spdk-bridge_opi --rm -it namely/grpc-cli call --json_input --json_output opi-spdk-server:50051 NullDebugList "{}"
Sorry, something went wrong.
consider using https://grpc.io/docs/languages/go/basics/#server-side-streaming-rpc
maybe create NVMfRemoteNamespace objects per output of the bdev_nvme_attach_controller call...
NVMfRemoteNamespace
bdev_nvme_attach_controller
glimchb
No branches or pull requests
also can't get them via
so I have no idea how to call
since
n7981
is unknown...The text was updated successfully, but these errors were encountered: