BANNARI AMMAN INSTITUTE OF TECHNOLOGY

SATHYAMANGALAM
Department of Information Technology

Class IV IT A&B
Subject Code
11I010
Subject GRID COMPUTING
Prepared By Arun Shalin L.V & Aiswarya Devi VJ
Time: 75 mins
Unit No. &
Lesson. No
(3/4)

1.

Content List: Open Grid Services Infrastructure

2.

Skills Addressed:
Reading, Questioning, Drawing mind map, Summarizing, Discussion, Drawing Diagrams,
Expressing orally and in writing.
3. Objectives:
1. To gain basic knowledge of Open Grid Service Infrastructure
2. To gain the knowledge about Service Implementation and port types

4. Lesson Links:
Concepts/ ideas/ formulae /definition/laws etc

5. Alpha Breathing : (1 Min)
The three steps for alpha breathing are
Breathe in
Breathe out
Hold
(Repeat the three steps for 8 times)
6. Evocation and In-depth teaching:( 35-40 mins)
Grid Computing has attracted global technical communities with the evolution of Business
on Demand computing and Autonomic Computing. Grid Computing is a process of
coordinated resource sharing and problem solving in dynamic, multi-institutional virtual
organizations. It is a technical challenge to achieve a highly ambitious interaction among
resources being shared across virtual organizations with less centralized control, while at
the same time ensuring the highest quality of service. The GGF started a number of
architecture standardization efforts in order to provide better software interoperability,
higher levels of security, more encompassing resource definitions, discovery capabilities,
policy management, and overall environmental manageability aspects.
Grid Services
A grid service provides the controlled management of the distributed and often long-lived
state that is commonly required in sophisticated distributed applications. According to the
definition of OGSI, every grid service is a Web service; however, the converse need not be
true
.
The OGSI specification defines the following:
How grid service instances are named and referenced
How the interfaces and behaviors are common to all GRID services
How to specify additional interfaces, behaviors, and their extensions
We will be focusing on the OGSI concepts used by this sample service implementation,
and not on the manageability features. Since OGSI is layered on top of the Web service
standard, familiarity with the core Web service concepts, including XML, XML schema,
WSDL, SOAP, and the Web services programming model, (i.e., client and server side) will
help us to better understand the OGSI in greater depth. We can find greater details on these
technologies in the previous discussion and by visiting their Web sites. The interface
inheritance diagram, as shown in Figure 9.1,introduces the following concepts of a grid
service, enabled by:
Providing a stateful
Web service implementation of the operating system service withpublic interface
(Operating System port Type) to access the service and its state.

Supporting interface inheritance.
The operating system service implements Operating System port Type, which is derived
from the Base Manageable Resource interface, which in turn extends the Grid Service
interface.
Specifying the common grid service behaviors (public "state data" and "operations") using
Grid Service port Type as defined by the OGSI.
Allowing the operating system services to inherit the public state data and operations from
its parent port types.
Manipulating the state of a service through the Grid Service operations such
as"findServiceData" and "setServiceData."

Enabling the client so that it can discover the state and meta-data of the service through
"findServiceData" of the Grid Service interface. We will see the common OGSI-
definedservice meta-data later in this chapter.
Establishing a pattern implementation for the operating system service, whereby thefactory
service inherits from the OGSI factory interface. This is an optional feature andhence may
not present itself in the real grid service implementation environments.

The OGSI Port Type Inheritance model for operating system service and the operating
system factory service sample (the solid arrow indicates the inheritance).
One of the requirements of services defined by the OGSI is the ability to describe the
precedingconcepts using an OGSI description model, which is a combination of Web
service WSDL andOGSI GWSDL. We will see the details in later sections


A High-Level Introduction to OGSI
This high-level introduction will set the stage for the detailed technical discussion on
OGSI. TheOGSI specification defines a component model using a Web service as its core
base technology,with WSDL as the service description mechanism and XML as the
message format:1.

