June 2008 - ogsa-wg - lists.ogf.org

Two security profiles are published as GFD
by Hiro Kishimoto 15 Jun '08

15 Jun '08

Hi Duane and OGSA-WG, Two security profiles are published as GFD. GFD.132: Secure Communication Profile 1.0 GFD.131: Secure Addressing Profile 1.0 http://www.ogf.org/gf/docs/?final Thank you very much for your excellent work. -- Hiro Kishimoto

1 0

Re: [ogsa-wg] [DRMAA-WG] Grid Command Line interfaces
by Daniel Templeton 04 Jun '08

04 Jun '08

DRMAA is narrowly focused on offering an API, but as was already pointed out, as soon as you have a Perl binding (which we do), the API itself also becomes a set of commands. Daniel Andre Merzky wrote: > Well, DRMAA is an API specification as well, so does not > really define command line tools in the spec. There are a > number of tools available, but I am not qualified to say if > the DRMAA group intended to have a complete API mapping, or > plan to standardize these tools, etc. > > Cc to the DRMAA group, maybe they have input on the topic... > > Quoting [Omer F. Rana] (Jun 04 2008): > >> Date: Wed, 04 Jun 2008 16:35:13 +0100 >> From: "Omer F. Rana" <o.f.rana(a)cs.cardiff.ac.uk> >> To: Andre Merzky <andre(a)merzky.net> >> Subject: Re: [ogsa-wg] Grid Command Line interfaces >> >> Hi Andre, >> >> Thanks. It might be useful to understand the relationship between these >> and commands provided >> in DRMAA perhaps? Just a thought. >> >> best wishes >> Omer >> >> Andre Merzky wrote: >> >>> Hi Omer >>> >>> Quoting [Omer F. Rana] (Jun 04 2008): >>> >>> >>>> Hi, >>>> >>>> Doesn't DRMAA already do this? >>>> >>>> Andre: I thought the aim of SAGA was to provide a programmatic >>>> API rather than a command line tools interface? >>>> >>>> >>> Of course, you are perfectly right. However, several people >>> (including our won group) use SAGA for the purpose to write >>> such command line tools (which are then middleware >>> independent), and thus we considered mappings from the SAGA >>> API to command line tools since quite a while... >>> >>> Best, Andre. >>> >>> >>> >>>> regards >>>> Omer >>>> >>>> Steven Newhouse wrote: >>>> >>>> >>>>> It may make sense to define common tools for job: >>>>> >>>>> Submit >>>>> Status >>>>> Terminate >>>>> >>>>> I'm not sure what broader interest we would have to do generic SAGA >>>>> commands. >>>>> >>>>> Steven >>>>> >>>>> >>>>> >>>>> >>>>>> -----Original Message----- >>>>>> From: Andre Merzky [mailto:andre@merzky.net] >>>>>> Sent: Wednesday, June 04, 2008 2:48 PM >>>>>> To: Steven Newhouse >>>>>> Cc: Andre Merzky; ogsa-wg(a)ogf.org; ogsa-hpcp-wg(a)ogf.org >>>>>> Subject: Re: [ogsa-wg] Grid Command Line interfaces >>>>>> >>>>>> Quoting [Steven Newhouse] (Jun 04 2008): >>>>>> >>>>>> >>>>>> >>>>>>>> is a SAGA command line binding something you would >>>>>>>> conider worth pursuing? We actually started to do >>>>>>>> something like that, in a pet project... >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> Do you mean the ability to implement any defined command >>>>>>> line interface using the SAGA APIs? (i.e. internal to the >>>>>>> command) Or To define a set of command line tools to cover >>>>>>> elements of the SAGA API? >>>>>>> >>>>>>> >>>>>>> >>>>>> The latter. For example, for the SAGA call >>>>>> >>>>>> class saga::filesystem::file >>>>>> { >>>>>> void copy (saga::url src, saga::url tgt, it flags); >>>>>> } >>>>>> >>>>>> define the command line tool >>>>>> >>>>>> saga_file_copy [flags] <src> <tgt> >>>>>> >>>>>> flags: >>>>>> session related flags >>>>>> -s|--session <s> run command in session s >>>>>> -c|--context <c> use context c >>>>>> >>>>>> operational flags >>>>>> -a|--async=<Sync|Async|Task> >>>>>> use async mode Sync, Async or Task >>>>>> default is Sync >>>>>> call specific flags >>>>>> -r|--recursive copy recursively >>>>>> -o|--overwrite overwrite target if exists >>>>>> ... >>>>>> >>>>>> So, the command line tools would basically reflect what we >>>>>> define in the SAGA API spec, with a set of flags which are >>>>>> consistent for all command line tools such defined. >>>>>> >>>>>> >>>>>> A session could look like: >>>>>> >>>>>> # saga_create_context --name=my_context --type=UserPass --user=anon >>>>>> <prompts for password> >>>>>> >>>>>> # saga_create_session --name my_session --add_context=my_context >>>>>> >>>>>> # /bin/date | saga_file_cat --session=my_session --write >>>>>> gsiftp://localhost/tmp/in.dat >>>>>> >>>>>> # saga_file_copy --session=my_session gsiftp://localhost/tmp/in.dat >>>>>> gsiftp://remotehost/tmp/out.dat >>>>>> >>>>>> # saga_file_cat --session=my_session gsiftp://remotehost/tmp/out.dat >>>>>> Wed Jun 4 14:43:27 CEST 2008 >>>>>> >>>>>> >>>>>> or, with some default assumptions of course (default session >>>>>> and context): >>>>>> >>>>>> >>>>>> # /bin/date | saga_file_cat --write gsiftp://localhost/tmp/in.dat >>>>>> # saga_file_copy gsiftp://localhost/tmp/in.dat >>>>>> gsiftp://remotehost/tmp/out.dat >>>>>> # saga_file_cat gsiftp://remotehost/tmp/out.dat >>>>>> Wed Jun 4 14:43:27 CEST 2008 >>>>>> >>>>>> >>>>>> Best, Andre. >>>>>> >>>>>> PS.: As for option (a) of yours: yes, that would be trivial to >>>>>> implement in SAGA :-) Well, at least it would be easy (one >>>>>> needs to add some magick for state management, to keep track >>>>>> of async ops and security credentials between separate calls >>>>>> to different tools. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> Steven >>>>>>> >>>>>>> >>>>>>> >>>>>> -- >>>>>> Nothing is ever easy. >>>>>> >>>>>> >>>>>> >>>>> -- >>>>> ogsa-wg mailing list >>>>> ogsa-wg(a)ogf.org >>>>> http://www.ogf.org/mailman/listinfo/ogsa-wg >>>>>

