- jsdl-wg - lists.ogf.org

Reminder no call this morning,
by Michael Saravo 26 Jan '12

26 Jan '12

Just a reminder that last week we decided to not have a call this week. --Mike

1 0

reminder call in 3 hours
by Michael Saravo 19 Jan '12

19 Jan '12

Just a gentle reminder we will be starting our JSDL calls back up in approximately 3 hours (8:30 am eastern time). Today we would like to talk about preparations/attendance at the next OGF in Oxford. Also I would like to gauge interest in the current set of requirements and see if anyone is willing to take it on as a task for themselves to come up with example profiles/renderings that meet some of the requirements. I still have a tracker/action item for me to add a couple requirements after parsing a document which I will try to do before the call. I think it would be a good goal to have a couple actual jsdl changes or profiles at OGF to discuss. --Mike

5 7

requirements from BES/JSDL document to discuss on the call ( in about an hour)
by Michael Saravo 19 Jan '12

19 Jan '12

Sorry if the last follow up email caused confusion, it should not have been titled call in 3 hours, that was a reply to the original email I sent. I have parsed the document that I had a task to do and below is what came out. I would like to discuss them briefly on todays call to get feedback and then I will create tracker items for them. unique-name attribute, This is currently supported by GenesisII in the resource request element It is used to group jobs, currently to manage a Scratch filesystem which prevents duplicate files from being staged multiple times, but in the future the use could be extended (to scheduling for instance) Wall clock time restriction **currently in posix not resource requirements matching parameters name/value pair that a job can use to indicate arbitrary properties to schedule on requires/supports Profile that implements OGSA-WSRF-BP, all BES attributes are there for interoperability We need a way to determine what staging protocols a BES supports before scheduling (possibly related to the above). --Mike

1 0

A Happy New Year - and with refreshed energy into a successful 2012
by Michel Drescher 12 Jan '12

12 Jan '12

Dear all, I would like to wish you all a Happy New Year, and may your good intents for 2012 come true. :-) The new year just begun, and activities are picking up momentum again after well-deserved vacations. To join the bunch I would like to pick up again with JSDL, realising that OGF34 is already waiting for us in the near future. To kick off our activities for 2012 I would like to resume our weekly conference calls starting next week Thursday 19 January 2012, dedicating it to preparations for OGF34, and a plan for what we would like to achieve this year. Cheers, and a toast to a successful 2012 for JSDL, Michael and Michel -- Stichting European Grid Initiative (EGI.eu) http://www.egi.eu Mobile:+31 (0)6 303 726 55 Skype: michel.drescher.egi

2 1

Telecon tomorrow
by Michael Saravo 15 Dec '11

15 Dec '11

We will be having a call tomorrow at the scheduled time (8:30 am eastern). Connection details are located here: http://forge.gridforum.org/sf/wiki/do/viewPage/projects.jsdl-wg/wiki/HomePa… The jsdl-wg source forge page is still not entirely up yet. Specifically the tasks section, under which we have been tracking action items is still not available. Tomorrows call will most likely be brief. The main focus of which I would like to discuss what people feel is most important going forward in jsdl. I.e I would like to get an opinion of what we should be focusing on. Next week is a holiday, and as such the call will be cancelled. I would like a good idea of what topics we can begin focusing on immediately in the new year to get jsdl back making progress. --Mike

3 4

Conference Call cancelled
by Michael Saravo 01 Dec '11

01 Dec '11

Sorry for the late notice, but we will not be having a jsdl call today. I just got back in town two days ago and since my return grid forge has been down so I have not been able to make any progress on my action items or review the minutes from the last meeting. We will have the normally scheduled call next week. --Mike

1 0

Re: [jsdl-wg] Trackers, artefacts and assignees
by Michel Drescher 22 Nov '11

22 Nov '11

