[Go-essp-tech] PCMDI3 not responding

[philip.kershaw at stfc.ac.uk]

That sounds good - thanks Luca.

Phil

On 06/06/2011 12:53, "Cinquini, Luca (3880)" <Luca.Cinquini at jpl.nasa.gov>
wrote:

>Hi all,
>	the p2p stack does have a standalone attribute service, that could be
>deployed on  a separate Tomcat instance. The only missing piece would be
>to write the plugin to read the attributes from the gateway db.
>But in general - should we consider discussing the registration workflows
>and single point of failure problem at tomorrow's go-essp call ? I'll add
>it as a possible agenda item.
>thanks, Luca
>
>On Jun 6, 2011, at 5:48 AM, <philip.kershaw at stfc.ac.uk> wrote:
>
>> I thought that pcmdi3 had a some kind of failover system in place?
>> 
>> With the existing infrastructure it should be possible to mirror the
>>PCMDI attribute service at other locations in the federation.
>> 
>> Cheers,
>> Phil
>> 
>> From: Estanislao Gonzalez <gonzalez at dkrz.de<mailto:gonzalez at dkrz.de>>
>> Organization: DKRZ
>> Date: Mon, 6 Jun 2011 13:26:43 +0200
>> To: <stephen.pascoe at stfc.ac.uk<mailto:stephen.pascoe at stfc.ac.uk>>
>> Cc: <drach1 at llnl.gov<mailto:drach1 at llnl.gov>>,
>><go-essp-tech at ucar.edu<mailto:go-essp-tech at ucar.edu>>
>> Subject: Re: [Go-essp-tech] PCMDI3 not responding
>> 
>> Hi,
>> 
>> is it possible to separate the attributeService from the gateway? The
>>most simple way would be a second installation with only 443 access and
>>the gui turned off or something alike.  I'm just thinking that mixing
>>the central attribute service with the production Gateway is not very
>>wise in the long run. If it breaks, it breaks the whole federation... We
>>don't need springs nor even tomcat for that, the more we can strip the
>>service down the more robust it will get.
>> Of course this is only a half-step solution, which we should continue
>>ASAP. I totally agree with Stephen..
>> And in any case a DOS attack to us is so simple that it makes me cry...
>> 
>> Thanks,
>> Estani
>> 
>> Am 06.06.2011 13:07, schrieb
>>stephen.pascoe at stfc.ac.uk:<mailto:stephen.pascoe at stfc.ac.uk:>
>> The PCMDI3 node isn't responding today.  This is preventing all access
>>to CMIP5 data as the PCMDI AttributeService is queried for each download
>>or when a user browses to  that dataset in a Gateway.
>> 
>> I think this single point of failure is a big problem in the system --
>>we need to address it ASAP.
>> 
>> Stephen.
>> 
>> ---
>> Stephen Pascoe  +44 (0)1235 445980
>> Centre of Environmental Data Archival
>> STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK
>> 
>> 
>> 
>> --
>> Scanned by iCritical.
>> 
>> 
>> 
>> _______________________________________________
>> GO-ESSP-TECH mailing list
>> 
>>GO-ESSP-TECH at ucar.edu<mailto:GO-ESSP-TECH at ucar.edu>http://mailman.ucar.ed
>>u/mailman/listinfo/go-essp-tech
>> 
>> 
>> 
>> --
>> Estanislao Gonzalez
>> 
>> Max-Planck-Institut für Meteorologie (MPI-M)
>> Deutsches Klimarechenzentrum (DKRZ) - German Climate Computing Centre
>> Room 108 - Bundesstrasse 45a, D-20146 Hamburg, Germany
>> 
>> Phone:   +49 (40) 46 00 94-126
>> E-Mail:  gonzalez at dkrz.de<mailto:gonzalez at dkrz.de>
>> 
>> _______________________________________________ GO-ESSP-TECH mailing
>>list GO-ESSP-TECH at ucar.edu<mailto:GO-ESSP-TECH at ucar.edu>
>>http://mailman.ucar.edu/mailman/listinfo/go-essp-tech
>> -- 
>> Scanned by iCritical.
>> _______________________________________________
>> GO-ESSP-TECH mailing list
>> GO-ESSP-TECH at ucar.edu
>> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech
>

-- 
Scanned by iCritical.