RFE: Allow vdu (VM) names to be specified as a parameter

[Sridhar Ramaswamy]

Currently VMs spawned by Tacker through Heat uses a dynamically generated VM name like,

ta-3e9f-a228-4c19-985f-545d6a90c42e-VDU1-e24ii2ygzbgt

.. which is auto-generated by Heat.

This request-for-enhancement is to add support to accept a "name" property in the VDU TOSCA node type which should be passed to Heat to create the VM with this specific name. Of course this property need to be parameterize-able using {get_input vdu1-name}

Here is the suggested TOSCA enhancement,

topology_template:
  node_templates:
    VDU1:
      type: tosca.nodes.nfv.VDU.Tacker
      properties:
        name: {get_input : vdu1-name}
        image: cirros-0.3.4-x86_64-uec
        flavor: m1.tiny
        availability_zone: nova
        mgmt_driver: noop

[Sridhar Ramaswamy (srics-r)]

@Aqsa - Are you actively working on this ? If not can you please un-assign so that another community member can pick it up.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by dharmendra kushwaha (<email address hidden>) on branch: master
Review: https://review.openstack.org/359576
Reason: While updating the patch, it failed to update and unknowingly(by mistake) new patch has been generated. i.e.: https://review.openstack.org/#/c/363549/

[OpenStack Infra (hudson-openstack)]

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

commit c7c0dc9bc4190bd2462d14c839ae5b0dbe0b0f8d
Author: dharmendra <email address hidden>
Date: Wed Aug 31 18:19:36 2016 +0900

    Allow vdu (VM) names to be specified as a parameter

    Adding support to accept name property in the VDU TOSCA node type
    which will be passed to Heat to create the VM with this specific name.

    Closes-bug: 1570557
    Change-Id: Iac0ae4397edcc5398cf8c1fdede709c6e903cceb

[OpenStack Infra (hudson-openstack)]

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