Re: [ptp-dev] Fwd: Supporting additional remote managers

[Wyatt Spear <wspear@xxxxxxxxxxxxxx>]

Should be working in PTP 5_0 or master/head for our RM stuff?  I'm seeing some pretty significant differences on the perl side but it isn't clear which is active.

=Wyatt

On Tue, Jan 3, 2012 at 11:58 AM, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:

This is a pretty accurate summary. If Cobalt uses the same commands as PBS for monitoring, then you could just use the PBS or TORQUE schedulerType. Otherwise you'll need to write some perl (it's pretty simple). We're looking at ways to make the monitoring side more configurable also, but at some point you need to write perl (or some other scripting language).

Greg

On Dec 20, 2011, at 7:35 PM, Jeffrey Overbey wrote:

>> What more do I need to modify/add/change in order to add support for Cobalt?
>> In particular, do I need to create a new resource manager, or can I just
>> extend the perl scripts for PBS?
>
> I recently contributed support for Sun Grid Engine (Bugs 365254 and
> 365330), so maybe I can help.  Greg/Claudia/whoever can correct me if
> I'm wrong; I'm definitely not an expert on this either.
>
> Basically, there are two parts.  First, you'll want to create a
> configurable resource manager for the machine (i.e., an XML file) --
> this will let you create launch configurations so you can submit jobs
> to the machine.  Then, you'll want to create an LML driver, which
> populates the views in the System Monitoring perspective and allows
> you to monitor the status of the job after it's been submitted.
>
> The resource manager should be easy; you should be able to copy one of
> the existing XML resource manager descriptions (e.g.,
> pbs-generic-batch.xml or
> edu.illinois.ncsa.forge.pbs.batch.openmpi.xml).  The very last part of
> the XML file -- <monitor-data schedulerType="TORQUE"> -- determines
> which LML driver is used.
>
> The LML part is going to be more fun.  In the lml.da project, you
> should be able to use the existing Perl scripts for PBS as a starting
> point, although I would imagine you'll want to copy them and give your
> driver a new name (CobaltPBS or whatever).
>
> FWIW, one thing tripped me up a bit: When you change or add Perl
> scripts, you have to (1) manually rebuild the tar file in
> lml.da.server (i.e., run Ant), and (2) rm -rf ~/.eclipsesettings on
> the remote machine to force it to load and unpack the new tar file
> with the updated scripts.
>
> Jeff
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev

_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev