Derived_Manifests_1

Hi everyone.

My push of the Derived Manifests project to slim_source (changeset 1087) adds new AI manifest management to the installadm command.  Now implemented are:

Default manifests are now managed by an SMF property.

There is support for Derived Manifests (DM) scripts.  Python or ksh93 DM scripts can be registered with a service just as an XML manifest can.  (Note, however, that until AI-CUD integrates there is not client support for this feature.  More will be said about this in a future heads-up.)

Any manifest or DM script can be set up as the service's default now. If a manifest or script with criteria associated with it is designated the default, those criteria are ignored.  If a manifest or script without criteria is un-designated as the default, it becomes inactive.

New installadm commands

Here are new installadm commands added as part of this manifest handling.  Please see type installadm with no arguments to see the complete usage of all installadm commands.

installadm add-manifest -d

Allows one to add a new manifest or script as the default.

installadm set-service -o default-manifest=<new-default-manifest>

Specify a service's pre-existing manifest or script to be the new default.

installadm update-manifest

Install a new version of a manifest or script (as from an external file) while leaving intact all  criteria associated with that manifest or script.

installadm export -m

Export to the screen or a file, one or more manifests and/or scripts.

installadm list -m

Enhanced listing of manifests and scripts show which are default and have ignored criteria, and which are inactive.

Bugs

Handling of existing default.xml manifests from old services is a known issue (7038729) and will be fixed before build 165 closes.

Please file bugs against solaris/install/installadm in bugster and direct any questions or comments to me.

        Enjoy,
        Jack