Hi Jan, On Thu, 30 Jul 2009, Jan Damborsky wrote:
> Hi Alok, > > > Alok Aggarwal wrote: >> >> >>>>> 3.2 >>>>> >>>>> Where do network-based AI boot and media-based AI >>>>> boot converge? In other words, when an AI client boots, >>>>> where does the knowledge in differences in boot-style end? >>>> >>>> The two converge after the service to locate a manifest >>>> to use has found a manifest to be used. The auto-installer >>>> service will subsequently invoke the installer in the same >>>> way regardless of media type. >>> >>> There's not much of a description in 3.4, but the separated >>> "manifest-locater" service shouldn't have to be media-based >>> vs. networked-based boot aware either. Is this correct? >>> In general, I think the convergence should happen as >>> early as possible. >> >> I think to a certain extent, this "manifest-locater" service >> will need to know about the boot media because in the current >> implementation, whether service discovery (/usr/bin/ai_sd and >> friends) is kicked off is a function of the boot media. >> > > > For longer term we were thinking about taking advantage > of null transport. It would be implemented by transport layer designed > as part of webserver project. That layer would be consumed by > by service/manifest discovery engine to transfer data between service > provider and consumer isolating service/amnifest discovery engine from > actual transfer mechanism. > If 'service locater' itself is provided be means of similar > mechanism we use today - as GRUB option, service/manifest discovery > engine might decompose it as necessary as pass the part > determining transport type to the transport layer as one of parameters. Thanks for clarifying. When we do the work for the null transport, we'll want to account for the bootable AI case as well. Alok
