delta/openstack/python-openstackclient.git/openstackclient/tests/unit/network, branch 3.15.0 opendev.org: openstack/python-openstackclient Merge "neutron: add --mtu for create/set network" 2018-03-23T14:31:39+00:00 Zuul zuul@review.openstack.org 2018-03-23T14:31:39+00:00 29d4dd7a6150cb4cf5bfbb2ecbb82a404b5898b5 






Merge "Remove duplicated network attributes"
2018-03-23T14:10:42+00:00

Zuul
zuul@review.openstack.org

2018-03-23T14:10:42+00:00

350b545201bd6f5d3bc525ecef3a6ab1f7ced30e












neutron: add --mtu for create/set network
2018-03-15T13:50:59+00:00

Emilien Macchi
emilien@redhat.com

2018-03-15T12:21:41+00:00

18563b4132f794cc6612c2897795f96a31b565ae

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

Change-Id: I93d23581c7e8c84eaf9bb3b293360036f60f456b





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

Change-Id: I93d23581c7e8c84eaf9bb3b293360036f60f456b







Remove duplicated network attributes
2018-03-14T01:33:21+00:00

Dongcan Ye
hellochosen@gmail.com

2018-02-24T03:54:34+00:00

f6688986fc8e32976a84ce4a6e86c08e58a1718a

Change-Id: If77609d06e7d80c8da5111b8a30036b58fbfa187





Change-Id: If77609d06e7d80c8da5111b8a30036b58fbfa187







Merge "Add support for "--dns-domain" argument"
2018-02-24T10:59:41+00:00

Zuul
zuul@review.openstack.org

2018-02-24T10:59:41+00:00

1b5cab40b54ad2436c5d8b35369b0d802c75837d












Add support for "--dns-domain" argument
2018-02-23T20:30:37+00:00

Tytus Kurek
tytus.kurek@canonical.com

2017-09-04T06:14:37+00:00

4a9e84be994575146b30bd40a341d5686174eaad

This patchset implements support for "--dns-domain" argument to the
following commands: "openstack port create" / "openstack port set".

Change-Id: I4bb001054b00a969b74db3bb310e567033bf589b
Depends-On: https://review.openstack.org/#/c/500660/
Closes-Bug: #1714878
Partial-Bug: #1704769





This patchset implements support for "--dns-domain" argument to the
following commands: "openstack port create" / "openstack port set".

Change-Id: I4bb001054b00a969b74db3bb310e567033bf589b
Depends-On: https://review.openstack.org/#/c/500660/
Closes-Bug: #1714878
Partial-Bug: #1704769







Use find_ip from openstacksdk
2018-01-29T18:05:22+00:00

Monty Taylor
mordred@inaugust.com

2018-01-29T15:59:08+00:00

a742e47ecf86ef514d124ec5d10df197c01b253b

The find_ip from openstacksdk started being usable by OSC back in 0.9.15
but the local method never got replaced.

Change-Id: I18a334280e5f384f8bb96198cdad79c612a02290





The find_ip from openstacksdk started being usable by OSC back in 0.9.15
but the local method never got replaced.

Change-Id: I18a334280e5f384f8bb96198cdad79c612a02290







Merge "Add floating IP qos_policy actions"
2018-01-11T21:03:18+00:00

Zuul
zuul@review.openstack.org

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

8abf6bf5ba389a0ebbd202d69d0dbf8b64bb30d6












Add floating IP qos_policy actions
2018-01-11T18:10:11+00:00

LIU Yulong
i@liuyulong.me

2017-11-05T04:05:09+00:00

cf91d7a2f46b4a8546169a4836cc64476fce44d8

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





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







Allow ports filtering with device_id
2018-01-03T21:11:02+00:00

Hongbin Lu
hongbin.lu@huawei.com

2017-12-08T22:52:59+00:00

5fdd0730c88b7a3f65b728c0ea87bb34cbc1d9c4

Right now, if a neutron port is owned by a container powered by
Kuryr, there is no way to list and filter those ports because
OSC assumed a neutron port is owned by either a server or router.
This patch adds support for that by introducing an option '--device-id'
to the 'port list' command.

Change-Id: Ib1fd27e8d843a99fb02ccabd8a12a24ac27cec9c





Right now, if a neutron port is owned by a container powered by
Kuryr, there is no way to list and filter those ports because
OSC assumed a neutron port is owned by either a server or router.
This patch adds support for that by introducing an option '--device-id'
to the 'port list' command.

Change-Id: Ib1fd27e8d843a99fb02ccabd8a12a24ac27cec9c