Fix docs "Line too long" under doc8 style.
When running "#tox -e docs", there is an error of
doc8 saying "Line too long"
Change-Id: Ifd64d805cb9caf74f4c5ac82ebf31aa7b85ec32a
Signed-off-by: Andy Yan <yanchao3@lenovo.com>
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
Now that heat is available as a devstack plugin, it should be
used. The document is updated to enable the heat devstack plugin
before the tacker plugin.
Co-Authored-By: Kanagaraj Manickam <mkr1481@gmail.com>
Change-Id: I9d20d72dfa50f36ee454f56f3c67d063012ef05b
In this patch I have added --visibility option in
glance image-create command. without this it is creating
with private. And then if we use it for creating VNF,
it is throwing error "Image not found". And also I have added
openstack cli
Change-Id: I870dabfe88f3d9bc2b0d067d79581941fd13d2e2
By following the present installation guide we are getting errors
So In this patch I have updated to get successful installation
Change-Id: I719a641c5a8d9b12364d6b9b0ac435199ce03f7a
Closes-Bug: #1610950
Closes-Bug: #1604228
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
Introduce a TACKER_MODE variable. If this is set to 'all', the
tacker devstack plugin will install other components just like
previous way. If it is set to 'standalone', the tacker devstack
plugin will disable all other services and enable the mysql,
keystone, tacker and horizon services.
Change-Id: I5d7613566ed45aa273848bfe85d76c7a7fe97ba1
Closes-bug: 1633327
Closes-bug: 1620163
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