<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffcc" text="#000000">
Hello, <br>
<br>
I agree with Philip. As a member of the group that convened to
discuss ESGF Security System Integration Tests, I think that the
corresponding document was pretty clear with identifying primary
issues and enumerating concrete tests that we should be able to
perform in the system. A careful review and execution of these
tests gives everyone a common baseline. We should no re-invent this
discussion when we have the fruits of a careful study of these
(security) integration issues.<br>
<br>
With regards to the wiki. I am of the mind that the wiki, in this
context, can (should) be used as a means of inditing our progress
through these tests and help coordinate where we are collectively as
we go through the ESGF Security System Integration Tests document.
We should also probably be having very regular conversations about
our progress on each front of this integration. I don't want to
speak too soon but I think the installation issues have waned... so
on to the next thing... integration.<br>
<br>
By the way... we should be codifying these tests into a suite of
tests. Indeed the manual process should be done up front, of
course, but I think that the result of this effort should be a
tangible test suite of CODE! I am a believer in better living
through code :-). The test suite should be *intuitive* and easy to
use and evolve with the federation. I'd be happy to start a repo for
these tools. I am going to assume that the suite will be of all
ilks, scripts, java, python, etc. no problem. I'll start setting
this up. :-).<br>
<br>
On 11/19/10 4:09 AM, <a class="moz-txt-link-abbreviated" href="mailto:philip.kershaw@stfc.ac.uk">philip.kershaw@stfc.ac.uk</a> wrote:
<blockquote
cite="mid:EB1E7CB92F5B35459E0B926D2A614DB60D7D5D2F@EXCHANGE19.fed.cclrc.ac.uk"
type="cite">
<pre wrap="">Hi Eric and all,
Firstly, thank you for raising the issue of testing and putting it up the agenda.
I can understand your concerns about scope of the testing and time available.
My concern though would be to keep this activity within the scope of what we already agreed.
At the September meeting at ANL one of the express purposes was to lay out a plan for federation wide testing of the security system. The document I referenced was an output from that. It's not complete and to a large extent just sets out a framework.
I'm not saying that we should slavishly keep to it if it's not going to address our needs. That said, because it was what we worked on together I think we should at the very least review it and take it into account. It could be that the outcome of that is we say, it's not suitable - and that would be fine. If we don't follow this process though, I think there's a danger of us not being consistent in our approach: perhaps missing out important items for testing our repeating or reinventing work that has already been done.
We can still have a test plan which encompasses a broad scope even if given time constraints, all those can't be met. The tests can be listed and against each we agree at what stage we do them in our process of completing and rolling out the system. It could be that some tests can't be done in the time - fine, but at least we have captured and recorded them. If we go with an alternative organic wiki approach to the plan there's a danger that important things are omitted.
I had more of a think about using a wiki for the plan and I still have some unease about it. Firstly, I appreciate the need for some kind of collaborative environment which we can all input into. However, the plan needs to have distinct 'releases' so that we have consistent benchmarks upon which we can analyse the system. E.g. this sets of releases of this set of software passed against these tests a, b, c described in version X of the test plan. There's a danger of things becoming vague if we grow a document organically and don't have a concept of distinct versions.
The test plan is an expression of what we expect the system to be able to do so it reflects the overall requirements. I think it's important we do this really well.
Just as a general observation I think it can be hard with this kind of large collaborative project to document what we do consistently and that contrasts with the rigour I've seen applied to the documentation process in other software development projects. That said, I think there's more that could be done and we would get a much better outcome for the system we deliver.
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 16:44
To: Estanislao Gonzalez
Cc: <a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a>; <a class="moz-txt-link-abbreviated" href="mailto:esg-gateway-dev@earthsystemgrid.org">esg-gateway-dev@earthsystemgrid.org</a>
Subject: Re: [esg-gateway-dev] [ESG-CET] CMIP5 Federation Testing
Outline
Hi Estani, Phil, Luca,
Thanks for all these thoughts and ideas (and Estani's action to place
the doc on the ESGF wiki.)
I agree that version control on the document is important. Is the
version history tracked on the wiki?
If not, can we place a revision history block at the top of the
document
and agree to utilize it?
Phil, thanks for noting the security document and attaching it for all.
I hesitated adding a link to that as it is not broadly accessible.
Indeed, much of the content there is very pertinent to this pre-release
testing work.
However, given the small amount of time we have to perform federation
testing I'd like to scope our collaborative work to what we feel is of
the highest importance (Eg: critical or blocking tests.) I think the
document should represent this as we work on it (tho there may be some
differing opinions on priority and I'll try to focus on resolving them
if so.)
I've sent a request to Gavin for editor acess on the wiki. Let's try
out collaborating on this on the ESGF wiki. Who else needs access?
Note: I've dropped esg-cet from the cc: list to lower the volume on
this
thread.
Thanks,
-Eric
Estanislao Gonzalez wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
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)
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.)
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
</pre>
</blockquote>
<pre wrap="">ready)
</pre>
<blockquote type="cite">
<pre wrap="">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.
Until we have a plugin for managing users in place I need to know
</pre>
</blockquote>
<pre wrap="">your
</pre>
<blockquote type="cite">
<pre wrap="">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>).
Thanks,
Estani
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:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Eric,
There's actually also the document we started at the ANL security
</pre>
</blockquote>
</blockquote>
<pre wrap="">meeting in Sept. :) ...
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
<a class="moz-txt-link-freetext" href="https://docs.google.com/document/d/17PcZqDs0zONyUa4A3Z835Rt">https://docs.google.com/document/d/17PcZqDs0zONyUa4A3Z835Rt</a>-
</pre>
</blockquote>
</blockquote>
<pre wrap="">_ePsEBKHWWP8XkawEow/edit?hl=en#
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
This is not visible to all so I've attached a PDF also. We could
</pre>
</blockquote>
</blockquote>
<pre wrap="">lift what we have in there to whatever format doc we want to use to
share with: wiki etc.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
My only reservation about a wiki approach is that you don't lose the
</pre>
</blockquote>
</blockquote>
<pre wrap="">concept of some kind of change control. I think it's important to keep
track of versions with a document like this.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
I think we could also prepare some test tools for system wide tests.
</pre>
</blockquote>
</blockquote>
<pre wrap="">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:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
<a class="moz-txt-link-freetext" href="http://proj.badc.rl.ac.uk/ndg/browser/TI12">http://proj.badc.rl.ac.uk/ndg/browser/TI12</a>-
</pre>
</blockquote>
</blockquote>
<pre wrap="">security/trunk/esg_system_tests/esg/security/test/system
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
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>
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">[<a class="moz-txt-link-freetext" href="mailto:esg">mailto:esg</a>-
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""><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
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">them,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">and what constitutes and acceptable outcome.
2) A tracking document to capture the tests themselves with
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">comments,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">dates and test related details as you note below.
I think a wiki is ideal for the outline (1) above. I agree
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">emailing a
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">document around is too cumbersome.
I think an issue tracker is ideal for (2) above. I propose we use
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">existing NCAR Jira system for this. Once we have a good outline
organized we can then create the necessary Jira tasks to track
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">progress
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">of
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">conducting each test between institutions (A,B), with an attached
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">date
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">the
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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-
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">ESSP
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">serve to coordinate our testing efforts, however, I need help
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">from
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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="">
</pre>
</blockquote>
</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>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">options
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">this
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">release.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">data
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">particular,
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</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"
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">below.)
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">For installation and update details, see the included email
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">below.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">require
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</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.
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">The
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">already
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">upgraded to the 1.2.0 RC1 version. If you have not yet upgraded
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">(<a class="moz-txt-link-freetext" href="http://esg.prototype.ucar.edu">http://esg.prototype.ucar.edu</a>)
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">tests
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">key
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">importance. I will send a follow up email regarding this
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">testing
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</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="">
</pre>
</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>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">1.1.0
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</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
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">can
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">
</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="">
</pre>
</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>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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="">
_______________________________________________
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="">
--
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>
</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="">--
Scanned by iCritical.
_______________________________________________
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>
<pre class="moz-signature" cols="72">--
Gavin M. Bell
Lawrence Livermore National Labs
--
"Never mistake a clear view for a short distance."
-Paul Saffo
(GPG Key - <a class="moz-txt-link-freetext" href="http://rainbow.llnl.gov/dist/keys/gavin.asc">http://rainbow.llnl.gov/dist/keys/gavin.asc</a>)
A796 CE39 9C31 68A4 52A7 1F6B 66B7 B250 21D5 6D3E
</pre>
</body>
</html>