animesh sinha

garuda indian grid project

2008-09-03T03:53:00.000+05:30

GARUDA is a collaboration of science researchers and experimenters on a nation wide grid of computational nodes, mass storage and scientific instruments that aims to provide the technological advances required to enable data and compute intensive science for the 21st century. One of GARUDA’s most important challenges is to strike the right balance between research and the daunting task of deploying that innovation into some of the most complex scientific and engineering endeavors being undertaken today.

The Department of Information Technology (DIT), Government of India has funded the Centre for Development of Advanced Computing (C-DAC) to deploy the nation-wide computational grid ‘GARUDA’ which will connect 17 cities across the country in its Proof of Concept (PoC) phase with an aim to bring “Grid” networked computing to research labs and industry. GARUDA will accelerate India’s drive to turn its substantial research investment into tangible economic benefits.

GARUDA aims at strengthening and advancing scientific and technological excellence in the area of Grid and Peer-to-Peer technologies. The strategic objectives of GARUDA are to:

Create a test bed for the research & engineering of technologies, architectures, standards and applications in Grid Computing

Bring together all potential research, development and user groups to develop a national initiative on Grid computing

Create the foundation for the next generation grids by addressing long term research issues in grid computing

http://www.garudaindia.in/images/Grid_Garuda_India-Map_01.gif

Grid Computing

2008-09-03T03:26:00.000+05:30

Grids versus conventional supercomputers

"Distributed" or "grid" computing in general is a special type of parallel computing which relies on complete computers (with onboard CPU, storage, power supply, network interface, etc.) connected to a network (private, public or the Internet) by a conventional network interface, such as Ethernet. This is in contrast to the traditional notion of a supercomputer, which has many processors connected by a local high-speed computer bus.
The primary advantage of distributed computing is that each node can be purchased as commodity hardware, which when combined can produce similar computing resources to a multiprocessor supercomputer, but at lower cost. This is due to the economies of scale of producing commodity hardware, compared to the lower efficiency of designing and constructing a small number of custom supercomputers. The primary performance disadvantage is that the various processors and local storage areas do not have high-speed connections. This arrangement is thus well-suited to applications in which multiple parallel computations can take place independently, without the need to communicate intermediate results between processors.
The high-end scalability of geographically dispersed grids is generally favorable, due to the low need for connectivity between nodes relative to the capacity of the public Internet.
There are also some differences in programming and deployment. It can be costly and difficult to write programs so that they can be run in the environment of a supercomputer, which may have a custom operating system, or require the program to address concurrency issues. If a problem can be adequately parallelized, a "thin" layer of "grid" infrastructure can allow conventional, standalone programs to run on multiple machines (but each given a different part of the same problem). This makes it possible to write and debug on a single conventional machine, and eliminates complications due to multiple instances of the same program running in the same shared memory and storage space at the same time.
Design considerations and variations

One feature of distributed grids is that they can be formed from computing resources belonging to multiple individuals or organizations (known as multiple administrative domains). This can facilitate commercial transactions, as in utility computing, or make it easier to assemble volunteer computing networks.
One disadvantage of this feature is that the computers which are actually performing the calculations might not be entirely trustworthy. The designers of the system must thus introduce measures to prevent malfunctions or malicious participants from producing false, misleading, or erroneous results, and from using the system as an attack vector. This often involves assigning work randomly to different nodes (presumably with different owners) and checking that at least two different nodes report the same answer for a given work unit. Discrepancies would identify malfunctioning and malicious nodes.
Due to the lack of central control over the hardware, there is no way to guarantee that nodes will not drop out of the network at random times. Some nodes (like laptops or dialup Internet customers) may also be available for computation but not network communications for unpredictable periods. These variations can be accommodated by assigning large work units (thus reducing the need for continuous network connectivity) and reassigning work units when a given node fails to report its results as expected.
The impacts of trust and availability on performance and development difficulty can influence the choice of whether to deploy onto a dedicated computer cluster, to idle machines internal to the developing organization, or to an open external network of volunteers or contractors.
In many cases, the participating nodes must trust the central system not to abuse the access that is being granted, by interfering with the operation of other programs, mangling stored information, transmitting private data, or creating new security holes. Other systems employ measures to reduce the amount of trust "client" nodes must place in the central system such as placing applications in virtual machines.
Public systems or those crossing administrative domains (including different departments in the same organization) often result in the need to run on heterogeneous systems, using different operating systems and hardware architectures. With many languages, there is a tradeoff between investment in software development and the number of platforms that can be supported (and thus the size of the resulting network). Cross-platform languages can reduce the need to make this tradeoff, though potentially at the expense of high performance on any given node (due to run-time interpretation or lack of optimization for the particular platform).
Various middleware projects have created generic infrastructure, to allow diverse scientific and commercial projects to harness a particular associated grid, or for the purpose of setting up new grids. BOINC is a common one for academic projects seeking public volunteers; more are listed at the end of the article.
In fact, the middleware can be seen as a layer between the hardware and the software. On top of the middleware, a number of technical areas have to be considered, and these may or may not be middleware independent. Example areas include SLA management, Trust and Security, VO management, License Management, Portals and Data Management. These technical areas may be taken care of in a commercial solution, though the cutting edge of each area is often found within specific research projects examining the field.
CPU scavenging