A service is maintaining its state information. These are normally classified asapplication
state and in the case of grid service it directly maps to the state of theresource.2.

The interaction pattern between the client and service can be stateful. There are numerous
architecture styles and programming models for defining these stateful interactions
including BPEL4WS

and REST (Fielding).As of now, the OGSI is attempting to answer the first dimension of
the state problem by creating a programming model for how and where an
application/service resource state The following list describes points of interest related to
this model.

Grid services are layered on top of Web services.

Grid services contain application state factors, and provide concepts for exposing thestate,
which is referred to as the service data element.

Both grid services and Web services communicate with its client by exchanging XML
messages.
Grid services are described using GWSDL, which is an extension of WSDL. GWSDL
provides interface inheritance and open port type for exposing the service state information

referred to as service data. This is similar to interface properties or attributes commonly
found in other distributed description languages.

The client programming model is the same for both grid service and Web service. But grid
services provide additional message exchange patterns such as the handle resolution
through OGSI port types.


The transport bindings are selected by the runtime. Message encoding and decoding is done
for the specific binding and high-level transport protocol (SOAP/HTTP).


Web service
: A software component identified using a URI, whose public interfaces and binding are
described using XML. These services interact with its clients using XML message
exchanges.
Grid service
: This is a stateful Web service with a common set of public operations and state behaviors
exposed by the service. These services are created using the OGSI-defined specification.
Grid service instance: An instance of a grid service created by the hosting container and
identified by a unique URI called grid service handle (GSH).
OGSI and Its Use of WSDL
OGSI is based on Web services and it uses WSDL as a mechanism to describe the
publicinterfaces of the grid service. There are two core requirements for describing Web
services basedon the OGSI:


The ability to describe interface inheritance


The ability to describe additional information elements (state data/attributes/properties)with
the interface definitions The WSDL 1.2

working group has agreed to support these features through portType (nowcalled
"interface" in WSDL 1.2) inheritance and an open content model for portTypes. This being
one of the most important and challenging parts of the OGSI specification, we need to
spend some time analyzing the GWSDL schema and its relation to WSDL.


7. Brain Activation: (2 mins)
Any one of the following activities like
Right brain activities
Solving puzzles
Brain GYM
Optical Illusions
Perpetual calendar recalling

Survey and Reading by students (18 mins.)

Textbook
Joshy Joseph and Craig Fallenstein, Grid Computing, Pearson Education, New Delhi, 2004

The OGSA Platform Component 129
Native Platform Services and Transport Mechanism 130
Core Networking Services Transport and Security 135

8.






Discussion: ( 9 mins)
The students will be asked to discuss the relevant topic among their team/other
team/Faculty. The students those who have not taken part will be noted and kindle them to
do.
9. Mind Map: (8 mins)



10. Gazing/Rote memory: (1 mins)
A long and fixed look at the Mind map by the students before doing the presentation.

11. Summary: (9 mins)
We understand the roles of grid computing and Organizations developing Grid
standards and the Global Grid Forum in this chapter

The OGSA Platform Component
Native Platform Services and Transport Mechanism
Core Networking Services Transport and Security

12. Assessment: (5-10 mins)

1. Technical challenge to achieve a highly ambitious interaction among ___.
a) business b) applications c) system d) resources
2. The GGF started a number of architecture standardization efforts in order to
provide better _________________
a) infrastructures b) intra structure c) software interoperability d) none
3. _________instances are named and referenced
a) Rescheduling b) infrastructure c) structure d) grid service
4. The interaction pattern between the client and service can be _________
a) stateful b) stateless
c) Stallone d) all the above
5. Inheritance and an open content model for _____
a) flexibility b) expand c) fixed d) portTypes

Two Marks:
1. Who are the actors in NFC?
2. Mention the scenarios NFC.
3. What are the functional requirements of NFC on CGSA?
4. Who are the actors in NFC?
5. Mention the scenarios NFC.
13. Learning outcomes:
The Students can gain knowledge about the OGS Infrastructure and its methodologies
and services.