[RUS-WG] Chater and RUS core spec
Xiaoyu Chen
Xiaoyu.Chen at brunel.ac.uk
Fri Jan 26 11:01:02 CST 2007
hello, everyone:
----------------------------------------------------------------------------------------------------
>Today's Topics:
>1. Re: New Charter in Documents area GridForge (Gilbert Netzer)
The chater document plans to divide the RUS specifications into "core" which is the current release and "extended" one, which server-side aggregation and data replication (previous in the scope of version 2.0). This seems reasonable but we need to modify our specification 2.0 draft as extensions, which means we have to reconsider the back-compatibility to "core" spec.
In this case, I would like to put my comments to core specification here, which were supposed to be in version 2.0.
a). the core schema is based on [URWG SPEC] 1.8, which should be the current schema version 1.9 with namespace as http://schema.ogf.org/urf/2003/09/urf;
b). why RUSId instead of urf:RecordIdentity#recordId;
c). As the charter document, the storage of RUS "core" specification should be [URWG SPEC] compatable, but the rus::RUSUsageRecord is not. I can understand the reason why use the rus:RUSId and rus:WhoAndWhen elements, which are to ensure each usage record per usage document in case of oversize the maximum of Xindice XML file limitation (5Mb) and to tracing modification history of a particular usage record. However, why not leave the storage as [URWG SPEC] as it is, because the [URWG SPEC] 1.9 does provide "WhoAndWhen" property in urf:RecordIdentity element but only for creation of the usage record. This seems reasonable to me, 'cos the modification history should be the administrative tasks of an RUS implementation. Besides that, we also need tracing who also access what usage records for RUS administration to ensure the authorization framework works properly. If we put all these information in RUSUsageRecord (as defined now in current RUS core specification), the size of RUS usage record is really increasing and potentially oversize to 5MB as well. So what i can suggest here is leave storage as [URWG SPEC] and using log to monitoring and tracing RUS implementation. And this should not be put into the specificaiton itself becasue of implementation dependent.
d). Because of the proposal of "RUSUsageRecord" format, the service interface definition are too RUSId specific, in turn lacking of flexibility for batching operations on a group of usage records relating to certain criteria.
for example;
RUS:ModifyUsageRecordPart only allows to modify one particular usage record with "RUSId". In really application, users more would like to perform modifications upon a batch of usage records. e.g. a resource manager is intended to change the machine name (from "CRAY" to "BLUE") of a set of usage records previously stored. With current modification interface, we have to extract RUSId of these records first and then operation update operation one by one.
e). I also doubt the configuration of operation result, which should also be implementation dependent. When exposing Usage record through OGSA-DAI, for example, the OGSA-DAI itself returns reponse document to indicate the process status. I believe there are other batch-like systems provides status and results tracing. The RUS core specfication should keeps the service interface definition as flexible as it can. Other advanced features can be defined in extended specifications or implementions. Speaking of the RUS:operationResult, why not keeps this element as string type, but leaves the paring and processing of this element to implementations.
PS: i will also upload the content of last telcon to web, so that every one can have more details about comments above.
Best regards
School of Engineering and Design
Mobile: Mobile: ++44(0)7871876894
X. Chen
________________________________
From: rus-wg-bounces at ogf.org on behalf of rus-wg-request at ogf.org
Sent: Fri 26/01/2007 14:29
To: rus-wg at ogf.org
Subject: rus-wg Digest, Vol 4, Issue 13
Send rus-wg mailing list submissions to
rus-wg at ogf.org
To subscribe or unsubscribe via the World Wide Web, visit
http://www.ogf.org/mailman/listinfo/rus-wg
or, via email, send a message with subject or body 'help' to
rus-wg-request at ogf.org
You can reach the person managing the list at
rus-wg-owner at ogf.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of rus-wg digest..."
Today's Topics:
1. Re: New Charter in Documents area GridForge (Gilbert Netzer)
2. New Charter with review comments integrated (Morris Riedel)
3. WG: New Charter with review comments integrated (Morris Riedel)
----------------------------------------------------------------------
Message: 1
Date: Fri, 26 Jan 2007 10:18:36 +0100
From: Gilbert Netzer <noname at pdc.kth.se>
Subject: Re: [RUS-WG] New Charter in Documents area GridForge
To: Morris Riedel <m.riedel at fz-juelich.de>
Cc: rus-wg at ogf.org
Message-ID: <45B9C76C.9010809 at pdc.kth.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Hi Morris, hello RUS members,
I have tried to correct some spelling mistakes and added the References to
the section.
In my opinion the Charter looks good, thanks Morris for the work!
Best Regards
Gilbert Netzer
Morris Riedel wrote:
> Hi RUS ? team,
>
>
>
> please find on GridForge under Documents ? Charter
>
>
>
> a new version of the new charter (2007-01-24 ?)
>
>
>
> Please change the document as you like using the track changes option
> from word.
>
>
>
> Thanks for any comments and suggestions.
>
>
>
> Deadline for the changed would be tomorrow evening.
>
>
>
> Some initial points:
>
>
>
> (1)
>
> I discussed with a colleague that the specification should not be named
> as 2.0 and 1.0 otherwise it would make no sense to get 1.0 out if there
> are functions already needed for 2.0. So, we should argue like core
> (base) specification and on-top specifications?
>
>
>
> (2)
>
> This colleague is a long time with OGF ? so he helped me a bit with
> realistic timescales in the roadmap / milestones
>
>
>
> However, all points are also for discussion but we should consider his
> experiences from my point of view.
>
>
>
> Best regards,
>
> Morris
>
>
>
>
>
>
>
> --------------------------------------------------------------------------------
> Morris Riedel
>
> SW - Engineer
>
> Distributed Systems and Grid Computing Division
> Central Institute of Applied Mathematics
> Research Centre Juelich
>
> Wilhelm-Johnen-Str. 1
> D - 52425 Juelich
>
> Germany
>
>
>
> Email: m.riedel at fz-juelich.de <mailto:m.riedel at fz-juelich.de>
> Info: http://www.fz-juelich.de/zam/ZAMPeople/riedel
>
>
>
> Phone: +49 2461 61 - 3651
> Fax: +49 2461 61 - 6656
>
>
>
> Skype: MorrisRiedel
>
>
>
> 'We work to improve ourselves and the rest of mankind.'
>
>
>
>
> ------------------------------------------------------------------------
>
> --
> rus-wg mailing list
> rus-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/rus-wg
------------------------------
Message: 2
Date: Fri, 26 Jan 2007 15:24:36 +0100
From: "Morris Riedel" <m.riedel at fz-juelich.de>
Subject: [RUS-WG] New Charter with review comments integrated
To: <rus-wg at ogf.org>
Message-ID: <20070126142437.60415100020F at zam837.fz-juelich.de>
Content-Type: text/plain; charset="us-ascii"
Hi RUS - team,
please find on gridforge a slightly modified charter that addressed review
comments:
(1)
The appearance of OMII - Europe was significantly reduced since OGF is a
community effort, not a project effort
(remains just in context interoperability with funded efforts)
(2)
The security paragraph of section 2.2 was more or less what also the other
groups in area security within OGF want to achieve. So I get rid of it.
(3)
I try to foster more what should be inside the second specification, however
I'm quite unsure if we should add a profile for connection technologies such
as WS-RF or if we just state a rendering section like within OGSA-BES with
respect to WS-RF.
If no other reviews or comments reach me by 20:00 this evening, I will send
our new charter to our area director.
Thanks for helps,
Morris
----------------------------------------------------------------------------
----
Morris Riedel
SW - Engineer
Distributed Systems and Grid Computing Division
Central Institute of Applied Mathematics
Research Centre Juelich
Wilhelm-Johnen-Str. 1
D - 52425 Juelich
Germany
Email: <mailto:m.riedel at fz-juelich.de> m.riedel at fz-juelich.de
Info: <http://www.fz-juelich.de/zam/ZAMPeople/riedel>
http://www.fz-juelich.de/zam/ZAMPeople/riedel
Phone: +49 2461 61 - 3651
Fax: +49 2461 61 - 6656
Skype: MorrisRiedel
'We work to improve ourselves and the rest of mankind.'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/rus-wg/attachments/20070126/794f24a4/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2396 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/rus-wg/attachments/20070126/794f24a4/attachment-0001.bin
------------------------------
Message: 3
Date: Fri, 26 Jan 2007 15:29:19 +0100
From: "Morris Riedel" <m.riedel at fz-juelich.de>
Subject: [RUS-WG] WG: New Charter with review comments integrated
To: <rus-wg at ogf.org>
Message-ID: <20070126142920.7A3AE100048D at zam837.fz-juelich.de>
Content-Type: text/plain; charset="us-ascii"
Note that the document is indicated by the date of today!
----------------------------------------------------------------------------
----
Morris Riedel
SW - Engineer
Distributed Systems and Grid Computing Division
Central Institute of Applied Mathematics
Research Centre Juelich
Wilhelm-Johnen-Str. 1
D - 52425 Juelich
Germany
Email: <mailto:m.riedel at fz-juelich.de> m.riedel at fz-juelich.de
Info: <http://www.fz-juelich.de/zam/ZAMPeople/riedel>
http://www.fz-juelich.de/zam/ZAMPeople/riedel
Phone: +49 2461 61 - 3651
Fax: +49 2461 61 - 6656
Skype: MorrisRiedel
'We work to improve ourselves and the rest of mankind.'
_____
Von: rus-wg-bounces at ogf.org [mailto:rus-wg-bounces at ogf.org] Im Auftrag von
Morris Riedel
Gesendet: Freitag, 26. Januar 2007 15:25
An: rus-wg at ogf.org
Betreff: [RUS-WG] New Charter with review comments integrated
Wichtigkeit: Hoch
Hi RUS - team,
please find on gridforge a slightly modified charter that addressed review
comments:
(1)
The appearance of OMII - Europe was significantly reduced since OGF is a
community effort, not a project effort
(remains just in context interoperability with funded efforts)
(2)
The security paragraph of section 2.2 was more or less what also the other
groups in area security within OGF want to achieve. So I get rid of it.
(3)
I try to foster more what should be inside the second specification, however
I'm quite unsure if we should add a profile for connection technologies such
as WS-RF or if we just state a rendering section like within OGSA-BES with
respect to WS-RF.
If no other reviews or comments reach me by 20:00 this evening, I will send
our new charter to our area director.
Thanks for helps,
Morris
----------------------------------------------------------------------------
----
Morris Riedel
SW - Engineer
Distributed Systems and Grid Computing Division
Central Institute of Applied Mathematics
Research Centre Juelich
Wilhelm-Johnen-Str. 1
D - 52425 Juelich
Germany
Email: <mailto:m.riedel at fz-juelich.de> m.riedel at fz-juelich.de
Info: <http://www.fz-juelich.de/zam/ZAMPeople/riedel>
http://www.fz-juelich.de/zam/ZAMPeople/riedel
Phone: +49 2461 61 - 3651
Fax: +49 2461 61 - 6656
Skype: MorrisRiedel
'We work to improve ourselves and the rest of mankind.'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/rus-wg/attachments/20070126/53ae8391/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2396 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/rus-wg/attachments/20070126/53ae8391/attachment.bin
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00015.txt
Url: http://www.ogf.org/pipermail/rus-wg/attachments/20070126/53ae8391/attachment.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2396 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/rus-wg/attachments/20070126/53ae8391/attachment-0001.bin
------------------------------
--
rus-wg mailing list
rus-wg at ogf.org
http://www.ogf.org/mailman/listinfo/rus-wg
End of rus-wg Digest, Vol 4, Issue 13
*************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 16773 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/rus-wg/attachments/20070126/f52e1119/attachment-0001.bin
More information about the rus-wg
mailing list