Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-26 Thread Josh Hursey
On the telconf today we discussed names and decided on: ORCA: Open MPI Runtime Collaborative Abstraction I will commit this to the trunk this evening. It is a -BIG- commit to the OMPI and ORTE layers so I am going to need some quiet time to help make sure things go smoothly. I would like to star

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-26 Thread Josh Hursey
I like the {O} = {Open MPI}. I don't mind the ORTA/ORTI versions. The only problem that might arrise there is when we talk about the layering they sound very similar to ORTE so it might be difficult to articulate. -- Josh On Tue, Jun 26, 2012 at 10:14 AM, Ralph Castain wrote: > > On Jun 26, 201

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-26 Thread Ralph Castain
On Jun 26, 2012, at 8:10 AM, Jeff Squyres wrote: > On Jun 26, 2012, at 9:28 AM, Josh Hursey wrote: > >> - ORCA: Open Runtime Collaborative Abstraction >> - OCRA: Open Collaborative Runtime Abstraction >> - OREI: Open Runtime Environment Interface >> - ORSL: Open Runtime Services Layer >> - ORRA:

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-26 Thread Jeff Squyres
On Jun 26, 2012, at 9:28 AM, Josh Hursey wrote: > - ORCA: Open Runtime Collaborative Abstraction > - OCRA: Open Collaborative Runtime Abstraction > - OREI: Open Runtime Environment Interface > - ORSL: Open Runtime Services Layer > - ORRA: Open Runtime Resource Abstraction > - ORTA: Open Runtime AP

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-26 Thread George Bosilca
ORTE -> ORTI : Open Runtime Interface -> ORTA : Open Runtime API george. On Jun 26, 2012, at 15:28 , Josh Hursey wrote: > The final thing to do for the Pineapple project is to give it a real > name. This is an easy sed script to patch the project, but finding a > name is somewhat challen

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-26 Thread Josh Hursey
The final thing to do for the Pineapple project is to give it a real name. This is an easy sed script to patch the project, but finding a name is somewhat challenging. The base parameters for the name are: - it has to start with an 'O' word - acronym must be 4 letters (O???) - acronym must be p

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-25 Thread Josh Hursey
Just a reminder that this change is headed for the trunk tomorrow afternoon/evening. We will discuss it on the teleconf, but if you have cycles to test please do so. Thanks, Josh On Fri, Jun 22, 2012 at 1:45 PM, Josh Hursey wrote: > In response to some early feedback, I fixed the following in th

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-22 Thread Josh Hursey
In response to some early feedback, I fixed the following in the branch and updated the wiki: * Fixed 'make distcheck' (missing a file) * Cleanup some warnings from autogen and configure for -no-orte builds * Added an ./autogen.pl -no-pineapple option (give you just the ORTE/OPAl stack) - see wi

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-22 Thread Josh Hursey
The pineapple branch is ready for testing. It was last sync'ed to the trunk at r26620. I'll try to update that later today, and keep current with the trunk moving forward. I created a wiki page to discuss some of the build options, for those interested. At the bottom of the page are some remaining

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-18 Thread Josh Hursey
That sounds good. The approach for this project can be seen as multi-phased. Phase 0: Baseline - Baseline implementation of just the interfaces that OMPI uses. - This is what I want to commit to the trunk next week. Phases 1-N: Interface enhancements - There are a number of suggested enhancem

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-18 Thread Ralph Castain
No disagreement over the approach - having the interface only cover OMPI as it sits is fine. As I said at the meeting, those of us using ORTE for other purposes have no real reason to need "pineapple" and can just work directly with the ORTE interfaces (GP will commit to this route). Based on th

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-18 Thread Josh Hursey
On Sat, Jun 16, 2012 at 10:32 AM, Ralph Castain wrote: > Hi Josh > > I had a chance to review your code this morning, and generally find it is > okay with me. I see a couple of things that appear to limit it, though they > may be intentional: In this pass of the pineapple interface I included o

Re: [OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-16 Thread Ralph Castain
Hi Josh I had a chance to review your code this morning, and generally find it is okay with me. I see a couple of things that appear to limit it, though they may be intentional: 1. the call to pineapple_init really needs a third flag to define the process type. Locking the underlying orte_init

[OMPI devel] RFC: Pineapple Runtime Interposition Project

2012-06-15 Thread Josh Hursey
What: A Runtime Interposition Project - Codename Pineapple Why: Define clear API and semantics for runtime requirements of the OMPI layer. When: - F June 22, 2012 - Work completed - T June 26, 2012 - Discuss on teleconf - R June 28, 2012 - Commit to trunk Where: Trunk (development BitBucket b