[
https://issues.apache.org/jira/browse/CLOUDSTACK-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-4467:
-----------------------------------------
Priority: Critical (was: Major)
> [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
> Priority: Critical
> Fix For: Future
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
