* Keith Mitchell (Keith.Mitchell at Sun.COM) wrote: > Hi Glenn, > > Some comments of my own: > > Sec 1.4.1 >> - Provide observibility to the Distribution Constructor for the >> purpose of progress reporting, install status and error reporting > "to the Distribution Constructor" seems to specific, implying that the > image must communicate directly to the DC. The installer just needs to > provide status and error reporting that would be accessible to a remote > process.
I agree. The remote process however will be DC. But that's semantics. > Sec 1.5 >> Network access to an IPS repository (for generating the AI image or >> for installing the VM with) > This should be "either access to an IPS repository, or an installable > ISO image" I think. Yes and no. It depends on the design for the bootable AI image. If that image contains everything you're going to install (as it does today) then we only need access to an IPS repository when we're constructing that image and not during the actual installation. If however the AI image is just a 'skeleton' image that boots and starts an install but pulls the bits from a repo, then the VM will need access to an IPS repo. I don't think I have a preference either way really. Though there may be some issues with very large bootable AI images, but I believe any known issues Dave already has a patch for (clofi issue with archives greater than 4gb). Thanks! -- Glenn
