[SAGA-RG] SAGA Resource Package Comments

Steve Fisher dr.s.m.fisher at gmail.com
Wed Jan 16 08:33:03 EST 2013


Andre,

I like the generality that a resource provides services - however I take
your point that it does make the users code more verbose. Perhaps
getService(capability) would do the trick where capability is the set of
capabilites that you require for the service. It provides at most one
service.

Steve


On 16 January 2013 12:29, Shantenu Jha <shantenu.jha at rutgers.edu> wrote:

> On 1/16/13 7:13 AM, Andre Merzky wrote:
>
>> On Wed, Jan 16, 2013 at 1:01 PM, Ole Weidner <ole.weidner at rutgers.edu>
>> wrote:
>>
>>> Why not? I should be able to use a "network resource" to manage my
>>> bandwidth
>>> reservations / allocations, right?
>>>
>> A network resource is only useful if you can specify what resources it
>> connects -- that is one of the uses we had for the resource pool,
>> which I think won't exist anymore in the next version.  So, how would
>> you specify connectivity?
>>
>>  It is still early days in our understanding, but at some stage possibly,
> the ability to include
> networks as a resource will be important. We have not scoped this out yet,
> but
> my hope would be that the current design would be "extensible" to
> other/novel
> resources as eventually needed, whilst retaining simplicity to address the
> compute
> and storage resources that are well known at this stage.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/saga-rg/attachments/20130116/de24486a/attachment.html>


More information about the saga-rg mailing list