[jira] [Resolved] (CLOUDSTACK-4467) [Doc] Enhance the Upgrade Section for Clarity

["Pierre-Luc Dion (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Luc Dion resolved CLOUDSTACK-4467.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Future)
                   4.4.0

The Release-notes upgrade sections of 4.4.0 split cloudstack-agent upgrade from management-server. There is also speration between CentOS and Ubuntu based OS.

> [Doc] Enhance the Upgrade Section for Clarity
> ---------------------------------------------
>
>                 Key: CLOUDSTACK-4467
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4467
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>            Reporter: Radhika Nair
>            Assignee: Pierre-Luc Dion
>            Priority: Critical
>             Fix For: 4.4.0
>
>
> Suggestion from Frank
> the upgrade instructions should be divided in two parts. mgmt server upgrade and kvm agent upgrade. upgrading cloud-agent is actually upgrading KVM agent running on host. Putting them together will confuse customers who don't use KVM
> the same applies to upgrading xenserver and usage server. we should put them in dedicated chapter, now all stuff are in a single chapter which is quite confusing.
> can we arrange them like this:
> Upgrade management server
> 4.0 to 4.2
> 2.2.x to 4.2
> Upgrade cloud agent
> 4.0 to 4.2
> 2.2.x to 4.2
> Upgrade usage server
> 4.0 to 4.2
> 2.2.x to 4.2
> Upgrade Xenserver host



--
This message was sent by Atlassian JIRA
(v6.2#6252)