delta/openstack/python-openstackclient.git/doc/source/command-objects, branch 3.10.0 opendev.org: openstack/python-openstackclient Fix Nova-net netowrk commands 2017-04-27T20:36:00+00:00 Dean Troyer dtroyer@gmail.com 2017-04-27T15:26:07+00:00 589a65c3fee2d61a13eaa53785afd3525d9ae80d In cleaning up functional tests for nova-net, I discovered some problems in network create: * --subnet option is required in network create command * Switch API to use /os-networks rather than /os-tenant-networks as this is what we were actually using via novaclient * Fix functional tests for nova-net * Normalize some private function names in network/v2/network.py Change-Id: I426b864406756d58d140575a3a45ee9aee67ce84 
In cleaning up functional tests for nova-net, I discovered some
problems in network create:
* --subnet option is required in network create command
* Switch API to use /os-networks rather than /os-tenant-networks as this
  is what we were actually using via novaclient
* Fix functional tests for nova-net
* Normalize some private function names in network/v2/network.py

Change-Id: I426b864406756d58d140575a3a45ee9aee67ce84
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
Merge "Add --network and --port to server create" 2017-04-25T13:54:46+00:00 Jenkins jenkins@review.openstack.org 2017-04-25T13:54:46+00:00 7977f7df1887de570e17ed37bbb7da7b226e303d 






Merge "Allow override of distributed router flag"
2017-04-17T15:18:20+00:00

Jenkins
jenkins@review.openstack.org

2017-04-17T15:18:20+00:00

62d71aa2435b2257670480dce73d2192652bb14d












Add --network and --port to server create
2017-04-07T14:36:18+00:00

David Rabel
rabel@b1-systems.de

2017-03-13T14:16:48+00:00

8549071363805a9eef815dd2429b6b860db11a2c

--nic option is quite unhandy. It is better to have
two seperate options --network and --port to add a
network to a new server.

Change-Id: I523abdc83ca2dd4c5dd3871f8f109c2bf57c2e02
Closes-Bug: #1612898





--nic option is quite unhandy. It is better to have
two seperate options --network and --port to add a
network to a new server.

Change-Id: I523abdc83ca2dd4c5dd3871f8f109c2bf57c2e02
Closes-Bug: #1612898







Allow override of distributed router flag
2017-04-06T14:37:14+00:00

venkata anil
anilvenkata@redhat.com

2017-02-14T05:05:20+00:00

fe59e339ae6dd6a5e9075773fb5c2a0fea9c2e53

When router_distributed=True is set in neutron.conf,
user can't override this and create a centralized router
through openstack client. Openstack client allows modifying
routers from distributed to centralized after creation but
not supporting centralized flag during creation. We allow
centralized and distributed flags during router creation
with this change.

Closes-bug: #1664255
Change-Id: I75f72ca695338ad8c381cfa89fbb9d8e61ee7bc5





When router_distributed=True is set in neutron.conf,
user can't override this and create a centralized router
through openstack client. Openstack client allows modifying
routers from distributed to centralized after creation but
not supporting centralized flag during creation. We allow
centralized and distributed flags during router creation
with this change.

Closes-bug: #1664255
Change-Id: I75f72ca695338ad8c381cfa89fbb9d8e61ee7bc5







Merge ""floating ip set/unset port" for OSC"
2017-04-06T01:55:24+00:00

Jenkins
jenkins@review.openstack.org

2017-04-06T01:55:24+00:00

80726b1340631b2b7d1c962d22a122e0c36486ac












Merge "Add "qos-policy" option to "port create" & "port set""
2017-04-06T01:43:44+00:00

Jenkins
jenkins@review.openstack.org

2017-04-06T01:43:44+00:00

8983373e52e49ee8d6fa603f689957a915191759












Merge "Enable to create legacy router"
2017-04-05T17:00:49+00:00

Jenkins
jenkins@review.openstack.org

2017-04-05T17:00:49+00:00

27f96a3a7a5515ff621300a917872b5ec62f41de












"floating ip set/unset port" for OSC
2017-04-05T16:12:40+00:00

Sindhu Devale
sindhu.devale@intel.com

2016-10-06T15:01:59+00:00

763c8c5670f238920398165e670592e006213f32

Implements Neutron feature of floating ip associate/disassociate
into OpenStack Client.

Previously, network.find_ip() function only supported to
search floating ip by UUID. Hence, _find_floating_ip()
function is used in floating_ip.py, to search fip both by UUID
and ip_address. [1] adds the ability to find fip object using both UUID
and ip_address. This functionality however, won't be available until
the SDK is released. Hence, we continue to use _find_floating_ip()
method, which was cleaned up by [2] to remove the use of ip_cache.
Once, the SDK is released, we will remove all the usage of
_find_floating_ip() method and instead only use network.find_ip().

[1] https://review.openstack.org/#/c/449879/2
[2] https://review.openstack.org/#/c/447938/

Change-Id: I6c5222287c46ca42365917d2deae70bdb626347
Co-Authored-By: Reedip<reedip.banerjee@nectechnologies.in>
Co-Authored-By: RuiChen<chenrui.momo@gmail.com>
Closes-Bug: #1560297





Implements Neutron feature of floating ip associate/disassociate
into OpenStack Client.

Previously, network.find_ip() function only supported to
search floating ip by UUID. Hence, _find_floating_ip()
function is used in floating_ip.py, to search fip both by UUID
and ip_address. [1] adds the ability to find fip object using both UUID
and ip_address. This functionality however, won't be available until
the SDK is released. Hence, we continue to use _find_floating_ip()
method, which was cleaned up by [2] to remove the use of ip_cache.
Once, the SDK is released, we will remove all the usage of
_find_floating_ip() method and instead only use network.find_ip().

[1] https://review.openstack.org/#/c/449879/2
[2] https://review.openstack.org/#/c/447938/

Change-Id: I6c5222287c46ca42365917d2deae70bdb626347
Co-Authored-By: Reedip<reedip.banerjee@nectechnologies.in>
Co-Authored-By: RuiChen<chenrui.momo@gmail.com>
Closes-Bug: #1560297