Hi all,
At the first OGSA-WG session, we select Old Sam's Chophouse
for group dinner place.
Old Sam's Chophouse (Traditional British)
Back Pool Fold, Chapel Walks, off Cross Street, Manchester M2 1HN
Tel: 0161 834 3210
www.samschophouse.co.uk
We will meet at the entrance of the MCC at 7pm # and
take < 10 minutes walk to the restaurant.
I have booked table for group of 10 people. If you plan to come but
have not raised your hand at the 1dt OGSA-WG session, please let me
know ASAP.
Thanks,
--
Hiro Kishimoto
Andrew and Duane -
Of interest for the Express Profile work?
Alan
Begin forwarded message:
> From: "Ratering, Ralf" <ralf.ratering(a)intel.com>
> Date: May 4, 2007 2:52:29 AM CDT
> To: "Dan Fraser" <fraser(a)mcs.anl.gov>, <gt-user(a)globus.org>
> Subject: RE: [gt-user] Fw: Core options writeup
>
> Hi Dan,
>
> we are developing the Grid Programming Environment (GPE) as an Open
> Source project (http://gpe4gtk.sourceforge.net)
> Our goal is to provide graphical user interfaces and programming
> tools for Grid end users and developers, independent of the
> underlying Grid Middleware. Therefore we have defined a programming
> API and a set of so-called "atomic services" that manage jobs,
> files and (virtual) machines on a Grid system.
> Currently we have implementations of the atomic services for GT4
> and for UNICORE6.
>
> A major problem that we have to struggle with is the difference in
> the WSRF/WSN specification versions since UNICORE is using the
> final versions. So right now we have to provide two different API
> implementations and client distributions. Synchronizing the WSRF/
> WSN specs between GT4 and UNICORE would allow us to use the same
> clients for both server-side implementations, which is actually
> what we assumed would happen some day.
>
> The second issue is, that we would like to switch to a modern SOAP
> framework, like Axis2, XFire or Jax-WS. Last time I looked at the
> Axis2-based Muse, the implementation looked quite similar to GT4,
> although security is missing of course. So migrating from GT4-core
> to Muse seems to require the least modifications, but I may be
> wrong there....
>
> And finally there's the WS-RT family of management standards coming
> up, that let's people assume the implementation will change again
> some day.
>
> As a summary, we'd be happy if GT4 only upgrades the WSRF/WSN specs
> for now. But we need a concrete roadmap that allows us to plan our
> GPE development for GT. One option could be to implement GT5 on top
> of Muse and then in the long term move towards WS-RT together with
> the Muse project, or?
>
> Regards,
> Ralf
> --
> Best Regards
>
> Ralf Ratering
> Intel
> Software & Solutions Group
> Hermuelheimer Strasse 8a, 50321 Bruehl, Germany
> Tel: +49 2232 209049, Fax: +49 2232 209029
> ----
> Intel GmbH, Dornacher Strasse 1, 85622 Feldkirchen/Muenchen Germany
> Sitz der Gesellschaft: Feldkirchen bei Muenchen
> Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
> Registergericht: Muenchen HRB 47456
> Ust.-IdNr./VAT Registration No.: DE129385895
> Citibank Frankfurt (BLZ 502 109 00) 600119052
>
>
> From: owner-gt-user(a)globus.org [mailto:owner-gt-user@globus.org] On
> Behalf Of Dan Fraser
> Sent: Dienstag, 1. Mai 2007 22:27
> To: gt-user(a)globus.org
> Subject: [gt-user] Fw: Core options writeup
>
> Hi Committers,
>
> The CDIGS team is currently evaluating whether we need to update
> the Java WS Core and C WS Core at this time to conform to the final
> version of the WSRF specifications. Depending on the implementation
> model, this could increase both the support and implementation
> complexity of the toolkit. We would like to have some email
> discussion on this topic to understand what your requirements are
> and determine the best course to pursue.
>
> Joe, Rachana, Charles, and Ravi have been diligently working to put
> together the attached document. Please help us understand if the
> benefits of upgrading are worth the increased support/
> implementation complexity and lack of backward compatability for
> our user community.
>
> I would also like to propose a concall meeting on Monday May 14 at
> 11:00am CT to discuss this further.
>
> Thank you,
>
> Dan
>
Alan Sill, Ph.D
TIGRE Senior Scientist, High Performance Computing Center
Adjunct Professor of Physics
TTU
====================================================================
: Alan Sill, Texas Tech University Office: Admin 233, MS 4-1167 :
: e-mail: Alan.Sill(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 :
====================================================================
HI,
I've uploaded version 4 of the glossary - this version includes the
changes for deployment and provisioning, as agreed at the last
discussion. You'll find it at http://tinyurl.com/2mo6r3.
For Thursday's call I propose to discuss the following terms, as time
permits
o State. We had discussed this, and Jay has an action to improve
the current proposal. So far I haven't had a proposal from Jay, but we
need to put this one to bed, so we'll have a brief discussion and if we
don't have a better proposal at the meeting I'll go with what we have.
There will be an opportunity to improve this or any term in the final
review.
o Resource, Grid component, and Service. We had definitions for
Resource and Service in both the OGSA and the EGA glossaries, so we need
to produce a consolidated definition. Grid component comes from the EGA
glossary. I've condensed it from the original, but (hopefully) haven't
changed its meaning.
Rather than reproduce these terms here please take a look at the
working/discussion document, which you'll find at
http://tinyurl.com/23a6zd. These are the first four terms listed, and
the text you'll find is a starting point for discussion. If you have
comments and you're not going to make tomorrow's meeting, please pass
them on to me; otherwise I'll follow up after the meeting with revised
text for review.
Thanks!
- Jem
Jem Treadwell
Software Engineer
HP Software
856.638.6021 office | 856.638.6190 fax | jem.treadwell(a)hp.com
6000 Irwin Road | Mount Laurel | NJ 08054
www.hp.com/go/software
<http://www.hp.com/go/software>
