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. > and we just need to call those or something like that. Since this same > functionality is needed by the GUI and Text Installer as well, probably > a program/function can be implemented and all the components that > needed the info can use that. Then, VMC can take the list of packages > specified by the deployer for the VM image, and figure out the needed size > for the disk. See above. Cheers, -- Shawn Walker
