delta/openstack/python-openstackclient.git/openstackclient/volume/v2/volume_snapshot.py, branch 6.2.0 opendev.org: openstack/python-openstackclient Fix typos 2021-10-26T13:53:51+00:00 Cyril Roelandt cyril@redhat.com 2021-10-26T13:53:35+00:00 43639e1118a757fd1a00d9ea999db43133c40763 Change-Id: Idd502c8df21da79ff3b9339870f38378f5337879 
Change-Id: Idd502c8df21da79ff3b9339870f38378f5337879
Merge "Fix faulthy state argument choice" 2020-03-24T21:34:44+00:00 Zuul zuul@review.opendev.org 2020-03-24T21:34:44+00:00 81dcc91214c7b449e74ed5d0fe6854590431e6ef 






Replace six.iteritems() with .items()
2020-01-09T09:41:29+00:00

lihaijing
lihaijing@fiberhome.com

2017-07-07T03:48:48+00:00

d15bbada73f81136c966007d9c564dd6cfb2fd9c

1. As mentioned in [1], we should avoid using six.iteritems to achieve
   iterators. We can use dict.items instead, as it will return iterators
   in PY3 as well. And dict.items/keys will more readable.

2. In py2, the performance about list should be negligible,
   see the link [2].

[1] https://wiki.openstack.org/wiki/Python3
[2] http://lists.openstack.org/pipermail/openstack-dev/2015-June/066391.html

Co-Authored-By: Akihiro Motoki <amotoki@gmail.com>
Change-Id: I4b9edb326444264c0f6c4ad281acaac356a07e85
Implements: blueprint replace-iteritems-with-items





1. As mentioned in [1], we should avoid using six.iteritems to achieve
   iterators. We can use dict.items instead, as it will return iterators
   in PY3 as well. And dict.items/keys will more readable.

2. In py2, the performance about list should be negligible,
   see the link [2].

[1] https://wiki.openstack.org/wiki/Python3
[2] http://lists.openstack.org/pipermail/openstack-dev/2015-June/066391.html

Co-Authored-By: Akihiro Motoki <amotoki@gmail.com>
Change-Id: I4b9edb326444264c0f6c4ad281acaac356a07e85
Implements: blueprint replace-iteritems-with-items







Fix faulthy state argument choice
2019-12-19T08:48:17+00:00

Bram Verschueren
verschueren.bram@gmail.com

2019-12-13T10:13:54+00:00

69870ae439f18863979949f5728543a0fb1cbe83

The correct state name for a failing volume snapshot deletion is
'error_deleting' instead of 'error-deleting'. [1]

[1] https://opendev.org/openstack/cinder/src/commit/89d6a5042fcb2ede5a0b1112d72fae805ea52fcd/cinder/objects/fields.py#L126

Task: #37844
Story: #2007037

Change-Id: Ia99900ece4f1cd29769b22ddaa3965789d719556





The correct state name for a failing volume snapshot deletion is
'error_deleting' instead of 'error-deleting'. [1]

[1] https://opendev.org/openstack/cinder/src/commit/89d6a5042fcb2ede5a0b1112d72fae805ea52fcd/cinder/objects/fields.py#L126

Task: #37844
Story: #2007037

Change-Id: Ia99900ece4f1cd29769b22ddaa3965789d719556







Use cliff formattable columns in volume v2 commands
2019-06-22T19:56:10+00:00

Akihiro Motoki
amotoki@gmail.com

2017-05-15T10:19:07+00:00

4cd614305fbe8b90d45ad6803bfa8b7978f19318

Partial-Bug: #1687955
Partially implement blueprint osc-formattable-columns

Change-Id: I761ccac126208927594ad0d98a3cf5ad8b44bd48





Partial-Bug: #1687955
Partially implement blueprint osc-formattable-columns

Change-Id: I761ccac126208927594ad0d98a3cf5ad8b44bd48







Fix NoneType error for volume snapshot create command
2017-04-26T16:07:08+00:00

Huanxuan Ao
huanxuan.ao@easystack.cn

