"Python 3.3 support is being dropped since OpenStack Liberty."
written in following URL.
https://wiki.openstack.org/wiki/Python3
And already the infra team and the oslo team are dropping py33
support from their projects.
Since we rely on oslo for a lot of our work, and depend on infra
for our CI, we should drop py33 support too.
Change-Id: Ie7cd91f72b6bc80723286187ebe5d0bcb769d7d2
Closes-Bug: #1526170
As of mitaka, the infra team won't have the resources available to
reasonably test py26, also the oslo team is dropping py26 support
from their libraries. sine we rely on oslo for a lot of our work,
and depend on infra for our CI, we should drop py26 support too.
Closes-Bug: 1519510
Change-Id: Ie8dc40df5fddce298f31f7a3d5436493b9b090bb
This is important because if we install tacker along with
other openstack components, this inconsistency will break
system.
Due to the upgrade of hacking, current codes violate many
new rules. These violations will be fixed in follow up
patches.
Author: yong sheng gong <gong.yongsheng@99cloud.net>
Change-Id: Ib30d31ca804aebf43c02eb8247c718ab00629f6f
Closes-bug: 1516045
When deleting a vnfd using vnfd-name as argument it returns
'descripton' string, if db has multiple entries with same name.
This patch fix this problem by checking the existence of key
'description' in 'vnfd' dict.
Change-Id: I3c350ec1b563b1933df93106717f373afc368146
Closes-Bug: #1508174
Use 'unicode_escape' to escape YAML while configuring
VDU at the time of vnf-create or vnf-update using --config
flag
Change-Id: Ia4543b9437f28b4e6312bbd2fab9a7c47dd9f610
Partial-Bug: #1501079
python-tackerclient has been modified to invoke Tacker MANO API
directly for VNF and VNFD resource requests. The current wrapper
implementation of invoking servicevm REST APIs has been removed.
Change-Id: I447fd971d97987911d5e85abafc94a24599ac209
Implements: blueprint tacker-api-mano
Depends-On: I9dffd4bee25b1f49aea7478f2bd779cf0f6dfb49
This commit adds code to ensure that the values supplied by end
user for 'config' argument is not dropped in the create_vnf()
method. This scenario occurs in the case where end user supplies
values for both the 'config' and 'param-file' arguments.
Change-Id: Ied565217c2571283330f8f8cf62f76e2942826ba
Closes-Bug: #1493671
This commit adds code to support onboarding a VNFD template that
supports parameterized input.At VNF deploy time, this feature
allows to specify a yaml file with values to be substituted for
the parameters specified in the VNFD template.
Change-Id: If55229fde092d1d760870d0280aec0bcd5cb9c6f
Closes-bug: #1484227
Depends-On: I72b6e8da8826a3c80c1a73aa37f912fc9ec3e291
* The vnf and vnfd create output text contains the "attributes"
field which is so large that it makes it impossible to format
the output text so it is readable.
* Modified the CreateCommand class to provide the ability to
remove specified fields from the output of the create command
* Modified the CreateVNF and CreateVNFD classes to specify that
the "attributes" field should be removed from the output of
the create command.
Change-Id: I7563175a2cec3e3e9528b66153354aec982a14b4
Closes-Bug: 1474975
* Added support for vnfd-name in place of the vnfd-id when
creating a VNF. The vnfd-id and vnfd-name are now mutually
exclusive parameters but one of them is required to be
specified. An appropriate error will print if neither is
provided.
* If the vnfd-name is specified the code will retrieve the
associated vnfd-id and pass it to the create method as if it
had been specified on the command line.
Change-Id: Ia62a33ee821e0fc89a167755aa55beac94d36c57
Closes-Bug: 1474983
