On 02/19/10 05:43 PM, Dave Miner wrote: > Thanks for the comments on the revised image management spec. I've > published a revision that captures the discussion; of particular note > are links to an updated man page and diffs against the existing page. > > http://hub.opensolaris.org/bin/view/Project+caiman/AI+Image+Management
Something I just thought of today: "In defining a solution, we note that controlling the pkg(5) repository contents effectively controls the software made available for installation by the AI clients. As such, customers of any scale can be expected to deploy their own local mirrors of Sun's release and support repositories and select the versions published to aid in change management." While an administrator could rely on the contents of a repository for change management, I suspect that could lead to unpleasant surprises. The best way to control what OS build is installed is probably by specifying a build for the incorporation that will constrain the system (e.g. entire at 0.5.11,5.11-0.133). Since the system incorporation (e.g. entire) is the first package that is installed, all subsequent packages should be constrained to that same version. Of course, controlling the contents of the repository is a necessity for the image-update case and when considering the availability of new OS releases. Cheers, -- Shawn Walker
