150 likes | 237 Vues
This research project explores the integration of applications in real-world ubicomp environments, focusing on zero-admin and incremental approaches to enhance collaboration. The study introduces an innovative infrastructure called iROS, enabling efficient communication among applications through Event Heap, simplifying integration efforts and ensuring recoverability from failures. The configuration is centralized, installation is quick, and boundaries of interaction are clearly defined. The iROS Manager daemon controls application activities, ensuring flexibility for various applications. The study showcases a successful deployment with TeamSpace, demonstrating the feasibility of creating unified, zero-admin environments from diverse software components.
E N D
Balancing Zero-Adminand Incremental Integrationin Real-World Ubicomp Environments Andy Szybalski Adviser: Armando Fox 25 May 2004
Stanford iRoom • Conference room augmented with: • 3 SmartBoard displays • wireless input andoutput devices • custom software infrastructureand applications (iROS) • Facilitates collaborative work
OpenURL(www.stanford.edu) OpenURL(www.stanford.edu) iROS • Incremental integration: applications communicate indirectly through Event Heap • Minimizes effort of integration associated with adding new applications to the environment • Difficult to recover from hardware and software failures X MultiBrowseSender MultiBrowseRec’ver MultiBrowseSender MultiBrowseRec’ver PointRight for Mac Event Heapserver PointRight for Win
Zero-Admin • recoverability from transient hardware and software failures • configuration minimal and centralized • installation can be done quickly and easily to integrated new machines into the environment • boundaries of interaction clearly defined • All applications on a machine connected or disconnected • One Event Heap per room without increasing effort of integration
iROS Manager • iROS Manager is a daemon that controls starting, monitoring, and stopping of applications in a ubicomp environment • Must be flexible enough to accommodate arbitrary applications • takes advantage of universal mechanisms Macapp Javaapp Event Heapserver Winapp Javaapp iROS Manager iROS Manager iROS Manager
PingEvent() Recoverability Event Heapserver Javaapplication default monitor Event Heap monitor iROS Manager • Restartability: if an application stops functioning, iROS Manager kills its process and restarts it. • Monitoring: how to tell if an application is functioning properly • default: process alive • custom Event Heap monitor: ping • Uses universal mechanisms, but: • applications must be restartable
Configuration • Global settings across all applications • In addition, each application must be accompanied by a config.ini file specifying how it should be run: APPLICATION = java MultiBrowseService ${MACHINE_NAME} ${EHEAP_SERVER} • Someone must write these config.ini files
Zero-Admin • recoverability from transient hardware and software failures • configuration minimal and centralized • installation can be done quickly and easily to integrated new machines into the environment • boundaries of interaction clearly defined • All applications on a machine connected or disconnected • One Event Heap per room mostly without increasing effort of integration
Success Story: TeamSpace • Model for a public zero-admin interactive workspace • Deployed in Meyer Library • TeamSpace client installation with iROS Manager, PointRight, MultiBrowse • Simple GUI foriROS Manager
TeamSpace GUI • Event Heap server preset to teamspace.stanford.edu • Connected to Event Heap iff application is open • Very few code modifications needed: • Integrated MultiBrowse sender functionality into GUI • Made PointRight non-configurable • Nomenclature
Conclusions • Future work • restartability using dependencies • global configuration across multiple machines • It is possible to create a unified, zero-admin environment from a heterogeneous set of software • Balance between zero-admin and incremental integration Andy Szybalski andys@cs.stanford.edu