[ogsa-wg] Any additions to "example projects" section in OGSA Roadmap?

[Hiro Kishimoto]

Thanks Rajkumar,

I'm grad to hear that GridBus plans to use WSRF. As you already
knows, OGSA-WG defines OGSA WSRF Basic Profile 1.0 in order to
ensure interoperability among multiple grid middlewares.

https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-basic-profile/en/12

Is it possible that future release of GridBus will use the OGSA WSRF
Basic Profile 1.0 as their base (instead of pure WSRF)?

Does your SLA-based allocation use WS-Agreement 1.0?

Thanks,
----
Hiro Kishimoto

Rajkumar Buyya wrote:
> Hi Hiro:
> 
> I have updated writeup and explicitly mentioned about what kind of 
> interfaces we are using and what kind of end-user interfaces we support. 
> How does the updated stuff below sounds?
> ---------------------------------------------------------------------------- 
> 
> The Gridbus Project at the University of Melbourne is one of the major 
> OSS projects focused on the design and development of service-oriented, 
> utility computing grid technologies. The Gridbus project has designed 
> and implemented open source version of Grid Service Broker, Grid 
> Workflow Management system, GridBank (Grid Authorisation, 
> Authentication, and Accounting Services), SLA-based Allocation of Grid 
> Resources, and .NET-based Enterprise Grid manager. All of these 
> technologies support or committed towards providing a standard compliant 
> (both GGF Grid and W3C Web Services standards) interfaces for 
> application developers. Gridbus makes use of WSRF compliant technologies 
> in its development of advanced Grid services. Gridbus contributes to and 
> provides reference implementations of Grid Service Broker (GSB) with 
> interfaces confirming to Job Submission Description Language (JSDL) and 
> Portlets standard, GridBank database confirming to Resource Usage Record 
> (RUR) and access interfaces confirming to WSRF, Workflow management 
> system interface confirming to Web Services Business Process Execution 
> Language (WSBPEL).
> ---------------------------------------------------------------------------- 
> 
> 
> Timeline for release of GGF/W3C/OASIS compilant services/components:
>    - Grid Service Broker - by Aug/Sept 2005.
>    - Grid Bank - by Aug/Sept 2005.
>    - Workflow management system - Oct 2005
>    - WSRF based Access Interface for .NET Enterprise Grid (Alchemi) - 
> Nov 2005
> -------
> If we finish implementation early, we will let you know.
> 
> Cheers
> Raj
> 
> 
> 
> Hiro Kishimoto wrote:
> 
>> Thanks Bajkumar for Gridbus information,
>>
>> We really appreciate your input about your OSS project.
>>
>> However, since this document is "OGSA roadmap document," we need to
>> know
>> - Specify which OGSA specifications or profiles you will use
>> - When you will implement them
>>
>> Since we don't need commitment, please let us know your current plan.
>>
>> Thanks again,
>> ----
>> Hiro Kishimoto
>>
>> Rajkumar Buyya wrote:
>>
>>> Hi Jem:
>>>
>>> Here is a text from our Gridbus Project for inclusion in Roadmap:
>>> ---------------------------------------------------------------------------- 
>>>
>>> The Gridbus Project at the University of Melbourne is one of the 
>>> major OSS projects focused on the design and development of 
>>> service-oriented, utility computing grid technologies. The Gridbus 
>>> project has designed and implemented open source version of Grid 
>>> Service Broker, Grid Workflow Management system, GridBank (Grid 
>>> Authorisation, Authentication, and Accounting Services), SLA-based 
>>> Allocation of Grid Resources, and .NET-based Enterprise Grid manager. 
>>> All of these technologies support or committed towards providing a 
>>> standard compliant (both GGF Grid and W3C Web Services standards) 
>>> interfaces for application developers. We are using and promoting the 
>>> use of standard compliant technologies in the development of various 
>>> e-Science applications in Australia and internationally.
>>> ---------------------------------------------------------------------------- 
>>>
>>>
>>> Thanks
>>> Raj
>>>
>>> Treadwell, Jem wrote:
>>>
>>>> Hi,
>>>>  
>>>> Section 8 of the OGSA Roadmap document describes some open-source 
>>>> projects that are working with OGSA concepts and specifications, and 
>>>> by doing so are contributing to the OGSA effort.  The current text 
>>>> of the section is below.  If anyone would like to add a few lines 
>>>> about any other project, please pass them on to me before the end of 
>>>> this week.  We plan to do final review of the document on Monday 
>>>> next week, so please don't delay if you want to get something to 
>>>> me.  Please keep your submission fairly short and in line with the 
>>>> style of what you see below, and be specific about what is being 
>>>> implemented.
>>>>  
>>>> Also note that although the section is currently entitled 
>>>> "Open-Source Software Projects" commercial projects or other 
>>>> non-open-source projects can be included, provided they fit the 
>>>> criteria of contributing to the development of OGSA.  We'll change 
>>>> the section heading if appropriate.
>>>>
>>>> Thanks!
>>>> - Jem
>>>>  
>>>>  
>>>>
>>>> *Open-Source Software Projects*
>>>>
>>>> OGSA is expected to be implemented by multiple open-source software 
>>>> (OSS) projects and commercial software vendors. OSS projects such as 
>>>> Globus, the Business Grid Computing Project, the NextGrid Project, 
>>>> the NAREGI Project, University of Virginia Global Bio Grid, UK 
>>>> e-Science, and others will contribute.
>>>>
>>>> The *Globus Toolkit* (Globus) is one example of a major OSS grid 
>>>> project. The Globus Alliance is contributing to the development of 
>>>> OGSA by supporting the design and implementation of open-source 
>>>> software that implements specifications detailed in OGSA Profiles, 
>>>> and the participation of the implementers of that software in 
>>>> relevant standards processes.  With its current version, GT4, based 
>>>> on early implementations of WSRF and WS-Notification and including 
>>>> implementations of all relevant security standards, Globus provides 
>>>> a comprehensive software infrastructure that allows developers and 
>>>> users to work with OGSA concepts now.  Additional standards will be 
>>>> incorporated into future versions of the toolkit as they evolve.
>>>>
>>>> The Globus Consortium is a group of companies with a common interest 
>>>> in promoting the development and adoption of the Globus Toolkit for 
>>>> commercial use. Consortium participants also have a strong interest 
>>>> in standards in general, and in OGSA in particular.
>>>>
>>>> The team at the *University** of Virginia* (UVA) is committed to 
>>>> implementing several pieces of the OGSA Roadmap described here. 
>>>> Specifically, UVA will implement open versions of ByteIO, BES, RNS, 
>>>> and the WS-Naming specifications.
>>>>
>>>> The *Business Grid Computing Project* (BG) is based on the OGSA 
>>>> Architecture specification. It is developing several services using 
>>>> specifications described in this Roadmap. In particular, BG will 
>>>> make available as open source software implementations of the 
>>>> Application Contents Service, JSDL, and WS-Agreement. BG intends to 
>>>> use the OGSA WSRF Basic Profile 1.0.
>>>>
>>>> The *National Research Grid Initiative* (*NAREGI*) is a Japanese 
>>>> national e-science grid project aiming at developing a computational 
>>>> infrastructure for supporting scientific and engineering research. 
>>>> One of the primary goals of the NAREGI Project is to contribute to 
>>>> the GGF standardization activities. NAREGI has been interested in, 
>>>> participated in, and, where possible, given feedback to numerous GGF 
>>>> working groups and research groups. Amongst the various groups, 
>>>> NAREGI has recently placed high emphasis on the OGSA-WG activities, 
>>>> being the first project or group to implement the EMS architecture 
>>>> described in the OGSA Architecture v1.0 specification, in its alpha 
>>>> incarnation of the software stack that was released in 1Q 2005. 
>>>> Future plans will have NAREGI contribute to and provide reference 
>>>> implementations for Basic Execution Services (BES), Resource 
>>>> Selection Services (RSS), and Application Contents Service (ACS).
>>>>
>>>>  
>>>> ------------------------------------------------------------------------ 
>>>>
>>>> Jem Treadwell
>>>> Hewlett-Packard Company
>>>> 6000 Irwin Road
>>>> Mount Laurel, NJ 08054           Phone:     856-638-6021
>>>> Fax:     856-638-6190
>>>> E-mail:     Jem.Treadwell at hp.com <mailto:Jem.Treadwell at hp.com>
>>>>
>>>>  
>>>
>>>
>>>
>>>
>>
>