delta/openstack/python-openstackclient.git/openstackclient/tests/functional, branch stable/victoria opendev.org: openstack/python-openstackclient Merge "Show words indicating booted from volume for server image" 2020-09-30T20:34:53+00:00 Zuul zuul@review.opendev.org 2020-09-30T20:34:53+00:00 e7b2528c4a4fc221d5efdd88d60ffd95ea4e3f63 






Merge "Output correct json for security groups in 'openstack server show'"
2020-09-25T09:44:41+00:00

Zuul
zuul@review.opendev.org

2020-09-25T09:44:40+00:00

03b921631816ef3e6c41a87bc90259ec75176eea












Output correct json for security groups in 'openstack server show'
2020-09-14T13:22:27+00:00

jay
jayadityagupta11@gmail.com

2020-06-04T12:09:03+00:00

bae89b30144fdf40d0fea31e1a595b507e32c4f3

Fixes incorrect json output for 'openstack server show -f json'.
The security group json output groups all the json as one
for e.g. "security_groups": "name='group1'\nname='group2'"
The correct output should be
"security_groups" : [{"name" : "group1"}, {"name" : "group2"}]
properties and volumes_attached fields also has similar issue.

Story: 2007755

Change-Id: I1b1cac716329e0530400aff782c08000b21d8e1d





Fixes incorrect json output for 'openstack server show -f json'.
The security group json output groups all the json as one
for e.g. "security_groups": "name='group1'\nname='group2'"
The correct output should be
"security_groups" : [{"name" : "group1"}, {"name" : "group2"}]
properties and volumes_attached fields also has similar issue.

Story: 2007755

Change-Id: I1b1cac716329e0530400aff782c08000b21d8e1d







Show words indicating booted from volume for server image
2020-08-27T20:24:48+00:00

melanie witt
melwittt@gmail.com

2020-07-27T22:04:47+00:00

4a3c5207c1b2d628d1ec8b30e28f56e5956bd2e0

For a server booted from a volume, nova API does not store an image_id
and instead returns an empty string. Currently, openstackclient
similarly shows an empty string for Image Name and Image ID for servers
booted from volumes.

To aid CLI users in understanding the meaning of no image_id, we can
display the string "N/A (booted from volume)" in the image field if the
server was booted from a volume.

Change-Id: I9c62cf6fe23b2e934dcbf5ebbf706b2705d2e424





For a server booted from a volume, nova API does not store an image_id
and instead returns an empty string. Currently, openstackclient
similarly shows an empty string for Image Name and Image ID for servers
booted from volumes.

To aid CLI users in understanding the meaning of no image_id, we can
display the string "N/A (booted from volume)" in the image field if the
server was booted from a volume.

Change-Id: I9c62cf6fe23b2e934dcbf5ebbf706b2705d2e424







Delete the testcases that arent needed anymore
2020-07-23T21:08:42+00:00

mb711d
mb711d@att.com

2020-07-15T21:18:53+00:00

4e2aefb5fa2ce236473187650149cf421c5f8c53

The file test_examples.py has never worked since its written and and cli in
the example directory are covered by other functional tests for container,
flavor and object lists and they have better asserts. So, deleting the file

Change-Id: Ib9af40da96e66354fe878e79a80048a58f8dd6fe





The file test_examples.py has never worked since its written and and cli in
the example directory are covered by other functional tests for container,
flavor and object lists and they have better asserts. So, deleting the file

Change-Id: Ib9af40da96e66354fe878e79a80048a58f8dd6fe







Merge "Add '--force; parameter to 'openstack quota set'"
2020-07-06T20:50:24+00:00

Zuul
zuul@review.opendev.org

2020-07-06T20:50:24+00:00

d0741d78533ae5f538f3f0be0a8a0035581745cc












Resolve PEP8
2020-05-14T18:53:38+00:00

Pete Zaitcev
zaitcev@kotori.zaitcev.us

2020-05-14T18:53:38+00:00

52ff421e3d339f81c2625bff429e6829a2d9af67

No idea how this happened, but reviews started failing the
pep8 gate job. The failures are legitimate, see the commit.
I guess the pep8 tests became smarter and found these issues.

Change-Id: Id9a0dad644134dafd68eed37fe8f41c583d7a619





No idea how this happened, but reviews started failing the
pep8 gate job. The failures are legitimate, see the commit.
I guess the pep8 tests became smarter and found these issues.

Change-Id: Id9a0dad644134dafd68eed37fe8f41c583d7a619







Add '--force; parameter to 'openstack quota set'
2020-04-14T20:59:52+00:00

hackertron
jayadityagupta11@gmail.com

2020-03-19T13:35:54+00:00

b328cf74df7f94a20de85b3c0992dcb65e818458

The compute service allows us to to force set a quota, setting a
quota value that is less than the amount of the resource currently
consumed. Expose this feature by way of a '--force' boolean
parameter.

Change-Id: I1d1ac1ac46f49f64794ffc8631e166935537966c





The compute service allows us to to force set a quota, setting a
quota value that is less than the amount of the resource currently
consumed. Expose this feature by way of a '--force' boolean
parameter.

Change-Id: I1d1ac1ac46f49f64794ffc8631e166935537966c







Merge "Support for stateless security groups"
2020-04-08T08:31:28+00:00

Zuul
zuul@review.opendev.org

2020-04-08T08:31:28+00:00

78b18030b5aaa42d7b438d73cb8d1170869ec758












Support for stateless security groups
2020-03-31T10:05:18+00:00

Tom Stappaerts
tom.stappaerts@nuagenetworks.net

2020-03-05T16:54:55+00:00

5e62411e5f6c5b68512d1f72470b4222199eb456

Add support for stateful attribute of security groups,
using --stateful and --no-stateful flag on security group.
This allows a user to create security groups with stateful
false.

Change-Id: Ifd20b5fc47fd0ea0bb5aeda84820dcc0fb1e8847
Blueprint: stateless-security-groups
Depends-On: https://review.opendev.org/711513/





Add support for stateful attribute of security groups,
using --stateful and --no-stateful flag on security group.
This allows a user to create security groups with stateful
false.

Change-Id: Ifd20b5fc47fd0ea0bb5aeda84820dcc0fb1e8847
Blueprint: stateless-security-groups
Depends-On: https://review.opendev.org/711513/