cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9104) VM naming convention in case vmware is used
Date Mon, 14 Dec 2015 08:13:46 GMT


ASF GitHub Bot commented on CLOUDSTACK-9104:

Github user bhaisaab commented on the pull request:
    @priyankparihar Fair enough, please see a code review comment. Once you fix the null check,
I think your PR is good to go. Also, write a unit test to enforce the changes; i.e. the unit
test should break in future if someone tries to change the VM naming convention in future.

> VM naming convention in case vmware is used
> -------------------------------------------
>                 Key: CLOUDSTACK-9104
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Priyank Parihar
> ======
> VM naming convention in case vmware is used.
> Description
> ==========
> User with different account cannot create VMs with the same name, which was possible
earlier (I am not sure in which CCP version). That time naming convention used was like this
> Currently if vm.instancename.flag is set to true the VM name will be exactly as display
name given. 

This message was sent by Atlassian JIRA

View raw message