[
https://issues.apache.org/jira/browse/CLOUDSTACK-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833907#comment-13833907
]
Steve Searles commented on CLOUDSTACK-5069:
-------------------------------------------
Any thoughts on getting this merged into the next release? 4.2.1? I find this
almost a blocker if you have a large VM 100GB+ you are trying to import from
OVF. This is causing users to be unable to migrate to cloudstack from a
traditional vm farm setup. Can someone direct me to where in the source this
is hardcoded so we can manually fix the issue and recompile in versions less
than 4.3?
> 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)
