[
https://issues.apache.org/jira/browse/CLOUDSTACK-9104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15040811#comment-15040811
]
ASF GitHub Bot commented on CLOUDSTACK-9104:
--------------------------------------------
GitHub user priyankparihar opened a pull request:
https://github.com/apache/cloudstack/pull/1165
CLOUDSTACK-9104: VM naming convention in case vmware is used
I have reverted all the changes. Now functionality is same as it was in
earlier version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/priyankparihar/cloudstack CLOUDSTACK-9104
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1165.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1165
----
commit 2588925e9c82a9914b76e06204a04f4a5ff1ddb1
Author: Priyank Parihar <priyank.pari...@citrix.com>
Date: 2015-11-05T15:18:00Z
CLOUDSTACK-9104: VM naming convention in case vmware is used
----
> VM naming convention in case vmware is used
> -------------------------------------------
>
> Key: CLOUDSTACK-9104
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9104
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Priyank Parihar
>
> ISSUE
> ======
> 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 “I-<user-id>-<Display-Name>”
> 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
(v6.3.4#6332)
