SD 1

Distributed Systems Course Objectives
High-Performance Networks
Clusters and Computational Grids
In this the course we are going to presented the distributed
systems, high performance networks, clusters and
computational grids environments.
In the end, participants will have a good idea of the basis

of these subjects in both theoretical and practical aspects.
Prof. Mario Dantas, PhD
Course Outline Course Outline
z Distributed Systems Distributed Systems

In this part of the course we will cover the following aspects of
the distributed systems :
z High Performance Networks
• Characteristics
• Architectural Models
z Clusters and Computational Grids • Networking and Internetworking
• InterProcess Communication (IPC)
• Distributed File System (DFS)
• Name Services (NS)
Course Outline Distributed Systems - Characteristics
The recommended literature are presented below and

we base our course in the first book. intranet ☎
☎
☎ ISP
☎
z Distributed Systems: Concepts and Design, 3rd
Edition, G. Coulouris, J. Dollimore, T. Kindberg, backbone
Addison-Wesley, August 2000, ISBN 0201-61918-0.
z Distributed Systems: Principles and Paradigms, satellite link
Andrew S. Tanenbaum, Maarten Van Steen,
desktop computer:
Prentice Hall, 2002, ISBN 0130888931. server:
network link:
An Internet Example
Distributed Systems Distributed Systems
email server Desktop

computers
print and other servers Internet
Local area
Web server network
email server WAP

Host intranet Home intranet
print Wireless LAN gateway
File server
other servers
the rest of
the Internet Mobile Mobile Equipments in a DS
router/firewall phone
Printer Laptop
An Intranet Example
Camera Host site
Date Computers Webservers

http://www.google.comlsearch?q=kindberg
www.google.com
Browsers 1979 – 188 0

Web servers
December
www.cdk3.net Internet
http://www.cdk3.net/
1989 – July 130,000 0
www.w3c.org
File system of http://www.w3c.org/Protocols/Activity.html

www.w3c.org Protocols 1999 – July 56,218,000 5,560,866
Activity.html
Web servers and web browsers
Transparencies
Date Computers Web servers Percentage
Access transparency: enables local and remote resources to be accessed
1993, July 1,776,000 130 0.008 using identical operations.
1995, July 6,642,000 23,500 0.4
1997, July 19,540,000 1,203,096 6 Location transparency: enables resources to be accessed without knowledge of
their location.
1999, July 56,218,000 6,598,697 12
Concurrency transparency: enables several processes to operate concurrently
using shared resources without interference between them.
Replication transparency: enables multiple instances of resources to be used to

increase reliability and performance without knowledge of the replicas by users or
application programmers.
Distributed Systems Distributed Systems – Architectural Model
Transparencies Architectural Models

Failure transparency: enables the concealment of faults, allowing users and
application programs to complete their tasks despite the failure of hardware or
Applications, services
software components.
Mobility transparency: allows the movement of resources and clients within a

Middleware
system without affecting the operation of users or programs.
Performance transparency: allows the system to be reconfigured to improve

Operating system
performance as loads vary.
Platform
Scaling transparency: allows the system and applications to expand in scale Computer and network hardware
without change to the system structure or the application algorithms.
A service provided by multiple servers

Clients invoke individual servers
Service
Server
Client invocation Server
invocation
Client
result result
Server
Server
Client
Key: Client
Process: Computer:
Server
A distributed application based on peer processes

Web proxy server
Application Application
Client Web Coordination Coordination

server code code
Proxy
server
Client Web
server Application
Coordination
code
Web applets Thin clients and compute servers
a) client request results in the downloading of applet code
Client Web
Applet code server
b) client interacts with the applet
Web
Client Applet server
Spontaneous networking in a hotel Real-time ordering of events

Music send receive receive
service Alarm
gateway X
service 1 m1 4
m2
Internet send
receive
2 3 Physical
Y
receive time
Hotel wireless
network send
Discovery Z
service receive receive
Camera
m3 m1 m2
A
receive receive receive
TV/PC Guests t1 t2 t3
Laptop PDA
devices
Omission and arbitrary failures
Class of failure Affects Description

Processes and channels Fail-stop Process Process halts and remains halted. Other processes may
detect this state.
Crash Process Process halts and remains halted. Other processes may
process p process q not be able to detect this state.
Omission Channel A message inserted in an outgoing message buffer never
send m receive arrives at the other end’s incoming message buffer.
Send-omission Process A process completes a send, but the message is not put
in its outgoing message buffer.
Communication channel
Receive-omission Process A message is put in a process’s incoming message
buffer, but that process does not receive it.
Outgoing message buffer Incoming message buffer
Arbitrary Process or Process/channel exhibits arbitrary behaviour: it may
(Byzantine) channel send/transmit arbitrary messages at arbitrary times,
commit omissions; a process may stop or take an
incorrect step.
Timing failures Objects and principals
Class of Failure Affects Description

Clock Process Process’s local clock exceeds the bounds on its Access rights
rate of drift from real time. Object
Performance Process Process exceeds the bounds on the interval invocation
between two steps.
Performance Channel A message’s transmission takes longer than the Client
stated bound. result Server
Principal (user) Network Principal (server)
The enemy
Copy of m
Process q
Process p Secure Channel
The enemy
m’
Process p m Process q
Communication channel
Distributed Systems –
Networking and Internetworking Distributed Systems
Message sent Message received
Range Bandwidth (Mbps) Latency (ms) Layer n

LAN 1-2 kms 10-1000 1-10
WAN worldwide 0.010-600 100-500
MAN 2-50 kms 1-150 10
Wireless LAN 0.15-1.5 km 2-11 5-20 Layer 2
Wireless WAN worldwide 0.010-2 100-500 Layer 1
Internet worldwide 0.010-2 100-500 Sender Communication Recipient
medium
Network types Conceptual layering of protocol software

Application-layer message
Message sent Message received
Layers
Presentation header
Application
Session header Presentation
Transport header Session

Transport
Network header
Network
Encapsulation as it is applied in layered protocols Data link
Physical
Sender Communication Recipient
medium
Protocol layers in the ISO
Open Systems Interconnection (OSI) model
Layer Description Examples Message
Application Protocols that are designed to meet the communication requirements of HTTP,FTP , SMTP, Layers
specific applications, often defining the interface to a service. CORBA IIOP
Presentation Protocols at this level transmit data in a network representation that is Secure Sockets
independent of the representations used in individual computers, which may (SSL),CORBA Data Application
differ. Encryption is also performed in this layer, if required. Rep.
Session At this level reliability and adaptation are performed, such as detection of
failures and automatic recovery. Internetwork
Transport This is the lowest level at which messages (rather than packets) are handled. TCP, UDP Transport protocols
Messages are addressed to communication ports attached to processes,
Protocols in this layer may be connection-oriented or connectionless.
Network Transfers data packets between computers in a specific network. In a WAN IP, ATM virtual
or an internetwork this involves the generation of a route passing through circuits Internetwork
routers. In a single LAN no routing is required.
Data link Responsible for transmission of packets between nodes that are directly Ethernet MAC,
Internetwork packets
connected by a physical link. In a WAN transmission is between pairs of ATM cell transfer,
routers or between routers and hosts. In a LAN it is between any pair of hosts. PPP Network interface
Underlying
Physical The circuits and hardware that drive the network. It transmits sequences of Ethernet base- band
binary data by analogue signalling, using amplitude or frequency modulation signalling, ISDN Network-specific packets network
of electrical signals (on cable circuits), light signals (on fibre optic circuits) protocols
or other electromagnetic signals (on radio and microwave circuits). Underlying network

router/
Routing in a wide area network Campus138.37.95.240/29
router subnet
138.37.95.241 firewall
hammer
Staff subnet Student subnet
138.37.88 138.37.88.251 138.37.94.251 138.37.94
compute Eswitch Eswitch file server/
server gateway
bruno
138.37.88.249 custard
138.37.94.246 printers
dialup
A 1 B ☎ server
henry
138.37.88.230
other
Hosts 2 file
server
servers
3 Links 4
hotpoint
or local C 138.37.88.162
web
networks 5
server
copper
138.37.88.248
hub hub A Network Example
D 6 E
Routers desktop computers138.37.88.xx desktop computers138.37.94.xx
sickle
Campus138.37.95.248/29 100 Mbps Ethernet
router subnet router/
138.37.95.249 firewall
1000 Mbps Ethernet
Eswitch: Ethernet switch
Message
Layers
Application
IPv6 encapsulated in IPv4 packets Messages (UDP) or Streams (TCP)
Transport
IPv4 network
IPv6 IPv6 UDP or TCP packets
A B
Internet
IP datagrams
Network interface
Encapsulators Network-specific frames
Underlying network
Tunnelling for IPv6 migration
TCP/IP layers
Application message
TCP header port

