[ https://issues.apache.org/jira/browse/CLOUDSTACK-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224673#comment-15224673 ]
ASF GitHub Bot commented on CLOUDSTACK-9333: -------------------------------------------- Github user rafaelweingartner commented on the pull request: https://github.com/apache/cloudstack/pull/1457#issuecomment-205423791 I think this is the best way to tackle the problem. You just need to add that insert into the version’s upgrade script. > 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)