vnfd-create displays the service id in value column
of 'service_types row, which is not relevant to the user.
Hence its removed.
This fix is under review as part of
https://review.openstack.org/#/c/348874/ which is abondoned due
to code merge messup.
Change-Id: Ic8c657baae445bb8b22754df77e281d6f36a5d42
Closes-Bug: #1592289
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
oslo.xxx and keystone middleware configurations
are added now to the config generator
Closes-Bug: #1633974
Change-Id: Ief0d106f45248af0ab21de4815ea6e361165df48
At present when vnf is created the event detail message is
"VNF status updated". But it would be good to have message
"VNF CREATE Complete". So In this patch it is corrected.
Change-Id: I8b9efb977fe6f51604fd7a10dcf89cf208b86eb8
Closes-Bug: #1629177
This patch is used to modify word spelling mistakes.
Here change vfn/vfnd to vnf/vnfd in test_vnfm_param.py.
Trivial Fix.
Change-Id: Ic5d1f82ecd2425210fb9f1271cc64b4b0a162fe1
Releasenote translation publishing is being prepared. 'locale_dirs'
needs to be defined in conf.py to generate translated version of the
release notes.
Note that this repository might not get translated release notes - or
no translations at all - but we add the entry here nevertheless to
prepare for it.
Change-Id: I5898445bfb82767be43da10c36a99e013773af45
This commit adds code to support the below related to alarm
monitoring and scaling:
1.Consolidates the two event captures in the update_vnf_with_alarm
method into just a single event capture with alarm url details.
2.Captures events in update_vnf_with_alarm method when policy action
and alarm action name are missing.
3.Captures the event information for ActionAutoscalingHeat policy
action invocation and scaling action in the right time order.
Change-Id: Iea255a4f454fb0c721b152090514ad8ca8732890
Closes-Bug: #1629453
ActionPolicy getter was recently changed to use infra_driver [1].
However the alarm monitor handling of scaling policy missed passing
infra_driver causing scaling due to alarm monitoring trigger to fail.
This fix now correctly passes infra_driver for monitor
ActionPolicy.get_policy method in this specific case.
[1] https://review.openstack.org/#/c/375181/
Change-Id: I545f959fb889036846282cd78e7967822604975f
Closes-Bug: #1627975
As per OpenStack Docstrings guide lines [1]:
[H401] Docstrings should not start with a space.
[H403] Multi line docstrings should end on a new line.
[H404] Multi line docstrings should start without a leading new line.
[H405] Multi line docstrings should start with a one line summary
followed by an empty line.
[1] http://docs.openstack.org/developer/hacking/#docstrings
trivialfix
Change-Id: Ia0320493edc025a2340e58724e91e8bf72112de0
Modify the validation for VnfPolicyNotFound by breaking the
logic in to two steps:
1. Verify if action is already part of DEFAULT_ACTIONS
2. If 1. fails, try to get the policy for action name defined in
template.
If 2 fails, only then raise an exception.
also fix the vim_auth args sent to the monitoring policy
execute_action method.
Closes-Bug: #365435
Change-Id: I7923189575c44efcd4121b0158c270f801b7cf2b