[Go-essp-tech] CMIP5 Data Coming February 1st

[Cinquini, Luca (3880)]

Hi Dean,
thanks for the notice... indeed it might be a very good idea to focus on CMIP5 preparedness on the next GO-ESSP conf call.

This is my personal understanding of the situation:

o Local system (Data Node + Gateway) are able to collect and deliver data, and register users.

o Single Sign On among federation patners is working correctly

o An issue has been uncovered which affects authorization when the Data Node is front-ended by a proxy, as it happens for BADC:
http://esgf.org/bugzilla/show_bug.cgi?id=11

o Another issue has been uncovered recently which affects a user from gateway A downloading data published to gateway B when using wget/curl, when the data is protected by the an attribute controlled by Gateway C (for example, the PCMDI attribute "CMIP5 Research"): the download will work only if the user from Gateway A has already logged into Gateway B. This may not be the most critical case, at this point... See http://esgf.org/bugzilla/show_bug.cgi?id=12

o We have not performed extensive testing of metadata exchange yet, although it is generally believed to work.

Everybody, please add your understanding of the current status...

thanks, Luca

On Jan 14, 2011, at 10:04 AM, Williams, Dean N. wrote:

Dear Colleagues,

            Karl has informed me that we are expecting to receive CMIP5 model output in 3 weeks, so we must have ESG ready to publish and distribute data to the community by February 1st. At the moment, the targeted model output is CCCma (Canadian Centre for Climate Modelling and Analysis). (I am sure other data sets will quickly follow suit.) To be ready, we must have federation completed. Luca, Stephen, Eric, Craig, and others can you give the status of the federation testing? The last I remember:


 1.  Stephen was going to include some Hadley data for federation federation testing;
 2.  Craig was testing replication from multiple sites;
 3.  Federation security was in place;

   From what I remember, The federation was mainly completed and mostly tested with a few minor changes needed. Primarily we need to test federation between PCMDI-BADC, PCMDI-DKRZ, PCMDI-ANU, etc.. What else are we missing to be ready for the Febuary 1st deadline?

    Perhaps this next Tuesday, we can discuss our preparedness for the onslaught of data. How many of us will be around for a Tuesday go-essp meeting at our regular time?

Thanks and best regards to all,
            Dean

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20110114/1e6200ab/attachment.html