[Go-essp-tech] [esg-node-dev] CMIP5 Datanode : data access services.

[Sébastien Denvil]

  Hi Stephen,

thanks all for your answers. See some answers/questions below.

On 03/05/2011 11:32, stephen.pascoe at stfc.ac.uk wrote:
> Hi Sebastien,
>
> As I hope others have explained, the ESGF software can support gridFTP and OPeNDAP access at this time, however each node and gateway are moving at different paces on configuring and testing these features.  At BADC we are at full stretch keeping up with CMIP5 publishing and I regret the timescale for these features keep slipping.  It is invaluable for us to hear what the user's immediate needs are; thanks.
>
> So, what is your first priority?  Configuring the IPSL datanode to support gridFTP and/or OPeNDAP or having gridFTP/OPeNDAP enabled on other datanodes?

Our first priority is to configure IPSL datanode to support OPeNDAP. We 
will in parallel upgrade our netcdf library and clients to the 4.1.2 
release.

GridFTP will come after that. Regarding gridFTP we target to install the 
"end user" version first.

> If you enable gridFTP on your datanode the BADC gateway can publish gridFTP download links today with very little effort.  Similarly Phil and I have experience of the security-enabled netCDF client library and can help there.  I hope others can help with configuring OPeNDAP and LAS on the datanode (particularly LAS) as I haven't got there yet.
>
> At BADC we have 90% of the gridFTP setup in place but I will need to republish all our THREDDS catalogs to fix a small metadata inconsistency.  I intend to do this once we've deployed a fresh datanode version.  Similarly I'd rather fix OPeNDAP once a new datanode version is in place.  If this is a real priority for you I can work out a firm deadline.

When you say you have 90% of the gridFTP setup in place, you mean the 
bdm configuration or the "end user" one? The bdm one will be use for 
replication right?
Gavin mentioned that the bdm configuration has been tested/validated but 
the "end user" one not completely. At least it was my understanding.

See you next week in Asheville.

Cheers.
Sébastien

> Cheers,
> Stephen.
>
> ---
> Stephen Pascoe  +44 (0)1235 445980
> Centre of Environmental Data Archival
> STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK
>
>
> -----Original Message-----
> From: owner-esg-node-dev at lists.llnl.gov [mailto:owner-esg-node-dev at lists.llnl.gov] On Behalf Of Sébastien Denvil
> Sent: 02 May 2011 14:32
> To: esg-node-dev at lists.llnl.gov; go-essp-tech at ucar.edu
> Subject: [esg-node-dev] CMIP5 Datanode : data access services.
>
>    Dear all,
>
> we received increasing demand asking for regional model boundary
> conditions from CMIP5 simulations. Those datasets are heavy and
> therefore "wget" is not my favourite answer. I would like this answer to
> be base on a ESG-F solution and not a home made one.
>
> In order to build a meaningful response I would like to know what are
> the plan regarding the datanode to have :
> - openDAP enable with CMIP5 filters.
> - netCDF subsets enable with CMIP5 filters.
>       * openDAP and/or netCDF subsets will be very useful for those
> focusing on a specific region (Africa OR Asia for example). They could
> then extract only the area of interest.
>
> - gridFTP enable with CMIP5 filters.
>       *gridFTP will be very useful for those focusing on many regions
> and/or doing the CORDEX exercise but without a limited area model. It's
> very likely that they will download the whole datasets.
>
> My understanding is that gridFTP is not fully functional at this point
> of time and that openDAP and netCDF subsets are not yet secure by the
> ESG-F security layer.
>
> A corollary coming from those questions : Is there a documentation we
> could refer to if we want to update a production data node?
>
> Please refine my understanding.
>
> Thanks.
> Sébastien
>


-- 
Sébastien Denvil
IPSL, Pôle de modélisation du climat
UPMC, Case 101, 4 place Jussieu,
75252 Paris Cedex 5

Tour 45-55 2ème étage Bureau 209
Tel: 33 1 44 27 21 10
Fax: 33 1 44 27 39 02


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4172 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20110504/1e869ea0/attachment.bin