Sue Sohn stated:
< 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>
Hi Sue,
for some builds of Solaris (both s11 and s11u1) we've had to
use an AI image from a previous build to install a later build.
just want to confirm that this would still work.
Eg, for s11u1_15 we use s11u1_14's AI image to install s11u1_15.
so in the AI manifest we'd have:
<name>pkg:/entire@[email protected],5.11-0.175.1.0.0.15.0</name>
with the AI client being build 14's.
Sean.
.
<
< 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
--
Sean.
.
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
