William,
This below is, to some extent, the crux of the issue in my mind:
AI client changes: 5.7.2.2 Boot process - describes what has to
happen on the AI client side. Will add description of AI client
script to fetch the profiles (getting criteria, http
request/response, handling multiple profiles). Some implementation
details are still to be decided (request URL determination, wanboot
interaction).
This definitely needs fleshing out. I was unclear as to why a second
request, with seemingly similar (if not identical) input, is required
to obtain the configuration manifest.
One of the project requirements is to decouple AI manifests from SC
profiles. I take this as meaning the fetching process as well.
Decoupling, in terms of requirements, means to ensure that the
*management* of the configuration profile(s) becomes independent of the
management of the AI manifests, thus removing the existing 1-1
relationship that is a result of delivering the configuration profile as
a section (a comment, right now) of the AI manifest.
Delivering them simultaneously is perfectly fine, and as you can gather,
I think preferable. My point of view is that wanboot-cgi has a quite
suitable method already for delivering a bundle of content and would
like to see that leveraged, rather than inventing yet another mechanism
that is specific to system configuration.
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
