nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Simultaneous deploys using same deploy definition?

System

Using OpenDeploy 5.5.2, we have created our whole deployment structure as a set of ksh scripts. We use parameter substitution extensively, and as a result have some 'generic' deploy configurations that we can call from multiple scripts.

We used to (with OD 4.5.x) be able to have multiple deploys running against the same definitions -- we managed to pound our deploy server with over 18 simultaneous deploys, one for each of our european locales. Load average hit 13 on a 2 CPU Sun E450 (geek cool! :-)

With OD 5.5.2, any deploy that executes a configuration that is already running errors out, indicating the config is already in use. As a result, our deploy process now takes significantly longer since we have to execute each deployment in sequence.

The 'pendSession' parameter doesn't seem that helpful, since it only queues one more deploy.

Any other options on this? We'd prefer not to create 20-some identical deployment configurations and then have to keep them all in sync.

Find more posts tagged with

Comments

Migrateduser

With OpenDeploy 5.5.1, you can run multiple deployments with the same name simultaneously using the -inst flag on the iwodstart command.

For example:

iwodstart mydeploy -inst aaa -k "mykey=value1'

Now while that one is running, do:

iwodstart mydeploy -inst bbb -k "mykey=value2'

Todd Scallan
Senior Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

Thanks Tom!

MikeMoretti

Does this only work for OD 5.5.1? Or does it work for 5.0.1 also? We have the exact same problem with OD 5.0.1.

Thanks!
-Mike Moretti

Adam Stoller

How's it goin' Mike?

I believe '-inst' existed in 5.0.1 (though I truly do not remember) - one would hope the usage information would tell you, but I do remember that there was a lot of usage cleanup done for the CLT's in 5.5.1 so it's possible it might support it and not tell you. At this point, unless you can get a definitive response from someone who has 5.0.1 - I'd go with empirical evidence: Try it and see.

Of course upgrading to 5.6 would be a good choice too....

--fish
(Interwoven Senior Technical Consultant)

MikeMoretti

How ya doin Adam?

-inst works great in 5.0.1. Thanks!
The only thing I don't like about it is that it creates new log files for each deployment (because the deployment name is now whatever the config file name is plus whatever comes after -inst).

-Mike

output.afp

Adam Stoller

That's kind of necessary - otherwise the logs of two conccurently running deployments would get mixed together making it impossible to track what happened in which deployment - or worse, output would get lost because the writes to the logfile could collide and one process could overwrite the other's before the data was saved. Not desirable.

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

does the <initatorProperties pendSession="yes" /> allowing for the queueing of more than a 2nd occurance (say 4 or 5) or not?

Adam Stoller

No - it only allows for the last requested deployment of an already running deployment to wait until the currently running deployment is finished. Thus it is only advisable to use this option for sourceFilesystem non-filelist deployments. For anything else, you'll want to use the '-inst instname' parameter to allow concurrent deployments of varying content to be deployed (this too is subject to potential issues with regard to transactional deployments - as you might try to clobber the same file.iwnew file....)

So - I'd recommend against using '-inst' with transactional deployments and against using pendSessions with sourceTeamsite and filelist deployments.

I believe "true queueing" of deploymens is already registered as a feature request - contact Interwoven Support to verify, add your name, or create it if it isn't there.

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

Feature request number is 39129.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com