Proposed FTB Layers Introduction and Discussion

1. Proposed FTB LayersIntroduction and Discussion Jul 24th 2007

2. FTB Logical Overview Universal Logger Component Event Schema Any Other Component Fault Tolerant Backplane Event Analysis Middleware Like MPI Automatic Actions Diagnostics Tools MPI Event Schema Job Scheduler/ Resource Manager Application JS/RM Event Schema Application Event Schema

3. FTB Architecture Component 1 Component 2 Components FTB Verbs System dependent FTB Core System independent FTB Software FTB Network Network Module1 Network Module2

4. Goals • Make each layer independent of the other • Each layer talks to the other layers using well-defined API • Goal is to have a single implementation for BG and linux clusters and CRAYs

5. FTB Verbs • Will provide an interface for applications to communicate with FTB • Verbs API will include primitives like • FTB_Register, FTB_Catch, FTB_Throw for the components • FTB_Get_Thrown_Event, FTB_Set_Catch_Event, etc., for the FTB core • Implementation of Verbs API will differ for linux-based clusters and BG architectures

6. FTB Core • Provides the ‘core’ functionality for FTB • Keeps track of registered components and thrown events for a node (or a group of nodes) • Forwards ‘throw’ events to lower layers like FTB Network for further propagation • Deals with event (‘catch’) distribution, making wildcard distribution decisions • Grouping and Aggregation decisions • Talks to other FTB cores on other nodes

7. FTB Network • Provides a mechanism to add different networks or different communication options(reliable, unreliable) • Will deal with all network and communication details • Will connect the FTB Cores on various nodes together • Note: Communication between the BG compute node and I/O node will not go via this layer