delta/openstack/python-cinderclient.git, branch 3.2.0

Merge "Unsupported 'message' Exception attribute in PY3"

2017-08-29T02:32:01+00:00

Merge "Fix attachment_id returned by create and show volume"

2017-08-28T22:25:02+00:00

Fix attachment_id returned by create and show volume

2017-08-28T12:36:12+00:00

The attachment_ids in the volume info returned by show volume
were incorrect. It was showing the volume_id, not the actual
attachment_id. This fix changes the attachment_ids returned by show
volume to correctly reflect the attachment_id.

Also, added a unit test for this, and added an attachment_id
to the fake volume so that other tests wouldn't now fail.

Closes-Bug: #1713082
Change-Id: I9ec36af5dd460d03d786aeeb3cc36a869c19ff62

Unsupported 'message' Exception attribute in PY3

2017-08-28T02:35:45+00:00

The 'message' attribute has been deprecated and removed from Python3.
Use six.text_type(e) instead of e.message. For more details, please
check [1]:

[1] https://www.python.org/dev/peps/pep-0352/

Change-Id: Ibd4e7f5fefa6b1dfb6258c5eacfa53cd3485d22c

Enable F811, F821

2017-08-23T19:02:14+00:00

F811 is a little noisy with api_versions.wraps()
decorated methods, but opting to disable it in these
cases seems better than missing problems in the rest
of the code.

Change-Id: I9c46938ab2a442e55f96b5ab6c119c4475afaecd

Fix method/module redefinition errors

2017-08-23T18:52:58+00:00

These are caught by F811, but that test is
currently disabled because it fails on
@api_versions.wraps() decorated methods.

Just clean up these errors for now.

Change-Id: I42aed024352f798ebafddeb6f12880d8726360fe

Updated from global requirements

2017-08-23T12:20:09+00:00

Change-Id: Iacb099eeea7cf67b9a2ee792cb8bfa751406f1f6

Merge "Enable H306"

2017-08-22T14:34:25+00:00

Add an attachment_complete API call

2017-08-14T16:27:44+00:00

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

Fix wrong links

2017-08-11T09:02:16+00:00

Some docs links have changed. We should update the wrong links in our codes.

Change-Id: I2e43cd26e10e5be0452d611064e199f784ea0d34