ay, December 28, 2012 10:31 AM
>To: cloudstack-dev@incubator.apache.org
>Subject: RE: [DISCUSS] Virtual machine's Base Image Updatation Facility
>
>
>
>> -Original Message-
>> From: David Nalley [mailto:da...@gnsa.us]
>> Sent: Thursday, December 27, 2012 7:40 A
@incubator.apache.org
Subject: RE: [DISCUSS] Virtual machine's Base Image Updatation Facility
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Thursday, December 27, 2012 7:40 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUS
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Thursday, December 27, 2012 7:40 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Virtual machine's Base Image Updatation Facility
>
> On Wed, Dec 26, 2012 at 3:47 PM,
The JEOS approach does not work well with Windows. Specifically patch
management / gold image management with desktop vms where there is a high
density of vms with the same base image (say Win7). It is more economical
and easier to "discard" the unpatched / previous image than to maintain
patches o
On Wed, Dec 26, 2012 at 3:47 PM, Chiradeep Vittal
wrote:
> Templates should be immutable --if there is a new version created, then it
> is another template.
> The api should just take a reference to the new template and not try to
> deal with trickiness around updating templates. That workflow (ve
What might be interesting is to integrate Cobbler with ACS...
John
On Dec 25, 2012, at 10:48 PM, Harikrishna Patnala
wrote:
> When a user tries to create VM, following sequence of events happen with
> current CloudStack implementation
>
>
> (1)User / admin adds a template (which is stor
Templates should be immutable --if there is a new version created, then it
is another template.
The api should just take a reference to the new template and not try to
deal with trickiness around updating templates. That workflow (versioning
templates) is a different ball of wax entirely.
On 12/25
Hi Hari,
My comments inline.
On 26-Dec-2012, at 12:18 PM, Harikrishna Patnala wrote:
> When a user tries to create VM, following sequence of events happen with
> current CloudStack implementation
>
>
> (1)User / admin adds a template (which is stored on secondary storage)
>
> (2)Temp
