Bug 1041726 - [RFE][cinder]: Stackable/flexible protocol to attach/detach volumes
Summary: [RFE][cinder]: Stackable/flexible protocol to attach/detach volumes
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/cind...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 18:50 UTC by RHOS Integration
Modified: 2015-11-20 19:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:15:03 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 18:50:40 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/stackable-transaction.

Description:

Now cinder and nova have fixed protocol to attach/detach volumes. If volume drivers can do many transactions between cinder-volume and nova-compute (or cinder-agent), they can extend its capability like dynamic client ACL management or authentication. To do it, each driver should have function lists for attaching/detaching volumes and cinder/nova-side volume drivers should be able to call any function in the lists at the other-side with any arguments.

For example:
Nova-side function list: [begin_attaching, get_connection_info, connect_volume],  [begin_detaching, disconnect_volume, finish_detaching]
Cinder-side function list: [reserve, initialize_connection, attach], [begin_detaching, terminate_connection, detach]

Attaching protocol: nova:begin_attaching > cinder:reserve > nova:get_connection_info > cinder:initialize_connection > nova:connect_volume > cinder:attach

Detaching protocol: nova:begin_detaching > cinder: begin_detaching > nova:disconnect_volume > > cinder:terinate_connection > nova:finish_detaching > cinder:detach

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.