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

[Bryan Lawrence]

---- Original Message ----
> From: Bryan Lawrence <bryan.lawrence at stfc.ac.uk>
> To: "Gavin M. Bell" <gavin at llnl.gov>
> CC: "philip.kershaw at stfc.ac.uk" <philip.kershaw at stfc.ac.uk>, "Dean N. 
Williams" <williams13 at llnl.gov>, Luca Cinquini 
<Luca.Cinquini at jpl.nasa.gov>, Estanislao Gonzalez 
<estanislao.gonzalez at zmaw.de>, Bob Drach <drach at llnl.gov>
> Subject:Re: [Go-essp-tech] [esg-node-dev] Re: [esg-gateway-dev] 
Upcoming gateway/datanode coordination points
>
> Hi Gavin
> 
> I think you are misunderstanding the thrust of my question, which is
> possibily fair enough, since I was being a wee bit provocative.
> 
> I don't much care what the SLA level is, I just care that it is
> jointly understood, documented, and everyone knows what it is. It
> clearly isn't. At this stage I cam concerend that most of us have no
> visibility of what you are doing, what the dependencies are for the
> rest of us on what you are doing, what the interfaces  are, and what
> the timetables are.
> 
> Given your response: I am particularly interested in where you have
> written detials of how the new architecture of the node will
> "ameliorate"  if not eliminate the issue of availabity of federation
> metadata for the security.
> 
> Thanks
> Bryan
> 
> > Hi Bryan,
> > 
> > As the other team members mentioned in this thread, availability is
> > not under such a stringent 'SLA' such that it will impede the
> > functioning of the federation.  In addition the architecture of the
> > node will greatly ameliorate, if not eliminate the issue of
> > availability.
> > 
> > Indeed Phil brought up a good point with the Attribute Service.  I
> > would like to fix a time for us to all meet and discuss the issues
> > surrounding that service and availability.
> > 
> > On 3/18/11 2:15 AM, Bryan Lawrence wrote:
> > > 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
> 
> --
> 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

--
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