May 2006 - ur-wg - lists.ogf.org

Meeting Notes
by Donal K. Fellows 14 Jun '06

14 Jun '06

I'm not very good at this note taking business, but here's what I've got: ---------------------------------- Collaboration with OGSA good idea once things are solidified. Future version to extend to more complex things than batch system job accounting. Stick with using email for resolving issues; not worth changing technologies half way through. Short-term Timeline: Mailing list discussions to close: 30 June Consensus: 15 July Revised document: 15 August Submit to editor: 1 September Three-way joint meeting: OGSA RUS UR Call for use cases and reference implementations Telecons ======== Keep going. Biweekly. One hour. 1300 UTC. First on 25 May. ---------------------------------- Donal Fellows.

4 4

Prototype of strawman
by Donal K. Fellows 31 May '06

31 May '06

Hi everyone! Here's a snapshot of where I've got to with doing an updated usage record schema. It's massively incomplete when it comes to listing all the elements, but it's got some of the flavour of what I intended. The main things to note are that it defines a CompoundUsageRecord and an AtomicActivityUsageRecord (which is incomplete) that are both in effect subtypes of UsageRecord (which has a few elements associated with it) and that I've split apart the concepts of Memory and NodeCount into PeakMemory and AverageMemory (and PeakNC and AverageNC respectively). There are probably more useful concepts to identify, and there's certainly more work to do copying things across. I'm also trying to put in sane documentation comments as I go. In any case, comments/brickbats would be welcome before I invest much more time and effort into this. :-) (I'm also using a somewhat-proper namespace URI now.) Donal.

1 0

Concall Agenda: 25-May
by Laura F McGinnis 24 May '06

24 May '06

Usage Records concalls will resume tomorrow, 25-May at 2pm BST/9am EDT (Pittsburgh). Call-in information is below. The agenda is: 1) Status on comments - how active is the mailing list? 2) Review of GGF17 notes 3) Discussion of comments that have been responded to - Do we have consensus on anything yet? 4) Discussion of comments that have not been responded to - as time permits. Thx LM Primary Dial-in Number: 0844.888.8888 (UK 5p National Rate) Alternate Dial-in Numbers: +44.870.088.5706 (For Callers Outside of the U.K.) 01805.004.102 (For Callers in Germany) The Participant Access Code is: 61652. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Laura F. McGinnis, Project Coordinator Data & Information Resource Services Pittsburgh Supercomputing Center email: lfm(a)psc.edu 300 South Craig St, #313 phone: 412-268-5642 Pittsburgh, PA 15213 fax: 412-268-5832 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

1 0

Out of Scope: Comment #5k
by Laura F McGinnis 24 May '06

24 May '06

2 2

Extensions: Comment #10
by Laura F McGinnis 24 May '06

24 May '06

2 2

Mailing List Discussions: Comment #14a
by Laura F McGinnis 24 May '06

24 May '06

2 2

Mailing List Discussions: Comment #3c
by Laura F McGinnis 18 May '06

18 May '06

4 5

Next few conference calls
by Stephen M Pickles 16 May '06

16 May '06

We agreed at GGF17 to hold conference calls every two weeks, at the same time. Accordingly I have booked the next three conference calls: Thursday 25 May 2006, 2pm BST (9am Pittsburgh) Thursday 2 June 2006, 2pm BST Thursday 16 June 2006, 2pm BST BST is British Summer Time (UTC+1). I have booked 6 lines for 55 minutes. The details are the same for each call: Primary Dial-in Number: 0844.888.8888 (UK 5p National Rate) Alternate Dial-in Numbers: +44.870.088.5706 (For Callers Outside of the U.K.) 01805.004.102 (For Callers in Germany) The Participant Access Code is: 61652. Best wishes, Stephen

3 3

Re: [ur-wg] Meeting Notes
by Matthew Ford 11 May '06

11 May '06

Quoting "Donal K. Fellows" <donal.k.fellows(a)manchester.ac.uk>: > Future version to extend to more complex things than batch system job > accounting. But I think think we have this now! Maybe I'm reading too much into the term "extend". It's much more a change of method and clarification that I would like to see. As you move through-out the document it becomes increasingly generalised. By section ten, I believe the current specs clear intention is to be able to account much more than a batch job. However it's not with out problem. Some thoughts and quotes: - Job Level Accounting from the Original Spec is supposed to work at the batch job level. It is restricted form of the usage of the base properties of section 3 or later the common properties of section 10. From Sec.4: "Job level accounting reports accounting data at the job level. PBS and LoadLeveller. This type of usage record MAY contain any of the base properties. This type of usage record MUST contain at least one of the following properties:o LocalJobId o GlobalJobId" - Aggregate Accounting is specifically allowed, and integral to the current doc. From Sec.5: "Aggregate accounting reports the accounting data in aggregate (summarized form). Aggregate accounting MAY contain any of base properties listed in this document," From Introduction: "Aggregation: Most sites have indicated that job-level aggregation is sufficient for their current needs. Where sites aggregate or decompose to other levels of usage tracking, provisions are available within the schema to accommodate." From Sec.3: "Base Properties: The following is a list of base properties that define common usage record requirements for both job level and aggregate properties." - The Global definitions in sections 7,8 and 9 clearly intend to setup a generic framework in which most types of usage can can be accounted. + Sec.7 sets-up Global Elements to allow substitution for inclusion into other schemas. + Sec.8. sets-up Global attributes sets up generic attributes which maintain meaning independent of context. i.e, forcing common usage of units. + Sec.9. specifically sets-up a *generic* usage record From Sec.7 "The global definitions are those that may be used compliantly with this specification as root elements for an XML document or which may be used as extension points within or included within other XML Schema definitions." From Sec.8 "Global attributes, and attribute groups, are attributes that are common to many of the element definitions contained in this specification. A global definition of these maintains standard semantic meaning within each context that they are used." From Sec.9 "UsageRecordType Complex Type: This complex type definition establishes the structure of the *generic* usage record." - Section 10, Usage Record Common Properties is an obivious attempt to generalise the base proprieties of section 3. The problem is that not all the base properties of section three are appropriate as Common Properties for a *generic* record. Further as the bulk of section 3 is seemingly based on batch level reporting, the scope of the section is serverely limited. From Sec.10 "10. Usage Record Common Properties: the complete specifications for each element that MAY appear in the *generic* usage record are presented below." > > Stick with using email for resolving issues; not worth changing > technologies half way through. > > Short-term Timeline: > Mailing list discussions to close: 30 June > Consensus: 15 July > Revised document: 15 August > Submit to editor: 1 September > > Three-way joint meeting: OGSA RUS UR > > Call for use cases and reference implementations > > Telecons > ======== > Keep going. Biweekly. One hour. 1300 UTC. First on 25 May. > ---------------------------------- > > Donal Fellows. > >

2 1

UR-WG GGF17 Slides (draft) (fwd)
by Laura F. McGinnis 10 May '06

10 May '06

Here are the slides for tomorrow's UR-WG session. Please let me know if I'm missing anything. Because of time constraints we will not be discussing the individual comments at the session. We will focus on process and planning instead. LM

1 0