Yo,
I recommend calling the Thing That Henry Does Not Want To Call A
root-GIIS, a "HBII".
Back in EDG we had the 'HairBall' LFN test file and 'hairball' use case
but I never managed to get anyone to call something a hairball.
BTW the original names of the BDII were the 'fake-II' and 'hack-II' but
those didn't stick either.
J "or we could call it the Pack Rat II" T
Henry Nebrensky wrote:
> On Thu, 24 Nov 2005, Jeff Templon wrote:
> ...
>
>>my take on the matter: the old BDII was originally made to take over the
>>function of the top-level info index; later the *software system* BDII
>>was used to implement lower levels of the system as well. Hence the
>>confusion, as you guys have already summarized.
>>
>>I think we should start separating the two. The BDII is a software
>>product. GRIS and GIIS would be OK except people might confuse them
>>with the globus products. We have
>>
>>GRIS (Grid Resource Info Service) -- single computer
>>GIIS (Grid Index Info Service) - anything that aggregates info from
>>multiple sources.
>>
>>GRIS is clear, GIIS is the problem in that there are multiple flavors.
>
>
> Depending on whether the "multiple flavors" is read as referring to
> site-vs-root (below) or MDS-vs-BDII; I would add that IMHO as S stands for
> service anything that exposes the right interface and supplies the
> expected set of information can be a GIIS, however it's implemented.
>
> So I'm quite happy with the "site-GIIS" suggestion (which the GOC DB
> already uses).
>
>
>>We could easily come up with site-GIIS which aggregates over a single
>>grid site, and root-GIIS which aggregates over all sites in a particular
>>grid federation.
>
>
> My objections to this would be that
>
> - the nutrient information That Thing distributes actually originates at
> a whole lot of resource GRIS's (trunk-GIIS? stalk-GIIS?)
>
> - people will refer to the site-GIIS as just a "GIIS", and we'll end up
> with the reverse confusion
>
> (and to top-level-BDII, suggested elsewhere
> - it's only a top-level anything in that it publishes data actually
> created several layers lower in the organisation. And where would
> something aggregating across Grids go?)
>
>
> My own preference would be to call it Something Utterly Different,
> but the best I can think of this late is Information Intermediary (is the
> old II acronym available for reuse yet?) or maybe Information Aggregation
> Service.
>
> Thanks
>
> Henry
>
>
> VOs wanting to use a filtered list of SUDs would implement an Information
> Intermediary Identifier (III). Wise experiments would have several IIIs in
> case of problems, and thus deploy an Information Intermediary Identifier
> Index (IIII).
>
> Hey, scalability's good, right?
>
|