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 |
+---------------+--------------------------------------+----------------------------+
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_
Here is the snapshots of hot templates of normal VNF and scale VNF.