Create VNF: Inconsistency between CLI, Horizon UI and API for VNF name
Bug #1474966 reported by
vishwanath jayaraman
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
Fix Released
|
Low
|
Manikantha Srinivas Tadi |
Bug Description
Specifying a VNF name is mandatory along with the VNFD-ID when creating a VNF from Horizon UI, however, the command line allows for creating VNF without specifying a name.
When the VNFs are viewed from the Horizon UI, there is no way to distinguish between the VNFs created.
Its better that specifying a name be made mandatory from the command line as well. API needs to be fixed as well to mandate VNF/VNFD/VIM names for REST calls.
Changed in tacker: | |
assignee: | nobody → Bob Haddleton (bob-haddleton) |
status: | New → In Progress |
Changed in tacker: | |
status: | In Progress → Fix Committed |
summary: |
- Create VNF: Inconsistency between CLI and Horizon UI + Create VNF: Inconsistency between CLI, Horizon UI and API for VNF name |
description: | updated |
Changed in tacker: | |
assignee: | Bob Haddleton (bob-haddleton) → Manikantha Srinivas Tadi (manikantha-tadi) |
Changed in tacker: | |
milestone: | none → newton-2 |
To post a comment you must log in.
Agree, this needs to be fixed. Current the name is extracted from the VNFD template. We should co-ordinate this fix with the v2 API efforts.