We had a few schedule/topic changes (noted with (*)). The most notable of which is the ORTE/Red Storm meeting needs to move to 1pm Tuesday (Greg/Ralph -- this affects you). So we'll start with Greg's stuff at 1pm, and move on to Red Storm/ORTE after that.

Here's the updated schedule:

TUESDAY
--------

- We're starting 8am at the Holiday Inn Express in the conference room.

- We'll start off with status reports followed by a presentation of goals from each institution (see the list below). Feel free to bring a few slides for your presentation, if it would help. Aim for 10-15 minutes max.

(*) - 1pm, Greg and the ORTE/Red Storm will discuss Greg's perspective of ORTE (approx 30 minutes). Then we'll move on to Red Storm and other general ORTE issues.

- The rest of the day will be ad hoc discussion of the other agenda items and/or specific code issues (see below).

WEDNESDAY
---------

- Collective sub-group will convene at 8am at the ACL building (will probably need to arrive a bit earlier to get badges). Access Grid starts at 8:30, goes until 11:30am.

- Rest of group convenes at the Holiday Inn at 8am. Ad hoc progression through the other agenda items and/or code issues.

- Rich would like to invite everyone over for a cookout at his home on Wednesday evening. Time TBD.

THURSDAY
---------

- Collective sub-group will convene at 8am at the ACL building (will probably need to arrive a bit earlier to get badges). Access Grid starts at 8:30, goes until 11:30am.

- Rest of group convenes at the Holiday Inn at 8am. Ad hoc progression through the other agenda items and/or code issues.

======================================================================== =========

Random note: I motion that we skip the Tuesday teleconference the following week (2 August), since we'll all just have been together the previous week.

======================================================================== =========

Here's the full list of topics / sub-meetings:

- All: Current status, future plans/goals (presentation from each
  organization)
  - Jeff: IU/subcontract
  - Tim: LANL
  - Rich: DOE
  - Rainer: HLRS
  - Graham: UTK/subcontract
- All, Tim: overview of PML/BTL interface and design
  - Retire teg/PTL?
- All: SC, Euro PVM/MPI, LACSI planning
- All, Brian: what you need to know about the new configure.m4 system
- All: discussion of others coming into the tree (e.g., IB vendors)
- All: project split issues
  - tools in wrong trees (abstraction issues)
  - (*) need to move unit tests
  - wrapper compilers for ORTE/OPAL?
  - #include files
  - any final cleanup moving between opal/orte/ompi trees
- All: processor/memory affinity
- All: MCA issues
  - Framework hiding / re-entrance (e.g., ompi_info)
  - How to have multiple PML's without re-initializing BTLs/PTLs?
  - Better guidelines for framework/component "open" calls
- Separate function for framework/component MCA parameter registration?
  - Frameworks as DSOs
- All, Jeff: build system changes (lower priority than most other items)
- (*) Jeff, Sami: collectives pre-discussion (Tues morning)

- ORTE sub group:
  - external perspective from Eclipse guys
  - simplifying GPR access
  - multi-cell RTE
- (*) how to split ORTE and get stable drops only (personnel / resource issues)
- Red Storm sub-group:
  - current status
  - RTE design -- trial, error, and how to proceed
- One-sided sub-group: current status, SC plans, future plans
- Fault tolerance sub-group:
  - Integrating LAM-style coordinated, synchronous checkpointing
  - How to do other kinds of checkpointing (e.g., FT-MPI, MPICH-V, etc.)
- Collectives sub-group (including Access Grid participants):
  - New framework (coll v2)
  - Using btl's
  - Striping
  - Non-blocking collectives
  - ...?

--
{+} Jeff Squyres
{+} The Open MPI Project
{+} http://www.open-mpi.org/

Reply via email to