1 / 11

Fault Tolerant Backplane Demo

Fault Tolerant Backplane Demo. July 3rd 2007. Objective. A simplified FTB toy demo to demonstrate basic FTB functionality Enable component owners to use the FTB Demo to throw their events and catch other component events

nikki
Download Presentation

Fault Tolerant Backplane Demo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Fault Tolerant BackplaneDemo July 3rd 2007

  2. Objective • A simplified FTB toy demo to demonstrate basic FTB functionality • Enable component owners to use the FTB Demo to throw their events and catch other component events • To provide an incremental modularized approach for implementing next steps

  3. FTB Demo - Logical Overview Central Logger FTB Watchdog Watchdog Information Logger Information Centralized FTB Server FTB Server Information MPICH2 Event Schema MPICH2 Component Event Schema Other Components MPICH2 Information

  4. FTB Demo - Sequence of Steps • Checkout the code from the SVN • Read the README file (contains important instructions) • Use make to compile the code • Start the ftb_server first • Set the LD_LIBRARY_PATH on the clients and run examples like logger/watchdog from examples directory • Play with the MPICH2 component • Define your component events and play them with FTB Demo • Integrate your component into FTB

  5. Current Limitations/Work-in-Progress • The FTB Demo is just a Demo! The design and API is not final. • The FTB framework is currently centralized and not scalable • Next steps is to tackle scalability and communication issues one-by-one • Toy Demo contains only MPICH2 sample events • Need to integrate other events, once defined, from other components • The sample events contain only sample attributes • Component schema currently in plain text and not in XML

  6. Next Steps • FTB Toy Demo available in SVN • Location: /projects/cifts/ftb/devel/ftb_demo/ • Can be browsed from the CIFTS website • Ftb-commit mailing list setup • Checkout the Demo and play with it • README, documentation available in FTB directory • Initiate work on specific component events and schema • Try to integrate it in the Toy Demo, so other other components can try to catch them

  7. Backup

  8. FTB Demo - FTB_Server • Location: /projects/cifts/ftb/devel/ftb_demo/ftb_src/bin • Server starts on default port 10808 • Displays appropriate messages when new components (including logger, watchdog) register as debug information • Display events being sent to the FTB_Server BACK

  9. FTB Demo - FTB_Logger • Location: /projects/cifts/ftb/devel/ftb_demo/ftb_src/examples • ./ftb_logger • Automatically connects to FTB Server on start-up • Logs all events that it gets them in a log file BACK

  10. FTB Demo - FTB_Watchdog • Location: /projects/cifts/ftb/devel/ftb_demo/ftb_src/examples • ./ftb_watchdog • Automatically connects to FTB Server on start-up • Throws a heartbeat event (called WATCHDOG_HEARTBEAT) periodically. This event is caught by default by itself BACK

  11. FTB Demo - MPICH2 component • Location: /projects/cifts/ftb/devel/ftb_demo/mpich2 • Based on MPICH2-1.0.5-p4 (download code from MPICH2 website) • Provides a FTB patch for MPD BACK

More Related