Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of shadowsor@gmail.com designates
 209.85.220.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKprHVaJB7SWFmgJaMA=cyVbFrkdFgL696+hAgfVBb90KXy7_w@mail.gmail.com>
References: 
 <7914B38A4445B34AA16EB9F1352942F101435C4F132D@SJCPMAILBOX01.citrite.net>
	<44B61608130E8C44ABA956373E8251DD027AEF@SINPEX01CL03.citrite.net>
	<CALFpzo5yzj1xDeGkz0pSHsjGnG-aKPfXQqBxzbqCcWsBBRLeoA@mail.gmail.com>
	<7914B38A4445B34AA16EB9F1352942F101435C71FFBF@SJCPMAILBOX01.citrite.net>
	<CALFpzo69cT4hbQJMcNBe=r1A9egbd=o-NDsqgV7oJGnrc3e-jQ@mail.gmail.com>
	<6E004C34C1C59E45A35B4338808BC31501445CCC1542@SJCPMAILBOX01.citrite.net>
	<20130328021612.GM53904@USLT-205755.sungardas.corp>
	<CAKprHVaJB7SWFmgJaMA=cyVbFrkdFgL696+hAgfVBb90KXy7_w@mail.gmail.com>
Date: Wed, 27 Mar 2013 21:04:07 -0600
Message-ID: 
 <CALFpzo7q_BpZ_q7NDWHNpON=k1AUphi9tF=d2tApw5fk31MORQ@mail.gmail.com>
Subject: Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1
From: Marcus Sorensen <shadowsor@gmail.com>
To: dev@cloudstack.apache.org
Cc: Sangeetha Hariharan <Sangeetha.Hariharan@citrix.com>
Content-Type: multipart/alternative; boundary=20cf3071cc966c71fc04d8f3683e

--20cf3071cc966c71fc04d8f3683e
Content-Type: text/plain; charset=ISO-8859-1

There are two things, upgrade of system VM, and upgrade of software on
system VM. Any time you start a system VM the latest scripts get copied to
it. This isn't the same as using the new ipv6 template. I can understand
needing to reboot the system VMS if the scripts change, but its not the
same as upgrading the OS in the system VM.
On Mar 27, 2013 8:59 PM, "David Nalley" <david@gnsa.us> wrote:

> >> Deploying Vms in existing networks succeed. But Vms are not given any
> ip address.
> >> In router, I see that the mac address of the Vm is not populated
> correctly.
> >> root@r-4-VM:~# cat /etc/dhcphosts.txt
> >> 02:00:42:47:00:01,set:10_1_1_17,10.1.1.17,test123,infinite
> >> -4,set:10_1_1_195,10.1.1.195,-m,infinite
> >> root@r-4-VM:~#
> >>
> >> After stopping and starting of the existing routers , Vm deployment
> succeeds.
> >>
> >> Seems like all the routers need to be stopped and started after upgrade.
> >
> > Forgive the question, but I actually haven't upgraded a production
> > environment yet!  Is this normal to have to restart the VR's after a
> > major update?  I *think* I remember that this is, but I just want to
> > confirm.
> >
>
> So it's expected if we change the sysvms materially - but I would have
> expected them to have continued working.
> That said, I thought update of sysvms was optional and only necessary
> if you wanted IPv6-enabled system VMs.
> Can someone canonically answer this? Things like this will affect
> install documentation.
>

--20cf3071cc966c71fc04d8f3683e--