This patch updates the install instruction of Tacker in Devstack
with two modes, i.e., all-in-one mode and standalone mode.
It also removes some redundant configurations in local.conf.example
which already had in the Devstack settings.
Change-Id: I6d8d1bbe54b1a382fcbf83a1aef1fa389c43c1fc
This patch fix these:
- If nested_resource_name is 'SP1_res.yaml' it will create
a loop in heat translator and vnf creation will fail. This
is a bug of heat translator and this patch is to bypass
the loop hole by using a different name than 'SP1_res.yaml'.
- Incorrect syntax:
...
translate_to_yaml_files_dict() takes exactly 2 arguments (3 given)
...
Co-Authored-By: Cong Phuoc Hoang <hoangphuocbk2.07@gmail.com>
Co-Authored-By: yong sheng gong <gong.yongsheng@99cloud.net>
Co-Authored-By: Trinh Nguyen <dangtrinhnt@gmail.com>
Change-Id: I60dc0a6d443598264c29fde8a3959d4bd7fba904
Closes-bug: #1753645
devstack is using apache as a ssl proxy for wsgi api service.
Current tacker does not support it. We remove it for the time being
This patch also skip scale unit tests which failed due to
heat translator change. The unit test will be enabled at
another patch.
Change-Id: If767d05a0241888663f0ff21282cebfd256efb49
Closes-bug: 1755664
According to SFC RFC standard, the chains should be decoupled
from classifiers.
In Networking-sfc the chains and classifiers are completely
decoupled. This patch lets user can do it by allow creating
VNFFG with no flow-classifier.
User can use "tosca-vnffgd-no-classifier-sample.yaml" to create
VNFFG with no flow-classifier. User also have the ability to
add flow-classifiers through updating VNFFG with
"tosca-vnffgd-sample.yaml" in vnffgd tosca templates folder.
This patch only support Forwarding path with type
"tosca.nodes.nfv.FP.TackerV2". Tacker also support altering the
direction of the traffic in forwarding path, update new
forwarding path, add, remove and update flow-classifers though
updating VNFFG.
For more information: https://review.openstack.org/#/c/531817
Change-Id: Ice2f0f03f7a90f4fefdee751283ff26b9c037d87
Closes-Bug: #1745818
While deploying a vnf with autoscaling, heat translator failed with
premission denied error. This issue occured because [1] opening file
in root dir (i.e. '/'), due to which it giving permission denied.
Fixing it by setting current working dir as '/temp'
[1]: https://github.com/openstack/heat-translator/blob/master/translator/hot/tosca_translator.py#L69
Change-Id: Ib2b0fd6c4c32a523b9fb25f47eae19225b84439f
Closes-bug: #1749394
This patch along with another patch on the tacker client
will remove the need to mention ssl_ca_cert in the vim
configuration file.
Tacker client patch: https://review.openstack.org/546578
Change-Id: I362c40e8b2a606e3b28d368a95e74ee5ea306241
This patch adds the customized OpenWRT image that enables DHCP making
the VNF can be ping. Therefore, the continuously respawning of VNF
can be fixed.
This patch also rewrites the instruction of deploying VNF
based on OpenWRT.
Change-Id: Ieb4d98fe374676bad101a6c2965354a9b19ea0a2
Closes-Bug: #1557008
Closes-Bug: #1749243
Closes-Bug: #1709557
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 reason is wrong in manual_installation.rst.
Written in manual_installation.rst is [nfvo], but wrote in the code is
[nfvo_vim].
The source code as follows:
tacker/nfvo/nfvo_plugin.py:79: cfg.CONF.register_opts(OPTS,
'nfvo_vim')
Change-Id: I6d130e646ca82697f6a2bcc0ef886a16f16912a3
This spec proposes implementing containerized VNF. We choose
to use Kubernetes resources (ConfigMap, Deployment, Horizontal
Pod Autoscaler, Service, etc) to define a containerized VNF.
1. Add "configurable_properties" type in VDU node.
2. Support translate TOSCA to Kubernetes templates.
3. Add kubernetes infra driver to support CRUD containerized
VNF.
Implements: blueprint containerised-vnfs
Change-Id: I706f1f325ca8c2b33debd7e6a13e81535245a5ad
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I9ea26512320eab0a154880b991910656a8651e87
Because of null tenant_id, vnffg delete operation fails to delete
entry from ACLMatchCriteria.Hence delete attemp on parent table fails
with DBReferenceError.
Co-Authored-By: Dharmendra Kushwaha<dharmendra.kushwaha@nectechnologies.in>
Closes-Bug: 1658364
Change-Id: I699f66dfa2eab49dc5239e70973b68967f4d0142