CPU-scavenging, cycle-scavenging, cycle stealing, or shared computing creates a "grid" from the unused resources in a network of participants (whether worldwide or internal to an organization). Typically this technique uses desktop computer instruction cycles that would otherwise be wasted at night, during lunch, or even in the scattered seconds throughout the day when the computer is waiting for user input or slow devices.
Volunteer computing projects use the CPU scavenging model almost exclusively.
In practice, participating computers also donate some supporting amount of disk storage space, RAM, and network bandwidth, in addition to raw CPU power. Since nodes are apt to go "offline" from time to time, as their owners use their resources for their primary purpose, this model must be designed to handle such contingencies.
History

The term Grid computing originated in the early 1990s as a metaphor for making computer power as easy to access as an electric power grid in Ian Foster and Carl Kesselmans seminal work, "The Grid: Blueprint for a new computing infrastructure".
CPU scavenging and volunteer computing were popularized beginning in 1997 by distributed.net and later in 1999 by SETI@home to harness the power of networked PCs worldwide, in order to solve CPU-intensive research problems.
The ideas of the grid (including those from distributed computing, object oriented programming, web services and others) were brought together by Ian Foster, Carl Kesselman and Steve Tuecke, widely regarded as the "fathers of the grid[1]." They led the effort to create the Globus Toolkit incorporating not just computation management but also storage management, security provisioning, data movement, monitoring and a toolkit for developing additional services based on the same infrastructure including agreement negotiation, notification mechanisms, trigger services and information aggregation. While the Globus Toolkit remains the defacto standard for building grid solutions, a number of other tools have been built that answer some subset of services needed to create an enterprise or global grid.

During 2007 the term cloud computing came into popularity, which is conceptually similar to the canonical Foster definition of grid computing (in terms of computing resources being consumed as electricity is from the power grid). Indeed grid computing is often (but not always) associated with the delivery of cloud computing systems.

2007-09-19T13:55:00.000+05:30

Windmills that would float hundreds of miles out at sea could one day help satisfy our energy needs without being eyesores from land, scientists said today.
Offshore wind turbines are not new, but they typically stand on towers that have to be driven deep into the ocean floor. This arrangement only works in water depths of about 50 feet or less—close enough to shore that they are still visible.
Researchers at the Massachusetts Institute of Technology and the National Renewable Energy Laboratory (NREL) have designed a wind turbine that can be attached to a floating platform. Long steel cables would tether the corners of the floating platform to a concrete-block or other mooring system on the ocean floor, like a high-tech ship anchor. The setup is called a "tension leg platform," or TLP, and would be cheaper than fixed towers.
"You don't pay anything to be buoyant," said Paul Sclavounos, an MIT professor of mechanical engineering and naval architecture who was involved in the design.
The floating platforms to sway side to side but not bob up and down. Computer simulations suggest that even during hurricanes, the platforms would shift by only about three to six feet and that the bottom of the turbine blades would revolve well above the peak of even the highest wave. Dampers similar to those used to steady skyscrapers during high winds and earthquakes could be used to further reduce sideways motion, the researchers say.
Like the offshore windmills currently in use, the TLP's would use undersea cables to shuttle the electricity to land.
The researchers estimate their floater-mounted turbines could work in water depths ranging from about 100 to 650 feet. This means that in the northeastern United States, they could be placed about 30 to 100 miles out at sea. Because winds are stronger farther offshore, the floating windmills could also generate more energy—5.0 megawatts (MW), compared to 1.5 MW for onshore units and 3.5 MW for conventional offshore setups.
To save money, assembly of the TLP's could be done onshore—probably at a shipyard—and towed out to sea by a tugboat, the researchers say.
Sclavounos estimates that building and installing the TLP's should cost a third of what it costs to install current offshore tower windmills. Another advantage of using floating platforms is that the windmills could be moved around. If a company with 400 wind turbines in Boston needs more power in New York City, it can unhook some of their windmills and tow them south.
The researchers plan to install a half-scale prototype of their invention south of Cape Cod.
"We'd have a little unit sitting out there to show that this thing can float and behave the way we're saying it will," Sclavounos said.

2007-09-17T16:11:00.000+05:30

“Aluna is a unique proposal for the world’s first tidal powered Moon Clock। It will change the way we consider time and understand our planet। Larger than Stonehenge, Aluna’s forty metre wide, five storey high structure is made up of three concentric translucent glass rings। By looking at how each ring is illuminated, you can follow the Moon’s movements, its current phase and the ebb and flow of the tides। This animation of light is called Alunatime। Using the latest design and technologies, Alunatime will be powered directly by the tides using turbines। A waterside landmark and a public sculpture, Aluna unites art, science and spirituality and is an ever-changing reminder of the natural cycles that have shaped our past and will determine our future”।