Anomalies observed in VNF event log as part of alarm monitoring plus scaling

[vishwanath jayaraman]

As part of trying to understand alarm monitoring and scaling, I used the sample VNFD at https://github.com/openstack/tacker/blob/master/samples/tosca-templates/vnfd/tosca-vnfd-alarm-scale.yaml to upload a VNFD and create a VNF. I ran command "dd if=/dev/zero of=/dev/null" as part of a script inside the VMs to load the CPU and trigger alarm that resulted in scaling up the VNF.
The screen shot attached captures the event log for the VNF from time of creation to end of scaling operations.
Some of the observations from the log are:
1. Event IDs 20 and 21 may need to be merged and called out in the Event Details as "VNF updated with Alarm URL: <Alarm URL string>"
2. Event ID 25 indicates in the Event Details column that scaling action has been initiated and may need to have occurred or captured before Event ID 24.
3. ActionAutoscalingHeat action is invoked even when a VNF is in a non Active state

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/380685

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/380685
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=09edd7badf57a1c1f45bc4ce6cd5e243cae3af76
Submitter: Jenkins
Branch: master

commit 09edd7badf57a1c1f45bc4ce6cd5e243cae3af76
Author: vish <email address hidden>
Date: Sat Oct 1 02:11:34 2016 +0000

    Fixes event ordering for alarm monitor and scale actions.

    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

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/389526

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/389526
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=328bb029d3cd1c6aa9d54c99965834b75bae5117
Submitter: Jenkins
Branch: stable/newton

commit 328bb029d3cd1c6aa9d54c99965834b75bae5117
Author: vish <email address hidden>
Date: Sat Oct 1 02:11:34 2016 +0000

    Fixes event ordering for alarm monitor and scale actions.

    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
    (cherry picked from commit 09edd7badf57a1c1f45bc4ce6cd5e243cae3af76)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tacker 0.6.0 release.