On 07/12/10 01:57 PM, jean.mccormack wrote:
On 07/12/10 01:50 PM, Sarah Jelinek wrote:
On 07/12/10 01:33 PM, jean.mccormack wrote:
It would look something like this:
<software_spec>
<destination>
<image ips_search_index="true">
</destination>
<software>
...
</software>
<software_spec>
The idea is that the generation of the ips search index is an
attribute on the IPS image we are creating as part of the DC process.
I believe that should work. Thanks
Sorry, after really looking at this I need the ips/cpio arguments to
fall under software, reason being that these
arguments can and often will change within a checkpoint but
different transfers within. Best served by an example....
In a checkpoint I really want to transfer via cpio files from:
/usr/bin with default cpio args
/usr/lib with cpio args "-pdm"
/usr/whatever with default cpio args.
Are these args something the user should have control over? Are these
set in the application?
Possibly? But ips_search_index also falls into the category of I would
like it under software. All the IPS ones do.
In fact, you have 3 types of IPS argument lists, one for creation of
the image, one for pkg installing and one for
pkg uninstalling. So if a checkpoint does a image
create/install/uninstall that is 1 software_spec node but 3
software nodes.
yes, you are correct. But, in the case of 'create' the 'install' action
will create the image, using the image attributes if one is not created,
right? And, in the case of uninstall, what are the ips attributes you
would want to specify that are not specified in the initial image
settings? It seems to me that if you said --no-index for the create then
you wouldn't want to update the index for the remove, would you?
Multiple actions can be applied to an ips image, and the initial setting
of the image attributes applies to all actions associated with the
image. The action tells the checkpoint what packages apply for that
action. So, the checkpoint would have to get all the software with an
action of say 'uninstall'.
How do I know which one to apply the arguments listed in image to? The
idea behind these arguments
is that I'm not supposed to have to be aware of what arguments there
are, just pass them through to IPS.
Yes, I agree. But, if you look at how I have encapsulated the elements
and attributes, a software_spec element applies to one image at a time,
and anything to do with other images must be enclosed in a new
software_spec element. The attributes you are referring to are image
attributes not software attributes.
And in reply to your email I just got:
"Actually.. wouldn't these values be a set of args to the Checkpoint?
The checkpoint element has an args element which is parsed character
data. I would think that the arguments for something like this would
be specified here."
No for the same reason as above. They really need to not be checkpoint
specific but rather which actual transfer you're doing specific, the
key being I may do n transfers/checkpoint.
So, in terms of the cpio args, who has the ability to change these? Does
the user? Or is this an application specific thing?
thanks,
sarah
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
