Though not part of the AI engine at all, I do see manifest selection logic
becoming difficult for an administrator to unravel on a server with lots
of criteria. I'd suspect more than simply returning the manifest name
would be good, the client could flag it wants this output when asking for
criteria from the webserver.
I think instrumenting in usr/src/cmd/ai-webserver/AI_database.py function
findManifest(), especially in the "for crit in getCriteria" loop would be
good (perhaps returning a list of manifests eliminated during each loop
iteration.
Thank you,
Clay
On Fri, 19 Dec 2008, Alok Aggarwal wrote:
>
> On Fri, 19 Dec 2008, Ethan Quach wrote:
>
> >
> >
> > Alok Aggarwal wrote:
> >> Here is what I'm thinking of implementing in the AI engine
> >> as far as dry run functionality goes -
> >>
> >> - Parse and validate the manifest obtained from the AI
> >> webserver
> >> - Set up installation parameters based on the information
> >> in the manifest
> >> - Initiate target discovery to either select a target
> >> device specified in the manifest or pick a default target
> >> - Initiate target instantiation in dry run mode to do
> >> some sanity checking
> >> - Print out the installation parameters such as target
> >> device, IPS repo name/port, list of packages to be
> >> installed
> >>
> >
> > Just a nit but printing out which manifest from which
> > service got selected would also be useful.
>
> I believe that information is presently available in
> one of the logs (ai_sd_log I think).
>
> Alok
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>
