cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8197) make minimal sysvm version configuratble
Date Tue, 03 Feb 2015 13:48:35 GMT

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

Rohit Yadav commented on CLOUDSTACK-8197:
-----------------------------------------

[~dahn] - not really, what I'm suggesting is keep minimum version same as current jar's major
version and use that value to override global config (sort of upgrade automatically) if it's
less than that. For example, upgrading to 4.4.3 from 4.4.2 won't change the min version as
by the logic I shared min version remains 4.4.0 which of course in global config is 4.4.2
so it's fine. But when you upgrade to 4.5.0 or 4.5.1, the min value becomes 4.5.0. While the
other of doing this is to change the global config param/value in an upgrade path. The former
solution would fix it automatically for us so less maintenance, the latter is explicit so
could also be useful.

> make minimal sysvm version configuratble
> ----------------------------------------
>
>                 Key: CLOUDSTACK-8197
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8197
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, SystemVM
>            Reporter: Daan Hoogland
>            Assignee: Daan Hoogland
>
> MinVRVersion is hard coded in the VirtualNetworkApplianceService. To facilitate users
to make their own versions it must be a config key. As such it will be best to move it to
NetworkOrchestrationService as it's use is mostly from that layer.



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

Mime
View raw message