1 0

Updated WSRF BP document
by Michel Drescher 04 Jun '08

04 Jun '08

Folks, in some spare time I dared updating the WSRF BP Word document as taken from Gridforge. Please find the new version attached (draft 47, document revision 44) - I feel uneasy trying to put it on Gridforge... Please comment. Cheers, Michel -- Michel Drescher Fujitsu Laboratories of Europe, Ltd. Hayes Park Central Hayes End Road Hayes, Middlesex UB4 8FE Reg. No. 4153469 +44 20 8606 4834 Michel.Drescher(a)uk.fujitsu.com

1 0

Grid Command Line interfaces
by Steven Newhouse 04 Jun '08

04 Jun '08

At the discussion in the workshop today we discussed defining a command line interface to interact with the HPCBP/BES service. Oxana pointes us to these tools generated by Nordu Grid. > I meant the NorduGrid's ARC CLI and API. The "classic" pre-BES CLI and > API are documented here: > > http://www.nordugrid.org/documents/ui.pdf > http://www.nordugrid.org/documents/arclib.pdf > > and the new BES-compatible prototypes here: > > http://www.nordugrid.org/documents/arc1-clients.pdf > > Hope it helps, > Oxana

3 8

Re: [ogsa-wg] Grid Command Line interfaces
by Hugo Mills 04 Jun '08

04 Jun '08

On Wed, Jun 04, 2008 at 02:48:25PM +0100, Omer F. Rana wrote: > Andre: I thought the aim of SAGA was to provide a programmatic > API rather than a command line tools interface? If you're a shell programmer (as I tend to be these days), the command-line tools *are* the API binding for the language... Hugo. -- Hugo Mills <hugo(a)soton.ac.uk | hugo(a)omii.ac.uk> OMII-UK, Southampton, SO18 1NP, UK

1 0

Slide presentation for OGSA-WG session today (6/4 2-3:30pm)
by Hiro Kishimoto 04 Jun '08

04 Jun '08

Hi all, Please find draft slide presentation for today's OGSA-WG session at Sant Gervasi. Since network connection is very unstable, we are unlikely to setup polycom bridge for this session. Thanks, ---- Hiro Kishimoto

1 0

SAS Grid Use Cases for ISV primer
by Christopher Smith 03 Jun '08

03 Jun '08

The attached document describes the way that SAS uses Grid technology within their environment. It would be nice to incorporate these use cases into the ISV primer document if possible. -- Chris

1 0

Life Science Resource Profile BOF
by Osamu Tatebe 02 Jun '08

02 Jun '08

