[Pgi-wg] Promised document

Wed May 20 07:41:53 CDT 2009

Team,

  further work with white flags between the fronts...

Since fronts 1 and 2 coming closer I thought about the question what we really keep from BES vs. what we have to do new, here some thoughts taking the document from both fronts into account:

### BES portType level - BES-Factory
#Keep portType to create activities
#Re-define operation CreateActivity with new in-out-fault-elements

### BES portType level - BES-Activity
#Keep portType to modify single activities (instead of using factory portType)
#Add operations to modify single(vector) activities

### BES portType level - BES-Management
#remove portType

### BES State Model
#Add our proposed manual data-staging requirements that affect the states
#Use GLUE2 syntax to describe it - but define new values for our additional states

### Information Model
#Use GLUE2 instead
#But definition of allowed values for GLUE2 structures
#deprecate old information schemas (e.g. FactoryAttributes)
#find ways to scale with outcome of available activities (e.g. EPR list)

### Resource Model
#only WS-I I guess
# no WS-RF agreement (or other profiles)

Please correct/add if I'm somewhere wrong...

Some thoughts,
Morris

------------------------------------------------------------
Morris Riedel
SW - Engineer
Distributed Systems and Grid Computing Division
Jülich Supercomputing Centre (JSC)
Forschungszentrum Juelich
Wilhelm-Johnen-Str. 1
D - 52425 Juelich
Germany

Email: m.riedel at fz-juelich.de
Info: http://www.fz-juelich.de/jsc/JSCPeople/riedel
Phone: +49 2461 61 - 3651
Fax: +49 2461 61 - 6656

Skype: MorrisRiedel

"We work to better ourselves, and the rest of humanity"

Sitz der Gesellschaft: Jülich
Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498
Vorsitzende des Aufsichtsrats: MinDirig'in Bärbel Brumme-Bothe
Vorstand: Prof. Dr. Achim Bachem (Vorsitzender), 
Dr. Ulrich Krafft (stellv. Vorsitzender)

>------Original Message-----
>-From: pgi-wg-bounces at ogf.org [mailto:pgi-wg-bounces at ogf.org] On Behalf Of
>-Morris Riedel
>-Sent: Wednesday, May 20, 2009 2:18 PM
>-To: 'Oxana Smirnova'; pgi-wg at ogf.org
>-Subject: Re: [Pgi-wg] Promised document
>-
>-Yeah,
>-
>-  I agree on this one document Oxana - but with obviously two fronts already
>-established it's hard to agree on one and that's why I proposed to have this factsheet
>-approach with both voices in it per item/operation - but this is not what the group
>-wants obviously... :-)
>-
>-
>-However, just that we are all sure that we have these fronts as follows:
>-
>-
>-Front 1
>-Keeping BES/JSDL nearly as is and try to fit / squeeze solutions for the requirements
>-in it or put them close to them (e.g. modify portType operations already existing).
>-
>-
>-Front 2
>-Taking bits and pieces from BES/JSDL where it makes sense (w/o structures), but
>-define a new structure (e.g. new portType operations) by still referencing to the origin
>-in the respective source documents.
>-
>-
>-Realistically, both fronts mean no backwards compatibility to a BES 1.0.
>-
>-
>-Since the beginning it was 'start from scratch vs. not changing old elements'.
>-
>-
>-Now, we have Front 1 willing to change views towards changing a few standard
>-elements and Front 2 willing to keep elements (at least w/o structure) from good
>-elements of the standard by creating a new structure.
>-
>-
>-This already means we getting closer together over time - so I'm looking forward to
>-further discussions today.
>-
>-
>-End of the philosophical work,
>-Morris
>-
>-
>-------------------------------------------------------------
>-Morris Riedel
>-SW - Engineer
>-Distributed Systems and Grid Computing Division Jülich Supercomputing Centre
>-(JSC) Forschungszentrum Juelich Wilhelm-Johnen-Str. 1 D - 52425 Juelich
>-Germany
>-
>-Email: m.riedel at fz-juelich.de
>-Info: http://www.fz-juelich.de/jsc/JSCPeople/riedel
>-Phone: +49 2461 61 - 3651
>-Fax: +49 2461 61 - 6656
>-
>-Skype: MorrisRiedel
>-
>-"We work to better ourselves, and the rest of humanity"
>-
>-Sitz der Gesellschaft: Jülich
>-Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498 Vorsitzende
>-des Aufsichtsrats: MinDirig'in Bärbel Brumme-Bothe
>-Vorstand: Prof. Dr. Achim Bachem (Vorsitzender), Dr. Ulrich Krafft (stellv.
>-Vorsitzender)
>-
>-
>->------Original Message-----
>->-From: pgi-wg-bounces at ogf.org [mailto:pgi-wg-bounces at ogf.org] On Behalf Of
>->-Oxana Smirnova
>->-Sent: Wednesday, May 20, 2009 1:55 PM
>->-To: pgi-wg at ogf.org
>->-Subject: Re: [Pgi-wg] Promised document
>->-
>->-Hi,
>->-
>->-20.05.2009 13:36, Morris Riedel пишет:
>->-> Hi,
>->->
>->->> - We will *always* have the two front, ...
>->->
>->-> ... we shouldn't - in the end, all we want is interoperability and I hope we
>->-> still can get consensus that makes sense and not drift off like in an
>->-> IDL-like thinking where solutions come up that are not interoperable at
>->-> all...
>->->
>->-
>->-Precisely, and to avoid two or three or N fronts, we must establish a
>->-procedure. When a document is circulated for comments or additions,
>->-these comments/additions should be attached/included to the circulated
>->-document. They must not come in form of another document that in turns
>->-demands a separate round of comments.
>->-
>->-So, let's take one document at a time, and let's formalize a bit the way
>->-comments are submitted. Specifically, I find it convenient when comments
>->-are in-line, and additions/corrections are inserted with tracing of
>->-changes switched on. This will hopefully prevent opening new fronts. I
>->-do not want to merge two or three or N documents, I want to finish work
>->-on ONE document first.
>->-
>->-Cheers,
>->-Oxana
>->-_______________________________________________
>->-Pgi-wg mailing list
>->-Pgi-wg at ogf.org
>->-http://www.ogf.org/mailman/listinfo/pgi-wg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3550 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/pgi-wg/attachments/20090520/111ed9f2/attachment.bin 