IP header TCP
TCP UDP
Ethernet header IP
IP
Ethernet frame
The programmer's conceptual view of a TCP/IP Internet

Encapsulation in a message transmitted via TCP over an
Ethernet
octet 1 octet 2 octet 3 Range of addresses
Network ID Host ID
7 24 1.0.0.0 to
Class A: 1 to 127 0 to 255 0 to 255 0 to 255 127.255.255.255
Class A: 0 Network ID Host ID Network ID Host ID
Class B: 128 to 191 0 to 255 0 to 255 0 to 255 128.0.0.0 to
14 16 191.255.255.255
Network ID Host ID
Class B: 1 0 Network ID Host ID 192.0.0.0 to
Class C: 192 to 223 0 to 255 0 to 255 1 to 254
223.255.255.255
21 8 Multicast address
Class D (multicast): 224 to 239 0 to 255 0 to 255 1 to 254 224.0.0.0 to
Class C: 1 1 0 Network ID Host ID 239.255.255.255
28 Class E (reserved): 240 to 255 0 to 255 0 to 255 1 to 254 240.0.0.0 to

255.255.255.255
Class D (multicast): 1 1 1 0 Multicast address
27
Class E (reserved): 1 1 1 1 0 unused
Decimal representation of Internet addresses

Internet address structure, showing field sizes in bits

Version (4 bits) Priority (4 bits) Flow label (24 bits)
Payload length (16 bits) Next header (8 bits) Hop limit (8 bits)
header Source address

(128 bits)
IP address of source IP address of destination data
up to 64 kilobytes
Destination address
(128 bits)
IP packet layout
IPv6 header layout
Sender Subsequent IP packets
tunnelled to FA Mobile host MH a) Filtering router Protected intranet
Router/
Address of FA filter
returned to sender
Internet
First IP packet
addressed to MH web/ftp
server
Internet Firewall configurations
Foreign agent FA
b) Filtering router and bastion
Home R/filter Bastion
agent First IP packet
tunnelled to FA
Internet
web/ftp
server
c) Screened subnet for bastion R/filter Bastion R/filter

The MobileIP routing mechanism
Internet
web/ftp
server

A B C
IEEE 802 network standards Laptops
radio obstruction
IEEE No. Title Reference Wireless
D LAN
802.3 CSMA/CD Networks (Ethernet) [IEEE 1985a] Palmtop E
802.4 Token Bus Networks [IEEE 1985b] Base station/

Server
802.5 Token Ring Networks [IEEE 1985c] access point
802.6 Metropolitan Area Networks [IEEE 1994]

802.11 Wireless Local Area Networks [IEEE 1999]
LAN
Wireless LAN configuration
Message
Layers
Application Header: 5 bytes
Virtual path id Virtual channel id Flags Data
Higher-layer protocols 53 bytes
ATM adaption layer

ATM cells
ATM layer
ATM cell layout
ATM virtual channels
Physical
ATM protocol layers
Distributed Systems Distributed Systems - IPC
Host
VPI = 2 Applications, services
VPI = 3 VP/VC RMI and RPC

VP switch
switch
VPI = 4 request-reply protocol Middleware

This
VPI in VPI out layers
chapter
2 4 VPI = 5 marshalling and external data representation
3 5
VP switch
UDP and TCP
Host
VPI : virtual path identifier
Virtual path Virtual channels

Switching virtual paths in an ATM network Middleware layers
Distributed Systems - IPC Distributed Systems - IPC
Type Representation
sequence length (unsigned long) followed by elements in order
any port agreed port string length (unsigned long) followed by characters in order (can also
socket socket
can have wide characters)
array array elements in order (no length specified because it is fixed)
message
struct in the order of declaration of the components
client server enumerated unsigned long (the values are specified by the order declared)
other ports union type tag followed by the selected member
Internet address = 138.37.94.248 Internet address = 138.37.88.249
Sockets and ports CORBA CDR for constructed types
index in notes
sequence of bytes 4 bytes on representation Serialized values Explanation
0–3 5 length of string Person 8-byte version number h0 class name, version number
4–7 "Smit" ‘Smith’ java.lang.String java.lang.String number, type and name of
3 int year name:
8–11 "h___" place: instance variables
12–15 6 length of string 1934 5 Smith 6 London h1 values of instance variables
16–19 "Lond" ‘London’
20-23 "on__" The true serialized form contains additional type markers; h0 and h1 are
24–27 1934 unsigned long handles
The flattened form representsPerson

a struct with value: {‘Smith’, ‘London’, 1934}
Indication of Java serialized form
CORBA CDR message
Client Server
Request
doOperation
message getRequest
32 bits 32 bits 32 bits 32 bits select object

(wait) execute
Internet address port number time object number interface of
remote object Reply method
message sendReply
(continuation)
Representation of a remote object reference
Request-reply communication
public byte[] doOperation (RemoteObjectRef o, int methodId, byte[] arguments) Request-reply message structure
sends a request message to the remote object and returns the reply.
The arguments specify the remote object, the method to be invoked and the
arguments of that method. messageType int (0=Request, 1= Reply)
public byte[] getRequest ();
acquires a client request via the server port. requestId int
public void sendReply (byte[] reply, InetAddress clientHost, int clientPort);
sends the reply message reply to the client at its Internet address and port. objectReference RemoteObjectRef
methodId int or Method
Operations of the request-reply protocol arguments array of bytes
HTTP request message

RPC exchange protocols
method URL or pathname HTTP version headers message body

Name Messages sent by GET //www.dcs.qmw.ac.uk/index.htmlHTTP/ 1.1
Client Server Client
R Request
RR Request Reply
RRA Request Reply Acknowledge reply
Distributed Systems - IPC Distributed Systems - DFS
In this section we will present an important subject in distributed systems,

the Distributed File Systems. The idea is to understand how they work
HTTP reply message And present case study examples.
Therefore, we will :
HTTP version status code reason headers message body
HTTP/1.1 200 OK resource data
Distributed Systems - DFS Distributed Systems - DFS
z Understand the requirements that affect the design of z In first generation of distributed systems
distributed services
z NFS: understand how a relatively simple, widely-used service is
(1974-95), file systems (e.g. NFS) were the
designed only networked storage systems.
– Obtain a knowledge of file systems, both local and
z With the advent of distributed object systems
networked
– Caching as an essential design technique
(CORBA, Java) and the web, the picture has
– Remote interfaces are not the same as APIs become more complex.
– Security requires special consideration
z Recent advances: appreciate the ongoing research that often
leads to major advances
Storage systems and their properties
* *
Types of consistency between copies: 1 - strict one-copy consistency

√ - approximate consistency
X - no automatic consistency
z Persistent stored data sets

Sharing Persis- Distributed Consistency Example z Hierarchic name space visible to all processes
tence cache/replicas maintenance
z API with the following characteristics:
Main memory 1 RAM – access and update operations on persistently stored data sets
File system 1 UNIX file system – Sequential access model (with additional random facilities)
Distributed file system Sun NFS z Sharing of data between users, with access control
Web server z Concurrent access:
Web
– certainly for read-only access
Distributed shared memory Ivy (Ch. 16) – what about updates?
Remote objects (RMI/ORB) 1 CORBA z Other features:
Persistent object store CORBA Persistent
– mountable file stores
1
Object Service – more? ...
Persistent distributed object store PerDiS, Khazana
WHAT IS A FILE SYSTEM ?
* *
UNIX file system operations File system modules
filedes = open(name, mode) Opens an existing file with the given name.
Directory module: relates file names to file IDs
filedes = creat(name, mode) Creates a new file with the given name.
Both operations deliver a file descriptor referencing the open
file. The mode is read, write or both. File module: relates file IDs to particular files
status = close(filedes) Closes the open file filedes. Access control module: checks permission for operation requested
count = read(filedes, buffer, n) Transfers n bytes from the file referenced by filedes to buffer.
count = write(filedes, buffer, n) Transfers n bytes to the file referenced by filedes from buffer. File access module: reads or writes file data or attributes
Both operations deliver the number of bytes actually transferred
and advance the read-write pointer. Block module: accesses and allocates disk blocks
pos = lseek(filedes, offset, Moves the read-write pointer to offset (relative or absolute,
whence) depending on whence). Device module: disk I/O and buffering
status = unlink(name) Removes the file name from the directory structure. If the file
has no other names, it is deleted.
status = link(name1, name2) Adds a new name (name2) for a file (name1).
status = stat(name, buffer) Gets the file attributes for file name into buffer.
* *
Distributed Systems - DFS

