Wrong value set required when passing parameter to VNFD

[helander]

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".

[Ukesh (ukeshkumar)]

could you please share the VNFD template ?

[helander (lehswe)]

VNFD attached.

[Sridhar Ramaswamy (srics-r)]

This seems to be a duplicate of https://bugs.launchpad.net/tacker/+bug/1648003.

Is this issue isolated to using CP type value "sriov" ?

[helander (lehswe)]

No this is not a duplicate of https://bugs.launchpad.net/tacker/+bug/1648003.

The reported problem is related to when the value "sriov" is not explicit in the VNFD but transfered in a "parameter".

If this problem is isolated to just CP and further limited to the "sriov" value or if it is a more general problem with regards to how parameterised values are mapped, I do not know.

[Ukesh (ukeshkumar)]

No this is not a duplicate of https://bugs.launchpad.net/tacker/+bug/1648003.

The problem here is, when the value "sriov" is passed via parameter, the current code won't map it to "direct" in the heat template.

One solution of this bug can be, we have to check for "sriov" string in the type and if it is a parameter, then we have to check its value for "sriov", if it is then instead of the parameter, we have to give directly the value "direct" for type of CP.

[OpenStack Infra (hudson-openstack)]

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

[Sridhar Ramaswamy (srics-r)]

Out of time for Ocata, moving to Pike.