Hi all, # sorry for the cross-posting I would like to inform there will be an iteresting BoF about Life Science Ressource Profile. Basically it intends to standardize a set of metadata for life science based on RNS (Resource Namespace Service). Please join to the BoF if you are interested in. Thursday, June 5 9:00 am - 10:30 am Life Science Resource Profile BOF (90 mins) Life Science Resource Profile Working Group Fumikazu KONISHI, Tokyo Tech, JAPAN A Life Science application has the history to which the format and/or the name of file have been decided mutually without order. When one file is applied to name, each researcher applies a probably different name even the file is completely the same content. Even same naming rule applied in some project, the other similar project is not necessarily applied to the same rule. Even same rule applied in one organization, it is hard to understand the file content without scanning the real file by the other organization. We think that this is a big barrier for an interoperability among life science project. Many life science grid project had challenged this kind of the naming problem, then catalog service is one of the solution for the purpose. The service allows us to identify a content without scanner. Any user can access the catalog data, then the user understand what it is. Some workflow engine can manage the prerequisite process for the next transition point. However we don’t have any standard catalog entry for life science research project. Thus, we still have same problem for an interoperability among an inter-grid project. In the OGF, Grid File System Working Group (GFS-WG) had published a proposed recommendation such as “Resource Namespace Service Specification” in Sep 6, 2006. The document describes the specification of the Resource Namespace Service (RNS) which offers a standard way for mapping names to any resource within distributed environnant. GFS-WG had designed the specification for catalog service for implementing the grid file service. However, the RNS can add the catalog profile that specializes in life science, with the GFS-Profile because the extendibility is very abundant. Therefore, LSR-Profile WG works on defining for Life Science Resource Profile based on RNS specification. Location: Sant Gervasi -- Osamu Tatebe <tatebe(a)cs.tsukuba.ac.jp>

1 0

Re: [ogsa-wg] Fwd: FINAL CALL: ogsa info & data model arch doc
by Ellen Stokes 02 Jun '08

02 Jun '08

Hiro, Yes, I agree. I will remove the 'paper' from the title. I was wondering when someone would make that comment. Ellen "Hiro Kishimoto" <hiro.kishimoto(a)jp.fujitsu.com> Sent by: hiro.kishimoto(a)gmail.com 06/02/2008 12:20 AM To Ellen Stokes/Austin/IBM@IBMUS cc hiro.kishimoto(a)gmail.com Subject Fwd: [ogsa-wg] FINAL CALL: ogsa info & data model arch doc Hi Ellen, Just a minor comment. Do you think the title should have "paper" at the end? How about "Information & Data Modeling in OGSA Grids Architecture"? Thanks, ---- Hiro Kishimoto -------- Original Message -------- Subject: [ogsa-wg] FINAL CALL: ogsa info & data model arch doc From: Ellen Stokes <stokese(a)us.ibm.com> To: ogsa-wg(a)ogf.org Date: 2008/05/28 23:00 > Hi all, > > The OGSA info/data model arch doc has exited public comment, the comments > received have been reflected into the doc (and the trackers updated), and > this updated version has been reviewed again by the OGSA wg with comments > reflected into the doc as well as example alignment with the GLUE docs > that were submitted last week to the pubic comment process. > > This starts the final call for comments for the OGSA info/data model arch > doc - this updated doc (per above paragraph) is attached below. > (I'll post to GridForge when it starts working again). > > Please send comments no later than Friday June 6. > After this final call and any minor updates from this final call this doc > will be sent to the OGF editor for publication as an informational > document. > > Ellen > > > > > ------------------------------------------------------------------------ > > -- > ogsa-wg mailing list > ogsa-wg(a)ogf.org > http://www.ogf.org/mailman/listinfo/ogsa-wg

1 0

Re: [ogsa-wg] FINAL CALL: ogsa info & data model arch doc
by Hiro Kishimoto 02 Jun '08

02 Jun '08

Hi Ellen, Just a minor comment. Do you think the title should have "paper" at the end? How about "Information & Data Modeling in OGSA Grids Architecture"? Thanks, ---- Hiro Kishimoto -------- Original Message -------- Subject: [ogsa-wg] FINAL CALL: ogsa info & data model arch doc From: Ellen Stokes <stokese(a)us.ibm.com> To: ogsa-wg(a)ogf.org Date: 2008/05/28 23:00 > Hi all, > > The OGSA info/data model arch doc has exited public comment, the comments > received have been reflected into the doc (and the trackers updated), and > this updated version has been reviewed again by the OGSA wg with comments > reflected into the doc as well as example alignment with the GLUE docs > that were submitted last week to the pubic comment process. > > This starts the final call for comments for the OGSA info/data model arch > doc - this updated doc (per above paragraph) is attached below. > (I'll post to GridForge when it starts working again). > > Please send comments no later than Friday June 6. > After this final call and any minor updates from this final call this doc > will be sent to the OGF editor for publication as an informational > document. > > Ellen > > > > > ------------------------------------------------------------------------ > > -- > ogsa-wg mailing list > ogsa-wg(a)ogf.org > http://www.ogf.org/mailman/listinfo/ogsa-wg

1 0