File attribute record structure
File service requirements
Tranparencies
Concurrency properties
Replication properties
Heterogeneity
Access:
Fault Sameproperties
tolerance operations
Consistency
Isolation
Security
File length File service
Efficiency
Service can maintains
be accessed multiple
by identical
clients copies
running on
Location:
Service
Unix Same
must
offers name space
continue
one-copy update after
tocontrol
operate relocation
even
semantics when
for as
Creation timestamp z Transparenc File-level
of files
Must
Goal or
for record-level
maintain
(almost) any access
OS
distributed or locking
hardware
file systems and privacy
platform.
is usually
clients of
operations files
make or processes
onerrors
local or crash.
files - caching is
updated y Other
•Design for
formslocal
Load-sharing of files.
performance concurrency
between
comparable control
servers to minimise
makes
tothe
local
Read timestamp Mobility: must be
Automatic
completely
• service
at-most-once compatible
relocation
transparent.
semantics withof files isfile system.
file
by system: contention
•based
more on identity of user making request
scalable
Write timestamp z Concurrency systems of different OSes
possible
• •Difficult
Local
to
at-least-once
access
achieve
•identities
has
the
semantics
ofbetter same
remote for distributed
users
response must be
(lower
file
Attribute timestamp z Replication Performance:
Service
systems Satisfactory
interfaces
while must performance
be
maintaining open good- across
precise
latency) authenticated
•requires idempotent operations
a specified
specifications
performance of
and range
APIs areofpublished.
scalability. system loads
Reference count z Heterogeneit Service •privacy
must requires secure communication
y • Fault
Scaling: Service can be expanded tomachine
tolerance resume after a server meet
Owner crashes.
Service interfacesloads are open to all processes
additional
Full replication is difficult to implement.
File type z Fault If thenot excluded
service by a firewall.
is replicated, it can continue to
updated Caching (of all or part of a file) gives most of
Access control list tolerance operate even during
•vulnerable to a server crash.and other
impersonation
by owner: the benefits (except fault tolerance)
z Consistency attacks
E.g. for UNIX: rw-rw-r--
z Security
z Efficiency..
* *
Model file service architecture
Lookup
AddName
File Group
UnName To construct a globally
GetNames
unique ID we use some
A collection of files that can be located on
Client computer Server computer unique attribute of the
any server or moved between servers
while maintaining the same names. machine on which it is
Directory service – Similar to a UNIX filesystem
created, e.g. IP number,
program program even though the file group
– Helps with distributing the load of
file serving between several
may move subsequently.
servers.
Flat file service – File groups have identifiers which
File Group ID:
are unique throughout the system
Client module Read 32 bits 16 bits
(and hence for an open system,
Write they must be globally unique). IP address date
Create
Delete z Used to refer to file groups and
GetAttributes files
SetAttributes
* *
NFS Architecture
Client computer
Case Study: Sun NFS Client computer Application

NFS Server computer
program Client
z An industry standard for file sharing on local networks since the Application Application Application
Kernel program
1980s program program
UNIX
z An open standard with clear and simple interfaces system calls
z Closely follows the abstract file service model defined above UNIX kernel Virtual file system Virtual file system
z Supports many of the design requirements already mentioned: Operations Operations
on
– transparency on local files
file system
remote files
– heterogeneity UNIX NFS UNIX
NFS NFS Client
file file
Other
– efficiency client server
system system
– fault tolerance
z Limited achievement of:
– concurrency NFS
protocol
– replication (remote operations)
– Consistency and security
* *
NFS Architecture:
Does the implementation have to be in the system kernel? But, for a Unix implementation there are advantages:
– Binary code compatible - no need to recompile applications
z Standard system calls that access remote files can be routed
No: through the NFS client module by the kernel
– there are examples of NFS clients and servers that run – Shared cache of recently-used blocks at client
at application-level as libraries or processes (e.g. early – Kernel-level server can access i-nodes and file blocks directly
Windows and MacOS implementations, current z but a privileged (root) application program could do almost the
PocketPC, etc.) same.
– Security of the encryption key used for authentication.
* *
NFS server operations (simplified)

NFS access control and
• read(fh, offset, count) -> attr, data fh = fileModel flat file service
handle:
authentication
• write(fh, offset, count, data) -> attr Read(FileId, i, n) -> Data
Filesystem identifier i-node number i-node generation
• create(dirfh, name, attr) -> newfh, attr Write(FileId, i, Data)
• remove(dirfh, name) status Create() -> FileId z Stateless server, so the user's identity and access rights must be
• getattr(fh) -> attr Delete(FileId) checked by the server on each request.
• setattr(fh, attr) -> attr GetAttributes(FileId) -> Attr – In the local file system they are checked only on open()
• lookup(dirfh, name) -> fh, attr SetAttributes(FileId, Attr) z Every client request is accompanied by the userID and groupID
• rename(dirfh, name, todirfh, toname) – not shown in the Figure 8.9 because they are inserted by the RPC
Model directory service
• link(newdirfh, newname, dirfh, name) system
Lookup(Dir, Name) -> FileId
• readdir(dirfh, cookie, count) -> entries z Server is exposed to imposter attacks unless the userID and groupID
AddName(Dir, Name, File)
• symlink(newdirfh, newname, string) -> are protected by encryption
UnName(Dir, Name)
status z Kerberos has been integrated with NFS to provide a stronger and
GetNames(Dir, Pattern)
• readlink(fh) -> string more comprehensive security solution
->NameSeq
• mkdir(dirfh, name, attr) -> newfh, attr – Kerberos is described in Chapter 7. Integration of NFS with
• rmdir(dirfh, name) -> status Kerberos is covered later in this chapter.
• statfs(fh) -> fsstats * *
Local and remote file systems
Mount service accessible on an NFS client
z Mount operation: Server 1 Client

(root)
Server 2
(root)
(root)
mount(remotehost, remotedirectory,
localdirectory)
export . . . vmunix usr nfs
z Server maintains a table of clients who have
mounted filesystems at that server
Remote Remote
z Each client maintains a table of mounted file people
mount
students x staff
mount
users
systems holding:
big jon bob . . . jim ann jane joe
< IP address, port number, file handle>
Note: The file system mounted at /usr/students in the client is actually the sub-tree located at /export/people in
z Hard versus soft mounts Server 1; the file system mounted at /usr/staff in the client is actually the sub-tree located at /nfs/users in Server 2.
* *
Automounter Kerberized NFS
NFS client catches attempts to access 'empty' mount points and z Kerberos protocol is too costly to apply on each file access request
routes them to the Automounter z Kerberos is used in the mount service:
– Automounter has a table of mount points and multiple – to authenticate the user's identity
candidate serves for each – User's UserID and GroupID are stored at the server with the
– it sends a probe message to each candidate server and client's IP address
then uses the mount service to mount the filesystem at the z For each file request:
first server to respond – The UserID and GroupID sent must match those stored at the
z Keeps the mount table small server
z Provides a simple form of replication for read-only filesystems – IP addresses must also match
– E.g. if there are several servers with identical copies of z This approach has some problems
/usr/lib then each server will have a chance of being – can't accommodate multiple users sharing the same client
mounted at some clients. computer
* – all remote filestores must be mounted each time a user logs in *
NFS optimization - server caching NFS optimization - server caching
z Similar to UNIX file caching for local files: z NFS v3 servers offers two strategies for updating the disk:
– pages (blocks) from disk are held in a main memory buffer cache
– write-through - altered pages are written to disk as soon as they
until the space is required for newer pages. Read-ahead and
are received at the server. When a write() RPC returns, the NFS
delayed-write optimizations.
client knows that the page is on the disk.
– For local files, writes are deferred to next sync event (30 second
– delayed commit - pages are held only in the cache until a commit()
intervals)
call is received for the relevant file. This is the default mode used
– Works well in local context, where files are always accessed by NFS v3 clients. A commit() is issued by the client whenever a
through the local cache, but in the remote case it doesn't offer file is closed.
necessary synchronization guarantees to clients.
* *
NFS optimization - client caching NFS optimization - client caching
z Timestamp-based validity check

