Garg S. et al., J. Harmoniz. Res. Eng.

, 2013, 1(2), 95-99

Journal Of Harmonized Research (JOHR)

Journal Of Harmonized Research in Engineering

1(2), 2013, 95-99 ISSN 2347 – 7393

Review Article

DISTRIBUTED OPERATING SYSTEM

Shweta Garg, Shrishti Vashist, Shruti Aggarwal

CSE Department, Dronacharya College Of Engineering,

Gurgaon, India

Abstract:
A logical model of a distributed operating system has been presented. This model of a distributed
operating system contains a set of processes managing resources, connections between these
processes, and mappings of events controlling this distributed operating system into processes
managing resources. The fundamental types of resources introduced by the architecture of local
computer networks, i.e., messages and data structures describing the location of resources in the
network, have been defined. Operations on these resources and connections between the processes
managing them and processes managing other resources of the distributed operating system have
been presented. Addressing processes have been discussed. The model has been constructed in such
a way that a synthesis of different simulation tools (models) to study distributed operating systems
can be carried out.

Keywords: Ubiquitous- existing or being everywhere, Collaborative- characterised, Mitigates-to

lessen in force, Proliferation- the growth of cells by multiplication of parts.
Abbreviation:- DOS- distributed operating system, IPC-inter process communication, OS-
operating system
1. Introduction the global aggregate operating system. Each
A distributed operating system (DOS) is subset is a composite of two distinct service
software over a collection of independent, provisioners. The first is a ubiquitous minimal
networked, communicating, and physically kernel, or microkernel, that directly controls
separate computational nodes. Individual that node’s hardware. Second is a higher-level
nodes each hold a specific software subset of collection of system management components
that coordinate the node's individual and
For Correspondence: collaborative activities. These components
yadav21shikhaATgmail.com abstract microkernel functions and support
Received on: October 2013 user applications.
The microkernel and the management
Accepted after revision: November 2013
components collection work together. They
Downloaded from: www.johronline.com
support the system’s goal of integrating

www.johronline.com 95 | P a g e
 Garg S. et al., J. Harmoniz. Res. Eng., 2013, 1(2), 95-99

multiple resources and processing 3. Overview:-

functionality into an efficient and stable 3.1. The kernel
system .This seamless integration of At each locale (typically a node), the kernel
individual nodes into a global system is provides a minimally complete set of node-
referred to as transparency, or single system level utilities necessary for operating a node’s
image; describing the illusion provided to underlying hardware and resources. These
users of the global system’s appearance as a mechanisms include allocation, management,
single computational entity. and disposition of a node’s resources,
processes, communication, and input/output
management support functions.Within the
kernel, the communications sub-system is of
foremost importance for a distributed OS.
In a distributed OS, the kernel often supports a
minimal set of functions, including low-level
address space management, thread
management, and inter-process
communication (IPC). A kernel of this design
2. Description:- is referred to as a microkernel Its modular
Structure of monolithic kernel, microkernel nature enhances reliability and security,
and hybrid kernel-based operating systems essential features for a distributed OS. It is
A distributed OS provides the essential common for a kernel to be identically
services and functionality required of an OS, replicated over all nodes in a system and
adding attributes and particular configurations therefore that the nodes in a system use
to allow it to support additional requirements similar hardware. The combination of minimal
such as increased scale and availability. To a design and ubiquitous node coverage enhances
user, a distributed OS works in a manner the global system's extensibility, and the
similar to a single-node, monolithic operating ability to dynamically introduce new nodes or
system. That is, although it consists of services.
multiple nodes, it appears to users and 3.2. System management components
applications as a single-node. System management components are software
Separating minimal system-level functionality processes that define the node's policies.
from additional user-level modular services These components are the part of the OS
provides a “separation of mechanism and outside the kernel. These components provide
policy.” Mechanism and policy can be simply higher-level communication, process and
interpreted as "how something is done" versus resource management, reliability, performance
"why something is done," respectively. This and security. The components match the
separation increases flexibility and scalability. functions of a single-entity system, adding the
transparency required in a distributed
environment.
The distributed nature of the OS requires
additional services to support a node's
responsibilities to the global system. In
addition, the system management components
accept the "defensive" responsibilities of
reliability, availability, and persistence. These
responsibilities can conflict with each other. A
consistent approach, balanced perspective, and
a deep understanding of the overall system can
assist in identifying diminishing returns.

www.johronline.com 96 | P a g e
 Garg S. et al., J. Harmoniz. Res. Eng., 2013, 1(2), 95-99

