[caiman-discuss] Draft Design Document for Virtual Machine Constructor now available

[Shawn Walker]

B J Wahl wrote:
> On Mon, Aug 03, 2009 at 06:48:17PM -0500, Shawn Walker wrote:
>> Karen Tung wrote:
>>> Glenn Lagasse wrote:
>>>> No.  The AI client (though I haven't found it yet) has I believe some
>>>> idea of what it requires in order to work in terms of client memory.
>>>> So, for installing the VM we'll set the memory to that required size.
>>>> After the VM is installed, we'll allow the user to set the memory size
>>>> of the VM to whatever value he wants to deploy the VM with.
>>>>
>>>> The disk size is a different problem.  If we were using something like
>>>> the liveCD that includes the image size we could use that, but we don't.
>>>> I know there's been discussion about getting IPS to deliver some sort of
>>>> interface for figuring out how big an installed set of packages is but I
>>>> don't think there's anything imminent there.  For now, the deployer will
>>>> need to have an idea of how much disk space he needs inside the VM in
>>>> order to set it.
>>>>   
>>> When we talk with the IPS group a couple of weeks ago, I believe
>>> they said that the functionality is already available in the API level,
>> Not yet.  But it should be delivered within the next month or two.
> 
> The suggestion was to use the same approach the IPS GUI guys are using 
> to estimate the package sizes.

As far as I know, they don't estimate sizes.  You can call the info() 
method to obtain a 'size' -- but that reflects the installed size for 
installed packages, or the size of the not-yet-installed packages based 
on the current image's variants, etc.  Doing that in installation 
context is a bit of a different animal.

-- 
Shawn Walker