The oslo.reports library provides some options under the [oslo_reports]
section. This change ensures these parameters are rendered by
the oslo-config-generator command.
Change-Id: If1cd703bf06c76fa23c567e61434ef703c24daa0
The oslo.service library provides a separate entrypoint to load options
for periodic tasks. Because Tacker imports periodic tasks mechanism
from the library, the related options should be loaded as well.
Change-Id: Ic6de82be9d1bed1c557c53216caabcbf9e944e3f
Fixed the problem that "vnflcm_mgmt_driver = vnflcm_noop" does not exist
in /etc/tacker/tacker.conf after installing the tacker.
In setup.cfg, change vnflcm_drivers to vnflcm_driver.
In etc/config-generator.conf, add "namespace = tacker.vnflcm.vnflcm_driver".
Closes-Bug: #1918232
Change-Id: I50ffb4c96837599dcb0d04dd673e0c4681ffedfa
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
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
Takashi Kajinami
LiangLu
Niraj Singh
liuyuanyuan
Cong Phuoc Hoang
Yan Xing'an
doantungbk
gong yong sheng
Kanagaraj Manickam
Sripriya