delta/openstack/python-openstackclient.git/doc, branch stable/queens

Document 2.53 behavior for compute service list/delete

2019-09-25T16:22:58+00:00

With compute API microversion 2.53, nova-compute services
can only be deleted with the ID as a UUID to uniquely identify
the service in a multi-cell deployment. This documents that for
the "compute service delete " argument. The description
of the "compute service list" command is also updated to mention
that the ID can be retrieved as a UUID using 2.53 or greater.

Change-Id: If7d4a27c0aaef588bcd77dd9edddec1e535fbf31
Story: 2005349
Task: 30302
(cherry picked from commit 1557afb554e908e097abd39081891ea78083e20e)
(cherry picked from commit 111d6a9b23d8c6b9bcce437039ff49536f0b5dd1)
(cherry picked from commit 72922ae1a1b842b1a5058377f8033cbf09086b4c)

Stable branch combination fix

2019-05-16T21:00:59+00:00

We have two dueling problems in the stable branches that have to be
fixed at the same time:

* bandit 1.6.0
* sphinx 2.0

This is a squash of the two cherry-picks from master:

----------
Blacklist Bandit 1.6.0 due to directory exclusion bug

Bandit 1.6.0 introduces a regression[0] with the -x option, a fix
is expected to be included in 1.6.1 soon.

[0] https://github.com/PyCQA/bandit/issues/488
[1] https://github.com/PyCQA/bandit/pull/489

Signed-off-by: Dean Troyer 
(cherry picked from commit 6385d64237c9973dd4c7dd53efb6664ea2c719da)

----------

Update sphinx requirement.

Sphinx 2.0 no longer works on python 2.7, start cappingit there as well.

(cherry picked from commit f1791179768115b6d074f70f9a8695f9c1e0b9f5)

Change-Id: I0076645d9e1a2429efce39f51ceea679fa6c13cb

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

neutron: add --mtu for create/set network

2018-03-26T14:26:53+00:00

Support Neutron network mtu configuration with a new argument, --mtu
that allows CLI users to set MTU for Neutron networks.

Change-Id: I93d23581c7e8c84eaf9bb3b293360036f60f456b
(cherry picked from commit 18563b4132f794cc6612c2897795f96a31b565ae)

Updated from global requirements

2018-01-24T01:31:48+00:00

Change-Id: I7b712b41e633f7e3dc40749b5a55706cb32fecee

Merge "Fix indentation in authentication.rst"

2018-01-18T18:53:47+00:00

Updated from global requirements

2018-01-18T03:30:37+00:00

Change-Id: Ic5715c21e19d92c8f3d85091bfa41c28bb271c42

Fix indentation in authentication.rst

2018-01-17T17:33:33+00:00

Fix indentation in doc/source/cli/authentication.rst

Change-Id: I7d408e9d27a384903680303219f2578be0e2937e

Merge "Add floating IP qos_policy actions"

2018-01-11T21:03:18+00:00

Add floating IP qos_policy actions

2018-01-11T18:10:11+00:00

Now we can associate a qos policy to the floating IP, and
dissociate it. The commands are:

  $ openstack floating ip create --qos-policy ...
  $ openstack floating ip set --qos-policy ...
  $ openstack floating ip set --no-qos-policy ...
  $ openstack floating ip unset --qos-policy

These commands are based on the neutron change:
I4efe9e49d268dffeb3df4de4ea1780152218633b

Partially-Implements blueprint: floating-ip-rate-limit

Change-Id: I932b32f78cc5a2b53926feaec1a0b392cf7e8b57