Distributed system concept and architecture

Goals of Distributed OS: 1. Efficiency:

Due to communication delay in distributed environment.(milliseconds to microseconds) Delay is caused by -Data propagation -Load distribution Need effective communication primitives at the language or O.S level and good communication protocols at the network levels

2. Flexibility: Users view Related to friendliness and freedom of using system. Provide consistency and reliability Systems view Systems ability to evolve & migrate Key properties are Portability Modularity Interoperability Scalability

3. Consistency: System behavior should be predictable. Uniformity in using the system Inconsistency causes because of Replication and partitioning of data Component failures Complexity of interaction among modules

4. Robustness : Ability to handle exceptional situations and errors such as Changes to the system topology Long message delays Inability to locate a server

 Other major responsibilities of DOS are Reliability Protection Access control

Transparency
Hide all system dependent details from user. Different types: 1. Access transparency- Ability to access both local and remote system objects in a uniform way 2. Location transparency- Users have no awareness of object locations 3. Migration transparency- Object is not only referred to by its logical name but can also be moved to a different physical location without changing the name 4. Concurrency transparency- Sharing of objects without interference 5. Replication transparency-Provides consistency of multiple instances of files and data 6

6. Parallelism transparency-Permits parallel activities without users knowing how, where and when these activities are carried out by the systems 7.Failure transparency-Provide fault tolerance such that failures in the system can be transformed into graceful system performance degradation 8.Performance transparency-Achieve a consistent and predictable performance level even with changes of the system structure or load distribution
7

9.Size transparency-It allows incremental growth of a system without the users awareness 10.Revision transparency- Refers to the vertical growth of systems as opposed to the horizontal growth in system size

Categorization of transparencies based on system goals

System Goals
Efficiency

Transparencies
Concurrency Parallelism Performance Access Location Migration Size Revision Access Replication Performance Failure Replication Size Revision

Flexibility

Consistency

Robustness

Distributed system issues and transparencies

Major Issues Communication Synchronization Distributed algorithms Process scheduling Deadlock handling Load balancing Resource scheduling File sharing Concurrency control Failure handling Configuration Redundancy Transparencies Interaction and control transparency Performance transparency

Resource transparency

Failure transparency
10

Services
1. Primitive services: -Implemented inside kernel. -They are basic services for process communication. - Process communication is by message passing. -Synchronization -Processor multiplexing 2. Services by System servers: Implemented any where in system 1) Name server: -Find the location of file. 2) Network server: -Name and location from name server is system dependent. -Translation of address and routing information are 11 provided by network server.

3) Time server: -Used for Synchronization and scheduling of hardware and software. - 2 types of timing information are: Physical clock provide real-time. Logical clock provide artificial time to preserve event ordering 4) Servers for managing shared system resources are: File server Print server Authentication server Migration server
12

3) Value added services: - They are special purpose services. - Group server: Manage the creation and termination of group activities. Responsible for group addressing and communication. contain information like : -Membership -Admission policy -Members privileges
Ex: Distributed conference group, Network news group
13

A. Distributed System architecture

1. 2. 3. 4. Workstation Model Workstation- Server Model Processor-pool model Hybrid model

14

1. Workstation Model
Workstation

Workstation Communicati on network Workstation

Workstation

Workstation

15

 Consists of several workstations interconnected by communication network Eg. A companys office have several workstations scattered throughout a building Each workstation equipped with its own disk and serving as a single user computer Eg. Sprite system[1988] Xerox PARC[1982]
16

 When the system finds that the users workstation does not have sufficient processing power for executing the processes of the submitted jobs efficiently, it transfers one or more of the processes from the users workstation to some other workstation that is currently idle and get the process executed there, and finally the results of execution is returned to the users workstation
17

2. Workstation-Server Model
Workstation Workstation

Workstation Communication network

Workstation

MiniComputer File server

MiniComputer Data base server

MiniComputer Print server

18

 Diskful workstations workstation with its own disk Diskless workstations workstation without its own disk This model consists of a few minicomputers and several workstations(most of which are diskless, but a few of which may be diskful ) interconnected by a communication network
19

 When diskless workstations are used on a network, the file system to be used by these workstations must be implemented either by a diskful workstation or by a minicomputer equipped with a disk for file storage Eg. V-system [1998]

20

 Client workstations Diskless Graphic/interactive applications processed in local All file, print, database computation requests are sent to servers. Server minicomputers Each minicomputer is dedicated to one or more different types of services. Client-Server model of communication RPC (Remote Procedure Call)

21

 Clients: They log in one of terminals (diskless workstations)

Servers: Necessary number of processors are allocated to each user from the pool. Better utilization but less interactivity

22

3. Processor-Pool Model
Terminals Communication network Data base server Pool of processor
23

File server

 When the user needs a large amount of computing power for a short time, the processors are pooled together to be shared by the users as needed Each processor in the pool has its own memory to load and run a system program or an application program Eg. Amoeba[1990], Plan 9[1990]

24

4. Hybrid Model
Combine the advantages of Workstationserver model and processor-pool model The processors in the pool can be allocated dynamically for computations that are too large for workstations or that require several computers concurrently for efficient execution

25

B. Communication Network Architecture

point-to-point connection multipoint connection IEEE 802 LAN standards Ethernet Token Bus Token Ring FDDI SONET
26

Communication Network Protocols Set of rules , that regulate the exchange of messages to provide a reliable and orderly flow of information Two categories of communication services 1. Connection oriented 2. Connectionless Circuit switching Packet switching
27

Cont..
Popular network protocol suite: 1. OSI protocol suite - 7 layers -data transparency is achieved by an encapsulation process - protocol data unit 2. TCP/IP protocol suite

28

OSI Reference Model

Layered model:
7. Application 6. Presentation 5. Session 4. Transport 3. Network 2. Data Link 1. Physical
Netprog: OSI Reference Model

The Physical Layer

Responsibility:
transmission of raw bits over a communication channel.

Issues:
mechanical and electrical interfaces time per bit distances

Netprog: OSI Reference Model

The Data Link Layer Data Link Control

Responsibility:
provide an error-free communication link

Issues:
framing (dividing data into chunks)
header & trailer bits

addressing
10110110101
Netprog: OSI Reference Model

01100010011

10110000001

The Data Link Layer The MAC sublayer

Medium Access Control - needed by mutiaccess networks. MAC provides DLC with virtual wires on multiaccess networks.

Netprog: OSI Reference Model

The Network Layer

Responsibilities:
path selection between end-systems (routing). subnet flow control. fragmentation & reassembly translation between different network types.

Issues:
packet headers virtual circuits
Netprog: OSI Reference Model

The Transport Layer

Responsibilities:
provides virtual end-to-end links between peer processes. end-to-end flow control

Issues:
headers error detection reliable communication
Netprog: OSI Reference Model

The Session Layer

Responsibilities:
establishes, manages, and terminates sessions between applications. service location lookup

Many protocol suites do not include a session layer.

Netprog: OSI Reference Model

The Presentation Layer

Responsibilities:
data encryption data compression data conversion

Many protocol suites do not include a Presentation Layer.

Netprog: OSI Reference Model

The Application Layer

Responsibilities:
anything not provided by any of the other layers

Issues:
application level protocols appropriate selection of type of service

Netprog: OSI Reference Model

Cont..
Two major types of system interactions: 1.Interprocess communication -uses process id 2.Internode communication TCP is a transport layer protocol equivalent to TP4 in OSI IP

38

Cont..
Socket abstraction of network I/O Allows standard Read and Write operation created using socket system call Given by a socket descriptor System calls
connect bind sendto recvfrom
39