Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Fri, 8 Mar 2013 12:20:07 -0500
From: Chip Childers <chip.childers@sungard.com>
To: cloudstack-dev@incubator.apache.org
Cc: Chiradeep Vittal <Chiradeep.Vittal@citrix.com>
Subject: Re: Using newer DIY SystemVMs
Message-ID: <20130308172007.GF70639@USLT-205755.sungardas.corp>
References: 
 <CANLSSBU6r-6xaC-oMu4KcUnYSs8DLqUG=EDEJApEizHZ8jRT=w@mail.gmail.com>
 <CALFpzo6aRJmKzavSZMD3ZM3wFAaPR7-K_DRC+Fk23acNqJpFWw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CALFpzo6aRJmKzavSZMD3ZM3wFAaPR7-K_DRC+Fk23acNqJpFWw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Thu, Mar 07, 2013 at 08:55:19PM -0700, Marcus Sorensen wrote:
> Just for confirmation, we are going to require a new system VM in 4.2 (or
> 5.0?), right? 

I believe that's the best thing to do, yes.

> What about upgrading, is there a facility for updating the
> system VM template? I know there's the global setting that rebuilds the
> system VMS on every reboot...

I think that we need to document that process.  It will at least involve
a DB change (which we should probably put into the upgrade scripts).
Then I assume that the user would need to destroy any existing system
VMs, perhaps including the VRs.

Also - we need a place to host the new system VMs.  Does Citrix (someone
that can represent Citrix) want to continue to donate that download
location?  Or do we want to circle back to infra@ (referencing the old
agreement from legal-discuss@) to ask for a place?