Asynchronous Deployments for Stress Testing

jajtiii

I am constructing some simple scripts to test the submission of files in a WA to STAGING, deploying to an integration/qa location and finally deploying to a prod location.

When using iwocmd, there appears to be an '-async' flag, which allows my script to continue to the next task once the 'iwodcmd' successfully starts.

Can I turn this flag on and then run my script through a loop, so that 'iwocmd start my_deployment -async' is executed multiple times in a short period of time?

My knowledge of how the 'od daemon' works is limited (I do not know if this will simply create a queue or if Solaris/TS will kick off each call when the script is run, therefor using up a ton of resources.)

Thanks in advance for your help,

jones

jed

I have not used the -async flag before, but I have used "fork" within perl to enable the invocation of multiple OD processes. If you are starting multiple OD processes, make sure that you are using a unique "inst" value for the various deployments, otherwise, you will only be able to invoke one deploy at a time. Below is a snippet of code from the script I was using to invoke multiple deployments in a short amount of time.

Note: all the output goes to STDOUT. You will probably want to log all output to a file.

for($i=$ARGV[0];$i<$ARGV[1];$i++){
    # args split for readability
    my $cmd="/OpenDeployNG/bin/iwodcmd start wft_filelist_test -inst $i 
                    -k area=<my-area> 
                    -k filelist=<my-filelist>";
    print "$cmd\n";
    #cmd($cmd);
    sleep 1;
}

# run the backend process to update the source > target
sub cmd{
    my($cmd)=@_;

    $SIG{INT} = 'IGNORE';  # c 'turn undead' zombies
    unless(fork) {
        open STDIN,  "</dev/null";
        open STDOUT, ">/dev/null";
        exec("$cmd");
        exit;  # This block only executes if we're the child, so exit when we're done.
    }
}

--
Jed Michnowicz
jedm@sun.com
Content Management Engineer
Sun Microsystems