On 05/11/10 04:45 PM, Alok Aggarwal wrote:
On Tue, 11 May 2010, Keith Mitchell wrote:
On 05/11/10 03:53 PM, Alok Aggarwal wrote:
Hi Darren,
I'm looking into converting DC over to the engine
prototype that you guys worked on. And, I've run
into an interesting problem -
A number of the DC checkpoints are implemented as
ksh scripts. That brings up the question of a) Can
the engine register shell scripts as checkpoints?
and, b) Is there a way these scripts can talk to
the DOC (which is a python object)?
(b) is needed because these scripts need certain
values out of the DOC in order to perform their
function.
I had initially planned on wrapping these shell scripts in python
program that interact with the DOC, extract the needed values out of
it and invoke the shell script with those values as arguments. However,
that can become quite cumbersome for scripts that
look up more than a handful value and/or deal with
variable number of arguments. So, I'm looking for
an alternate approach.
Since the DOC can register multiple things to the same "name" (the
items get added as a list), could you simply add the series of
arguments as "some_checkpoint_argv" in order by DC, then have the
checkpoint pull those out, and execute the shell by passing those
arguments? I believe the eventual desire is that the finalizers are
all implemented in Python, but for a prototype, this seems like it
would be sufficient. Or is there another interaction component for
some finalizers that I'm glossing over?
That was my initial thought as well. But it may not
work as easily for some finalizers without additional
hackery.
Take for instance, boot_archive_configure. That script
pulls out a list of service profiles to apply and that
list can be arbitrary length. Sure, the length could
be hard coded for the purposes of the prototype but I'm
just wondering if there's a generic way get the list
out of the DOC from the finalier.
How are these service profiles specified today? In the manifest?
However, it may just be a moot point given that we don't
expect such a mechanism to be of any use in the final
product since we expect even the end-user supplied checkpoints to
implement the checkpoint class (and be in
python as a result).
Alok
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
