Skip to content
New issue

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 doesn't return list of created bdevs #12

Open
glimchb opened this issue Oct 25, 2022 · 3 comments
Open

NVMfRemoteControllerConnect doesn't return list of created bdevs #12

glimchb opened this issue Oct 25, 2022 · 3 comments
Assignees

Comments

@glimchb
Copy link
Member

glimchb commented Oct 25, 2022

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...

@glimchb
Copy link
Member Author

glimchb commented Oct 25, 2022

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 "{}"

@glimchb glimchb self-assigned this Oct 25, 2022
@glimchb
Copy link
Member Author

glimchb commented Mar 20, 2023

@glimchb
Copy link
Member Author

glimchb commented Jun 29, 2023

maybe create NVMfRemoteNamespace objects per output of the bdev_nvme_attach_controller call...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant