I checked all the files in openstackclient/common
and fixed the missing i18n supprots.
Change-Id: Id7f76a24aae663f5832ef9bcf1bd5a6b7081af24
Partial-bug: #1574965
This patch adds functional tests for IP availability
Partially-Implements: blueprint neutron-ip-capacity
Change-Id: I1c1dc01801707fe8f0dc3c976e5d345d2b0db0ec
Moving the old release notes into the Reno releasenots tree broke
the embedded :doc: roles. Restore these using sphinx.ext.extlinks to
manage the URL to the OSC docs.
Add the following aliases:
* lpbug - generic Launchpad bug :lpbug:`123456`
* oscbp - OSC blueprints :oscbp:`Blue Print <bp-name>`
* oscdoc - OSC Docs :oscdoc:`Comamnd List <command-list>`
Change-Id: Iecfdd666d961c35f0ccb3b9f10df1d2620cb099f
Normally, we can unset multi properties but the "volume type unset"
command could not, because the action "append" was missed. So I add
it and also fix the unit test and doc in this patch.
Change-Id: I20470f2b7bb2a8d7f292cea498826669c3418c77
Unit test cases don't cover compute "server set/unset" commands,
the patch add some test cases for them.
Change-Id: I440c32968bd41b948352a9764a37c9af3e68803d
OSC does not support to list volume transfer from one user
to other user.
This patch will provide support for listning volume transfer
requests.
Closes-Bug:#1554886
Implements: bp cinder-command-support
Change-Id: Ie659bc39cb1d1e931cca7a40b2f126a067ee484c
set/unset commands should ends up normally instead of
logging an error when nothing is specified to modify.
The main reason is: When nothing is specified, the
command sets/unsets nothing, which is a normal behavior,
and ends up normally. No API call fails. No error happens.
Change-Id: Ib03a512650e5da90aa1ef38019772448383d0d33
Partial-bug: #1588588
Translated messages should not be combined with orther literal
strings to create partially translated message.
Although this change is very small, but this is the only one in
the directory VOLUME.
Change-Id: If798aacde9d5d5e8ac2edd49e75099ec255c858e
In test_flavor_set_no_project(), we aimed to test a
situation like this: User specifies "--project" option,
but didn't specifies the project name or ID.
But in the source code, it becomes "--project ''".
The test could past because if project and property
are both None, the command will raise an exception.
Change-Id: I39567306debb901e8bad420fa2492f1b207efddc
The --enable option on commands is ignored when the arguments are parsed.
This is related to the --enable-beta-commands option. Renaming the option
to --os-beta-command fixes the problem.
There's no need to handle backwards compatibility for the option name
change because there hasn't been an OSC release yet with beta commands.
Change-Id: I0327ba8a2058858a83e9a42e231470ed733cc834
Closes-Bug: #1588384
