amoeba distributed operating system presentation
Active In SP
Joined: Apr 2010
09-05-2010, 01:48 AM
AMOEBA1.pptx (Size: 327.51 KB / Downloads: 200)
Â¢ AMOEBA â€œa study of distributed system
what is Amoeba
It is distributed operating system which collects a huge variety of single machines connected over a network to one ,huge computer.
It is developed at Vrije University in amsterdamby Andrew S. Tannenbum.
AMOEBA system will connect the multiple AMOEBA systems in different sites into single coherent system.
This goal is obtained by using objects and their capabilities in uniform ways
Developed at the Vrije Universiteit Amsterdam, Netherlands. Chief designer: Andrew S. Tanenbaum
Other developers were Frans Kaashock, Sape J. Mullender, Robbert van Renesse, Leendert van Doorn, Kees Verstoep and many, many more.
First proto release in 1983 (V1.0), last official release 1996 (V5.3) Supports multiple architectures: 68k, i80386, SPARC
D. Small kernel aprroach:
Â¢ System Architecture
It implements universal distributed client-server model.
Whole system need only three functions to work:
1. Transaction call from a client
3. PutReply functions on server side.
It consists of four principle components:
1. File servers:
3. Pool processors:
Currently Amoeba has only drivers for Ethernet,but other network drivers are under consideration.
Amoeba do not set upper limit for no. of computers but in some cases it is limited by n/w bandwidth or topology.
Amoeba is reasonably portable and has run on five architectures.
It is currently available on following architectures.
1. The motorola MC680x0 family
2. The intel 80386 family
3. Members of SPARC family
Processor pool may contain processors more than one type of architecture.
Â¢ Pool,specilazied server,workstation
Â¢ AMOEBA KERNEL FEATURE
AMOEBA kernel has some major features over commonly used other os kernels.
1. High performance server client communication:
Remote procedure call:
Interprocess procedure call:
Â¢ 2.Kernel administration:
Remote rebooting of kernels:
Remote status report:
Â¢ AMOEBAâ„¢s object concept & capabilities
AMOEBA is organized as a collection of objects:each with some operations that process can perform on it.
There are many object classes like files,directories,memorysegments,processes etc.
When an object is created, the server returns a Capability.
capability is used to address and protect the object.
Â¢ Process Management
A process is an object in Amoeba. Information about the processes in Amoeba are contained in capabilities and in a data structure called a process descriptor.
Amoeba supports a simple thread model. When a process starts up, it has at least one thread. The number of threads is dynamic.
Three methods are provided for thread synchronization:Mutexes,Semaphores ,Signals
Â¢ Memory Management
Amoeba supplies a simple memory management based on segments. Each process owns at least three segments:
1. Text/Code segment
2. Stack segment for the main thread/process
3. Data segment
Each further thread gets his own stack segment, and the process can allocated arbitrary additional data segments.
All segments are page protected by the underlying MMU, the kernel segments, too
All processes, the kernel too, communicate with a standardized RPC (Remote procedure call) interface. There are only three functions to reach this goal:
1. trans(req_header, req_buf, req_size, rep_header,rep_buf, rep_size)
do a transaction to another server
get a client request
send a reply to the client
Â¢ The Virtual Amoeba Machine
The Virtual Amoeba Machine Environment
Â¢ consists of these main parts:
Â¢ 5. Amoeba
Â¢ The native Amoeba kernel (called the VERTEX-Kernel), with these features:
Clean and modern micro kernel design
Easy to implement device drivers
User space device driver support
Full network performance through direct FLIP network access
The kernel operates standalone, and needs no further configuration
Â¢ General Requirements
The amoeba distributed operating system can run on many different types and brands of computers.
It is intended that it should run on network with at least five computers.
the main machine should be equipped with at least 64 MB RAM (128 MB recommended) and at least with 500MB disk space.
Currently, Fireball Ã‚Â¬Amoeba only supports Ethernet. In special only the 10 MBit/s connectivity with RJÃ‚Â¬45 or RGÃ‚Â¬58 connectors, and now 100 MBit/s Fast Ethernet, too.
According to Tanenbaum (1990), AMOEBA system has been implemented to five different CPU : 68010, NS 32016, 8088, VAX, PDP-11.
Current configuration has 48 single board VME based computers using 68020 and 68030 CPU and also 10 VAX CPU forming additional processor pool.
Current research includes connecting AMOEBA at 5 locations in 3 countries. Using Wide Area Network facilities.
Amoeba has two level of protection:
1. Ports for protecting access to server
2. Capabilities for protecting access to individual objects.
Hardware solution: A small interface box (F - box) are put between each processor module and the network.
software solution: since ports for public servers are known to all users it is easy for an intruder to impersonate a server just by doing a get_rerequest on the serverâ„¢s port.
Â¢ Comparision of Amoeba and V
Amoeba and V use the small kernel to provide the infrastructure of the distributed system.
Amoeba and V are free-market model service, Service such as the file system are in principle just an ordinary user process.
Amoeba and V use client-server and remote procedure call.
V does not have the processor pool, and there is no dynamic processor allocation. Amoeba has a processor pool and does the processor allocation.
Amoeba is more fault tolerance than V (Cheriton 1988), because V was designed for interactive workstation, so if there are something goes wrong, user can re-execute.
Â¢ Field of Application
Distributed measuring and data acquisition systems, for example remote digital camera servers connected with an Ethernet network.
The native Amoeba kernel is very well suited for embedded systems.
Distributed control systems.
High performance parallel computing and other distributed numerical computations.
Distributed file systems using raw disk access on the top of standard operating systems.
A distributed system potentially will be more reliable and low cost than a time sharing system.
By placing the other service outside the kernel and keeping the kernel as small as possible, the system is more flexible and reliable.
The client-server model with remote procedure call have proved that using basic primitive communication the overhead of communication can be reduced.
By using the object and capability model, Amoeba is more flexible and more easily be used.
Amoeba is the only one Distributed Operating System which implements Wide Area Network.
Use Search at http://topicideas.net/search.php wisely To Get Information About Project Topic and Seminar ideas with report/source code along pdf and ppt presenaion
Active In SP
Joined: Jan 2011
29-01-2011, 01:52 PM
i want amoeba distributed os ppt's so plz help me for seminar and presentation on it
Joined: Apr 2012
02-07-2012, 11:11 AM
The Amoeba Distributed Operating System
The Amoeba Distributed Operating System.pdf (Size: 38.86 KB / Downloads: 44)
In the 1980s, prices came down to the point where each user could have his or her
own personal computer or workstation. These machines were often networked together,
so that users could do remote logins on other people’s computers or share files in various
(often ad hoc) ways.
Nowadays some systems have many processors per user, either in the form of a
parallel computer or a large collection of CPUs shared by a small user community. Such
systems are usually called parallel or distributed computer systems.
WHAT IS AMOEBA?
Amoeba is a general-purpose distributed operating system. It is designed to take a
collection of machines and make them act together as a single integrated system. In
general, users are not aware of the number and location of the processors that run their
commands, nor of the number and location of the file servers that store their files. To
the casual user, an Amoeba system looks like a single old-fashioned time-sharing
Amoeba is an ongoing research project and implimentation. It should be thought of as a platform for
doing research and development in distributed and parallel systems, languages, protocols
and applications. Although it provides some UNIX emulation, and has a definite
UNIX-like flavor (including over 100 UNIX-like utilities), it is NOT a plug-compatible
replacement for UNIX. It should be of interest to educators and researchers who want
the source code of a distributed operating system to inspect and tinker with, as well as to
those who need a base to run distributed and parallel applications.
Amoeba is intended for both ‘‘distributed’’ computing (multiple independent users
working on different project and implimentations) and ‘‘parallel’’ computing (e.g., one user using 50 CPUs
to play chess in parallel). Amoeba provides the necessary mechanism for doing both
distributed and parallel applications, but the policy is entirely determined by user-level
programs. For example, both a traditional (i.e. sequential) ‘make’ and a new parallel
‘amake’ are supplied.
The basic design goals of Amoeba are: