tackerclient is currently using python logging module to
implement logging functionality.
This patch made a switch to oslo.log(logging for openstack projects)
Reference:-
http://docs.openstack.org/developer/oslo.log
Change-Id: Iecab180e605c788bb820c7a628781abf9a4918ea
Closes-Bug: #1656167
When a single vnfd is deleted, the following success message is delivered.
$> tacker vnfd-delete cirros-vnfd-multi-vdu
All vnfd(s) deleted successfully
The above success message has to modified to
" All specified %(resource)s(s) %(msg)s successfully? "
Change-Id: I48443622b718a1d6a1476f53c6378b67ce0d82e4
Closes-Bug: #1672302
Starting from Ocata tacker payloads will only accept
YAML dict for config and param payload values. Hence
remove the warning when something other than YAML dict
is received by the client. Such a CLI input is no longer
make sense. So, starting Ocata deprecate all direct
YAML input and remove it in Pike.
Change-Id: I03f3ac405e92d7e9fa69fd2b2761c243456fd7e8
Partial-Bug: 1656416
Allows creating VNF from the VNFD template directly without the need of
VNFD being stored in Tacker VNFD catalog.
Change-Id: I719237dd04dd7fe13fb7e7964402d7074679b2d6
Implements: blueprint vnf-inline-template
From Mitaka version, Tacker supports TOSCA based VNFD templates.
Legacy templates were deprecated in newton. Server side already
commited in https://review.openstack.org/#/c/382786/.
Removing related checks in client side now.
Implements: blueprint deprecate-legacy-template-dsl
Change-Id: I60b683c6d63b6976d438ff6130d16ddbf0656940
events-list command's help text for some options does not follow common
format. Also, *-events-list commands have similar issues. This patch
fixes help texts for these commands to make them clearer for users.
Change-Id: Icd85d13fee437bf0f83979eb6625377b38ce39ad
Closes-bug: #1628769
Unit tests are not testing the behavior of command-line client
code properly since mox was replaced with mock in [1].
[1] https://review.openstack.org/#/c/313165/
assert_called_once_with() should be called after the target
call of the patched method.
Change-Id: I99873e9cb1d75d1fa2e41c02b9f87dfa4f9ef1f7
Partial-Bug: #1572706
For logging the exception message: e.message has been
deprecated. The preferred way is to call str(e).
more details:
https://www.python.org/dev/peps/pep-0352/
Change-Id: Ic22fbd37376843f714d2c1669d2cdc25a3569225
Adding constraints support to libraries is slightly more complex than
services as the libraries themselves are listed in upper-constraints.txt
which leads to errors that you can't install a specific version and a
constrained version.
This change adds constraints support by also adding a helper script to
edit the constraints to remove python-tackerclient.
Change-Id: Ibf4801a72637840cc5f908c4938c5d95077ef9d7
This patch removes passing infra and mgmt driver as part of VNFD body from
client and API.
Change-Id: I4684e69b8993e6c35503317503dd73e2c13f44dd
Partial-Bug: #1630936
Help msg in tacker project should support oslo.i18n. But
tests directory faces developer, So it needn't support oslo.i18n.
Co-Authored-By: ShuYingya<yingya.shu@easystack.cn>
Change-Id: I60106b106cfd77b46663ff35a2735cfa5ea158f0
In Python 3 __ne__ by default delegates to __eq__ and inverts the
result, but in Python 2 they urge you to define __ne__ when you define
__eq__ for it to work properly [1]. There are no implied relationships
among the comparison operators. The truth of x==y does not imply that
x!=y is false. Accordingly, when defining __eq__(), one should also
define __ne__() so that the operators will behave as expected.
[1]https://docs.python.org/2/reference/datamodel.html#object.__ne__
Change-Id: I6adceadb6e3749e34cf847654f28a3b6eea832fd
Tacker CLI does not support updating name and description of VIM.
This patch introduces --name and --description options to vim-update.
Also, existing --is-default option's behavior can be improved.
Currently is_default attribute will be set to False when --is-default
is ommited, and will be set to True when --is-default is specified.
So even a user, who wants to update attributes other than is_default,
needs to be aware of current is_default setting. This patch will make
the behavior of --is-default option clearer like below:
1.When --is-default True is specified, it'll be set to True.
2.When --is-default False is specified, it'll be set to False.
3.When --is-default is ommited, it will stay as-is.
In addition, --config-file should be a required option because both
server and client expect it to be given when updating VIM.
Change-Id: Ic19fb6b0efb48bc3486f94836be4f2ff35f8c84b
Partial-Bug: 1637360
