The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Change-Id: I7a43ff6d91bad919dcaa450e66ef492a1d3a03ef
Added command support for downloading csar vnf package contents.
Change-Id: I6371ebdf0dd9d127ca88bcd721a31036d11ea5fc
Implements: bp enhance-vnf-package-support-part1
Added command support for fetching VNFD of the vnf package.
Please see results here:-
http://paste.openstack.org/show/789212/
Change-Id: Ifa15ddf7ff306ed2705cf7a170d9e9f512491fba
Implements: bp enhance-vnf-package-support-part1
Added command support for updating vnf package.
Please see results here:-
http://paste.openstack.org/show/788463
Change-Id: I0cd32d531db569b7013332fcfaaaefde403e7aed
Implements: bp enhance-vnf-package-support-part1
Added a new command ``openstack vnflcm heal`` to heal vnf
instance.
Blueprint: support-etsi-nfv-specs
Change-Id: I31165e1def0a53a56e1fcefd1877630712bfab5e
Added a new command ``openstack vnflcm list`` to list the vnf instances.
Blueprint: support-etsi-nfv-specs
Change-Id: I4ef7ac0dd4d4744c74ceb13df6b4438a090ac72a
Added a new command ``openstack vnflcm create`` to create a new vnf.
Blueprint: support-etsi-nfv-specs
Change-Id: Ia90955df6ac141661c3d58e4de4e098c4cb51aab
assertItemsEqual was removed from Python's unittest.TestCase in
Python 3.3 [1][2]. We have been able to use them since then, because
testtools required unittest2, which still included it. With testtools
removing Python 2.7 support [3][4], we will lose support for
assertItemsEqual, so we should switch to use assertCountEqual.
[1] - https://bugs.python.org/issue17866
[2] - https://hg.python.org/cpython/rev/d9921cb6e3cd
[3] - testing-cabal/testtools#286
[4] - testing-cabal/testtools#277
Change-Id: I1d77929d26af29e5d060eefdac85a5da2dd145d6
When you pass non-existing vnf package uuid to ``vnf package upload``
command as shown below, it doesn't show user-friendly message as it's
shown in case ``vnf package show`` command.
$openstack vnf package upload --path sample_vnf_pkg.zip dummy-id
"404-tackerFault"
This patch fixes this issue and now it will output below error message:
$openstack vnf package upload --path sample_vnf_pkg.zip dummy-id
Can not find requested vnf package: dummy-id
Change-Id: I84de0140463d6bd834d3bcc22f6a6cea1fef9130
Closes-Bug: #1799683
Added support vnf package upload command and their unit test cases.
Please see result here.
http://paste.openstack.org/show/766299/
Change-Id: I88da4e209413a00d52c73fc83983ed2f5fd273c6
Implements: bp tosca-csar-mgmt-driver
Added support for below three commands and their unit test cases.
1.vnf package list
2.vnf package show
3.vnf package delete
Please see results here
http://paste.openstack.org/show/774848/
Change-Id: I47e3e99a42aa36ab286fa01802999deb964a168f
Implements: bp tosca-csar-mgmt-driver
Added support vnf package create command and their unit test cases.
Please see the results here:
http://paste.openstack.org/show/775422/
Change-Id: Idf59847aaf33e360dae696eae819d217ae63570f
Implements: bp tosca-csar-mgmt-driver
Current tacker client requires us to mention ssl_ca_cert
and set it to None if we don't want to use ssl cert. This
patch along with another patch on the tacker server side
will make ssl_ca_cert a truly optional config. And, only
the correct ssl_ca_cert will be able to authenticate.
Tacker Server changes: https://review.openstack.org/#/c/546580/
Change-Id: Ic87fe3382e100183c685c3b34768a5a5de889982
Currently, Tacker can not communicate with VIM endpoints that
use SSL. This patch will add cert_verify parameter, user can
set "cert_verify" to False (default value is True) to disable
verifying SSL.
Change-Id: I0af2a0f91ecda2a63cf6233d780e1dd7c064513c
This patch will add "--vnffgd-template" to vnffg-update command to support
update VNFFG from file. User can run:
tacker vnffg-update --vnffgd-template <vnffgd-file-name> vnffg_name
to update the existing VNFFG.
Partially Implements: blueprint update-vnffg
Change-Id: Ief0469d870530693798f798ecd2f52782318795b
This patch will add changes to support Kubernetes as VIM feature
in python-tackerclient.
After this change, user have to provide VIM type in VIM config file
when creating or updating VIM. The default VIM type is openstack.
Partially Implements: blueprint kubernetes-as-vim
Change-Id: I1b1610cb89a78a2a8fe134265b83dd469d72fdcd
Missed this with create fix:
Ide2aeab73b1dd88beb6e491e6b07cdee9fb7e48a
Change-Id: Ia983150de322d1ffbd7eeedc2048c19c095afefb
Signed-off-by: Tim Rozet <trozet@redhat.com>
Bug where 'True'/'False' strings were being passed in REST to Tacker
service which would end up throwing an exception because the DB type for
symmetrical is boolean/small int. This converts it to boolean in the
client.
Closes-Bug: 1711550
Change-Id: Ide2aeab73b1dd88beb6e491e6b07cdee9fb7e48a
Signed-off-by: Tim Rozet <trozet@redhat.com>
Currently, Tacker only support creating VNFFG and NS from VNFFG descriptor
and NS descriptor. This patch will support creating directy VNFFG and NS
from template file without initiating VNFFG and NS descriptors before.
Change-Id: If7554287bbe1184d9b84609f81e53f17d7b5fdfe
Closes-bug: #1681032
Make auth_creds display the user specified credentials
which are project_name and username. Normally
vim configuration yaml file has no project_id and user_id
Change-Id: I987ad7bda04b0a161c56284f77964063490a18e0
Closes-Bug: #1629169
use mock instead of mox
Co-Authored-By: Trinath Somanchi <trinanth.somachi@nxp.com>
Change-Id: I9e5327a4e4e6cba220670b096f718e7343fd43dc
Closes-Bug: #1572706
it caused No handlers could be found for logger "tackerclient.shell"
This reverts commit af2f0f031f.
Change-Id: I8556dbf7ea45a268daa900e00c5334f11cd106d0
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
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
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
This patch removes passing infra and mgmt driver as part of VNFD body from
client and API.
Change-Id: I4684e69b8993e6c35503317503dd73e2c13f44dd
Partial-Bug: #1630936
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
