openstack
/
openstack
Code Issues Proposed changes

Updated openstack/openstack 

Project: openstack/python-cinderclient  b7d34684607bbc0d8c507970661d0b1d3bed7843

Add an attachment_complete API call

The new attachment_update method in Cinder's API creates an attachment
object and populates it with the provided connector info. In addition,
we set the volumes status to in-use and update the attachment object
status to "attached".

This isn't really accurate though, because we don't know if the volume
is actually attached (connected) by the consumer or not.  Also a big
side effect here is that currently all of our tests and automation
use volume-status to determine if a volume is fully connected/ready
for use and that everything went well.  It's used as an ack in most
cases.

This change goes back to using multiple states to signify where a
an attachment is in it's life-cycle:
1. attachment_create
    We've created an empty attachment record but haven't done anything
    with it yet.
2. attachment_update
    We provided a connector and set up the TGT so that everything is
    ready for a consumer to connect/use it.
3. attachment_complete
    An ACK back from the consumer letting us know that they connected
    it successfully and are doing their thing.

It would be cool to just key all these checks of the attachment object itself,
and just use attachment_update to do so, maybe in the future?

Change-Id: I3b28d2cb89a8d81c7cdec425f355c78bfdfe3450
Related-Bug: #1710295
This commit is contained in:
John Griffith 2017-08-11 23:36:07 +00:00 committed by Gerrit Code Review
parent 0629e05f42
commit 7905a6fed0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
python-cinderclient

@ -1 +1 @@
Subproject commit 09a6506dda4bf7351719ee85e0fc9aac018bf435
Subproject commit b7d34684607bbc0d8c507970661d0b1d3bed7843