VNF resource list output after scaling shows incorrect data

Bug #1629028 reported by Sridhar Ramaswamy on 2016-09-29
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tacker
Medium
Tung Doan

Bug Description

VNF resource list after scale out shows scaling policies instead of actual VNF resources like VDU, CP, etc.

vyatta@controller-vish:~/devstack$ tacker vnf-resource-list hello
VNF 7bbb21d2-90d9-4cd5-8901-532fa80549a1 is not in Active state Cannot fetch details

vyatta@controller-vish:~/devstack$ tacker vnf-resource-list hello
+-------------+--------------------------------------+-------------------+
| name | id | type |
+-------------+--------------------------------------+-------------------+
| VDU1 | 65b6a3be-28cc-4917-b7f9-66cca1417097 | OS::Nova::Server |
| CP1 | e8d6712a-87d3-4e9b-bf53-ebed309a1100 | OS::Neutron::Port |
| CP2 | 892db25a-d3fa-4533-9d47-dea85a51a6a7 | OS::Neutron::Port |
| CP3 | edc04d41-5ba8-4dc9-8263-b4592019ea1c | OS::Neutron::Port |
| VDU1_flavor | ad6303f8-2dde-4635-8773-02ff84e28962 | OS::Nova::Flavor |
+-------------+--------------------------------------+-------------------+

vyatta@controller-vish:~/devstack$ tacker vnf-resource-list scale
+---------------+--------------------------------------+----------------------------+
| name | id | type |
+---------------+--------------------------------------+----------------------------+
| SP1_scale_out | a45d59dbf863419e9ce0a038605c23e0 | OS::Heat::ScalingPolicy |
| G1 | f875cdba-107b-4e66-8202-202e7af9c24f | OS::Heat::AutoScalingGroup |
| SP1_scale_in | 435b2869a52a468b80d03f1a769a2f6d | OS::Heat::ScalingPolicy |
+---------------+--------------------------------------+----------------------------+

Changed in tacker:
assignee: nobody → venkatamahesh (venkatamaheshkotha)
Changed in tacker:
status: New → Confirmed

Hi Sridhar,

The resource list is extracted from the hot template by the heat client. For a normal vnfs after translating to hot template the resources are not changed and so we are getting as VDU1, VDU2, CP ....
But In case of scaleVNF the resources are changing from VDU..... to G1, .... So while returning the resources list by heat client we are getting as G1, SP1_scale_in...........

Here is the snapshots of hot templates of normal VNF and scale VNF.

Sridhar Ramaswamy (srics-r) wrote :

Thanks for the analysis. Any possible solution to get around this issue ?

One way is to parse the output of heat resource list and if we see intermediate resources like G1, SP1_scale_in, some new logic can do further heat calls on these resources to get to the actual VDU, CP resources.

Changed in tacker:
importance: Low → Medium
milestone: ocata-1 → ocata-2
Tung Doan (tungdoan) wrote :

Hi venkatamahesh,

Sorry for bothering. This bug is a very nice catch. I saw that it is a significant stuff for next features, especially scaling for SFC. I fixed this bug and added you as co-author.
Result: http://paste.openstack.org/show/593687/

Thanks

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

Changed in tacker:
assignee: venkatamahesh (venkatamaheshkotha) → Tung Doan (tungdoan)
status: Confirmed → In Progress

Hi Tung Doan,

Ok.

Reviewed: https://review.openstack.org/415935
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=2edb3bd51f626f8204ab0834879ecfc7cfc6db90
Submitter: Jenkins
Branch: master

commit 2edb3bd51f626f8204ab0834879ecfc7cfc6db90
Author: doantungbk <email address hidden>
Date: Sat Dec 31 01:36:03 2016 -0800

    Fix: nested resources are ignored

    The current "resource-list" method in Tacker just mentioned to
    the first-layered resources. Meanwhile scaling feature used the
    nested template which contains VNF discription. Therefore, the nested
    resources are ignored in the scaling case. This spec will fix this issue.

    Co-Authored-By: venkatamahesh <email address hidden>
    Closes-Bug: #1629028

    Change-Id: I0a4258873f7898a009a155f2b048638cdbc581d9

Changed in tacker:
status: In Progress → Fix Released

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers