Open Grid Forum

View
 Active Groups
 Completed Groups
 Hibernating Groups

 ABOUT OGF  RESOURCE CENTER  OGF EVENTS  DOCUMENTS  AREAS/GROUPS 
 MEMBERS  NEWS  STANDARDS  CONTACT US  SITE MAP  REDMINE 
OGF Active Groups

Architecture


Area Director: Andrew Grimshaw

The Architecture Area hosts working and research groups that aim to define architectures for Grid computing. Architectures form the frameworks and design patterns for grids.
 
 
OGSA Naming Working Group (OGSA-NAMING-WG)
Group Information
Group Type: Working Group
Group Chair(s): Andrew Grimshaw
 
Group Description
The objective of this working group is to work on two specifications (RNS and WSNR) to realize a three level name space for OGSA and to produce WS-Naming naming specification based on WS-Addressing. Thus, both RNS and WS-Naming must be combinable with OGSA Basic Profile.
 
Group Links
 
 
Open Grid Services Architecture WG (OGSA-WG)
Group Information
Group Type: Working Group
Group Secretary(s): Andreas Savva
 
Group Description
The Open Grid Forum (OGF) has embraced the Open Grid Services Architecture as the blueprint for standards-based grid computing. 'Open' refers to the process used to develop standards that achieve interoperability. 'Grid' is concerned with the integration, virtualization, and management of services and resources in a distributed, heterogeneous environment. It is 'service-oriented' because it delivers functionality as loosely coupled, interacting services aligned with industry-accepted Web service standards. The 'architecture' defines the components, their organizations and interactions, and the design philosophy used. OGSA-WG is developing the architecture and its constituent specifications and profiles in collaboration with a number of fellow working groups.
 
Group Focus and Scope
OGSA-WG manages an architectural process of OGSA standards by working to collect requirements, evaluate the maturity of specifications, and produce periodic updates to OGSA informational documents and OGSA recommendation profiles.

The scope of the proposed working group is to produce the following documents. All documents are Informational except for OGSA Profiles, which are Recommendations.

* Architecture document and Glossary: The Architecture document identifies the framework, taxonomy, and functionality that should be provided to address use case requirements. The Glossary provides an unambiguous definition of terms used in the Architecture document.

* Service Description documents and Scenario documents: Service Description documents describe each OGSA service in natural language, listing the interfaces and operations defined by each service. Scenario documents demonstrate how these services can implement the use cases, using a combination of natural language and UML. Fellow-WGs may also develop such documents.

* OGSA Roadmap document: The Roadmap document expresses OGSA-WG views on the likely future evolution of OGSA to address unmet requirements and/or respond to technology evolution.

* Guideline documents: Guideline documents outline how to write specific OGSA normative documents. Examples of guideline documents include the OGSA Profile Definition document and the Grid Information/Data Model Guidelines document.

* OGSA Profiles: An OGSA Profile specifies requirements on referenced specifications and other profiles to improve interoperability. A Profile has 'conformance statements' and 'extension points' as specified in the OGSA Profile Definition document.

The OGSA-WG will ensure consistency among OGSA informational documents, OGSA Profiles, and related specifications which are produced by fellow-WGs.
 
Group Links
 
 
Production Grid Infrastructure WG (PGI-WG)
Group Information
Group Type: Working Group
Group Chair(s): Johannes Watzl, Morris Riedel
 
Group Description
The objective of this working group is to formulate a well-defined set of profiles, and additional specifications if needed, for job and data management that are aligned with a Grid security and information model that addresses the needs of production grid infrastructures.
 
Group Focus and Scope
The origin of this working group is from the Grid Interoperation Now (GIN) community group. The GIN-CG has representatives from production grid infrastructures (such as EGEE, OSG, NAREGI, NorduGrid, TeraGrid, NGS, etc) and supporting organizations (such as OGF-Europe, OMII-Europe, OMII-UK, etc.). Over the last two years the members of GIN that are working daily in world-wide production grids have been working within the OGF to explore the interoperability issues in:
• jobs submission and job monitoring
• data access and movement
• authentication and authorization
• information representation and discovery
As a result of this collaborative activity the GIN-CG now feels there is sufficient understanding and motivation within the group to define a set of profiles around a well-defined use case. This use case should use open standards from different areas of OGF to facilitate interoperability among production Grid infrastructures. This is the focus of this working group.


