Greetings All,

I'm working on a specification for an Enterprise-class Open Source
batch scheduler, and I really would like some expert commentary from
experienced Ops/Systems people. Please have a look at:

http://openjcs.sourceforge.net

and the specification to date at:

http://openjcs.sourceforge.net/doc/OpenJCS-arch.pdf

Frankly, I'm of two minds about it. Half of me thinks it's massive
overkill, and the other half thinks I must be missing something really
important. Let me know what you think.

Carl

[ Post a follow-up to this message ]

carlwk...@gmail.com wrote:
>
> I'm working on a specification for an Enterprise-class Open Source
> batch scheduler, and I really would like some expert commentary from
> experienced Ops/Systems people. Please have a look at:
>
> http://openjcs.sourceforge.net
>
> and the specification to date at:
>
> http://openjcs.sourceforge.net/doc/OpenJCS-arch.pdf
>
> Frankly, I'm of two minds about it. Half of me thinks it's massive
> overkill, and the other half thinks I must be missing something really
> important. Let me know what you think.

Maestro without a GUI?  Cool beans.

[ Post a follow-up to this message ]

On May 15, 10:21 am, Doug Freyburger <dfrey...@yahoo.com> wrote:
> carlwk...@gmail.com wrote:
> 
> 
> 
> 
> 
>
> Maestro without a GUI?  Cool beans.


Well, sadly, it will eventually have a GUI, but I am firmly of the
opinion that first you do the CLI and get it really right, then do the
GUI to implement the most bacic parts of the CLI. And I'm planning on
making it a LOT more powerful than Maestro. I wrote one back in the
80s to compete with Maestro, and everyone who tried my product liked
it better. Now, I want to write something more powerful than both put
together.

[ Post a follow-up to this message ]

carl <carlwk...@gmail.com> wrote:
> Doug Freyburger <dfrey...@yahoo.com> wrote: 
> 
> 
>
> Well, sadly, it will eventually have a GUI,

I don't see that as sad at all.  CLI and GUI both have their
place.  If I want to add a printer to a UNIX box I'm happy
to use the GUI to do that.  If I want to add it to all 106
workstations currently on-line, CLI time and some loops.

> but I am firmly of the
> opinion that first you do the CLI and get it really right, then do the
> GUI to implement the most bacic parts of the CLI.

Carefully roasted, fresh ground, espresso brewed, then
refrigerated to make them cool, beans.

> And I'm planning on
> making it a LOT more powerful than Maestro.

Better for less money.  Such a choice.

> I wrote one back in the
> 80s to compete with Maestro, and everyone who tried my product liked
> it better. Now, I want to write something more powerful than both put
> together.

[ Post a follow-up to this message ]