Another category just mentioned is:
node-monitor -- ex. PBS, Warehouse, ...
Another proposed name for this was "node-manager" but I feel that "manager"
implies action and therefore control over the node's state, where
monitoring info as provided by Warehouse system-monitor or the pbm_mom
doesn't control the node's state.
Something else actually controls that node...well maybe depending on how
advanced the cluster management system is. ;) My preferred, and as I
interpret matters, the current SSS layout is to use a Node State Manager
that fills the role of "node-manager".
Anyway, more SSS info that most will care to hear but the new category
seems appropriate.
--tjn
PS Anyone have strong feelings between "queue-manager" & "QueueManager"
formatting?
PSS Revised list,
node-monitor -- ex. PBS, Warehouse, ...
mpi -- ex, LAM, MPICH <<already in use>>
switcher -- ex, Env-Switcher <<sort of odd case, already in use>>
allocation-mananger -- ex, Gold, QBank, ???
scheduler -- ex, MAUI
queue-manager -- ex, Bamboo, PBS
process-manager -- ex, MPD
job-manager -- ex, MPD?, Bamboo?
meta-scheduler -- ex, Silver?
meta-manager -- ex, ?<not sure on this one>? :)
_________________________________________________________________________
Thomas Naughton [EMAIL PROTECTED]
Research Associate (865) 576-4184
On Wed, 25 Feb 2004, Thomas Naughton wrote:
>
> On Wed, 25 Feb 2004, Jason Brechin wrote:
>
> > > The following list shows the proposed list, including some that already
> > > exist as well as a couple of examples where these would be used.
> > >
> > > mpi -- ex, LAM, MPICH <<already in use>>
> > > switcher -- ex, Env-Switcher <<sort of odd case, already in use>>
> > > allocation-mananger -- ex, Gold, QBank, ???
> > > scheduler -- ex, MAUI
> > > queue-manager -- ex, Bamboo, PBS
> > > process-manager -- ex, MPD
> > > job-manager -- ex, MPD?, Bamboo?
> > > meta-scheduler -- ex, Silver?
> > > meta-manager -- ex, ?<not sure on this one>? :)
> >
> > It seems fine on the surface... it's mostly defined as we start using
> > them and writing code to deal with multiple mpis or schedulers. For the
> > most part, these names seem suitable.
>
> I based them off of the identified components in the SSS spec. It will
> make since to them and hopefully most others dealing with these sorts of
> system services.
>
>
> > > Lastly, it makes since that a package might have multiple <provides>. The
> > > example I think of is PBS providing <queue-manager>, <process-manager> and
> > > <scheduler> all in one package. I'm not sure if we can handle multiple
> > > <provides> / <requires> blocks or if the element can have multple
> > > sub-elements but this will also need to be honored for this to work
> > > fully.
> >
> > This is already handled in oda AFAIK. Specify as many provides requires
> > or conflicts as you want.
>
> Excellent! That's what I was hoping to hear. Question, where are these
> actual dependence issues dealt with? In Selector? If so, are they
> seperated from the gui code?
>
> thanks,
> --tjn
>
> _________________________________________________________________________
> Thomas Naughton [EMAIL PROTECTED]
> Research Associate (865) 576-4184
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Oscar-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/oscar-devel
>
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