z Server caching does nothing to reduce RPC traffic between client and
– reduces inconsistency, but doesn't eliminate it
server
– validity condition for cache entries at the client:
– further optimization is essential to reduce server load in large
(T - Tc < t) v (Tmclient = Tmserver)
networks
– t is configurable (per file) but is typically set to
– NFS client module caches the results of read, write, getattr, lookup 3 seconds for files and 30 secs. for directories
and readdir operations – it remains difficult to write distributed
– synchronization of file contents (one-copy semantics) is not applications that share files with NFS t freshness guarantee
guaranteed when two or more clients are sharing the same file. Tc time when cache entry was
last validated
Tm time when block was last
updated at server
T current time
* *
Other NFS optimizations NFS performance
z Sun RPC runs over UDP by default (can use TCP if required) z Early measurements (1987) established that:
z Uses UNIX BSD Fast File System with 8-kbyte blocks – write() operations are responsible for only 5% of server calls in
z reads() and writes() can be of any size (negotiated between client and typical UNIX environments
server) z hence write-through at server is acceptable
z the guaranteed freshness interval t is set adaptively for individual files – lookup() accounts for 50% of operations -due to step-by-step
to reduce gettattr() calls needed to update Tm pathname resolution necessitated by the naming and mounting
z file attribute information (including Tm) is piggybacked in replies to all semantics.
file requests
* *
NFS performance NFS performance
z More recent measurements (1993) show high z Provides a good solution for many environments
performance: including:
1 x 450 MHz Pentium III: > 5000 server ops/sec, < 4 millisec. – large networks of UNIX and PC clients
average latency – multiple web server installations sharing a single file store
24 x 450 MHz IBM RS64: > 29,000 server ops/sec, < 4 millisec.
average latency
see www.spec.org for more recent measurements
* *
NFS - Summary NFS - Summary
z An excellent example of a simple, robust, high- Concurrency: Limited but adequate for most purposes;
performance distributed service. when read-write files are shared concurrently between
z Achievement of transparencies : clients, consistency is not perfect.
Access: Excellent; the API is the UNIX system call Replication: Limited to read-only file systems; for
interface for both local and remote files. writable files, the SUN Network Information Service
Location: Not guaranteed but normally achieved; naming (NIS) runs over NFS and is used to replicate essential
of filesystems is controlled by client mount operations, system files.
but transparency can be ensured by an appropriate
system configuration.
NFS - Summary NFS - Summary
Achievement of transparencies (continued): Performance: Good; multiprocessor servers achieve

very high performance, but for a single filesystem it's
Failure: Limited but effective; service is suspended if a
not possible to go beyond the throughput of a
server fails. Recovery from failures is aided by the
multiprocessor server.
simple stateless design.
Scaling: Good; filesystems (file groups) may be
Mobility:Hardly achieved; relocation of files is not
subdivided and allocated to separate servers.
possible, relocation of file systems is possible, but
Ultimately, the performance limit is determined by the
requires updates to client configurations.
load on the server holding the most heavily-used
filesystem (file group).
* *
Distribution of processes in the File name space seen by clients of
Andrew File System AFS
Workstations Servers
Local Shared
User Venus / (root)
program
Vice
UNIX kernel
UNIX kernel
tmp bin . . . vmunix cmu
User Venus Network
program
UNIX kernel
bin
Vice
Venus
User
program UNIX kernel
Symbolic
UNIX kernel
links
* *
Implementation of file system calls

System call interception in AFS in AFS
Workstation
User process UNIX kernel Venus Net Vice
open(FileName, If FileName refers to a
mode) file in shared file space,
pass the request to Check list of files in
local cache. If not
Venus. present or there is no
valid callback promise ,
User Venus
send a request for the
file to the Vice server
program that is custodian of the
volume containing the Transfer a copy of the
UNIX file Non-local file file. file and a callback
promise to the
system calls operations Place the copy of the
workstation. Log the
callback promise.
file in the local file
Open the local file and system, enter its local
return the file name in the local cache
list and return the local
UNIX kernel descriptor to the
application. name to UNIX.
read(FileDescriptor, Perform a normal
Buffer, length) UNIX read operation
UNIX file system on the local copy.
write(FileDescriptor, Perform a normal
Buffer, length) UNIX write operation
on the local copy.
close(FileDescriptor) Close the local copy
Local and notify Venus that
the file has been closed. If the local copy has
been changed, send a
Replace the file
disk copy to the Vice server
that is the custodian of contents and send a
callback to all other
* *
the file.
clients holding c a llba c k
promises on the file.
The main components of the Vice
service interface Recent advances in file services
Fetch(fid) -> attr, data Returns the attributes (status) and, optionally, the contents of file NFS enhancements
identified by the fid and records a callback promise on it. WebNFS - NFS server implements a web-like service on a well-
Store(fid, attr, data) Updates the attributes and (optionally) the contents of a specified known port. Requests use a 'public file handle' and a pathname-
file. capable variant of lookup(). Enables applications to access NFS
Create() -> fid Creates a new file and records a callback promise on it. servers directly, e.g. to read a portion of a large file.
Remove(fid) Deletes the specified file. One-copy update semantics (Spritely NFS, NQNFS) - Include an
SetLock(fid, mode) Sets a lock on the specified file or directory. The mode of the open() operation and maintain tables of open files at servers,
lock may be shared or exclusive. Locks that are not removed which are used to prevent multiple writers and to generate
expire after 30 minutes.
callbacks to clients notifying them of updates. Performance was
ReleaseLock(fid) Unlocks the specified file or directory. improved by reduction in gettattr() traffic.
RemoveCallback(fid) Informs server that a Venus process has flushed a file from its
cache.
BreakCallback(fid) This call is made by a Vice server to a Venus process. It cancels
the callback promise on the relevant file. * *
Recent advances in file services New design approaches
Improvements in disk storage organisation Distribute file data across several servers
RAID - improves performance and reliability by striping data – Exploits high-speed networks (ATM, Gigabit Ethernet)
redundantly across several disk drives – Layered approach, lowest level is like a 'distributed virtual disk'
Log-structured file storage - updated pages are stored – Achieves scalability even for a single heavily-used file
contiguously in memory and committed to disk in large 'Serverless' architecture
contiguous blocks (~ 1 Mbyte). File maps are modified whenever
an update occurs. Garbage collection to recover disk space. – Exploits processing and disk resources in all available network
nodes
– Service is distributed at the level of individual files
* *
New design approaches New design approaches
Examples: z Replicated read-write files

xFS : Experimental implementation demonstrated a substantial – High availability
performance gain over NFS and AFS
– Disconnected working
Frangipani : Performance similar to local UNIX file access
z re-integration after disconnection is a major problem if
Tiger Video File System
conflicting updates have occurred
Peer-to-peer systems: Napster, OceanStore (UCB), Farsite (MSR),
Publius (AT&T research) - see web for documentation on these – Examples:
very recent systems z Bayou system
z Coda system
* *
Summary Summary
z Sun NFS is an excellent example of a distributed service z Most client and server failures can be masked
designed to meet many important design requirements
z Superior scalability can be achieved with whole-file
z Effective client caching can produce file service serving (Andrew FS) or the distributed virtual disk
performance equal to or better than local file systems approach
z Consistency versus update semantics versus fault Future requirements:

tolerance remains an issue – support for mobile users, disconnected operation, automatic re-
integration (Cf. Coda file system)
– support for data streaming and quality of service (Cf. Tiger file
system)
* *
The role of names and name
Distributed Systems – Names Services services
The objectives of this section are – z Resources are accessed using identifier or reference
– An identifier can be stored in variables and retrieved from
z To understand the need for naming systems in distributed tables quickly
systems – Identifier includes or can be transformed to an address for
z To be familiar with the design requirements for distributed name an object
services z E.g. NFS file handle, Corba remote object reference
– A name is human-readable value (usually a string) that can
z To understand the operation of the Internet naming service -
be resolved to an identifier or address
DNS
z Internet domain name, file pathname, process number
z To be familiar with the role of discovery services in mobile and z E.g ./etc/passwd, http://www.cdk3.net/
ubiquitous computer systems
* *
The role of names and name

services Requirements for name spaces
z For many purposes, names are preferable to z Allow simple but meaningful names to be used
identifiers z Potentially infinite number of names
– because the binding of the named resource to a physical z Structured
location is deferred and can be changed – to allow similar subnames without clashes
– because they are more meaningful to users – to group related names
z Resource names are resolved by name services z Allow re-structuring of name trees
– to give identifiers and other useful attributes – for some types of change, old programs should continue to
work
z Management of trust
* *
Composed naming domains used to
access a resource from a URL Names and resources
URL Currently, different name systems are used for each type of resource:
http://www.cdk3.net:8888/WebExamples/earth.html resource name identifies
DNS lookup file pathname file within a given file system
Resource ID (IP number, port number, pathname) process process id process on a given computer
port port number IP port on a given computer
138.37.88.61 8888 WebExamples/earth.html Uniform Resource Identifiers (URI) offer a general solution for any type of
ARP lookup resource. There two main classes:
URL Uniform Resource Locator
(Ethernet) Network address
– typed by the protocol field (http, ftp, nfs, etc.)
2:60:8c:2:b0:5a – part of the name is service-specific
file – resources cannot be moved between domains
URN Uniform Resource Name
Socket – requires a universal resource name lookup service - a DNS-like
Web server * system for all resources *
Names and resources Iterative navigation
More on URNs
format: urn:<nameSpace>:<name-within-namespace>
examples:
NS2
a) urn:ISBN:021-61918-0
2
b) urn:dcs.qmul.ac.uk:TR2000-56 1 Name
Client NS1 servers
resolution: 3
a) send a request to nearest ISBN-lookup service - it would return NS3
whatever attributes of a book are required by the requester
A client iteratively contacts name servers NS1–NS3 in order to resolve a name
b) send a request to the urn lookup service at dcs.qmul.ac.uk
- it would return a url for the relevant document
* *
Iterative navigation Iterative navigation
Used in:
DNS: Client presents entire name to servers, starting at a local
Reason for NFS iterative name resolution server, NS1. If NS1 has the requested name, it is resolved, else
This is because the file service may encounter a symbolic link NS1 suggests contacting NS2 (a server for a domain that
includes the requested name).
(i.e. an alias) when resolving a name. A symbolic link must be
NFS: Client segments pathnames (into 'simple names') and
interpreted in the client’s file system name space because it may
presents them one at a time to a server together with the
point to a file in a directory stored at another server. The client filehandle of the directory that contains the simple name.
computer must determine which server this is, because only the
client knows its mount points. (p.362.)
* *
Non-recursive and recursive server- Non-recursive and recursive server-

controlled navigation controlled navigation
NS2
NS2 DNS offers recursive navigation as an option, but iterative is the
2
4
standard technique. Recursive navigation must be used in
2 1 3
client NS1 domains that limit client access to their DNS information for
1
client NS1 5 security reasons.
4 3 NS3
NS3
Recursive
Non-recursive server-controlled
server-controlled
A name server NS1 communicates with other name servers on behalf of a client
* *
DNS - The Internet Domain Name DNS - The Internet Domain Name
System System
z A distributed naming database

z Name structure reflects administrative structure of the Internet
z Rapidly resolves domain names to IP addresses
– exploits caching heavily
Basic DNS algorithm for name resolution (domain name -> IP number)
– typical query time ~100 milliseconds • Look for the name in the local cache
z Scales to millions of computers • Try a superior DNS server, which responds with:
– partitioned database – another recommended DNS server
– the IP address (which may not be entirely up to date)
– caching
z Resilient to failure of a server
– replication
* *
DNS name servers

a.root-servers.net
(root)
Without caching
uk
ns1.nic.uk purdue.edu
a.root-servers.net
(uk) yahoo.com
(root)
.... ns.purdue.edu
(purdue.edu)
Note: Name server names are in co.uk
uk
italics, and the corresponding purdue.edu ac.uk
ns1.nic.uk ns0.ja.net
domains are in parentheses. yahoo.com ...
(uk) (ac.uk) * .purdue.edu
Arrows denote name server .... ns.purdue.edu
entries (purdue.edu) ic.ac.uk
co.uk
authoritative path to lookup: ac.uk qmw.ac.uk
ns0.ja.net ...
jeans-pc.dcs.qmw.ac.uk ...
(ac.uk) * .purdue.edu
IP: alpha.qmw.ac.uk
ic.ac.uk alpha.qmw.ac.uk dns0.dcs.qmw.ac.uk dns0-doc.ic.ac.uk 2 client.ic.ac.uk

qmw.ac.uk (qmw.ac.uk) (dcs.qmw.ac.uk) (ic.ac.uk)
... IP:jeans-pc.dcs.qmw.ac.uk
IP:ns0.ja.net
alpha.qmw.ac.uk dns0.dcs.qmw.ac.uk dns0-doc.ic.ac.uk

dcs.qmw.ac.uk
*.qmw.ac.uk
*.dcs.qmw.ac.uk *.ic.ac.uk
14
(qmw.ac.uk) (dcs.qmw.ac.uk) (ic.ac.uk) jeans-pc.dcs.qmw.ac.uk ?
dcs.qmw.ac.uk *.dcs.qmw.ac.uk *.ic.ac.uk

