On Apr 14, 2012, at 3:43 PM, Alex Margolin wrote:
> On 04/15/2012 12:36 AM, Ralph Castain wrote:
>> The 1.6 branch is a stable series - no new features will be added to it, so
>> your patch won't be going there. I'd focus solely on the trunk.
> OK, but what would you recommend for benchmarking?
Nope - 1.5 is completed and will now be rotated to 1.6 in the near future. The
trunk will be branched to create the new 1.7 series, and then released this
summer. Your module can go in there, I suspect.
On Apr 14, 2012, at 4:45 PM, Alex Margolin wrote:
> On 04/15/2012 12:36 AM, Ralph Castain wr
On 04/15/2012 12:36 AM, Ralph Castain wrote:
The 1.6 branch is a stable series - no new features will be added to it, so
your patch won't be going there. I'd focus solely on the trunk.
- Can I add my module(s) to 1.5 branch? (as well as the trunk?)
What you're doing with he RAS is fine for no
On 04/15/2012 12:36 AM, Ralph Castain wrote:
The 1.6 branch is a stable series - no new features will be added to it, so
your patch won't be going there. I'd focus solely on the trunk.
OK, but what would you recommend for benchmarking? a local 1.6 checkout?
What you're doing with he RAS is fin
The 1.6 branch is a stable series - no new features will be added to it, so
your patch won't be going there. I'd focus solely on the trunk.
What you're doing with he RAS is fine for now. In the next few days, I'll be
changing the API to the RAS components, but it isn't a big change and we can
a
As to the old version: I'm working in parallel on a patch to branch 1.6
and the trunk, which (the patches, not the versions) are almost identical.
There is a minor difference in my patch for the RAS: in the trunk I used
the preexisting total_slots_alloc while in 1.6 I added it to
orte_ras_base (
Looks like you are using an old version - the trunk RAS has changed a bit. I'll
shortly be implementing further changes to support dynamic allocation requests
that might be relevant here as well.
Adding job data to the RAS base isn't a good idea - remember, multiple jobs can
be launching at the
Hi,
The next component I'm writing is a component for allocating nodes to
run the processes of an MPI job.
Suppose I have a "getbestnode" executable which not only tells me the
best location for spawning a new process,
but it also reserves the space (for some time), so that every time I run
it I
