cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafael Weingartner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8946) Refactor migratewait global setting
Date Wed, 14 Oct 2015 01:03:05 GMT

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

Rafael Weingartner commented on CLOUDSTACK-8946:
------------------------------------------------

This ticket is also related to : https://issues.apache.org/jira/browse/CLOUDSTACK-8949
The name of the parameter does not suggest what it does.
Is it a parameter to specify VMs migration timeout? Volumes timeout? Is it just for Xen, or
for others hypervisors too?
Moreover, as said on CLOUDSTACK-8949, that parameter should be set on MigrateVolumeCommand,
otherwise the ACS end up using the defualt parameter called "wait", which BTW does not mean
much.
It would be nice to refactor both parameter names, making them more specific and clear.

> Refactor migratewait global setting
> -----------------------------------
>
>                 Key: CLOUDSTACK-8946
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8946
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Ryan Farrington
>            Priority: Trivial
>
> Rafael Weingärtner [rafaelweingartner@gmail.com] suggested in the users mailing list
that the global setting "migratewait" be refactored as in his words "I think that is a terrible
parameter name. We should refactor that".  



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

Mime
View raw message