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/04/03 22:55:15 UTC

[jira] [Commented] (CLOUDSTACK-3886) VM name on vCenter not getting set correctly when vm.instancename.flag is set to true

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

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

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

CLOUDSTACK-3886: Volume attach/detach implementation for ROOT disk
Implemented for Xen hypervisor only by now
Unittests are included


> VM name on vCenter not getting set correctly when vm.instancename.flag is set to true
> -------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3886
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3886
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: Vmware deployment in cloudstack.
>            Reporter: Venkata Siva Vijayendra Bhamidipati
>            Assignee: Venkata Siva Vijayendra Bhamidipati
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> In a vmware deployment on cloudstack, if the vm.instancename.flag is set to true, and a displayname is supplied during VM creation, the displayname simply gets appended to the internal name i-x-y of that VM in vCenter. The expected behaviour is this:
> If the vm.instancename.flag is set to false (default), there is no change in current behavior:
> 1. If hostname isn't supplied, it is set to the uuid.
> 2. If displayname is supplied, it shows up in the GUI. If not, it is set to the internal VM name i-x-y-VM.
> If the vm.instancename.flag is set to true:
> 1. If hostname is not supplied, and displayname is supplied, set hostname to displayname, and set the instance name as it appears on vCenter also, to the displayname.
> 2. If hostname is not supplied, and displayname is also not supplied, set hostname to uuid, but set internal name of the VM as it appears on vCenter to i-x-y-VM as is done currently.
> 3. If hostname is supplied, set the instance name as it appears on vCenter to this hostname.



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