<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I've already took the liberty to move it into esgf. The page can be
found here: <a class="moz-txt-link-freetext" href="http://esgf.org/wiki/Cmip5Status/Tests">http://esgf.org/wiki/Cmip5Status/Tests</a> (Phil I haven't
gone through your doc yet)<br>
<br>
I also modified some things, please check this is ok. (GridFTP from
federation node is not possible, is it? Maybe something else was
meant, please check.)<br>
<br>
I think it's better to keep everything on the same "page". We could
link every test to a page only viewable by Editors or any registered
user, as you like. We could use Jira or ESG's bugzilla (if it's
ready) for tracking specific problems, but I do think that storing
the results on tickets is not the best option, as with time they get
obfuscated by new tickets... A table with the results, or at least
with the positive results, should be IMO better. What what really
matters is to gather all links at the sameplace and I think esgf
wiki does the job.<br>
<br>
Until we have a plugin for managing users in place I need to know
your names to add you to the editor group. Please send them two
me/Gavin/Luca... or any other
Admin(<a class="moz-txt-link-freetext" href="http://esgf.org/wiki/AdminGroup">http://esgf.org/wiki/AdminGroup</a>). <br>
<br>
Thanks,<br>
Estani<br>
<br>
<br>
On 11/18/2010 05:05 PM, <a class="moz-txt-link-abbreviated" href="mailto:philip.kershaw@stfc.ac.uk">philip.kershaw@stfc.ac.uk</a> wrote:
<blockquote
cite="mid:EB1E7CB92F5B35459E0B926D2A614DB60D7D5B0F@EXCHANGE19.fed.cclrc.ac.uk"
type="cite">
<pre wrap="">Hi Eric,
There's actually also the document we started at the ANL security meeting in Sept. :) ...
<a class="moz-txt-link-freetext" href="https://docs.google.com/document/d/17PcZqDs0zONyUa4A3Z835Rt-_ePsEBKHWWP8XkawEow/edit?hl=en#">https://docs.google.com/document/d/17PcZqDs0zONyUa4A3Z835Rt-_ePsEBKHWWP8XkawEow/edit?hl=en#</a>
This is not visible to all so I've attached a PDF also. We could lift what we have in there to whatever format doc we want to use to share with: wiki etc.
My only reservation about a wiki approach is that you don't lose the concept of some kind of change control. I think it's important to keep track of versions with a document like this.
I think we could also prepare some test tools for system wide tests. I've attempted to kick this off by preparing a Python test script to probe the SSL endpoints in the federation and check for correct configuration:
<a class="moz-txt-link-freetext" href="http://proj.badc.rl.ac.uk/ndg/browser/TI12-security/trunk/esg_system_tests/esg/security/test/system">http://proj.badc.rl.ac.uk/ndg/browser/TI12-security/trunk/esg_system_tests/esg/security/test/system</a>
Cheers,
Phil
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:esg-gateway-dev-bounces@mailman.earthsystemgrid.org">esg-gateway-dev-bounces@mailman.earthsystemgrid.org</a> [<a class="moz-txt-link-freetext" href="mailto:esg">mailto:esg</a>-
<a class="moz-txt-link-abbreviated" href="mailto:gateway-dev-bounces@mailman.earthsystemgrid.org">gateway-dev-bounces@mailman.earthsystemgrid.org</a>] On Behalf Of Eric
Nienhouse
Sent: 18 November 2010 15:52
To: Cinquini, Luca (3880)
Cc: ESG-CET Mail List; <a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a>; esg-gateway-
<a class="moz-txt-link-abbreviated" href="mailto:dev@earthsystemgrid.org">dev@earthsystemgrid.org</a>
Subject: Re: [esg-gateway-dev] [ESG-CET] CMIP5 Federation Testing
Outline
Hi Luca, All,
Thanks for this input. What I would propose are two "documents" to
support this testing work:
1) An outline of the tests with some detail about how to perform them,
and what constitutes and acceptable outcome.
2) A tracking document to capture the tests themselves with comments,
dates and test related details as you note below.
I think a wiki is ideal for the outline (1) above. I agree emailing a
document around is too cumbersome.
I think an issue tracker is ideal for (2) above. I propose we use the
existing NCAR Jira system for this. Once we have a good outline
organized we can then create the necessary Jira tasks to track progress
and issues.
Does this sound reasonable?
Thanks,
-Eric
Cinquini, Luca (3880) wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Eric,
thanks for starting this document, the list of tests to perform
</pre>
</blockquote>
<pre wrap="">looks like a good start - we might want expand it in a little more
detail, like for example distinguishing between:
</pre>
<blockquote type="cite">
<pre wrap="">
1) http file download via browser started at the gateway
2) http file download via browser started at the TDS page
3) http multi-files download via wget script (directly to the TDS)
for both home data node and federated data node.
We might also want to have a matrix table where we list the result of
</pre>
</blockquote>
<pre wrap="">conducting each test between institutions (A,B), with an attached date
when the test was last performed.
</pre>
<blockquote type="cite">
<pre wrap="">
As for where the document should live, I personally favor the esgf
</pre>
</blockquote>
<pre wrap="">wiki option, although I could also go with 3) and 4). Exchanging the
document by email is kind of cumbersome IMO.
</pre>
<blockquote type="cite">
<pre wrap="">
thanks, Luca
On Nov 18, 2010, at 7:25 AM, Eric Nienhouse wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear ESG Gateway Collaborators,
We discussed the need for federation testing in our recent GO-ESSP
call. I would like to continue our test planning discussion and
collaboratively develop a document to support this effort.
I welcome your input and insights, in particular for testing
</pre>
</blockquote>
</blockquote>
<pre wrap="">scenarios
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">related to security and access control of CMIP5 datasets. I plan to
serve to coordinate our testing efforts, however, I need help from
others to develop and document them.
I have an draft outline of these key federation tests at the link
</pre>
</blockquote>
</blockquote>
<pre wrap="">below
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">and I would like your input:
</pre>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="https://wiki.ucar.edu/display/esgcet/CMIP5+Federation+Testing+Task+Matr">https://wiki.ucar.edu/display/esgcet/CMIP5+Federation+Testing+Task+Matr</a>
ix
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
Several options exist to enable collaborative access to this
</pre>
</blockquote>
</blockquote>
<pre wrap="">document.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I'd like suggestions from others on the best approach. Some options
</pre>
</blockquote>
</blockquote>
<pre wrap="">follow:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
1) Exchange this document by email and merge edits (we've done this
</pre>
</blockquote>
</blockquote>
<pre wrap="">in
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">the past)
2) Move the document to the ESGF wiki (Stephen and Estani have
suggested this already.)
3) Keep it on wiki.ucar.edu and provide logins to all
</pre>
</blockquote>
</blockquote>
<pre wrap="">collaborators.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">4) Move it to Google Docs.
There is momentum to use the ESGF wiki as at least one supporting
document may already be there (CMIP5 Status of Gateways and
</pre>
</blockquote>
</blockquote>
<pre wrap="">Datanodes.)
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
What do others think would be best?
Thanks for your input on this.
Kind regards,
-Eric
Eric Nienhouse wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear ESG Gateway Collaborators,
We're quickly approaching the 1.2.0 ESG Gateway software release.
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">This
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">version will provide the basis for the upcoming CMIP5 activity data
management effort.
The Gateway 1.2.0 Release Candidate 1 (RC1) is now available for
inter-gateway federation testing. We encourage all who can to
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">upgrade
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">to this version as soon as is reasonably possible. (In particular,
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">if
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">your gateway is on the list of "Key Participating Gateways" below.)
For installation and update details, see the included email below.
Please note that the Gateway 1.2.0 RC1 requires a corresponding
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">Data
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Node version 1.0.4.0 or greater. This Gateway upgrade may require
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">an
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">update to your Data Node components as well.
We're in need of significant inter-gateway (eg: federation)
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">testing.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">In order to begin this process, it is important that all
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">participating
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">gateways are running a consistent pre-release 1.2.0 version. The
1.2.0 RC1 is the recommended version for federation related
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">testing.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
Following are the Key Participating Gateways. Several have already
upgraded to the 1.2.0 RC1 version. If you have not yet upgraded to
the 1.2.0 RC1 version, please advise as to when this may be
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">reasonably
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">possible. (Please send any details or questions to:
<a class="moz-txt-link-abbreviated" href="mailto:esg-gateway-dev@earthsystemgrid.org">esg-gateway-dev@earthsystemgrid.org</a>)
ANU
BADC
DKRZ
JPL
LBNL
NCAR
ORNL
PCMDI
Please note the NCAR testing site (<a class="moz-txt-link-freetext" href="http://esg.prototype.ucar.edu">http://esg.prototype.ucar.edu</a>)
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">currently running the 1.2.0 RC1 version for federation testing
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">purposes.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
I would like to begin discussing the top priority federation tests
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">would like to hear your input. In particular, testing scenarios
related to security and access control of CMIP5 datasets are of key
importance. I will send a follow up email regarding this testing
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">effort.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
Thank you for your involvement in this effort!
Kind Regards,
-Eric
On Sun, 14 Nov 2010 20:15:48 -0700
Nathan Wilhelmi <a class="moz-txt-link-rfc2396E" href="mailto:wilhelmi@ucar.edu"><wilhelmi@ucar.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello,
We have made a new release of the gateway available, 1.2.0-RC1.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">The
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">release resolves a number of issues that were identified in the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">BETA3
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">release.
The new BETA release can be downloaded directly from here:
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="https://vets.development.ucar.edu/nexus/content/repositories/releases/s">https://vets.development.ucar.edu/nexus/content/repositories/releases/s</a>
gf/gateway/1.2.0-RC1/
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
For this release the the new installation and upgrade from 1.1.0
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">guides
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">remain the same.
If you already have 1.2.0-BETAx installed upgrade instructions can
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">be
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">found here:
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><a class="moz-txt-link-freetext" href="https://wiki.ucar.edu/display/esgcet/Gateway+Upgrade+Instructions+%28ve">https://wiki.ucar.edu/display/esgcet/Gateway+Upgrade+Instructions+%28ve</a>
rsion+1.2.0-BETA-1.2.0-BETA2+to+version+1.2.0-BETA3%29
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
Please provide feedback (good or bad!) to:
<a class="moz-txt-link-abbreviated" href="mailto:esg-gateway-dev@earthsystemgrid.org">esg-gateway-dev@earthsystemgrid.org</a>
-or-
If you have Jira Issue Tracking access, please enter a trouble
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">ticket
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">against version "1.2.0-RC1" under the "Affects Version/s" drop-
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">down.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
Thanks!!!
-Nate
</pre>
</blockquote>
</blockquote>
<pre wrap="">_______________________________________________
ESG-CET mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ESG-CET@earthsystemgrid.org">ESG-CET@earthsystemgrid.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.ucar.edu/mailman/listinfo/esg-cet">http://mailman.ucar.edu/mailman/listinfo/esg-cet</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
esg-gateway-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:esg-gateway-dev@mailman.earthsystemgrid.org">esg-gateway-dev@mailman.earthsystemgrid.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.earthsystemgrid.org/mailman/listinfo/esg-gateway-dev">http://mailman.earthsystemgrid.org/mailman/listinfo/esg-gateway-dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
esg-gateway-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:esg-gateway-dev@mailman.earthsystemgrid.org">esg-gateway-dev@mailman.earthsystemgrid.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.earthsystemgrid.org/mailman/listinfo/esg-gateway-dev">http://mailman.earthsystemgrid.org/mailman/listinfo/esg-gateway-dev</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
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: <a class="moz-txt-link-abbreviated" href="mailto:estanislao.gonzalez@zmaw.de">estanislao.gonzalez@zmaw.de</a>
</pre>
</body>
</html>