[
https://issues.apache.org/jira/browse/CLOUDSTACK-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827520#comment-13827520
]
ASF subversion and git services commented on CLOUDSTACK-5069:
-------------------------------------------------------------
Commit f15c9977690f8916543c2c066ee49cb37b34c730 in branch refs/heads/4.3 from
[~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f15c997 ]
CLOUDSTACK-5069. Added global config 'vmware.vcenter.session.timeout' to make
the vCenter session timeout value configurable.
> Make VMware vCenter session timeout value configurable.
> -------------------------------------------------------
>
> Key: CLOUDSTACK-5069
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5069
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Priority: Critical
> Fix For: 4.3.0
>
>
> We see socket timeout errors in a VMware setup if a VMware task
> (RelocateVM_Task, CloneVM_Task etc.) takes more than 20 minutes.
> Add a global config 'vmware.vcenter.session.timeout' to make the vCenter
> session timeout value configurable.
> Note that VMware tasks like CloneVM_Task take longer if we use the default
> full-clone mode and a slow storage.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
