logging in or signing up pre e272 Jancis Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 20 Category: Entertainment License: All Rights Reserved Like it (0) Dislike it (0) Added: October 21, 2007 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript CORBA/RMI issues in Nile: CORBA/RMI issues in Nile Authors: F. Handfield (University of Texas, Austin, TX USA) D. Mimnagh (University of Texas, Austin, TX USA) M. Ogg (University of Texas, Austin, TX USA) L. Zhou (University of Florida, Gainesville, FL USA) Presented by: D. Mimnagh (University of Texas, Austin, TX USA) CHEP 2000Overview: Overview What is Nile? Distributed Object Architecture CORBA RMI Future workWhat is Nile?: What is Nile? Nile: Distributed computing solution for CLEO fault-tolerant (recover from resource failure) self-managing (sophisticated resource scheduling) heterogeneous (will run anything anywhere) Designed for HEP track reconstruction data analysis simulation But very generic Nile Architecture: Nile ArchitectureHistory of Nile: History of Nile Initially C++ Electra, for the CORBA ORB Isis for replication Isis product was eventually abandon by its vendor C++ was hard to use portably Nile rewritten in Java with CORBADistributed Object Architecture: Distributed Object Architecture Computation is distributed Should we distribute the control system? scalability resilience separation of function additional failure modes error handling Choices available: CORBA, RMI, DCOM Nile with CORBA: Nile with CORBA Code specified by IDL to Java bindings write interfaces in IDL compile IDL to Java for interfaces, proxies helper classes etc... implement Java interfaces Successful robust Nile implementation achieved HERA-B MC CLEO II MCSlide8: Restrictive object model pass data only not Serializable members are public classes are final Under specified OMG politics? Name Service is single point of failure ORB supplier bug reporting Scaling problems CORBA IssuesNile with RMI: Nile with RMI No code mappings needed write interfaces in Java implement Java interfaces compile implementation to proxies classes Improved Nile prototype (see E301) no deadlocks no scalability problems with 60 CPUsRMI Issues: RMI Issues Less complex only the essentials functions are provided fewer lines of code Java only (could use JNI to get to others) rudimentary registry service Real objects data + code One vendor better integration no alternatives It does the job!Future Work: Future Work Complete port to RMI robust fault-tolerance,GUIs, etc... CLEO III data processing and analysis scheduling data management comprehensive security Enhance Nile with RMI technologies Jini Jini: Jini Lookup Service Name Service transparent replication object database Lease mechanism Distributed events You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
pre e272 Jancis Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 20 Category: Entertainment License: All Rights Reserved Like it (0) Dislike it (0) Added: October 21, 2007 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript CORBA/RMI issues in Nile: CORBA/RMI issues in Nile Authors: F. Handfield (University of Texas, Austin, TX USA) D. Mimnagh (University of Texas, Austin, TX USA) M. Ogg (University of Texas, Austin, TX USA) L. Zhou (University of Florida, Gainesville, FL USA) Presented by: D. Mimnagh (University of Texas, Austin, TX USA) CHEP 2000Overview: Overview What is Nile? Distributed Object Architecture CORBA RMI Future workWhat is Nile?: What is Nile? Nile: Distributed computing solution for CLEO fault-tolerant (recover from resource failure) self-managing (sophisticated resource scheduling) heterogeneous (will run anything anywhere) Designed for HEP track reconstruction data analysis simulation But very generic Nile Architecture: Nile ArchitectureHistory of Nile: History of Nile Initially C++ Electra, for the CORBA ORB Isis for replication Isis product was eventually abandon by its vendor C++ was hard to use portably Nile rewritten in Java with CORBADistributed Object Architecture: Distributed Object Architecture Computation is distributed Should we distribute the control system? scalability resilience separation of function additional failure modes error handling Choices available: CORBA, RMI, DCOM Nile with CORBA: Nile with CORBA Code specified by IDL to Java bindings write interfaces in IDL compile IDL to Java for interfaces, proxies helper classes etc... implement Java interfaces Successful robust Nile implementation achieved HERA-B MC CLEO II MCSlide8: Restrictive object model pass data only not Serializable members are public classes are final Under specified OMG politics? Name Service is single point of failure ORB supplier bug reporting Scaling problems CORBA IssuesNile with RMI: Nile with RMI No code mappings needed write interfaces in Java implement Java interfaces compile implementation to proxies classes Improved Nile prototype (see E301) no deadlocks no scalability problems with 60 CPUsRMI Issues: RMI Issues Less complex only the essentials functions are provided fewer lines of code Java only (could use JNI to get to others) rudimentary registry service Real objects data + code One vendor better integration no alternatives It does the job!Future Work: Future Work Complete port to RMI robust fault-tolerance,GUIs, etc... CLEO III data processing and analysis scheduling data management comprehensive security Enhance Nile with RMI technologies Jini Jini: Jini Lookup Service Name Service transparent replication object database Lease mechanism Distributed events