- Fix create_vnffgd cannot get 'description' and 'name'
from TOSCA yaml file
- Delete redundant 'description' line in vnffgd template
file following the standard in vnffg_usage_guide.rst
Change-Id: I9c384678058c5e27239e9afc8cc2ae1de01ff750
Closes-Bug: #1751433
Currently, when a VNFFG is created, Tacker also create port-pair,
port-pair-group, port-chain and flow-classifier. There are no
reusing ability in this approach.
This patch will check the port-id of a VNF is using in other VNFFG
or not. If it is used in a VNFFG, the existing port-pair-group will
be added to the new port-chain.
Therefore, we can create 2 VNFFGs that can go through one VNF.
This patch also clean up network resource such as port pair, port
pair group and flow classifier if there are failures.
Change-Id: I648693103dd7eab7a4b10cde89f11766a9232e8d
Closes-Bug: #1746721
If the mgmt_driver is checked in the first place,
then there is no problem when the VNF is created.
Change-Id: I6a37cf93f4c7c2bbfab7ce68ea65a34f11407633
Closes-Bug: #1611228
Until now there was no implementation of updating an existing
VNFFG with the use of the 'vnffgd-template' parameter which is
introduced in the Tacker client side. This patch addresses exactly
that.
Implements: blueprint update-vnffg
Change-Id: I8fa748a76fd479649be5dd7a19244f7143849687
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
The functinality of naming the classifiers which are
created through a vnffgd template is essential so the user
can identify somehow the classifiers that he created for a chain.
In addition to that the classifiers' names would be an important
tool in subsequent patches where we will use them to update the ACL
of an existing classifier though the vnffgd template. We are going to
use the name to identify which classifier's ACL the user wants to
update.
Change-Id: Ia586061c578a99662d49ad284d1ff313c350e1f3
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
Although tacker client side supports the update of the VNFs which
are currently used in an existing VNFFG this functionality is not
implemented at the Tacker server side.
Through this patch we are trying to address exactly that problem.
Also this patch is the first step for the implementation of this:
Implements: blueprint update-vnffg
Change-Id: I147e9f8a52f3e307767cd855492eb9bb5867cf29
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
Tacker uses the class path+file name+uuid as stack names to
uniquely identify the stacks for vnf create and vnf respawn workflow.
Tacker now mandates VNF names to be provided in API layer and will be
made unique. It is useful to base stack names based on vnf names for
debugging purposes. This affects the naming of nova instances as well.
Change-Id: If043ad8c6c356f3fa1d2f5648d3d861ff5006602
Closes-Bug: #1590215
Develop a Zabbix plugin in Tacker VNF manager to monitor application level
parameters that can't be supported by current Tacker monitoring driver
Change-Id: I25e871b8e8ddfb49a1f3f22e78c1ea8ba9835d74
Implements: blueprint zabbix-plugin
This patch add kubernetes_driver in vim nfvo and kubernetes_utils to support
CRUD Kubernetes cluster VIM (register, deregister, delete and update).
Partially Implements: blueprint kubernetes-as-vim
Change-Id: Ib1bf4d78ca4796c4e0297bca6fc7e9f004078242
If you on-board a VNF to tacker and try to on-board it again tacker
gives 500 InternalServerError. The response message user get is
correct but the response code returned is incorrect which is 500.
message returned:
"vnfd already exist with given ['tenant_id', 'name', 'deleted_at']"
The type of a TackerError returned is 'DuplicateEntity' which has
500 response code as it is derived from 'TackerException'.
This patch changes the response code from 500 to 409 as this case
is of HTTPConflict.
This affects to below mentioned API's:
* POST /v1.0/vnfds
* POST /v1.0/vnfs
* POST /v1.0/vims
* POST /v1.0/nsds
* POST /v1.0/nss
NOTE:
There are no existing unit test cases written for such API's.
Closes-Bug: #1734316
Change-Id: I7f63ab5f9612c2f32f0f11397ad0d6e3cee2f8d6
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is
entirely due to the current convention of pulling in the version
information. Release notes should not need installation in order
to build, so this unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html .
Change-Id: I32dd5453b4d05e46cfd1cddfc5d2f885ce53da83
This patch adds support to attach volumes to VDU.
This patch does not deal with boot from volume case.
Change-Id: I4bee80610eaa4e2ec8a1ccb2a5d36fb723a09806
Implements: persistent-block-storage
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: I4e8ec8405a291300aa6749cf814ad582786c285d
Closes-bug: #1681032
As part of the docs migration work[0] for Pike we need to switch to use
the openstackdocstheme.
[0]https://review.openstack.org/#/c/472275/
Change-Id: Idf8ddcb0c76c4d211881e6ccb1bef82efffdbb70
1. Add new option 'use_barbican' in config file [vim_keys] section,
default value is False for Pike.
2. Use fernet to encrypt vim password, and save the fernet key into
barbican as a secret.
3. Add new fields 'key_type', 'secret_uuid' into VimAuth.auth_cred
json string. secret_uuid is masked in vim-show or vim-list response.
4. Set the vim's default 'shared' value to False,
vim can only be used by who created it.
5. Add a devref to show how to test.
6. Add a release note.
Implements: blueprint encryption-with-barbican
Partial-bug: #1667652
Change-Id: I5c779041df5a08a361b9aaefac7d241369732551
