[Go-essp-tech] [esg-gateway-dev] [esg-node-dev] Re: Upcoming gateway/datanode coordination points

[Gavin M. Bell]

Hello Team,

So indeed you guys are all correct, thanks for responding to Bryan
giving him a good context in which to think about the registry service. 
Nathan, indeed as you indicated there are points of integration that we
need to touch base on.  I think next week would be a good time to do
so.  It would be good to get on the same page with the xsd.  I am not
sure which version you are using and I discovered a few more
modifications that had to be made, which also simplifies things as
well.  We have to make sure we capture all the information and agree on
the xsd organization.

Indeed the registration information will be able to be easily aggregated
and disseminated and as you and  Estani mentioned, cached.

On 3/18/11 7:13 AM, Nathan Wilhelmi wrote:
> Hi Estani,
>
> The caching you describe is implemented in the gateway now. All the 
> registry information is persisted in the database and the code that 
> synchronizes with the registry is decoupled from the parts that use the 
> registry information. As such if worst came to worst one could directly 
> modify the database if a change was needed and the service is down.
>
> -Nate
>
> On 03/18/2011 04:21 AM, Estanislao Gonzalez wrote:
>> Hi Bryan,
>>
>> I don't think it is important to be available 24x7. I hope (probably is
>> not developed, but will be pretty simple to do) that the Gateway caches
>> the last registry document found, so that it can be still restarted
>> without problem if precisely at that moment PCMDI's central registry is
>> not available.
>>
>> The worst case scenario would be if someone wants to install a Gateway
>> anew and at precisely that moment the registry is down. this could be
>> solved by packing a "pre-cached" version of the registry with it (not
>> that I think this will be that important, as adding this new Gateway to
>> the federation will take time).
>>
>> So while the server is down, no new Gateway can be added to the
>> federation, nor any other changes be done. But the federation itself
>> should work without a hitch.
>>
>> But perhaps I'm missing something here...
>>
>> Thanks,
>> Estani
>>
>>
>> Am 18.03.2011 10:15, schrieb Bryan Lawrence:
>>> Hi Gavin
>>>
>>> What will the API be to this registry?
>>> What service level with PCMDI provide for it (since it's going to have
>>> to work 24x7 globally)?
>>>
>>> Thanks
>>> Bryan
>>>
>>>
>>>> We will have a single registry, it should be served from PCMDI on
>>>> pcmdi3.  The esgf nodes will all be coded to set pcmdi3 as the
>>>> default location for this registry.  Indeed coordination with Nate
>>>> and Neill and Rachana will have to take place.  I suspect that early
>>>> next week will be that time.  Stay tuned, we'll make this happen.
>>>> ;-)
>>>>
>>>> On 3/17/11 8:32 AM, philip.kershaw at stfc.ac.uk wrote:
>>>>> So long as we are co-ordinated on this.  Will we have a single
>>>>> registry for the federation or many?  I'm opening that question
>>>>> more widely to all …
>>> --
>>> Bryan Lawrence
>>> Director of Environmental Archival and Associated Research
>>> (NCAS/British Atmospheric Data Centre and NCEO/NERC NEODC)
>>> STFC, Rutherford Appleton Laboratory
>>> Phone +44 1235 445012; Fax ... 5848;
>>> Web: home.badc.rl.ac.uk/lawrence
>>>
> _______________________________________________
> esg-gateway-dev mailing list
> esg-gateway-dev at mailman.earthsystemgrid.org
> http://mailman.earthsystemgrid.org/mailman/listinfo/esg-gateway-dev

-- 
Gavin M. Bell
--

 "Never mistake a clear view for a short distance."
       	       -Paul Saffo


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20110318/00135bcd/attachment.html