*.qmw.ac.uk IP:dns0.dcs.qmw.ac.uk 3
* *
DNS server functions and
configuration DNS resource records
Record type Meaning Main contents
A A computer address IP number
z Main function is to resolve domain names for computers, i.e. to get NS An authoritative name server Domain name for server
their IP addresses CNAME The canonical name for an alias Domain name for alias
– caches the results of previous searches until they pass their 'time SOA Marks the start of data for a zone Parameters governing the zone
to live' WKS A well-known service description List of service names and protocols
PTR Domain name pointer (reverse Domain name
z Other functions: lookups)
– get mail host for a domain HINFO Host information Machine architecture and operating
– reverse resolution - get domain name from IP address
system
MX Mail exchange List of <preference, host> pairs
– Host information - type of hardware and OS
TXT Text string Arbitrary text
– Well-known services - a list of well-known services offered by a
host
– Other attributes can be included (optional)
* *
DNS issues Directory and discovery services
z Name tables change infrequently, but when they do, z Directory service:- 'yellow pages' for the resources in a
caching can result in the delivery of stale data. network
– Clients are responsible for detecting this and recovering – Retrieves the set of names that satisfy a given
z Its design makes changes to the structure of the name description
space difficult. For example: – e.g. X.500, LDAP, MS Active Directory Services
– merging previously separate domain trees under a new root z (DNS holds some descriptive data, but:
– moving subtrees to a different part of the structure (e.g. if – the data is very incomplete
Scotland became a separate country, its domains should all be – DNS isn't organised to search it)
moved to a new country-level domain.
The GNS, is a research system that solves the above
issues.
* *
Directory and discovery services Revision: Spontaneous networks
z Discovery service:- a directory service that also:

– is automatically updated as the network configuration changes Music
service
– meets the needs of clients in spontaneous networks (Section gateway
Alarm
service
2.2.3)
Internet
– discovers services required by a client (who may be mobile) within
the current scope, for example, to find the most suitable printing
service for image files after arriving at a hotel. Hotel wireless
network
– Examples of discovery services: Jini discovery service, the Discovery
service
'service location protocol', the 'simple service discovery protocol' Camera
(part of UPnP), the 'secure discovery service'.
TV/PC Guest's
Laptop PDA
devices
* *
Revision: Spontaneous networks Revision: Spontaneous networks
Discovery service
z Easy connection of guest's devices • .A database of services with lookup based on service
– wireless network
description or type, location and other criteria, E.g.
1. Find a printing service in this hotel
– automatic configuration compatible with a Nikon camera
z Easy integration with local services 2. Send the video from my camera to the digital TV in my room.
– discovery of services relevant to guest's needs
• Automatic registration of new services
• Automatic connection of guest's clients to the discovery service
* *
Revision: Spontaneous networks 1. ‘finance’
Printing
service
admin
Mobile client
lookup service?
admin
Lookup Client
Other issues for spontaneous networking: service
Network 2. Here I am: .....
• Unreliable connections when mobile 4. Use printing
admin, finance
service
• Security exposure of ports and communication channels
3. Request Lookup
Corporate Printing service
printing &
infoservice service
receive
financeproxy
Service discovery in Jini

* *
Service discovery in Jini Topics not covered
z GNS case study

z Jini services register their interfaces and descriptions with the Jini
lookup services in their scope – an early research project (1985) that developed solutions for the
problems of:
z large name spaces
z Clients find the Jini lookup services in their scope by IP multicast
z restructuring the name space
z X.500 and LDAP
z Jini lookup service searches by attribute or by interface type
– The designers of Jini argue convincingly that this the only reliable way to
– a hierarchically-structured standard directory service designed for
do discovery world-wide use
– accommodates resource descriptions in a standard form and their
retrieval for any resource (online or offline)
– never fully deployed, but the standard forms the basis for LDAP,
the Lightweight Directory Access Protocol, which is widely used
* *
Topics not covered Summary
z Trading services Name services:

– Directories of services with retrieval by attribute searching – defer the binding of resource names to addresses (and other
attributes)
– Brokers negotiate the contract for the use of a service, including
negotiation of attribute such as quality and quantity of service – Names are resolved to give addresses and other attributes
– Goals :
z Scalability (size of database, access traffic (hits/second), update
traffic)
z Reliability
z Trust management (authority of servers)
– Issues
z exploitation of replication and caching to achieve scalability without
compromising the distribution of updates
* z navigation methods *
Summary
Directory and discovery services:

– 'yellow pages' retrieval by attributes Questions ?
– dynamic resource registration and discovery
End of Part I
(Distributed Systems)
*
z Distributed Systems High-Performance Networks
z High Performance Networks Networks become the important part to any system, because nowadays
distributed local and remote systems are the bases of any computational
environment. However, different network approaches exists.
z Clusters and Computational Grids In this module of the course we will study high performance networks.
ISO/OSI Model and TCP/IP Architecture
Course Outline High Performance Networks

The recommended literature are presented below : Application
z Tecnologias de Redes de Comunicação e Computadores, Mario
Application
Dantas, Axcel Books, ISBN 85-7323-169-6 Presentation
z High Performance Networks - Technology and Protocols Session
(Editor)Ahmed N. Tantawy, Kluwer, ISBN 0-7923-9371-6;
ISO/OSI TCP/IP Transport
Transport
z Sharing Bandwidth, Simon St. Laurent, IDG Books, ISBN 0-7645-
7009-9; Internet Internet
z 4 - Internetworking with TCP/IP - Volume I Principles,
Protocols, and Architecture, Douglas E. Comer, Third Edition,
Link Subnet
Prentice Hall, 1995, ISBN 0-13-216987-8;
Physical
Internet
Internet Architecture
FTP, TELNET, SMTP, DNS, SNMP
TCP UDP
IP, ICMP, ARP, RARP
Sub-net access
TCP/IP Protocol Family TCP/IP Protocol Family
Application
arp rlogin,ftp,... NFS,DNS,.. tracert arp rlogin,ftp,... NFS,DNS,.. tracert
TCP UD Transport TCP UD

P P
IP ICMP IP ICMP
Net
ARP , Device drivers ARP , Device drivers
Net Net
Sub-
Sub-Net
TCP - Connection
High Performance Networks
Sends SYN seq=x

Receives SYN
Send ACK x + 1, SYN seq=y
Receives SYN + ACK

Sends ACK y + 1
Receives ACK
Machine A Machine B
TCP - Acknowledegment and retransmission

High Performance Networks
Go-back-n x seletive retransmission
Lightweight Protocols
1 2 3 4 5 6 7 8 9 10
Go-back-n 5 6 7 8 9 10
Seletive retransmission 5
High Performance Networks High Performance Networks
Metric Multicast 1:3 x FTP "Multicast" 1:3 150.000 9

Buffer 1024 bytes XTP multicast 1:2
135.000 8
TCP p/ c4
(Timing)
TCP p/ c4 120.000 TCP p/ c5
7
T h r o u g h p u t ( M b it s / s )
TCP p/ c5 105.000
5000 6 XTP multicast 1:2
T e m p o (m s )
4000 90.000
5
Tem po (s)
3000 Metric Multicast 1:3 75.000

4
2000 FTP "Multicast" 1:3 60.000
3
1000 45.000
0 30.000 2
1M
2M
4M
8M
16M
32M
64M
128M
256M
512M
64k
128k
256k
512k
1GB
15.000 1
Tam anho (bytes)
0 0
1M 4M 16M 64M 1M 4M 16M 64M
Tamanho do Arquivo Tamanho do Arquivo
High Performance Networks High Performance Networks

220.000 9
XTP multicast 1:3 200.000 8 TCP p/ c2
280.000 9
180.000 TCP p/ c4
TCP p/ c2 7 260.000 TCP p/ c2
TCP p/ c5 XTP multicast 1:4 8
160.000 240.000
TCP p/ c4 6 220.000 7
TCP p/ c3
140.000 XTP multicast 1:3 TCP p/ c2
T e m p o (m s )
TCP p/ c5 TCP p/ c4
200.000
120.000 5 TCP p/ c3 180.000 6
TCP p/ c5
T e m p o (m s )
100.000 TCP p/ c4 160.000 5
4 140.000 XTP multicast 1:4
80.000 TCP p/ c5 120.000 4
3
60.000 100.000 3
2 80.000
40.000 60.000 2
20.000 1 40.000
1
20.000
0 0 0
0
1M 4M 16M 64M 1M 4M 16M 64M 1M 4M 16M 64M 1M 4M 16M 64M
Tamanho do Arquivo Tamanho do Arquivo Tamanho do Arquivo Tamanho do Arquivo
Course Outline
z Distributed Systems
Questions ?
z High Performance Networks
z Clusters and Computational Grids
End of Part II
(High Performance Networks)
• Computing Paradigms and Applications The recommended literature for this part of the course
is :
• Users
z The Grid : Blueprint for a New Computing
• Grid Architecture Infrastructure, Foster,I. , Kesselman, C.
Morgan Kaufmann, 1998, ISBN 1558604758.
• Grid Computing Environments
• Experimental Results z Grid Computing: Making The Global Infrastructure a

Reality, Berman, F., Fox, G., Hey, T. , John Wiley &
Sons, 2003, ISBN 0470853190.
Clusters and Computational Grids Computing Paradigms and Applications
A important difference between clusters and grids is

mainly based in the way resources are managed.
What is the difference between
Cluster and Computational Grid ? In the clusters, the resource allocation is
performed by a centralized resource manager and
all nodes cooperatively work together as a single
unified resource.
Inside the Grids, each node has its own resource

manager and do not target for providing a single
system view.
Computing Paradigms and Applications Computing Paradigms and Applications
Clusters Clusters
High Performance Computing (HPC) traditionally has been based

on specific parallel architectures, such as MPP (Massively Parallel What is a cluster configuration ?
Processors) and SMP (Symmetric Memory Processors)
More recently, low cost computers gather either physically or

virtually, are used called as Clusters or Nows. These architectures
are interesting to many organizations.
Clusters Clusters
Cluster environments are used when applications which require

processing performance can not execute in a single node.
These environments are built with a local connection of

many no expensive computers using a specific network equipment.
The following figures present examples of cluster environments.
Clusters Clusters
Clusters Clusters
Clusters Clusters and Computational Grids
Cluster management is an important task

for this new distributed architecture, many The experimental research with the I-WAY,
packages exist with this specific function first large scale Grid effort, bring to us that
(e.g. Oscar)
there were five classes of applications using
a specific computing paradigm.
Clusters and Computational Grids Clusters and Computational Grids
Computing paradigms and applications can be classify as 1. Distributed Supercomputing

following :
Applications that use this approach can be characterized by the
• Distributed Supercomputing fact that it is not possible to solve these applications in a single
computational system.
• High-Throughput Computing
The aggregation environment which we are referring to can be
• On-Demand Computing represented by all the supercomputers of a specific country or
all the workstation inside of an organization.
• Computing for Large Amount of Data
• Collaborative Computing
Examples of applications using the distributed supercomputing • Simulation of complex models such as those in weather
approach are : forecast and cosmology.
• Distributed Interactive Simulation (DIS) : this is a simulation
technique used to model the behaviour and movement of hundred
(or thousand) of entities which are usually employed for military
planning and teaching.
2. High-Throughput Computing
Classical examples for high-throughput computing are :
The main objective of this approach it solve the problem of
applications that require a transfer of a large amount of data. • Condor High-Throughput – this software environment
from the University of Wisconsin is used to manage pools
The computational environment is used for scheduling a large of hundreds workstations in the university and other labs
number of loosely couple tasks and enhance the utilization of around the world.
machines with a low workload.
3. On-Demand Computing
This class of applications usually can be characterized by the

use of resources that can not be used in the local site, because
• The Platform Computing software - used by AMD during it is not available.
the projects of K6 e K7 processors. It is reported that the
company has used all the desktops which were not in use by The resources can be computing, data streams, software,
the engineers in a specific period of time. archives and for examples experimental results.
4. Computing for Large Amount of Data
This class of application and computing paradigm covers the

Difference between this approach and distributed requirement for processing large amount of data stored in a
Supercomputing is related to the cost of performance geographic distributed fashion.
then the complete performance behaviour.
Examples are large databases and digital libraries that are
available for access in a distributed way.
The Digital Sky Survey and modern weather forecast

Systems are applications examples.
5. Collaborative Computing
NICE is a collaborative learning environment for
young children (approximately 6-8 years of age).
Examples for this class are those which are oriented to the The environment depicts a virtual island in which
improvement the relation between humans. the children can tend a virtual garden and learn
about environmental concepts.
Many collaborative applications allow the share use of
computational resources.
Users Users
Users Clusters and Computational Grids
Answers for the two questions should be based on costs and

Another approach used to understand what is a Grid, is to benefits for sharing resources.
understand who is going to use.
Therefore it is usually presented in the academic and
A Grid is above of the mechanisms of resource sharing commercial reports efforts for the following groups of grid
therefore we can image two questions : environments :
A - Which kind of entity is going to invest in the • National

infrastructure for a Grid ? • Private
• Virtual
B - Which kind of resources each community of
• Public
the entity will be share ?
Users Users
• National Grid – the target of this group is to be

a strategic computational resource and serve as a
bridge between national sharing facilities.
• Private Grid – the heath community it is an

example of private grid organization. This group,
was identified to benefit from grid configurations
because of the strategic utilization of computational
power.
NSF National Technology Grid
Users Users
z NEESgrid: national
infrastructure to couple
earthquake engineers • Virtual Grid – this community is formed by researches and
with experimental scientists which require the use of expensive equipments and a
facilities, databases,
computers, & each great computational power.
other
z On-demand access to • Public Grid – this group is basically characterized by those
experiments, data which the main activity includes services using a great
streams, computing, quantity of computational power.
archives, collaboration
NEESgrid: Argonne, Michigan, NCSA, UIUC, USC

Network for Earthquake Engineering Simulation
Users Users
Data Grids for High Energy Physics
Online Access to Scientific Instruments
~PBytes/sec
Advanced Photon Source 1 TIPS is approximately 25,000
Online System ~100 MBytes/sec SpecInt95 equivalents
wide-area There is a “bunch crossing” every 25 nsecs.

Offline Processor Farm
~20 TIPS
dissemination There are 100 “triggers” per second
~100 MBytes/sec
Each triggered event is ~1 MByte in size
real-time ~622 Mbits/sec
Tier 0 CERN Computer Centre
collection or Air Freight (deprecated)
Tier 1
archival desktop & VR clients France Regional
Centre
Germany Regional
Centre
Italy Regional
Centre
FermiLab ~4 TIPS
with shared controls ~622 Mbits/sec

storage
Tier 2 Caltech Tier2 Centre
Tier2 Centre
Tier2 Centre
Tier2 Centre
~1 TIPS ~1 TIPS ~1 TIPS ~1 TIPS ~1 TIPS
~622 Mbits/sec
Institute
Institute Institute Institute
~0.25TIPS Physicists work on analysis “channels”.
Each institute will have ~10 physicists working on one or more
Physics data cache
~1 MBytes/sec channels; data for these channels should be cached by the
institute server
tomographic reconstruction Tier 4
Physicist workstations
DOE X-ray grand challenge: ANL, USC/ISI, NIST, U.Chicago
Image courtesy Harvey Newman, Caltech
Grid Architecture
Grid Architecture Clusters and Computational Grids
Before we start to study the Grid architecture it is interesting to Virtual Organizations

know about Virtual Organizations (VO). Virtual organizations
are the entities that share resources of the Grid under a specific Virtual Organizations are different from each other considering
policy .Examples of VO are : the following parameters :
• Providers of applications, data storage and • Main objective

computational power. • Geographic extension
• Size (or physical dimensions)
• Research organizations • Time to use the facilities
• Structure
• Universities • Community
Grid Architecture Grid Architecture
Aspects such as :
Similar to the experience with Internet, researches
involved with the Grid established an architecture - authentication,
aiming the interoperability between VOs. - authorization,
- mechanism of message passing,
- resource sharing,
- scheduling and
- load balancing of tasks
are some of issues which a Grid architecture should

provide.
A standard Grid architecture was proposed as :
Application
Fabric –
Collective
Components of this layer implement local operations which
occurs in each resource mainly because of the sharing provided
Resource
by the above layers.
Application
Connectivity
Collective
Fabric
Resource
Conn
Connectivity
Five Layers Grid Architecture Fabric
Fabric – Connectivity
Mechanisms are necessary to obtain information about the In this layer exists the definition of the basic protocols necessary
structure, state and available resources. for communication and authentication for a specific transaction
of the Grid.
On the other hand, it is also important techniques to
management the QoS (Quality of Service) for each query. The communication protocols allow the data Application
exchange between the Fabric layers. This Collective

service includes the transport, routing and Resource
name services. Conn
Connectivity
Fabric
Resource
Connectivity
This layer uses the connectivity protocols(communication
The authentication protocols are responsible for building and authentication) to define protocols and APIs to
the communication services which are way to prove provide security during the negotiation, starting, control,
secure mechanism to verify the identity of users and monitoring, creating reports and details involved
resources During the individual resources operations. Application
Collective
Resource
Conn
Connectivity
Fabric
Collective
Resource
The resource layer treats the scope of individual resource
Protocol implementations of this layer utilizes calls from operations.
the Fabric to access and control local resources.
On the other hand, in the collective layer components work with
the interaction of resource collections.
Application
Collective
Resource
Conn
Connectivity
Fabric
Application
Collective
This layer is related to the users´ applications in their
The elements from this layer use the resource and application virtual organizations The previous commented layers
layers to implement a variety of services, such as : provide services for this layer.
Application
• Directory service : this facility allows members of virtual
organization to discover which are the resources available Collective
Resource
• Common Authorization Servers : this facility is also Conn

Connectivity
Fabric
design to implement a better policy to access resources.
Grid Architecture
Equivalence between the Gird and Internet Models Grid Computing Environments
Grid Internet
Grid Consortiums and Open Forums
Application
Application • C3CA
Collective • Global Grid Forum
• Australian Grid Forum
Resource • Peer-
Peer-to-
to-Peer (P2P) Working Group
• eGrid:
eGrid: European Grid Computing Initiative
Transport • Asia Pacific Grid
Connectivity
Internet
Fabric
Link
Grid Computing Environments Grid Computing Environments
Grid Consortiums and Open Forums
• GridForum Korea
• EuroTools SIG on Metacomputing
• IEEE Task Force on Cluster Computing
• New Productivity Initiative (NPI)
• The Distributed Coalition
• Content Alliance: About Content Peering
• `My´
My´ Brazilian ....
Grid Middleware Grid Middleware
• Cosm P2P Toolkit • Grid Datafarm
• Globus • GridSim:
GridSim: Toolkit for Grid Resource Modeling
and Scheduling Simultation
• GRACE: GRid Architecture for Computational
Economy • Simgrid
• Gridbus • Jxta Peer to Peer Network
• Legion: A Worldwide Virtual Computer

DataGrid Initiatives Grid Systems
•Virtual Laboratory: Tools for Data Intensive •Compute Power Market

Science on Grid • Global Operating Systems
•EU DataGrid • XtremWeb
•DIDC Data Grid work • JAVELIN: Java-Based Global Computing
•GriPhyN (Grid Physics Network) • MILAN: Metacomputing In Large Asynchronous
•HEPGrid (High Energy Physics and Grid Networks) Networks
•Particle Physics Data Grid (PPDG) • Harness Parallel Virtual Machine Project
•Datacentric Grid • Management System for Heterogeneous Networks
• PUNCH - Network Computing Hub
• MOBIDICK
Grid Systems Computational Economy
• Amica •GRACE: GRid Architecture for Computational

• MultiCluster Economy
• Poland Metacomputing •Compute Power Market (CPM)
• Echelon: Agent Based Grid Computing •G-Commerce
• Bayanihan •Mariposa: A New Approach to Distributed Data
• NeuroGrid •The Information Economy
• GridLab •FORTH Information Economies
• DAMIEN •Share Meta
• CrossGrid •D'Agent
• DIET •Program for Research on the Information Economy
Computational Economy Computational Economy
• Xenoservers - Accountable Execution of Untrusted • W3C effort: Common Markup for micropayment
Programs per-fee-links
• Electricity Trading Over the Internet Begins in Six
New England States • Agent-Based Computational Economics
• POPCORN
• CSAR: Resource Tokens and Trading Pool • Electronic Brokerage
• OCEAN - The Open Computation Exchange & Arbitration
Network • Society for Computational Economics
• Spawn: A Distributed Computational Economy
• Market-Based Computing • Internet Ecologies
Grid Schedulers Grid Portals
• Nimrod/G Grid Resource Broker • ActiveSheets

• AppLeS
• SILVER Metascheduler • UNICORE - Uniform Interface to Computing Resources
• ST-ORM • SDSC GridPort Toolkit
• Condor/G • Enginframe
• NetSolve • Lecce GRB Portal
• DISCWorld • Grid Enabled Desktop Environments
• Computing Centre Software (CCS) • Interactive Control and Debugging of Distribution- IC2D
• NLANR Grid Portal Development Kit
Grid Programming Environments Grid Programming Environments

•Nimrod - A tool for distributed parametric modeling
•Ninf •Jave-based CoG Kit
•Cactus Code •GAF3J - Grid Application Framework for Java
•MetaMPI - Flexible Coupling of Heterogeneous •ProActive PDC
MPI Systems •REDISE - Remote and Distributed Software
•Virtual Distributed Computing Environment Engineering
•GrADS: Grid Application Development Software •Albatross: Wide Area Cluster Computing
Project
Grid Testbeds and Developments

Grid Performance Monitoring and Forecasting
• World Wide Grid (WWG)
• Network Weather Service • Polder Metacomputer
• NASA Information Power Grid (IPG)
• NetLogger • NPACI: Metasystems
• Asia Pacific Bioinformatics Network
• The Distributed ASCI Supercomputer (DAS)
• Remos • G-WAAT
• Micro Grid
• Alliance Grid Technologies
• The Alliance Virtual Machine Room
• EuroGrid
Grid Testbeds and Developments Grid Applications
• Molecular Modelling for Drug Design

• Internet Movie Project • Neuro Science - Brain Activity Analysis
• Nordic Grid • Cellular Microphysiology
• ThaiGrid • HEPGrid: High Energy Physics and the Grid
• TeraGrid Network
• Access Grid
• Irish Computational Grid (ICG)
• Globus Applications
• GrangeNet • The International Grid (iGrid)
• LHC Grid • UK Grid Apps Working Group
• I-Grid • NLANR Distributed Applications
• DataGRID - WP9: Earth Observation Science
Application
Grid Applications Grid Applications
• Particle Physics Data Grid • Australian Virtual Observatory
• DREAM project: Evolutionary Computing and • US Virtual Observatory

Agents Applications • Distributed Proofreaders
• Knowledge Grid
• Fusion Collaboratory • NEESgrid: Earthquake Engineering Virtual
• APEC Cooperation for Earthquake Simulation Collaboratory
• Australian Computational Earth Systems Simulator • Geodise: Aerospace Design Optimisation
• EarthSystemGrid • Japanese BioGrid
Experimental Results
Experimental Results Clusters and Computational Grids
Globus The resource allocation component of the Globus

environment (GRAM - Globus Resource Allocation
The Globus software environment is a project developed by Manager) is the element that acts as an interface between
Argonne National Laboratory (ANL) and University of global and local services.
Southern California. In our work we use the version 1.1.4 of t
he Globus software package because this release provides Application programmers use the GRAM element,
support to MPI applications. through the gatekeeper software portion which is
responsible for the user authentication and association
The Globus environment is composed by a set of components with a local computer account.
implementing basic services to resource allocation,
communication, security, process management
and access to remote data .
Experimental Results Experimental Results
RSL
Broker specialization
The mechanism to identify users of the grid is based on RSL
a file called map-file. In this file exists information about

Queries Information
authorized users of the grid configuration. Application
& Info Service
Ground RSL
Any requirement for resource should be translated to the Co-allocator
Resource Specification Language (RSL). Simple ground RSL

Local
GRAM GRAM GRAM
resource
managers
LSF EASY-LL NQE
Communication in the Globus environment is performed

using a communication library called Nexus. This component
defines low a level API to support high level programming
paradigms.
Examples of high level programming paradigms supported

are message passing, remote procedure call and remote I/O
procedures.
The information about the system and the grid configuration are
management by a component called Metacomputing Directory
Service (MDS).
Legion
An important aspect of the Globus software environment
is the security. The Legion software environment is a system object oriented
which is being developed since 1993 at University of Virginia.
This software tool employs the certificate approach,
which is carried by a CA (Certificate Authority) using This environment has an architecture concept of grid computing
the protocol Secure Socket Layer (SSL) providing a unique virtual machine for users´ applications.
The approach of the Legion is to have some important concepts of

a grid configuration (e.g. scalability, easy to program, fault
tolerance and security) transparent to final users.
The security component of the Legion, as the others elements of

this software, is based on an object. The application programmer
In the Legion, every entity such as processing power,
specifies the security related to an object, where it is defined
RAM memory and storage capacity is represented as
which type of mechanism is allowed.
objects. Objects communicate with each other using
services calls to a remote mechanism.
In addition, the Legion provides some extra basic mechanism to
ensure more security.
The May I method is an example. Every class should define the

method May I, which check for a called object the related allowed
access.
The traditional system file is emulated in the Legion

environment through the combination of persistent objects
with the global information of object identification.
This approach simplifies the manipulation of files to

application programmers. In addition, it is allow to users
to add fault tolerance characteristics to applications using
rollback and recovery mechanisms
Grid Environment Legion Globus
Software requirement - OpenSSL 0.9.5 - SSLeay 0.9.0

- bin/ksh - OpenLDAP 1.2.7
Minimum Disk space De 250MB a 300 MB 200 MB
Minimum Memory RAM 256 MB Not specified
A CASE STUDY

Experimental Results

Hardware and Software

Environment
After providing some characteristics of the Globus and Computer

Name
AIX 1 AIX 2 AIX 3 AIX 4
Legion software tools, in this section we present our grid

Operating AIX 4.3 AIX 4.3 AIX 4.3 AIX 4.3
configuration environment. System
Processor PowerPC_ PowerPC_ PowerPC_ PowerPC_

It is important to mention that all the machines were in 604
233 MHz
604
MHz
233 604
MHz
233 604
MHz
233
the same laboratory. However, using a Ethernet Layer 3 Memory RAM 256 MB 128 MB 128 MB 512 MB
Switch we were able to have the abstraction of a WAN
(Wide Area Network) inside this box. Hard disk Two disks Two disks Two disks Two disks
of of of 4 GB of 4 GB
9 GB 4 GB and one and one
2 GB disk 2 GB disk
In other words, this equipment could prove the abstraction Software Legion Globus Globus Legion
of a distributed resource environment for our experiments. Environment
Table I: The grid environment configuration

The Legion software provides a homogeneous view

of the grid to the application programmer. We fixed some problems using our background on AIX
and exchanging several e-mails with other AIX systems
The environment uses its own tools to create the managers. The Legion concept of file system represents
homogeneity. The procedure to install the software does an advantage of the environment.
not represent any problem, because the application
programmer needs only to uncompress binary files and The Legion file system presents a unique identifier
execute some script files. However, for the AIX for each object.
environment it is necessary more information then those
available from the software documents.
This approach provides application programmers the The bootstrap host is responsible for the domain control.
facility to access files widely distributed only using their Another drawback of the environment is the low
names. communication rate between objects.
In other words, the users only use the name of the file, The paradigm of the Legion is to be a framework
which can be storage in a local or remote machine. environment, where users can develop their own tools,
such as security and fault tolerance facilities.
On the other hand, we have verified some problems with
the package. As a first problem, we can mention the This freedom can represent some flexibility to any
necessary installation of the entire environment when the developers group. However, it does not allow the use
bootstrap host has a power failure. external tools.
The system has an infrastructure based on X509 certificate

The Globus approach allows users to use existing system and the use the mutual authentification. On the other hand,
available tools and have a uniform interface to the gird one drawback of the software is the scalability, which can
environment. Interesting features of the Globus be understood as the capability to add new resources
environment are related to the security and to the and new sites.
autonomy of the configuration.
When considering new facilities application programmers
are required to have account into all new hosts.
MATRIX MULTIPLICATION (500x500) MATRIX MULTIPLICATION (500x500)
800 800
700 700
600
600
500
ELAPSED-TIME
500
ELAPSED-TIME
400
400
300
300
200
200
100
100
0
2 4 8 16
0
NUMBER OF PROCESSES
2 4 8 16
Legion Globus NUMBER OF PROCESSES
Legion Globus MPI Nativo

End of Part III
(Clusters and Computational Grids)

SD 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SD 1

Uploaded by

Copyright:

Available Formats

Distributed Systems Course Objectives

In the end, participants will have a good idea of the basis

Prof. Mario Dantas, PhD

Course Outline Course Outline

z Distributed Systems Distributed Systems

The recommended literature are presented below and

Distributed Systems Distributed Systems

email server Desktop

email server WAP

Date Computers Webservers

Browsers 1979 – 188 0

File system of http://www.w3c.org/Protocols/Activity.html

Distributed Systems Distributed Systems

Replication transparency: enables multiple instances of resources to be used to

Transparencies Architectural Models

Mobility transparency: allows the movement of resources and clients within a

Performance transparency: allows the system to be reconfigured to improve

Distributed Systems Distributed Systems

A service provided by multiple servers

A distributed application based on peer processes

Client Web Coordination Coordination

Distributed Systems Distributed Systems

Web applets Thin clients and compute servers

a) client request results in the downloading of applet code

b) client interacts with the applet

Spontaneous networking in a hotel Real-time ordering of events

Omission and arbitrary failures

Distributed Systems Distributed Systems

Class of failure Affects Description

Timing failures Objects and principals

Class of Failure Affects Description

Principal (user) Network Principal (server)

Distributed Systems Distributed Systems

Range Bandwidth (Mbps) Latency (ms) Layer n

Distributed Systems Distributed Systems

Transport header Session

Distributed Systems Distributed Systems

IPv6 encapsulated in IPv4 packets Messages (UDP) or Streams (TCP)

Distributed Systems Distributed Systems

TCP header port

The programmer's conceptual view of a TCP/IP Internet

28 Class E (reserved): 240 to 255 0 to 255 0 to 255 1 to 254 240.0.0.0 to

Decimal representation of Internet addresses

Distributed Systems Distributed Systems

header Source address

c) Screened subnet for bastion R/filter Bastion R/filter

Distributed Systems Distributed Systems

IEEE 802 network standards Laptops

802.4 Token Bus Networks [IEEE 1985b] Base station/

802.6 Metropolitan Area Networks [IEEE 1994]

Application Header: 5 bytes

Virtual path id Virtual channel id Flags Data

Higher-layer protocols 53 bytes

ATM adaption layer

ATM protocol layers

Distributed Systems Distributed Systems - IPC

VPI = 3 VP/VC RMI and RPC

VPI = 4 request-reply protocol Middleware

Virtual path Virtual channels

Sockets and ports CORBA CDR for constructed types

Distributed Systems - IPC Distributed Systems - IPC

The flattened form representsPerson

32 bits 32 bits 32 bits 32 bits select object

dcs.qmw.ac.uk .dcs.qmw.ac.uk .ic.ac.uk