Return-Path: 
 <dev-return-54276-apmail-cloudstack-dev-archive=cloudstack.apache.org@cloudstack.apache.org>
X-Original-To: apmail-cloudstack-dev-archive@www.apache.org
Delivered-To: apmail-cloudstack-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A37A810AC8
	for <apmail-cloudstack-dev-archive@www.apache.org>;
 Tue, 18 Mar 2014 05:15:43 +0000 (UTC)
Received: (qmail 61651 invoked by uid 500); 18 Mar 2014 05:15:42 -0000
Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org
Received: (qmail 61614 invoked by uid 500); 18 Mar 2014 05:15:40 -0000
Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:dev@cloudstack.apache.org>
List-Id: <dev.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list dev@cloudstack.apache.org
Received: (qmail 61605 invoked by uid 99); 18 Mar 2014 05:15:39 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2014 05:15:39 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of shadowsor@gmail.com
 designates 209.85.220.179 as permitted sender)
Received: from [209.85.220.179] (HELO mail-vc0-f179.google.com)
 (209.85.220.179)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2014 05:15:35 +0000
Received: by mail-vc0-f179.google.com with SMTP id ij19so6569518vcb.24
        for <dev@cloudstack.apache.org>; Mon, 17 Mar 2014 22:15:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=H6m5lpLLI5+IyhBo4uBFX5hVgBWiVQDRkTwvCWcQvJc=;
        b=qYOUYdErq29zcXmyOJkf+X0Y1p/s3Ec0i87Hso+jb/fZp3wwcIDIV6Gt0QC6DMOF5J
         SOqH0LPlxkhg4x30ZKizFVWEA5ooZxuEPZfKqVCP1AMyvcIHalNTKCcenFUqaY+Om1nx
         zX1E+ykCzM5dcGNCwOzeXNSm/VsbUUiRxCGMWlYEKZkRNQMFvus4QZ/m/hy0WAyD4PGM
         d2A2i5oER6VyqKaQtdEvsx1S+M8wwv5ac+4VQO6qy5EfkMCEY1o55Yydzm1lkKIKJqZX
         MRINYDU4xbBZ/jjf8tOUJpwCapmTH9HBjT1N2sFO4HRnvW4nCdIFySmJ6i+BWwYRLVA8
         l5GQ==
MIME-Version: 1.0
X-Received: by 10.220.250.203 with SMTP id mp11mr22864445vcb.2.1395119713838;
 Mon, 17 Mar 2014 22:15:13 -0700 (PDT)
Received: by 10.52.0.5 with HTTP; Mon, 17 Mar 2014 22:15:13 -0700 (PDT)
In-Reply-To: 
 <CAGyVKdvikZDJkXbSiN+hiW3zn1RGY1edoW-he7PynLkRPGA=2Q@mail.gmail.com>
References: 
 <CAGyVKdvikZDJkXbSiN+hiW3zn1RGY1edoW-he7PynLkRPGA=2Q@mail.gmail.com>
Date: Mon, 17 Mar 2014 23:15:13 -0600
Message-ID: 
 <CALFpzo55OxUb67MkZ7cnZ-y0S0xiqqCM_kM1dTxxzGckcNfMVw@mail.gmail.com>
Subject: Re: upgrading from CloudPlatform 4.2.0 to CloudStack 4.3.0
From: Marcus <shadowsor@gmail.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=089e013d0502f66cb304f4da9e17
X-Virus-Checked: Checked by ClamAV on apache.org

--089e013d0502f66cb304f4da9e17
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I never did get an answer as to how those upgrade instructions are supposed
to work. I did however look at the code and we came up with our own
procedure. It's a bit messy because it involves changing the db, use at
your own risk.

1. Make changes to system vm template. save as systemvm-ver<num>.qcow2 and
upload to a place that the ssvm will be able to reach (e.g.
http://something.com/template).
2. Register new qcow2 template in cloudstack under the name/description
=E2=80=9CSystemVM Template v<num> (KVM)=E2=80=9D, with Debian 7 as the type=
.
3. Log into mysql for the cloudstack install, find the template, make note
of template id:
mysql
use cloud;
select * from vm_template where name=3D"SystemVM Template v2 (KVM)";
5. Update the template to be a SYSTEM template:mysql update vm_template set
type=3D'SYSTEM' where id=3D<id>;
=E2=96=AA New system vms will now use this template simply because it's the=
 highest
ID SYSTEM template for KVM. Existing system vms will either need to be
destroyed/recreated, or updated in the db and rebooted if you have
systemvm.recreate.enabled=3Dtrue in global settings. Here's how to update s=
o
that existing system vms will get the new template when rebooted:mysql
update vm_instance set vm_template_id=3D'<new template id>' where
vm_template_id=3D'<old template id>';
If you are unsure of the latest, you can check for the latest template in
use via:

mysql
select * from vm_instance where name like 'r-%' order by id desc limit 1;

Finally, go into cloudstack's global config and change the value of
router.template.kvm to be the name of your system vm template (e.g.
=E2=80=9CSystemVM Template v2 (KVM)=E2=80=9D). This will ensure new routers=
 use the
template.



On Mar 17, 2014 8:19 PM, "Yichi Lu" <yichi.lu@sungard.com> wrote:

> I have a problem that bothers me to no end.
> I tried to upgrade from CloudPlatform 4.2.0 to CloudStack 4.3.0. So I fir=
st
> registered a 64-bit 4.3.0 systemvm template from:
>
> http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-mas=
ter-xen.vhd.bz2
>
> this step was successful. So now I have TWO active systemvm templates. Th=
is
> can be verified from vm_template table. If now I upgrade the rpm packages
> to cloudstack 4.3.0 from CloudPlatform 4.2.0, and restart
> cloudstack-management service, I always get a 32-bit ssvm:
> root@s-1-VM:~# uname -a
> Linux s-1-VM 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux
>
> I was never able to run a 64-bit ssvm for CloudStack 4.3.0.
>
> Any suggestions/thoughts?
>
> Yichi
>

--089e013d0502f66cb304f4da9e17--