Wrong value set required when passing parameter to VNFD
Bug #1643576 reported by
helander
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
In Progress
|
Medium
|
dharmendra |
Bug Description
In a VNFD template where the template is parameterized according to:
inputs:
connection-type:
type string
and
CP2:
type: {get_input : connection-type}
The same template without the parameter looks like:
CP2:
type: sriov
However when deploying the VNF "sriov" is not allowed as a value for "connection-type" but the Heat binding.vnic_type values (direct,normal, ...) are suggested.
It seems like them mapping between the VNFD type values and the Heat type values are "bypassed".
Changed in tacker: | |
assignee: | nobody → Ukesh (ukeshkumar) |
Changed in tacker: | |
importance: | Undecided → Medium |
Changed in tacker: | |
assignee: | Ukesh (ukeshkumar) → dharmendra (dharmendra-kushwaha) |
Changed in tacker: | |
milestone: | pike-1 → pike-2 |
Changed in tacker: | |
milestone: | pike-2 → pike-3 |
Changed in tacker: | |
milestone: | pike-3 → none |
To post a comment you must log in.
could you please share the VNFD template ?