* Dave Miner (Dave.Miner at Sun.COM) wrote: >> It is interesting you point this out. Glenn and Keith and I were >> talking about how folks could get bits into the VM image. The current >> way would be to get the bits into an IPS repo. >> >> but I was thinking it could be valuable to have the AI engine, in >> addition to pulling bits from IPS also have exra bits built into it by >> DC. >> >> This way if a customer would like to do a custom AI install, or VMC, >> with bits they develop, they would not have to push there bits to an >> IPS for AI to pull from. >> >> We could provide some, as yet to be defined, method of adding some bits >> to an AI image that could be copied from the image via CPIO after the >> IPS transfer. >> >> This would provide an easy way for folks to add custom bits to am AI image. >> > > I'd think that the most common need for additional, non-IPS content, > would be SVR4 packages. Beyond that, I'd expect to see requests to > support tarballs, debian-format packages from the Nexenta repositories > perhaps, RPM's since there have been Solaris RPM packages used in some > communities. > > Note that these requirements are not specific to the VM constructor, but > apply to automated installation in general...
That was my thought as well Dave. Since we're going to use the AI client technology, customizing the payload for a Virtual Machine has to be possible in that context. Which means that phase 0 of VM construction is going to be pretty limited in that regard. -- Glenn
