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
Descripton of Connection Point needs to be updated to keep
consistency with tacker_nfv_defs.yaml.
Currently 'type' is an optional property and has a constraint.
Also 'security_groups' property was introduced in [1].
[1] https://review.openstack.org/#/c/334256/
Change-Id: Ic0721c3914197bdc7128b5fff76783a2f7ba9f9e
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
This is a follow-on to [1] which introduces
'order' property of the CP.
[1] https://review.openstack.org/#/c/363352/
Change-Id: Ib7a8df468f48be1a90c9a7f43d2f8a1a5ca82366
With too many gerrit reviews in the queue, the team
needs a way to categorize and bubble up reviews that
are actionable. Hence introduce gerrit dashboard with
various filters to identify patchsets to review.
Change-Id: I6e1552f8a3fbd81ae45ad1943b493e8c3bd83654
Instead of handling each keystone parameter error in Tacker,
reuse keystone's BadRequest exception that already takes care of
parameter errors in user input not just for domains, but users,
projects and tenants.
Change-Id: I2a6aa6f7f9dec829bf1010d244d1aadf7942ec9d
After devstack installation, to run functional test cases, the
nova instance quota, keypair and neutron port quota should be
set to a level which will not block tests. This patch adds a tool
to do this preparation so that developers can easily run
functional tests locally.
Change-Id: I1c2fae110863906e3f7601456dbf79ff06da4c40
Closes-bug: #1617303
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
Name is made as mandatory and positional argument in getting started &
manual installation docs.
Also updated the devstack lib.
Change-Id: I5bd87925fc7ee89fdd44f873818d55fdd81611ac
Partial-Bug: #1474966
domain name information should be in VIM configure, which is
different from keystone configuration in tacker.conf.
Also domain name is prefered to domain id.
Change-Id: Iec492e55ff763f92304c129d2373e544269f6271
Partial-bug: #1603851
