Skip to content
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.

detaching volume by attachment_id #617

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jangseon-ryu
Copy link

This is a patch for detaching volume by attachment_id,
when using in attaching a same volume to multiple hosts.
This patch, Of course, support both 1:1 and 1:N attachment.

Currently, detaching logic in gophercloud can only support on 1:1(volume:host) attachment.
But many users want to be able to attach the same volume to multiple hosts.
(for example : clustered application(A:P))

BP : https://specs.openstack.org/openstack/cinder-specs/specs/kilo/multi-attach-volume.html

Signed-off-by: Jangseon Ryu jangseon.ryu@navercorp.com

when using in attaching a same volume to multiple hosts.
This patch, Of course, support both 1:1 and 1:N attachment.

Currently, detaching logic in gophercloud can only support on 1:1(volume:host) attachment.
But many users want to be able to attach the same volume to multiple hosts.
(for example : clustered application(A:P))

BP : https://specs.openstack.org/openstack/cinder-specs/specs/kilo/multi-attach-volume.html

Signed-off-by: Jangseon Ryu <jangseon.ryu@navercorp.com>
@coveralls
Copy link

coveralls commented Oct 19, 2016

Coverage Status

Coverage increased (+0.006%) to 80.499% when pulling e881b4a on jangseon-ryu:block-detach-attachmentid into e00690e on rackspace:master.

@j-griffith
Copy link

So technically this works, but it's pretty outdated. The problem here is that the attachment_id isn't always accessible. I'd suggest at this point that we add the V3/Attachments controller and utilize that (as it's designed to do what you want here). I have it on my list after Snapshots if that's helpful.

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

Successfully merging this pull request may close these issues.

3 participants