Opendeploy Concurrency/Sequential/FIFO deployments

nickcolorado

We have a need to guarantee that opendeploy jobs run in the order in which they are called. Currently, we have different deployment definition files like ofi-content_bulk_deployment.xml and ofi-content_selective_file_deploy.xml. The ofi-content_bulk_deployment.xml job takes a bit of time (10 minutes or so) and the ofi-content_selective_file_deploy.xml job takes 30-40 seconds. We need to make sure that the bulk job finishes before the selective job is processed to ensure we don't lose changes. We are basically looking for the ability to do a FIFO order of deployments across deployments with different OD config file names.

We have enabled queueing via the odbase.xml configuration element ''. It seems that this does not help us in our situation since the queueing only seems to take effect when the deployment definition files have the same name. This configuration does provide a queue for jobs of the same name, but it seems that any jobs that are kicked off after a job is queued replace the queued job. In other words, the queue holds a max of only 1 job. Is there not a way to make the queue unlimited?

To summarize: we'd like the ability to queue jobs with different definition files and have more than one job in the queue.

OD 6.2 on Solaris.

Thanks,
Nick

Adam Stoller

I think that what you are asking for is difficult at best.
First, you don't want sender-side pending-queueing (which sounds like what you described) - you want receiver-side target-area-based queuing (which only applies if you are using transactional deployments).

In the receiver-side queuing, it's the target area that determines whether a job is queued or not, and subsequent requests to deploy to the same target area will queue up (not replace an existing item in the queue) until the currently running transactional deployment to that target area is completed -- I believe this is regardless to 'instance' name of the deployment as well as regardless of the deployment configuration name (though feel free to check the manual and/or with Support).

If you can login to the Support site - check out KB 61497 for more information