Hi Dave. On 03/ 1/11 11:53 AM, Dave Miner wrote:
On 02/18/11 07:21 PM, Jack Schwartz wrote:Hi everyone.The Derived Manifests spec has been updated.In general, when you're updating a spec, especially one that was last reviewed months ago, please have OpenOffice record changes and produce changebars in the output.
Will post.
The main changes are:1) aimanifest command syntaxAssuming this implies that 5.2.5 was the changed section, it appears from manual comparison against .91 that the change was to add "-r" to the set and add subcommands? A nit that the add synopsis doesn't include it, only the descriptive text.
Will fix. Thanks.
OK. I'll up the priority of writing the manpage, and will insert it into the doc when done. This will likely be shortly after I post code review.It seems that at this point it would be useful to write the aimanifest man page and refer to it as the primary reference for command syntax.
2) installadm list outputAssuming that the reference is to 5.3.2:- why retain the parenthetical output in the Status column? Seems that this should match with the per-service output, and also include the inactive reference - going a bit further with the prior thought, would it not make sense to provide criteria as part of the -m output without a service name? In other words, -n merely becomes a way to filter the output, not a drill-down for details? (admittedly, this is perhaps outside the bounds of this project).
Modifying list output is easy to do and can be done before push. But...From previous versions of the design doc (done before I took over the project and I thought blessed by caiman-discuss) and with discussions with the previous project owner, my understanding was that list -m without a service name was to be a "high-level" view of services offered. This is why I did not add the details of criteria and inactive manifests. Then if someone wanted the details of a particular service, they could query for them specifically.
If we are limited to only the -n flag for installadm list -m, the right answer of what to display depends on how many different manifests (and associated criteria) a service will normally have out in the field, and how many services a large lab typically supports. These things will determine how cluttered the output would become if all the details for all services are shown.
A simple yet something-for-everyone solution would be to add another flag. How about:
installadm list -m -n service -v This would map to the current implementation as follows: current new description list -m list -m all services, basic output N/A list -m -n svc specific service, basic outputN/A list -m -v all services, verbose detailed output list -m -n svc list -m -n svc -v specific service, verbose detailed output
I'll wait for the dust to settle on this before updating and re-posting the design doc.
Thanks,
Jack
DaveRevised document is available at:http://hub.opensolaris.org/bin/download/Project+caiman/DerivedManifests/DerivedManifestsDesignSpec.pdf
_______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
