On 09/13/10 12:33 PM, Sue Sohn wrote:
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
What I would like (and maybe already exists but I missed it) is to be
able to say what the manifest name on the command line.
What I do now is have a script that reads the manifest and does some
minimal amount of processing - right now part of that processing is to
update the manifest name to be something usable. However, since the
script is doing this and is just make a temp file, the resulted file is
/tmp/ai_manifest_<pid of process> - that is really useless as a manifest
also.
The main issue I'm having here is this:
I let users add custom manifests for clients they are installing, but
the script that wraps around it uses the -c to set the criteria.
If another person goes and uses that same machine, I want to remove that
manifest so that the default is used- however, to do so, I need to know
what it is called.
So my solution right now is to name the manifest ai_<ip_addr> - in
that way, if I have the hostname, I know the ip address and can see if
there is a manifest that needs to be removed.
What would be handy here:
1) Something like 'installadm delete-manifest -n <service> -c
<criteria>' where that criteria is same as was used for add - in that
case, I care less what the manifest is called as I can then just put in
the same criteria as I used when adding it.
2) Related to that, have installadm list -m have some option to show
what criteria is used for each manifest - I'm getting around this right
now by using the ip address in the manifest name. It seems like
installadm knows this, as if I try to add a new manifest for a system
that already has one set up, it will generate an error about the conflict.
3) Have an option to add-manifest for it to use that as the manifest
name instead of pulling it either out of the file name or using the file
itself.
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
