Re: [Clockwork-developers] Decision time

[Joel L. <jo...@lo...>]

+- On Wednesday (3/13/2002 8:47) Shawn McMahon <smc...@ei...> Wrote-
| Decentralized would have "N" equal to the number of clients, I'd think.
| 
| I'm not opposed to multiple centers, I just think it only works if at
| any given moment there's unambiguous "ownership" of each job.

It occurred to me today that the "multiple centers" design is essentially
what AutoSys is in a multi-instance configuration. But the drawback of
AutoSys' multiple centers is that each has to be managed separately. Another
(less severe, perhaps) limitation is that cross-instance dependencies need
to explicitly specify the instance where the remote job lives. These two
things combined mean you need to not only manage the schedulers separately,
but design them as separate entities as well.

It doesn't seem too difficult to take the AutoSys multi-instance design
and make the management tool smart enough to talk to all the instances
behind the scenes, and present the user with one view of *all* the jobs.
And it should also be possible to devise a way to have dependencies across
instances without the user needing to specify the instance.

Wouldn't that be the best of both worlds? This question is really aimed at
Shawn Dvorak, since he was shooting for the decentralized design.

-- 
Joel