You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2013/11/20 12:07:37 UTC

[jira] [Updated] (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 ]

Likitha Shetty updated CLOUDSTACK-5218:
---------------------------------------

    Summary: CLONE - [Doc] Make VMware vCenter session timeout value configurable.  (was: CLONE - Make VMware vCenter session timeout value configurable.)

> 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
>            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#6144)