2017-03-08T02:01:16+00:00

1c49a1f01da73b8eed701809de88b408e738dfed

In volume snapshot command, <volume> is the same
as <snapshot-name> when --volume is not specified,
but <volume> cannot be None, so when <snapshot-name>
is not specified (<snapshot-name> is None), a NoneType
error appears.
So make <snapshot-name> no longer optional, it should
be always present.

Change-Id: I3d9f10753a8ef601e70816421c160598e2cc811f
Closes-bug: #1659894





In volume snapshot command, <volume> is the same
as <snapshot-name> when --volume is not specified,
but <volume> cannot be None, so when <snapshot-name>
is not specified (<snapshot-name> is None), a NoneType
error appears.
So make <snapshot-name> no longer optional, it should
be always present.

Change-Id: I3d9f10753a8ef601e70816421c160598e2cc811f
Closes-bug: #1659894







Help/docs cleanups: marker, limit, ip-address metavars
2017-04-04T03:56:19+00:00

Dean Troyer
dtroyer@gmail.com

2017-04-03T21:15:14+00:00

1686dc54f09b6e77b1de3abc708c297710987a04

Cleanup help strings and docs for clarity and to keep things consistent:
* --limit metavar should be <num-resource> to indicate what is being counted
* --marker metavar should be <resource> or <resource-id> to indicate the
  type of value being specified
* <*-ip-address> metavars should be just <ip-address> as there is no difference
  in format between fixed and floating IPs
* Move all occurances of '(name or ID)' to end of help text

Change-Id: I2c31746ed6ded3845244e03e57d809f8bc0e6b9d





Cleanup help strings and docs for clarity and to keep things consistent:
* --limit metavar should be <num-resource> to indicate what is being counted
* --marker metavar should be <resource> or <resource-id> to indicate the
  type of value being specified
* <*-ip-address> metavars should be just <ip-address> as there is no difference
  in format between fixed and floating IPs
* Move all occurances of '(name or ID)' to end of help text

Change-Id: I2c31746ed6ded3845244e03e57d809f8bc0e6b9d







Merge "Support "--no-property" option in volume snapshot set"
2017-01-26T06:38:31+00:00

Jenkins
jenkins@review.openstack.org

2017-01-26T06:38:31+00:00

da2a820d2f4e5589671f494edcd8e8b3e69b7cb0












Support "--no-property" option in volume snapshot set
2017-01-25T23:32:58+00:00

zhiyong.dai
zhiyong.dai@easystack.cn

2017-01-02T09:55:32+00:00

26d50be79a401322f4e74b94c066257ddf0f287c

Supporting "--no-property" option will apply user a convenient
way to clean all properties of volume snapshot in a short command,
and this kind of behavior is the recommended way to devref.
The patch adds "--no-property" option in "volume snapshot set" command,
and update related test cases and devref document.

Change-Id: I5f10cc2b5814553699920c4343995b2e11416e4e
Implements: blueprint allow-overwrite-set-options





Supporting "--no-property" option will apply user a convenient
way to clean all properties of volume snapshot in a short command,
and this kind of behavior is the recommended way to devref.
The patch adds "--no-property" option in "volume snapshot set" command,
and update related test cases and devref document.

Change-Id: I5f10cc2b5814553699920c4343995b2e11416e4e
Implements: blueprint allow-overwrite-set-options







Add --project and --project-domain option to "volume snapshot list"
2017-01-07T14:21:11+00:00

jiahui.qiang
jiahui.qiang@easystack.cn

2017-01-06T14:49:41+00:00

27e0be051714fe11a3b9b5306f2e0a72d95fe2c3

Add "--project" and "--project-domain" option to volume v2's
"volume snapshot list" command, it will filter list result by different project.

Change-Id: I7dccd6d8d9f1889fa9cb0c2d04a42d77975c645b





Add "--project" and "--project-domain" option to volume v2's
"volume snapshot list" command, it will filter list result by different project.

Change-Id: I7dccd6d8d9f1889fa9cb0c2d04a42d77975c645b