Hi - I've had some questions come up while working on the use cases.
With AI, after the client pxeboots, this is what the client does: 1. Requests and receives solaris.zlib file 2. Requests and receives solarismisc.zlib file 3. Requests and receives configuration files (install.conf - sparc, .imageinfo - x86) 4. Executes SMF method auto-installer. Requests and receives AI manifest Yesterday, we talked about the solution proposal - User supplies a base manifest with derived pieces that need to be filled in. A file providing code snippets and the manifest will be passed to the client. A manifest service will call into the code snippet file and fill in the manifest. Where do these pieces fit in with the current AI? Here is my guess: 1. Client requests and receives solaris.zlib file from server 2. Client requests and receives solarismisc.zlib file from server 3. I'm not sure about step 3, because we talked about having derived config files. 4. Manifest Service starts, requests and receives base manifest and code snippet file from server 5. Client executes code snippet file and base manifest is filled in 6. Client executes auto-installer method; auto-installer requests and receives the base manifest with the newly added info. (This is on the client, since it has been derived). Am I on track here? I'm a little confused about the manifest service/auto-installer interaction. thanks, ginnie -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090609/d24dcb2e/attachment.html>
