openstack/cinder
Code Issues Proposed changes

Modify a little desc to satisfy the code

Browse Source 
The method for attaching to update the status of the volume in the
DB is cinder.volume.api.reserve_volume in code and the method for
attaching to finalize the status of the volume and release the
resourece is cinder.volume.api.attach(self, context, volume,
instance_uuid, host_name, mountpoint, mode) in code.

Change-Id: I1af560d5840296d28d6f005b7758b6e75faa727e
This commit is contained in:
zejian Zhuang 2017-06-08 15:27:58 +08:00
parent 71a97f3470
commit 811eb1ec19
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/contributor/attach_detach_conventions.rst
View File

@ -28,7 +28,7 @@ There are three things that happen in the workflow for an attach or detach call.
1. Update the status of the volume in the DB (ie attaching/detaching)
- For Attach, this is the cinder.volume.api.reserve method
- For Attach, this is the cinder.volume.api.reserve_volume method
- For Detach, the analogous call is cinder.volume.api.begin_detaching
2. Handle the connection operations that need to be done on the Volume
@ -131,7 +131,7 @@ back up to the API and returned as the response back out to Nova.
At this point, we return attach info to the caller that provides everything
needed to make the remote iSCSI connection.
attach(self, context, volume, instance_uuid, host_name, mount_point, mode)
attach(self, context, volume, instance_uuid, host_name, mountpoint, mode)
--------------------------------------------------------------------------
This is the last call that *should* be pretty simple. The intent is that this