delta/openstack/python-openstackclient.git/openstackclient, branch queens-em

Handle multiple ports in AddFloatingIP

2018-11-08T20:44:40+00:00

AddFloatingIP refers to an old nova proxy API to neutron that was
deprecated in nova. The neutron API for floating IP associate requires
a port to be specified. Currently, the code is selecting the first port
if the server has multiple ports. But, an attempt to associate the
first port with a floating IP can fail if the first port is not on a
network that is attached to an external gateway.

In order to make the command work better for users who have a server
with multiple ports, we can:

  1. Select the port corresponding to the fixed_ip_address, if one was
     specified

  2. Try to associate the floating IP with each port until one of the
     attempts succeeds, else re-raise the last exception.
     (404 ExternalGatewayForFloatingIPNotFound from neutron)

This also fixes incorrect FakeFloatingIP attributes that were being set
in the TestServerAddFloatingIPNetwork unit tests, which were causing
the tests to use None as parsed args for ip-address and
--fixed-ip-address and thus bypassing code in the
'if parsed_args.fixed_ip_address:' block.

Task: 27800
Story: 2004263

Change-Id: I11fbcebf6b00f12a030b000c84dcf1d6b5e86250
(cherry picked from commit 013c9a4f3a44cb0b81fc7affe9b933e701cb5dba)
(cherry picked from commit e09c358e7b35ac938595aad90c5c42dfe402a42a)

Merge "Default --nic to 'auto' if creating a server with >= 2.37" into stable/queens

2018-11-02T18:59:27+00:00

Merge "Allow endpoint filtering on both project and project-domain" into stable/queens

2018-11-02T18:16:01+00:00

Default --nic to 'auto' if creating a server with >= 2.37

2018-10-25T20:53:42+00:00

Compute API version >= 2.37 requires a 'networks' value in
the server create request. The novaclient CLI defaults this
to 'auto' if not specified, but the novaclient ServerManager.create
python API binding code does not, as it wants clients to be explicit.

For the purposes of the OSC CLI, we should follow suit and if the
user is requesting OS_COMPUTE_API_VERSION>=2.37 without specific
nics, we should just default to 'auto'.

Change-Id: Ib760c55e31209223338a4086ff1f4fee88dc6959
Closes-Bug: #1750395
(cherry picked from commit 1008544882fbdae16b045abca05cf3e2e8a14787)
(cherry picked from commit 4944d4eaa9aaeffdee358680550ac7d7f0c6e8d8)

Don't sent disk_over_commit if nova api > 2.24

2018-10-25T20:53:26+00:00

In API microversion 2.25 Nova removed the disk_over_commit parameter
to the live migration server action. This patch makes sure that we
don't include it in our request if we're running with 2.25 or higher.

Story: #2002963
Task: #22966
Change-Id: I1bbdd33be96d82422a05982508e370237c3560f3
(cherry picked from commit d6121782d3aa6a95b883220b27a154e641b61f7f)

Allow endpoint filtering on both project and project-domain

2018-10-15T09:32:31+00:00

The --project and --project-domain flags are currently mutually
exclusive for listing endpoints, however the --project-domain argument
is supposed to help with filtering projects with colliding names. They
should be allowed together.

Story: 2004018
Task: 27006
Change-Id: I7340e01f509e3515f07cb46f175fb603f1ce8b67
(cherry picked from commit 91a2d888625488da3f65ad372b4248e9747b9a3e)

Merge "Fix 'project purge' deleting wrong project's servers and volumes" into stable/queens

2018-10-03T01:30:11+00:00

Fix 'project purge' deleting wrong project's servers and volumes

2018-09-17T10:46:36+00:00

Project purge would delete the servers and volumes for the project the
user is currently authenticated for, regardless of the --project flag.

Note: This change means that no server at all will be deleted if the
logged in user doesn't have the get_all_tenants permission set in the
Nova policy (default: admin_api). This doesn't appear to be an issue
with Cinder as the default rule appears to be admin_or_owner.

Change-Id: If1c54e24e1482438b81c3c32fd5fc9fdd7a7be04
Story: 1747988
Task: 26495
(cherry picked from commit 1b66ad9067cc404ebfdc8569822d226d5bffddd6)

Do not require port argument when updating floating IP

2018-08-21T14:24:51+00:00

When setting floating ip other properties, port argument is
force to use.
The patch modifies the command, when setting floating ip other
properties, like tags, no need port argument.

Change-Id: I908712c8913f32d3dd5fdfefe7347277d72f66de
Story: 1751431
Task: 13865
Closes-Bug: #1778666
(cherry picked from commit 402c9a21b347509520be206e28ee7d0ef4004b92)
Small changes due to changes in tag handling and how unit tests are
working.
Conflicts:
	doc/source/cli/command-objects/floating-ip.rst
	openstackclient/network/v2/floating_ip.py
	openstackclient/tests/unit/network/v2/test_floating_ip_network.py

Prevent "server migrate --wait" from hanging

2018-06-05T13:20:35+00:00

Migrate uses the same mechanism in the backend than Resize and so the
steps and step names are similar. Currently when using the --wait
option with 'migrate', we wait forever because the status won't get to
active until the user performs an action. This makes it return on
verify_resize status just like 'resize' does, so that the user can
perform the next manual step.

Change-Id: Ie1aeac52506bc8801f88fd6a6eb4f6094cf20050
Story: 2001994
Task: 19620
(cherry picked from commit de9a6fc0700d821f9fca6bf347407eccd87f0064)