This basic use case identified in production Grids is as follows: on behalf of an authorized user, a tool interrogates the information system (representing a grid or a single resource), locates an optimal execution resource, submits the job to the execution resource, which in turn interprets the submitted job description and locates and fetches the necessary input data from a remote storage - also on behalf of the user. Upon the completion, the newly created data is uploaded to a storage resource where this user is authorized (as a member of a Virtual Organization), registered in the necessary data indexing catalogs, and the job record is updated in the accounting and monitoring system.

Thus the milestones this working group must meet are particularly ambitious due to the needs of the production Grid infrastructures. There is a need to come to a common proven end-to-end interoperable definition of the services and their interactions within the next 18 months for the European middleware developers. This development work will take place within this time period – we feel it is imperative to attempt to do this work within OGF.

Scope
The scope of this working group is restricted to dealing with job and data management issues found in production grid infrastructures that together use a limited number of security specifications and information models. The resulting Web service interfaces and schemas defined by this working group will be a set of profiles of open standards and specifications such as OGSA-Basic Execution Services (GFD.108), Job Submission Description Language (GFD.136), GridFTP (GFD.20), Storage Resource Manager (GFD.129), and efforts of the GLUE2 (GFD tbc) working group. The additional work bv this group will go beyond the current specifications and extensions to include an authentication and authorization model, an extended state model, an integrated resource and informational model, and a data transfer and storage model – all tuned to the use cases found in production grid infrastructures.

Goals
This group will deliver the following document:

* Production Grid Infrastructure Roadmap Document (GFD-I)
* Provides an overview of missing links between open standards and the fundamental motivation for standardization of the production grid infrastructure profiles
* Secure Job and Data Management Profile in Production Grids (GFD-R.P)
* Develop a job/data/security profile assuming an deployed computing endpoint is already known by an end-user
* Secure Information Profile in Production Grids (GFD-R-P)
* Allows a user to discover resources that are appropriate for their request and that they are authorized to access
* Secure Accounting Profile in Production Grids (GFD-R-P)
* Develop an accounting profile that allows services to securely update a service within information about the resources they have used on behalf of a user.
* Secure Monitoring Profile in Production Grids (GFD-R-P)
* Develop a profile that allows services to securely record in a service the progress of an activity.

 
Group Links
 
 
Reference Model Working Group (RM-WG)
Group Information
Group Type: Working Group
Group Chair(s): David Snelling, Paul Strong
 
Group Description
In order to ensure that we share a common language when describing grids, what they are comprised of, how those entities interact and so forth, we need an agreed upon glossary and set of terms. When defining standards, protocols and interfaces for grid computing, the sets of components (both services and resources) that comprise a grid, their relationships and their life-cycles need to be more formally described.

Providing this formal description and associated terminology is the goal of the Reference Model working group. Whilst extant standards capture aspects of what is required, they are either incomplete or lack a Grid context and so need to be pulled together into a coherent whole. It is not the purpose of this group to replicate the work of established standards that in general meet our needs. Rather the work of this group will be to pragmatically develop the broader model that brings together, references and extends where appropriate.
 
Group Focus and Scope
This group will use the EGA Reference Model and the OGSA Glossary as its starting points.

The overall context for this work will be that of grids in the data center, although the output should be more or less applicable to all types of Grids. Nonetheless the use cases used to drive and validate the work will be data center centric, focused on the configuration management, provisioning (both transactional and batch), service level management, dynamic resource control and so forth.

The group's deliverables will seek to:
o Capture all of the common and abstract components (services and resources) that comprise a Grid.
o Describe, both formally and informally, these components, together with their life-cycles and their relationships with one another.
o Pragmatically reconcile these with other extant standards, including but not necessarily limited to the other OGF standards (planned for Reference Model v2.1), the DMTF's CIM (Common Information Model), the SNIA's SMI-S etc., ITIL, DCML and so forth (planned for Reference Model v2.2).
o Define ways of representing and serializing the model, including, but not necessarily limited to RDF/RDFS/OWL Vocabulary, SML, XML Schemas, Java etc (planned for Reference Model v3.0).
 
Group Links

> login   RSS RSS Contact Webmaster

OGFSM, Open Grid ForumSM, Grid ForumSM, and the OGF Logo are trademarks of OGF