Hi Oxana, Thanks for notifying me. I have added Morris as a WG member so that you can assign artifacts to him. I have also created a provisional new tracker, "[PROVISIONAL] Feature requests" ( http://forge.gridforum.org/sf/tracker/do/listArtifacts/projects.jsdl-wg/tra…) where you can add the artefacts. I also moved the artifacts that Etienne created to that new tracker. Philip, can you please archive the rest of the trackers away? Cheers, Michel On 21 November 2011 22:46, Oxana Smirnova <oxana.smirnova(a)hep.lu.se> wrote: > Hi Michel, > > I see that GridForge is an impenetrable enigma :-) Still, where should I > create tracker artefacts? I can follow Etienne and create them in any > active tracker, but this looks ugly. > > There's another small problem: I can assign artefacts only to the JSDL WG > members, and Morris is not among them. > > Cheers, > Oxana > -- Stichting European Grid Initiative (EGI.eu) P.O. Box 41882, 1009 DB Amsterdam 140 Science Park, 1098 XG Amsterdam The Netherlands F: +31 (0)20 893 2007 M:+31 (0)6 303 726 55 Skype: michel.drescher.egi

1 0

Gridforge system change
by Michel Drescher 18 Nov '11

18 Nov '11

Hi Joel, For the JSDL Working Group, we are using Gridforge Tasks to organise our work (among other stuff). However, we (well, I) seem unable to change the task change approval behaviour to effectively not approve any changes at all; it always enables approval for the status and the end date (see http://forge.gridforum.org/sf/taskmgr/do/adminGeneralSettings/projects.jsdl… ) Can you change this for us please? We would like to disable approval at all for Tasks. Cheers, Michel -- Stichting European Grid Initiative (EGI.eu) P.O. Box 41882, 1009 DB Amsterdam 140 Science Park, 1098 XG Amsterdam The Netherlands F: +31 (0)20 893 2007 M:+31 (0)6 303 726 55 Skype: michel.drescher.egi

3 3

OGF JSDL : We need to define which incarnation (view) of the JSDL document we are trying to specify
by Etienne URBAH 17 Nov '11

17 Nov '11

Michel, Philipp and all, +------------------+ | JSDL Documents | +------------------+ Inside the OGF JSDL WG, we are trying to improve the specifications of the JSDL document. But during the lifetime of a job, there are at least 3 incarnations (or views) of its JSDL document : User JSDL Document ------------------ - This is the document provided by the user submitting the job. - The syntax of this document should permit abstraction and should provide flexibility. - In particular, it is advisable that this document permits : -- Static 'OR' operators for requirements as described at http://forge.ogf.org/sf/go/artf6522 -- Conditional requirements as described at http://forge.ogf.org/sf/go/artf6521 Contextualized JSDL Document ---------------------------- - Out of the User JSDL Document, a matchmaker service produces this Contextualized JSDL Document and submits it to an LRMS (Batch System), which has to understand and execute it. - Therefore, the matchmaker service must solve the flexibility of the User JSDL Document against available resources, and the produded Contextualized JSDL Document must be deterministic. - In particular, the Contextualized JSDL Document : -- may still contain static 'OR' operators for requirements as described at http://forge.ogf.org/sf/go/artf6522 -- should NOT contain conditional requirements as described at http://forge.ogf.org/sf/go/artf6521 Activity Document ----------------- - This Activity Document contains only timestamped history, logs, traces, ... about the job, for purposes of monitoring, forensics, security audits, stats, data mining, ... - Therefore, this Activity Document should contain the User JSDL Document and the Contextualized JSDL Document, but only as embedded text. - It is advisable that this Activity Document indicates, for each user requirement, if the matchmaker service or the LRMS (Batch system) was able to really fulfill this user requirement. +-------------------------------------+ | Target of the JSDL specifications | +-------------------------------------+ My personal opinion is : - The specifications of the Contextualized JSDL Document are already provided by each LRMS (Batch system), such as Condor, LSF, PBS, SGE, ... - The target of the JSDL specifications which we have to improve is the User JSDL Document. - We should also take into account the existence of the 2 other documents, and describe the impact of the JSDL specifications on them when relevant. +--------------+ | Conclusion | +--------------+ - Please study carefully the definitions which I gave above for the 3 documents. Do not hesitate to criticize and provide suggestions for improvements. - Please provide also your opinion on which document is the target of the JSDL specifications. Thank you in advance for your work. Best regards. ----------------------------------------------------- Etienne URBAH LAL, Univ Paris-Sud, IN2P3/CNRS Bat 200 91898 ORSAY France Tel: +33 1 64 46 84 87 Skype: etienne.urbah Mob: +33 6 22 30 53 27 mailto:urbah@lal.in2p3.fr ----------------------------------------------------- On Thu, 17/11/2011 15:36, Michel Drescher wrote: > > * The group discussed three "incarnations" of a JSDL document (or views): > > ** The document a user submits, that allows abstraction and flexibility > > ** The contextualised document, which a matchmaker service produced out of solving the flexibility in the submitted version against available resources > > ** The document that describes the current activity as an activity document (see activity schema) > > * Take this discussion out on the mailing list and ask for comments before deciding on scope. > > Project: JSDL-WG

1 0

Fwd: [glue-wg] GLUE 2.0 attributes for usage inside JSDL
by Michel Drescher 17 Nov '11

17 Nov '11

Dear all, Here is the Email thread concerning introducing XQuery expressions in JSDL. The respective document is:http://www.ggf.org/documents/GFD.137.pdf A presentation (by me I think) is: http://www.ogf.org/gf/event_schedule/?id=903 Cheers, Michel ---------- Forwarded message ---------- From: Sergio Andreozzi <sergio.andreozzi(a)egi.eu> Date: 16 November 2011 10:42 Subject: Fwd: [glue-wg] GLUE 2.0 attributes for usage inside JSDL To: Michel Drescher <michel.drescher(a)egi.eu> Hi Michel, The OGF doc is referenced below. Plus you can consider this presentation about extending JSDL with XQuery made by a guy you should know: http://www.ogf.org/gf/event_schedule/?id=903 :) Cheers, Sergio ---------- Forwarded message ---------- From: Sergio Andreozzi <sergio.andreozzi(a)egi.eu> Date: 21 September 2011 12:38 Subject: Re: [glue-wg] GLUE 2.0 attributes for usage inside JSDL To: Etienne URBAH <urbah(a)lal.in2p3.fr> Cc: "John-Paul F. NAVARRO" <navarro(a)mcs.anl.gov>, glue-wg(a)ogf.org, jsdl-wg(a)ogf.org Dear Etienne et Al., The issue of JSDL/GLUE integration was touched few times in the past. If the use case is to express requirements on GLUE-based information, I consider the approach taken in JSDL 1.0 not suitable for a more complex set of information such as coming from GLUE. When selecting a computing service for instance, you may want to express requirements on the characteristics of the endpoint, of the execution environment, of the application environment and on the share. For each computing service, you may have many instances of the subcomponents, but not all are associated. E.g. a certain computing share is defined on top of 2 of the 5 execution environments, so you need to match requirements on the execEnv, on the share and the fact that the two are "in relationships". In the past, we have discussed to have the option to express requirements using an XQuery expression embedded in the JSDL. While this is a generic approach and would make JSDL not depended on GLUE terms (which is a good option as giving more flexibility), it has the drawback of having the need to write queries that may be complex. To mitigate this, you could think about letting the users express requirements with a simple descriptive format from which a query can be generated automatically. See section 5.3 of this document as an example of XQuery expression based on an XML document describing computing resources based on a preliminary draft of GLUE 2 back in 2008: http://www.ggf.org/documents/GFD.137.pdf My recommendation is, before to make any final choice, test the solution on production use cases to verify the suitability. Kind regards, Sergio On 21 September 2011 11:27, Etienne URBAH <urbah(a)lal.in2p3.fr> wrote: > On Tue, 20/09/2011 17:09, Etienne URBAH wrote: >> >> Michael, >> >> Concerning the GLUE 2.0 attributes for usage inside JSDL, I suggest to >> look at following pages : >> >> http://forge.gridforum.org/sf/wiki/do/viewPage/projects.pgi-wg/wiki/ReqJD3 >> >> >> http://forge.gridforum.org/sf/docman/do/downloadDocument/projects.pgi-wg/do… >> >> >> Best regards. >> >> ----------------------------------------------------- >> Etienne URBAH LAL, Univ Paris-Sud, IN2P3/CNRS >> Bat 200 91898 ORSAY France >> Tel: +33 1 64 46 84 87 Skype: etienne.urbah >> Mob: +33 6 22 30 53 27 mailto:urbah@lal.in2p3.fr >> ----------------------------------------------------- > > > _______________________________________________ > glue-wg mailing list > glue-wg(a)ogf.org > http://www.ogf.org/mailman/listinfo/glue-wg > > -- Sergio Andreozzi - Policy Development Manager - EGI.eu http://www.egi.eu - skype:sergio.andreozzi.egi -- Sergio Andreozzi - Policy Development Manager - EGI.eu http://www.egi.eu - skype:sergio.andreozzi.egi -- Stichting European Grid Initiative (EGI.eu) P.O. Box 41882, 1009 DB Amsterdam 140 Science Park, 1098 XG Amsterdam The Netherlands F: +31 (0)20 893 2007 M:+31 (0)6 303 726 55 Skype: michel.drescher.egi

1 0