Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 7 Apr 2016 17:31:26 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12955001.1459439841000.165498.1460050286219@Atlassian.JIRA>
In-Reply-To: <JIRA.12955001.1459439841000@Atlassian.JIRA>
References: <JIRA.12955001.1459439841000@Atlassian.JIRA>
 <JIRA.12955001.1459439841851@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9333) Exclude clusters from OVF
 operations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230650#comment-15230650 ] 

ASF subversion and git services commented on CLOUDSTACK-9333:
-------------------------------------------------------------

Commit 4aae0515588eafe880d33c33e875e257fdb9403f in cloudstack's branch refs/heads/master from [~nvazquez]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4aae051 ]

CLOUDSTACK-9333: Exclude clusters for OVF operations


> Exclude clusters from OVF operations
> ------------------------------------
>
>                 Key: CLOUDSTACK-9333
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9333
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.9.0
>            Reporter: Nicolas Vazquez
>             Fix For: 4.9.0
>
>
> h1. Introduction
> In some environments there is a need to exclude certain VMware clusters from performing OVF operations. This operations are part of: 
> * create template
> * create volume snaphsot
> * copy template, volume, images from primary storage to secondary storage
> * migrate volume 
> * participate when a template gets cached over to primary storage.
> In ESX/ESXi, OVF operations are low priority and bound to a single CPU and most likely get throttled to certain IOPS and network limits. 
> If the hypervisor chosen for OVF operations is weak or overloaded this results in significantly longer execution of such OVF command and therefore degraded performance of underlying CloudStack API call.
> h2. Proposed solution
> It is proposed to add a way to exclude hosts from selected clusters for OVF operations.
> To exclude a cluster, would be necessary to insert a record in {{cluster_details}} specifying property *{{'vmware.exclude_from_ovf'}}* in this way: (supposing we want to exclude cluster X)
> ||cluster_id||||name||value||
> |X|vmware.exclude_from_ovf|true|


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)