Booting from an AI service can result in different Solaris versions being
installed on the client. This can happen if the service uses a manifest, such as
the current default AI manifest, that installs:
pkg:/entire@latest
The release of solaris installed by that service matches the latest version in
the repo, which can change over time. For example, when S11.1 comes out, an AI
service that previously was installing S11 FCS will start installing S11.1.
Similarly for S11.2, etc.
While some users may desire this behavior, others may prefer to have the version
installed remain tied to that of the AI client image, as this is what the image
officially supports installing (see 7144329, "default manifest for services
should constrain entire@version, not entire@latest"). To implement this
functionality, the following changes are proposed:
Introduce a new <software_data> <name> element attribute into software.dtd,
use_system_version, that instructs the client to install the same version (minus
the timestamp) of that package as found on the running system (the AI client in
this case). The default value of use_system_version will be "false". The default
AI manifest would change from having:
<name>pkg:/entire@latest</name>
to
<name use_system_version="true">pkg:/entire</name>
For those users who wish to retain the current behavior of having the latest
version installed, the manifest entry would need to be modified to:
<name>pkg:/entire@latest</name>
Note that this proposal addresses the issue going forward. Services created with
the S11 installadm tools will exhibit the "rolling release" behavior described
above.
Please provide feedback on this proposal by COB Monday, June 11.
Thanks,
Sue
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
