There has been a fair amount of confusion stemming from the fact that the
filename used to publish a manifest with installadm add-manifest is not the same
as the name listed by installadm list or used by installadm delete-manifest and
installadm set-criteria. Instead, these subcommands use a name defined by an
attribute inside the manifest file (which is then appended with ".xml", if not
already present).
This issue is documented in:
4322 installadm list should list name of the manifest that was used for creation
12724 installadm list shouldn't append '.xml" to manifest names
6977446 name attribute of 'ai-instance' tag used as manifest filename in AI
database
To address this, the following changes are proposed:
1. Make the name attribute of the ai_instance (aka "internal name") optional
(and remove the name attribute from default.xml and ai_manifest.xml). When
publishing a manifest, if there is *no* internal name defined, the name of the
manifest will be the filename. If there *is* an internal name, the name of the
manifest will be the internal name. In either case, no ".xml" will be appended
to the name**.
** unless the name is "default" (see #2).
2. A manifest added to a service will be treated as the "default manifest" under
the following conditions:
a) The internal name is "default.xml" or "default"
b) There is no internal name, and the filename is either "default.xml" or
"default"
The default manifest will be stored as default.xml as usual in the appropriate
/var/AI/ subdirectory.
Already published manifests would not be affected by these changes.
Please provide feedback on this proposal by COB Friday, Sept. 17.
Thanks,
Sue
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
