[geclipse-dev] Storage vs. Service

[Mateusz Pabiś <uranium@xxxxxxxxxxxxx>]

Hi *,

This is about gLite middleware.

According to the discussion during our meeting today, we want to decide 
if LFC should be in Storage or Service branch of VO.

Just to remind, we have 3 branches: Computing, Services, Storage. 
Services are divided into 4 categories: Info, Job Status, Job Submission 
and Other Services.

Right now, LFC goes to Other Services. Storage Elements are grouped in 
Storage (each can be accessible via several protocols [ex. gsiftp, srm]).

We agreed on that LFC is a service of higher level than casual Storage 
Element, since LFC provides a catalogue for data distributed among 
Storage Elements.

We have gathered few ideas:
1. keep as it is
pros:
- no effort required
cons:
- it's hard to find LFC endpoint among other services
- "service" reminds request-response paradigm

2. create a new branch in Services: Data Access Services
pros:
+ all data access services are clustered in one place
+ it's easy to find LFC endpoint
+ small changes to gEclipse model (no critical changes)
cons:
- "service" reminds request-response paradigm

3. create an entry for LFC in Storage branch
pros:
+ logically consistent (LFC behaves as storage element)
+ easy integration with MountAction
cons:
- large effort changing gEclipse model (not recommended while we're 
introducing new middleware)

--
Mateusz Pabis