In tacker cli, stack_id is misspelled as instance_id
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
Invalid
|
Low
|
tamil vanan |
Bug Description
The tacker Cli "tacker vnf-show vnf_name" lists the vnf complete details.
In which it displays a field called "instance_id". The "instance_id" field carrying the stack_id.
Its better to change its name to "stack_id" to avoid confusion.
tamilhce@
+------
| Field | Value |
+------
| attributes | {"heat_template": .......
| created_at | 2016-09-29 07:41:03 |
| description | Demo example |
| error_reason | |
| id | b41b60ed-
| instance_id | 30874fca-
| mgmt_url | {"VDU1": "192.168.120.3", "VDU3": "192.168.120.7", "VDU2": "192.168.120.6"} |
| name | my_vnf |
| placement_attr | {"vim_name": "tamil"} |
| status | ACTIVE |
| tenant_id | 078639382692423
| updated_at | |
| vim_id | 4ccbdd47-
| vnfd_id | da40d441-
Changed in python-tackerclient: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in python-tackerclient: | |
assignee: | nobody → tamil vanan (tamilhce) |
affects: | python-tackerclient → tacker |
Changed in tacker: | |
milestone: | none → ocata-1 |
term stack_id is heat related. I don't see anything wrong with "instance_id". Instance here refers to a VNF instance.