This patch will add VNFFG support for NS. In NSD, users can
describe VNFDs and nested VNFFGDs inside. When NS is created,
VNFs and VNFFGs are also created too.
Work items of this patch:
1. Add sample nsd templates
2. Update NFVO plugin to adapt VNFFGD template extraction
from NSD and create VNFFGs using that template
3. Modify Mistral workflow to create/delete VNFFGs using NSD
User guide, defref will be added in following patches.
Co-Authored-By: Cong Phuoc Hoang <hoangphuocbk2.07@gmail.com>
Change-Id: Id5827e66aec0231bf27e87fc96d8fc6bc5cb9c26
Partially-implements: blueprint vnffg-ns
- 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
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
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
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
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>
This patch tries to fix the bug: https://bugs.launchpad.net/tacker/+bug/1719841
To disable the verification, a parameter must be included in vim_config.yaml
file.
cert_verify: 'False'
Co-Authored-By: Cong Phuoc Hoang <hoangphuocbk2.07@gmail.com>
Closes-Bug: #1719841
Change-Id: If9c8eab81bad2028ae146598d559831bc51cbbf5
Signed-off-by: Manuel Buil <mbuil@suse.com>
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 address
1. Update Symmetric Port Chains by setting 'symmetric=True' as
'chain_parameters' key and value pair.
2. Remove 'symmetrical' in flow-classifier functions.
3. Update the doc and VNFFG samples
Change-Id: I04cfafd111b1024ad61b8f9ee48bfe0186a97d0d
Closes-Bug: #1736630
In Devstack environment, cloud-init can not work correctly, because
instance can not access metadata over ther network.
1. This patch will fix cloud-init error, user can use 'user_data'
in vnfd template.
2. Update missing plugin in Tacker (mistral, ceilometer) and
user_data in vnfd template for testing VNFFG function.
Change-Id: Ic2037aaf3e947e941b43d1ae06e475a712398c09
Closes-Bug: #1736627
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
1. scaling and monitoring policy nodes got failed
From tosca-parser 0.8.0, tosca nodes required to be validated.
Unfortunately, the scaling and monitoring policies are not fully
leveraged tosca-parser. This patch will fix this issue.
2. Multiple alarm actions support
Closes-bug: #1682098
Change-Id: I29cb35edfe2447628fa93c64583e5cb4f7bee2f8
Add a function to validate vnffg property number_of_endpoints
Add some UT testcases for this function.
Change-Id: I5180c551f5d6571491c80a9f4bbcb3c74c3c5572
The patch updates the version of cirros image to the latest
0.3.5 disk image in all the sample files.
Change-Id: I400c7ac9d9fd9d295c6996b2935d0a1e0095fa77
Closes-Bug: #1671982
Tacker failed to support monitoring for multiple VDUs.
In addtiion, multi-vdu testing have not been mentioned in unit test.
This patch will fixed the above issues.
Change-Id: Ib4497a530439110bf149f1104c74ba4bdc96ba0a
Closes-bug: #1668587
Currently the tacker connection point (CP) support Virtural IP only if
the security group is off (via anti_spoofing_protection off).
But it's good to have both by supporting allowed_address_pairs.
This RFE is for this purpose.
Closes-Bug: #1664805
Change-Id: I9fa1d4b69f8cbf51b047110cd6cfa61fb91a0bf0
From Mitaka version, Tacker supports TOSCA based VNFD templates. Legacy
templates described under tacker/samples/legacy-templates are deprecated
in newton. Removing in Ocata.
Implements: blueprint deprecate-legacy-template-dsl
Closes-Bug: #1632214
Change-Id: I39f200bb536f4c5d10c920fc1c93bf8f382ca6c2
This patch will focus on:
1. Fixing hardcoded metadata
2. Adding functional test for alarm monitor
3. Refactoring tosca template for alarm monitor
4. Refactoring scaling in/out support in alarm monitor
5. Supporting multi-trigger
Partial-bug: #1630614
Change-Id: Ic5d0046d0dc0b4381713bda01c485cecae17abea
This patch will make the tosca template useful in tacker
installed by devstack directly.
Change-Id: Ifece7eff6c1aa4f189d51306a28f5706f9702748
Closes-bug: #1639163
For vnf scaling, the policy type which is defined in
tacker_def.yaml is 'tosca.policies.tacker.Scaling'.
So all the scaling policy should use this type.
Currently there are some typos when using this policy type.
Change-Id: I8f60c1712007756bb8b6650e053e0d7069f0f9ba
Closes-Bug: #1637895
Implements: blueprint tacker-vnffg
This patch implements the networking-sfc driver for VNFFG SFC driver
and necessary plugin side changes.
Change-Id: I531db5c65d7ed3b1adeeb30606e067aa600a957c
Signed-off-by: Tim Rozet <trozet@redhat.com>
Co-Authored-By: Sridhar Ramaswamy <srics.r@gmail.com>
This patch is the final in the series of deriving infra driver
from vim type. update has been made to monitor code to retrieve
infra_driver from vim information.
Change-Id: I4438f9b22cbe3286d191a2fd96e7e4590625d1cc
Closes-Bug: #1618724
Add definition of alarm monitor in VNFD TOSCA template definition,
support it in VNFM plugin. It can integrate with scaling feature.
An WSGI filter is used to receive ceilometer action URL call and
translate the call into inner action, such as scalling.
The configuration group alarm_auth in tacker.conf is used as the
credentials for ceilometer action URL call. they must have 'admin'
role to query all related stuff for the action.
Implements blueprint: #alarm-based-monitoring-driver
Co-Authored-By: dharmendra kushwaha <dharmendra.kushwaha@nectechnologies.in>
Co-Authored-By: gong yong sheng <gong.yongsheng@99cloud.net>
Change-Id: I7f1dbae361a5dfb97a86e8532bfd09813ce535e2
