I haven't had a chance to read the proposal yet, but wanted to comment on
one thing in particular.
On 03/31/10 07:57 AM, Rainer Orth wrote:
There's certainly the problem of assembling the manifests from pieces.
It doesn't only apply to the SC manifest/SMF profile, but also to the AI
manifest, where the target part most likely cannot be site-wide (some
system disks are mirrored when this becomes supported, others are not;
some machines get a minimal set of packages, others are used as Sun Ray
servers and need much more; the list goes on).
I can imagine two solutions:
* Assemble the fragments on the client. The problem here is that
whenever I change one single fragment, all dependent manifests have to
be regenerted and re-added. Right now, this is even worse: you cannot
replace an existing manifest by an updated one, but first have to
delete and then re-add it.
I'd very much like to explore the installers delivering a directory of
profile fragments and having SMF assemble them on boot.
The SMF team has long wanted profiles to be able to be directories. We
have compatibility problems to address for doing this with existing
profiles, but the general implementation to be able to apply a set of
profiles from a directory would be very straightforward.
* On the other hand, you could have the AI server do the assembling,
maybe via XML's include facilities. While this has some charme, I
wonder how manageable such a solution would be.
I think I agree -- includes are charming in terms of selecting different
capabilities at runtime, but are less so from a deployment perspective of
assembling many disparate parts.
liane
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
