[
https://issues.apache.org/jira/browse/CLOUDSTACK-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222633#comment-15222633
]
ASF GitHub Bot commented on CLOUDSTACK-9333:
--------------------------------------------
Github user rafaelweingartner commented on the pull request:
https://github.com/apache/cloudstack/pull/1457#issuecomment-204624408
@nvazquez,
I find the “AlertManager” class terrible for that. Its name gives the idea
of something that manages alerts and not clusters parameters/configurations.
To add that property, I was thinking about the
“com.cloud.resource.ResourceManagerImpl.discoverCluster(AddClusterCmd)” method
(lines 491 and 492 are already doing that for over-commitment factors), and
then you could create a static entry at “CapacityManager” that seems to be the
best option to hold such configurations.
If you change the “discoverCluster”, you would still need a script to add
that parameter to those clusters that the environment already has. You have to
do that to enable the users to change those parameters and use that
functionality through the web interface.
What do you think?
> 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)
