You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/07/22 08:41:39 UTC

[jira] [Commented] (CLOUDSTACK-7150) [VMware] Global config 'vm.instancename' is not honored

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069902#comment-14069902 ] 

ASF subversion and git services commented on CLOUDSTACK-7150:
-------------------------------------------------------------

Commit b3e4c6d6dc9bf57aa880ab100a76027b2a12053d in cloudstack's branch refs/heads/master from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b3e4c6d ]

CLOUDSTACK-7150. [VMware] Global config 'vm.instancename' is not honored.
If global config 'vm.instancename' is set to true, VM name in vCenter should be '<instance_name>-<vm_hostname>'.


> [VMware] Global config 'vm.instancename' is not honored
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-7150
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7150
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.5.0
>            Reporter: Likitha Shetty
>            Assignee: Likitha Shetty
>             Fix For: 4.5.0
>
>
> When global config 'vm.instancename' is set to true, VM name in vCenter is not being constructed correctly. The name in vCenter should be '<instance_name>-<vm_hostname>'.
> For e.g. for a VM with CS internal name i-2-3-VM is named in vCenter as i-2-<hostname> whereas it should be i-2-3-<hostname>.



--
This message was sent by Atlassian JIRA
(v6.2#6252)