Separation of policy and mechanism mitigates scalable system. However, this opportunity
such conflicts. comes at a very high cost in complexity.
3.4. The price of complexity
In a distributed operating system, the
exceptional degree of inherent complexity
could easily render the entire system an
anathema to any user. As such, the logical
price of realizing a distributed operation
system must be calculated in terms of
overcoming vast amounts of complexity in
many areas, and on many levels. This
calculation includes the depth, breadth, and
range of design investment and architectural
planning required in achieving even the most
modest implementation.
These design and development considerations
are critical and unforgiving. For instance, a
deep understanding of a distributed operating
system’s overall architectural and design
detail is required at an exceptionally early
point. An exhausting array of design
System management components overview considerations is inherent in the development
of a distributed operating system. Each of
3.3. Working together as an operating these design considerations can potentially
system affect many of the others to a significant
The architecture and design of a distributed degree. This leads to a massive effort in
operating system must realize both individual balanced approach, in terms of the individual
node and global system goals. Architecture design considerations, and many of their
and design must be approached in a manner permutations. As an aid in this effort, most
consistent with separating policy and rely on documented experience and research
mechanism. In doing so, a distributed in distributed computing.
operating system attempts to provide an 4. History:-
efficient and reliable distributed computing Research and experimentation efforts began in
framework allowing for an absolute minimal earnest in the 1970s and continued through
user awareness of the underlying command 1990s, with focused interest peaking in the
and control efforts. late 1980s. A number of distributed operating
The multi-level collaboration between a kernel systems were introduced during this period;
and the system management components and however, very few of these implementations
in turn between the distinct nodes in a achieved even modest commercial success.
distributed operating system is the functional Fundamental and pioneering implementations
challenge of the distributed operating system. of primitive distributed operating system
This is the point in the system that must component concepts date to the early 1950s.
maintain a perfect harmony of purpose, and Some of these individual steps were not
simultaneously maintain a complete focused directly on distributed computing, and
disconnect of intent from implementation. at the time, many may not have realized their
This challenge is the distributed operating important impact. These pioneering efforts
system's opportunity to produce the laid important groundwork, and inspired
foundation and framework for a reliable, continued research in areas related to
efficient, available, robust, extensible, and distributed computing.

www.johronline.com 97 | P a g e
 Garg S. et al., J. Harmoniz. Res. Eng., 2013, 1(2), 95-99

In the mid-1970s, research produced covers the communication pathways among

important advances in distributed computing. nodes. Control manages the operation of the
These breakthroughs provided a solid, stable earlier two considerations.
foundation for efforts that continued through 5.2.1. Organization
the 1990s. A centralized system has one level of
The accelerating proliferation of multi- structure, where all constituent elements
processor and multi-core processor systems directly depend upon a single control element.
research led to a resurgence of the distributed A decentralized system is hierarchical. The
OS concept. bottom level unites subsets of a system’s
5. Distributed computing models:- entities. These entity subsets in turn combine
5.1. The nature of distribution at higher levels, ultimately culminating at a
A distributed operating system’s hardware central master element. A distributed system is
elements spread across multiple locations a collection of autonomous elements with no
within a rack, or around the world. concept of levels.
Distributed configurations allow functions 5.2.2. Connection
to be distributed as well as decentralized. Centralized systems connect constituents
The specific manner of and relative degree directly to a central master entity in a hub and
in linkage between the elements, or nodes spoke fashion. A decentralized system (aka
in the systems differentiates the two. The network system) incorporates direct and
linkages between the two are the lines of indirect paths between constituent elements
communication between the nodes of the and the central entity. Typically this is
system. configured as a hierarchy with only one
shortest path between any two elements.
Finally, the distributed operating system
requires no pattern; direct and indirect
connections are possible between any two
elements. Consider the 1970s phenomena of
“string art” or a spirograph drawing as a fully
connected system, and the spider’s web or the
Interstate Highway System between U.S.
cities as examples of a partially connected
system.
5.2.3. Control
Centralized and decentralized systems have
directed flows of connection to and from the
central entity, while distributed systems
communicate along arbitrary paths. This is the
pivotal notion of the third consideration.
Control involves allocating tasks and data to
system elements balancing efficiency,
responsiveness and complexity.
Centralized and decentralized systems offer
5.2. Three basic distributions more control, potentially easing administration
To better illustrate this point, examine three by limiting options. Distributed systems are
system architectures; centralized, more difficult to explicitly control, but scale
decentralized, and distributed. In this better horizontally and offer fewer points of
examination, consider three structural aspects: system-wide failure. The associations conform
organization, connection, and control. to the needs imposed by its design but not by
Organization describes a system's physical organizational limitations.
arrangement characteristics. Connection

www.johronline.com 98 | P a g e
 Garg S. et al., J. Harmoniz. Res. Eng., 2013, 1(2), 95-99

6. Design considerations:- References:-

• Transparency 1. Nutt, Gary J- Centralized and Distributed
• Inter-process communication Operating Systems.
• Process management 2. Fortier, Paul J. (1986). Design of
• Resource management Distributed Operating Systems: Concepts
• Reliability and Technology. Intertext Publications.
• Availability 3. Chow, Randy; Theodore Johnson (1997).
• Performance Distributed Operating Systems and
• Synchronization Algorithms. Addison Wesley.
• Flexibility 4. Hansen, Per Brinch, ed. (2001). Classic
Operating Systems: From Batch
Processing to Distributed Systems

www.johronline.com 99 | P a g e