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

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

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

CLOUDSTACK-6168: fixed the description for global config "vm.instancename.flag" 
- the flag is applicable for VMware hypervisor only


> vm.instancename.flag inefficient
> --------------------------------
>
>                 Key: CLOUDSTACK-6168
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6168
>             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: Cloudstack 4.2.1 on 
>            Reporter: JF Vincent
>            Assignee: Alena Prokharchyk
>             Fix For: 4.5.0
>
>
> have set vm.instancename.flag to YES, restarted the management server 
> -> started a new instance in my KVM zone with or without any display name => 
> no change on instance name on hypervisor.
> -> started a new instance in my vCenter zone with a display name madrid. 
> Instance name on ESXi is just madrid and not i-xx-xxxx-madrid.
> Regards
> JF



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

Reply via email to