Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: I98ad21d153f2fcd0862627111fb5759f72bcc5ad
Sem-Ver: feature
Added reservation policy support.
With reservation policy user can use the reserved resources
by blazar to create VNF.
Depends-On:I2b989a49ac3447995a82ddb7193bf478bb847b73
Implements: blueprint reservation-vnfm
Change-Id: Ia6a87894ba219c045140e8e65e03f87509bbdb6d
This feature allows choosing SFC encapsulation between MPLS
and NSH (default MPLS). It also apply SFC proxy to make use
of correlation.
Change-Id: Ia5eda02df415c9e3f6f035068176d60a14ffb68f
This patch adds below functionality:
- New policy action ``vdu_autoheal`` for recovering failed VDUs
as reported by the respective monitoring driver configured in
the monitoring policy of the VNFD template.
- Add unit/functional tests.
- Added oslo_versioned library to implement HealVnfRequest object.
Note: The implementation of vdu_autoheal policy action will support
HealVnfRequest interface as mentioned in the ETSI standard [1]
[1]: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.05.01_60/gs_NFV-SOL003v020501p.pdf
Implements: blueprint vdu-auto-healing
Change-Id: If62acbdac41c92842de0ae3b7dedcda9fd1f86e6
This commit adds the functionality of tacker-status CLI for performing
upgrade checks as part of the Stein cycle upgrade-checkers goal.
It only includes a sample check which must be replaced by real checks in
future.
Change-Id: I7bb127fa10dd168ab24dd8c42013576f84eadfbb
Story: 2003657
Task: 26158
When Network Service (NS) is supported in Tacker, we can launch
multiple VNFFGs by initiating NS. Because each VNFFG can have
different 'symmetrical' value, we should support dynamic 'symmetrical'
parameter for each VNFFG in VNFFG descriptor.
This feature will add 'symmetrical' as a property of forwarding path,
so users can set 'symmetrical' value to 'true' or 'false' to change
symmetrical value of a port chain in networking-sfc.
Change-Id: Ie9a6abe96141954e95902cd426abafa10d744236
Change-Id: Ib58255e5b860f95b6c95c1373ee2c2e70722cd81
Co-Authored-By: Yan Xing an <yanxingan@cmss.chinamobile.com>
Implements: blueprint shared-barbican-secret
This removes usage of deprecated Ceilometer API
1. Changing trigger type from "OS::Ceilometer::Alarm"
to "OS::Aodh::GnocchiAggregationByResourcesAlarm"
2. Add "resource_type" fixed with value "instance"
3. Change some paramters (meter_name-> metric,
statistic ->aggregation_method, period-> granularity)
4. Change value from "average" to "mean" in method to
compare to the threshold
Change-Id: I486c14cbc9d05a0e826bbef1ad181bdcb2d8c951
Closes-Bug: #1735484
- This patch aims to add support for following placement policies in
addition to the default 'affinity' policy:
anti-affinity
soft-affinity
soft-anti-affinity
- This patch adds respective functional/unit test cases. To test
"anti-affinity" policy on the gate, changed the devstack functional
jobs `nodeset` from the default single node to "openstack-two-node".
- This patch also adds respective documentation and usage guide for
the above added policies.
Depends-On: I56a9cf4bb553c8026eec73212a3742d5eab17420
Co-Author: tpatil <tushar.vitthal.patil@gmail.com>
Implements: blueprint vdu-affinity-policy
Change-Id: I18aaa9d00c8539ccc60cb6e70570dee124df70a3
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
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