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.

Sign up for GitHub

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

Jump to bottom

Let PowerFlex disconnect from specific targets instead of all #14814

Open
roosterfish opened this issue Jan 17, 2025 · 0 comments
Open

Let PowerFlex disconnect from specific targets instead of all #14814

roosterfish opened this issue Jan 17, 2025 · 0 comments
Assignees
@roosterfish
Labels
Jira Triggers the synchronization of a GitHub issue in Jira

Comments

@roosterfish
Copy link
Contributor

Right now the PowerFlex driver is issuing nvme disconnect-all to disconnect from the NVMe/TCP subsystems. However this might produce a conflict if LXD isn't the only user of NVMe/TCP on this host or another storage driver like Pure is used in parallel to PowerFlex.

We can adapt the same techniques as they are performed in the Pure driver to connect to each individual subsystem's address.
Those addresses can be queried from PowerFlex by listing the SDT's availble for the used storage pool.
@roosterfish roosterfish added the Jira Triggers the synchronization of a GitHub issue in Jira label Jan 17, 2025
@roosterfish roosterfish changed the title Let PowerFlex disconnect from specific targest instead of all Let PowerFlex disconnect from specific targets instead of all Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@roosterfish roosterfish

Labels
Jira Triggers the synchronization of a GitHub issue in Jira
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@roosterfish