Add fenix plugin for host maintenance.
This feature creates plugin for fenix, create_vnf_maintenance() in VNFM and
VNFMaintenanceAlarmMonitor to create alarm for Fenix. And the feature modifies
alarm_receiver and CRUD in VNFM.
After this feature, all VNF has ALL_MAINTENANCE resource to interacts
with Fenix plugin and [VDU_NAME]_MAINTENANCE if VDU has maintenance property.
[VDU_NAME]_MAINTENANCE will use to perform VNF software modification.
Currently, the plugin can perform CRUD constraints for maintenance,
scale in/out and migration for MIGRATE and LIVE_MIGRATE. The feature has
functions for OWN_ACTION with modified healing, but it not works based on
default vnf workflow in Fenix. And The feature doesn't support server_group
and related with HA like switch over because of unsupported in Tacker.
So these features will be enhance after adding required.
Co-Authored-By: Hyunsik Yang <yangun@dcn.ssu.ac.kr>
Implements: blueprint vnf-rolling-upgrade
Change-Id: I34b82fd40830dd74d0f5ef24a60b3ff465cd4819
Vnf package wsgi app doesn't require extensions
so this patch removes it from composite:vnfpkgmapi_v1.
Change-Id: I724937cd5febc3fd83d8b76a922fae4ed5f5f939
1. Added new config options for vnf packages.
2. This will generate a new sample config each time build
sphinx is run. This is then used on a new docs page
where you can either view the file in its entirety,
or download the file.
Partial-Implements: blueprint tosca-csar-mgmt-driver
Co-Author: Bhagyashri Shewale <bhagyashri.shewale@nttdata.com>
Co-Author: Neha Alhat <neha.alhat@nttdata.com>
Change-Id: I900af00af7f939e6069411104caa714f396dc509
Fix the warning when execute ./tools/generate_config_file_sample.sh
to generate the configuration file tacker.conf.sample
Closes-Bug: #1807863
Change-Id: I45e60410a92d14936a5dab061469c17348f55ca5
Due this patch there are some issue with logging:
1: No Tacker logs generating on gate.
2: No logs in journalctl
3: unable to set log location with config file.
So here reverting this patch.
Closes-Bug: #1782718
This reverts commit 7f60e64bd3cdca461e1e3b507a1b557fd3240a89.
Change-Id: I8dd56d049459037a0f5ea5fd11aaa4449fc55f0f
The installation instructions for tacker conductor are not
included in the installation manual.
Close-Bug: #1777566
Change-Id: I47b2f76fe7df9b4de229d3bdc95700ad9dc1f99a
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 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
These modules have no config OPTS, so we remove them:
tacker.tacker.policy_actions.log.log,
tacker.tacker.policy_actions.respawn.respawn,
tacker.tacker.policy_actions.autoscaling.autoscaling
Change-Id: I553449ad1ef4e0182531ecb0c19938630a977bd1
Closes-Bug: #1734031
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
Currently, backend actions are tightly coupled with monitor module.
This is like a barrier when we have a various actions in the future.
Also, it will be good for separating monitoring-related features out
from tacker-server. This patch also proposes a policy action framework so
that VNF operators can easily add their own actions.
Change-Id: I6ad163f7435c3b778810f96c506c77298be0c53d
Closes-bug: #1582446
oslo.xxx and keystone middleware configurations
are added now to the config generator
Closes-Bug: #1633974
Change-Id: Ief0d106f45248af0ab21de4815ea6e361165df48
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
Currently, infra driver name is derived from VNFD API attribute
infra_driver during VNFD template onboarding. This limits the catalog
to be used for a specific VIM type. VNFD template should be generic
enough to be deployed on any VIM and should not contain infra driver
specific information.
This patch is a follow on for infra driver deprecation [1]
infra_driver value in VNFD request is silently ignored. The infra driver
derivation is now handled during VNF deployment workflow based on user
provied vim_id and corresponding vim_type.
[1] https://review.openstack.org/#/c/363455/
Partial-bug: #1618724
Partially Implements: blueprint infra-driver-refactor
Change-Id: I44cfd18ab75e32872776952560d1f716e99301d5
Previous patch https://review.openstack.org/#/c/349776/
has renamed the DB part.
tacker/vm/plugin.py and tacker/db/vm/vm_db.py are not renamed
in this patch due to the git problem. (It is always be done by
'delete/add' instead of 'rename').
They will be renamed in later patch with unit tests.
Change-Id: I334e0e79c8bdba4a10d97ab691b1e6b242a0f1c5
Partial-bug: #1589018
It also make required keystone config changes as part
of devstack plugin, which helps the functional test cases
to successfully complete and it makes inline with existing
tacker conf.
Closes-bug: #1592247
Change-Id: I545ceb2c9e61c22dbd8a0e1ee39a6e4fa24f8e88
The option was deprecated a long time ago, and will be removed in one of
the next library releases, which will render tacker broken if we keep
using the option.
More details:
http://lists.openstack.org/pipermail/openstack-dev/2016-May/095166.html
Change-Id: Iebd08194a600d3537df7a5ee7ab735e8f0a38899
Closes-Bug: #1586066
Infra driver nova is deprecated as of Mitaka and will be removed
for Netwon release
Change-Id: Iaf1dba67bda5c6e77b719d04cc86d1295b7ca56b
Partial-Bug: #1544332
Added support for multisite OpenStack VIM feature through a new
'nfvo' extension. This also enables remote VNF life cycle manage-
ment through the VIM Id parameter.
Implements: blueprint multi-site-vim
Depends-On: I3c08945f24343288c2c5614ab4b472d68a1e1d47
Change-Id: I7dd19a0c1ce948474bb3069073b3608ce265beb4
mgmt_driver, monitor_driver and infra_driver are configuration
items. Some of them are multistropt, some are listopt.
This patch uses the listopt for all of them.
In addition, rename drivers dir into infra_drivers.
Change-Id: I5bbc7b6a52d97dae8bbca7dd2e804b7c50c8f7a4
Closes-bug: 1524255
Initially the service name was 'servicevm' and 'advsvc' in install file.
Now it's been renamed to 'tacker' and 'nfv-role'. Change in install file
(tacker/devstack/lib/tacker) was necessary to show the updated names
in horizon/dashboard for tacker service.
Change-Id: I740f3bfe04525d616c8f7df2847cee8a8d2b1cab
Depends-on: I919d77276af72586a20f50239166325adbf9fb11
Depends-on: I097ccbfb7ae192410400b06bd8796e81e62ee65e
Closes-Bug: #1524224
This fix handles the usecase where Tacker falsely sets the VNF to
ERROR state after waiting for 50 seconds even though the actual
stack is succesfully completed whose creation time is greater than
50 seconds.
The current default wait time out of 50 seconds is bumped up to
300 seconds as a fair timeout, keeping the memory/cpu constrained
vms/systems in consideration.
Closes-Bug: #1521323
Change-Id: Ied1d904cc0dac2df91dee856100baeb988d65676
* Changes the monitor function to use a loadable driver
* Changes the monitoring thread to use a re-entrant lock
(RLock()) to prevent it from blocking itself during
recovery actions
Change-Id: Icf40ffd3123f3b804de16c88164d84077fbf28e2
Implements: blueprint health-monitoring
Closes-Bug: 1497474
Introduce new Tacker REST API endpoints 'vnfd' and 'vnf' based on NFV
MANO in 'vnfm' extension. Existing 'device' and'device_template'
endpoints will be retained for backward compatibility.
Change-Id: I9dffd4bee25b1f49aea7478f2bd779cf0f6dfb49
Implements: blueprint tacker-api-mano
Merge Neutron master branch to tacker master branch with modification
of tox.ini and .gitreview.
This patch imports the following change set of Neutron.
> commit cba140daccd7c4f715263cda422d5cec27af069d
> Merge: 63d8237 6bed4a0
> Author: Jenkins <jenkins@review.openstack.org>
> Date: Sun Jun 22 16:02:56 2014 +0000
>
> Merge "Adding static routes data for members"
Change-Id: I5a0f522bc20530c46e35dc9e03fe72d72ad04577