-
Notifications
You must be signed in to change notification settings - Fork 48
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
Disable SPDK discovery controller on GW initialization #192
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@leonidc 🖖 awesome PR! Please sign off the commit, see here, to color DCO check green 🟩. Also multi_gateway test fails consistently with this change, any idea why? |
@leonidc the multi gateway test runs "get_subsystems" and checks that it got 2 subsystem. As there is now only one subsystem you need to adjust the test. |
if multi gateway test checks that 2 subsystems are configured and we want to add configuration parameter in config file that in some cases server.py would not delete discovery subsystems - request of Aviv , it looks so many dependencies for such a small change. |
@leonidc you can check the config flag in the test, and fix accordingly. |
where can I find this flag ? it does not appear in conf file |
Fix multi-gateway test Signed-off-by: leonidc <[email protected]>
when Gateway is created it by default creates discovery subsystem
server.py when spdk is started, calls rpc nvmf_delete_subsystem.
Tests:
The rpc was issued before applying the new GW configuration :
[root@rhel8-leo-dev ceph-nvmeof]# nvmeof-cli get_subsystems
INFO:main:Get subsystems:
[] <= the discovery subsystem does not appear anymore
]# nvme discover -t tcp -a 192.168.13.3 -s 4420
Failed to write to /dev/nvme-fabrics: Input/output error
The PR has no impact on the current Gateway behavior. Checked also IOs from the nvme-tcp initiator.