On Fri, 31 Jul 2009, Joseph J. VLcek wrote: >>> Issue 2: >>> -------- >>> >>> 3.3 live-fs-root SMF service refactoring >>> and >>> 3.4 auto-installer service refactoring >>> >>> Can you please elaborate a bit on what will be done. >> >> The live-fs-root service is currently a dumping ground for >> all sorts of install media and variety of installers (LiveCD, >> AI, etc). As we add more installers, it will only become >> more complex and unwieldy. >> >> I intend to separate out the logic in that service into two >> services where each of the service does things a little differently based >> on the type of install media (network or >> cdrom/dvd/usb). >> >> As for the auto-installer service, it currently performs the >> dual function of doing service discovery to locate an install >> manifest and also invoking the auto-install binary. >> >> With media based boot, the service discovery doesn't need to >> run. So, while I'm adding more logic to the auto-installer >> service, it makes sense to separate out the "locating the manifest" >> part from "invoking auto-install" part. That would provide for >> better fault tolerance as well as easier extensibility when >> derived manifests get added to AI. > > > OK thanks. Could this description be included in the Bootable AI Image Spec?
Sure, I'll add it. >>> Issue 6: >>> -------- >>> >>> The VMC requires the Bootable AI Client to "shutdown" the system >>> after the install, for both successful installation and installs >>> the produced failures. >> >> I think this needs to be filed as an rfe and tracked separately. > > > I disagree. The requirement for the Bootable AI Client to shutdown was > something we talked about for the bootable AI Client right from the start. > It must be provided for in order for VMC to work. It appears the existing reboot functionality is implemented from within the auto-installer service. Since I'm touching that service anyway, I'll add shutting down the service to the list of tasks. Alok
