Hi Mark,
Though, not a slick interface and subject to change, but if it
helps you, you can determine the manifest used for a particular client:
First, go to http://<server>:<port>/mainfest.html
Second, in the text box provide the criteria requested (the criteria under
"Criteria:"). Follow the format in the example at top.
Lastly, submit the data. Upon submission the server will redirect you to
download the particular manifest by its name.
(For a pragmatic approach you can use http://<server>:<port>/manifest.xml
too and use the same XML format an AI client uses.)
On Mon, 13 Sep 2010, mwedel wrote:
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.
That's an interesting idea.
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.
Does installadm not provide that information now? I see the following:
ad...@osai-brm-x-1:/tmp$ installadm list -n install_test_ai_x86 -m
Manifest Criteria
-------- --------
foobar.xml mac = C0:FF:EE:C0:FF:EE
Thank you,
Clay
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
