One of the things that helped me quite a bit With the CentOS stuff was
that I created a VM with agent/management server running in it. I set
up a 4.0 system with an advanced zone, pulled down the source code
into it, and then took a copy of the VM. Then I ran through the
upgrade process 10 or 15 times, testing, making note of what was
missing, rolling back and then trying again, slowly building a patch
for the cloud.spec. With the database upgrade and everything else that
needs to be done, it's really hard to roll back a real environment and
try the upgrade again from scratch.

At this point upgrading CentOS is just installing the new RPMs along
with a few new dependencies, restarting the services, and restarting
the system vms so they get upgraded software. Your e-mail has prompted
me to want to create a wiki though, in case anything goes wrong,
unless upgrade notes will be released somewhere in particular. Just a
place to put upgrade tips like "Old configs will be moved from
/etc/cloud to /etc/cloud.rpmsave" in case something does need to be
moved manually by the admin.

On Sat, Mar 30, 2013 at 6:17 AM, Wido den Hollander <w...@widodh.nl> wrote:
> Hi,
>
> I've started a Wiki[0] to describe the upgrade process going from 4.0 to 4.1
> with Ubuntu packages.
>
> Since the packages got renamed from cloud-* to cloudstack-* a lot has
> changed and some manual intervention is required.
>
> The Wiki is work-in-progress while I'm upgrading one of my 4.0 clusters to
> 4.1 and see how it all works out.
>
> Feel free to change the Wiki if you find something that needs to be
> adressed!
>
> Wido
>
> [0]:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Ubuntu+upgrade+process
>

Reply via email to