Hi Sarah, On Fri, 31 Jul 2009, Sarah Jelinek 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. > > I am concerned about each service doing something different based on the type > of install media. Why would the services have to know about the install > media? Can you give examples of what you are planning with regard to this. > > Seems to me we have two services as you note: > > ai client > service discovery(which is really manifest discovery). > > Those things must happen regardless of installation media, correct? The Correct. > service discovery part doesn't strictly have to run since we haven't setup a > service, but making this more generic and utilizing the plans in the > transport project for a NULL transport mechanism, it seems to me we could > abstract the manifest discovery out in a way that the install media type > doesn't matter. > > My concern about having the services know how they are booted(which is what I > assume you are referring to), really makes extending these to add new > features possibly less than ideal. > > Can you clarify you plans in this regard? Ethan had a similar concern. He and I talked yesterday, I now understand the need to have the "manifest locater" service be boot media agnostic. As I start working on the code, I'll have more details on how exactly the service will work and we can then talk about whether it is extensible. Alok
