[Go-essp-tech] ESGF Registry Group Meeting June 28th @ 9am PDT

[Don Middleton]

Seconded. Closed source and black-box components are not going to serve our community well. We can't just install this on any of our production systems, and we need to have transparency in terms of what it does.

don


On Jun 28, 2011, at 3:13 AM, <philip.kershaw at stfc.ac.uk> <philip.kershaw at stfc.ac.uk> wrote:

> Hi Gavin,
> 
> Doesn't this break the idea of interfaces?  We agreed at the ESGF meeting that we would document the interfaces in the system so that anyone given a spec could go away and write code that adheres to it.
> 
> It's great that you have this system that people can install and I'm sure it may meet some sites' deployment requirements.  However, there are cases where it will not.   Stephen has mentioned such a case where some visibility to the code base is needed.    If we fully define the interfaces we give the maximum possibility for take up of ESGF: participating sites can use code we develop or roll their own, the choice is theirs.   We're open to how to best suit their particular needs.
> 
> Cheers,
> Phil
> 
> From: "Gavin M. Bell" <gavin at llnl.gov<mailto:gavin at llnl.gov>>
> Date: Mon, 27 Jun 2011 14:05:45 -0700
> To: Nathan Wilhelmi <wilhelmi at ucar.edu<mailto:wilhelmi at ucar.edu>>
> Cc: "go-essp-tech at ucar.edu<mailto:go-essp-tech at ucar.edu>" <go-essp-tech at ucar.edu<mailto:go-essp-tech at ucar.edu>>
> Subject: Re: [Go-essp-tech] ESGF Registry Group Meeting June 28th @ 9am PDT
> 
> Hi,
> 
> Easy
> 
> 1) To become a node, run the install script and install a node.
> 2) To read registry information point to the registration.xml file (by url or filesystem path according to your context) and read it.
> 3) To write to it... configure your node accordingly (using the node installer or by hand, if you are a masochist) and the salient information will automatically be gleaned and used.
> 
> The entire point of building this was to make things 'hands free' and easy for users.
> 
> I guess this will be a short meeting. :-)
> 
> On 6/27/11 12:54 PM, Nathan Wilhelmi wrote:
> 
> Hi Gavin,
> 
> From my perspective the important aspect would be discussing the issues
> Rick has raised, namely details of how one becomes a node to R/W
> registry information.
> 
> -Nate
> 
> 
> Gavin M. Bell wrote:
> 
> 
>  Hello Gentle-people,
> 
> So, based on the doodle pole (http://doodle.com/28vv25qpmbivmhvv ) a
> good time to meet is tomorrow @ 9am PDT.
> 
> The number is +1-925-422-7436 code 305757#
> 
> I don't quite know what we wish to discuss so...
> I invite you all to edit the group's wiki page accordingly, to add
> discussion topics.
> We only have the line for 30 minutes (I will check to see if I can get
> it for an hour) so try to keep it pithy.
> 
> As I recall we wanted to talk about xml sec, but that is all I recall.
> 
> 
> --
> Gavin M. Bell
> Lawrence Livermore National Labs
> --
> 
> "Never mistake a clear view for a short distance."
>               -Paul Saffo
> 
> (GPG Key - http://rainbow.llnl.gov/dist/keys/gavin.asc)
> 
> A796 CE39 9C31 68A4 52A7  1F6B 66B7 B250 21D5 6D3E
> 
> 
> 
> 
> --
> Gavin M. Bell
> Lawrence Livermore National Labs
> --
> 
> "Never mistake a clear view for a short distance."
>               -Paul Saffo
> 
> (GPG Key - http://rainbow.llnl.gov/dist/keys/gavin.asc)
> 
> A796 CE39 9C31 68A4 52A7  1F6B 66B7 B250 21D5 6D3E
> 
> 
> _______________________________________________ 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