You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Radhika Nair (JIRA)" <ji...@apache.org> on 2014/01/08 12:43:04 UTC
[jira] [Resolved] (CLOUDSTACK-5218) CLONE - [Doc] Make VMware
vCenter session timeout value configurable.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radhika Nair resolved CLOUDSTACK-5218.
--------------------------------------
Resolution: Fixed
> CLONE - [Doc] Make VMware vCenter session timeout value configurable.
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-5218
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5218
> 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: Radhika Nair
> Priority: Critical
> Labels: documentation
> 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.5#6160)