Download
the architecture of the starfish system mapping the survivability space n.
Skip this Video
Loading SlideShow in 5 Seconds..
The Architecture of the Starfish System: Mapping the Survivability Space PowerPoint Presentation
Download Presentation
The Architecture of the Starfish System: Mapping the Survivability Space

The Architecture of the Starfish System: Mapping the Survivability Space

429 Views Download Presentation
Download Presentation

The Architecture of the Starfish System: Mapping the Survivability Space

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. The Architecture of the Starfish System: Mapping the Survivability Space Kim Kihlstrom Chris Phillips Chris Ritchey Ben LaBarbera Westmont College Priya Narasimhan Carnegie Mellon University

  2. Starfish Goals • Provide survivability for middleware applications • Not specific to any middleware system • Applicable to local and wide area systems • Provide support for connected enterprises such as web services • Allow linking of multiple Starfish IASTED PDCS 2003

  3. Starfish Protocol Stack IASTED PDCS 2003

  4. Creating the Survivability Space • Define what is meant by survivability • Evaluate existing systems • Identify tradeoffs in survivability issues • Develop cohesive framework for survivable system design IASTED PDCS 2003

  5. Survivability • Encompasses but goes beyond reliability and security • Provide useful services even in event of malicious attacks, intrusions, accidents, or faults IASTED PDCS 2003

  6. Survivability Space IASTED PDCS 2003

  7. Reliability Subspace IASTED PDCS 2003

  8. Security Subspace IASTED PDCS 2003

  9. Quality of Service Subspace IASTED PDCS 2003

  10. Mapping of Prior Systems • Mapped a number of existing systems to survivability space IASTED PDCS 2003

  11. Starfish Philosophy • Starfish allows for tradeoffs between security, reliability, and quality of service by providing body, shoulders, and arm regions • Body: Byzantine fault model and high security guarantees, but lower performance and not scalable to wide area or large number of processors • Arms: High performance and highly scalable, but supports only crash/omission/timing fault model and less stringent security guarantees • Shoulders: Intermediate fault tolerance, security, performance and scalability IASTED PDCS 2003

  12. IASTED PDCS 2003

  13. Linked Starfish IASTED PDCS 2003

  14. Starfish Reliability Subspace IASTED PDCS 2003

  15. Starfish Security Subspace IASTED PDCS 2003

  16. Starfish Quality of Service Subspace IASTED PDCS 2003

  17. Reliability Mechanisms • Active and passive replication • Majority voting • Secure reliable ordered multicast • Byzantine fault detector • Value fault detector • Secure membership • Vaccination • Timeouts • Retransmission IASTED PDCS 2003

  18. Security Mechanisms • Threshold scheme • Encryption • Identifiers • Passwords • MACs • Signatures • Byzantine fault detector • Value fault detector • Secure membership • Logging • Anomaly detection Sandboxing Intrusion history Message digests State transfer Quarantine Vaccination Membership Message Digests Removal Recovery IASTED PDCS 2003

  19. Quality of Service Mechanisms • Removal/addition • Migration • Hierarchical Groups • Message prioritization • Optimistic Delivery • Live Upgrades IASTED PDCS 2003

  20. Conclusions • Mapping of prior systems to survivability space • Mapping of Starfish body, shoulders, and arms to survivability space • Identification of survivability properties and mechanisms for Starfish body, shoulders, and arms IASTED PDCS 2003

  21. Questions and Feedback • Kim Kihlstrom • kimkihls@westmont.edu • http://homepage.westmont.edu/kimkihls/ • Priya Narasimhan • priya@cs.cmu.edu • http://www.cs.cmu.edu/~priya/ • Chris Phillips • chphilli@westmont.edu IASTED PDCS 2003