Robert, It sounds like you are talking about more the Citrix CloudPlatform upgrade path.
>From a CloudStack upgrade path, you would be looking at going from 2.2.14 -> 3.0.2 -> 4.0.1. Personally I would suggest brining up your CentOS at the same time as there are going to be a number of patches and upgrades there as well that are going to help your management server, as well as support compatibility better. Matt On 4/16/13 4:16 PM, "Robert Botte" <robert.bo...@verio.net> wrote: >We are currently using Cloudstack 2.2.13 and CentOS 6.1 running on KVM >in the advanced networking configuration. We would like to move our >production platform to 3.0.6 > > > >My understanding is that we need to upgrade from 2.2.13 to 2.2.14, after >this upgrade do we have to upgrade to 3.0.2 than to 3.0.6? Is this the >upgrade roadmap we need to follow? My understanding from technical >feedback I received is this is known to be the successful path. > > > >Do we have to upgrade our CentOS version to be used for user VMs during >our upgrade to 2.2.14 or can we wait until the end of the upgrade >process when we finally land on 3.0.6 and then upgrade? I know the >Management Server is suggested not to be CentOS. Are there specific >instructions to successfully complete this upgrade regardless of the >CentOS version(s) we use? > > > >Are there any "critical steps" document that can be provided to help us >avoid any pitfalls? (new VM templates were successfully applied, files >placed in the proper format to ensure compatibility, duplicate resource >count table entries, etc...) > > > >How can we search for "ALL" custom content in advance to reduce any >possibility of upgrade failures? > > > > > > > >This email message is intended for the use of the person to whom it has >been sent, and may contain information that is confidential or legally >protected. If you are not the intended recipient or have received this >message in error, you are not authorized to copy, distribute, or >otherwise use this message or its attachments. Please notify the sender >immediately by return e-mail and permanently delete this message and any >attachments. Verio Inc. makes no warranty that this email is error or >virus free. Thank you.
