For the LDoms Manager we currently ship a single version as the
'ldomsmanager' IPS package. This version supports all current hardware
from T2 to T4. We have a requirement to be able to ship multiple
versions of LDoms Manager in order to support future platforms which
will not run on the current version of LDoms Manager, while still
allowing customers with existing systems to run the current version of
LDoms Manager. This could be done by delivering multiple
ldomsmanager-<version> packages that deliver their files in versioned
paths and using mediated links to select the version to run. Since
ldomsmanager is in the default Solaris software payload, a fresh install
of Solaris should result in the most appropriate version of LDoms
Mananager being selected by default.
However, the current implementation of mediators does not offer us a way
to select the best version based on the hardware platform it is
installed on. E.g. for T2 systems version 2.1 should be selected, while
a future platform would require some version greater than 2.1. Setting
mediator-priority to higher values in later versions of the
ldomsmanager-<version> packages would not help since that would select a
version not supporting T2 systems if later versions were installed.
Would there be value in filing a RFE to extend the mediator mechanism to
allow more specific control or is there a better IPS mechanism to do
this?. (There are no platform-specific packages we could declare a
dependency on). The alternative would be to deliver a run-once service
ourselves (in a generic ldoms package) that would determine the most
appropriate version from those installed and run pkg set-mediator during
self-assembly to set that version as default.
Thoughts?
Menno
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
