Yaxin Hu 2.8 SUMMARY

Outline Summary of different sections of chapter 2 Recent research papers Future works/predictions

What’s a distributed operating system and Why? What? An integration of system services, presenting a transparent view of a multiple computer system with distributed resources and control Why? increasing need to share resources and information decreasing cost of workstations Widespread use of networks Maturity of software technologies

2.1 Goals Efficiency Flexibility Consistency Robustness

2.2 Transparency 10 different aspects of transparency: Access, Location, Migration, Concurrency, Replication, Parallelism, Failure, Performance, Size, Revision Corresponding transparencies based on the four distributed system goals and issues

2.3 Services Kernel side: Primitive services provide communication, synchronization, and processor multiplexing Services by System Servers provide fundamental services for managing processes, files, and process communication Value-added Services in supporting distributed applications

2.4 Architecture Models Distributed System Architecture Workstation-server model Processor-pool model Communication Network Architecture Local area network (LAN) Metropolitan area network (MAN) Wide area network (WAN)

2.5 Communication Network Protocols OSI seven-layer protocol Suite: application, presentation, session, transport, network, data link, and physical TCP/IP two-layer protocol Suite: transport and internet

2.6 Major Design Issues Object Models and Naming Schemes Distributed Coordination Interprocess communication Distributed Resources Fault Tolerance and Security

2.7 Distributed Computing Environment (DCE) DCE architecture

SlapOS Open source Multi-purpose Distributed Cloud Operating System Based on Enterprise Resource Planning (ERP) billing Model Capable of allocating vitual machines, application servers, databases, and ERP applications Two types of servers SlapOS Nodes: datacenter/home, install software and run processes SlapOS Master: central directory of all SlapOS Nodes, allocate processes to SlapOS Node

SOA-DOS Service-oriented architecture Distributed Operating System Manage all embedded devices in a home network at high level interoperability Can solve many problems related to accessing home network from internet and future network like Smart Grids Also takes into consideration the limited resources of sensors as well as the matter of simultaneous multi-access, eventing, authorization, security and scheduling the on-line time of sensors in order to reduce power consumption

Future Works The proposed SOA-DOS is very interesting by adopting distributed operating system to manage resource-constrained embedded devices like in wireless sensor networks, and it might be worth trying within GSU campus buildings to do energy management.

References Smets-Solanes, J.-P.; Cérin, C.; Courteaud, R., "SlapOS: A Multi- Purpose Distributed Cloud Operating System Based on an ERP Billing Model," Services Computing (SCC), 2011 IEEE International Conference on, vol., no., pp.765,766, 4-9 July 2011 Sleman, A.; Moeller, R., "SOA distributed operating system for managing embedded devices in home and building automation," Consumer Electronics, IEEE Transactions on, vol.57, no.2, pp.945,952, May 2011