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, 25 Jan 2016 04:26:39 GMT


ASF GitHub Bot commented on CLOUDSTACK-9104:

Github user alexandrelimassantana commented on the pull request:
    @priyankparihar, since you are modifying this method, you could also generate it's javadoc.
It would be a nice upgrade from that single line comment placed just before the method signature
( line 2033 ). You could even state your parameter null check in the @parameter field in it.

> 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