On 04/01/2013 12:43 PM, Sailaja Mada wrote:
Hi,
I tried to upgrade 4.0 Ubuntu Management server to 4.1 with below instructions :
Procedure 1:
1. Add/Modify the line "deb http://cloudstack.apt-get.eu/ubuntu precise 4.1 "
in /etc/apt/sources.list.d/cloudstack.list
2. apt-get update
Observation: It failed with GPG Error.
Reading package lists... Done
W: GPG error: http://cloudstack.apt-get.eu precise Release: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY BBFCFE5386C278E3
I tried to key KEYS from
http://www.apache.org/dist/dev/incubator/cloudstack/KEYS as mentioned @
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/sect-source-verify.html
.
But I am getting 404 error as KEYS are not available at this location.
The key is available here: http://cloudstack.apt-get.eu/release.asc
wget -O - http://cloudstack.apt-get.eu/release.asc|sudo apt-key add -
It's not an official Apache mirror, so it's not using any Apache keys.
Procedure 2:
1. Tried to create APT Repo with packages that are built @
http://jenkins.cloudstack.org/job/package-deb-4.1/ and tried apt-get update .
But there are no packages got upgraded. Filed the JIRA ticket for this issue
couple of days back @ https://issues.apache.org/jira/browse/CLOUDSTACK-1848
Please read the Wiki again, since the packages have been renamed you
need to "apt-get install" the new packages.
apt-get update only retrieves the new package lists from the server.
Wido
Thanks,
Sailaja.M
-----Original Message-----
From: Wido den Hollander [mailto:w...@widodh.nl]
Sent: Sunday, March 31, 2013 12:38 AM
To: dev@cloudstack.apache.org
Subject: Re: [ACS41] Ubuntu upgrade process from 4.0.X to 4.1
On 03/30/2013 04:02 PM, Marcus Sorensen wrote:
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.
I did the same with the Deb packaging, I have a couple of VMs where I test all
of this.
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.
The problem is that we are moving files from location to location and we don't
simply want to do all of that without telling the admin what is going on.
I'll try to do as much as I can in the packages and pre- and post-installation files, but
I'll leave the "scary work" to the admins.
The big warning should say: BACKUP YOUR DATABASE before continuing.
So yes, the packages should do all the heavy lifting, but some guidance would
be nice for a lot of users I think.
Wido
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
