Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5150E10B8B for ; Wed, 27 Nov 2013 16:11:58 +0000 (UTC) Received: (qmail 31632 invoked by uid 500); 27 Nov 2013 16:11:57 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 31382 invoked by uid 500); 27 Nov 2013 16:11:54 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 31182 invoked by uid 500); 27 Nov 2013 16:11:44 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 31152 invoked by uid 99); 27 Nov 2013 16:11:43 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Nov 2013 16:11:43 +0000 Date: Wed, 27 Nov 2013 16:11:42 +0000 (UTC) From: "Steve Searles (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-5069) Make VMware vCenter session timeout value configurable. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)