parameter value wrongly mapped in vnfd

[Ukesh]

In VNFD template, if we give 'sriov' value to the name property, it is then converted to 'direct' in the heat template.

In VNFD:

    vPRE_int_cp:
      type: tosca.nodes.nfv.CP.Tacker
      properties:
        name: sriov
        order: 1
        anti_spoofing_protection: false

In heat template:

  vPRE_int_cp:
    properties:
      name: direct
      network: {get_param: int-network}
      port_security_enabled: false

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/408047
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=1da3bf459eff31b909d7cca18f9aa7c933591fdc
Submitter: Jenkins
Branch: master

commit 1da3bf459eff31b909d7cca18f9aa7c933591fdc
Author: Ukesh Kumar Vasudevan <email address hidden>
Date: Wed Dec 7 17:26:53 2016 +0530

    parameter value wrongly mapped in vnfd

    In VNFD template, if we give 'sriov' value to the name property,
    it is then converted to 'direct' in the heat template.

    Solution: before changing the value, key-name is checked now

    Change-Id: Ib7d96c7fccc781bc0615670ddf90bba4dcbdf24c
    closes-bug: #1648003

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tacker 0.6.0 release.