Hey Keith, * Keith Mitchell (Keith.Mitchell at Sun.COM) wrote: > > > Karen Tung wrote: >> Glenn Lagasse wrote: >>> Hi All, >>> >>> I've uploaded the functional specification for this project to be >>> reviewed at: >>> >>> http://opensolaris.org/os/project/caiman/VMC >>> >>> For anyone who doesn't know, the VM Constructor project is intended to >>> enhance the distribution constructor to allow it to create preconfigured >>> and preinstalled virtual machines which can be used by VirtualBox (and >>> any other hypervisors that support and can consume OVF images). >>> >>> Please direct any feedback to this alias/thread. >>> >>> Thanks! >>> >>> >> Section 1.6: >> Why specially define the term "deployer" in this case? Wouldn't "DC >> user" work? >> From the DC users' point of view, it's just another image type that >> they can create. >> >> Section 3.0: >> You mentioned that the user can manifest is for DC to create a >> bootable AI image and create and configure >> the VM. I think the part about creating a bootable AI image is an >> implementation detail, which they >> shouldn't have to know about. >> From the user's point of view, all they care is that they can specify >> a list of packages, and perhaps a few >> attributes of the resulting VM, and DC will do all the work to put >> those packages into this VM. > I think it's worth mentioning that some form of ISO is created, since we > are supporting the case where the user supplies an already created ISO. > Perhaps the wording should be changed, though?
Yeah, I just thought of that after hitting send on my response to Karen. I'm not sure how we can word this yet. I'll give it some thought. >> >> Section 5.1: >> After the ICTs, would there be a need to reboot the VM somehow so some >> of the first boot setups >> are run? That way, when people boot up their VM image, they don't >> have to waste the time >> to wait. > That's a good point. Glenn, do you know if we can export an OVF of a > "paused" VM? Then we could boot -> install -> reboot -> pause -> export, > so that the receiver of the OVF could start it up more rapidly (or the > creator could start it up, configure additional items within OpenSolaris > as desired, and then repackage and export). See my response to Karen. But I don't think we want to shield the user of the VM from the bootup process. They should see what's happening when you boot OpenSolaris imo. This way they can see how the whole thing works, from initial boot after installation on up. Thanks! -- Glenn
